Logitech MX1000 Battery

Bug #163649 reported by Martin Wimmer on 2007-11-18
70
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

With Feisty my Logitech MX1000 mouse always reported its battery level correctly. Since the upgrade to feisty, it always reports a battery level of 35%, which means that I always get a battery low message when gnome starts.

Also it would be nice if all mouse buttons worked by default, but that's not the issue of this bug report ;)

Martin Wimmer,
Do you need to activate some panel applet to show you the battery level?
Is this still a problem with gutsy or the latest development release hardy?

Martin Wimmer (martin-wimmer) wrote :

No, didn't have to activate anything. This error Message still appears under gutsy, couldn't test it yet under hardy.

The interesting thing is, that it's always stuck at 35% as long as the real capacity is higher than that. It works correctly as soon as the capacity drops under 35%

Is this still an issue with Ubuntu 8.04 or Intrepid, the current Ubuntu development version?

DavidGN (davidgn) wrote :

Still an issue in 8.04 + 8.10a2 - see https://bugs.launchpad.net/ubuntu/+bug/251498

DavidGN (davidgn) wrote :

From my comment at https://bugs.launchpad.net/ubuntu/+bug/251498, I can confirm it's the MX1000 and not my other mouse.

dmsuperman (dmsuperman) wrote :

I have an MX600 and it does it for me. It's popped up 14% charge for a week now. If this is accurate, can we at least get the ability to change this threshold? My batteries last me for months, so 14% is pretty high.

robled (robled) wrote :

100% reproducible on my Hardy system with a Logitech MX700 mouse.

Feanor (michael.pusterhofer) wrote :

On jaunty the battery status is updated only on boot up and on events. A powerhistory seems not to be available right now.
The power management says that the mouse battery is empty when i start loading the mouse (= 14%) and the details show discharging.

42% did also occur when i use the mouse. I think this is the value my mouse battery at boot up.

Feanor (michael.pusterhofer) wrote :

the debug is made at adding the mouse to the battery loading station. wait until the low battery message and removing it from the station. maybe it helps.

Guy Kroizman (kroizguy) wrote :

I have the same problem for years now.
constant notifications about low mouse battery (14%) regardless of the actual battery capacity.
current ubuntu is 9.10 (the problem is at least 3 ubuntu versions old)
mouse is wireless Logitech.

Chris Hillery (ceejatec) wrote :

I have this problem also with a Logitech Cordless Mouseman Optical. I have only had this problem with Karmic, however.

It always reports battery level of 14.3%. It does it fairly regularly throughout my session; it is not restricted to login time. This makes it incredibly annoying.

If this cannot be fixed, we really at least need a way to turn OFF this notification. I'm happy to wait until I notice that my mouse is skipping before getting around to replacing the batteries. (This is an older mouse which takes AA batteries, so there's no docking involved.)

dbruce100 (dbrucepoip) wrote :

Same issue under Karmic. Older Logitech Optical Mouse. alerts related to battery happen constantly with mo way to disable.

As others have mentioned, turning it off would be a big +

Fraxtil (fraxtil) wrote :

Confirming this issue with a Logitech Cordless Optical Mouse. Disabling all gnome-power-manager notifications does not disable the low mouse battery notification.

Bob Herrmann (bob-jadn) wrote :

I'm getting these a lot today.. and they are annoying... I'd prefer not to see them. I'm on a daily synced up version of 10.04

Bob Herrmann (bob-jadn) wrote :

My mouse is a Logitech Cordless Optical mouse model M-RM67A. Message always says 14.3%

Dan Quade (danquade) wrote :

Same problem on Ubuntu 10.10. MX1000 either shows 14.3% when low or 100% when above low. Clearly wrong.

Changed in ubuntu:
status: Incomplete → Confirmed
b (ben-ekran) wrote :

I confirm on lucid with my logitech cordless mouseman optical (M-RM64) also showing 14.3 percent a few days before I'll need to charge.

