PIN Code needed after a few hours

Ian

@eheintzmann You can check to see if your phone has rebooted by opening the terminal and entering

uptime

Followed by return. This should tell you how long your system has been up (since the last reboot). I'm sure this info used to be available from the GUI but I can't find it.

EDIT:

Install Ubuntu Info from the Openstore. Open it up and click on 'System', the uptime is displayed on about the 9th line.

Eric H

@arubislander

Are you sure it is your SIM card's pin code you need to enter?

Since I use same PIN code for SIM and device, yes, there is a
doubt.
As I remember, this morning it demanded two code.
I will confirm that next time it happens.

@Ian

You can check to see if your phone has rebooted by opening the terminal and entering uptime

I typed uptime -p into the terminal :
up 13 hours, 22 minutes

The device has rebooted in the night (~00:30) when I was sleeping

arubislander

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

As I remember, this morning it demanded two code.
I will confirm that next time it happens.

That makes sense, yes. One pin for the sim and one for device unlock. I am not sure which one gets asked for first.

Eric H

Same issue this morning…

@arubislander
The SIM pin is asked first :

The device pin is asked secondly :

Uptime command says the phone has rebooted again last night when i was sleeping :

uptime -s
2023-04-14 03:15:28

Eric H

I tried, in a terminal, as root, a :

grep -r -E "14 03:1[0-5]" /var/log

I got these messages (repeatedly, with different timestamps) in syslog

batt power supply prop 121 not supported
calculate esr condition not satisfy.
check_reduce_fcc_condition: cp_charge_enabled(0), charge_status(4), charge_type(1), batt_health(1)
GLib: Source ID 190 was not found when attempting to remove it
longcheer ,step_otg_chg_notifier_call:reverse_charge_state=0
[Networ][903861249927][01:14:42.391051] wlan: [2137:I:HDD] hdd_report_max_rate: 4201: Reporting legacy rate 540
QCOM-STEPCHG: handle_jeita: BATT_TEMP = 205 FCC = 6000000uA FV = 4480000uV
QCOM-STEPCHG: handle_jeita: BATT_TEMP = 206 FCC = 6000000uA FV = 4480000uV
QCOM-STEPCHG: handle_jeita: handle_jeita:fastcharge_mode=0
QCOM-STEPCHG: handle_jeita: lct ffc_chg_term_no_work=0
QG-K: qg_process_tcss_soc: [qg_process_tcss_soc] qg_iterm_ua=-350000
[schedu][902462849916][01:13:29.557718] wlan: [10250:W:PE] lim_process_probe_rsp_frame: 200: Recved Probe Resp from AP,AP-alive

Eric H

...and in repowerd.log

...
repowerd[1791]: UPowerPowerSourceAndLid: change_device(/org/freedesktop/UPower/devices/DisplayDevice), type=battery, is_present=1, state=fully_charged, percentage=100.00, temperature=0.00
repowerd[1791]: UPowerPowerSourceAndLid: change_device(/org/freedesktop/UPower/devices/battery_battery), type=battery, is_present=1, state=fully_charged, percentage=100.00, temperature=20.50
...
repowerd[1791]: UnityScreenService: dbus_emit_Wakeup()
repowerd[1791]: UnityScreenService: dbus_requestSysState(:1.119,ubuntu push client,1)
repowerd[1791]: UnityScreenService: dbus_requestSysState(:1.119,ubuntu push client,1) => 191
repowerd[1791]: DefaultStateMachine[c1]: disallow_suspend
repowerd[1791]: UnityScreenService: dbus_clearWakeup(:1.102,16931047011837021299)
repowerd[1791]: UnityScreenService: dbus_requestWakeup(:1.102,indicator-datetime,1683450000)
repowerd[1791]: UnityScreenService: dbus_requestWakeup(:1.102,indicator-datetime,1683450000) => 2510192338359437113

Eric H

The device rebooted itself again last night

uptime -s
2023-04-14 23:43:47

Eric H

@eheintzmann
The device continue to reboot every day.
And I have no idea why…

arubislander

@eheintzmann There was a similar issue on the Pixel 3a on Focal that has recently been fixed, if I am not mistaken. But as such I would think that it is a device specific issue. I wonder if any other users of the Poco X3 NFC are experiencing the same behavior. I will move your post to that sub-forum to increase it's visibility there.

arubislander

@arubislander A Poco X3 NFC subforum does not exist, and I do not seem to be able to create one. So I will move it to the Xiaomi subforum instead.

But while looking there I also found this post of a user with a similar issue.It would seem to be something that plagues this device in particular, so contacting the porter / maintainer would be a logical next step.

_Joao_

Hi Eheintzmann,
i have the same problem.

Eric H

@_Joao_
Hi,

I've updated to the latest 16.04 candidate (version 13) of Ubuntu Touch.
I'm going to watch, in the next days, if our issue is fixed in this version.

_Joao_

@eheintzmann
ok keep us posted

Eric H

@_Joao_
The phone rebooted again this morning.
According to https://devices.ubuntu-touch.io/device/surya#releaseChannels, the candidate version (13) of UT I used was released at the same date (4/17/2023) than the stable version (2). They are probably the same version.
I updated today to the development version (690). Let's see if it still reboots daily.

arubislander

@eheintzmann Software development is not magic. If something is causing your device to reboot daily, it will not fixed by randomly switching channels and applying updates. If the cause is not known, it is very unlikely to get fixed, even if by accident.

We need to go about this systematically.
First off, there is at least one other user with the same issue. This means there are probably more, but they hadn't noticed it as yet. The question is if there are others with this device that do not face the same issue? If so, then it is not an issue with the port. It may still have something to do with the state of the device before flashing UT on it, possibly, or some hardware state triggering a reboot. But that is move ahead of things.

The main question is: Do all Xiaomi Poco X3 NFC owners face daily automatic reboots on 16.04?

Eric H

@arubislander
I've read there is a hotfix for OTA 25. I would like to try this hotfix before contacting the porter. Since I didn't find information on versions in the candidate and development channel (is the hotfix applied ? Which bugs are fixed by the hotfix ?), what other options than testing them one after one ?

About the main question, are there other means to contact the other X3 NFC users than the UBPorts Forum ?

arubislander

@eheintzmann The hotfix tried (and possibly failed) to address an issue where devices would refuse to boot successfully. Your issue is totally different and will not have been addressed by the hotfix.

arubislander

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

are there other means to contact the other X3 NFC users than the UBPorts Forum ?

This is a good question. Maybe a query on the main Telegram chat group might help?

Eric H

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

The hotfix tried (and possibly failed) to address an issue where devices would refuse to boot successfully. Your issue is totally different and will not have been addressed by the hotfix.

OK, thanks for this information.
I will try to post to #ut_surya

Eric H

@arubislander
I posted the main question on #ut_surya and #ubports.
There was 5 answers :

3 users have similar issues.
1 user doesn't (but he uses 16.04 stable OTA April 1).
1 user says « I am note sure, but I think latest OTA had issues like this, maybe it is not fully fixed »