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

Search This thread
Oct 31, 2010
20
5
On latest nightly and mindthegapps my dialer app (stock, not google dialer) is not always appearing when I receive a phone call, anyone else geting this?

My workaround is to open dialer and try and make a phone call, the incoming call is then displayed along with a warning that I can't make an outgoing call right now, then I can answer the phone.
 

fightforlife

Senior Member
Oct 25, 2012
51
34
BBS is showing me two wakelocks which Seem to be connected to Bluetooth.

898000.qcom,qup_uart
hal_bluetooth_lock

They are active around 3-4 hours a day.
I found some old threads where people were told to restart the phone with Bluetooth off. Did someone here about this or also uses Betterbatterystats?
 

tchoucar

New member
May 26, 2021
3
0
Hello,
I have been using lineageos on my Beryllium for a very long time and I am really satisfied with it. But I have a question. It's 18.1, and I want to upgrade it to 19.1. How is the upgrade going? I have to erase the whole smartphone and start from scratch or I can do it keeping my data as a simple update?

Thanks.
 

bin/bash

Member
May 2, 2022
24
17
Hello,
I have been using lineageos on my Beryllium for a very long time and I am really satisfied with it. But I have a question. It's 18.1, and I want to upgrade it to 19.1. How is the upgrade going? I have to erase the whole smartphone and start from scratch or I can do it keeping my data as a simple update?

Thanks
See upgrade section on the official lineageos site: https://wiki.lineageos.org/devices/beryllium/upgrade

I would recommend backup important data though. For me there was no problem upgrading.
 

AtomicStryker

Senior Member
Nov 19, 2015
216
118
www.atomicstryker.net
BBS is showing me two wakelocks which Seem to be connected to Bluetooth.

898000.qcom,qup_uart
hal_bluetooth_lock

They are active around 3-4 hours a day.
I found some old threads where people were told to restart the phone with Bluetooth off. Did someone here about this or also uses Betterbatterystats?
Can't you just disable bluetooth and check if the wakelocks go away? I always have it off when not in use

With silvercore kernel, Magisk + LSPosed + Greenify aggressive doze my phone uses around 1% charge per hour, slightly more than it was in LOS 18. I have generally very low screentimes (2-3h per charge, no games). My phone is a glorified email reader / alarm clock which very rarely is used to navigate or play some music over BT.
 

rens-br

Member
Apr 5, 2013
16
12
Just installed the 02/07 version from the in-build updater, coming from the 20220430. When I first booted I got the 'Play Store has stopped' error, so I installed MindTheGapps-12.1.0-arm64-20220605_112439 through recovery. But I still have the 'Has stopped' error and went back to the 0430 version.
 

TioCareca

Senior Member
Just installed the 02/07 version from the in-build updater, coming from the 20220430. When I first booted I got the 'Play Store has stopped' error, so I installed MindTheGapps-12.1.0-arm64-20220605_112439 through recovery. But I still have the 'Has stopped' error and went back to the 0430 version.
i am using flame gapps and i dont have that problem since two last builds, both updated from in-build updater (OTA).
 
  • Like
Reactions: rens-br

rens-br

Member
Apr 5, 2013
16
12
i am using flame gapps and i dont have that problem since two last builds, both updated from in-build updater (OTA).
I have downloaded "FlameGApps-12.0-basic-arm64-20220612.zip" and the 12.1 version and with both versions I got the following error:
'This package is for android: 12/12.1 only. Your ROM is android. (And then no number)

Edit: I now downloaded "NikGapps-core-arm64-12.1-20220629-signed", looks like it stopped crashing. After I cleared the Google Play Services cache.

So to be clear: I'm running:
- 0702 version of LineageOS
- Magisk
- NikGapps-core-arm64-12.1-20220629-signed
 
Last edited:
  • Like
Reactions: TioCareca

HelmutK.

