• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

sponk0

Senior Member
Apr 7, 2019
50
68
Some thought: I'm currently running the 2021-09-04 build. About 1 1/2 days ago I gave auto brightness another try. So far it's behaving as it should, didn't get any 0% brightness wake up so far. I'll keep watching...
There is something listed in the changelog about auto brightness again, but too me it sounds like code clean up only, so I wasn't expecting any improvement... Well, let's see....
 

AtomicStryker

Senior Member
Nov 19, 2015
191
95
www.atomicstryker.net
Some thought: I'm currently running the 2021-09-04 build. About 1 1/2 days ago I gave auto brightness another try. So far it's behaving as it should, didn't get any 0% brightness wake up so far. I'll keep watching...
There is something listed in the changelog about auto brightness again, but too me it sounds like code clean up only, so I wasn't expecting any improvement... Well, let's see....

Doing the same, well auto-brightness appears to be working but the setting slider moves by itself randomly, after each unlock or so it feels. So i have a random-level of auto-brightness which might blow up my eyes at night or turn the screen useless in sunlight.
 

sponk0

Senior Member
Apr 7, 2019
50
68
Doing the same, well auto-brightness appears to be working but the setting slider moves by itself randomly, after each unlock or so it feels. So i have a random-level of auto-brightness which might blow up my eyes at night or turn the screen useless in sunlight.
My experience after a few more days of watching: auto brightness bug still exists. The initial phase where it seemed to be better must have been coincidence
 

Hondal277

New member
Sep 20, 2021
2
3
Hi, I was copying data (a book) from my phone to my PC and my phone just reboot and said that data was corrupted and I needed to factory erase. I did , and everything looks apparently normal. But I'm concerned of this because if it happened once, can happen again.
 

penticton8

Member
Feb 28, 2018
24
2
Google Pixel XL
Xiaomi Poco F1
Hi, I was copying data (a book) from my phone to my PC and my phone just reboot and said that data was corrupted and I needed to factory erase. I did , and everything looks apparently normal. But I'm concerned of this because if it happened once, can happen again.
Same also, turned on, said encrypted data was corrupted, asked for password which I don't have, said do factory reset.
TWRP was still there but would not install backup. Did factory reset and AOK.
 
  • Like
Reactions: gongoscho

Largamelion

Senior Member
Sep 10, 2010
517
225
I flashed the latest build from TWRP as always but lost Magisk & thereby root. After flashing Magisk all was good again, fortunately still passed Google Play certification without having to change the fingerprint. Only had to reflash ANX Camera as that also disappeared.

Other than that, everything seems to work fine.
 
  • Like
Reactions: ilya_m

Tremolo4

Member
Dec 2, 2017
11
11
I flashed the latest build from TWRP as always but lost Magisk & thereby root. After flashing Magisk all was good again, fortunately still passed Google Play certification without having to change the fingerprint. Only had to reflash ANX Camera as that also disappeared.

Other than that, everything seems to work fine.
Did you decrypt the data partition in TWRP before flashing the update?
I always do that and it worked fine for me, Magisk works before and after update.
IIRC, if TWRP can't access the data partition, then Magisk can not restore itself after the update via its addon.d script.
 

Largamelion

Senior Member
Sep 10, 2010
517
225
Did you decrypt the data partition in TWRP before flashing the update?
I always do that and it worked fine for me, Magisk works before and after update.
IIRC, if TWRP can't access the data partition, then Magisk can not restore itself after the update via its addon.d script.
I've never done this is the past that I know of, unless this happens automatically when you enter your PIN in TWRP? I just did what I always do and this was the first time I lost Magisk.
 
  • Like
Reactions: ilya_m

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hi. About Gps. So behavior is strange: gps tool is able to lock fine, but ll maps application are not able to keep the fix. Even with the background gps service app it does not work. So gps is fixed in background, but upon switching to maps the fix is there but in few seconds the circle around position increases and stays non fixed..
    I checked the permissions on both gps a0s amd maps are the same-location and acctyvity sensors...

    What could it be, so weird.. is it somehow related to the gapps installed? I did not try switching.

    Apps used: gps test-fixes fine, gmaps-no fix, no speed, etc.

    Sptember 25 version has build prop ro.build.version.security_patch=2021-09-05
    This happens due to denial location permission of com.google.android.gms.
    This can be fixed by grant the location permission using adb shell

    adb shell pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION adb shell pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
    4
    Flashed today's build 20210918 and we got September security patch 20210905. Everything seems as usual 🙂
    4
    Just for your information
    I installed today's update (OTA) from 2021-09-25, everything looks good and normal so far
    3
    It is great to have the latest Android security patch.
    On the other hand, it would be nice if @bgcngm could update the kernel as it is still on Linux Kernel 4.9.276 (4.9.282 is out).
    Cheers
    2
    Hi, I was copying data (a book) from my phone to my PC and my phone just reboot and said that data was corrupted and I needed to factory erase. I did , and everything looks apparently normal. But I'm concerned of this because if it happened once, can happen again.
  • 47
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), 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 v11.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:
    22
    New build is out. It includes March's security patch.
    22
    New build is up, with this month's Android security fixes already included and working WiFi Display.
    17
    Lots of updates for the upcoming build. :D
    16
    I am a little bummed about Lineage OS 17.1 official support being dropped as I was really happy on that ROM.
    You do realize that I am human and can't support both branches, right?