same here, i thing its phone services asking location...I still think something is strange wwith the battery usage.
On medium usage (just some web browsing and texting) I only get around 2 hours of SOT and I have to charge every evening. Before with the same apps and usage on 18.1 I was able to go nearly 2 days without charging.
I checked this with battery-historian and I see a lot of kernel wakelocks, roughly every 40 seconds.
But all of them are marked as "unknown".My gut tells me this has something to do with the phone service requesting location permission in nearly the same intervall when the screen is on.
Does someone know how to the source of these "unknown" events?
(The phone was placed on the table without usage for 1 hour., it never goes to deep doze, even over night.)
I followed the https://github.com/google/battery-historian#Advanced guide. Maybe I will try the kernel traces.
If you look here it is supposed that it is an issue with gapps and shall be fixed in nikgapps (I don't know the current state).I still think something is strange wwith the battery usage.
On medium usage (just some web browsing and texting) I only get around 2 hours of SOT and I have to charge every evening. Before with the same apps and usage on 18.1 I was able to go nearly 2 days without charging.
I checked this with battery-historian and I see a lot of kernel wakelocks, roughly every 40 seconds.
But all of them are marked as "unknown".My gut tells me this has something to do with the phone service requesting location permission in nearly the same intervall when the screen is on.
Does someone know how to the source of these "unknown" events?
(The phone was placed on the table without usage for 1 hour., it never goes to deep doze, even over night.)
I followed the https://github.com/google/battery-historian#Advanced guide. Maybe I will try the kernel traces.
I forgot to add the quote. Here it is.Don't worry, this will be fixed with next release of NikGapps. I'm removing the default permissions allocated to GoogleDialer app. Shouldn't be a problem then.
I am on a recent build and I don't have problems with mind the gapps. Just had to reflash it one time, but the update after that worked well without reflashingWell, are you on a recent LOS19 build? The entire reason we went to NikGapps is because MindTheGapps stopped working with any build past 20220528 (may)
I had problems with mind the gapps and only nikgapps core worked. On latest buildWell, are you on a recent LOS19 build? The entire reason we went to NikGapps is because MindTheGapps stopped working with any build past 20220528 (may)
i am using flamegapps without any problems, and i am not having the location bug anymore...I had problems with mind the gapps and only nikgapps core worked. On latest build
Yes, enable zygisk in magisk and deny list then add the apps you want to deny or hide from rootRoot can be successfully hidden from apps like Axis Mobile, ICICI Pockets in this ROM? I was successful in this regard in A11 (crDroid) but not since the switch to A12 (Awaken). I am planning to try different ROMs but I would rather not waste limited mobile data if anyone can please confirm or otherwise. Thanks.
For a lot of apps the above isn't sufficient and Shamiko is necessary to hide root. And for a few LSPosed + Xprivacy Lua and/or HMA is necessary. Plus freezing the Magisk Manager itself in the case of the two I had mentioned. Reportedly they just don't work in some ROMs.Yes, enable zygisk in magisk and deny list then add the apps you want to deny or hide from root
Which package did you flash? It won't let me flash FlameGApps-12.1-basic-arm64-20220612, wrong android version?i am using flamegapps without any problems, and i am not having the location bug anymore...
it was exactly that oneWhich package did you flash? It won't let me flash FlameGApps-12.1-basic-arm64-20220612, wrong android version?
I'd recommend not using magisk or rooting your device if you don't have to. Do you use it on this rom to pass safety net?For a lot of apps the above isn't sufficient and Shamiko is necessary to hide root. And for a few LSPosed + Xprivacy Lua and/or HMA is necessary. Plus freezing the Magisk Manager itself in the case of the two I had mentioned. Reportedly they just don't work in some ROMs.
Root is absolutely necessary in my case to manually lock LTE bands, enable bypass charging, install the bold font of my choice etc. However while I hadn't checked in Awaken in crDroid I found that out of the box without flashing Magisk these pesky apps were working without any issue! SafetyNet was passing by default. Afterwards even after flashing Magisk and following the usual steps these apps still continued to work. Only difference was I had formatted data and the device was encrypted this time as DFE didn't work for some reason.I'd recommend not using magisk or rooting your device if you don't have to. Do you use it on this rom to pass safety net?
That's right. Thanks for the heads-up, already updated the post.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.![]()
Lineage recovery is the only official supported at the moment. Of course it can't decrypt userdata, but that was never intended anyway.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?
I am aware of that and will try to fix it as soon as I have time. Not something with big priority.
I doubt that we will ever see a TWRP recovery that supports FBE decyption on this device.afaik neither FBE nor FDE work (well) with current TWRP, so maybe one fix on their side fixes it all ? we'll see![]()
![]()
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.