English

FP2 random reboots - see #rebootsguide for help

bootissues
randomreboots
Tags: #<Tag:0x00007f57d72c9cd8> #<Tag:0x00007f57d72c9918>

#587

Hi,
I’m completely new to this community, I got my FP2 3 weeks ago.
After everything went fine for the first days, dissapointment struck when I tried my first navigation runs. The apps (Google Maps and Here) interrupted and the phone did half and full reboots every 5 minutes.

After reading this thread and the rebootsguide I set off to try one by one whatever was suggested - and luckily for me the very first thing was a full success:

I deactivated G4 functionality and now I can use any navigation app and the phone is completely staple. No interrupts, no reboots!


#588

Could reproduce this rebooting misbehavior easily with a CPU burn test:
Fairphone 2 with FP Open, latest version, rooted and Xposed.
When set to 4G and running a CPU burn software (CPUBurn) at 99% stress, 4 threads, peak core temperatures (about 90 Celsius), I get consistent reboots about every 30 minutes.
When set to 3G and running the same stress routine, with exactly the same peak temperatures, I don’t get reboots.


#590

In reality reboots still happen in 3G, although much less frequently than in 4G in my case. Yesterday night for example it happened when I tried to turn on the hotspot function at the end of a recharge cycle. Reboots are clearly related to elevated temperatures in the region around the radio chip. This is why it happens more commonly at the end of a battery recharge cycle or when using data or CPU intensively.
I’ll try to deactivate and reactivate radio when I feel that temperatures rise due to Internet use, I wonder if something in the radio system gets stuck in a loop causing overheating. Hope it’s a software and not a hardware design problem, since this is a wonderful phone otherwise.
To be fair, my previous phone, an HTC One X, used to have frequent reboots until they sorted out the bugs, it took them more than a year to stabilize the system, and it would still reboot sometimes when overheated or under cpu stress. But the Fairphone at this point is less reliable than the HTC was with their last system update.


#592

Kudos to @Chris_R for sharing this important information! :+1:


#593

Considering my own experience we may narrow it to the new display module.
I never had any issue but my FP2 (running Open OS) is now randomly rebboting since I’ve recently change my broken screen…

Just installed the new release today, we’ll see. :slight_smile:


#594

Hey all, I wanted to share some information with you that we got this week.

As you might have noticed, some owners of newer Fairphone 2 phones are experiencing stability issues (i.e. The phone sometimes reboots on its own.) In most cases this issue causes the phone to reboot once per day (often while not in active use). A smaller number of phones are experiencing a higher rate of reboots. This issue affects mostly Fairphone 2’s sold after August 2017.

We expect to deliver an extra software update improving phone stability within two weeks (by 20 February 2018 latest). Owners of all Fairphone 2’s will receive an alert prompting them to install this update - following the same process as our routine monthly software updates.

This update has been successfully tested on our pool of impacted test phones, and eliminated the stability problems associated with this issue. It is also being validated with end user testing.

The cause of the issue is an updated memory package. Engineers at Fairphone, Qualcomm and our manufacturer have been working to resolve it. The update developed by our software team adjusts the memory interface parameters to solve this stability problem. After rolling out this update we will continue to monitor and fine-tune performance with future updates as needed, but we expect this update to resolve the current issue.

Advice to impacted phone owners:
We suggest that Fairphone 2 owners who might be affected by this problem wait a little longer and install the software updates when prompted.

So far, Fairphone has been replacing any phone identified as affected by this issue, at the phone owner’s request. We will continue to do so at the request of owners of new Fairphone 2 phones. However, we now recommend customers wait for the software update rather than shipping us their phones for exchange. The software update will very likely be faster and more convenient.

Thanks to you and the people affected for your patience throughout the troubleshooting process, and our apologies for the difficulties this issue has caused.


Reboot and battery drain
:gb: :de: Random reboots with (official) Lineage OS?
Special Update post-18.02.0
Special Update, is it trustworthy?
Special Update post-18.02.0
Fairphone OS 18.03.1 release
#595

Thanks @Douwe for your statement. It is incredible that it took almost half a year long for Fairphone to recognize the glitch. :no_mouth:

