[ROM][6.0.1] LineageOS 13.0

hga89 · Sep 9, 2017

nailyk said:
Encryption was working fine with for me on f2fs.
IIRC we have a metadata partition so the -16kB length shouldn't be a problem.
Here you have an unsecure boot to get logs while encrypting/decrypting (probably 13.0 but could be 14.1).
Maguro take long time to encrypt (around 20 min) right after a wipe.
On z3 thread we have lot of troubles with magisk and co breaking some part of init scripts who can be the source of your troubles.

I just encrypted my hitherto-unencrypted second GN running L 13 from August 12th. It went fine and I could reboot without problems.

osm0sis · Sep 9, 2017

Must be Magisk. I'll try without it over the weekend.

magur0 · Sep 9, 2017

osm0sis said:
Must be Magisk. I'll try without it over the weekend.

I don't to magic with magisk (just use 'integrated' root)... so could be that this is cause!

MrFlashGame · Sep 10, 2017

Hello there,
after using the newest nightly for quite a lot of time I've found some bugs which I would like to report here (Sorry, the official LOS bugtracker is too confusing for me).

I use LOS with Magisk(Two modules: IOS10Emoji, Unified Hosts) and OpenGapps. All of the bugs I reportes here are reproducable on my device.

1. If I apply a theme with the Designer App the SystemUI crash almost everytime (Sometimes not but I dont understand why).

2. The screen doesn't turn off in idle. This also affects the Lockscreen (The screen becomes a little bit darker after a time but never turns completely off automatically).

3. This is not a bug but I wanted to report it here anyways: I think the point "Update CM Recovery" in the Developer Settings is obsolete.

Would be nice if a dev could look into this and fix this. I've attached a bug report. If you need any other info please let me know.

Greetings Nils

nailyk · Sep 10, 2017

MrFlashGame said:
Hello there,
after using the newest nightly for quite a lot of time I've found some bugs which I would like to report here (Sorry, the official LOS bugtracker is too confusing for me).

I use LOS with Magisk(Two modules: IOS10Emoji, Unified Hosts) and OpenGapps. All of the bugs I reportes here are reproducable on my device.

1. If I apply a theme with the Designer App the SystemUI crash almost everytime (Sometimes not but I dont understand why).

2. The screen doesn't turn off in idle. This also affects the Lockscreen (The screen becomes a little bit darker after a time but never turns completely off automatically).

3. This is not a bug but I wanted to report it here anyways: I think the point "Update CM Recovery" in the Developer Settings is obsolete.

Would be nice if a dev could look into this and fix this. I've attached a bug report. If you need any other info please let me know.

Greetings Nils

AFAICT 3. is not a bug because lineage is provided with recovery. I guess if you tick it then OTA update you will loose twrp.
about 2. it is interesting because I have the same issue on z3/z3dual. Not all the time but looks like it happens if usb cable was unplugged while powering on/rebooting the device.
Can you confirm?
1. IIRC themes are not supported anymore on lineage because it was a cyanogenmod (r) mod.

Feel free to correct me.

MrFlashGame · Sep 10, 2017

nailyk said:
AFAICT 3. is not a bug because lineage is provided with recovery. I guess if you tick it then OTA update you will loose twrp.
about 2. it is interesting because I have the same issue on z3/z3dual. Not all the time but looks like it happens if usb cable was unplugged while powering on/rebooting the device.
Can you confirm?
1. IIRC themes are not supported anymore on lineage because it was a cyanogenmod (r) mod.

Feel free to correct me.

Hello @nailyk, as first thank you very much for your investigation. I didn't know that LOS still has its own recovery because I've never seen it on the official download page. But you are probably right there. I think we should at least rename this to LOS because CM is not the name of this ROM anymore. About 2: I can confirm that, I have just tested it. The screen has turned off now properly. About the CMTE stuff: I think it should be supported or removed, but this isn't a dealbraking bug and there is probabky no easy way to work around it so we should mayve just leave it as it.

Greetings Nils

nailyk · Sep 10, 2017

MrFlashGame said:
Hello @nailyk, as first thank you very much for your investigation. I didn't know that LOS still has its own recovery because I've never seen it on the official download page. But you are probably right there. I think we should at least rename this to LOS because CM is not the name of this ROM anymore. About 2: I can confirm that, I have just tested it. The screen has turned off now properly. About the CMTE stuff: I think it should be supported or removed, but this isn't a dealbraking bug and there is probabky no easy way to work around it so we should mayve just leave it as it.

Greetings Nils

My bad, here is a 13.0 thread and was talking about 14.1.
In 14.1 looks like the translation have been changed:

Code:

jenkins@4638e1e340ef:~/packages/apps/Settings/res/values-en-rGB$ rgrep "update_recovery_title\|update_recovery_summary"
cm_strings.xml:  <string name="update_recovery_title">Update recovery</string>
cm_strings.xml:  <string name="update_recovery_summary">Update the built-in recovery with system updates</string>

osm0sis · Sep 17, 2017

osm0sis said:
Must be Magisk. I'll try without it over the weekend.

Yup. After a couple of false starts, it worked once unrooted. :good:

Edit: Also can verify OTAs still don't work in @Android-Andi's 3.1.1-1 recovery due to the uncrypted block map ORS command failing.

hga89 · Sep 17, 2017

Spontaneous reboots when file system is encrypted

I have two GNs running L 13 with the file system encrypted and both reboot several times a day, both when not in use and also when in use. Has anyone else noted this problem?

