30

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

 1 year ago
source link: https://forum.xda-developers.com/t/rom-official-lineageos-19-1-weeklies-for-xiaomi-poco-f1.4449155/page-3#post-86979413
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

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

Updated to todays build. Installed Lygisk this time because sideloading Magisk every time gets old. My phone app has never accessed my location.

Yeah i'm also sure i'll soon switch to lygisk, reinstalling magisk really got old lol

Updated to todays build. Installed Lygisk this time because sideloading Magisk every time gets old. My phone app has never accessed my location.

Good to see someone using my advice

hakkitarion

Member
May 30, 2019
I updated to today's build fine and Lygisk (magisk fork) survived the update as it should on encrypted lineage and kept root

Thanks for the valuable tip with Lygisk. Have now also installed Lygisk and then updated the Rom. After the update my root is preserved

Reactions: first_damned

Abdel1993

Member
Sep 20, 2019
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! πŸ˜πŸ‘
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.

Kamul_PL

Member
Nov 28, 2015 Katowice
I can live with manually going into TWRP and updating from /data/lineageos_updates the OTA updates.

Encryption still listed with "getprop ro.crypto.type" as block.

Does it mean that you managed to update LineageOS from 18 to 19 with Full Disk Encryption enabled without bootloop? If yes, did you have "Require PIN/password to start device" option enabled?

If no, is anybody successful in such an update with "Require PIN to start" enabled? I'm asking, because I'm still waiting with update. I've heard, that mentioned by me configurations are problematic for LineageOS 19.

Last edited: Monday at 4:09 PM

simpz

Member
Dec 30, 2014
Does it mean that you managed to update LineageOS from 18 to 19 with Full Disk Encryption enabled without bootloop? If yes, did you have "Require PIN/password to start device" option enabled?

If no, is anybody successful in such an update with "Require PIN to start" enabled? I'm asking, because I'm still waiting with update. I've heard, that mentioned by me configurations are problematic for LineageOS 19.

Yup I have FDE and managed to update to LineageOS 19.1 20220521, this one finally prompted for an FDE password at boot like 18.1 did. Every version before this bootlooped for me.

The only thing I have is TWRP no longer can unencrpt my /data. But has remained FDE (thankfully). Just updated to 20220528 with no problems. I have kept TWRP but I have an SD Card with plain exFAT on it, so I can copy updates from /data/lineageos_upodates to the SD Card for installing in TWRP.

When I did the update to 19.1, I did it in TWRP with the /data unencryped and mounted, it seemed to want to do something to that partition. The 19.1 zip was on my SD card, with Magisk on there too. However I just did the 19.1 and not Magisk for the update, didn't want to complicate the update process.Went back to TWRP recovery after it updated/booted to 19.1 successfully.

My setup is probably even more complex than your, I setup a different FDE (long) password with a shorter PIN for screen lock. So if it works for me should work for you.

Kamul_PL

Member
Nov 28, 2015 Katowice
My setup is probably even more complex than your, I setup a different FDE (long) password with a shorter PIN for screen lock. So if it works for me should work for you.

And here you're wrong.πŸ˜‰ Exactly the same situation here. So even better, that also this case was tested.

