FP2 random reboots - see #rebootsguide for help

I’m also still struggeling with the rebooting problem. I already had three reboots today.
This is my second device because my first one was replaced a few moth ago (having the same reboot problem and a defect touch screen).

Even though I love the idea of the fairphone and I wished it would work perfectly, I also got to a point where I can’t stand it any longer and I have to give it back. This is too much of a struggel.

Wow, that’s a lot.
I guess it’s the reading fromthe hiccup app (or do you keep a list :wink: ).
My FP2 has had 495 crash-reports in two years time. That’s something I can deal with, even though there are some days or hours, when the phone is rebooting over and over again just minutes apart.

Your phone really seems broken and you should contact support for a replacement (contactsupport); unless you have installed an app causing those reboots, that is.
I guess, you already tried the troubleshooting guide: Phone stability and the rebootsguide (as it is mentioned even in the title of this topic).

I keep my fingers crossed for you.

2 Likes

Yes I did and I identified apps who are “at risk” : for instance using “Bike Citizens” especially with “Ping” on bluetooth (but also without and any bike app, actually), using “Player FM” and keeping it with the screen switched on, of course “Google Maps”… Another risk factor identified for an imminent reboot is heating of the back cover (but they can also occur with normal temperatures). And sometimes it occurs at 05:02 AM like this morning (the rebooting vibrations woke me up!) without any obvious reasons. It can occur with or without SIMs, with or without SD card, with or without 4G, with GPS on or off. Nothing changed with the recent patch. I can live with those reboots but I still have my 2010 iPhone 4 in a corner, ready to be re-used despite its small screen default if they become too troublesome. Still hoping for another patch, though.

1 Like

yeah! Thanks to the great work by Fairphone developers, the problem of random reboots is completely gone with the latest update. It was long due but great that a solution has been found finally.

1 Like

First of all, I’d like to thank you guys at Fairphone that you do such a good work of keeping our phones in good shape, softwarewise!

But I have to state that my phone crashes since I installed the update. Before that it went very smoothly and crashed extremely seldom. Strange! :thinking:

After a few days of stability I got a random reboot today, and the last_kmsg log file says it’s Aix Weather again. I’m giving up on it and will try Your local weather instead to see what happens. Below the relevant segment of the log file.

Pid: 5135, comm: aix.AixService]
CPU: 3 Tainted: G W O (3.4.0-ga177cec #1)
PC is at 0x729a71b8
LR is at 0x729a128d
pc : [<729a71b8>] lr : [<729a128d>] psr: 400e0030
sp : b37bf2a0 ip : 00000000 fp : 32d4cae0
r10: 32c005e0 r9 : adb23200 r8 : 00000000
r7 : 00000000 r6 : 32d2a720 r5 : 6fdc2dc8 r4 : 32d2d4a0
r3 : 00000000 r2 : ffffffff r1 : 00000000 r0 : 70739de0
Flags: nZcv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
Control: 10c5787d Table: 22c6806a DAC: 00000015
[] (unwind_backtrace+0x0/0x138) from [] (__do_user_fault+0x104/0x150)
[] (__do_user_fault+0x104/0x150) from [] (do_page_fault+0x384/0x410)
[] (do_page_fault+0x384/0x410) from [] (do_DataAbort+0x144/0x244)
unwind: Unknown symbol address c01026b8
unwind: Index not found c01026b8
aix.AixService]: unhandled page fault (11) at 0x00000000, code 0x005
pgd = e2c68000
[00000000] *pgd=00000000

