EDIT: I bought my FP6 through Clove Technology, so I do NOT have Murena OS
Fair phone 6, T-Mobile, USA
So I’m having the same “phone must restart to load corresponding configuration”
I’ve factory reset my phone 3 times and it still involuntarily restarts. I have noticed that low battery seems to make it restart less but I’m not sure if that’s coincidence or not.
Another thing to note, I’ve used multiple other launchers. But when the phone restarts it always resorts back to the quickstep launcher. And even Quickstep launcher crashes.
That might be quite significant info because Murena as the only company to sell the Fairphone in the USA “natively” declares the Murena Fairphone (Gen. 6) “Compatible with T-Mobile and its MVNOs”. Murena has its own USA beta tester group for the Fairphone 6, so they will definitely have to take the current restart issue into account with their /e/OS development for the FP6.
I would assume right now the Murena FP6 in the USA probably does not suffer from this issue yet, but given Murena gets firmware patches from Fairphone to weave into their /e/OS, Murena will have to find a way to deal with this one way or the other.
1 Like
To be fair the whole compatibility issue in general (not in this specific case) is more on the side of network operators in the US than Fairphone. I use a European SIM card that has roaming in the US included in its price plan and the phone works (well, worked…) just fine on T-Mobile, Verizon and at&t, including features like volte and vowifi.
Edit:
That said I now more and more believe this will end of being something super small like them having forgotten to include a small thing that includes the phone’s North American certifications (like it will look for the FCC ID, not find it, realize it is not supposed to be on this network in that case and reboot). Which would still be annoying but at least sounds like this could be a very simple push. I still hope someone with a Fairphone from Europe who has this update travels to the US or Canada and complains that their phone keeps restarting ever since they landed.
I can’t post on the other Thread about the Reboot issue that is affecting many users. Any updates if the issue has been identified?
FP will never ever be so fast to find a solution within 24h and post it here
1 Like
Where would they post the solution? I mean, are we supposed to be without our phones for days or weeks?
That’s so weird! Mine’s been up now for 3:10 which is WAY longer than it has ever managed to stay up and all I’ve done is disabled bluetooth. This is starting to feel like a very strange bug… I’m hoping the Fairphone techs aren’t as confused as we are, otherwise we might be waiting for a while for a fix. 
1 Like
I doubt there will be any hotfix for a market they dont support really so I guess def weeks and where or if they post, you never know…
Phone works “fine” otherwise though? I could live without bluetooth over not being able to use mobile data for “a while” 
Probably not an option for most, but given that Murena’s most recent /e/OS version 3.1.4. has a security patch level of September, 1st 2025, it should be possible to install it on the Fairphone 6 even after this Android OS 15.148.0 update (SPL August, 5th). If anyone wants to try (not for beginners): Info about Fairphone The Fairphone (Gen. 6) - FP6
1 Like
Otherwise it’s completely normal. It’s been up for 3:42 minutes now. That’s no guarantee that it’s actually not going to restart, but ‘s a lot better.
Personally, considering that music is my life, not having Bluetooth suuuuuuuuucks so I’m hoping they fix it ASAP otherwise I’m gonna need to get a new phone and that is going to destroy my soul.
1 Like
Probably a “at least I can make calls now” option for some but I would argue most of us bought the phone from Europe for the specific reason of not having to go through a “patch this, adb that” purgatory just to use Google Maps or watch YouTube videos 
Oh, Look! It says right there!!
”The unnecessary reboots happening with 3.1.3 in North America have been fixed and the device now passes FCC certification.”
There you have it! Murena’s fixed it! Not it is time for Fairphone to fix it.
It seems on reddit someone from FP at least posted to say “we are looking into it…”
2 Likes
You might be right. If you look at e/OS Murena’s latest security patch, is reads, “The unnecessary reboots happening with 3.1.3 in North America have been fixed and the device now passes FCC certification.” So it seem Murena had the same issue, and they fixed it.
2 Likes
To clarify for those not familiar with it:
/e/OS is a Custom ROM, an alternative operating system (also based on the Android AOSP core) available for all Fairphone since the FP2. Only Fairphone’s default “Android OS” is certified by Google for the highest degree of compatibility with apps.
4 Likes
@anon76468197 Why not mention that part of the update includes a location check? This check makes phones in North America useless by causing the lack of FCC certification to put the devices in an endless reboot loop.
Kindly stop posting over and over again in the general update topic and use the topic about the bug here for this
2 Likes
Coming here from /e/OS
The issue is not totally fixed. Several of us are still experiencing the issue.
Ticket here: FP 6 v3.1.3 build random reboot when user travels between US and EU (#8895) · Issues · e / Backlog · GitLab
But this is interesting that the issue is happening on stock as well now.
I found out you can prevent the reboots by disabling location services, which has helped others too. See if that works. No GPS is no fun but it will probably stop the reboots.
7 Likes
Seven hours, fifteen minutes without a restart! Damn I miss my headphones, but this is still way better than rebooting constantly.
1 Like