Thank you very much for the reply and for the good news.πŸ™‚ It's nice it's still possible to stay with the FDE.
So it seems the only problem (skipping the fact that TWRP can't decrypt /data) is to unable to revert the old LOS 18 via TWRP in case something went wrong?

simpz

Member
Dec 30, 2014
And here you're wrong.πŸ˜‰ Exactly the same situation here. So even better, that also this case was tested.

Thank you very much for the reply and for the good news.πŸ™‚ It's nice it's still possible to stay with the FDE.
So it seems the only problem (skipping the fact that TWRP can't decrypt /data) is to unable to revert the old LOS 18 via TWRP in case something went wrong?

That was pretty much my thinking. I took a backup to the SD Card from TWRP and I knew I could restore /data and reflash 18.1 which I had on the SD Card. But to be honest during earlier 19.1 bootloops I could from TWRP just reflash 18.1, as 19.1 hadn't appeared to have even tried looking at my /data.

Also not sure sure if I restored /data it may have been unencrypted but can't remember from last time I did this.

jojy thomas

Senior Member
Sep 13, 2016 Kottayam
Hi-Res seems to be working for me on today's build (28052022). It doesn't work for sampling rate of anything higher than 192 kHz though. For me 192kHz has been working since day one. IR camera doesn't work for me. I think there were some Gcam mods that supported secondary camera's, you can try them.

EDIT: After running the phone for a couple of hours here are some of the changes I saw,
Offline charging / power off charging works fine.
Didn't see many location requests from phone services in location usage. Mainly google.
Services do take a slight bit more time to start after boot.
Device seems to be taking random inputs / freezes after reboot.

EDIT2: Touch seems to be broken. There are times, where if I don't touch the device at all and then try to perform the actions, the actions don't register at all. The phone then takes up those inputs after 5 - 10s delay and just messes around on the screen. I have to lock the device and unlock it to get the touch working again. Reverting back to my older build of 07052022.

192kHz works, but it's not the best, the sound seems to be different, one side it's lower or something, 384KHz is perfect, but it's broken, android 11 had no issue like this!

Reactions: duttyend

Abdel1993

Member
Sep 20, 2019
@everyone Does anyone of you guys know if the Dutch language (or any other language) is finally supported in the AOSP keyboard?

Thanks in advance for letting me know! Cheers

fairyrobot

Senior Member
Jan 8, 2013
@everyone Does anyone of you guys know if the Dutch language (or any other language) is finally supported in the AOSP keyboard?

Thanks in advance for letting me know! Cheers

just tested again, no luck on latest build. the dictionary is installed, but gesture typing still does not work. back to g-board...

xdasmile

Member
Feb 25, 2014
Hi all,
Before updating to 19.1 I just wanted to make sure I have the right procedure. I also wrote it down in case it is right and helps anybody else. I would be very grateful if someone could have a look at it and confirm.

- in the existing system, backup everything that I can several times (online, SD card, etc.)
- download latest nightly zip of LineageOS 18.1 and latest MindTheGapps (at the time of writing this is MindTheGapps-12.1.0-arm64-20220416_174313.zip) β€” 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 TWRP which hasn't changed since 18.1, same for firmware.]
- reboot to recovery (I don’t have Magisk to make updates easier and because I can do most things I need without root)
- backup of everything except system and vendor
- install (dirty flash) LineageOS and MindTheGapps at once
- clear dalvik and cache, just in case
- reboot
- wait a bit for the system to come up

Would that work? Any help will be greatly appreciated!
Have a great day!
Hi all,
Before updating to 19.1 I just wanted to make sure I have the right procedure. I also wrote it down in case it is right and helps anybody else. I would be very grateful if someone could have a look at it and confirm.

- in the existing system, backup everything that I can several times (online, SD card, etc.)
- download latest nightly zip of LineageOS 18.1 and latest MindTheGapps (at the time of writing this is MindTheGapps-12.1.0-arm64-20220416_174313.zip) β€” 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 TWRP which hasn't changed since 18.1, same for firmware.]
- reboot to recovery (I don’t have Magisk to make updates easier and because I can do most things I need without root)
- backup of everything except system and vendor
- install (dirty flash) LineageOS and MindTheGapps at once
- clear dalvik and cache, just in case
- reboot
- wait a bit for the system to come up

Would that work? Any help will be greatly appreciated!
Have a great day!

1- too extreme of a backup (i do the same, 3 copies of everything) πŸ˜‰
2- lineage 18.1 or 19.1? (never used mind, i use nik but it should work)
If you use DFE you can put files in internal, but if not use sd,otg or adb
If you just use recovery for rom and gapps use los recovery
3-√
4- again a backup? I like your style
5- if you going from 18.1 to 19.1 is better to clean flash (dirty may work or not)
6-√
7-√
8-√

Reactions: duttyend

xdasmile

Member
Feb 25, 2014
1- too extreme of a backup (i do the same, 3 copies of everything) πŸ˜‰
2- lineage 18.1 or 19.1? (never used mind, i use nik but it should work)
If you use DFE you can put files in internal, but if not use sd,otg or adb
If you just use recovery for rom and gapps use los recovery
3-√
4- again a backup? I like your style
5- if you going from 18.1 to 19.1 is better to clean flash (dirty may work or not)
6-√
7-√
8-√

Thank you very much for your quick reply!
2a) of course I meant 19.1 I'll correct that when the rest is clear too.
2b) As I already have TWRP installed I thought I could leave it, last time I checked it was more powerful than los recovery?
5) Oh no, there's no way to update without reconfiguring everything? I'd really like to avoid that...
Have a nice day and thanks again!

Thank you very much for your quick reply!
2a) of course I meant 19.1 I'll correct that when the rest is clear too.
2b) As I already have TWRP installed I thought I could leave it, last time I checked it was more powerful than los recovery?
5) Oh no, there's no way to update without reconfiguring everything? I'd really like to avoid that...
Have a nice day and thanks again!

Some people reported that could update from 18.1 to 19.1 dirty, some used DFE but that only work if flashed before first boot if you already have encrypted rom it will mess the encryption and you will need to format, so dirty may or may not work, if you testing it be sure to have all backup outside phone internal.
You can backup app with data if you have root.
Anyway changing for different versions of android its always better to clean flash.
Good luck...

The padding isn't good for f1. And no game mode. Not even Google one.

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK