Thanks @mpolito1969 for taking the initiative to already start a topic. Much appreciated! Apologies that I was a bit slow on publishing the release notes yesterday.
So, let’s increase visibility, shall we … moved into its own topic from here.
And if anybody else could please set the #softwareupdate tag … I can’t.
While this update seems to be working fine, I just want to report in, that after updated my FP3 to Android 11 the phone won’t bring the mobile data link up after booting: switching the airplane mode on/off fixes the issue after each boot (country: Finland, carrier: Elisa).
Hi, I have a serious issue with NFC following this update. I use The Freestyle Libre app to scan the blood glucose monitor on my arm to manage my diabetes.
Unfortunately now whenever I scan my sensor, it does a long beep and says it failed to scan. Nothing else has changed and I am seriously stuck.
This is a requirement for my healthcare. Can I revert the upgrade to the previous which worked fine?
Before you downgrade which means a complete reset of your phone, have you restarted the phone,did you try to disable NFC and reenable, with restart oft the phone inbetween? Can you somehoe reset the connection of phone and Freestyle Libre? Is there any other way to connect the devices?
Is it expected for widgets/shortcuts to disappear after updates? I had a bunch of links to google maps addresses on one my screens which all disappeared after the update?
Known, yes. But being worked on? I doubt it, because when I reported it to support they wanted me to reset to factory settings which I refuse to do if it’s just a stab in the dark.
I disabled Digital Wellbeing recently to see if that helps and have successfully rebooted twice so far.
Thanks for your link to the other report of the same issue. I have done a cold restart of the phone, also have stopped and restarted the LibreLink and the NFC apps, to no avail. I also had an old unused sensor that I stuck on my other arm and attempted to twin with the app, but again the same scan error. As @ralfberlin says in the other thread, an NFC service component is likely at fault since the update. I have logged it with FF support, who are now asking me to prove that I own the phone…
Whatever, it seems that I shall have to do the reset/downgrade later today, because I have very few finger-prick tests with me.
A “reset” does that mean a reset to factory settings? So going up no data is lost (over the air), but going down a version means losing everything which is not back up at Google??
Yes with reset I meant a factory reset. When you manually flash something (up or down) and your bootloader isnt unlocked already all data will be wiped. When your bootloader is unlocked, normally an upgrade will not cause data loss, however a downgrade would normally cause a data loss. Having good back-up is always a good idea
Same here, neither BT-Headphone-controlls are working nor the controls from the car. That is completely broken.
However, for some of us changing the AVRCP-Version back to 1.4 (within Developers Options) might help (source: Fehlende Titelanzeige bei Bluetooth Verbindung im Auto – Android-Hilfe.de). Doesn’t work for me. Just a hint here: The issues of Android 11 with BT-Connections is know since 2020. Proof: ibid.
