Jump to content

Android 11&12 Charging issue. Reproducible trigger method.


Recommended Posts

We have in the lineage threads for 18 and 19, as well as AICP-R had a number of posts on a strange charging issue, where it keeps the battery at a stable level, neither charging nor discharging while connected.

This seems not to be limited to the Pro1, but is an issue that also affects the Pro1.

See the post I made here in the Lineage 19 thread.

Unfortunately this common problem is rather illusive, as it is not easy to say how to trigger or avoid it. All we know for sure is that it is temporarily gone after a reboot.

I have tried multiple times to find a 100% reproducible method, but today I might have some sort of a breakthrough:

I had the issue (at 29%) earlier today and then did this

  • Rebooted while connected
  • Did NOT enter the password but waited at few minutes
  • Picked it up while disconnecting, entered the password, and put it back on the table while connecting.

And it did NOT charge! I let it be on the table -starting typing info on this- and it did a spontaneous reboot(!!).
(Note that it did charge to 35% in the period before I entered the password)
Repeated the last two dots, and it still did not charge (but this time no spontaneous reboot).

I repeated it a third time, and this time it DID charge.

I then tried to repeat it some five more times afterwards, NOT being able to trigger it again. So could be some timing that has to be in a particular window to trigger (or not trigger) it...

I did it again waiting long before entering the password (now at 50%). And this DID trigger it!
So though not a 100% easy to use method there clearly is a pattern, that might be investigated further, for a 100% reproducible way!

I can not say for sure whether or not I by reflex have touched the fingerprint sensor during each pick up, but I think I did on most.

So if anyone want to spent some time digging further into this, it would be great, as a reproducible method is the first step in making an error report so someone can do what ever it takes in the Lineage&AICP distributions to circumvent the bug.

  • Thanks 4
Link to post
Share on other sites

