[ROM][OFFICIAL] LineageOS 17.1 [nightlies]

[papperlapapp]

I hope it is okay to ask 2nd question.....

After upgrade to LOS 17.1 2020-12-15 I get

random reboot to recovery "Can´t load Android system" "retry or factory reset".

I think this started with 20201215 version, did not see it with 20201208.
Device reboots randomly, even after fresh LOS install. Followed the install howto for LOS.

It also happens when plugging USB cable from PC.

Device Moto G7 plus 1965-3

 

[papperlapapp]

I have problems with recognition of my simcard + data (not working and gets switched off)(...)

There is a workaround
There is a workaround and it even is described in this thread....
Make a fresh install of LOS 17.1 20201124 and from there you can make an OTA update to 20201201, but do not use the later builds.

 

[oatwalker]

There is a workaround
There is a workaround and it even is described in this thread....
Make a fresh install of LOS 17.1 20201124 and from there you can make an OTA update to 20201201, but do not use the later builds.

I've spent a couple hours trying to find that build. How does one find older builds of LIneageOS?

 

[papperlapapp]

I've spent a couple hours trying to find that build. How does one find older builds of LIneageOS?

lineage-17.1-20201124-nightly-lake-signed.zip
md5sum e374de85d105535db3dd314fc2035335
Link: lineage-17.1-20201124-nightly-lake-signed.zip

lineage-17.1-20201124-recovery-lake.img
md5sum 897fc692f04f2a197be8cbe18b7bb8a4
Link: lineage-17.1-20201124-recovery-lake.img

Unfortunately this filehoster asks for an email adress to send the actual download link, but didnt find a better file hoster so quick.... best get a throw away email adress

 

[oatwalker]

lineage-17.1-20201124-nightly-lake-signed.zip
md5sum e374de85d105535db3dd314fc2035335
Link: lineage-17.1-20201124-nightly-lake-signed.zip

lineage-17.1-20201124-recovery-lake.img
md5sum 897fc692f04f2a197be8cbe18b7bb8a4
Link: lineage-17.1-20201124-recovery-lake.img

Unfortunately this filehoster asks for an email adress to send the actual download link, but didnt find a better file hoster so quick.... best get a throw away email adress

Thank you so much! I've been banging my head against my desk the better part of a day now trying to get a working phone. Using that version seems to be working.

 

[papperlapapp]

(.....)I found that clean installation of the 20201201 ROM causes the issues above, however a clean installation of 20201124 and then upgrading to 20201201 does NOT result in the same issues and seems to work fine on an initial check.

I made the same observation.
Now there was just 20201222 released, have you already tried this version? If yes, how did you intsall (OTA?) and what was your current installed version? Thnx!

 

[papperlapapp]

Thank you so much! I've been banging my head against my desk the better part of a day now trying to get a working phone. Using that version seems to be working.

You´re welcome.
From 20201124 you can try an OTA update to 20201201, that worked for me. But, I did not touch the versions after 20201201, I wait what the others say.

 

[oatwalker]

You´re welcome.
From 20201124 you can try an OTA update to 20201201, that worked for me. But, I did not touch the versions after 20201201, I wait what the others say.

I updated to the latest version before reading this. It seems to be working.

 

[chicovstheworld]

FYI, I'm seeing the exact same issues as well with a brand new XT1965-T and image 20201212 and 20201222. Same errors in the log about a service that keeps restarting because of a null sensor and spontaneous reboots after unplugging an active USB cable.

I can add that force stopping the Moto Gestures service (via System --> Advanced --> Moto Gestures) stops the messages in the logs about the restarting service and the phone no longer reboots when the USB cable is unplugged. As such, I can only assume it's the offending/problem service.

 

[papperlapapp]

(.....)a can add that force stopping the Moto Gestures service (via System --> Advanced --> Moto Gestures) stops the messages in the logs about the restarting service and the phone no longer reboots when the USB cable is unplugged.

That's a great hint to know!
How did you install? Clean install with ADB/recovery or did you make an OTA update to 20201222 from previous version?
Does cell network work with 20201222?

 

[chicovstheworld]

That's a great hint to know!
How did you install? Clean install with ADB/recovery or did you make an OTA update to 20201222 from previous version?
Does cell network work with 20201222?

Both installs, 20201222 and 20201212, were clean installs from ADB/recovery.

I just did another clean install of 20201222 from ADB/recovery to test the cell network. No cell network. I get an error message saying 'Turn off airplane mode to make call.' The device is not in airplane mode.

Let me know if you need any more testing. This new phone is a replacement for another phone with a cracked screen. The older phone is still perfectly functional, so I'm in no great rush to get the new phone working.

 

[Jleeblanch]

A bunch of you have made similar reports, and it'd be a pain in the ass to tag all of you, so here goes.

We are aware there is an issue, but not all seem to be effected. I'm trying like hell to reproduce this so I can understand what is happening that is causing some sensor to be null thus causing MotoActions (LineageActions) to ultimately crash eventually causing the device to reboot in some cases.

If one or more of you could answer a few questions, it would help us get to the bottom of this. We pushed a bandaid fix so that MotoActions doesn't crash Settings when a sensor comes back as null, but this doesn't resolve WHY the sensor is coming back as null.

Looking thru various logs, if I had to guess I'd say it's related to selinux issues on /mnt/vendor/persist (/persist). Some logs show "persist_file" which is stock labeling for /persist while lineage use "mnt_vendor_file". This tells me that secontexts for persist partition aren't being processed correctly which then causes the sensor null error which then causing MotoActions to go to ****.

On to the questions, if one or more of you could try to get more logs, especially during the initial boot process (tho on official builds, adb isn't available until you enable usb debugging in development settings, so you may need to leave usb plugged in, enable usb debugging, then reboot to bootloader and reboot to system). I also need kernel log (dmesg) which may require adb root to be enabled. You might be able to pull the files from /sys/fs/pstore for this as well. If needed, I can push an unofficial build with full debugging enabled.

If you have any questions, lemme know! Thanks for everyone's patience

 

[Pixelguin]

It appears that the builds for this device have disappeared overnight.

And on the day I just got the phone, too...I don't know if I missed an opportunity or dodged a bullet!

 

[chicovstheworld]

As requested, here's a boot log and dmesg output. This is for image 20201222 on a Moto G Plus (XT1965-T). Let me know if you need anything else!

For some reason I can't attach the files here, so I posted them to this link:

Files shared via Tresorit

Tresorit uses end-to-end encryption to keep file exchange secure and private. Access the received content via this link.

web.tresorit.com

 

[Jleeblanch]

As requested, here's a boot log and dmesg output. This is for image 20201222 on a Moto G Plus (XT1965-T). Let me know if you need anything else!

That was exactly what I was hoping for, so thanks. It's exactly as suspected, so need to work on how to solve it properly. I may have you try a build or two at some point.

 

[jf.navica]

It appears that the builds for this device have disappeared overnight.

And on the day I just got the phone, too...I don't know if I missed an opportunity or dodged a bullet!

Anybody know what happened on the lineageos page? lake still appears in the build-target list

 

[Jleeblanch]

Anybody know what happened on the lineageos page? lake still appears in the build-target list

We had all December builds pulled (for all Moto sdm660 devices) as those are the builds some users experienced issues on coming from stock. There will be a new build during next cycle, which is why it's still listed as a build target.

I'll post a test build shortly with more info that also includes a potential fix (not just a bandaid).

 

[Jleeblanch]

Here is a test build as promised. Download link below.

NOTES: This build has debugging enabled, so adb should work right from initial clean boot without first needing to enable it in Settings. That being said, when testing this build, please start the log asap after rebooting from fastboot or recovery..

adb wait-for-device logcat > lake-logcat.log

The logcat command will run until you stop it, so if you didn't flash gapps, then finish LineageSetup and once on home screen, stop logcat <ctrl + c>.

Once device has booted, to get kernel log, run...

adb shell dmesg > lake-dmesg.log

The changes in this build include this commit (bandaid fix) and this commit (potential solution). Bandaid stops MotoActions from crashing when a sensor comes back as null, and the solution reverts forced restorecon changes we introduced a while back, but updated in the beginning of December.

Download -> https://downloads.kaotic.dev/LineageOS/lake/lineage-17.1-20210101-UNOFFICIAL-lake.zip

 

[chicovstheworld]

I'm trying to sideload the unofficial build above, but getting errors during the install:

Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
E:Error in /sideload/package.zip (status 1)

Install completed with status 1.
Installation aborted.

Am I doing something wrong? Advice?

 

[Jleeblanch]

I'm trying to sideload the unofficial build above, but getting errors during the install:

Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
E:Error in /sideload/package.zip (status 1)

Install completed with status 1.
Installation aborted.

Am I doing something wrong? Advice?

Hm, signature mismatch. Trying using this recovery.img (boot.img from the build)

https://downloads.kaotic.dev/LineageOS/lake/lineage-17.1-20210101-UNOFFICIAL-lake-recovery.img

Also, in digging a little deeper, I see /mnt/vendor/persist isn't specifically labeled although /persist is and /persist is a symlink to /mnt/vendor/persist. So, working on changes for that too.