[ROM][OFFICIAL] LineageOS 20 weeklies for Xiaomi Poco F1

Search This thread

HatMan22

Senior Member
Oct 8, 2017
149
45
Dharan
Xiaomi Poco F1
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?
 

pmcmm

Senior Member
May 15, 2016
189
89
Xiaomi Poco F1
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.

In the past weeks, I've noticed some heavy redesigning, which is making LOS looking much more modern. Here are a few examples:
- the pin pad is round and goes squared when clicked
- the newly redesigned timer, which allows for setting multiple timers at once
- the awesome new "wallpaper and fonts", which allows to use customized icons
- the top bar when scrolling down twice

I see this week that the ThemePicker is being further developed, yeah!

For all the years that Ive been using LOS, rarely there had been costemic upgrades, and now I see a them coming on a regular basis. Thanks devs, love the work!
 
  • Like
Reactions: first_damned

Abdel1993

Senior Member
Sep 20, 2019
61
66
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?
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.

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:
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.
 

GeForce66

Senior Member
May 28, 2011
173
91
St. Pölten
Xiaomi Poco F1
I just noticed that RootBeer now shows all checkmarks as green (not rooted) after the latest update.
Did not find any problems.
Thanks for checking! Will have to try my banking app now and hope for the best ;)

EDIT: Holy cow, banking app works! Still not going to set it up as my 2FA, as any update could break it again ;)
EDIT2: Also PayPal works again, what a dream :)
 

marsa47

Senior Member
Aug 1, 2010
63
42
Xiaomi Poco F1
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:

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.
 

Attachments

  • P1750616.JPG
    P1750616.JPG
    919.5 KB · Views: 71
  • Like
Reactions: pmcmm

Abdel1993

Senior Member
Sep 20, 2019
61
66
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.
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.
 

pmcmm

Senior Member
May 15, 2016
189
89
Xiaomi Poco F1
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.

As for the non clickable buttons, you mean the minuscule ones in the tray? Were those ever clickable? I had no idea.
 

marsa47

Senior Member
Aug 1, 2010
63
42
Xiaomi Poco F1
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.
 
  • Like
Reactions: Hemphiz

pmcmm

Senior Member
May 15, 2016
189
89
Xiaomi Poco F1
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.
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.

As for the new design, it is a completely subjective evaluation, and you might have less luck reverting that one :)
 

fightforlife

Senior Member
Oct 25, 2012
62
42
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!
 

Largamelion

Senior Member
Sep 10, 2010
546
238
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!

That is basically my only issue with this ROM. Some apps check for Safetynet (Netflix, Mynexushealth) and other apps check for root (Itsme, etc...) forcing me to keep unrooting/rooting when I need to use them or update them. There's also a 3rd category like Payconiq which just says my device is unsafe, these apps seem to just check the ROM and if it's LOS they won't run.

Fortunately my bank app doesn't check anything and just runs whether I'm rooted or not. I don't even need to hide it when I'm rooted.
 

sponk0

Senior Member
Apr 7, 2019
115
205
Moto G 2015
Xiaomi Poco F1
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:)
 

AtomicStryker

Senior Member
Nov 19, 2015
231
128
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:)

As far i understand, there is basically only 2 things: Safetynet and Rootdetection.

If you "fail" Safetynet, Play Store wont let you install certain apps.
To fix this, you can use Universal SafetyNet Fix.
MagiskHide Props Config is flagged as dead but still works also. I have both installed.

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.
 
  • Like
Reactions: sponk0

Largamelion

Senior Member
Sep 10, 2010
546
238
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.

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.
 

AtomicStryker

Senior Member
Nov 19, 2015
231
128
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.
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).

Its basically an arms race between people who want or need root on their phone and the app developing people who do not want you to have it, ostensibly for safety reasons.

To be fair, having root on a phone gives you a level of access to their apps that is not intended.
 

jmf25

Member
Jul 17, 2021
5
0
Hi everybody
I'm trying to update to LOS20 from Los19 and I've found something that I've never found. That's what I've done:

1.- I run .\adb devices and the powershell shows me the name of my device
2.- I follow the next step of the guide and I run .\adb reboot bootloader. So my phone boot on bootloader and I see the bootloader sceen
3.- On the next step I run .\fastboot devices to be sure that my phone is always there and the powershell and I get:
???????????? fastboot

Normally I had to find the name of my device, so I think that´s something is wrong
Can anybody help me?
Should I continue the update?
I'm afraid of this abnormal behavior
Thanks for your answers
 

jojy thomas

Senior Member
Sep 13, 2016
107
26
23
Kottayam
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.
No problem for me
Atleast i didn't notice any
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Short feedback, lineage-20.0-20230506 working fine for me.
    2
    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?
    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.

    Hold down on the playstore app icon, App info, check in mobile data and WiFi
    2
    Fyi: Today's build 2023-05-13 running fine with no issues
    1
    What happens is that nothing is obviously wrong, but if you open the Magisk app it will tell you that Magisk is installed incompletely, it then "finishes" the installation and wants a reboot.

    Since it apparently can do that directly (root is available and everything), whatever problem that solves does not seem to impair functionality.
    1
    In the past I had issues with mindthegapps as it left me with non-functioning Google Play services.

    Strange thing, is that I could not activate internet access right away as it was disabled. I restarted my phone a few times and suddenly I could activate it.

    Not sure, what happened there, but now I got the Play Store back to work.
  • 28
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    GPL compliance:
    yG18r6g.png

    Working:
    • Camera (and flashlight)
    • WiFi
    • Bluetooth
    • Telephony (Calls and Data)
    • IMS (RCS, VoLTE and WiFi Calling)
    • Audio (Record and Playback)
    • Video Playback
    • Sensors
    • GPS
    • Encryption (FBE)
    • WiFi Display

    Broken:
    • Nothing (?)

    Compatibility:
    Compatible with all Xiaomi Poco F1 variants.​
    Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.​

    Device wiki:
    Downloads:
    Installation:
    • Follow instructions found in the respective wiki page
    14
    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.
    It will be fixed in upcoming builds.
    9
    I've not noticed it on my device
    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.
    7
    Installation Guides📚
    Official way of installation can be found at OP.

    Installation Guides: 👨‍🏫
    Clean Install via TWRP:

    • Backup your data to PC or SDCard if you have.
    • Downland:
      - TWRP by REIGNZ v2 [twrp-beryllium-v3.7.0-A12-V2.img] - [Current Bugs/Issues & Workarounds]
      - Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
      - Optional A13 GApps of your choice.
    • Boot, flash and reboot to TWRP. [Check Install Custom Recovery Guide]
    • Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
    • Reboot to recovery once again (needed due to a current issue with TWRP by REGINZ) and then Format data > type yes.
    • Transfer the files you previously downloaded into Internal Storage, while you are connected and into TWRP from PC to your Device. If you have SDcard or USB OTG you can also use that.
      [TWRP by REIGNZ have an issue, if PC doesn't recognize the device, press in twrp menu, Advanced > File Manager > and find and select sdcard folder aka Internal Storage > go back and now your pc should be able to recognize the device]
    • Flash ROM > GApps. NOTE: ROM IS FORCE ENCRYPTED
    • [Optional] Flash LineageOS recovery by pressing "Install Image > Navigate and Select the LineageOS Recovery > Flash it to recovery partition.
    • Reboot and Enjoy!
    • [Optional] In case you want to change Kernel to NGK or SC [SE version - aka System_Ext], flash it after the first boot of the ROM.
    • [Optional] In you case you want Root, flash Magisk after the first boot of the ROM.
    SafetyNet & Certified Play Store:⚠️
    • Official LineageOS doesn't pass SafetyNet or have certified Play Store by default. [Read here why]
    • Root your device with Magisk and Follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]

    OTA Upgrade/Update:
    ⚠️Warning⚠️

    • Only use OTA if you are encrypted. Simply go to updater and press install, everything will be automatic.

    Dirty Installation via TWRP:
    {Manually Upgrade/Update the ROM}

    • Download:
      - TWRP by REIGNZ [twrp-beryllium-v3.7.0-A12.img] - [Current Bugs/Issues & Workarounds]
      - Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
      - Optional A13 GApps of your choice.
    • Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
    • Flash ROM > GApps > [Optional]Magisk.
    • Reboot and Enjoy!
    Notes:🗒️
    6
    Installed 18032023 build just fine. Android security patch date is still 5th February. No issues so far.
    Yes, March's ASB was not merged in time for that build. Next one will already include it.