Just wanted to chime in and say, that setting apps to unrestricted has led to no significant improvement for me.
Whilst I do understand that this might (or might not) be an upstream issue I struggle to understand the decision to roll out an update with known flaws of this magnitude.
Just having an eye on it right now also really doesn’t solve the problem for the users, so I really hope this is one of the top priorities for fixes among the devs right now.
I really love my FP4 and the vision of FP in general, but right now this is not a device with which I want to work…
Dear Fairphone Community,
We’re still actively investigating this issue and gathering data. From what we’ve seen so far, this appears to be related to default Android 15 behavior and implementation of background app management, but we don’t have a final conclusion yet.
We don’t want to make any final statements or commitments until our investigation is complete and we have a clear picture of what can or can’t be improved. The feedback we receive is very valuable right now, it helps us understand the scope, patterns, and real-world impact.
Once we’ve drawn our conclusions, we’ll take appropriate action, whether that’s tuning the behavior or providing a fix if possible. If neither is feasible or necessary, we will be providing clear information and guidance on our website so users can make informed decisions.
Thank you, this is really unbearable. I cannot use my phone to login to 2FA protected websites and apps anymore. This really is a big deal for me.
To check from the other side, are there actually any users who are not affected at all? They would probably not be aware of this thread, however I think that might be interesting to know.
Could you please list your settings concerning the points mentioned above (battery settings and all that) and any other potentially relevant things (like rooted, fresh install and such)?
The point being to see if you have some special setting or if it’s just simple luck.
My FP4 ist not rooted, Nova Launcher is installed and it was the standard OTA update. I checked all the battery settings of the apps before I started the update, and there was just one app that had the background settings to “unlimited” (Fair Mail which requires it), the other apps had settings “optimized”. I cleared cache and data of NXTvision before the update.
No hassle after the update, all WiFi and Bluetooth Connections still working, mobile data and telephony OK.
The only thing I noticed was an increased battery consumption at the first day, but it’s ok now.
I also use Internet Radio inside the browser, and it doesn’t stop when it plays and I’m using another app.
I have Android 15 on my FP4 and it annoys the hell out of me.
If I do a longer Discord call with friends far away, after a random amount of time never over 1 hour, I get kicked from the call, because the app is killed in the background even though it was doing something (sending and receiving data from the call).
Same thing if I want to listen to an audiobook. I can do this for hours, or at least I would like to. The phone has other plans. It randomly kills Audible. But why? The app was playing audio. It wasn’t inactive.
Since ChatGPT just made up 8 different ways of fixing this with settings that don’t exist, I need help of good old natural intelligence.
So, if anyone could help: Greatly appreciated. I’ve long since given up on the FP support, as they simply never answer.
I have similar issues with my FP4 since the recent update. I noticed that when I run AccuBattery it showed a warning about this, with a link to Our mission | Don’t kill my app!
I’ve just installed the corresponding app, which is running a benchmark process that will complete in some time.
I’m a bit annoyed today because I lost most of my Strava recording for the ride I went on.
I mean if it was really just purely inactive background apps, that would be one thing.
But stopping background apps like Discord (while I’m in a call) or Audible (while it plays an audiobook) means it’s stopping active apps. That’s just plain stupid.
I created an account on this forum specifically for this issue and your post helped! Like other people, I couldn’t find the “secret” menu (yeah, I realise it may not be technically secret, but the user experience to reach that section is pretty weird).
Ever since the upgrade to Android 15 I’ve had Spotify randomly turn off, which was annoying, not to mention Discord being killed two seconds after switching to another page… How is this “battery optimisation” by the way? At least wait a few minutes before killing an app.. The effect is most likely the opposite of battery optimisation.
Its been like a whole month since I opted into this A15 update. As many have noted, apps keep randomly crashing, usually trigger when I open another app e.g Spotify is on. And I open another app which then shuts my Spotify.
Im relieved? Somewhat that others have it fine. But it seems to affect a significant portion of FP4 users.
How did this not get picked up during beta testing?
Where is the fairphone official response?
We dont care about the latest Android upgrades. We just want a functional phone that lasts a long time!
Im still pretty angry ; the phone is great but the software updates have a tendency to introduce more bugs than make the phone better. I still remember the A 12? update? That really borked the GUI until they ““quickpatched it 1-2 months later
I guess things like this usually happen during such big updates of major versions (and please note that FP skipped one major version completely in this case). Of course the valid question is, why did this not happen in the beta tests?
On the other hand, the background app handling has changed in A15 and in the beta tests it is hard to impossible IMO to rebuild every possible environment/setup. Still FP’s communication still has much room for improvement.
And not all seem to have such problems, probably the quiet majority is quite ok with the update. For example I do not have problems with this new behaviour as well as I did not have any problems with spontaneous reboots. So those problems or better their root causes always tend to be very individual and are hard to predict by the manufacturer beforehand.
In this case it is kind of an “invalid question” in the sense that it actually was reported during beta test.
I’m pretty sure that was mentioned earlier in this lengthy topic. Could be easily missed I guess.
To me this sounds somewhat similar to the fingerprint “degradation” of the FP3 with Android 13. Back then it was known there’s nothing to be done about it.
Here it seems to me the final conclusion hasn’t been reached yet. It could very well turn out to be a “it is what it is” situation.
Of course one could ask, why release so “early” when hope for a fix hasn’t been abandoned yet? Given that there are a couple of months left before support for A13 gets stopped. But then, waiting for releasing the major upgrade until the last possible moment also seems kind of risky to me. I’m undecided if I would choose the rock or the hard place to be honest. I’m still on A13 myself and I’m quite nervous how bad this will be for me when the day arrives. Reading the descriptions here sounds like a showstopper to me and I really fear I need to switch to a different phone in a worst case scenario.