Senior Member
Jan 30, 2018
86
9
Does anyone else have a problem with the microSD card? When I play offline content via tidal, playback stops after an indefinite period of time and tidal can no longer access the microSD card. Google Maps can no longer access the micro SD card either. However, the card does not show as ejected and I can still access it through the file manager. I've also tried another micro SD card, but with the same result.
 

sponk0

Senior Member
Apr 7, 2019
89
180
Moto G 2015
Xiaomi Poco F1
FYI: OTA update from 2022-07-02 to 2022-07-09 went fine on my device. All looking good so far

Note: I recently decided to go for a fresh install , after all those confusions with play services, location bug and several dirty-flash experiments with different Gapps versions. I restarted fresh with 2022-07-02 and mindthegapps, using los recovery (i.e. following exactly the official installation instructions). So far I am very happy with this combination.
 

Abdel1993

Member
Sep 20, 2019
35
41
FYI: OTA update from 2022-07-02 to 2022-07-09 went fine on my device. All looking good so far

Note: I recently decided to go for a fresh install , after all those confusions with play services, location bug and several dirty-flash experiments with different Gapps versions. I restarted fresh with 2022-07-02 and mindthegapps, using los recovery (i.e. following exactly the official installation instructions). So far I am very happy with this combination.
You have to learn to look better. The location bug is still there as of July 9 (Phone Services). Look for yourself in the Privacy Dashboard under Location, if you don't believe me.
 

bin/bash

Member
May 2, 2022
24
17
You have to learn to look better. The location bug is still there as of July 9 (Phone Services). Look for yourself in the Privacy Dashboard under Location, if you don't believe me.
Not there for me if I look in the Privacy Dashboard. Idk why you suppose the bug is there for him without being able to know that at all.
 
  • Like
Reactions: sponk0

sponk0

Senior Member
Apr 7, 2019
89
180
Moto G 2015
Xiaomi Poco F1
You have to learn to look better. The location bug is still there as of July 9 (Phone Services). Look for yourself in the Privacy Dashboard under Location, if you don't believe me.
Thanks for your feedback and sharing your experience. I'm no expert on this topic, I was referring to "obvious" access to location services, including the notification banner. I don't have these any more, unless I really use gps.
The privacy dashboard in the settings menu also only shows "location" access by 3 different apps I intentionally started myself for the last 24h (navigation apps, fitness tracker). Phone services is not listed there for me
 

Abdel1993

Member
Sep 20, 2019
35
41
The privacy dashboard in the settings menu also only shows "location" access by 3 different apps I intentionally started myself for the last 24h (navigation apps, fitness tracker). Phone services is not listed there for me
Please look good bro.

Go to Apps > Show System Apps > Phone Services and click on Permissions. You will see that the location permission cannot be changed and the location was recently requested.

I verified this literally minutes ago by LineageOS July 9 clean the flash with MindTheGapps.

This is a bug in LineageOS and I don't know when they plan to fix it.
 

sponk0

Senior Member
Apr 7, 2019
89
180
Moto G 2015
Xiaomi Poco F1
Please look good bro.

Go to Apps > Show System Apps > Phone Services and click on Permissions. You will see that the location permission cannot be changed and the location was recently requested.

I verified this literally minutes ago by LineageOS July 9 clean the flash with MindTheGapps.

This is a bug in LineageOS and I don't know when they plan to fix it.
Yes, you are correct, the permission is set as you described, and it has been used recently.
Whether this is a bug or intended behavior I can't judge. To me the "bug" was that the annoying popup came every few minutes. I personally have no problem with a system app using system functions. Sorry if my post was misleading.
 
Oct 31, 2010
20
5
I also clean installed July 2nd + MindTheGapps, then dirty flashed July 7th with no problem.

I haven't had the location icon in the notifications bar show up since the clean flash but Phone services (com.android.phone) does have location permissions and says it was accessed recently
 
  • Like
Reactions: sponk0

Skorpion96

Senior Member
Aug 28, 2014
228
37
Palermo
After latest update now my device reboot to fastboot instead of rebooting where I say, after that with keys combinations I can boot where I want, I wonder why?

