Battery applet never says fully charged Sony Vaio TX650

[Johnathon]

My battery says it is 100% charged and is still charging. It never shows as
fully charged. So, it seems like once 100% is found, that the icon would change
to just plugged-in and there would be no lightning symbol (and the text would no
longer say charging). This is on a Sony Vaio TX650.

[Johnathon (outdooricon)]

I'd like to note that this is different then some other bugs I've seen on here.
It doesn't show a battery icon when it's charging, it does correctly display the
plugged-un charging icon. The problem is that it never seems to reach a total
charged state.

[Daniel Holbach (dholbach)]

Thanks for your bug report. Which version of Ubuntu and gnome-applets do you
use? If you use Breezy, you might want to try to install a patched package from
http://people.ubuntu.com/~dholbach/gnome-applets/packages/

gnome-applets_2.12.1-0ubuntu1battstat_i386.deb and
gnome-applets-data_2.12.1-0ubuntu1battstat_all.deb should suffice on i386.

[Johnathon (outdooricon)]

I did as suggested and isntalled those packages. Still the same issue persists.

Here is my output from "acpi -V":
     Battery 1: charging, 100%, charging at zero rate - will never fully charge.

     Thermal 1: ok, 62.0 degrees C
     AC Adapter 1: on-line

[Johnathon (outdooricon)]

Oh, and to answer the other question, yes, I'm using Breezy.

[Daniel Holbach (dholbach)]

Ryan, you fixed this recently for Dapper, no? John, I guess we won't get the fix
into Breezy.

[Johnathon (outdooricon)]

(In reply to comment #5)
> Ryan, you fixed this recently for Dapper, no? John, I guess we won't get the fix
> into Breezy.

Ok, well, at least it should be better in April. Thanks.

[Carthik Sharma (carthik)]

So John, has this been fixed for you in Dapper Beta? If it is not a bug anymore, please let us know so we can close this bug.

Thank you for reporting this bug :)

[Johnathon (outdooricon)]

Carthik,
   I am unable to install dapper on that laptop right now. I'll be able to upgrade when Dapper Official is released but unfortunately I cannot test untill then. However, I will update this bug with my results as soon as i upgrade.

[Johnathon (outdooricon)]

This bug is not fixed. When the laptop is started while plugged in to AC power, it correctly shows no battery or plug-in icon in the notification area. However, once I unlpug the laptop, and then plug it back in, the battery icon once again says "Computer is running on AC power Laptop Battery Is Charging (100%)" and this never goes away. So, I would say this bug is half fixed.

[Johnathon (outdooricon)]

I also should mention that this is what I'm seeing in Dapper RC1.

[towsonu2003 (towsonu2003)]

Dapper up-to-date -> doesn't happen to me but used to happen intermittently 1-2 months ago.

[Daniel Holbach (dholbach)]

Thanks for following up. Closing the bug.

[Johnathon (outdooricon)]

This bug needs to be reopened as it is happening in Edgy now.

[thewall83 (vitorenna)]

Same problem here with a Sony Vaio FE11H on Ubuntu Edgy.

[Daniel Holbach (dholbach)]

Does it happen with Feisty?

[Johnathon (outdooricon)]

Yes, this is still happening in Feisty.

[thewall83 (vitorenna)]

Same here, with Ubuntu Feisty.

[unggnu (unggnu)]

I have the same problem with Feisty but I have read somewhere that the same problem appears under Windows so it seems to be a Sony ACPI bug. If I check the battery info under proc design capacity and last full capacity are the same so it seems to work. Maybe there is a workaround needed for the kernel.

[Toufik (toufik2)]

I've got a Vaio and discover the problem today while trying to make a widget which display my battery state. The problem seems to be related with ACPI. Indeed, here is my /proc/acpi/battery/BAT0/state when I'm 100% full

present: yes
capacity state: ok
charging state: charging
present rate: unknown
remaining capacity: 4800 mAh
present voltage: unknown

