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

Search This thread

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
edit:
I've installed this one and it's have been solved
1680335005701.png

Thanks
 

jmf25

Member
Jul 17, 2021
5
0
I just noticed that volume for the ringtones and notifications are on the same bar
In previous versions it was possible to have them independent
Is it possible to fix it?
Thanks
 

Attachments

  • Screenshot_20230401-101526_Ajustes.png
    Screenshot_20230401-101526_Ajustes.png
    124.8 KB · Views: 23

Pettersson07

Member
Apr 1, 2023
5
3
Hi, my F1 got the latest version of LOS, but the problem is older.
I have a problem with the device, but not all time.
Sometime I get a call, but there is no possibility to answer the call. No message in the display, no green/red touchfield. But the sound works. After the call I got a message about it.
This is independently if the mobile in standby or not and ist not allways, just from time to time. I checked the permissions and the notifications.
Is there anybody with a similar problem with the dialer?
Any ideas to solve it?
Thanks
 
  • Like
Reactions: first_damned

wowi63

Senior Member
Hello, everyone,

I ran the LOS 19 -> LOS 20 upgrade some time ago.
Generally I am satisfied.
I only noticed now that the upgrade instructions say to make sure Global has firmware "V12.0.3.0.QEJMIXM" installed before upgrading. https://wiki.lineageos.org/devices/beryllium/upgrade
There is also a link how to do this. https://wiki.lineageos.org/devices/beryllium/fw_update

Now I am unsure.
If I look for settings -> about phone -> android version for the baseband version, it has nothing to do with the firmware name above.
"AT4.0.c2 6-331-0508_1622_8a737a5."

How can I tell if the firmware should be updated?

We have 4 Poco F1 in the family, I had updated the MIUI before the LOS installation.
The first two devices I had bought in April 2020, they had shipped with MIUI 9.6 (Android 8). I had upgraded them via MIUI 10 to MIUI 11.0.4 (Android 10) and then installed LOS.

Can I assume that with the LOS upgrades that I have run since then, the firmware was also updated?

On a related note, an oddity:
The two phones I bought new from Online-Shop Alternate.de at the time have the text at the top of Baseband.

I had bought two Pocophones on Ebay about a year later.
With these phones I had done exactly the same - updated MIUI and then installed LOS.
The baseband of these phones says "4.0.c2.6-00335-1227_1222_40a1464".
These two devices show the text "Poco" at startup.
The first purchased ones show "Pocophone by Xiaomi".

Greetings,
wowi63
 

bgcngm

Recognized Developer
If I look for settings -> about phone -> android version for the baseband version, it has nothing to do with the firmware name above.
"AT4.0.c2 6-331-0508_1622_8a737a5."

...

I had bought two Pocophones on Ebay about a year later.
With these phones I had done exactly the same - updated MIUI and then installed LOS.
The baseband of these phones says "4.0.c2.6-00335-1227_1222_40a1464".
What you see there is the baseband version (also know as modem). Clearly two of the devices are running on an older modem. This is part of firmware, so for those two you /should/ upgrade firmware as per the instructions.
 
Last edited:
  • Like
Reactions: wowi63 and pmcmm

senpaidev

Senior Member
Jul 27, 2012
186
63
www.varisht.dev
I installed the 20230401 build today and the 2 button navigation is gone. The only two options I get are 3 button layout and the gesture based navigation. The 2 button layout was a decent middle ground between fully gesture based and 3 button layout. Is this really a regression with Android 13 or just a temporary bug?
 

wowi63

Senior Member
What you see there is the baseband version (also know as modem). Clearly two of the devices are running on an older modem. This is part of firmware, so for those two you /should/ upgrade firmware as per the instructions.

Thank you very much! It would have been nice to tell which baseband-version is outdated ...
So i flashed one F1 with the same firmware and update one other.
This phone now boots with the text "Poco" and not "Pocophone for Xiaomi" anymore.
Well, one of the files to flash was "logo.img".

"4.0.c2.6-00335-1227_1222_40a1464" is the last baseband-version.

Greets,
wowi63
 
Last edited:

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.
Good news, links will be back next week :)
 

TioCareca

Senior Member
Sep 8, 2010
2,931
1,585
Barreiro
Xiaomi Poco F1
Redmi K20 Pro
Hi, my F1 got the latest version of LOS, but the problem is older.
I have a problem with the device, but not all time.
Sometime I get a call, but there is no possibility to answer the call. No message in the display, no green/red touchfield. But the sound works. After the call I got a message about it.
This is independently if the mobile in standby or not and ist not allways, just from time to time. I checked the permissions and the notifications.
Is there anybody with a similar problem with the dialer?
Any ideas to solve it?
Thanks
seems like a phone app problem, what phone app you using, you have all permissions? you have pause app permissions if unused?
 