Will the update resolve reboot issues that are caused by modem crashes, too?

https://bugtracker.fairphone.com/project/fairphone-fairphone-os-android-6/issue/86


#596

You are welcome. Please be aware that we did recognize the ‘glitch’ pretty fast. But that is the easy part. Finding the cause, creating a solution and testing if it works are the tasks that consume most time.

And no, this patch is unrelated to the modem. As stated in the bugtracker by @rick, that bug is accepted and currently under investigation.


#598

Hi there,
Thanks a lot for the updates (here and the future release).
do you think it will solve my reboot issue as well? Cf my post above yours. I own an older FP2 but replaced the display module.


#599

As far as we know there is no link between the random reboot issue and the display in use. I’d advice you to get in contact with support to have your case looked at.


#600

Like @glouton , I have an older FP2 that still randomly reboots. Is the update expected to reduce / eliminate reboots on previous batches? Mine was purchased in May 2016.


#601

hey @dalq0001, thank you for your clarifying question. Sadly this patch is only for newer Fairphone 2’s where we were able to identify a root cause for reboots and fix it.

If your FP2 is rebooting, and has so from the beginning and you tried all tips in the #rebootsguide, then there is nothing left but to contact support and look with them if this still falls under warranty.


Reboot and battery drain
#602

Thank you for the explanation. I own a Fairphone 2 with Ubuntu Touch running. As I experience the same problem of spontaneous rebooting several times per day I would appreciate to know whether the update would have an impact on Ubuntu Touch in case I would reinstall Fairphone OS and after that install Ubuntu Touch on top of it (as this is the usual way to install Ubuntu Touch). Thank you.


#603

Same here, got a new FP2 and in regards to the overall quality I was expecting better than such reboot problems since the beginning. I will try to fix it following your guide and I will post back if I manage to.


#604

I can confirm now with certainty that the source of my random reboots was the Facebook app. It appears to cause increased stress and overheating triggered by unknown address or undefined instruction loops, hence only indirectly connected to 4G or any other activity that uses hardware more intensively.

For info here is my setup:
Fairphone 2 of August 2016
Open FP OS version 18.02.0 with microG version 0.2.4-108-g464d45d, Xposed version 89-sdk23-arm, and GSM location service
Tested after a factory reset and reinstallation of Open FP.

I collected 5 last_kmsg.log files taken with SysLog immediately after random reboots during a 14-hour period. Among those 5 log files I found that facebook.katana appeared as triggering undefined instructions in 3 of them. One was corrupted and can’t be read. One implicated another app but maybe as a result of previous Facebook activity, I’m keeping the other app under observation but for know it doesn’t appear to cause any problem. Uninstalling the Facebook app definitively solves the random reboot problem. It also reduces overheating and improves battery life.

Here a sample of how facebook.katana appears in the crash logs:

facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Norm_Shared1 (16098): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Norm_Shared1 (16098): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
audit: audit_lost=21462 audit_rate_limit=20 audit_backlog_limit=64
audit: rate limit exceeded
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc

No errors detected


:pencil2: A little Guide to... Random Reboots
Has anyone gotten rid of their random reboots?
#605

Thanks @Dr_Cool for updating the #rebootsguide. I don’t know how facebook didn’t make it on the guide yet. I just updated your entry a bit to indicate that this is a issue known for quite a long while now.


#606

Thanks for confirming and improving. This info would have helped me a lot had it been on the guide before I started my tests… :disappointed_relieved:


#607

Confirmed that the Aix Weather widget also causes random reboots. Adding this info to the wiki and will try to contact the authors.


#608

I can’t approve that. I’m running Aix Weather widget since over two years now, first under Fairphone OS, now under LineageOS, and don’t have any reboot issue


#609

Before this last FP2 update that Douwe is referring to, my phone was ‘rather’ stable (after removing AVS anti-virus), but not quite. With Google Maps for instance, it rebooted. And almost every day before the update, it tended to do so likewise.

Now after the update, all seems fine again. “Seems”, because, well, if one has experienced those random reboots often, it takes a while before trust is restored completely. But I’m hopeful.

Anyway, thanks for the update!