@struppi: I swapped my display module with a friend of mine and forgot to re-insert the paper I inserted there some time ago (oh, it’s over a year now ). Suddenly I had my first reboot for a long time. Are you aware of this?
Yes, I’m aware of this. Still, thanks for trying to rule out potential issues
The phone even reboots while just lying on the table in standby, so it’s probably not some sort of mechanical issue.
New random reboot. Add new last_kmsg file in this folder.
Is there a “HowTo” about creating a kmsg_last report step to step. Couldn’t find it, but did have some spontaneous reboots with the Official LOS, didn’t have it before with the unofficial version.
Here’s what works for me:
- You need a Terminal. Either install “Termux” and open that or enable debugging on the phone, connect it to your Computer and open a shell by “adb shell”.
- Gain root access: type “su”
- type “cat /proc/last_kmsg > /sdcard/Documents/FilenameOfYourChoice”
- The new file will appear in the “Documents” folder of your phone’s internal memory. Copy it by whatever means you like.
I don’t think there’s a way to access /proc/last_kmesg without becoming root first.
StevenHachel, you seem to have trouble with your sd card. Could you please remove it and check if it doesn’t have issues? And see if the reboots are gone without SD card?
There’s also one last_kmsg where the kernel is running in permissive mode and running busybox. Why?
Have now uninstalled BusyBox, because I currently no longer need it. The Kernel runs in the Enforce mode, according to query by getenforce. Will my phone go up without SDCard, which would not be an option for me in the long run.
Are you using the secard as internal storage?
…as an external device.
It should boot in both cases anyway. Chris
just had seven reboots after each other. Have removed the SD card before the last two restarts. Battery has dropped from 95% to 1%.
I uploaded the last last_kmsg file. I think my phone is just destroying itself.
can you please flash first this boot.img (boot for tomorrows OTA with more debug):
And send us dmesg here.
And then plase flash this boot.img (boot for tomorrows OTA with more debug + revert of this commit:
Author: chrmhoffmann firstname.lastname@example.org
Date: Sun Oct 22 09:49:28 2017 +0200
Revert "FP2: no clue what this does but it fixes startup reboot after deprecated/android-3.4 merge" This reverts commit 941db55e1d0d27f4a033dc930bc7fc115049914a.
yes, I like to do that.
Where can I find the dmesg file? logcat -d -f /sdcard/logcat.txt? …then I uploaded these here.
Currently the boot_debug.img is running.
Looking at the logcat file, you are using adiutor. You should maybe also stop that for a while and see if it helps.
You can find dmesg by running: adb root and adb shell dmesg (or adb shell then su then dmesg)
okay, I uploaded the dmesg. and now I will flash the other boot.img.
well, does it still crash with the first boot.img?
what is that?
WARNING: at …/…/…/…/…/…/omni-6.0/kernel/fairphone/fp2/fs/proc/generic.c:323 __xlate_proc_name+0xa8/0xbc()
Are you posting dmesg from TWRP?
yes, over TWRP. Why?