Thanks for checking this out. That’s weird, since I experienced it on all Roms I tested and I can’t imagine how this could be a hardware issue, since after changing this setting, everything is fine. But maybe it is??
OK. As I see it, we have the commit and the updated extract scripts for the device tree you just linked to, but don’t have suitable *.bp and *.mk files in the vendor 18.1 branch yet which would be the output of the extract scripts. I will get started on fixing that now.
I have worked through all remaining 17.1 issues that I had some hope of fixing. I will test and integrate the FP3 0101 release blobs over the weekend and then rebase the 18.1 work on top of 17.1 as you suggest. Starting next week we do 18.1 and freeze 17.1.
After I realized this is a long weekend I installed it… I tried mindthegapps, as i need gapps, and opengapps is only a test version, but it did not install, it complained about a low resources device and not enough space. So i went with opengapps test, which seem to work fairly well. Have to root the device again, this somehow did not want to work, but that’s not that urgent. I can’t overcome the minuscule display, though. It does not get the right size after rebooting. Maybe i misunderstood this. Switched to larger text and changed minimum width in developer options. For the rest, it seems everything is working fine
Edit: seems GPS does not listen to baidou and Galileo. Only us and glonass
I cannot edit the OP so moderators, it will be helpful if you can update the new link(available in post #33) and also a short hint to set “smallest width to 360 in developer options” to workaround this display issue.
Thanks for the info, and especially for this build!
Can you think of any reason i can’t flash Magisk? Patching the boot.img as file as well as renaming the apk to zip and installing it in twrp leads to an unbootable system. On LOS17 it was working
Edit: might very well be Magisk related. I joined an issue over there