Attachments

  • Screenshot_20230404-222732_Settings.png
    Screenshot_20230404-222732_Settings.png
    157.4 KB · Views: 26
Nov 1, 2018
25
12
LG G6
Xiaomi Poco F1
I installed the 20230401 build today and the 2 button navigation is gone. The only two options I get are 3 button layout and the gesture based navigation. The 2 button layout was a decent middle ground between fully gesture based and 3 button layout. Is this really a regression with Android 13 or just a temporary bug?
I also miss the 2 button layout since last update but I skipped 2-3 updates inbetween.
I also think its worse than in A12 because when I turn my phone there is no option to turn the screen in 2 button layout anymore, but its in the gestures layout available. ..
 

Peixeiro

Member
Mar 13, 2012
46
11
Hi, after a recent update (I miss some weeks updates) the phone don't vibrate when are in Do Not Disturb. In the past, with DND, the phone silence all sounds (call, messages, multimedia, ... but keep vibration. How to configure it to automatic at night disable sounds but keep vibration?

Another issue, the Recent Apps screen has stopped working. Every time I go there (I have gesture navigation) it's empty, just saying "No recent apps". I used it a lot to jump between applications and to close processes when I noticed the phone was slower.
 

bin/bash

Member
May 2, 2022
40
26
Hi, my F1 got the latest version of LOS, but the problem is older.
I have a problem with the device, but not all time.
Sometime I get a call, but there is no possibility to answer the call. No message in the display, no green/red touchfield. But the sound works. After the call I got a message about it.
This is independently if the mobile in standby or not and ist not allways, just from time to time. I checked the permissions and the notifications.
Is there anybody with a similar problem with the dialer?
Any ideas to solve it?
Thanks
Don't have that problem. However on another phone I had once the issue that if I would call, the phone app would hang up immediately. I suppose that it was a firmware issue. I put the sim in the second slot and there it was working. So if you can test the other slot maybe you can narrow down the issue.
 

first_damned

Senior Member
Feb 24, 2009
1,414
281
Birmingham
Xiaomi Poco F1
Hi, my F1 got the latest version of LOS, but the problem is older.
I have a problem with the device, but not all time.
Sometime I get a call, but there is no possibility to answer the call. No message in the display, no green/red touchfield. But the sound works. After the call I got a message about it.
This is independently if the mobile in standby or not and ist not allways, just from time to time. I checked the permissions and the notifications.
Is there anybody with a similar problem with the dialer?
Any ideas to solve it?
Thanks
I know how to solve this, are you using nikgapps by any chance? As its a known issue with the dialer not being set as default dialer/phone app.

Just force close phone app, clear the apps data and cache and set it as default phone app. That should work. I've had the same issue before.
 

Pettersson07

Member
Apr 1, 2023
5
3
I don't use any kind of GApps (Nikgapps, MicroG etc), most of the mobile is out of the box.
I changed now the SIMslot now from 2 to 1 by loosing the MicroSD-card. But without success, the mobile is ringing but the display keeps black as before.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    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.
    1
    I'm running LOS 20 20230520 and all looks good so far.
    1
    Since the upgrade from LOS 19 to 20. I have an intermittent problem with Wi-Fi. Always after some time (sometimes days, sometimes weeks), the phone disconnects from the AP and the attempt to reconnect fails. All APs are with WPA2 encryption. Restarting the phone always helps.

    In all APs the log is the same:
    11:54:16 wireless,info XX:XX:XX:XX:XX:[email protected]: connected, signal strength -56
    11:54:21 wireless,info XX:XX:XX:XX:XX:[email protected]: disconnected, unicast key exchange timeout, signal strength -55

    I think this is somehow related to wpa_supplicant. But I don't know how to debug it.

    I tried:
    - disable/enable Wi-Fi
    - forgetting the AP and setting it up again
    - fix connectivity button in the Internet section
    - change to random/static MAC address settings
    - every new weekly version of LOS 20 which was released

    Has anyone encountered this problem? Any ideas on how to debug this more?
    I've finally found solution. There is some kind of Wi-Fi/data/BT reset in Settings/Reset menu. No disconnections occurred since this.

    Downside is I've lost settings of SIM1/SIM2 settings for all my contacts. But this is not big trouble for me.
  • 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.