Interesting.
I had the problem very very often with LOS18.1 (I had always to reboot once the phone has been charging one time) , then I flashed LOS19.1 (wiping data), and I had (quickly) the same behaviour (but my fingerprint sensor worked, wtf ?).
Then I reflashed LOS18.1 (also wiping data), and I had only the problem two or three time in three weeks of use (and fingerprint sensor works quite all the time, wich wasn't the case in LOS17.1 and first installation from LOS18.1).
Very strange.

Link to post
Share on other sites

With the latest build, I'm having this issue no matter what. The previous build did a better job in that respect. No matter what I try or which charger I use, I just used my original charger for the very first time in 2 years, it won't start charging since I installed this build a couple of days ago. 

Back to rebooting every charge. And still no GPS fix by the way. Almost immediately 20 sats, but never a fix.

And, mine starts charging as soon as the boot logo is gone!

Edited by DieBruine
  • Sad 2
Link to post
Share on other sites
  • 2 weeks later...

 

On 7/22/2022 at 7:27 AM, DieBruine said:

With the latest build, I'm having this issue no matter what.

Maybe they changed something for the worse? That could be why it was so relatively easy to trigger it here too?
(reposting this as i had to steal an old post....)

  • Like 1
Link to post
Share on other sites
  • 2 weeks later...

Bad news! This ALSO seems to hit stock Android 11 on the Pro1X 😭

ADD: Though it seems that unplugging and re-plugging here several times can suddenly bring it back to normal, so not as bad as what we see on Lineage. and AICP.

  • Like 1
  • Sad 1
Link to post
Share on other sites
  • 4 weeks later...
On 7/21/2022 at 10:00 AM, EskeRahn said:

We have in the lineage threads for 18 and 19, as well as AICP-R had a number of posts on a strange charging issue, where it keeps the battery at a stable level, neither charging nor discharging while connected.

This seems not to be limited to the Pro1, but is an issue that also affects the Pro1.

See the post I made here in the Lineage 19 thread.

Unfortunately this common problem is rather illusive, as it is not easy to say how to trigger or avoid it. All we know for sure is that it is temporarily gone after a reboot.

I have tried multiple times to find a 100% reproducible method, but today I might have some sort of a breakthrough:

I had the issue (at 29%) earlier today and then did this

  • Rebooted while connected
  • Did NOT enter the password but waited at few minutes
  • Picked it up while disconnecting, entered the password, and put it back on the table while connecting.

And it did NOT charge! I let it be on the table -starting typing info on this- and it did a spontaneous reboot(!!).
(Note that it did charge to 35% in the period before I entered the password)
Repeated the last two dots, and it still did not charge (but this time no spontaneous reboot).

I repeated it a third time, and this time it DID charge.

I then tried to repeat it some five more times afterwards, NOT being able to trigger it again. So could be some timing that has to be in a particular window to trigger (or not trigger) it...

I did it again waiting long before entering the password (now at 50%). And this DID trigger it!
So though not a 100% easy to use method there clearly is a pattern, that might be investigated further, for a 100% reproducible way!

I can not say for sure whether or not I by reflex have touched the fingerprint sensor during each pick up, but I think I did on most.

So if anyone want to spent some time digging further into this, it would be great, as a reproducible method is the first step in making an error report so someone can do what ever it takes in the Lineage&AICP distributions to circumvent the bug.

(You need rooting to do this)

May you please try getting the output from running this in your own PC with the phone connected?

adb shell su -c "grep '.*' /sys/class/power_supply/battery/voltage_*"

 

Link to post
Share on other sites
21 minutes ago, brunoais said:

(You need rooting to do this)

May you please try getting the output from running this in your own PC with the phone connected?

adb shell su -c "grep '.*' /sys/class/power_supply/battery/voltage_*"

 

You want to see this when the issue is there I assume?
On AICP and LOS, Rooting is not needed as such.

adb root
adb shell "grep '.*' /sys/class/power_supply/battery/voltage_*"
adb unroot

returns something

/sys/class/power_supply/battery/voltage_max:4400000
/sys/class/power_supply/battery/voltage_now:4204334
/sys/class/power_supply/battery/voltage_qnovo:-22

and

/sys/class/power_supply/battery/voltage_max:4400000
/sys/class/power_supply/battery/voltage_now:3819082
/sys/class/power_supply/battery/voltage_qnovo:-22

on two different Pro1

The bug is not present at this moment on the first one, but is present on the second, ignoring charging, and pulling about 0.020A with screen OFF and 0.114A with screen ON

Link to post
Share on other sites
46 minutes ago, EskeRahn said:

You want to see this when the issue is there I assume?
On AICP and LOS, Rooting is not needed as such.

adb root
adb shell "grep '.*' /sys/class/power_supply/battery/voltage_*"
adb unroot

returns something

/sys/class/power_supply/battery/voltage_max:4400000
/sys/class/power_supply/battery/voltage_now:4204334
/sys/class/power_supply/battery/voltage_qnovo:-22

and

/sys/class/power_supply/battery/voltage_max:4400000
/sys/class/power_supply/battery/voltage_now:3819082
/sys/class/power_supply/battery/voltage_qnovo:-22

on two different Pro1

The bug is not present at this moment on the first one, but is present on the second, ignoring charging, and pulling about 0.020A with screen OFF and 0.114A with screen ON

 

That one didn't show me...
Let's try everything, then:

adb shell "grep '.*' /sys/class/power_supply/battery/*"

This can be a change in the capacity.

While on it, this can help too understanding if there's changes in "file" permissions there.

adb shell "ls -la /sys/class/power_supply/battery/*"

 

Link to post
Share on other sites
8 hours ago, brunoais said:

While on it, this can help too understanding if there's changes in "file" permissions there.

When the bug is present:

 

C:\Util\ADB>adb shell "grep '.*' /sys/class/power_supply/battery/*"
/sys/class/power_supply/battery/capacity:85
/sys/class/power_supply/battery/charge_counter:2491300
/sys/class/power_supply/battery/charge_done:0
/sys/class/power_supply/battery/charge_full:2906000
/sys/class/power_supply/battery/charge_type:N/A
/sys/class/power_supply/battery/charger_temp:296
/sys/class/power_supply/battery/charger_temp_max:812
/sys/class/power_supply/battery/constant_charge_current_max:-22000
/sys/class/power_supply/battery/current_now:-3417
/sys/class/power_supply/battery/current_qnovo:-22
/sys/class/power_supply/battery/cycle_count:5
/sys/class/power_supply/battery/die_health:Cool
/sys/class/power_supply/battery/dp_dm:0
/sys/class/power_supply/battery/fcc_stepper_enable:0
grep: /sys/class/power_supply/battery/device: Is a directory
/sys/class/power_supply/battery/health:Good
/sys/class/power_supply/battery/input_current_limited:0
/sys/class/power_supply/battery/input_suspend:0
/sys/class/power_supply/battery/parallel_disable:0
grep: /sys/class/power_supply/battery/power: Is a directory
/sys/class/power_supply/battery/present:1
/sys/class/power_supply/battery/rerun_aicl:0
/sys/class/power_supply/battery/set_ship_mode:0
/sys/class/power_supply/battery/status:Not charging
/sys/class/power_supply/battery/step_charging_enabled:0
grep: /sys/class/power_supply/battery/subsystem: Is a directory
/sys/class/power_supply/battery/sw_jeita_enabled:0
/sys/class/power_supply/battery/system_temp_level:0
/sys/class/power_supply/battery/technology:Li-ion
/sys/class/power_supply/battery/temp:240
/sys/class/power_supply/battery/type:Battery
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_NAME=battery
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_INPUT_SUSPEND=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_STATUS=Not charging
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_HEALTH=Good
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_PRESENT=1
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_TYPE=N/A
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CAPACITY=85
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_SYSTEM_TEMP_LEVEL=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGER_TEMP=296
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGER_TEMP_MAX=812
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_INPUT_CURRENT_LIMITED=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_VOLTAGE_NOW=4167713
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_VOLTAGE_MAX=4400000
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_VOLTAGE_QNOVO=-22
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CURRENT_NOW=-3417
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CURRENT_QNOVO=-22
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CONSTANT_CHARGE_CURRENT_MAX=-22000
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_TEMP=240
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_TECHNOLOGY=Li-ion
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_STEP_CHARGING_ENABLED=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_SW_JEITA_ENABLED=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_DONE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_PARALLEL_DISABLE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_SET_SHIP_MODE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_DIE_HEALTH=Cool
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_RERUN_AICL=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_DP_DM=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_COUNTER=2491300
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_FCC_STEPPER_ENABLE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_FULL=2906000
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CYCLE_COUNT=5
/sys/class/power_supply/battery/voltage_max:4400000
/sys/class/power_supply/battery/voltage_now:4167713
/sys/class/power_supply/battery/voltage_qnovo:-22

C:\Util\ADB>adb shell "ls -la /sys/class/power_supply/battery/*"
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/capacity
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_counter
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_done
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_full
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_type
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charger_temp
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charger_temp_max
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/constant_charge_current_max
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/current_now
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/current_qnovo
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/cycle_count
lrwxrwxrwx 1 root root    0 1972-06-25 08:20 /sys/class/power_supply/battery/device -> ../../../800f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smb2
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/die_health
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/dp_dm
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/fcc_stepper_enable
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/health
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/input_current_limited
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/input_suspend
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/parallel_disable
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/present
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/rerun_aicl
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/set_ship_mode
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/status
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/step_charging_enabled
lrwxrwxrwx 1 root root    0 1972-06-25 08:20 /sys/class/power_supply/battery/subsystem -> ../../../../../../../../class/power_supply
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/sw_jeita_enabled
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/system_temp_level
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/technology
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/temp
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/type
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/uevent
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/voltage_max
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/voltage_now
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/voltage_qnovo

/sys/class/power_supply/battery/power:
total 0
drwxr-xr-x 2 root root    0 2022-09-06 13:54 .
drwxr-xr-x 3 root root    0 2022-09-06 13:54 ..
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 control
-r--r--r-- 1 root root 4096 2022-09-06 13:54 runtime_active_time
-r--r--r-- 1 root root 4096 2022-09-06 13:54 runtime_status
-r--r--r-- 1 root root 4096 2022-09-06 13:54 runtime_suspended_time
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 wakeup
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_abort_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_active
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_active_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_expire_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_last_time_ms
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_max_time_ms
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_prevent_sleep_time_ms
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_total_time_ms

 

Link to post
Share on other sites

 

51 minutes ago, EskeRahn said:

When the bug is present:

 

C:\Util\ADB>adb shell "grep '.*' /sys/class/power_supply/battery/*"
/sys/class/power_supply/battery/capacity:85
/sys/class/power_supply/battery/charge_counter:2491300
/sys/class/power_supply/battery/charge_done:0
/sys/class/power_supply/battery/charge_full:2906000
/sys/class/power_supply/battery/charge_type:N/A
/sys/class/power_supply/battery/charger_temp:296
/sys/class/power_supply/battery/charger_temp_max:812
/sys/class/power_supply/battery/constant_charge_current_max:-22000
/sys/class/power_supply/battery/current_now:-3417
/sys/class/power_supply/battery/current_qnovo:-22
/sys/class/power_supply/battery/cycle_count:5
/sys/class/power_supply/battery/die_health:Cool
/sys/class/power_supply/battery/dp_dm:0
/sys/class/power_supply/battery/fcc_stepper_enable:0
grep: /sys/class/power_supply/battery/device: Is a directory
/sys/class/power_supply/battery/health:Good
/sys/class/power_supply/battery/input_current_limited:0
/sys/class/power_supply/battery/input_suspend:0
/sys/class/power_supply/battery/parallel_disable:0
grep: /sys/class/power_supply/battery/power: Is a directory
/sys/class/power_supply/battery/present:1
/sys/class/power_supply/battery/rerun_aicl:0
/sys/class/power_supply/battery/set_ship_mode:0
/sys/class/power_supply/battery/status:Not charging
/sys/class/power_supply/battery/step_charging_enabled:0
grep: /sys/class/power_supply/battery/subsystem: Is a directory
/sys/class/power_supply/battery/sw_jeita_enabled:0
/sys/class/power_supply/battery/system_temp_level:0
/sys/class/power_supply/battery/technology:Li-ion
/sys/class/power_supply/battery/temp:240
/sys/class/power_supply/battery/type:Battery
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_NAME=battery
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_INPUT_SUSPEND=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_STATUS=Not charging
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_HEALTH=Good
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_PRESENT=1
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_TYPE=N/A
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CAPACITY=85
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_SYSTEM_TEMP_LEVEL=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGER_TEMP=296
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGER_TEMP_MAX=812
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_INPUT_CURRENT_LIMITED=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_VOLTAGE_NOW=4167713
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_VOLTAGE_MAX=4400000
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_VOLTAGE_QNOVO=-22
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CURRENT_NOW=-3417
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CURRENT_QNOVO=-22
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CONSTANT_CHARGE_CURRENT_MAX=-22000
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_TEMP=240
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_TECHNOLOGY=Li-ion
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_STEP_CHARGING_ENABLED=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_SW_JEITA_ENABLED=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_DONE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_PARALLEL_DISABLE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_SET_SHIP_MODE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_DIE_HEALTH=Cool
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_RERUN_AICL=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_DP_DM=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_COUNTER=2491300
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_FCC_STEPPER_ENABLE=0
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CHARGE_FULL=2906000
/sys/class/power_supply/battery/uevent:POWER_SUPPLY_CYCLE_COUNT=5
/sys/class/power_supply/battery/voltage_max:4400000
/sys/class/power_supply/battery/voltage_now:4167713
/sys/class/power_supply/battery/voltage_qnovo:-22

C:\Util\ADB>adb shell "ls -la /sys/class/power_supply/battery/*"
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/capacity
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_counter
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_done
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_full
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charge_type
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charger_temp
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/charger_temp_max
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/constant_charge_current_max
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/current_now
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/current_qnovo
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/cycle_count
lrwxrwxrwx 1 root root    0 1972-06-25 08:20 /sys/class/power_supply/battery/device -> ../../../800f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smb2
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/die_health
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/dp_dm
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/fcc_stepper_enable
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/health
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/input_current_limited
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/input_suspend
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/parallel_disable
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/present
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/rerun_aicl
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/set_ship_mode
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/status
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/step_charging_enabled
lrwxrwxrwx 1 root root    0 1972-06-25 08:20 /sys/class/power_supply/battery/subsystem -> ../../../../../../../../class/power_supply
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/sw_jeita_enabled
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/system_temp_level
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/technology
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/temp
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/type
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/uevent
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/voltage_max
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/voltage_now
-r--r--r-- 1 root root 4096 2022-09-06 13:54 /sys/class/power_supply/battery/voltage_qnovo

/sys/class/power_supply/battery/power:
total 0
drwxr-xr-x 2 root root    0 2022-09-06 13:54 .
drwxr-xr-x 3 root root    0 2022-09-06 13:54 ..
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 control
-r--r--r-- 1 root root 4096 2022-09-06 13:54 runtime_active_time
-r--r--r-- 1 root root 4096 2022-09-06 13:54 runtime_status
-r--r--r-- 1 root root 4096 2022-09-06 13:54 runtime_suspended_time
-rw-r--r-- 1 root root 4096 2022-09-06 13:54 wakeup
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_abort_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_active
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_active_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_expire_count
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_last_time_ms
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_max_time_ms
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_prevent_sleep_time_ms
-r--r--r-- 1 root root 4096 2022-09-06 13:54 wakeup_total_time_ms

 

Oh! This is wrong!

51 minutes ago, EskeRahn said:
/sys/class/power_supply/battery/constant_charge_current_max:-22000

 

What happens if you (as root):

chmod 644 /sys/class/power_supply/battery/constant_charge_current_max
echo 22000 > /sys/class/power_supply/battery/constant_charge_current_max

But that may not be enough... If the % doesn't change in about 20 mins, try:

chmod 644 /sys/class/power_supply/battery/constant_charge_current_max
echo 40000 > /sys/class/power_supply/battery/constant_charge_current_max

That should be enough for the phone to start charging significantly.

Do execute this from time to time to confirm if it's being overridden by something else:

cat /sys/class/power_supply/battery/constant_charge_current_max

Let me know what you are able to figure out with this info...

Edited by brunoais
  • Like 1
  • Thanks 1
Link to post
Share on other sites
13 hours ago, brunoais said:

Oh! This is wrong!

14 hours ago, EskeRahn said:

/sys/class/power_supply/battery/constant_charge_current_max:-22000

 

 

It looks this way no matter if charging is working or not. So not an indicator as such.
And do not get fooled by the sign. Some phones reports charging as negative (e.g. Pro1 and Samsung S8-) other reports usage as negative  (e.g. Titan Slim).

I see this in "3C All-In-One Toolbox", that there is disagreement on the sign between different models..

 

Link to post
Share on other sites
1 hour ago, EskeRahn said:

It looks this way no matter if charging is working or not. So not an indicator as such.
And do not get fooled by the sign. Some phones reports charging as negative (e.g. Pro1 and Samsung S8-) other reports usage as negative  (e.g. Titan Slim).

I see this in "3C All-In-One Toolbox", that there is disagreement on the sign between different models..

 

In that case, try using a negative number instead:

echo "-40000" > /sys/class/power_supply/battery/constant_charge_current_max

(FYI: Pro¹-X uses positive numbers here)

Edited by brunoais
FYI
Link to post
Share on other sites

That variable has the same value on my Pro1.

rostkatze:~ # cat /sys/class/power_supply/battery/constant_charge_current_max
-22000

I'm still running LOS 16.0 and never had the charging bug. Whatever that number means, I think it is unlikely that this is the right track ...

  • Like 1
  • Thanks 2
Link to post
Share on other sites
3 hours ago, EskeRahn said:

I'm not too happy about messing with the system files, and as the numbers are the same when charging the battery works and when it does not, it is unlikely to be relevant.

These numbers are reset if you reboot the phone, though.

However, it appears like the issue isn't there. Given so, it might be in the drivers or it can be something I'm missing...

  • Like 2
Link to post
Share on other sites
On 9/12/2022 at 11:53 AM, EskeRahn said:

Noticed THIS difference:

image.thumb.png.a5c6a80ade560a7aaf904420a9dfe28b.png

And POWER_SUPPLY_INPUT_CURRENT_LIMITED sounds very much like what has been my theory all along.....
The big question is how to avoid this state being triggered too soon though....

From the kernel/driver side, that switch is actually controlled manually and not automatically. It's supposed to be controlled by a userland program which sets that value. I was going to jump to that one after 

constant_charge_current_max

but you mentioned you didn't want o continue, so I stopped.

the `uevent` file is just providing all data from other files with some extras. In this case, the culprit is:

/sys/class/power_supply/battery/charge_control_limit

In my phone, there's 7 settings for it (between 0 and 6). Basically, it's a choice of how fast to charge. I think my device can only use 0-4. I can't see a difference between 4/5/6 when using the provided charger and cable. I almost always set it to either 0 or 1. There should be a service in your phone setting it to 0 in order to stop charging. I wonder what and why...

Edited by brunoais
Clarifying what I mean by "manual control"
  • Thanks 2
Link to post
Share on other sites
  • 1 month later...

Got the Pro1X in a state where it refused to charge even during and after after a restart. And did not charge powered down either - well it indicated that it did, but only pulled 0.07A, 5V. So only sustained the usage, no charging.

A deeper restart by holding the power-button for several seconds fixed it (for now?)

That was a (for me) new variant of the bug..... Anyone else had that variant?

Link to post
Share on other sites

Interesting... For me, there no charging problems with the Pro1X so far (except in one case, but I could pin that down to a specific cable + magnetic adapter issue, even though both items are new and seem clean, too)...

 

  • Thanks 1
Link to post
Share on other sites
  • 1 month later...
9 hours ago, Tomatoman29 said:

Connecting any OTG device fixes the charging problem. 

 

31 minutes ago, EskeRahn said:

Interesting, will try that next time - had it on two devices earlier today...

Interesting indeed. I have something that maybe related to share, I wasn't sure what to think of it before...

For a while I'm now using magnetic USB C connector and cable and since then I did not have any charging issue on both my Pro1 and my Pro1X.

By the number of contacts, I expect only USB 2.0 signaling is supported (just like the included charger). I am not sure what is really different except that connection is generally instant rather than relatively slow to reach all contacts.

  • Like 2
  • Thanks 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

Terms