Waiting for a new build
Hi Mr @ChronoMonochrome
Do you still work on this rom?
When will the new build #3 be ready?
Hi Mr @ChronoMonochrome
Do you still work on this rom?
When will the new build #3 be ready?
Hi Mr @ChronoMonochrome
Do you still work on this rom?
When will the new build #3 be ready?
He has already made it very clear that it is a long and hard job, with no deadlines, just wait and if you can help then help.
He has already made it very clear that it is a long and hard job, with no deadlines, just wait and if you can help then help.
I'm not getting enough time to support this project, so if anyone waiting for soon updates, unfortunately it's not going to happen soon.It is a legit question. The same with debian. Debian is expected to be released somewhere in Q3 or Q4 of 2019. Probably.
It seems like there are some more devs working on Pie builds now, so you can try one of those builds and help devs reporting bugs.I am wondering the same because: if the OS does not work on my phone until Q4 of 2019, i probably go and buy a new phone.
Not to stress the dev, but to know where i am.
If he says this will take 3-5 years, thats ok, but then i will go with another phone and let the s3 off in the drawer until its released.
I'm not getting enough time to support this project, so if anyone waiting for soon updates, unfortunately it's not going to happen soon.
I can't work continuously supporting just one project so I switched for now to others. I have some other devices to work on, plus some non-Android dev projects.
Fixing the rest bugs of this ROM mentioned here in the latest posts (battery drain, overheating, etc and so on) doesn't seem to be straightforward for now, so I will return as soon as I'll come up with any working solution.
It seems like there are some more devs working on Pie builds now, so you can try one of those builds and help devs reporting bugs.
I won't do any promises, but when Q released (should be released in August), I'll definetely try it out. But no any promises, as it still seems to be unclear whether it's ever will be possible to run it on this phone.
Isn't a good idea try to port Project Treble to S3 base? So this way, any new android upgrades will be straightforward. I think is a best (And longer) approach than fix a specific rom. What you think about?
try on my friend because S3 still has usersThat should be a long-term fix that can persist even Android upgrades, if all the Treble stuff is implemented in a recommended way.
At the current stage, it probably should be possible to boot up a GSI (Generic System Image), since we aren't using any hacks in android sources (the latest hack used here can be eliminated by setting lowram property), but I'm too lazy to work on it.
Will try whenever I'm again in a mood to work on it.
flashing it with newest TWRP 3.3.0
Hi Mr. @ChronoMonochrome
Thanks Your efforts
Should we be ready for the new Build and be happy?
(We have been waiting for this great thing for a long time)
Hi, i have made an optimized version of this rom and today i'm releasing a new build!
https://xdaforums.com/galaxy-s3/development/rom-optimized-lineageos-16-0-team-t3940142
plz test and let me know
he is helping me with this rom maybe when he get time, he will release an update to this romTnx for your support
Mr. @ChronoMonochrome no longer develops this ROM?
he is helping me with this rom maybe when he get time, he will release an update to this rom
Do a clean flashI installed rom:
There is still a black problem with the page after the call
There is a restart random issue
strange, i didn't had that issue
/*
* 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
Mr @ChronoMonochrome
Given that the lineageos team has begun merging LOS 16 to LOS 17 ...
Will you be back to this device(S3 i9300) with Android 10?