I'm testing this 20190222 right now.
My setup:
- lineage-15.1-20190222-UNOFFICIAL-i9300
- MindTheGapps-8.1.0-arm-20180808_153837
- addonsu-15.1-arm-signed
I encounter a similar issue, as I described earlier (referred to 20190306-UNOFFICIAL). Occasionally, my phone suffers from a massive slowdown. For example, when I open Chrome and press menu button on the phone, when Chrome menu pops up, there is this unnatural, annoying slowdown. Or when I open SwiftKey Keyboard control panel, is the same thing, everything slowing down enormously.
But so far, there are minor differences of this issue, between 20190306-UNOFFICIAL and 20190222-UNOFFICIAL:
- with 20190222, if I close an app in which problem occur, everything else works fine, but with 20190306, issue were present until the device was restarted,
- with 20190222, those issues are limited to specific apps (I mean, at the moment, because I've only been testing for a few hours), and to be even more precise - to a specific elements of those apps, but with 20190306, those slowdowns occurred also out of sudden, no matter what I did.
When comparing to 14.1, battery drain seems to be worse on 15.1. And overall performance is noticeably worse than 14.1.
I will continue testing for a few more days.
will this work on sprints galaxy s3 L710? if not, will they update it?
lastest standart build have software restarting problem when the device heats up.
That's the best compromise, I do it so too. The stability, over all performance and the low battery drain of 14.1 is currently not yet available at 15.1 or 16.0. LOS 16.0 runs very smoothly in the beginning, but in the long run, RAM usage increases immeasurably and everything goes into the swap. This makes a fluidly working impossible. 14.1 works here in deep sleep mode for almost two days, until the battery is empty.So I just stick with LOS14.1 and I will be waiting for more stable LOS16.
Thank you very much for your time. I have replaced the Lineageos 14.1 Nougat with Lineageos 15.1. I tried running Android Auto and received an error message that some google services are missing. Has anyone managed to get Android Auto working? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Did you install open gapps pico?
Try using nano instead and try again.
BTW there's already a LineageOS 16 if you want to be more up to date.
https://xdaforums.com/galaxy-s3/development/rom-lineageos-16-0-t3875899/amp/
Heya, can you provide a link to LOS 14.1 that you were using? Thanks.That's the best compromise, I do it so too. The stability, over all performance and the low battery drain of 14.1 is currently not yet available at 15.1 or 16.0. LOS 16.0 runs very smoothly in the beginning, but in the long run, RAM usage increases immeasurably and everything goes into the swap. This makes a fluidly working impossible. 14.1 works here in deep sleep mode for almost two days, until the battery is empty.
Hey guys the official Lineageos website has removed the Galaxy S3 i9300 Roms!
So where can I find all the official and unofficial roms for I9300?
Thanks
Sent from my SM-J730F using Tapatalk
I sold my S3 GT-I9300 a few days ago, and now I'm using the S5 (G900F) as my daily driver. The latest ROM I had used on the S3 was this unofficial RR-ROM - based on LineageOS 14.1:Heya, can you provide a link to LOS 14.1 that you were using? Thanks.
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
A rough timestamp of when the issue occurred is also useful.
to quickly & easily capture logcat (Main log), Kernel log (dmesg) & Last Kernel log (last_kmsg which is important in case of unwanted reboot) without using a computer + adb or use a Terminal emulator on the phone:
Done! And make the dev happy.
- Root the phone
- Developer Options > Store logger data persistently on device > select All. More info about it here on developer.android.com
- Install the free SysLog. (screenshot)
View attachment 4644180
- Reboot the phone & reproduce the problem(s).
- Open Syslog & select logcat, dmesg & last_kmsg. Add some significant keywords in the bottom including in Notes describing the bug & hit Take log.
- The individual logs + a .zip of all of them will be saved in /sdcard/Syslog. You must rename them .txt to be able to attach them to an XDA post like logcat.log > logcat_log.txt for example. Or you can choose Share which will .zip them & then you can attach to a post or upload somewhere & link to in your post if the .zip is too big for XDA's attachment service (20 MB max).
***
Bug Reports & Logs?
If the phone is not rooted you can grant this permission to enable Syslog using ADB (15 seconds ADB Installer) & a computer:
You can also install an app like MatLog to analyse the logcat, filter it, search in it, export files etc but Syslog is fast & easy. If not rooted grant permission for MatLog:
- adb shell pm grant com.tortel.syslog android.permission.READ_LOGS
***
- adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
sys.selinux_enforcing=false