PIN Code needed after a few hours

[_Joao_]

@eheintzmann hello, do you have any other reboot bugs since your last message?

[Eric H]

@_Joao_ hello, sorry for the delay.
Yes, sadly, my phone still randomly reboot every day.

[arubislander]

@eheintzmann Is your phone up to date? I haven't had any random reboots for quite a while now.

[Eric H]

@arubislander Yes, my phone is up-to-date. This is probably a surya only issue.

[arubislander]

@eheintzmann oh, this is the Xiaomi section. I mistakenly assumed it was the Pixel 3a section. That devices used to have this same issue.

[_Joao_]

@eheintzmann What a shame this bug.

[Eric H]

Hi @_Joao_

A week ago, I tested a script found in this forum :
https://forums.ubports.com/topic/6211/howto-alternate-way-of-saving-battery-when-using-4g-lte/70?_=1700961879422

As expected, autonomy of my phone was improved.
But as a bonus, its stability was also improved.
Indeed, I didn't see any random reboot for one week !

[_Joao_]

@eheintzmann hi
Interesting... Maybe the battery is at the end of its life. I've been asking myself this question from the beginning.

[Eric H]

@_Joao_
Maybe yes

But
I've seen random reboot when plugged
I didn't see ant random reboots in airplane mode (plugged or unplugged)

So maybe not…

[_Joao_]

@eheintzmann hi, the script works to improve battery life, but it doesn't launch with the terminal but by restarting the phone and unfortunately the phone keeps its untimely restart bug. I'm waiting for the stable version of focal to redo a clean installation to see...

[Eric H]

Hi @_Joao_

I tested only the 20.04/focal version of this script.
In this version, it uses a systemd service to automatically start/restart.
No reboot, nor manual, intervention is needed.

On my surya, with this script activated, I've never seen any random reboot.

[Eric H]

Possibly, I found something. Possibly…

Just after a random reboot, in the file /var/lib/systemd/pstore/dmesg-ramoops-0, there are these lines :

<3>[81418.767313] icnss: Received early crash indication from FW
<6>[81418.767688] [irq/42][1563404930635][16:17:26.881053] wlan: [192:I:HDD] wlan_hdd_pld_uevent: 1634: pld event 1
<6>[81418.767726] [irq/42][1563404931377][16:17:26.881092] wlan: [192:I:HDD] wlan_hdd_handle_the_pld_uevent: 1565: Driver modules are already closed!
<6>[81418.768246] [kworke][1563404941345][16:17:26.881611] wlan: [26935:I:HDD] wlan_hdd_pld_uevent: 1634: pld event 0
<6>[81418.768277] [kworke][1563404941953][16:17:26.881643] wlan: [26935:I:HDD] wlan_hdd_handle_the_pld_uevent: 1565: Driver modules are already closed!
<3>[81419.310797] Fatal error on modem!
<3>[81419.310863] modem subsystem failure reason: EX:kernel:0x0:ims:0xe0:PC=0xd8c08564.
<6>[81419.310895] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = SYSTEM.
<3>[81419.311017] Ramdump(ramdump_microdump_modem): No consumers. Aborting..
<6>[81419.311032] microdump_modem_notifier_nb: do_ramdump() failed
<0>[81419.422972] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

I found similar logs for the FairPhone 4 at :
https://gitlab.e.foundation/e/backlog/-/issues/6096

And the solution of the e-foujndation at :
https://gitlab.e.foundation/e/devices/android_device_fairphone_FP4/-/merge_requests/23/diffs

So maybe, setting two properties will solve the problem :

setprop persist.vendor.ssr.enable_ramdumps 0
setprop persist.vendor.ssr.restart_level ALL_ENABLE

[Eric H]

Before settings properties :

$ cat /sys/bus/msm_subsys/devices/subsys*/restart_level
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM

After settings properties :

$ cat /sys/bus/msm_subsys/devices/subsys*/restart_level
RELATED
RELATED
RELATED
RELATED
RELATED
RELATED
RELATED

Let's see if there are still random reboots in the next few days...

[_Joao_]

@eheintzmann it's all a bit complicated for me... But actually this report seems logical because in airplane mode the phone does not turn off by itself

[Eric H]

Since I installed UT on my phone (xenial first, then focal afterward), I have never taken 24 hours of uptime.
But with the changes indicated in my preceding posts, I have reached 3 days of uptime today.

[Eric H]

Hi @_Joao_

If you also want to test this solution, just type in a terminal these lines :

setprop persist.vendor.ssr.enable_ramdumps 0
setprop persist.vendor.ssr.restart_level ALL_ENABLE

Nothing else is necessary, and it survives a reboot.
Of course, these settings are reversible if needed.

[_Joao_]

@Eric-H
Hi Eric, I'd like to thank you and the developers because the previous operations solved the problem; the phone no longer restarts by itself and I've gained +/- 6 hours of autonomy, which is really cool.

Thanks again and best wishes for 2024.

Note: if I can help with other tests to further the community, I'd be delighted to do so.

[Eric H]

Hi @_Joao_

You are on xenial, aren't you ?

Do you see, sometimes, UI flickering ?

[_Joao_]

@Eric-H
yes xenial.
yes, it happens sometimes...I restart and the symptom disappears.
there's also a bug when I launch waydroid several times, the phone crashes and restarts by itself.

[Eric H]

@_Joao_ said in PIN Code needed after a few hours:

yes, it happens sometimes...I restart and the symptom disappears.

It happens on focal too.
I am trying to understand where this flickering comes from.
If you have any ideas...

there's also a bug when I launch waydroid several times, the phone crashes and restarts by itself.

I think this is fixed on focal.

In case you are not aware, we have now a 20.04/RC channel for surya