Hello, thanks for the info! I'll try doing a permissive build later today and will check if it's still going to loop.There's a gpsd selinux denial since it's running enforcing, likely causing the looping.
Hello, thanks for the info! I'll try doing a permissive build later today and will check if it's still going to loop.There's a gpsd selinux denial since it's running enforcing, likely causing the looping.
You can just create the gpsd lock file that it needs to see if that gets past the loop.Hello, thanks for the info! I'll try doing a permissive build later today and will check if it's still going to loop.
I created that file, but I still can't seem to get past the Lineage logoYou can just create the gpsd lock file that it needs to see if that gets past the loop.
Just put a 0 as content into the file
Likely more SELinux permissions needed for gpsd, got another log ?I created that file, but I still can't seem to get past the Lineage logo
Here is a logcat after creating the lock file: https://gofile.io/d/X6V6e1Likely more SELinux permissions needed for gpsd, got another log ?
Disable SELinux or build permissive.
There's SElinux rules needed for gpsdHere is a logcat after creating the lock file: https://gofile.io/d/X6V6e1
(For some reason I can't upload the fire directly here)
Can you do a build for klimtlte too? Thank You!
It's already posted on the previous page
On Permissive the build boots and everything works fine. I guess I'll have to use Permissive for now, as I don't really know how SELinux rules work.
On Permissive the build boots and everything works fine. I guess I'll have to use Permissive for now, as I don't really know how SELinux rules work.
adb logcat -b all -d | audit2allow -p ./out/target/product/chagalllte/recovery/root/sepolicy
I managed to solve the issue thanks to audit2all. It took me like 5 or even more builds to get rid of all the denials, but everything is working as expected now. This tablet really feels smoother with microG than with GApps installed ans battery life if longer as well. Even SafetyNet passes with sig spoofing. Once again, thanks for identifying the issue and providing me a solution.There's the audit2allow utility which does most of the work required for SELinux rules.
You run it, change rules, build & flash , rinse repeat till no more violations.
eg. (change product path to suit)
Code:adb logcat -b all -d | audit2allow -p ./out/target/product/chagalllte/recovery/root/sepolicy
Can you link the latest build so i can give it a try?I managed to solve the issue thanks to audit2all. It took me like 5 or even more builds to get rid of all the denials, but everything is working as expected now. This tablet really feels smoother with microG than with GApps installed ans battery life if longer as well. Even SafetyNet passes with sig spoofing. Once again, thanks for identifying the issue and providing me a solution.
Cheers
Can you obtain a log of when it happens?Check this one, currently I've had an issue after using it for some time that it loops on Lineage time random times during boot and it's something related to the Lineage Touch HAL![]()
lineage-18.1-20230526-microG-signed-chagallwifi.zip
This file has been shared with you on pixeldrainpixeldrain.com
Here, take a look if you can. It took me 2 reboots to trigger the issue. I tried disabling the Touch HAL by the way, but the issue still persists.Can you obtain a log of when it happens?
Be interested to see what's failing
Looks like [email protected]::IKeyDisabler/default is not starting, hence boot loop.Here, take a look if you can. It took me 2 reboots to trigger the issue. I tried disabling the Touch HAL by the way, but the issue still persists.
This seemed to work, at least after 5 reboots it didn't loop a single time.Looks like [email protected]::IKeyDisabler/default is not starting, hence boot loop.
Try this change, even though its abandoned
Are you referring to LOS 16.0 now or LOS 18.1 with microG? (I'll have to make a new thread for the microG builds if the interest for it will be high enough)
I can try to do a build for klimtwifi today
Experimental test build for klimtwifi can be for now found here: https://pixeldrain.com/l/C34B8P5u
Are you referring to LOS 16.0 now or LOS 18.1 with microG? (I'll have to make a new thread for the microG builds if the interest for it will be high enough)
Hi! Android 9 has a partial dark mode. The built in system apps as well as the system UI is dark, but third party apps do not support this dark theme and are light by the default. Many third party apps can be manually set to dark theme.Hi Just a quick question.. my understanding is that android 9 does not support dark mode, that your screenshot almost seem to suggest that it does.
my reason for asking is that I am visually impaired, and really can't read anything on a white background. anyway just wanted clarification before I try out this rom.
Cheers
I'd recommend rooting it then and trying Franco Kernel ManagerRuns well so far, any way you can add a cpu governor inside los settings? All good if not, I wanna try tweaking some cpu settings. Thanks!