Check my POCO F1 Ultimate Collection & Guides at Magisk section Universal SafetyNet Fix.Is there a way to pass safety net so I can use my banking app please?
Check my POCO F1 Ultimate Collection & Guides at Clean Install guide.excuse me, i'm experiencing bootloop, i read the flashing instruction, but no luck and it stuck on bootanimation, i use official twrp, any suggestion ??
Hide prob config worked in magisk with magisk hide enabled and fingerprint changed to xiaomi pocophone F1. Now passes safety net fine.Check my POCO F1 Ultimate Collection & Guides at Magisk section Universal SafetyNet Fix.
wowi63 said:
I like to listen to podcasts in public transport and car via headphone jack - in the car via 3.5 mm jack plug on the radio. Every few weeks, the sound gets quieter without my intervention.
I have to unlock the F1 and want so raise the volume. I see a message:
"Raise volume above threshold? If you listen at a higher volume for a longer period of time, you can damage your hearing. Cancel/OK"
This is annoying in public transport and dangerous when driving.
I asked in another forum and got a note for a module in Magisk, "High Volume warning (Disable high volume popup dialog)". But I do not want to root my F1.
Is there another way to get rid of this message?
Thank you, Demodroid,Demodroid said:
Double tap the volume up button, it will automatically ignore the message.
Thank you, Demodroid,
Double Tap helps, but i have to unlock the Screen, which is not a good advice when driving car.
Is there no way to build LineageOS so that the message comes only once?
Hi there, I always supposed that all elements within any gapps package perform self-maintenance, I've been using gapps for years and never saw any outdated google app. Why do you want to update it, are you experiencing any issues?Guys, I'm on latest LineageOS 18.1, I wonder if I can update NikGapps (stock) package without performing a clean install (if so, how?). I didn't root the device, I'm using OrangeFox Recovery.
No issues at all, just thought I may have outdated apps but, if they do auto-update then it's okay.Hi there, I always supposed that all elements within any gapps package perform self-maintenance, I've been using gapps for years and never saw any outdated google app. Why do you want to update it, are you experiencing any issues?
Dirty flash according my Dirty Installation Guide, use MindTheGApps and install the rest apps from Play Store or use FlameGApps. NikGApps seems to have some issues.Guys, help. I downloaded LOS and installed NikGapps, and then cleared dalvik / cache as expected. However, there are some problems: some applications give a synchronization error and demand to install GP services. So I think, maybe I downloaded the wrong version? How to install it correctly on top of the existing one?
Root and then Magisk with MagiskHide, and if that isnt enough, MagiskHide Props and/or Universal Safetynet fix modules in Magisk.Hello, after updating to latest build some apps tells I'm rooted but I'm not.. Any idea how to solve? Thanks
Thanks, the idea is not to root and then having to hide it...I don't need to be root (and actually I'm not) but with the newest build a couple of apps started telling I'm root and don't let me use them..I could try to dirty flash the old version but it's a pity...Root and then Magisk with MagiskHide, and if that isnt enough, MagiskHide Props and/or Universal Safetynet fix modules in Magisk.
Basically DOUBLE DOWN
Lineage doesn't pass safetynet by default unlike some other roms. You'll have follow what Atomic said in order to do that.Thanks, the idea is not to root and then having to hide it...I don't need to be root (and actually I'm not) but with the newest build a couple of apps started telling I'm root and don't let me use them..I could try to dirty flash the old version but it's a pity...
Strange, it's working as it should here for me. Have you tried resetting the auto brightness user data by clearing the app data of "Device Health Services"? Just guessing, but maybe it helps.Note regarding the auto brightness: Same as others reported, it's much better now, but the "bug" as far i understand is still there. The slider on the brightness bar still moves (after unlocks) without me touching it, but now it keeps moving back to 50% instead of moving to 0%.
For windows 10:Can confirm it is related to drivers.
For me Windows used an ADB driver even though phone was in MTP mode with ADB disabled in developer options.
Simply went into device manager, selected to update driver and manually selected "MTP device" from the list - voila, it was showing again in win explorer![]()
Was facing similar issues in the beginning. Would suggest you use lineage recovery instead of twrp.2022 05 21 installed, got bootloop, anyone else ??
(Twrp came up ok but would not install from sd card or
restore, had to factory reset).
I tried again, as advised by people here, using LineageOS recovery to install LOS19.1(20220507). It made no difference it still boot loops. As previously it doesn't prompt for a FDE decryption password which must mean there is still something broken with the FDE support. It should recognise there is an FDE partition and prompt to try and decrypt it.That explains your issues. You should be able to flash los18 and mindthegapps 11 again, then your device should boot again (see previous posts in this thread)
In #1386 I described my experience with a FDE device. (I ended up factory resetting and installed fresh.)
Yes you need los recovery in order to get OTA updates while you are encrypted since TWRP can't handle decryption of encrypted A12 ROMs yet.A question towards those who already migrated to Los19:
Which recovery are you using?
I currently have TWRP installed, but some posts indicate that you need lineage os recovery? Is that correct?
Very likely. I am noticing these auto-brightness issues more often now while working on Android 12 and it's driving me nuts. Will give it a try and if it fixes the issue I will apply it over to the current builds.Having built the ROM with this patch, I can also confirm that it resolves my issues with auto brightness.
@bgcngm, it would be great if the patch was included.
It's ready, I just didn't share any unofficial build yet.