I don’t seem to have random reboots any more. Noticed it less with Android 7, and not at all since I dropped the phone and had to take it apart + reassemble to get it going again, without unscrewing anything. That said, I’ve given up trying to use Waze when driving: my internet provider seemed to drop the signal and disconnect me at regular intervals when on the move, so it was unusable. I also found that switching location on used up the battery in no time.
2 Likes
Mmmmh, taking the phone apart and reassembling it is be a nice idea, thanks!
I made experiences with three fairphones, got them from my companies mobile phone pool.
The first phone started somewhen with the random reboots. And whatever I did, it didn’t went away: FPOS Android 6 and 7, Lineage OS Android 7 and 8, installed as update, installed from scratch, the random reboots remained.
Having gotten the 2nd and 3rd FP2, I tested with them also many combinations of OS, and with the ‘new’ Fairphones I never had a random reboot. Only with Lineage I have here and there very seldom a warm reboot, so only GUI reboot.
So I assume the issue with my first FP is with the phones hardware.
2 Likes
Also disabling the auto-update feature for all apps will rise the stability level significantly once the few apps causing serious troubles are sorted out and uninstalled.
Not every update necessarily fixes bugs but maybe implement even new ones.
At least when manually updating there is a chance to distinguish which app could be the culprit.
Totally agree, and I also only do manual updates for the reasons mentioned. Unfortunately there is a culture among smartphone coders of using app updates as “news boards” instead of looking as in the past for software that would “mature” in as few versions as possible. That was once considered to be the essence of being a truly professional coder or engineer. GAFAs however utterly destroyed deontological approaches in tech fields, and we are all paying a heavy price with poorly designed, unreliable and invasive devices.
1 Like
I had reboots with my own Fairphone 2 in the first few months while testing different setups with the Open OS. Then I finally found a stable version. Later I bought another Fairphone 2 for my wife, and not having installed any of the previously identified problem apps, her phone never experienced a random reboot that we know of.
Well this doesn’t look good:
> unwind: Unknown symbol address c0102ab8
> unwind: Index not found c0102ab8
> Code: bad PC value
> ---[ end trace 5fd39709331e79a7 ]---
> Kernel panic - not syncing: Fatal exception in interrupt
> SMP: failed to stop secondary CPUs
> wcnss crash shutdown 0
> Rebooting in 5 seconds..
> SMP: failed to stop secondary CPUs
> Going down for restart now
Still no idea what causing it, though. Can’t find anything in the log that I can link to an app or anything.
I’ll leave the phone running with adb from the pc next night maybe that will be more enlightening.
Oh welcome - so you found out about it aswell…
Therefore I keep properly working apps and their installation file in case of an update does not work as flawless as it’s precursor. I only had few of those cases in the past.
So unfortunately because of this I rather stick to some old version that works instead of (auto-)updating anyway and introducing problems or simply accepting new/more permissions opening more “doors” for data leech.
Speaking of app permissions, I still keep the same rigorous judgement which app makes it/stays on my handset than at the very first beginning.
Erm, be careful with this - I am afraid it is simply too much truth for many users…
Instead of blaming specific apps/developers it seems to be much more comfortable these days to blame the phone having a poor design or the OS being faulty.
All is going to waste…
1 Like
So the logcat before the crash reads:
02-10 07:15:11.191 27466 28153 E DatabaseUtils: Writing exception to parcel
02-10 07:15:11.191 27466 28153 E DatabaseUtils: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/images/media from pid=27849, uid=10108 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
02-10 07:15:11.191 27466 28153 E DatabaseUtils: at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:633)
02-10 07:15:11.191 27466 28153 E DatabaseUtils: at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:503)
02-10 07:15:11.191 27466 28153 E DatabaseUtils: at android.content.ContentProvider$Transport.query(ContentProvider.java:214)
02-10 07:15:11.191 27466 28153 E DatabaseUtils: at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:102)
02-10 07:15:11.191 27466 28153 E DatabaseUtils: at android.os.Binder.execTransact(Binder.java:697)
02-10 07:15:11.193 27849 29434 E JobExecutor: Crashed job{id=19664, finished=true, result=FAILURE, canceled=false, periodic=true, class=FilesSyncJob, tag=FilesSyncJob}
02-10 07:15:11.193 27849 29434 E JobExecutor: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/images/media from pid=27849, uid=10108 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.os.Parcel.readException(Parcel.java:2013)
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.content.ContentProviderProxy.query(ContentProviderNative.java:418)
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.content.ContentResolver.query(ContentResolver.java:754)
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.content.ContentResolver.query(ContentResolver.java:704)
02-10 07:15:11.193 27849 29434 E JobExecutor: at android.content.ContentResolver.query(ContentResolver.java:662)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.owncloud.android.utils.FilesSyncHelper.insertContentIntoDB(FilesSyncHelper.java:194)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.owncloud.android.utils.FilesSyncHelper.insertAllDBEntriesForSyncedFolder(FilesSyncHelper.java:101)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.owncloud.android.utils.FilesSyncHelper.insertAllDBEntries(FilesSyncHelper.java:163)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.owncloud.android.jobs.FilesSyncJob.onRunJob(FilesSyncJob.java:100)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.evernote.android.job.Job.runJob(Job.java:124)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.evernote.android.job.JobExecutor$JobCallable.runJob(JobExecutor.java:181)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.evernote.android.job.JobExecutor$JobCallable.call(JobExecutor.java:166)
02-10 07:15:11.193 27849 29434 E JobExecutor: at com.evernote.android.job.JobExecutor$JobCallable.call(JobExecutor.java:149)
02-10 07:15:11.193 27849 29434 E JobExecutor: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
02-10 07:15:11.193 27849 29434 E JobExecutor: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
02-10 07:15:11.193 27849 29434 E JobExecutor: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
02-10 07:15:11.193 27849 29434 E JobExecutor: at java.lang.Thread.run(Thread.java:764)
Looks like I should uninstall Nextcloud +___+ But I have no idea why Evernote is in there, I never used nor installed that app in my live. Any ideas?
Clearly it’s part of Evernote:
And for some reason it’s in your system, at least its libraries. These leftovers could be the cause of your troubles. Hard to give you a solution though, except for reinstalling a clean system.
2 Likes
Wow, that is sooo weird! I never in my life installed Evernote on any phone I owned and cerstainly not this FP2. Maybe it’s bundled with another app?
I actually just did a clean install after booting into Safe Mode garbled my accounts, so let’s see what happens ^ _ ^
1 Like
Sorry, no success story here. I’ve installed FPOpen as soon as I got my FP2 two years ago and have had random reboots for as long as I can remember. I did get the mainboard exchanged on warranty once (for a different reason), did not fix it. Disassembled, cleaned the contacts, reassembled, did not fix it. Installed the update to Android 7. Did not fix the random reboots, but added warm reboots to the mix. No Gapps, Netflix, Facebook, Instagram… installed.
The reboots are only really annoying when they happen during a call (which seems to happen too frequently for them to be completely random). I haven’t been digging around in logs at all to hunt down the issue. Maybe I should try to find some time to investigate and try to fix this. Thanks to all for the pointers of possible solutions !
PS: Oh and @jfml just re-read your last post about garbled accounts: Just last week one of the random reboots during the night removed all of my contact data from the phone. This was the first time ever a reboot actually deleted data (other than the current state of apps I used during the reboot). Well, of course the contacts are synchronized with an account so I didn’t really loose anything. Could this be similar to your case ? I didn’t try to boot to Safe Mode though.
1 Like
I’m so sorry to hear that! +___+
So far looking at the logs wasn’t very enlightening for me I still have no clue what’s causing the reboots (if it is only one thing) and I’m still unsure what to look out for exactly and feel that this is all a bit over my head (I do realize that this is a super complicated problem with no easy one-fits-all-solution …)
I’m pretty sure that my lost accounts have to do with the boot into Safe Mode, it’s even mentioned in the wiki entry (which I only read after I booted into it +___+) because I saw it directly after I booted back into normal mode.
Any comments on that?
I noticed that the battery symbol on the phone was still on charging, but it was unplagged, than I wan’t to kill battery charge limiter, but instead I got a soft reboot, I can send the whole log, but I only have dmesg.log
[14310.439736] 2728,14310439736;ILITEK LINE = 252: ilitek_i2c_transfer:252, error, ret -107
[14310.498517] 2729,14310498517;ILITEK LINE = 1232: ilitek_i2c_suspend, 0x02 0x00 set tp suspend err, ret -107
[14330.521645] 72730,14330521645;init: Untracked pid 32707 killed by signal 1
[14330.572711] 72731,14330572711;init: starting service 'bootanim'...
[14330.598913] 72732,14330598913;init: property_set("ro.boottime.bootanim", "63434806567279") failed: property already set
[14330.618919] 72733,14330618919;healthd: battery l=94 v=4086 t=26.5 h=2 st=3 c=921 fc=2366000 cc=0 chg=
[14330.654330] 72734,14330654330;healthd: battery l=94 v=4084 t=26.4 h=2 st=3 c=1042 fc=2366000 cc=0 chg=
...
[14331.506186] 72761,14331506186;init: Service 'zygote' (pid 471) killed by signal 9
[14331.506280] 72762,14331506280;init: Sending signal 9 to service 'zygote' (pid 471) process group...
[14331.509406] 72763,14331509406;init: Successfully killed process cgroup uid 0 pid 471 in 2ms
[14331.594032] 72764,14331594032;init: Unable to open '/sys/android_power/request_state': No such file or directory
[14331.594255] 72765,14331594255;init: Unable to write to '/sys/power/state': Invalid argument
[14331.594405] 72766,14331594405;init: Sending signal 9 to service 'audioserver' (pid 482) process group...
[14331.599913] 72767,14331599913;healthd: battery l=94 v=4114 t=26.4 h=2 st=3 c=692 fc=2366000 cc=0 chg=
[14331.649122] 72768,14331649122;healthd: battery l=94 v=4113 t=26.4 h=2 st=3 c=734 fc=2366000 cc=0 chg=
[14331.683006] 72769,14331683006;healthd: battery l=94 v=4106 t=26.4 h=2 st=3 c=749 fc=2366000 cc=0 chg=
[14331.726725] 72770,14331726725;init: Successfully killed process cgroup uid 1041 pid 482 in 132ms
[14331.729502] 72771,14331729502;init: Command 'restart audioserver' action=onrestart (<Service 'zygote' onrestart>:3) returned 0 took 135ms.
...
[14331.921360] 72824,14331921360;init: starting service 'zygote'...
[14331.950181] 72825,14331950181;init: property_set("ro.boottime.zygote", "63436155478111") failed: property already set
[14331.951102] 72826,14331951102;init: starting service 'audioserver'...
[14331.951213] 72827,14331951213;init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[14332.018942] 72828,14332018942;init: property_set("ro.boottime.audioserver", "63436185498007") failed: property already set
1 Like
There is a quick and stunning simple way to get rid of those random reboots:
Switch oft FP2 and buy a Samsung A7. Works perfect and btw it solves many other FP2 issues.
Keep on rebooting, felliows!
KP
1 Like
There is a quick and stunning simple way to make sure you don’t come across as somebody who can’t even search the internet:
5 Likes
Thx. I’ve been using 2 FP2 in the family with random reboots and many other issues. Ever since I use (as before the FP2) Samsung phones, I had none of these issues. Just because it can be found in the internet doesn’t mean I have to have these issues. With the FP2s we have all that stuff on both phones.
It quit wasting time in looking for hints, clues and workarounds to use a mobile phone. i want to USE it, not REPAIR it half the time.
All the best.
KP
I’m glad you found a phone which works out well for you.
But just because it works for you doesn’t mean it works well for everybody who buys one. Sadly.
And just because my Fairphone 2 works without random reboots for me doesn’t mean it works this way for everybody who buys one. Sadly.
Posting in problem topics something like “Get a working phone like mine, then!” doesn’t help much, whatever phone you want to recommend.
You can run into trouble with every smartphone potentially.
9 Likes
We are supporting the fruit of a movement here at the forum, everybody who likes to have support is welcome, even you @kpzeyen, if you want to come back some day. Just keep that in mind.
4 Likes
This is working for me…
Since upgrading to Android 7 I have been plagued with reboots and have tried most of the things suggested in the troubleshooter but couldn’t find anything to work. Then I remembered I had the same problem when I first got my FP2 about 3 years ago. A fellow android user (Samsung) said they had to clear their cache of the Gmail app because of known problems. I tried it then and it worked. I’ve tried it now and I’m on day 3 with no reboots. Hurrah! 
I’m hopeful 
4 Likes