Thank you for the info on this.
I’ve created this issue Device rebooting (#63) · Issues · ota / issue-tracker · GitLab and will discuss with iode devs.
1 Like
If the problem is lower than the framework then only the dmesg can show information related to the reboot.
1 Like
What tools have u found helpful to analyze these log files? 
You just read them, when you don’t know something you search on the internet, most messages are not important and just inform you about the system, if you can’t see any error at all probably the system just crashes due to some low level hardware fault or firmware bug.
dmesg comes directly from the Linux kernel so there you should be able to see something reaching a critical point even if there is no record of the system shutting down, this for example would be the case of overheating, you would get some warnings of high temperature and the system would crash if it isn’t able to throttle the CPUs or hibernate in some way.
I have an older Sony phone running iode that is still on the OS 6.X branch and is stable. I think the instability started on the Brax3 when it got to the 7.x branch of iode.
I will look at dmesg today. It was useful in the past when I was upgrading the kernel on my Linux server.
I have another BraX3 that is stable and running iode 6.9. I will compare dmesg on that phone to the unstable BraX3 I have. Should I pipe dmesg through tee? What is the best command to get a file on each?
I tried it but I can’t get root access, I don’t know whether this is possible without losing the user data, ask plamen and I will look it up too
As I can understand it can’t be done
So if you try to root your phone you’ll wipe your data too but there is a chance that it will stop rebooting
You could also try a factory reset first and then do the same things to see if it still reboots
Brave AI is saying that it is possible to get kernel information on non-rooted Android devices…this doesn’t work for me on the BraX3:
adb logcat -b kernel
EDIT:
I guess that just filters for the word kernel. I do that on the first logcat file using a text editor and don’t see much.
-b is buffer, it tries to read some specific buffer, I don’t think it’s possible without rooting the phone
on F-Droid you can find some LogCat apps that help you read the files easier with colours
-v color will output colours on terminal, I don’t know if this affects the syntax of the output file
oh-buffer. I was wondering how b was for filter…it’s not.
I pulled that tee file into a spreadsheet and right before the system crashes, there are a lot of warnings about AudioFlinger. I’m not sure what that is…nothing I installed.
This is what Brave AI says about that…it’s not an app problem!
AudioFlinger is the core system service responsible for managing audio processing in the Android operating system, running within the mediaserver process.
It serves as the central component of the Android audio architecture, enabling audio use cases by providing an interface for upper-layer applications and services to utilize sound.
AudioFlinger communicates with the hardware abstraction layer (HAL) to manage audio devices and processes audio through playback and recording threads.
The last 5 warnings are about the Citrine app I installed to make my phone a Nostr relay. I’ll remove that and see if it makes a difference!
You had asked for some analysis app, for example LogCat Reader gives a beautiful presentation of the file.
OK-thanks for your help! I uninstalled Citrine to see if my phone gets stable again. I’m thinking if this is instability in iode is only impacting me than it is likely an app error rather than the phone audio system causing the problem!
Apps shouldn’t reboot the phone without root permissions, they should just crash the sandbox they run into.
oh-am I the only one with an unstable phone since iode’ went into the 7.x branch?
Users report mostly the dm-verity problem , bootloops , black screens etc
If it persists after a factory reset replace the device, there is no reason to struggle.
I’m hoping an iode’ OS upgrade takes care of this. I didn’t even notice it until last week because my phone would reboot while I was sleeping.
You probably have limited time for replacement, it could be a hardware problem that coincided with the update. If you can’t use the device properly don’t reside on that it will get fixed with an update. For the time being your case is the only incident of that kind.