I am very close to making the same decision. Ultimately the phone is usable, but the continuous annoyances are making me a little more disappointed and disengaged every day.
In my opinion this is a major issue for Fairphone, whose original mission was to develop a product that could be kept by customers for 5 years.
The problem described in this thread breaks that promise, which was one of the key points for which someone would pick a Fairphone over other more established manufacturers.
What a disappointment. This is ruining your reputation and reliability. I am so frustrated with the current situation. I tried your recommendations nothing worked. We are talking about basic stuff of modern technology, MUTLITASKING. I’ve patient for so long.. I am having FP4 for 4 years, at this point I am also considering switching to another brand.
Fairphone is taking this problem very serious.
They are testing in the beta-group. Which is a very complicated process. Because one doesn’t want a solution that breaks something else.
All I can ask for is patience.
@Fairphone_CM maybe you’d want to add a comment?
I am on fairphone 5 and getting this plus apps just stopping all the time. I switched to qobuz and thought the issue was them, but I am realising the timing lines up with all the other issues. Do you know how to raise a formal bug thing? Really frustrating!!
Cool. In which update is this fixed exactly?
Where is this already fixed?
hello, this is the topic for FP4
the topic for FP5 is here
I agree with @Dryhte that there is no need to raise a formal bug on this issue, as it has already been acknowledged and the Fairphone team has been working on that
Unfortunately, to clarify and respond to @atttze and @langhaarschneider , the fix has not been released yet.
We’re aware that it is being worked on by Fairphone, but we don’t know when the fix will be released (both for FP4 and for FP5 a fix is on the way).
My radio app just stops randomly. It stops and it deletes itself from the screen. Not the same it believe as what you describe
Since I updated to A15 end of last year, my phone has been borderline unusable at some points because of the app killing.
I waited patiently for this update, but since this doesn’t appear to address the issue, could we have a communication on whether or not the issue has been identified and is being worked on ?
After 4 month of a subpar experience with little to no communication from fairphone, I am sadly considering going another route. This goes against the whole reason I purchased this phone a few years ago, but I have my limits.
Beta testing looked very promising on this issue.
Looked meaning for this update?
Or meaning it’s still being worked at and a solution has been found but not yet enough tested and thus not yet available?
@Fairphone_CM thank you very much for the info and for the work to get this done. Finally some light at the horizon after ~3.5month of frustration. I got the update offered from 15.15.2 (rolled out by accident) to 15.16.1 and the update process itself went well.
On the old version my phone was “borderline unusable at some points because of the app killing” (as @Gdfphone said it nicely).
During the last ~36hrs on the new version I had the feeling that the phone became more reliable and its usability has improved. But the app killing has not been (fully) resolved.
E.g. my launcher seems to usually load quicker but still has to load certain things like widgets each time I go back to the launcher and re-index apps when I switch to the all apps list. Or my public transport check-in ticket app which should track my trip in the background still gets killed when I read stuff in other apps even though I am still on commute … I did not yet had a chance to try all the background apps where I had troubles with in the past like Spotify etc.
At least my corporate apps work again with the fresh security update level. Please be quicker with the next update, I really don’t want to get through this a 2nd time.
@Fairphone_CM Could you please officially acknowledge that this background app killing issue exists also for FP4, that you are working on a fix and on what timeline? (I see a potentially related fix was in the update for FP5, is this the same as for FP4 which you will port if it works there?) Thank you for building sustainable trust with open, fair and honest communication.
Thanks to all the community moderators (@Meaghan, @yvmuell …) here for your support too, however it is sometimes really difficult to draw conclusions out of your statements on updates/issues as it is usually not clear to me what is now based on actual facts/insights you got to know from FP directly or what is based on assumptions. Hence I would appreciate an official statement from FP.
Its not mentioned in the release notes and for the rest no one knows…
Hello
there has been an official acknowledgment of this issue by Community Manager.
Myself, as a community moderator, will not be providing any updates on behalf of the company, that is not how I see my role here. I am reading your words as a confirmation that you agree with that:)
Statements like these are really hard to interpret and it would be nice if you could clearly state whether these are just assumptions or to what degree this is based on beta test insights or other info:
E.g. do you know that was indeed not in the update or was it just not mentioned clearly in the release notes, could be that parts have been fixed and just not mentioned.
Well, there is always hope, but this does not bring us further here. This statement implies that you have insights, then please state them clearly, if not, please do so too. As you have the Community Mod label and some of you are part of beta test groups your statements kind of have a slightly higher credibility, but if you also just assume and hope, then imho we should know to not assume and hope too much. Thank you
yes, that was an actual factual statement - the fix for this specific issue has not been included in this update.
I think it is safe to assume that if something that major is not included in the release notes, it is not included in the software as well.
Now, I am not a beta tester and I refrain from sharing any official information which has not been made official yet. So please read my conclusion as an interpretation of the following
Sorry, but what it it now, a factual statement or an assumption? 
The only acknowledgment I find in this thread is that FP is gathering data, and somewhere else that they are looking into something related.
Imho a good, fair and sustainable way of communicating would be to also mention severe known issues in release notes potentially with an updated acknowledgment and roadmap, not just silence @Fairphone_CM
Apologies.
Fact: not included.
General suggestion: if something major is not mentioned in the release notes, it is not there.
I understand most of your comments are aimed at Lotte, so will not be responding more unless you tag me;-) just please note that these are not usual working hours for company reps:)