yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] AsuraAristocrat:
I already tried TWRP, but it won't help me with my issue sadly.

Before installing LOS20 i would like to take a recent backup somehow or just boot back into 19 and proceed from there.

I investigated the issue a bit further, it looks like my system believes that im using File Based encryption (fileencryption=ice for /data in /vendor/etc/fstab.qcom and ro.crypto.type also displays file instead of disk or block(im not sure which one is the right one)) while i used Full Disk Encryption for my Data.

To be save, i already took a copy from the raw blockdevice (dm-0 in my case). But since i haven't found a way to get the encryption key for the Full Disk Encryption, i had no luck to decrypt it on another PC.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] chillipig:
As some apps appear to refuse to work unless a device is encrypted, I looked for a possible workaround and came across this: https://xdaforums.com/t/fake-encryption.3849826/

It suggests simply changing ro.crypto.state= to encrypted in system.prop on a non-encrypted device is enough to fool at least some apps.

The above is a Magisk module but I can't see it does anything other than change that one entry.

The question I have - Is doing this likely to actually activate real encryption? or would it cause a bootloop (I'm using twrp-beryllium-v3.7.0-A9.img by Reignz) and DFE-Pocof1-A13.zip to disable encryption as obviously I want the F1 to remain unencrypted.

Thanks.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Why not just encrypt?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] bgcngm:
Maybe he thinks that FDE is still a thing on this device. :p
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] chillipig:
No, it's not that, I just want straight forward access to files if I end up in a bootloop following a failed update and would rather benefit from the lack of an encryption overhead.

The thread also says RootBeer passes on all counts when fake encryption is applied along with the Zygisk deny list.

If this is true it would enable many apps to work that just rely on the RootBeer method of detection.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
You'll still get access to your files through recovery after putting in your pin/pattern if your encrypted, connect to a computer and away you go.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] chillipig:
In principle of course that should work, but I've seen enough unrecoverable bitlocker problems to know sometimes the correct pin/passcode can't be recognised because of hardware failings / data corruption etc.

I was just hoping someone would have an understanding of the encryption process on A13 as I use the phone all the time and can't really be doing a clean install, should I end up with major problems from trying this out.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] phaleg:
Hello!

I am considering to upgrade from my PE+11 to LineageOS and I have couple questions

May I do it on TWRP that is the only way I know? (post #11 from Jan. seems positive on it, if still valid)

Will the ROM be force encrypted in a way that I cannot avoid?

Is there any other big differences in the flashing process that I should be aware of?

Where can I find a more stable 19.1?

Thanks
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] p_a_l_o:
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:XX@wlan1: connected, signal strength -56

11:54:21 wireless,info XX:XX:XX:XX:XX:XX@wlan1: 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?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sponk0:
Just installed latest version 2023-04-22. All good. Security string updated to April 2023
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sponk0:
Digging up this older post again:

There apparently was something different in the builds with March 2023 security string compared to all other builds. Since today's build 2023-04-22 my health insurance and banking apps stopped complaining that my device is unsafe and started to work as they used to again.

Funnily rootbeer now shows that the device is rooted (rootbeer did not show root during builds with March security string)

@bgcngm : any idea what might have triggered this behavior?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Qpr2
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] senpaidev:
Installed the 20230422 build today. Works fine, though I still miss the 2 button navigation.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] GeForce66:
Installed 04/22 build today as well.

All good, except banking app now stopped working as it detects modified ROM :(

Not sure why all of the sudden, must be some LOS code change that triggered detection.

Left them a 1 star review on Play Store :/

Some dev here who has the power to restore functionality again? ;)

The bank devs are lazy, they just use "RootBeer" from Github.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] GeForce66:
Sorry doublepost
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] aragorn1203:
You can use adb from your computer for now.

Make sure you enable Rooted debugging in Developer options.

If you're on linux you can make a nice little script from this code.

adb root
adb shell mount -o rw,remount /
adb shell sed -i 's/ro.debuggable=1/ro.debuggable=0/' /system/build.prop
adb shell reboot

