THIS!!! I turned off location services and I haven’t had a restart in hours! The longest time in 3 days. >:(
I have on WiFi, Bluetooth, and NFC, just an FYI.
Absolutely not an acceptable permanent fix but it’ll have do in the meantime.
3 Likes
I mean.. yay-ish? This is the longest I’ve used the phone without airplane mode on since the update.
I guess I’ll just go places I know how to get to until the next update. 
2 Likes
For what it’s worth, I have been using Bluetooth connectivity constantly today to take wifi / VoIP calls (Teams) with no forced reset (airplane mode on).
Have now turned off airplane mode and toggled off location services. Let’s see.
Also, a FP employee contacted me to request logs. Looks like they are taking this seriously. I’m quite appreciative.
Edit: 3 hours later and no forced reset has occured. Seems to endorse the ‘turn off location services’ solution
6 Likes
I ordered my Fairphone from Clove a few days ago and it’s due to arrive some time next Monday.
If the bug isn’t fixed till then, what are some things I should avoid doing when I get my phone so I don’t get stuck in a reboot loop?
I am on the Freedom Mobile network in Canada.
1 Like
Your phone should’ve been in their storage for some time. If it offers a device update during setup and it allows you to “skip for now”, do that. 
4 Likes
A new thing. I turned Location Services back on but switched off “Location Accuracy” in “Location Services” - basically all location heavy apps tell me that is a terrible choice, but will mostly work after they made that point (and they got a GPS lock). Bluetooth, WiFi and dual SIM are on. Current up time is 10 minutes after turning Location Accuracy on just to see what would happen after a reboot (it immediately went into a reboot). This setting can be turned off while in airplane mode for those who experience “faster” loops.
5 Likes
I am following what your lead and doing the same. So far no reboots with location accuracy turned off.
Disabled the GPS (and in battery saver), and I have 12 hour uptime.
2 Likes
I guess I’m lucky. No issue with mine on PlussMobil here in Norway. I have VoLTE and WiFi calling turned off. I also had to set carrier info for data and mms manually.No idea if that’s what saved me.
I’ll definitely postpone any future updates until I’ve seen peoples reactions in the forums
1 Like
I turned off Location Accuracy and it stayed up for 9h.
Before that it was rebooting either 1-5 mins or stayed up for almost an hour.
19:2025-10-02 18:17:46 SYSTEM_BOOT (text, 479 bytes)
20:2025-10-02 19:10:14 SYSTEM_BOOT (text, 479 bytes)
21:2025-10-02 19:31:22 SYSTEM_BOOT (text, 479 bytes)
22:2025-10-02 19:34:48 SYSTEM_BOOT (text, 479 bytes)
25:2025-10-02 19:42:04 SYSTEM_BOOT (text, 479 bytes)
26:2025-10-02 19:42:49 SYSTEM_BOOT (text, 479 bytes)
27:2025-10-02 19:48:32 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 28470 bytes)
28:2025-10-02 19:48:32 SYSTEM_TOMBSTONE (compressed text, 10812 bytes)
29:2025-10-02 19:48:46 SYSTEM_BOOT (text, 479 bytes)
30:2025-10-02 19:49:41 SYSTEM_BOOT (text, 479 bytes)
31:2025-10-02 20:03:37 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 28567 bytes)
32:2025-10-02 20:03:37 SYSTEM_TOMBSTONE (compressed text, 10821 bytes)
33:2025-10-02 20:05:55 SYSTEM_BOOT (text, 479 bytes)
34:2025-10-02 20:14:15 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 28652 bytes)
35:2025-10-02 20:14:15 SYSTEM_TOMBSTONE (compressed text, 10761 bytes)
36:2025-10-02 20:14:31 SYSTEM_BOOT (text, 479 bytes)
37:2025-10-02 20:15:05 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 28551 bytes)
38:2025-10-02 20:15:05 SYSTEM_TOMBSTONE (compressed text, 10760 bytes)
39:2025-10-02 20:15:05 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 60965 bytes)
40:2025-10-02 20:15:05 SYSTEM_TOMBSTONE (compressed text, 10031 bytes)
41:2025-10-02 20:15:22 SYSTEM_BOOT (text, 479 bytes)
42:2025-10-02 20:19:48 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 28569 bytes)
43:2025-10-02 20:19:48 SYSTEM_TOMBSTONE (compressed text, 10779 bytes)
44:2025-10-02 20:20:05 SYSTEM_BOOT (text, 479 bytes)
45:2025-10-02 20:20:40 SYSTEM_TOMBSTONE_PROTO_WITH_HEADERS (compressed data, 28619 bytes)
46:2025-10-02 20:20:40 SYSTEM_TOMBSTONE (compressed text, 10750 bytes)
47:2025-10-02 20:20:56 SYSTEM_BOOT (text, 479 bytes)
48:2025-10-02 20:26:02 SYSTEM_BOOT (text, 479 bytes)
49:2025-10-02 20:26:52 SYSTEM_BOOT (text, 479 bytes)
50:2025-10-02 20:37:41 SYSTEM_BOOT (text, 479 bytes)
51:2025-10-02 20:38:32 SYSTEM_BOOT (text, 479 bytes)
52:2025-10-02 20:43:53 SYSTEM_BOOT (text, 479 bytes)
53:2025-10-02 20:45:27 SYSTEM_BOOT (text, 479 bytes)
54:2025-10-02 20:55:56 SYSTEM_BOOT (text, 479 bytes)
55:2025-10-02 20:57:00 SYSTEM_BOOT (text, 479 bytes)
56:2025-10-02 21:01:50 SYSTEM_BOOT (text, 479 bytes)
57:2025-10-02 21:04:05 SYSTEM_BOOT (text, 479 bytes)
58:2025-10-02 21:15:28 SYSTEM_BOOT (text, 479 bytes)
59:2025-10-02 22:13:28 SYSTEM_BOOT (text, 479 bytes)
60:2025-10-02 22:25:35 SYSTEM_BOOT (text, 479 bytes)
I turned the location accuracy back on while hooked up to my laptop and so far it’s up for additional 22 mins.
2 Likes
Same story here (except it’s been 20 hours). I’ve since turned location services back on but turned off increased accuracy and that was 3 hours ago.
2 Likes
Well, I spoke to soon. I have the same issue. I just witnessed my phone reboot. I now remember having to type my pin a few times lately and realize I’ve probably been through reboots when that happens. Turned off GPS for now.
2 Likes
So after turning Location accuracy back on, it stayed up for about an hour and then it did 2 reboots back to back:
61:2025-10-03 09:25:23 SYSTEM_BOOT (text, 479 bytes)
62:2025-10-03 09:26:46 SYSTEM_BOOT (text, 479 bytes)
Actually I noticed there is a pattern. Once whatever this config is applied and makes the phone reboot on the next boot it’ll apply it again and reboot immediately. Then it stays up a bit longer: up to an hour sometimes and then this pattern repeats.
Btw, I’m on Rogers in Toronto area, Canada.
3 Likes
I noticed the same pattern as well. The 2nd reboot is immediately. Mine has been up for 14 hours with Location On and Location Accuracy Off.
I have had no issues, UK user with Physical SIM ecotalk (MVNO of EE), location, WiFi calling, VoLTE and 90Hz display on. Battery saver off.
Most users who reported issues were based in US or Canada.
So far I have noticed two exceptions, @alehel (Norway) and @Raiken (Denmark).
5 Likes
Either way, a reboot due to a config change because of location is strange on Android. I have had many Androids and I have never seen one reboot because of a location change. I’m talking cross-Atlantic location change during travel. I think someone shat the bed by issuing reboot where it wasn’t necessary. Restarting the relevant services should be enough. Country location can change even without physically moving due to external changes or errors in location services. Rebooting when that happens seems like a time bomb. Even if a reboot is necessary, it should not be involuntary. Instead the user must be prompted to trigger it. The more I think about this, the more it feels like one of my junior developers merging a PR they didn’t fully understand the implications of without asking for review. 
(We’re working with Android Automotive.) Perhaps the change came straight from Qualcomm.
1 Like
Apologies for lack of context, I was meaning to reply directly to @alegel as I am nearer to them.
1 Like
Could be interesting to see if our two Scandinavian outliers may have other things going on that might prompt it. Maybe like a travel eSIM installed or connected to a VPN for the US or Canada?
Now approaching 17 hours without a reboot. Hoping quite a few fairphone owners like to travel, if tourists to Canada or the US experience this over the next few days, the fix might be here faster. 
1 Like
6 posts were merged into an existing topic: Is Fairphone remotely disabling imported Fairphone 6 models in North America via software update?