TheShanMan said:

You've more than made your point already. Rather than complaining about each build, how about downgrading to 18.1 or 19.1 to avoid these issues? I suspect that's what everyone else who can't live with these bugs is doing, myself included.

Or perhaps they've missed the point...the point of this place... which is development. If the product were perfect there would be no need for a development thread such as this.

As you suggest, staying on a previous Android version is probably the best thing to do for people who don't want to participate in development, or who want wait until newer Android version is mature before switching.

Boyd LaRue III said:

Will this work on Moto G7 Plus? Or its counter part T-Mobile Revvlry Plus????

Nope, but there is a whole thread for that device specificially, just google it.

Jim_Doe said:

Since none of the reported bugs (about five releases before) were addressed:
lineage-20.0-20230507-nightly-river-signed
is also a flop!

Install it and you'll get:
- 2 buggy AF camera apps
- impractical lock-screen that wears your physical power button down
- but finally: a working FM radio

Is it worth to have android No. 13 and phone unable to take photos without problems but with a radio?

Click to expand...

At this point you're talking to the ether - just stop - we are working on the camera issues - Aperture works in most cases - the lockscreren thing is _not_ a normal use case, hence why you're the only one reporting it

PMDPhD said:

Anyone not able to update? On the device the updater won't grab the file, and if I go to the Lineage website I get a "Request failed with status code 502" error. Lineage status page doesn't seem to show any issues.

Also, nice work on the FM radio, but I have a question. Is there any way to keep the radio on while the screen is off? It does not seem to behave like other audio apps like Spotify, the FM will turn off if the screen is off. I think on stock rom this did not happen, is there a setting or something I need to enable?

Download portal is down, working on it, and I'll look into it.

npjohnson said:

hence why you're the only one reporting it

I think i have also say this that i have problem with the lock screen. I have the same error on the G7.

I have tested every (currently updated) camera app from F-Droid and the latest GCam port from Parrot043 (this one). However, I haven't tested Aperture, yet, and am waiting for the new Lineage for MicroG build to come.

Here's my report:
-Affected by the Bug-
Simple Camera
Moto Camera 2
GCam
PhotonCamera (from IzzyOnDroid repo)
OpenCamera

-Unaffected by the Bug-
Libre Camera

The bug inconsistently affects usability of camera apps, as has been reported. There isn't a reliable work-around, aside from just closing the app and trying again later or just playing with settings and such to "jostle" it into working. I, personally, have found my camera still usable and I haven't been too strongly affected by this bug, but I still believe the root cause needs to be addressed and resolved.
Libre Camera is a camera app developed using Flutter. I have not encountered any stuttering or similar issue to the other apps or reports. Entertainingly, it has the highest viewport refresh rate I've seen and makes it feel like my device is running at 90 or 120hz (this was weirder after actually using a 90hz device). I don't know if it is because it is using Flutter, but there may be some clue there as to what's happening on the system level.

Thank you for maintaining LineageOS for this device, let alone officially. This has been very helpful for me and I hope my feedback can support further development.

I'm currently running the official lineage-20.0-20230514-nightly-river build on a Moto G7 River that has been rooted with Magisk 26.1. I've noticed that every once in awhile, I will lose access to root / su. Rebooting the phone restores access to root / su.

There is a closed issue / post on Magisk's github that suggests that this behavior is linked to certain kernel patches in certain custom roms, including LineageOS.

See - https://github.com/topjohnwu/Magisk/issues/6914

There seem to be some acknowledgment of this issue, in LineageOS msm8998 specific builds - https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8998/+/355841

Any chance this is something that would also be applicable to the sdm632, or River specific LineageOS builds?

kind of android newbie said:

I'm currently running the official lineage-20.0-20230514-nightly-river build on a Moto G7 River that has been rooted with Magisk 26.1. I've noticed that every once in awhile, I will lose access to root / su. Rebooting the phone restores access to root / su.

There is a closed issue / post on Magisk's github that suggests that this behavior is linked to certain kernel patches in certain custom roms, including LineageOS.

See - https://github.com/topjohnwu/Magisk/issues/6914

There seem to be some acknowledgment of this issue, in LineageOS msm8998 specific builds - https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8998/+/355841

Any chance this is something that would also be applicable to the sdm632, or River specific LineageOS builds?

Click to expand...

next build will have it

npjohnson said:

next build will have it

Okay. Thank you for the update.

Thank you for working on Safety net attestation.

npjohnson said:

next build will have it

Just to follow up on this. I have been running the May 21 build for River for about 24 hours, and have not lost Magisk root. I'm going to tentatively conclude that the reversion (i.e. "Revert "kernel: Only expose su when daemon is running") addressed the issue. Thanks.

kind of android newbie said:

Just to follow up on this. I have been running the May 21 build for River for about 24 hours, and have not lost Magisk root. I'm going to tentatively conclude that the reversion (i.e. "Revert "kernel: Only expose su when daemon is running") addressed the issue. Thanks.

Yup. Thx for alerting me.