I confirm the identical behaviour with my Logitech cordless MX-1000 (Logitech part M-RAG97). It has behaved the same way for me on *every* release of Ubuntu since release 8.04 (Hardy Heron) up to and including the current Ubuntu 11.10 (Oneiric Ocelot) release.

Phillip Susi (psusi) wrote :

If this is still an issue on 12.04 or later, please attach the output of upower -d.

Changed in ubuntu:
assignee: Pascal De Vuyst (pascal-devuyst) → nobody
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired

I'm on Saucy and I get this message since they added support for unifying receiver messages. And the level says it's less than 1% left)

Here's upower output:

fredrik@AMDx2:~$ upower -d
Device: /org/freedesktop/UPower/devices/mouse_0003o046DoC52Bx0004
  native-path: /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6.4/1-6.4:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004
  vendor: Logitech, Inc.
  model: M570
  power supply: no
  updated: Sun Aug 25 08:42:17 2013 (215 seconds ago)
  has history: yes
  has statistics: no
  mouse
    present: yes
    rechargeable: yes
    state: discharging
    percentage: 90%

Daemon:
  daemon-version: 0.9.21
  can-suspend: yes
  can-hibernate: no
  on-battery: no
  on-low-battery: no
  lid-is-closed: no
  lid-is-present: no
  is-docked: no

Here's output while popping the message:

fredrik@AMDx2:~$ upower -d
Device: /org/freedesktop/UPower/devices/mouse_0003o046DoC52Bx0004
  native-path: /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6.4/1-6.4:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004
  vendor: Logitech, Inc.
  model: M570
  power supply: no
  updated: Sun Aug 25 08:59:17 2013 (9 seconds ago)
  has history: yes
  has statistics: no
  mouse
    present: yes
    rechargeable: yes
    state: discharging
    percentage: 1%
  History (charge):
    1377413957 1.000 discharging

Daemon:
  daemon-version: 0.9.21
  can-suspend: yes
  can-hibernate: no
  on-battery: no
  on-low-battery: no
  lid-is-closed: no
  lid-is-present: no
  is-docked: no

Changed in ubuntu:
status: Expired → Confirmed
Letheed (letheed) wrote :

On Saucy too, same problem as Fredrik's on two computers with two Logitech MX

Device: /org/freedesktop/UPower/devices/line_power_AC
  native-path: /sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/AC
  power supply: yes
  updated: dim. 08 sept. 2013 00:29:30 CEST (775 seconds ago)
  has history: no
  has statistics: no
  line-power
    online: yes

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0
  vendor: Sanyo
  model: DELL NH6K928
  serial: 4063
  power supply: yes
  updated: dim. 08 sept. 2013 00:29:35 CEST (770 seconds ago)
  has history: yes
  has statistics: yes
  battery
    present: yes
    rechargeable: yes
    state: fully-charged
    energy: 62,16 Wh
    energy-empty: 0 Wh
    energy-full: 62,16 Wh
    energy-full-design: 62,16 Wh
    energy-rate: 0,0111 W
    voltage: 12,435 V
    percentage: 0%
    capacity: 88,6607%
    technology: lithium-ion

Device: /org/freedesktop/UPower/devices/mouse_0003o046DoC52Bx0004
  native-path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004
  vendor: Logitech, Inc.
  model: Performance MX
  serial: FDD32E58
  power supply: no
  updated: dim. 08 sept. 2013 00:42:02 CEST (23 seconds ago)
  has history: yes
  has statistics: no
  mouse
    present: yes
    rechargeable: yes
    state: discharging
    percentage: 5%

Daemon:
  daemon-version: 0.9.21
  can-suspend: yes
  can-hibernate: no
  on-battery: no
  on-low-battery: no
  lid-is-closed: no
  lid-is-present: yes
  is-docked: no

The bug was fixed in upower

Changed in ubuntu:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers