Just looking into this thread again after some time.
The problem with the non-working timeout for automatic locking seems to be a general problem on LOS 17.1. See, for example, here:
If you still want to use a timeout for screen locking, you may want to try the following workaround: Turn OFF the setting “On/Off locks device immediately” (translated from German). Then the timeout set above is honored. To lock the screen manually, you could use the On/Off Menu (press and hold On/Off button). Enable the corresponding option in the Settings under System > Keys > On/Off Menu > Lock (also translated, so no guarantee for correct labels).
just to add my comment:
I upgraded our three FP2 to LineageOS 17.1 in July and keep them up to date quite regularly. All of them experience the “no mobile data”-feature.
I did not spend too much time in investigating, but it’s hard to find a pattern when mobile data works and when it doesn’t. 90% when leaving wifi it does not. Reboot helps.
But nevertheless: Thanks to Chris (and everyon else) to maintain Lineage for FP2. I hope for some more time!
Interesting! Thanks for saying. I will do some comparisons when it’s released.
(I was considering registering for downloading the alpha or beta build (I don’t quite get how they deal with their builds), but if it seems it’s ready…)
I also face the two issues. Mobile data does not work sometimes, sometimes it does.
I normally de-active Mobile Data when I’m at home and active WLAN. When I leave my flat I do it the other way around.
I also still have random reboots, but I already had them on LOS16 - never really investigated this, as it happens about 1-3 times per week and I somehow live with that even it is a bit annoying.
Most annoying thing with rebooting for me is, that I use Spotify (I get it via from Aurora store and it works fine without GSF) and after every reboot the external SD card on my FP2 needs some time until it is useable after the reboot. Spotify looses all the downloaded music on the sd-card and the only way to fix this is to restore the data (I use OAndBackupX to do so). Now with the additional necessary reboots I have to go through this procedure even more often :-/.
I still have Reboots, but not so directly related to the charging.
At the moment, mine has been running for 7 days, it may be that it runs for a few weeks, but it can also be that it is rebooting in the next moment, both has already been experienced.
With the first command “ adb root” I have the following error ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
rebooting in TWRP first solve the issue
System patched, seems to works: After enabling/disabling Airplaine mode → Data is there .
I’ll use it in the next days and report if something strange happens
Yes, sorry: you need adb root enabled through the Developer options, yes. You should not need TWRP to do that. Just follow instructions from the error message.
.