This code changes the value ro.debuggable in /system/build.prop from 1 to 0.

Hope it helps
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] GeForce66:
Thanks for the input! I will try tonight and report back, currently not @ home.

Much appreciated!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] GeForce66:
Hopped onto my Fedora right now and did your steps, and guess what - IT WORKS! :)

Checked the source code on Github for rootbeer and it just checks for "ro.debuggable = 1" and "ro.secure = 0".

You are a lifesaver, have a great day!

As mentioned, the bank devs are lazy and have just copied rootbeer into their banking app (checked their source code with APKlab)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] aragorn1203:
You might want to check this post:

https://xdaforums.com/t/rom-discontinued-lineageos-19-1-for-xiaomi-poco-f1.4449155/post-87696309

The pocketmode service was my culprit in the earlier version of this ROM and I still have it disabled in this version.

I am not sure if that is your case, but it is worth a try.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sponk0:
FYI: 2023-04-29 OTA update running fine
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
I try different roms but always come back to lineage, it's the fastest, most stable and up to date rom there is.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Peixeiro:
Hi,

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

Anyone with this issue? Until last month, this worked fine.

EDITED: PROBLEM RESOLVED!!!

After a deep search, I found here in a topic of another phone brand, a user with the same problem and who had the same configuration (LineageOS + NikGapps full).

I re flashed the NikGapps Full, updated version (previous installed was on Fev'2023) and now all work as expected. Recent apps menu, bottom swipe left or right, ...

Now, I leave the question, is it advisable to manually update the Gapps?

Shouldn't everything be updated automatically via the Play Store?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Ray Pist:
Has anyone tried if magisk 26+ survives lineage OTA updates? I know there's some kind of survival script when the update is flashed but the new magisk readme says: "any installation of Magisk v26+ using custom recovery will be incomplete; a subsequent re-installation through the Magisk app after booting up is required"

Would you recommend just staying on 25.2 or does it not affect the OTA updates?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] AtomicStryker:
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.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Ray Pist:
That's great to hear, thank you
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] fightforlife:
Short feedback, lineage-20.0-20230506 working fine for me.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Lineage beryllium website isn't loading for me and I need to download latest version
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Morillio:
Please post the last build here!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Hauk92:
Build from 06.05.2023:

vbmeta.img

recovery.img

boot.img

lineage-20.0-20230506-nightly-beryllium-signed.zip
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] No_Reason:
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?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
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
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] No_Reason:
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.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
I've had problems with mtg also, but all seems ok lately. Glad you got it sorted 👍
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sponk0:
Fyi: Today's build 2023-05-13 running fine with no issues
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] senpaidev:
Installed the 20230513 build today. No issues so far. Android security updated to 5th May 2023.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] jmf25:
Hello everyone

I have to thank the developers for all the awesome work they are doing. Congratulations

I want to make my contribution by improving LOS 20 because I have noticed a change in the adjustment of sounds in LOS 20 compared to LOS 19: now there is no option Link ring & notification volume

I think this option is a positive point in LOS 19 compared to LOS 20

Is it possible to transfer this option (Link ring & notification volume) in LOS 20?

In the attached file I have tried to make the comparison between both versions

Thanks again for your awesome work.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Ray Pist:
Just to add, I noticed some magisk modules break after installing OTA updates (in my case Viper4Android) until the installation through the magisk app is completed. So it's necessary for some use cases but everything works perfectly after that
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Astania:
I also would like to say big thank you for LineageOS developers maintaining updates for Poco F1.

My phone's running now LOS 20 20230513 build, but...

I've noticed, that Axet's Call Recorder (link) has stopped working.

It was working flawlessy before 8th may, but now it creates a file, a file lasts as long as the conversation time, but the recording is completely empty, there's only a silence.

I didn't change nothing in settings.

After updating LineageOs to new wersion (i've installed earlier build of LineageOS 20 with clean flash, now I've updated with system updater) Axet's Call recorder stopped to record.

I installed Magisk module, and after updating LineageOS I've also updated Magisk.

