FP6 Restart the phone to load the corresponding configuration - 15.148.0 - US/Canada

I’m in West GTA. When I’m home there are no issues. When I go out, whether in a car or transit, my FP6 occasionally restarts. Sometimes it does’t. Other times it restarts once or twice per trip. It’s not unusable but it can be bad if you’re in a pickle when you really nees your phone and it ends up restarting on you.

Still happening on Android 16.

I’ve also been having random crashes, especially when I’m using location services and data and I got in and out of a service area (i.e. going through a tunnel or in the subway) which leads me to believe it’s the modem or GPS, and…I would’t be surprised ‘cause modem’s where most of the bugs are ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯. I can try and check if there are any tombstones that could provide more info.

Hi @Paupau, welcome to the forum. Are you by any chance located in North America/outside Europe?

Are you running Android or e/OS? What is your software version?

Hi @kwasow! Yups, I’m in California.

I now have Android 16 (FP6.QREL.16.48.0)

I’ve moved your post to the topic, where the issue is tracked. You can try disabling location accuracy under Settings > Location > Location services as this seems to reduce the issue.

You can also read through this thread to see if there is anything relevant to you, or any additional info you think is important, but hasn’t been mentioned yet.

Hi, is this still happening to anyone? I recently travelled to Canada and it’s been happening a lot for me. Maybe it will settle now

It was still happening for me until I got FP6.QREL.16.69.0. I’m in the beta & I think this build finally resolves it but I need a few more road trips to confirm it. Its a strange bug because it only happens when data comes in (text, & calls close together) after a location change. It seems that the tower changes & then location data is pulled & then phone either slows down to a crawl & you manually reboot or a reboot is triggered. That slowdown seems to be what triigers it & that lag is what’s gone so far, again still testing.

Nope, still broken for me even with the update. Went a whole day before it rebooted though.

New to the forum but I’m having this issue on my /e/OS FP6 on Koodo (Telus) in eastern Canada (PEI/NB), and I think I might be able to add some context I don’t see in the thread, in case it helps with troubleshooting.

On my phone, I’m using it doing whatever (no pattern, happens randomly, on WiFi or 4G/5G) when I get a system message saying something like “Region changed to EU, rebooting to reload new configuration.” Then immediately get the same message, before the reboot, with US instead of EU, and then the phone reboots. That had been happening maybe once a week - I would see the messages if I was using the phone at the time, but the phone also rebooted sometimes when I wasn’t using it.

Today my phone has rebooted 4 or 5 times since I woke up about 6 hours ago. Yesterday I installed CellMapper, an app that detects and uploads cell tower locations to a public database, which uses location in the background pretty frequently. I’m thinking now maybe the phone is getting an occasional bad location from the GPS and forcing a reboot based on the wrong location, but it hasn’t happened enough times yet to see if the region change messages always coincide with a GPS lookup.

If anyone has any suggestions, I’m happy to try whatever if it helps with troubleshooting. More info that might be relevant:

OS version: /e/OS 3.7.3-a15-20260506618655-official-FP6
Build number: BP1A.250505.005

Cheers!

Hi, thanks for your input and welcome to the Fairphone community forum :slight_smile:

As you will know from reading this topic, this problem has been associated with the use of location services, so the first thing to do would be to disable Location. Of course, that also explains why you have been experiencing reboots more frequently since you installed CellMapper, which needs location to log the position of cell towers.

Another option is to turn off Location Accuracy, while leaving Location on. I mention both, because Location is quicker to turn off/on, but it seems that you can leave Location on if you just turn of accuracy. Opinions and findings differ.

A more detailed account is offered here:

Clearing the Google services cache seems important.

It’s important to remember that the majority of users posting in this topic will be using the stock Fairphone Android, and not /e/OS. It’s important to distinguish the two groups, as both /e/ and Fairphone have been working on the problem.

Fairphone released a corrective patch in November, but this didn’t immediately alleviate the problem for all users. Probably clearing that cache would have helped.

As far as I can gather (e.g. from this thread in the Murena forum), work is still continuing for /e/.
I recommend you follow things over in the Murena forum.

And I just had it reboot twice. I was driving at the time so I didn’t see the screen when it happened, but I suspect it’s the same Location Accuracy issue we had before. In the latest Android 15 release, I had Location Accuracy turned on and it was stable, but considering we are seeing other regressions (the android auto one at least) I suspect we’re seeing another one with the location accuracy.

(I have now turned off Location Accuracy again just to be safe)

The issue wasnt fixed for everyone, moving your comment to the topic.

I bought my phone in Germany and so have a 5G SIM Card from Simplytel. The problem did not appear.

Right now I’m traveling the US andsid aquire an eSIM from etravelsim. As soon as I get into areas with a bad reception (which is happening in the US quite a lot and more then I expected) the issue occurs. In the middle of taking a picture or navigating with Google maps the message appears, just for a very short time, most of the time I’m not able to read it fully and it does the restart. Most of the time it is then more than one reboot, as if one wrong config is being updated and a short time after a better one…

Anyways, putting it to flight more while navigating helps to keep it from rebooted, but this is just solving it for now. Still need a fix.

My os version. Is android 16 patch from 5th of May