I made the same experience. My FP2 regularly reboots when using GPS and charging in my car.
Okey, so now I have deactivated everything that has to do with google (I think), I’m just wondering, how did you do it to deactivate all your google apps/widgets? I’ve turned off all sync of google but sadly it still reboots daily (might be less often though) but is there something else you can do to deactive them? Sadly they can’t be removed due to being standard applications
Thanks
Has happened to me too a few times now. If it’s starts happening on a regular basis I’ll be sure to try some of the advice in here. For now just following the topic 
Hello. I received my Fairphone 2 1,5 week ago. Very satisfied, but what is not satisfying is that it reboots one to five times a day while using it. I have the latest OS installed 1.28. I´ve also tried to removed the SD and SIM card, but it doesn´t seem to help. Any feedback is welcome!
After the Update on the 1.2.8 Version I experianced the first reboots. Just 5 times in some weeks but never had reboots before.
The reboot problem is not on the official bug list of the fairphone devs just on the known issues list of the forum.
The problem for the most people here is mutch bigger than mine so i wondering if the devs are working on this topic?
Do we have to live with the workarounds or is there hope for the next version?
Not fixed in version 3.2.6 released today :’(
https://forum.fairphone.com/t/fairphone-os-1-3-6-update/18090?source_topic_id=11553
…I will install this tomorrow. Anyone tried already ?
On my FP2 (1.1.7) reboots are not so random. They are triggered by the use of a single application: Crossy Road. I cannnot play this game long enough to beat my score before it restarts the phone. No idea why. Anyone similar?
From my experience, an application can crash a system (be it on a computer, phone or server) by either exhausting the resources of the device (ex: using all the RAM) or by simply using a faulty component or bugged driver until it crashes.
In my case my FP2 reboots more often when OsmAnd or Google maps are used. I don’t think either of those applications are responsible as they are used on thousands of devices without crashing the system. It is far more probable that the GPS driver developed by Fairphone has a bug.
The same goes for other applications like gmail. This application is used by far too many people without problem to be the root cause of such an issue. It probably uses more data than other applications or accesses the memory more often. If the memory or SIM reader drivers are bugged this would make the phone reboot “as if” these applications were the root cause.
The same misconception has given Windows the reputation to be unstable when it was often the drivers provided with graphic cards or other components which where full of bug.
I might be wrong but it seems that Fairphone has not tested their drivers and/or hardware properly before releasing. Many bugs like camera noise, random reboots, unresponsive touchscreen, unstable brightness, etc, point in that direction.
1 Like
Still there on 1.3.6. It looks like its thermal problem. 3-5 reboots a day if we have warm weather and the phone is offen in use.
Dear FP users,
I am in my 2. month to use the FP2.
Beside other major technical problems it also starts to reboot and getting blocked more and more frequently after the second week of use. For example it blocks
1.during the process of unlocking (with pattern or numbercode) = no access to the phone.
2. Or gets blocked during use of apps or
3. shuts down completely during use of skype or whatsapp even with full battery.
Other point of risk might be the extrem warming up during use of whatsapp/skype and other online applications.
Does any body have similar experiences?
Did you find any solutions?
Thank you.
Martin
Dear FP users,
I am in my 2. month to use the FP2.
Beside other major technical problems it also starts to reboot and getting blocked more and more frequently after the second week of use. For example it blocks
1.during the process of unlocking (with pattern or numbercode) = no access to the phone.
2. Or gets blocked during use of apps or
3. shuts down completely during use of skype or whatsapp even with full battery.
Other point of risk might be the extrem warming up during use of whatsapp/skype and other online applications.
Thank you.
Martin
1 Like
[quote]The same misconception has given Windows the reputation to be unstable
when it was often the drivers provided with graphic cards or other
components which where full of bug.[/quote]
Or hardware issues, even.
A microkernel-based OS is a lot more complex, but is also going to be much more stable and allows more security. The alternatives we see though are VM-based security, capability-based security, and containers. For desktop, that is Qubes (for server, a plethora of options) and examples of the other two are something like SELinux and Docker.
1 Like
Mine too. It happened when I was in the middle of something important too. I need something reliable, but this issue makes me nervous about using my FP2 on business trips.
1 Like
My first Fairphone 2 suffered random rebooting. Finally, after several emails and then two phone calls, and sending it back, after two weeks I was then sent a second new one, which worked fine until the 23 May update. After an hour or two there was a reboot, then about a week later another one. I will email customer service (hope there’s a response this time) to report it. One more reboot and I’ll be considering getting a refund. My first FP2 was sent in early February.
I’m realy suprised how I could mitigate the reboot issue on my fp2.
The only thing I changed is the position of my two sim cards. Just switch the cards in the slots and switched the funktion of the cards also. Same cards same funktion just another slot for the cards. One card is used for data and one for calls/sms.
So i the End no reboots since more than a week. Supprise, supprise!
2 Likes
I wrote down all reboots since installation of update 1.3.6 (2016-05-23, 21:32). I wrote down date/time, Wi-Fi and Bluetooth status, used app, background apps (not services), crash type (instant reboot, hang and reboot, reboot while not in use), later (since 2016-06-04 21:50) also if it was connected to the charger or not.
_ * = not experienced live, only seen PIN dialogue
2016-05-26, 02:44
2016-05-26, 06:15*
2016-05-26, 06:17
2016-05-28, 03:02
2016-05-28, 10:37
2016-05-28, 10:46
2016-05-28, 20:51
2016-05-28, 21:41
2016-05-29, 20:03
2016-06-03, 06:10*
2016-06-03, 15:28
2016-06-04, 09:47*
2016-06-04, 21:50
2016-06-05, 01:37
2016-06-05, 09:26
2016-06-05, 10:09*
2016-06-05, 10:16
2016-06-06, 05:02*
2016-06-06, 19:12
2016-06-06, 19:19
2016-06-07, 23:27
2016-06-11, 12:23
2016-06-11, 21:21
Notable is that there were long times without any crash:
May 24-25
May 27
May 30-Jun 02
Jun 08-10
At other times, the FP2 crashes twice within 10 minutes.
All crashes (except 2016-06-03, 15:28) occurred at home while connected to the Wi-Fi. All crashes since 2016-06-04 21:50 occurred while connected to the charger. But there were earlier crashes while not on the charger.
The location switch was permanently on, so GPS can be used anytime.
6 Likes
Nice list. It would even work better as a CSV list (see example below). Or have you done that and the forum software is only showing half of it?
Date; Time ; Wifi 1/0; GPS 1/0 ; SIM 1/0 ; Bluetooth 1/0 ; Crash type ; Charger 1/0
So GPS was on all the time? Could you try a few days without it? Just for testing? Are there people that have tried to use the phone without a sim card at all for a few days?
Yes I have. From January 5th or so when I got the phone to the release of Fairphone Open OS I used the FP2 without a SIM. Then until two weeks ago or so when I dropped it in the toilet I used it with a SIM. But I never ever had a reboot.
I have to search for his comments on that. I would like to see the “crash” comparison of a FP2 running without Bluetooth, GPS, Wifi, or SIM for a few days versus phones where either only either Bluetooth, GPS, Wifi, or the SIM is activated, best attached to a computer logging everything … or trying to find last_kmsg after the crash?
Does this work on a FP2, right after a crash?
$ adb shell cat /proc/last_kmsg
Or before/monitoring
$ adb shell cat /proc/kmsg
Maybe someone could release a FP ROM with more debugging options activated? Or is it possible to get kernel logs right now? I would like see them.