I tried to reinstall Axet's Call Recorder Magisk module but it didn't help.

Any ideas what to do?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] youvedone:
I'm running LOS 20 20230520 and all looks good so far.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Szynek:
Hello,

According to the doc, after installation I should see this:

However, I have this:

Question: is this ok? No errors reported on the phone side, plus the system booted without issues, but I wonder whether this can cause problems later down the line (does it mean that 0.02% of the procecess did not happen?).

I should point out, that I'm not dirty-flashing or anything (performed factory reset plus format data on the top of it), but I used TWRP instead of LOS recovery (which I'm not sure whether that's a factor in all this).
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] AtomicStryker:
You can re-flash the firmware from recovery if you are very scared. But you should be fine. Or just wait until saturday and perform the update which is a full flash aswell.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] p_a_l_o:
I had also troubles w. call recording since switch from Miui to LOS 20. I tried Google dialer magisk hack, BCG, axet, skvalex.

Axet was best free recorder but I had silent recordings for volte and car Bluetooth calls.

Now I'm using skvalex. It is the only one call recorder able to handle all types of calls. Unfortunately it costs 12 USD.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Just use the aosp dialer which comes with lineage to record calls
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] p_a_l_o:
Builtin LOS dialer recording is not available in my country so another hack have to be applied. And I'm also missing auto record feature. (Maybe I've not found option to enable it)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
There is no auto record function, just press record on dialer when your in a call.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Largamelion:
I'm still on LOS 19.1 with FDE. I would like to upgrade to LOS 20 but is there an easy way to switch to the newer FBE?

When upgrading from 18.1 to 19.1 I just disabled my fingerprint and PIN prior to upgrading and flashed LOS recovery to replace TWRP. All went well so I assume the same process will work for upgrading from 19.1 to 20 but if possible I would like to be up to date with encryption and switch to FBE.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] bin/bash:
It was mentioned somewhere earlier in this forum that FDE is not supported anymore in LOS20. So I suppose upgrading wouldn't work in your case anyway. I don't think you have another option than to clean install to switch to FBE.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Astania:
I've solved the trouble with recording with Xiaomi Poco F1 and official LOS 20, Axet's call recorder.

Unfortunately recording included in dialer doesn't support automatic call recording, so one who wants automatic call recording must use other solutions.

I figured out, that Axet's call recorder still works perfectly, but

DON'T UPGRADE TO THE NEWEST VERSION (actually 1.8.4) available on F-Droid.

Just install magisk module which also installs the app and don't upgrade it.

It works perfect on default settings, even after updating LOS to 20230527 and flashing Magisk again.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] p_a_l_o:
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.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Largamelion:
So there is no way to decrypt either prior to upgrading (disable FDE)? A clean install would mean about two days work to get everything setup correctly again, something I want to avoid at all cost. I have certain apps that require an entire process of identifying yourself to get them working again, a lot of hassle. Not even sure if it's worth upgrading then as 19.1 still works good, but I'd like to stay up to date security wise and 19.1 is no longer getting security updates either.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Afraid not. It'll be a busy weekend for you then, something to do.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Today's update is spot on as usual
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] johnbhatt:
I am having this issue with Bluetooth devices. Within couple minutes of pairing, device is disconnected and audio comes out.

Tried multiple devices.

Clean format, latest build with gapps.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] kosto6:
Hi all, I did a dirty upgrade from 19.1 to 20 and the phone is working, but after some minutes the touchscreen stops working and the phone is restarted automatically.

When the touchscreen stops working, the phone seems that is still working, for example, I was playing Clash Royale and I could see and listen how the game was working, but I could not interact with the game.

Ideally I would like to prevent a factory reset :). Do you know what can I check or do?

Regarding the update process. Initially I had an encrypted 19.1 with twrp 3.7.0_a12. I installed from twrp the LOS20 image then mindthegapps and finally magisk and clean cache/dalvik. I didn't install any custom kernel.

