A (short) phone call worked fine, no peculiarities.
(As it’s mentioned as untested…)
Edit: I seem to not being able to switch NFC on
Edit 2: system seems to get warmer when active. Might be caused by the test build, but looking at cpu frequencies it seems to not drop to the lowest frequency
Edit 3: another observation. Automatic brightness is more reactive than on LOS17, it seems (which I’d good, IMO), but it also tends to drop to the lowest level which makes the display unreadable, as it’s not that dark.
@TeamB58 : is it ok to list everything here, or is there an issue tracker somewhere?
Fine. Will do. As stated in the LOS17 thread I’m busy using my phone (so jumping the band wagon might have been a risk…) and so should stumble over things not yet ready…
Unexpectedly, the system declared the SD card as corrupt and wanted to format it. After a reboot everything was fine again.
The probably relevant lines in logcat:
05-25 11:03:49.917 512 512 D vold : exfatprogs version : 1.0.4
05-25 11:03:49.917 512 512 D vold : /dev/block/vold/public:179,65: clean. directories 6979, files 32638
05-25 11:03:49.926 512 512 I vold : Check OK
05-25 11:03:49.944 512 512 E vold : Mount failed; attempting read-only: Out of memory
05-25 11:03:49.966 512 512 E vold : public:179,65 failed to mount /dev/block/vold/public:179,65: Out of memory
I didn’t succeed with mindthegapps also, but the test package from opengapps for android 11 works fine.
The display thing is hidden in this thread. Go to developer options, display section, and set minimum width to 360dpi. It’s somewhere at 700 after a new install
For me that’s ok. Maybe there’s one or other thing i might find and you can fix it. Win-win (sorry… )
Edit: so, for example, i see a notably higher battery consumption, which might well be caused because it’s still in debug, serial console is active, but maybe also (i can’t say what’s causing it) the obviously not using the lower cpu frequencies when idle.
This morning the phone didn’t react on fingerprint or on button. Even though it was obviously running (also, tasker log did not indicate any crash). I couldn’t get any logcat, as abd seems to have died. I had to press power for a long time
@TeamB58 is there a way to get the console output, as this seems to be configured? Or is some previous dump active? I did not see /proc/last_kmsg.
For the record. I got Magisk working again. Restarting in safe mode (but interrupt the reboot, go into fastboot, flash magisk installed boot image and reboot) disabled all Modules.
Looks like the Universal SafetyNet Fixer was the culprit. I still have F-Droid Extension and Properties Editor active, and everything works again (except for SafetyNet, but as this is a debbug build I’m not that surprised
Edit: as I’m posting too much in this thread: Anyone knows whether it’s normal on Android 11 i can’t access app data below Android/ on the internal storage with a file browser?
An official build will take time. I estimate at least another month due to time constraints on my side, needed testing, and review by LineageOS. I would offer another alpha build as soon as we have more fixes, kernel changes, or anything else affecting user experience.