Now, after a few hours of using the Oct. 31 nightly build I can tell there are still random reboots on the AA model (this doesn’t come unexpected, of course).
Probably even more important than GPU clock is the memory clock . Anyone knows how to find out what clock rate the memory runs at? Googling didn’t bring up anything useful. Also, I don’t think I have any way to influence RAM clock from userspace (if I understand correnctly, RAM clock generally is set up by second level bootloader? Anyone can confirm this? I’m not really familiar with android, only with “normal” embedded linux boards ) .
I have experience with 2 different PRO-AA phones and they both didn’t have any random-reboot problems (at least not with LineageOS). I had major issues in the summer of 2016 but that was probably due to buggy FP Open versions and not because of the phone because each month it got less and less with software updates.
I have an AA processor.
I only had some random reboots with modem-17.08.1 (with Fairphone Open OS as well as with LineageOS), not before that, not after that.
Interesting. I have this PRO-AA phone since February 2016. I’ve been using FP Open ever since I heard of it, and haven’t had any issues with random reboots, until I upgraded to the last Android 5.1 release. All releases of Android 6 also gave me random reboots, and each of them was worse.
So, the end I did the jump to Lineage at some point in summer, and haven’t had reboots there, until I switched to the official one.
@chrmhoffmann
I’ve started to gather them at https://struppi.name/fp2_last_kmsg/
Gonna send you a private message when i put new ones there, so I can refrain from spamming this thread
There’s two of those last_ksmg files now, the first one in the folder you’ve already seen through
Ahh, sorry I missed a part of the convo. I can’t seem to find the processor version in LOS though at Settings -> About phone. I fired up Termux, did a cat /proc/cpuinfo and it says I got PRO-AA. I got pretty bad memory with regards to random reboots cause generally it does not bother me. Gonna try to remember!
There’s now 8 last_kmsg.txt files at above mentioned URL:
I can’t spot any particular pattern in the files preceding the crashes. @chrmhoffmann, what’s your opinion on the memclock issue? Running the processor at out-of-spec conditions might explain the seemingly random error patterns IMHO.
struppi, to be honest. I don’t know. It’s weird that you have so many issues where I have no reboots at all. Some of crashes seem to be related to some filesystem problems though. I’ll try to run kernel debug and see if there’s something fishy.
I just now noticed something in the description of the “Efficiency” performance profile of the power saver settings. You can read about it here (because German locale on my phone).
The “Efficiency” profile is described as
“Favor power savings. Limit maximum CPU power and optimize for power saving at the cost of higher latency.”
If Kernel Adiutor doesn’t work, perhaps that setting could do something helpful?
I did set it when I installed LineageOS because it seemed to be the reasonable choice for me, but I totally forgot about the CPU limiting part …
) .