2 problems:
* charging state never changes --> this is the problem in this bug
* present rate keeps saying unknown, even at charge or discharge --> this is why I have no indication of the remaining time from the applet

To be complete, here is /proc/acpi/battery/BAT0/info

present: yes
design capacity: 4800 mAh
last full capacity: 4800 mAh
battery technology: non-rechargeable
design voltage: 12547 mV
design capacity warning: 1000 mAh
design capacity low: 400 mAh
capacity granularity 1: 100 mAh
capacity granularity 2: 100 mAh
model number:
serial number:
battery type: LiOn
OEM info: Sony Corp.

My battery is non-rechargeable :)

Feisty on a Sony Vaio VGN-FS315

Toufik

[Pedro Villavicencio (pedro)]

May someone try to reproduce this bug with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ ; thanks in advance.

[unggnu (unggnu)]

Tribe 5 still has the same problem. But I have read somewhere that Windows has the same problem. It seems to be an acpi or design bug. Maybe only a workaround is possible.

ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charging
present rate: 0 mW
remaining capacity: 57720 mWh
present voltage: 8392 mV

ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 57720 mWh
last full capacity: 57720 mWh
battery technology: non-rechargeable
design voltage: 7400 mV
design capacity warning: 0 mWh
design capacity low: 120 mWh
capacity granularity 1: 0 mWh
capacity granularity 2: 10 mWh
model number:
serial number:
battery type: LION
OEM info: Sony Corp.

[ddoxey (dylan-doxey)]

My Sony Vaio has a related problem, although the symptom is different.

Symptom: Battery state always reads 100%.

This is a fresh install of Xubuntu Gutsy Gibbon.

dylan@yuki:~$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: discharging
present rate: 103400 mW
remaining capacity: 36000 mWh
present voltage: 11626 mV

dylan@yuki:~$ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 36000 mWh
last full capacity: 36000 mWh
battery technology: non-rechargeable
design voltage: 155 mV
design capacity warning: 0 mWh
design capacity low: 120 mWh
capacity granularity 1: 0 mWh
capacity granularity 2: 10 mWh
model number:
serial number:
battery type: LION
OEM info: Sony Corp.

The present voltage value declines while the battery discharges, but the remaining capacity remains steady.

[ddoxey (dylan-doxey)]

I suspect the battery applet problem is a symptom of the known acpi kernel bug.

"Kernel detects battery management wrong"
https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/147560

Aside from that, regarding Pedro's comment on 2007-08-17:
Is running a live CD more informative than a complete installation?

[Leann Ogasawara (leannogasawara)]

I'm retargeting this bug towards the upcoming Hardy kernel and have tagged it as "hardy-kernel-candidate". However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

[Leann Ogasawara (leannogasawara)]

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

[unggnu (unggnu)]

It still happens in current Hardy. I have inserted a full battery and it still tells me that the battery is charged. Btw. the point non-rechargeable is wrong too.

cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charging
present rate: 0 mW
remaining capacity: 57720 mWh
present voltage: 8354 mV

cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 57720 mWh
last full capacity: 57720 mWh
battery technology: non-rechargeable
design voltage: 7400 mV
design capacity warning: 0 mWh
design capacity low: 120 mWh
capacity granularity 1: 0 mWh
capacity granularity 2: 10 mWh
model number:
serial number:
battery type: LION
OEM info: Sony Corp.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jim Lieb (lieb)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.

[unggnu (unggnu)]

This is still an issue in Jaunty with default Kernel and 2.6.30-rc3.
Btw. it is an acpi issue which happens under Win too so obviously it needs a quirk.

[Leann Ogasawara (leannogasawara)]

Could you attach your dmidecode?

sudo dmidecode > dmidecode.log

[penalvch (penalvch)]

Johnathon, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Johnathon (outdooricon)]

I am unable to test this as I no longer have a battery for that laptop. Would anyone else be able to?

[dino99 (9d9)]

This version has expired