On 3/11/07, Miles Sabin <[EMAIL PROTECTED]> wrote: > troy engel wrote, > > See a previous post -- bcharge failing to detect the device on second > > run is normal, it's a bit of missing code loop check in the tool > > (I'll see if I can't write a patch today :) ).
Patch submitted: #1678400 - two whole whopping lines of code. rawr. New output on a Pearl already adjusted should look like: $ ./bcharge Scanning for Blackberry devices... Found...already at 500mA 0 device adjusted. > But then btool -l just hangs as before. Right you're A-OK so far! This is exactly what I was also getting on 4.2.0.64 (official T-Mobile release) when I was running it last week. I have since upgraded (to answer your other question) to 4.2.0.71 (official Cingular release), and now btool is not hanging anymore and is working after a rmmod usb_storage. This is why Chris was wanting to see if you could upgrade, to try and verify if it was in fact a bug fixed in the firmware that I accidentally found. But without Windows and the ability to do that, well...you can't. -te -- some live, some die in the way of the samurai ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel