olpc-batcap is not what you want, sir!

[James Cameron]

Perhaps the original poster didn't want to check the battery discharge
current until the battery is depleted.  That's what olpc-batcap is
for.  It will cause a nice hum in the speakers to ensure the maximum
current is being drawn, and monitor the discharge logging the results
until the battery is depleted.  It is very technical.  It tries to
measure the _capacity_, which is not usually what people want.

If you want to see the battery state of charge, which is what is
presented to the user in Gnome or Sugar, then use this shell command:

	cat $(find /sys -name capacity)

Please don't raise bugs against olpc-batcap asking for it to report
the battery state of charge.  ;-}

Please do use devel@ mailing list for general questions about OLPC
software, thanks.  You will get a wider review.

On Mon, Sep 02, 2013 at 12:47:13AM -0500, Jerry Vonau wrote:
> /bin/olpc-batcap
> 
> If it doesn't work right file at bug against olpc-utils at: http://
> dev.laptop.org/newticket as it is a olpc supplied package.
> 
> Jerry
> 
> 
> On 2 September 2013 00:36, <tkkang at nurturingasia.com> wrote:
> 
>     What is impossible is possible ! Well I have been looking for USB ethernet
>     compatabile dongle for many years. There are good ones and bad ones and
>     they are repackage different but maybe from the same source. Anyway once I
>     get one working and with lights indicator I make a mark that it is working.
>     I bundle 2 dongles that seems to work together - diffrent mac address.
> 
>     Have to be contented since they cost me US$5
> 
>     Here is the message log from my XO-175 for the debugging. Thanks.
> 
>     What command to check battery current status?
> 
> 
>     >-----Original Message-----
>     >From: Jerry Vonau [mailto:jerry at laptop.org.au]
>     >Sent: Monday, September 2, 2013 01:23 PM
>     >To: xsce-devel at googlegroups.com
>     >Subject: Re: [XSCE] XSCE-4 testing: Findings
>     >
>     >On 2 September 2013 00:17, Anna <aschoolf at gmail.com> wrote:
>     >
>     >> On Sun, Sep 1, 2013 at 11:53 PM, Jerry Vonau <jerry at laptop.org.au>
>     wrote:
>     >>
>     >>> Avoid at all costs usb adaptors that carry the mac address
>     >>> 00:e0:4c:53:44:58, twice in the last while we have seen 2 adapters in
>     >>> the same machine with the same mac address. The first time I personally
>     >>> came across this was at an XSCE sprint when I borrowed Anna's adapter
>     to
>     >>> test with, and I almost lost my mind when the adapters would change on
>     >>> reboot, I never suspected you could have a duplicate mac address. Now
>     the
>     >>> funny thing is the packaging was completely different between the 2
>     >>> adapters and that given we live in different countries and over 1000
>     miles
>     >>> apart.... Now there is 4 hours of my life I won't get back.
>     >>>
>     >>
>     >> Just the other day, Anish was trying to do a two dongle install and was
>     >> having trouble with the network.  I asked, to his initial confusion,
>     "Can
>     >> you do ifconfig and make sure the MAC addresses for your adapters are
>     >> different?"  His response, "WTF...  How is this even possible?"  Yep,
>     they
>     >> had the same MAC address as mine and Jerry's.  It's one of those "WTF"
>     and
>     >> then "OMG" and then "LOL" and then "oh, hell, no" hardware issues.
>     >>
>     >> Anna
>     >>
>     >
>     >I still have the pictures to prove it.
>     >
>     >Jerry
>     >
> 
> 

-- 
James Cameron
http://quozl.linux.org.au/