I got similar problem on Redmi 9. For me it works, if i reboot the phone in airplane mode. But when I enable SIM, then some channels are disabled. Maybe it is because of improper applying regulatory rules for detected country.Since I upgraded to 19.1 my phone does not pickup Wifi channels between 100-144 (so 5Ghz) anymore.
if don't know how to do these things like root, flash custom roms, about data, stealing. i think stay on original miui.
1-no... perhaps a gcam have enable the wide angle camera but in lineage i don't know (in arrow os it does have it)few questions:
1 no wide camera?
2 how to change color of settings menu without buyig repainter?
3 how to block phone by hacking by foreig people? i meann in miui eveyrything is locked and here easy access to twrp etc? how to make phone data etc safe if sommeone steal it?
4 easiest way to root?
I see people reporting lots of bugs on LineageOS 19.1, maybe someone that tested latest version can verify these problems or can share his/her experience with LOS 19.1?
I'm thinking into update, but reading latest replies i have big doubts.
Those happens due to denial location permission of com.google.android.gms, and related to the gapps bug(happens sometimes).LOCATION/GPS ISSUES
Hi everyone!
On lineage-19.1-20220617-nightly-vayu-signed I have issues with my phone locating with Google Play Services. It works with the app "GPS Test", but neither "Maps" or "Öffi" (public transport app).
Is there any way fixing this location issue without reflashing Lineage?
EDIT: MAybe worth noting that I came from MiUI 15.5 to LOS 19.1 ...
Thanks in advance!
Cheers!
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
YEEEHAAA!!!!Those happens due to denial location permission of com.google.android.gms, and related to the gapps bug(happens sometimes).
This can be fixed by grant the location permission using adb shell
Code: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
That's a pretty old version of TWRP, update to the latest "UNOFFICIAL"(but it works like a charm) build from the official developer.FAIL: DECRYPT /DATA IN TWRP
For making backups I need to decrypt /data, but in TWRP 3.6.0._11-0 I can neither draw a pattern and password hacks/workarounds do not work at all. MiUI password does not work neither.
Any ideas?
That still doesn't decrypt /data any better than the official build. It just doesn't bother asking when it boots up. Look in /data/media/0 and you'll still find a load of jumbled/encrypted data. If you go to "mount" and press "decrypt /data" it still fails with same error as the official build ("failed to decrypt user 0").That's a pretty old version of TWRP, update to the latest "UNOFFICIAL"(but it works like a charm) build from the official developer.
To update watch this video.
ok now delete your account because your egsistence here is senselessif don't know how to do these things like root, flash custom roms, about data, stealing. i think stay on original miui.
The answer is yes, but with a lot of hassle in my experience. The reason it doesn't work at the moment is linked to the fact that TWRP (and other custom recoveries) can't decrypt /data on Android 12.Hello.
Is there any way to reinstall Magisk automatically after every update, please?
What are you talking about? There is already twrp with android 12/12.1 decryption fully working.WARNING: I soft bricked my phone trying this the first time and had to format /data to get it working again. Back everything up if you're going to try it.
The answer is yes, but with a lot of hassle in my experience. The reason it doesn't work at the moment is linked to the fact that TWRP (and other custom recoveries) can't decrypt /data on Android 12.
The solution is this fork of Magisk made for the very purpose of getting Magisk to survive OTA updates when recovery can't decrypt /data:
https://github.com/programminghoch10/Lygisk
WARNING 2: That fork only supports LineageOS Recovery. When I tried it with TWRP that's when I got the soft brick. I then wiped and reinstalled everything, including LineageOS Recovery, Lygisk and an older version of LineageOS 19.1. When I then updated LineageOS using the OTA updater, the update went fine and Lygisk survived the update OK too.
I don't think there is, or if there is then it's not very easy to find which is why that question was asked. The official build can't decrypt /data fully without deleting all lockscreen passwords and fingerprints. Neither can the unofficial one posted above. Which leads me to the question as politely as you're clearly capable of asking, what are YOU talking about?What are you talking about? There is already twrp with android 12/12.1 decryption fully working.
I've got LSPosed installed via Zygisk and it seems to work fine, athough I've only used one module so far (SIM number setter).Has anybody installed any Xposed framework under lineageOS 19.1? Any particular issues found?
I'm planning to upgrade from LineageOS 18.1 to 19.1 but wouldn't like to loose some (currently EdXposed) modules.
Just updated from 11 to 12 today via dirty flash and so far so good.
Here's what I did;
1. Downloaded latest version of MindTheGapps for 12L.
2. Downloaded TWRP-3.6.2-vayu-Nebrassy-03-07-22.img
3. Downloaded latest 19.1 LinageOS daily.
4. Extracted boot.img and created MagiscBoot image.
5. Removed lock from existing 18 linage. The nebrassy twrp can't decode android 11 for some reason (works on 12).
6. Reboot to Recovery
7. Flash nebrassy twrp and reboot to recovery
8. Flash LinageOS 19.1
9. Flash nebrassy twrp recovery
10. Flash magisc boot image
11. Flash MindTheGapps
12. Clear cache/dalvik
13. Reboot
After adding fingerprint and lock, twrp can decode.
And that's it. All my apps and data remained
Pass safety net, gpay working. Happy days
Someone asked?Thanks for finally releasing LineageOS, but you devs are 3 months too late... ArrowOS has inadvertently stolen my heart in your absence, lol.