I have checking the logcat just in case I was lucky, and I have seen that the phone generates a stacktrace report that I attach (I have tried to attach the file but it seems that I can't) but I am not able to get something clear. It seems that PowerManagerService is triggering the problem, but I am not sure....

Since It seems that I cant upload the stactrace file I just copy the beginning of the generated file (anr_2023-01-04-14-57-18-201):

Subject: Blocked in handler on foreground thread (android.fg), Blocked in handler on main thread (main), Blocked in handler on ActivityManager (ActivityManager), Blocked in handler on PowerManagerService (PowerManagerService)

--- CriticalEventLog ---
capacity: 20
events <
timestamp_ms: 1672840317649
java_crash <
exception_class: "android.database.sqlite.SQLiteException"
pid: 31101
process: "com.android.deskclock"
process_class: 2
uid: 10143
>
>
events <
timestamp_ms: 1672840396233
half_watchdog <
subject: "Blocked in monitor com.android.server.power.PowerManagerService on foreground thread (android.fg), Blocked in handler on PowerManagerService (PowerManagerService)"
>
>
events <
timestamp_ms: 1672840435381
watchdog <
subject: "Blocked in monitor com.android.server.power.PowerManagerService on foreground thread (android.fg), Blocked in handler on PowerManagerService (PowerManagerService)"
uuid: "7387aa73-4965-4def-a5b6-caf26123b997"
>
>
events <
timestamp_ms: 1672840468368
java_crash <
exception_class: "android.database.sqlite.SQLiteException"
pid: 5159
process: "com.android.deskclock"
process_class: 2
uid: 10143
>
>
events <
timestamp_ms: 1672840493597
java_crash <
exception_class: "android.database.sqlite.SQLiteException"
pid: 9633
process: "com.android.deskclock"
process_class: 2
uid: 10143
>
>
timestamp_ms: 1672840599023
window_ms: 300000
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Abdel1993:
Oh f*ck! Good to know I'm not the only one walking around with this problem, super irritating!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] pmcmm:
Yep, bluetooth seems to be broken. I still face audio quality issues, and if i do a phone call, bluetooth goes off.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] marsa47:
It is so strange that Bluetooth is working fine for me. I use BT earbuds for few hours every day and haven't experienced a single issue so far.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] 123r4ka456:
Alright, thanks bro.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] jojy thomas:
Probably bT codec issue, SBC, aac , aptX, ldac?

Which is yours?

SBC and AAC probably works fine ig
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] marsa47:
Just checked, and you are correct. One of my headsets is AAC and the other SBC only (both working fine).
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] kosto6:
I solved my problem. It seems that the greenify app was causing all the mess.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sponk0:
My headphones use aptX HD and I didn't notice any problems so far (I had to re-pair them once after the upgrade, though, but since then all looks good)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sam1101119:
Did the guide for passing the safetyNet check worked for others? I seem to be unable to make it pass the CTS one, because the universal safetyNet fix un-checks the zygisk hide for Google play services. Anyone has a solution?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] TioCareca:
Strange, i just flash safetynet fix, and i always pass and PlayStore is certified, i never check nothing in zygist hide.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sam1101119:
Which version of the safetyNet fix do you have?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] TioCareca:
2.3.1
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] sam1101119:
One thing I noticed is that my play store wasn't certified even before I installed magisk, is that normal for lineageOS or may be strange?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] TioCareca:
Its normal, lineageOS don't pass certification because its a custom rom and obey the rules google has for custom roms.

Other custom roms may pass certification and safetynet and some even got gapps pre installed but google don't like that and lineageOS want to survive long run, its like that since cyanogen mod...
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Do you use magisk hide props config module to set the device fingerprint to pocophone F1 too?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] TioCareca:
I used in 19.1, i didn't in 20.0.

Device is identify as poco f1 without any modifications.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] first_damned:
Ah I didn't realise, I still used hide props config. No harm I suppose but its a step that's not needed
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] TioCareca:
I only flashed rom, gapps and magisk canary, after that activate zygist in magisk settings, flashed safetynet fix, reboot and all working, PlayStore certified and safetynet pass...