Revision history [back]

Battery indicator got stuck in 4%.

Background: The phone was bought in the launch day and has had battery in and in normal daily use from since. Tohd.service has been stopped manually (not disabled) since the TOH-problem was found. Extra repositories in use are mer-tools and python3 repos.

The problem: Before this the battery had been dischanging normally for a day from 100%, and was at 49%, when suddenly the phone lost power. The phone was at the time in normal use, browsing internet with Opera on aliendalvik.

Powering on was successful and happened immediately after pressing the power button the required 1 to 2 seconds. Eg. no powering down happened which confirmed that the phone had just suddenly switched off and was in off state.

Now, after powering on, the battery status has frozen to 4%. It looks like there is more battery left, probably discharging normally from that 49% it had left before the power failure.

Dmesg shows get_prop_batt_capacity: low battery charge = 4% this event is reported every time the battery status is checked.

I checked the status of upower.service, and it showed that it was running. I also restarted it twice. Service restart was successful, but on the first go it gave an error: localhost upowerd[5173]: GLIB WARNING * UPower-Linux - did not recognise...ort* (This extra line to the normal report was what it said after running 'systemctl status upower.service')

The second time I restarted the service I did not get any errors.

I expect the problem to go away if I shutdown the phone down and remove the battery for couple of seconds. Before doing this I ask if there is any logs I should save or commands to run.

Battery indicator got stuck in 4%.

Background: The phone was bought in the launch day and has had battery in and in normal daily use from since. Tohd.service has been stopped manually (not disabled) since the TOH-problem was found. Extra repositories in use are mer-tools and python3 repos.

The problem: Before this the battery had been dischanging normally for a day from 100%, and was at 49%, when suddenly the phone lost power. The phone was at the time in normal use, browsing internet with Opera on aliendalvik.

Powering on was successful and happened immediately after pressing the power button the required 1 to 2 seconds. Eg. no powering down happened which confirmed that the phone had just suddenly switched off and was still in off state.

Now, after powering on, the battery status has frozen to 4%. It looks like there is more battery left, probably discharging normally from that 49% it had left before the power failure.

Dmesg shows get_prop_batt_capacity: low battery charge = 4% this event is reported every time the battery status is checked.

I checked the status of upower.service, and it showed that it was running. I also restarted it twice. Service restart was successful, but on the first go it gave an error: localhost upowerd[5173]: GLIB WARNING * UPower-Linux - did not recognise...ort* (This extra line to the normal report was what it said after running 'systemctl status upower.service')

The second time I restarted the service I did not get any errors.

I expect the problem to go away if I shutdown the phone down and remove the battery for couple of seconds. Before doing this I ask if there is any logs I should save or commands to run.

Battery indicator got stuck in 4%.

Background: The phone was bought in the launch day and has had battery in and in normal daily use from since. Tohd.service has been stopped manually (not disabled) since the TOH-problem was found. Extra repositories in use are mer-tools and python3 repos.

The problem: Before this the battery had been dischanging normally for a day from 100%, and was at 49%, when suddenly the phone lost power. The phone was at the time in normal use, browsing internet with Opera on aliendalvik.

Powering on was successful and happened immediately after pressing the power button the required 1 to 2 seconds. Eg. no powering down happened which confirmed that the phone had just suddenly switched off and was still in off state.

Now, after powering on, the battery status has frozen to 4%. It looks like there is more battery left, probably discharging normally from that 49% it had left before the power failure.

Dmesg shows shows

get_prop_batt_capacity: low battery charge = 4%

this event is reported every time the battery status is checked.

I checked the status of upower.service, and it showed that it was running. I also restarted it twice. Service restart was successful, but on the first go it gave an error: error:

localhost upowerd[5173]: GLIB WARNING * UPower-Linux - did not recognise...ort* recognise...ort*

(This extra line to the normal report was what it said after running 'systemctl status upower.service')

The second time I restarted the service I did not get any errors.

I expect the problem to go away if I shutdown the phone down and remove the battery for couple of seconds. Before doing this I ask if there is any logs I should save or commands to run.

Battery indicator got stuck in 4%.

Background: The phone was bought in the launch day and has had battery in and in normal daily use from since. Tohd.service has been stopped manually (not disabled) since the TOH-problem was found. Extra repositories in use are mer-tools and python3 repos.

The problem: Before this the battery had been dischanging normally for a day from 100%, and was at 49%, when suddenly the phone lost power. The phone was at the time in normal use, browsing internet with Opera on aliendalvik.

Powering on was successful and happened immediately after pressing the power button the required 1 to 2 seconds. Eg. no powering down happened which confirmed that the phone had just suddenly switched off and was still in off state.

Now, after powering on, the battery status has frozen to 4%. It looks like there is more battery left, probably discharging normally from that 49% it had left before the power failure.

Dmesg shows

get_prop_batt_capacity: low battery charge = 4%

this event is reported every time the battery status is checked.

I checked the status of upower.service, and it showed that it was running. I also restarted it twice. Service restart was successful, but on the first go it gave an error:

localhost upowerd[5173]: GLIB WARNING * UPower-Linux - did not recognise...ort*

(This extra line to the normal report was what it said after running 'systemctl status upower.service')

The second time I restarted the service I did not get any errors.

I expect the problem to go away if I shutdown the phone down and remove the battery for couple of seconds. Before doing this I ask if there is any logs I should save or commands to run.

Battery indicator got stuck in 4%.

Background: The phone was bought in the launch day and has had battery in and in normal daily use from since. Tohd.service has been stopped manually (not disabled) since the TOH-problem was found. Extra repositories in use are mer-tools and python3 repos.

The problem: Before this the battery had been dischanging normally for a day from 100%, and was at 49%, when suddenly the phone lost power. The phone was at the time in normal use, browsing internet with Opera on aliendalvik.

Powering on was successful and happened immediately after pressing the power button the required 1 to 2 seconds. Eg. no powering down happened which confirmed that the phone had just suddenly switched off and was still in off state.

Now, after powering on, the battery status has frozen to 4%. It looks like there is more battery left, probably discharging normally from that 49% it had left before the power failure.

Dmesg shows

get_prop_batt_capacity: low battery charge = 4%

this event is reported every time the battery status is checked.

I checked the status of upower.service, and it showed that it was running. I also restarted it twice. Service restart was successful, but on the first go it gave an error:

localhost upowerd[5173]: GLIB WARNING * UPower-Linux - did not recognise...ort*

(This extra line to the normal report was what it said after running 'systemctl status upower.service')

The second time I restarted the service I did not get any errors.

I expect the problem to go away if I shutdown the phone down and remove the battery for couple of seconds. Before doing this I ask if there is any logs I should save or commands to run.

EDIT: Here are the links to dmesg and journalctl -n 5000 outputs. The situation is still on.outputs.

dmesg

journalctl -n 5000