I donāt have an activated search bar and Iām also using the Nova Launcher. I can see what can be found in the settings and try it.
Iāve used it a few times since the upgrade, and I havenāt found any problems so far.
Will it be possible to stay with Android 13 and get continued security updates for it?
Searchbar was enabled in the settings. had now deactivated them and will see how the phone behaves now.
No. Fairphone only updates the latest Android version per phone.
Hi,
I am (was) A13 beta tester on the FP4.
I see no update available for A15 in the settings.
Iām on Orange F.
When you are still beta tester, kindly check this in the beta group.
I think there were some issues with Orange network after this update, with suggestions to stop the update
Other than that, please double check with your beta tester group as suggested:)
As said if still beta, this has to be adressed in the beta group, as the IMEI still might need to be reassigned.
I doubt that the roll out was stopped, however we should not speculate and clarify first in the beta program.
Edit: and even if @chantoine you cancelled beta for this device, it might still need some intervention from the teamā¦
And even if they did continue security updates for Android 13 for now, the Android 13 base will stop getting security updates from Google early 2026, if prior Android versions are any indication.
So even in theory this would not be a path forward for long.
Sorry to say this, but after the update I have a serious stability issue. Not only QuickSetp crashes all the time (mentioned previously), I also randomly get restarts either on operations I do (sometimes just starting an app) to bluetooth connections. It renders the phone really entirely useless.
Can I downgrade w/o using my data???
If your bootloader is not alteady unlocked, no
Reg the Quickstep issue, see the workaround here
And reg the rebooting, see here when you are in Germanyā¦
To further understand the root causes, it would be good to add important info to the respective topics.
https://xdaforums.com/t/app-2-2-11-dec-2022-v3-1-betterbatterystats.1179809/post-90077289
@BBS
The latest version is 3.4.0-525. It most likely will not work on A14 and after. The dev made an announcement a long time back that he is still working on it. But I donāt know of any recent forks or mods.
Yes I knew that there might be problems with Android >14. Still I havenāt found any decent replacement that extracts the battery usage of wakelocks so well as BBS did. I am open for any idea ![]()
The support bot suggested the following to stabilize Android Auto:
-
Go to Settings ā System ā Developer options -
Disable "Force Desktop Mode"
Actually, I doubt this will help, but I will try and report here.
In parallel I opened a support ticket for the issue.
this helped with specific issues on the FP5 after A15 upgrade
I just tried it again after disabling the option āForce Desktop Modeā and cleaning the cache of Google Play Services and Android Auto.
It seems to work, now. At least in my short test ![]()
Too bad. :-/
Tried that - impossible because it crashes immediate when I try to switch, after reboot its not disabled.
Thanks for the hint! If I have news that might be helpful, does it make sense to post them here?
(Net Operator: 1&1, Location: Germany.)
Is there any crash-log / core dump created that I can send to the dev team to investigate? Might be a simple fix⦠missing NULL pointer check at that line of code or alikeā¦
By default, this option is not on, right?