Fixed: was my vol- button fault, I pressed hard it and cleaned with alcohol and it fixed
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Fyi: OTA Update from 2022-07-16 install went fine, everything looks good. Security string updated to July 05, 2022
    7
    OK, thanks a million for your quick reply, I’ll launch the update now then… 🤞
    It worked! I’m so so so happy! Thanks a million!!!

    For "posterity", here’s what I did in the end:
    1. in the existing system, backup everything that I can several times (online, SD card, etc.)
    2. download latest nightly zip of LineageOS 19.1 (for me it was lineage-19.1-20220709-nightly-beryllium-signed.zip), MindTheGapps (for me it was MindTheGapps-12.1.0-arm64-20220605_112439.zip) and TWRP (for me it was twrp-beryllium-v3.6.2-A12-V3.img) — put everything on the SD card (if there is no SD card, it also works with adb, and maybe also with the internal memory but I'm not sure) [Apparently no need to update firmware which hasn't changed since 18.1] — usually, the latest files can be found here https://forum.xda-developers.com/t/poco-f1-ultimate-collection-guides.4192715/
    3. reboot to recovery
    4. backup everything in TWRP except system and vendor
    5. update (flash) TWRP
    6. reboot to recovery — the new TWRP will not be able to decrypt the data, so press cancel when asked for your PIN, you can flash the zip files anyway
    7. if you can, backup again [in my case it didn’t work since it wouldn’t decrypt]
    8. install (dirty flash) LineageOS and MindTheGapps at once and in this order
    9. clear dalvik and cache, just in case
    10. reboot
    11. wait a bit for the system to come up. Check if everything works fine. In my case, there were small bugs that disappeared after a second reboot.
    12. if you want, you can now reboot to recovery, this time TWRP can decrypt your data and you can backup the functioning new system (I wasn’t able to backup SystemExt or Recovery, TWRP didn’t move forward and when I canceled, it showed an error related to CreateTarFork, but when I unchecked SystemExt and Recovery, everything went well)
    Have a nice day, and thanks again to all of you and the great developers!
    6
    OTA 30 july successful...
    4
    Fyi: OTA Update to 2022-07-23 build went fine here, all is looking good
    3
    Aug 06 Update went fine ( OTA), all looking good
  • 25
    Just fixed power-off charging mode.
    23
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), 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.​

    Downloads:

    Notice:
    • No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

    Installation:
    • Reboot to recovery
    • Format /system, /data and /cache
    • Install LineageOS zip package
    • Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
    Important notes:
    • * Required * firmware version must be based on MIUI Q-based builds.
    • GApps can only be flashed on clean installs.
    • Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

    Credits & collaborations:
    All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​

    Device wiki:
    7
    This has remained unchanged for years, but I think you mean version 12.0.3.0. That is the last available version for our device.👍
    That's right. Thanks for the heads-up, already updated the post.
    7
    Are there any downsides to the Lineage recovery as opposed to TWRP? I've only ever used TWRP before but apparently Lineage recovery seems to work more reliably for this build. Is it true that TWRP won't work with encryption and OTA updates need to be flashed manually in TWRP?

    With Lineage recovery, can I still backup, restore, root with Magisk, and install Gapps?
    Lineage recovery is the only official supported at the moment. Of course it can't decrypt userdata, but that was never intended anyway.
    Offline charging is broken, I suspect it's a kernel problem.
    I am aware of that and will try to fix it as soon as I have time. Not something with big priority.
    afaik neither FBE nor FDE work (well) with current TWRP, so maybe one fix on their side fixes it all ? we'll see :)
    I doubt that we will ever see a TWRP recovery that supports FBE decyption on this device.
    7
    2okPze5.png

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

    @bgcngm This has remained unchanged for years, but I think you mean version 12.0.3.0. That is the last available version for our device.

    As several people have already said, thank you so much for your years of support to the LineageOS community! 😁👍