Pid: 5135, comm: aix.AixService]
CPU: 3 Tainted: G W O (3.4.0-ga177cec #1)
PC is at 0x729a71b8
LR is at 0x729a128d
pc : [<729a71b8>] lr : [<729a128d>] psr: 400e0030
sp : b37bf2a0 ip : 00000000 fp : 32d4cae0

Found an Aix Weather replacement app: Meteogram Weather Widget. I can confirm that this one causes no reboots.

Can someone help me ?

After opening the serialconnection with my DIY-shield (attached on the extension port of the fairphone) the FP reboots a few minutes or seconds later…
I logged with adb wireless because the reboots only happen when no usb cable is plugged in…

here is the last log I get with quite some errors…

03-16 13:58:56.686 330 330 I ServiceManager: Waiting for service AtCmdFwd…
03-16 13:58:57.686 330 330 I ServiceManager: Waiting for service AtCmdFwd…
03-16 13:58:57.728 9184 9184 W sfq : Failed to find local clusters.
03-16 13:58:57.866 9184 10504 E wua : Job(ItemMessageAttachmentsCacheEvictorJob#0.20) Enqueued job ‘ItemMessageAttachmentsCacheEvictorJob’ failed
03-16 13:58:57.866 9184 10504 E wua : java.lang.IllegalArgumentException: Attachment cache cannot be null.
03-16 13:58:57.866 9184 10504 E wua : at oyk.a(Unknown Source)
03-16 13:58:57.866 9184 10504 E wua : at ozy.a(Unknown Source)
03-16 13:58:57.866 9184 10504 E wua : at xth.a(SourceFile:2)
03-16 13:58:57.866 9184 10504 E wua : at wtm.b(SourceFile:2)
03-16 13:58:57.866 9184 10504 E wua : at wtn.a(Unknown Source)
03-16 13:58:57.866 9184 10504 E wua : at xth.a(SourceFile:2)
03-16 13:58:57.866 9184 10504 E wua : at xso.run(SourceFile:1)
03-16 13:58:57.866 9184 10504 E wua : at wko.run(Unknown Source)
03-16 13:58:57.866 9184 10504 E wua : at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
03-16 13:58:57.866 9184 10504 E wua : at java.util.concurrent.FutureTask.run(FutureTask.java:237)
03-16 13:58:57.866 9184 10504 E wua : at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:154)
03-16 13:58:57.866 9184 10504 E wua : at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
03-16 13:58:57.866 9184 10504 E wua : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
03-16 13:58:57.866 9184 10504 E wua : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
03-16 13:58:57.866 9184 10504 E wua : at java.lang.Thread.run(Thread.java:818)
03-16 13:58:57.905 336 6730 E CABL : hist_preprocess: Incorrect histogram data!!!
03-16 13:58:57.905 336 6730 E PPDaemon: abl_calc_lut() failed with ret = 1

How can you check these log files?

2 Likes

you use adb for this :slight_smile:

1 Like

I used SysLog, rooted mode.

@Dr_Cool could you please have a look on this last_kmsg…

Cannot access the file, sorry. You need to open it with Wordpad (not Notepad) and look for words like “tainted,” “page fault,” “unknown symbol address,” “undefined instruction,” “freezing user space,” or any other suspicious message in the file. Then you check for the last app showing activity before the suspicious message, it’s usually the culprit one. The segment you copied a few messages above unfortunately doesn’t offer me any hint of a problem, but my knowledge is limited, maybe somebody else can see something wrong in it?

Now it should work…
I allready know the app or better the activity causing this unwanted behavior…
It´s the opening of a serial connection to the DIY-board…

This is harder to debug because there can be a hardware failure involved, for example, the serial connection could be overloading the i/o circuitry, then causing system failure.

What do you mean with overloading ? Draining a to high current?
I don’t think this is the case because the shield is always attached to the FP and so is draining always a small amount oft current…
It only restarts when I open a serial connection and the usb-cable has to be unplugged …

I thought the baud-rate could be the problem but i don’t think so … :smiley: i mean with a usb-cable attached it works and so we can forget this point…

This hadn’t happened for a while, but has just started again. I thought it was Facebook, but I removed the app and it’s still happening with any app or none - usually after I’ve been using the phone for a little while (15 minutes?) but the phone isn’t hot (and sometimes it happens when im not using it).

Not sure if it’s since the latest update or had started before then.

Does anyone have any ideas? Bear in mind that I’m a technophobe/luddite so won’t understand any technical terms! Thanks!

Hello,

Wanted to say that after some time observing when reboots occurs it seems to be link to silly Facebook app. Also I experience some reboots with Waze as well.

Anyway, thank you for the confirmation, gonna backup, reinstall OS and try again to leave with F-Droid only. :slight_smile:

1 Like

I’ve been using SlimSocial as a replacement for the Facebook app. it doesn’t have all the features but it works well and respects your phone, battery and privacy.

Hello,

I’m now using FaceSlim installed via F-Droid. Works for my needs. :slight_smile:

SlimSocial for Facebook has a newer version though, gonna give it a try.

Thanks.