frusso3 · Sep 19, 2017

Hi guys, I'm still with 11 cm and I'm fine. I would like to install this lineage and I wanted to know: is it okay for every day? Any problems? Are the pictures good? Does USB otg work? I still twrp 2.8.7, do I have to update it? Thank you all

bamtan2 · Sep 19, 2017

frusso3 said:
Hi guys, I'm still with 11 cm and I'm fine. I would like to install this lineage and I wanted to know: is it okay for every day? Any problems? Are the pictures good? Does USB otg work? I still twrp 2.8.7, do I have to update it? Thank you all

To stay "fine" you should not update. Updates are good when you want to have fun, or if there is a feature you are missing. I am using 5.1 and I have not updated because it works fine for me. There will be many changes if you update. The chance of having problems is higher than 0%. But many happy users are here.

Always use newest TWRP, just in case. In THIS case, yes, it is required

frusso3 · Sep 19, 2017

bamtan2 said:
To stay "fine" you should not update. Updates are good when you want to have fun, or if there is a feature you are missing. I am using 5.1 and I have not updated because it works fine for me. There will be many changes if you update. The chance of having problems is higher than 0%. But many happy users are here.

Always use newest TWRP, just in case. In THIS case, yes, it is required

Thanks for the sincere response, then I stay with cm11. I was undecided between this and 6.0 aosp

hga89 · Oct 2, 2017

hga89 said:
I have two GNs running L 13 with the file system encrypted and both reboot several times a day, both when not in use and also when in use. Has anyone else noted this problem?

I have some more information on the crashes: although some of the crashes occur when the phone is /not/ being used, on other occasions it crashes when I am using firefox and the webpage might be complex or have problems loading. Might it be that the OS crashes when it encounters a particular low-memory situation?

Some of the crashes result in a "soft"(?) reboot and when the phone reboots it cannot connect to the phone service provider (and this can only be resolved with a hard reboot). Other crashes result in a "hard" reboot where I have to reenter the encryption password after which the phone finishes booting and does connect to the phone service provider. I speculate that when a "soft" reboot happens it does not initialize everything properly?

GerardJ · Oct 6, 2017

Spontaneous reboots

hga89 said:
I have two GNs running L 13 with the file system encrypted and both reboot several times a day, both when not in use and also when in use. Has anyone else noted this problem?

I do have this problem since updating with the last NIGHTLY (13.0.20171002-NIGHTLY-maguro). Reboots while the phone is inactive, about 3 or 4 times per 24 hours. It shows when I re-activate my phone out of sleeping condition, and have to enter the SIM card pin code.

MrFlashGame · Oct 6, 2017

GerardJ said:
I do have this problem since updating with the last NIGHTLY (13.0.20171002-NIGHTLY-maguro). Reboots while the phone is inactive, about 3 or 4 times per 24 hours. It shows when I re-activate my phone out of sleeping condition, and have to enter the SIM card pin code.

Yep I have similar problems too, not with the SIM Unlock (I use normal PIN, maybe you should test this too), but sonetimes the phone soft reboots. And in some really rare cases it keeps stuck in the "Upgrading Android" Screen.

nailyk · Oct 6, 2017

MrFlashGame said:
Yep I have similar problems too, not with the SIM Unlock (I use normal PIN, maybe you should test this too), but sonetimes the phone soft reboots. And in some really rare cases it keeps stuck in the "Upgrading Android" Screen.

On my latest 13.0 tries device stuck at 'upgrading android' if it is booted with charger.

Am not working on (maguro) 13.0 anymore but /proc/last_kmsg should be helpful to debug this.

hga89 · Oct 6, 2017

GerardJ said:
I do have this problem since updating with the last NIGHTLY (13.0.20171002-NIGHTLY-maguro). Reboots while the phone is inactive, about 3 or 4 times per 24 hours. It shows when I re-activate my phone out of sleeping condition, and have to enter the SIM card pin code.

You and I see this because the phone hangs: in your case asking for the SIM pin code, in my case asking for the encryption password. If the phones were not hanging for us, we would not be aware of these frequent crashes...

hgmichna · Oct 6, 2017

Random Reboots

nailyk said:
/proc/last_kmsg should be helpful to debug [spontaneous reboots].

In my experience, last_kmsg is singularly useless for debugging spontaneous reboots for more than one reason.

Google is just not interested in solving this widespread problem, otherwise they would add a log that is actually useful.

GerardJ · Oct 6, 2017

Spontaneous reboots

hga89 said:
You and I see this because the phone hangs: in your case asking for the SIM pin code, in my case asking for the encryption password. If the phones were not hanging for us, we would not be aware of these frequent crashes...

Agree. Once you are aware of these crashes, you can also see the effect in Settings - Battery, where the green graph shows the white interruptions.

guest4711 · Oct 6, 2017

GerardJ said:
Agree. Once you are aware of these crashes, you can also see the effect in Settings - Battery, where the green graph shows the white interruptions.

...or when displaying the uptime, either using terminal

Code:

maguro:/ $ uptime
 19:10:24 up  7:31,  0 users,  load average: 0.95, 1.01, 1.19
maguro:/ $

or via settings -- about phone -- status -- uptime.

[ROM][6.0.1] LineageOS 13.0

Senior Member

Senior Recognized Developer / Contributor

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Recognized Developer / Contributor

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Similar threads

Top Liked Posts