I've just updated, everything is fine, can't see any issue with the QS.After today's update, the top part of the QS drawer is somewhat messed up (see attached screenshots). The clock and service indicators are partially of fully hidden on a random basis. Also they are not touchable even when fully shown. For instance tapping on the clock doesn't open Clock app, tapping on battery percentage doesn't open the Battery settings menu and so on.
I've just updated, everything is fine, can't see any issue with the QS.
You're the only one I'm afraid. Look for any inconsistencies in how you setup your phone. Or use apps like Naptime/Servicely to save some battery.Most of the battery is consumed by Lineage System. Overnight battery drain was 15%. I checked for wakelocks and found there are too many wakelocks for NETLINK. Is this normal?
Very strange indeed. Seems like something is wrong with the setup of your phone. You can try to delete the cache and app-data for Trebuchet and SystemUI. Because the UI seems to have something to do with SystemUI.That's strange. I have basically zero customization and this is a clean install since the first LOS20 build. Here is a video of my issue:
![]()
New video by Le Kobiashvili
photos.app.goo.gl
Most of the battery is consumed by Lineage System. Overnight battery drain was 15%. I checked for wakelocks and found there are too many wakelocks for NETLINK. Is this normal?
Thanks for checking! Will have to try my banking app now and hope for the bestI just noticed that RootBeer now shows all checkmarks as green (not rooted) after the latest update.
Did not find any problems.
That's strange. I have basically zero customization and this is a clean install since the first LOS20 build. Here is a video of my issue:
![]()
New video by Le Kobiashvili
photos.app.goo.gl
Everyone has this QS-problem described above. It's a super small problem. Don't whine like that man! The developers will fix it in the next update.Re indicators above QS tiles, I did some experimenting on my spare older F1. Did a clean install of the latest 20230325 build. The issue is present when animations are disabled (Settings > Accessibility > Color and motion > Remove animations). If animations are enables, the indicators are rendered normally, but I hate such a sluggish experience of the phone. I always disable animations.
Still, the main problem for me is that: 1st - this section takes more space since 20230325 build, and 2nd - the indicators are not clickable anymore (they were clickable up until 20230318). I used to go to battery stats via this icon.
On the attached photo, left is my test phone showing the 20230318, right is 20230325.
Interesting post. I had written a few posts ago about the redesigned top bar and your post shows clearly how better it is looking. Its a much better use of the space. I don't see a problem there.Re indicators above QS tiles, I did some experimenting on my spare older F1. Did a clean install of the latest 20230325 build. The issue is present when animations are disabled (Settings > Accessibility > Color and motion > Remove animations). If animations are enables, the indicators are rendered normally, but I hate such a sluggish experience of the phone. I always disable animations.
Still, the main problem for me is that: 1st - this section takes more space since 20230325 build, and 2nd - the indicators are not clickable anymore (they were clickable up until 20230318). I used to go to battery stats via this icon.
On the attached photo, left is my test phone showing the 20230318, right is 20230325.
If there was a link before, then it's definitely within the reach of a developer to bring it back if users miss it. It's not even clear at the moment if the devs just decided to delete the links, or if it is a bug caused by the redesign. I'd bet on the second option. I dont see any problem with your previous post, it's informative and a constructive critique.I didn't mean to look like a whine. In the previous posts I've been told that the problem is only on my phone, so I thought to do some investigating and provide feedback explaining the problem. I mean for a problem to be solved by a developer, it has to be noticed at first, right?
@pmcmm I guess the look is a personal preference. It's not a big deal. But yes, the icons were clickable, and the battery shortcut was useful for me.
Just a few posts above I wrote that RootBeer shows everything as green and just now my health insurance app starting detecting root where there is none. Most likely they are checking safetynet CTS.
Now I have to root to "unroot".
But definitely not a problem of this excellent ROM!
Funny, I got exactly the same problem. Not sure yet, what to do. All this magisk/zygisk/safetynet-fix/ih8sn discussions totally confuse me. Dozens of versions, many of them marked as deprecated, I'm fully lost.Just a few posts above I wrote that RootBeer shows everything as green and just now my health insurance app starting detecting root where there is none. Most likely they are checking safetynet CTS.
Now I have to root to "unroot".
But definitely not a problem of this excellent ROM!
Funny, I got exactly the same problem. Not sure yet, what to do. All this magisk/zygisk/safetynet-fix/ih8sn discussions totally confuse me. Dozens of versions, many of them marked as deprecated, I'm fully lost.
If you have a working solution without negative side effects I'd be interested in a how-to![]()
Unrelated to the first, when an app tells you your phone is "unsafe" that is typically the app detecting the phone is rooted.
To fix this, you use the Magisk Denylist and prevent the app from "seeing" root.
There is no telling what app programmers do specifically. Their specific check might get around the Magisk Denylist. They might store "this phone was rooted" in the app data, in which case deleting the application data might help. They might blacklist your deviceID online because it was rooted at one point, in which case you would have to fake a different device (using MagiskHide Props Config).Unfortunately that is not the case cause when I unroot using Magisk uninstaller, these apps still say my phone is unsafe while the apps that didn't work when rooted (like Itsme), work fine after unrooting.
Another thing I noticed after unrooting, my Google Play Store still says my device is certified, but apps like Netflix can no longer be updated, so they definitely check elsewhere too unless passing Safetynet is more then the device being certified.
No problem for meAfter today's update, the top part of the QS drawer is somewhat messed up (see attached screenshots). The clock and service indicators are partially of fully hidden on a random basis. Also they are not touchable even when fully shown. For instance tapping on the clock doesn't open Clock app, tapping on battery percentage doesn't open the Battery settings menu and so on.
You shouldn't need to update nikgapps as the playstore will automatically update itself. I normally use the recommended mindthegapps with Lineage but nikgapps core has worked for me to. Check the permissions for the playstore, does it have access to the Internet.Hey there,
I just updated my phone to lineage-20.0-20230506-nightly and also updated Google Play Services via NikGapps to NikGapps-basic-arm64-13-20230418.
Everything seems to work fine except for the play store. Every time I open the Play Store it says I'm offline, which is not the case because all of the other apps are happily consuming internet.
I already re-booted the phone and also forced stopped the Play Store but this didn't work.
Anyone else got an idea on how to get the Play Store online again?
It will be fixed in upcoming builds.Yes, that turned out to be my problem with bluetooth. Turning off the AAC HD setting fixes the audio issue. I dont know how big of an issue that is for audiophiles, in my headphones i dont notice any difference on and off. In any case, its a bug.
Nevermind, I have figured it out. Turns out that the "latest" update to the touchscreen driver introduced this issue. The touchscreen was being flashed with a wrong firmware, which in my case was leading to these touchscreen issues from time to time. I have just pushed the fix and it will be available in the next build.
Yes, March's ASB was not merged in time for that build. Next one will already include it.Installed 18032023 build just fine. Android security patch date is still 5th February. No issues so far.