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…
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?
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.
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.
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
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.
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.
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.
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.
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
I’m seeing these random reboots since I installed 18.09.02
As far as I can tell they are not linked to any app. They do occur more often if the battery is full in my case.
I’m a bit sad that we don’t hear a lot from the Fairphone developers. These reboots are killing the Fairphone experience and it should be of the highest priority to fix these.
Even if these random reboots affect only a part of the fairphones, it should be a high priority issue.
I do not think it is hardware, prior to upgrading to Android 7 it only occurred a few times and it was gone the moment i reseated the battery. I reported my issues in the bug tracking system, but very little feedback. But I will contact support anyway to see what they say.
I will read this thread later. I’m at work. I was just trying to console my wife who phoned with news of a death in her family, when my FP2 decided to reboot. Next time, it’s on eBay.
I’m hopeful 
