You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Start BtBatStat on 10.8.2
2. Note battery% from the app and from the OS
What is the expected output? What do you see instead?
The app shows results that are different from the OS.
What version of the product are you using? On what operating system?
0.9 on 10.8.2
Please provide any additional information below.
I'm running 10.8.2 and see the following:
- keyboard % is correct
- mouse % is shown as 61% while OSX itself shows it as 100%
I tried a different mouse (Logitech bluetooth mouse) and it is not detected, so
the issue is with this (Magic) mouse only.
I reconnected the mouse and it dropped to 60%.
Not saying BtBatStat is incorrect, it is just different. Here is the result
from my freshly-loaded rechargeables:
ioreg -n BNBMouseDevice |grep -i perc
| | | "ExtendedFeatures" = {"SuperMode"={"size"=1,"id"=215,"min"=0,"max"=1,"type"=2},"FullFactoryDefault"={"id"=68,"type"=2},"DeviceNameChange"={"id"=80,"type"=2},"DeviceName1"={"id"=81,"size"=8,"type"=2},"BatteryCalibrationData1"={"id"=97,"size"=29,"type"=2},"DeviceName2"={"id"=82,"size"=8,"type"=2},"DeviceName3"={"id"=83,"size"=8,"type"=2},"LongDeviceName"={"id"=85,"size"=64,"type"=2},"BatteryState"={"size"=1,"id"=48,"min"=0,"max"=2,"type"=0},"UnloadedAndLoadedBatteryVoltages"={"id"=105,"size"=4,"type"=2},"DeviceName4"={"id"=84,"size"=8,"type"=2},"CalibratedBatteryThresholds2"={"id"=96,"size"=11,"type"=2},"FactoryDefault"={"id"=69,"type"=2},"CalibratedBatteryThresholds1"={"id"=96,"size"=25,"type"=2},"BatteryPercent"={"size"=1,"id"=71,"min"=0,"max"=100,"type"=2},"WillShutdown"={"id"=64,"type"=2},"RecantConnection"={"id"=65,"type"=2},"UserMode"={"size"=1,"id"=67,"min"=1,"max"=3,"type"=2}}
| | | "BatteryPercent" = 60
Original issue reported on code.google.com by san...@goudswaard.nl on 19 Nov 2012 at 6:57
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
san...@goudswaard.nl
on 19 Nov 2012 at 6:57The text was updated successfully, but these errors were encountered: