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

Search This thread

mohan_168

Senior Member
Apr 14, 2013
381
254
Bangalore
That's your stable. There used to be monthlies or sth similar. Those builds where somwhat stable, but didn't have the latest features. But I feel that was quite a long time ago.
Do we have build to build upgrades available? I plan to put this on my parents phone, and not nag them about an update every few days.
Planning to switch them back from Pixel Exp 12.1 which is now EoL
 

deathontheshore

Senior Member
Sep 10, 2012
178
69
Braunschweig
Xiaomi Poco F1
Do we have build to build upgrades available? I plan to put this on my parents phone, and not nag them about an update every few days.
Planning to switch them back from Pixel Exp 12.1 which is now EoL
What dou you mean by build to build upgrades?
There's only weekly nightlies, so it's not daily. As long as there's no bugs an no security update you don't have to flash every build. Also it's OTA snd no user input is needed other than clicking download and install.
 

mohan_168

Senior Member
Apr 14, 2013
381
254
Bangalore
What dou you mean by build to build upgrades?
There's only weekly nightlies, so it's not daily. As long as there's no bugs an no security update you don't have to flash every build. Also it's OTA snd no user input is needed other than clicking download and install.
I believe you answered my question on build to build, which I believe is once every few days. I am glad OTA works.

As I said, I come from PE where the updates are available only once a month (and they used to support OTA)
 

pgzh

Member
Feb 26, 2013
33
17
I believe you answered my question on build to build, which I believe is once every few days. I am glad OTA works.

As I said, I come from PE where the updates are available only once a month (and they used to support OTA)
You can also configure the updater to check for updates daily/weekly/monthly to reduce "nagging".
 

joeslovakia

Member
Nov 5, 2017
45
4
I have question. I flash lineageos 20 from pixel experience recovery. now phone is on lineage and have recovery PE. I possible after update lineage -automatic change recovery from PE on lineage recovery?
 

MadcapCries

Member
Nov 20, 2015
6
4
Has anyone tried to volume up the call speaker?
I was trying with that method but nothing happened
 

MagnesG

Member
Dec 6, 2016
15
5
Is it easy to get GoogleSans font working? Have anyone been using it on this rom?

For the record, I used fontmanager for that in 12.1 so not sure if 13 is compatible or not.
 

LTFOUND

Member
Jul 27, 2017
48
20
T-Mobile LG G2
Xiaomi Poco F1
  • Like
Reactions: MagnesG

pmcmm

Senior Member
May 15, 2016
188
87
Xiaomi Poco F1
Ive been facing a bug with the calendar for a while now, so i decided to check if there are more people facing it.

When creating an event in the calendar, are you able to switch the time zone? Its set by default to GMT, and no way to change it, it appears always "no results" no matter what I type.

Screenshot as example:
Screenshot_20230209-182711_Calendar.png
 

BigWaxx

Senior Member
Oct 22, 2013
56
14
Trigrad
HTC Desire HD
OnePlus One
Hello, not sure it's happening to anyone else but I had issues with the wifi tethering today. Once the laptop was connected the icon in the notif bar started blinking and the connection was not working. No issue at all with USB tethering...
Had the same with 20230114 build. Works as intended with 20230128 and later.
I am currently on 20230204 and I'm getting a huge battery usage by Trebuchet and Aperture even when not working. Battery barely lasts a day now.
Anyone else experiencing the same thing?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    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.
    4
    To all people who have trouble with their banking apps, I did reverse engineer my banking app some time ago and found they use "Rootbeer" implementation from Github:
    https://github.com/scottyab/rootbeer

    So if some expert here can compile a list of steps to trick all of the detection methods we might get somewhere - this is the most comprehensive detection implemention I have seen so far. I even detects just LineageOS without root already as "unsafe".

    I could just re-compile the app with "rootbeer" always returning "false", but I am not sure how that will fair with a) my own signature applied (probably play store might flag it) and b) future updates, where I would have to recompile the app each time.

    Even my countries local "McDonalds" app has root detection, though they don't use Rootbeer.

    Such a shame companies don't trust root users any more, even though in my opinion we use our devices in a more responsible way than most.
    3
    Good news then. Will March security patch be in tomorrow's build?
    No, we are still testing.
    3
    Just for reference my stock lineage without root is showing the following results with rootbeer.
    I do not have any problems with banking apps.
  • 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.