Came from FPOS with a clean install, everything went swimmingly, had to fiddle with the Magisk/Zygisk business for the banking apps but it worked out in the end.
I forgot a WhatsApp database export so last three months of convo are gone 
Tested: Wi-Fi, data connection, calls, bluetooth (for media but not calls), syncing, GPS.
Not tested: Bluetooth in call, NFC
2 Likes
Updated yesterday and as far as I can see everything is working perfectly and it even seems a bit more responsive than 21 (it may be a placebo though). I love this phone, so thank you very much for your work.
Just upgraded yesterday (microg for LOS) and overall everything seems to work fine. I just have two issues. One is that SafetyNet doesnât pass because it detects my unlocked bootloader. I thought I remembered this didnât happen on prior versions but by itself this doesnât seem to be a big problem so far.
The bigger issue is with Revolut, who now seem to block customs roms by virtue of looking for certain ro.build variables. See this thread for reference.
It worked fine before but since after the upgrade I need to log into the app again, I now canât anymore. There seems to be a known fix of changing those variables that make crdroid and grapheneOS work but that would need to be done for the LOS builds aswell and Iâm not sure how permanent of a fix this would be or if this will just turn into an eternal cat and mouse chase.
So for now I canât recommend anyone using Revolut to do any action, that may lead to them having to log in again, otherwise they may become locked out like me
1 Like
On FP3+ I have sucessfully relocked bootloader with LOS4microg. So @AtomToast you can resolve safetynet, but you will loose your data without a backup.
I was game to try that and then during the process it told me Iâd have to wipe my phone again 
Iâve only set it up again, I wonât bother
I just thought I remembered it passing safetynet with unlocked bootloader previously but itâs not that problematic really. I never had an issue with apps not working with an unlocked bootloader so far.
Also apparently from what I was able to gather, Revolut actually more aggressively bans phones with relocked bootloaders and is fine with unlocked bootloaders (something about yellow vs orange device status).
Unfortunately the only fix seems to be to build the rom with a different name, like how grapheneOS is doing it now.
Also I found two weird issues now after having used the update for a bit:
- pulling down the quick access menu from the top on the lockscreen and then pushing it back up leaves all notifications on my lockscreen semi-transparent
- sometimes the language of my quick access menu and specifically the pin unlock screen randomly changes to German (I have my whole phone in English but have set German as a secondary language). This just persists for some time and at some point also seems to switch back to English on its own. Itâs very bizarre and I have no clue what causes it
Hello, I dirty flashed the microG version 22.1 it worked well, thank you so much - but unfortunately now my patched Play-Store which I flashed via Magisk (the december 24 version from FriendlyNeighbourhoodShane) crashes. MicroG works well, all boxes are checked. And on my tablet after the update to LOS MicroG 22.1 the playstore worked fine. Has anyone had the same problem with FP3 - or any idea what went wrong?
Since updating my FP3 to 22.1, it stops charging at night (stops between 50% and 70%)
It wonât continue charging on its own.
My settings:
- Alarm: 8:15
- Charging control: activated
- Charging mode: automatic schedule
When I unplug the charger and replug it, it continues charging again.
Why dirty flash? Also be clear please you have LOS4microg 21 and flashed LOS 22.1?
no I fashed LOS4migrog 22.1, but yes I did a dirty flash I found no remark that this wonât work
Dirty flash is not raccomanded, but if you are licky is without issue. Since official LOS have added recenlty (finally) a patch to correct handle microg, I have suppose that you have installed LOS.
I was thinking about upgrade LOS4microg 21 to LOS 22.1 since there is no reason to have LOS4microg, but for avoid dirty flash I will remain to LOS4microg untill remain mantained.
Did an install a week ago and itâs like I have a brand new phone! My banking app even likes the fingerprintsensor.
Only problem was the use of GooglePay. It was complaining about my phone being rooted (it wasnât) but fixed it by, well⌠rooting it with Magisk and install some fix adon.
1 Like
I had that on my backup FP3, too. While it was plugged in, it was turned turned off. When I turned it on, Android showed a 99% charge. Go figureâŚ
1 Like
Nope, still doesnât work for me.
A small question regarding the Battery Information in LOS/Android.
Does this thing work? It always displays that my Battery has 100% of its initial capacity. Well i always try to take good care of my battery⌠aka let it stay always between 20% and 80% if possible and so on.
But⌠the battery is 5 years old⌠thatâs why i donât think thin the Info which is displayed here is correct XD
1 Like
100% here too compared to initial capacity
To determine the capacity of the battery, it must be completely discharged from time to time and then charged to 100%.
2 Likes
Update from last week broke my Hotspot/tethering, an device-independant bug. Update today did not fix this.
This temp fix worked for me:
1)check if persist img is corrupted
open dialer and call # #4636 (closed)##
check âwifi statusâ and press ârefreshâ if the mac adress is legit (sequence of numbers and letters) than follow -step 2-
if it showing â02:00:00:00:00:00â it means persist.img is corrupted {flash stock persist.img(not recommended)}
2)connect your pc and phone and execute this command
âadb shell settings put global tether_offload_disabled 1â
and then
âadb rebootâ
this will fix the issue 99% , if you fall into 1% its the kernel or your persist.img is corrupted.
are you saying the issue appeared on March 5th build and that is not present on older builds?
Not sure but that is what I think.