That’s a shame, I hope it was fixed for Android 16. I don’t have the issues with things not installing and backing up, but I’m deeply annoyed that I can’t even reliably copy/paste text within two apps without them reinitialising. Hope it gets fixed soon, thanks for everyone who dove into this ![]()
Booking summer flights for next year, I had to redo the process twice, because of needed app swapping.
No… this Batterie managament thing does jack regarding this problem. ![]()
Me too. Battery Manager.
That’s really strange. I tried that a while ago. Without success. Now I’ve turned Battery Manager off again and set the battery optimisation for the launcher (total launcher) to “unrestricted”. And the problems seem to have disappeared. That doesn’t necessarily mean there’s a connection. But it seems to have changed something in the system. A few days ago, I reset the launcher back to “optimised” and it continues to work. Battery consumption has also decreased slightly overall.
Hopefully it will stay that way.
No it is definetely not something A15 related. It’s FP’s (or the ODM’s) implementation of Android. No way that Google woud get away with an Android Version that is killing all major music apps while playing. Also I have never heard such a thing from other phones.
And for me it started already on A14 (and for several others as well). I would therefore rather merge this thread (or at least link it) to the spotify-thread and the “switching apps” you closed lately @yvmuell . I agree the threads are more or less duplicates, but closing the first/most extensive one doesn’t seem a good idea to me.
I tried both things as well, but no real change. I even used another launcher before, but it was so bad in terms of bugs that I came back to Quickstep which is snappy at least…
This memory bug is terribly annoying in daily life. I hope the dev team gets it fixed (as well as tiny other things like the VOLTE notification which is still there)
Same here. Since A15 update apps get killed in background. It’s 10th of November now and this problem is still not solved.
I often use 2FA but can’t do it now because the apps after switching back are restarting.
While driving with Android Auto I’ve noticed that the system killed my music app twice during short time. Android Auto restarted it automatically.
In my household only I have a Fairphone and only I got this problem. I’m starting regretting buying this phone, even though I’m standing behind the policy, but what can I do if the phone is almost not usable?
Hi and welcome to the community forum ![]()
Even though Fairphone have already commented above, you can open a ticket with official Support and thus possibly contribute useful information for resolving the problem.
Just a data point or two that I have not had this problem of apps being killed in the background, not in A14 or now in A15 (upgraded two weeks ago). I did disabled many unneeded apps using adb when first got the phone (sorry, don’t have the list now), and have also set the screen refresh rate to 60Hz. My wife’s FP5 is still running A14, and she does not have the problem either (though I did the same initial setup to her phone too). One thing that DOES happen in FP5 running A15 is that Vivaldi browser sometimes reboots. Not often, but still probably related to the problems reported here. Hope this helps.
Just wanted to chip in and confirm that I’m seeing the exact behaviour described here happening on my FP4.
On A15, I can only use one or two apps simultaneously before all other (background) apps (including my third-party launcher) inevitably get killed within seconds of “inactivity”. This has NOT been an issue for me on A13, which, I believe, was the version my phone was on before (IIRC A14 was skipped).
This issue makes using music apps, banking apps, 2FA apps and to some extent even browser apps an incredibly anxious experience as I have to keep one of them in the foreground or switch between them quick enough so the process(es) won’t get killed. Suffice it to say; background media playback on this Android version is utterly worthless.
I truly hope the Fairphone team has been looking into this issue, as this update was only rolled out to me (a FP4 user) a few days ago, but FP5 users have apparently been experiencing this for at least two months already. A fix for this is long overdue.
Hi and welcome to the community forum ![]()
We are in a FP5 topic here so I suggest you look for one about FP4 that’s about your background apps problems. Have a look around. If you spot one then we can move the conversation over.
Otherwise we’ll start a new topic because it’s likely there will be similar cases.
In the mean time it’s important to inform official FP Support of your problem. https://support.fairphone.com
Thanks