ASUS UX305UA - Battery displayed as discharging at a rate of 0 even if full and on AC

Bug #1550964 reported by Michael Weimann
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

The system displays the battery as discharging event if it's fully charged and AC connected. The discharging rate is 0.

acpitool -a -b
  Battery #1 : Discharging, 100.0%
  AC adapter : online

acpitool -B
Battery #1 : present
    Remaining capacity : 56855 mWh, 100.0%
    Design capacity : 56041 mWh
    Last full capacity : 56855 mWh
    Present rate : 0 mW
    Charging state : Discharging
    Battery type : Li-ion
    Model number : ASUS

Notes:
• The latest BIOS is installed

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-30-generic 4.2.0-30.36
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mweimann 6047 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Feb 28 19:00:45 2016
HibernationDevice: RESUME=UUID=1c62ed80-e1a6-40bd-b496-e8e253dd0d80
InstallationDate: Installed on 2016-01-30 (29 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57cb Realtek Semiconductor Corp.
 Bus 001 Device 004: ID 046d:c31b Logitech, Inc. Compact Keyboard K300
 Bus 001 Device 002: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ DVI KVMP Switch]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305UA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=76d3ee0c-d0b2-4949-929c-e15a742b6541 ro quiet splash acpi_osi= vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-30-generic N/A
 linux-backports-modules-4.2.0-30-generic N/A
 linux-firmware 1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305UA.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UA.201:bd10/12/2015:svnASUSTeKCOMPUTERINC.:pnUX305UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1932 F.... pulseaudio
CasperVersion: 1.367
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
MachineType: ASUSTeK COMPUTER INC. UX305UA
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash ---
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-8-generic N/A
 linux-backports-modules-4.4.0-8-generic N/A
 linux-firmware 1.156
Tags: xenial
Uname: Linux 4.4.0-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305UA.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UA.201:bd10/12/2015:svnASUSTeKCOMPUTERINC.:pnUX305UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Michael Weimann (m982) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Michael Weimann, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-201
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Michael Weimann (m982) wrote :

Christopher M. Penalver this issue is still present using kernel 4.5.0-040500rc6-generic.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.5-rc6
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Michael Weimann (m982) wrote :

Note: Could be related to bug 1482390.

Revision history for this message
penalvch (penalvch) wrote :

Michael Weimann, to clarify, is this an issue in a prior release?

Also, it wouldn't hurt to rule out some wonky user space issue by testing http://cdimage.ubuntu.com/daily-live/current/ .

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Weimann (m982) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Michael Weimann (m982) wrote : CRDA.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : IwConfig.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : JournalErrors.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : Lspci.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : Lsusb.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : ProcModules.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : PulseList.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : RfKill.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : UdevDb.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote : WifiSyslog.txt

apport information

Revision history for this message
Michael Weimann (m982) wrote :

Christopher M. Penalver I had no previous Ubuntu versions installed on my device.

I also tested it with the latest daily ISO and uploaded the apport information.
The problem also occurs with the latest daily ISO (28-Feb-2016).

Revision history for this message
penalvch (penalvch) wrote :

Michael Weimann, to advise, you don't need to apport-collect further unless specifically requested to do so.

However, as you have tested both the latest mainline kernel, and release of Ubuntu, I'll go ahead and mark it Triaged.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Michael Weimann (m982) wrote :

This bug still appears on Ubuntu 16.04. Are there any news?

Revision history for this message
PabloAB (pabloab777) wrote :

Same here: Discharging but AC adapter online (?)

$ acpitool -a -b && acpitool -B && acpitool -A && uname -r && sudo dmidecode -t baseboard | grep "Manufacturer\|Product"
  Battery #1 : Discharging, 97.52%
  AC adapter : online
  Battery #1 : present
    Remaining capacity : 49213 mWh, 97.52%
    Design capacity : 52953 mWh
    Last full capacity : 50467 mWh, 95.31% of design capacity
    Capacity loss : 4.695%
    Present rate : 0 mW
    Charging state : Discharging
    Battery type : Li-ion
    Model number : ASUS
Sorry, but no Asus ACPI extensions were found on this system.
4.12.0-041200rc3-generic
        Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: UX303UB

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

When the battery's not full when charging, what's the charging state?

Revision history for this message
Muntakimur Rahman (muntakimur701) wrote :

Still facing the same problem in my Asus K401U laptop in Ubuntu 20.04lts.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.