Issue metadata
Sign in to add a comment
|
[Peach-pi] power_supply_info show "discharging" with 0 voltage |
||||||||||||||||||||||
Issue descriptionGoogle Chrome : 53.0.2785.13 (Official Build) dev (32-bit) Revision : f88481b907e2fff8fd02eaf4043e66d86ff7bfb9-refs/branch-heads/2785@{#70} Platform : 8530.11.0 (Official Build) dev-channel peach_pi What steps will reproduce the problem? (1) Plug in AC power cable (2) Run "power_supply_info" (3) What is the expected output? It should show charging What do you see instead? It shows discharging However battery icon shows charging chronos@localhost / $ power_supply_info Device: Line Power path: /sys/class/power_supply/tps65090-ac online: yes type: Mains enum type: AC voltage (V): 0 current (A): 0 max voltage (V): 0 max current (A): 0 active source: tps65090-ac available sources: tps65090-ac* [/] supports dual-role: no Device: Battery path: /sys/class/power_supply/sbs-20-000b vendor: SDI model name: 4352D47 serial number: 00db state: Discharging voltage (V): 7.787 energy (Wh): 1.73 energy rate (W): 15.3793 current (A): 1.975 charge (Ah): 0.228 full charge (Ah): 4.529 full charge design (Ah): 4.7 percentage: 5.03422 display percentage: 1.11207 technology: Li-ion localhost / # ectool battery Battery version 0 is not supported Always reproducible ( tested 2 AC cables. 2 devices) Feedback report: http://feedback/#/Report/11145620634
,
Jul 12 2016
Please assign bugs like this to the device owners. power_supply_info just reports what it reads from the kernel. If the battery is discharging when it shouldn't be, it's a low-level issue rather than something that can be fixed in powerd.
,
Jul 13 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 1 2016
Is this issue still observed? After being plugged for some time, is 'power_supply_info' showing same? Do you see this only when percentage is small amount? What does 'ectool battery' show?
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 12 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 12 2018
Feel free to reopen after answering the questions in #4. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by helenzhang@chromium.org
, Jul 12 2016