Open GoogleCodeExporter opened 8 years ago
Unfortunately, there's nothing I can do to my app to make this any better if
the battery is reporting an incorrect voltage like this. You should report the
issue to Asus, as they are the only ones with the ability to correct this.
Original comment by andr...@darshancomputing.com
on 22 Sep 2011 at 9:30
Issue 68 has been merged into this issue.
Original comment by andr...@darshancomputing.com
on 29 Feb 2012 at 6:13
Original comment by andr...@darshancomputing.com
on 29 Feb 2012 at 6:14
Issue 77 has been merged into this issue.
Original comment by andr...@darshancomputing.com
on 19 Jul 2012 at 8:37
I wanted to offer a more detailed explanation of what's going on here, since it
seems manufacturers are still sometimes putting out devices with this problem.
Some devices report a useless whole number of volts rather than the whole
number of millivolts. For example, if the voltage is 4057 millivolts (which is
4.057 volts), the device should report the number of millivolts as "4057". The
devices with this issue instead report "4". Since it's an integer value,
there's no way to extract any extra information out of "4". I can determine
"Oh, you must mean volts, not millivolts", and report it as "4V", but then the
voltage will always just show either "4V" or "3V", which seems kind of
pointless.
So what I am going to do is this: when the voltage reported by the battery is
clearly wrong, I just wont display the voltage in the notification. I expect
this to be in the next release, within a few weeks.
Original comment by andr...@darshancomputing.com
on 19 Jul 2012 at 8:46
Thanks for the explanation!
Original comment by casper.l...@gmail.com
on 23 Jul 2012 at 8:03
Original issue reported on code.google.com by
victor....@gmail.com
on 12 Sep 2011 at 10:12