Reboots after A15 upgrade

There is no commonality for why but my FP4 randomly reboots multiple times in a day since the upgrade to Android 15 (A15)

I saw that FP’s troubleshoot guide suggests it could be an app that causes random reboots - but that’s unrelated to a major software update like A15 - and as said, there is no common thread as to which apps I use / recently used / recently closed etc before a reboot happens

It often also happens within minutes of the phone being turned on after being turned off - or coming out of ‘bedtime mode’ in the morning before I’ve opened any app

I’ve emailed support@fairphone multiple times but had no response

I assumed it would be a known issues with A15 given how frequently the reboots happen but I’m surprised to see no topic relating to this on the forum… which makes me wonder whether it is isolated to my phone…

Anyone else had the same?

There is currently a strong suspicion that the A15 update has some incompatibility with the Android graphics driver. For several users the reboots stopped after going into Settings > Display > Visual Enhancement: There you see in the middle an item “Screen Color” with 3 choices: Vivid, Natural, and Advanced. Apparently the dangerous choice is “Advanced”. “Vivid” and “Natural” should be safe, at least people who switched to one of those reported that the reboots had stopped. (I don’t know the specifics, I’m still on A13)

Support is totally overloaded (always was). Don’t expect any answer before next year.

Like this one?

1 Like

Thank you!! That does seem to be the issue… As soon as I tapped “Display” I got a system error pop up mentioning some kind of system UI app keeps stopping…didn’t grab a screenshot… But it offered the usual “wait” or “close app” - I chose close app and tried again and now I can’t access the Display settings… I’ll keep trying!

All the best,

Tim

In fact it’s the visual enhancement item that causes the crash - and this time I managed to get a screenshot of NXTVISION app pop up - seems this is the issue?

Try the following steps:

Thanks for the suggestion, I tried that two days ago but I’m still experiencing reboots as usual. (in fact, I feel like they got more frequent - it rebooted 3 times in a row, for the first time, shortly after turning on Eye Comfort Mode)

Hi,
maybe it’s worth a try to turn off all settings under advanced and set screen color to natural.
greets Robert

I have also tried clearing all my NXTVision data, updating and restarting.

The only thing that seems to make my phone “usable” is to remove both the SD and SIM cards. Not terribly usable as a phone, though.

For what it’s worth, my phone restarts so aggressively it’s possible it doesn’t even complete the “Phone is starting” phase of booting up before restarting.

Hi. This is all to complicated. For me anyway

I had this issue too. A restart every day. On some days two or more. That occurred excatly with upgrading to Android 15. Very annoying, started grunting Fairphone. Submitted ticket, no reply. This hint here solved the problem indeed. Another observation is that the home screen now starts displaying faster than after the Android 15 upgrade. During that time it seemed like the lauch app hesitates to start. Now good. Thanks for posting the hint!

1 Like

I try to help somebody as a Fairphone Angel, but I am stuck.
It’s impossible to change the Screen Color in NXTVISION as Visual Enhancement is grey instead of black (see the screenshot in Dutch).
(Eyecomfortmodus set to off makes no difference.)
Who has an idea to make Screen Color changeable?

Hi Lidwien,

Switch off “oogcomfortmodus”, after that the setting you want to change is accessible

Greets Robert

2 Likes

I did that butthat makes no difference, it stays unaccessible.

Maybe it would help to stop NXTvision and clear cache and data once more?

1 Like

No! Already have done that. Several times

Same here; sudden reboots, NXTvision app keeps crashing and I’m not even able to access the Visual Enhancement section.

(side issue is that there’s suggested apps om my homescreen now that I can’t get rid of)

So I guess, if all the possible workarounds do not work there is only one thing left: A fresh install from scratch (with a backup prior to this, of course)