-
On Xiaomi Poco X3 NFC (surya), this issue has been reported here :
https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3/xiaomi-surya/-/issues/2 -
Hi @_Joao_
Can you find these files after your phone has crashed ?
/proc/last_kmsg
/sys/fs/pstore/*
-
yes but they are empty
-
@_Joao_ I upgraded to focal. Now, I can see the battery charge graph.
-
@eheintzmann that's cool, what's the procedure to switch to focal please?
-
Hi @_Joao_
I just chose the 20.04 focal development channel into the updater of the settings app (and I forced the reinstallation of all apps after the upgrade).
There are two (optional) updates a day in this channel.But now, after a week, I can see a few bugs.
- Camera and Barcode Readers apps does not work.
- Flashlight is not working via upper UT menu. (But sometimes it works with utorch)
- Sometimes Waydroid makes the phone crash.
-
@_Joao_
Please, forget what I've written about Camera and Barcodes apps :
I reinstalled Ubuntu Touch with the installer (wiping all data, using 20.04 Development channel). And now, all apps work fine on focal… -
@eheintzmann ok, the trick I found is to restart the phone before it does it on its own.
-
@eheintzmann hello, do you have any other reboot bugs since your last message?
-
@_Joao_ hello, sorry for the delay.
Yes, sadly, my phone still randomly reboot every day. -
@eheintzmann Is your phone up to date? I haven't had any random reboots for quite a while now.
-
@arubislander Yes, my phone is up-to-date. This is probably a surya only issue.
-
@eheintzmann oh, this is the Xiaomi section. I mistakenly assumed it was the Pixel 3a section. That devices used to have this same issue.
-
@eheintzmann What a shame this bug.
-
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?_=1700961879422As 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 ! -
@eheintzmann hi
Interesting... Maybe the battery is at the end of its life. I've been asking myself this question from the beginning. -
@_Joao_
Maybe yesBut
I've seen random reboot when plugged
I didn't see ant random reboots in airplane mode (plugged or unplugged)So maybe not…
-
-
@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...
-
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.
-
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/6096And the solution of the e-foujndation at :
https://gitlab.e.foundation/e/devices/android_device_fairphone_FP4/-/merge_requests/23/diffsSo maybe, setting two properties will solve the problem :
setprop persist.vendor.ssr.enable_ramdumps 0 setprop persist.vendor.ssr.restart_level ALL_ENABLE