PIN Code needed after a few hours

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

Eric H

Hi @_Joao_
Have you upgraded to focal/20.4 stable ?

_Joao_

@Eric-H
hi Eric,
no I'm on 16.04 (OTA 25) but I'll look at updating to focal, thanks I'm a bit late on updates...

_Joao_

@Eric-H
Hi Eric,

I switched to focal stable and the phone works much better, no more reboots when activating waydroid.

I also recovered the battery graph and I have a battery life of +/- 24 hours with normal use.

Some applications no longer work, such as the tor browser, and there are 3 or 4 sentences in the menus that aren't translated into French, but that's not a problem.

GPS works with pur map and OMS Scout server.

Thanks to the developer and the community, I use my phone on a daily basis and it works very well.

I can't wait for the next stable update, as I can already feel the power and stability of this Ubuntu focal version.

Eric H

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

@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.

Please, may I ask your help with the flickering issue ?

Could you do a simple test ?

Wait for flickering
1. Remove ~/.cache/UBports/lomiri/qmlcache directory
```
rm -r /home/phablet/.cache/UBports/lomiri/qmlcache
```
2. See if there is still flickering (probably yes)
(if still flickering)
1. go to sleep mode (by quick power button pressure, for example)
2. resume (by quick button pressure)
3. see if there is still flickering
(if still flickering)
1. Close all open apps (morph, telegraph…)
2. see if there is still flickering (probably not)

If flickering is still here, redo the previous test but deleting ~/.cache/mesa_shader_cache directory this time

Thanks

Eric H

For information, before closing this thread :

The flickering issue has been fixed in 20.04 devel channel :

https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3/xiaomi-surya/-/commit/9d36e8d5986b2bf21afed7feff46baaa7c7535c9

Thanks to @_Joao_ and everybody on pocox3 telegram channel for their help