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.
Hi,
I am experiencing the same problem since a few weeks. Anything that needs switching apps is not working. I basically can’t log in or pay anywhere because I need to go to the authenticator app and back. And that is not working!
Also, spotify just closes when I switch tabs…
Anyway, just to mention something that I changed recently to narrow things down for troubleshooting maybe:
I recently created a new profile and I am using a second SIM (esim) that I am using for the second profile (for work). I thought it might have been related to this, but reading this thread, it seems to be a general problem.
So, a question for all the other people experiencing this: Do you have second profiles or second SIM cards?
Cheers,
Marcel
Hello Marcel
I have a second eSIM but no second profile.
Plus I don’t really experience the issue as described. Like my Spotify stops from time to time but that’s all. I can do payments and switching between the apps.
I changed the launcher to pear and it helped with some of the recent app issues I had before. I have also experienced some issues with 3-button navigation not working but it got improved and I no longer notice that.
I finally gave up on my fp5 after yet another update came and went with no fix, and bought a Nothing Phone 3. None of the issues that I’d had with my FP5 since the Android 15 update (background apps getting killed, GPS going bad until a reboot) are just an Android 15 issue, it’s just a Fairphone issue.
Well, while my background apps are not being killed, the latest October update did not fix the infrequent crashing of the Vivaldi browser either. And the latest update did turn off the default haptic feedback of the fingerprint sensor (only possible to turn back on if ALL haptics are active, go figure why). Feels like communication between the coders and the FP could be better..
Another case of this issue here. Interestingly my phone doesn’t seem to close apps playing media, but anything else is fair game. Even if I switch from browser to banking app for 10 seconds, the browser will reload. Battery Manager is switched off.
how can I possibly recommend the fairphone if the experience is so horrible right now.
I can’t switch to my two factor auth code app sometimes cause by the time I get the code, the original app i needed it for was already killed… how…
I’ve changed a developer setting and so far it seems to have stop the issue.
Changed “Suspend execution for cached apps” from “Default” to “Disabled”.
Will report back on how well it goes.
Thanks, apps seem to switch much quicker now, I’ll see how it goes.
Was curious to see what my setting was as I hardly have any issues with apps being killed. It was default on my phone.
I doubt it’s the true issue.
I had a good look through developer setting trying to think what could impact it. Background apps are in a way cached so thought changing it could help and it seems too.
It does make me wonder what it causing it. It seems to be sporadic. Something somewhere seems be making that default become a true instead of false.