Battery acting weird on Gnawty
Reported by
factor...@gmail.com,
Feb 12 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10176.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.144 Safari/537.36 Platform: 10176.68.0 (Official Build) stable-channel gnawty Steps to reproduce the problem: 1. charge the Chromebook to 100% 2. keep working on it while on AC 3. after a while see the power indicator showing a charge value significantly lower than 100% What is the expected behavior? What went wrong? The battery on my Chromebook is acting weird. Please take a look at the powerd log attached. You can see that on AC it apparently charged up to 3.766 Ah which is well above the charge_full_design value of 3.220 Ah as shown in power_supply_sysfs. Then, while still on AC, it suddenly dropped to 77% with charge of 2.888/3.766 Ah. Please note that I did not mess with the adapter or the power supply in any way, it just happened by itself. Then, when I turned off the power supply, switching to battery, the indicator jumped back from 77% to 100% with 3.006 Ah charge. In this state, when I run the battery_test the battery charge does not decrease - the test result says "Battery discharged 0.00% in 300 second(s). Did this work before? N/A Chrome version: 64.0.3282.144 Channel: stable OS Version: 10176.68.0 Flash Version:
,
Feb 16 2018
,
Feb 16 2018
Just capturing relevant lines from powerd, [0212/140842:INFO:daemon.cc(776)] On AC (Mains) with battery at 100%, 3.723/3.723Ah at 0.583A, full [0212/141106:INFO:daemon.cc(776)] On AC (Mains) with battery at 100%, 3.744/3.744Ah at 0.536A, full [0212/141824:INFO:daemon.cc(776)] On AC (Mains) with battery at 100%, 3.766/3.766Ah at 0.419A, full [0212/144225:INFO:daemon.cc(776)] On AC (Mains) with battery at 77% (displayed as 78%), 2.888/3.766Ah at 0.196A [0212/145619:INFO:daemon.cc(776)] On AC (Mains) with battery at 100%, 3.006/3.006Ah at 0.236A, full [0212/150054:INFO:daemon.cc(776)] On AC (Mains) with battery at 100%, 3.006/3.006Ah at 0.000A, full I'm not aware of similar reports on this board. In the past I have seen bogus readings due to i2c failures but this seems differnent than those. Vincent this sound familiar?
,
Mar 9 2018
Hi Eason, Can you help to assign this bug to your battery team to have a look. Thanks.
,
Mar 12 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by factor...@gmail.com
, Feb 12 201830.9 KB
30.9 KB View Download
909 bytes
909 bytes View Download
598 bytes
598 bytes View Download