This as an overview of all threads covering the issue, that FP is killing background apps very aggressively (2FA impossible). Including music playback/GPS-tracking apps and alternative launchers.
I’ve decided to create a quick overview because I have seen multiple topics coming up over the last year which are IMO all related to the same issue. Also the same workarounds have been suggested over and over again. But at least as far as I’ve seen there is no sustainable solution. The intensity of the problem just varies over time as it very much depends on the history of used apps/background tasks etc.
My personal experience is that:
- Killing music players while playing music is something very much unique to FP
- Unloading the browser so you cannot even access the 2FA app quickly is also not common on phones other than FP
- 3 out of 7 threads were started even before Android 15 was released for FP5. So A15 might have worsened the issue, but it is not the origin of the problem.
- Not any battery-optimization setting nor developer options help solving this problem for good. It’s just the intensity of the problem that is fluctuating.
[AI generated:]
Threads started before July 2025 (A15 release date for FP5):
| Thread Title | Start Date |
|---|---|
| Spotify playback stopping and disappearing from notification tab | February 24, 2025 |
| WhatsApp voice message stopping playback when leaving app | February 21, 2025 |
| Apps reloading when switching apps | January 16, 2025 |
Threads started after July 2025:
-
Spotify stops music often when I open new apps or when I get a notification (August 8, 2025)
-
Spotify is crashing if I get a WhatsApp notification (October 2025)
-
FP5: Android 15 killing background apps more aggressively (August 14, 2025)
-
FP4: Android 15 background apps being killed more aggressively (November 10, 2025)
The things I have not tried yet:
- Rooting the phone and changing system parameters with Magisk.
- Alternative ROMs
- Complete Factory reset
I still hope that Fairphone gets it’s software developers (maybe at T²Mobile) to fix the issue, although I doubt it.