My friend won't let me take apart the iriver he lent me, but maybe someone can give this a shot. Can someone with tools and an ammeter open up the iriver and stick an ammetre between the battery and the device? That way you could measure the current consumption of the device, then try various things in software to see what configuration makes the current consumption unusually high. Would that be an idea?
On Tue, 2006-06-06 at 00:29 +0200, Manuel Dejonghe wrote: > On 5/31/06, Jonathan Corbet <[EMAIL PROTECTED]> wrote: > > For the 3.0 release, my ever so humble > > suggestion would be to *document* the battery life issue and worry > about > > things which can actually hang up the player. > > For the sake of documentation, I know for sure that it is not related > to the cpu speed. > > I checked it by trying to play jewels on a longer trip (no music > playing). I idled the cpu in the debug menu, and the slow > swap-animation showed me that the cpu was not boosted all the time. > > And for what it's worth, I do not know which other part in the iriver > device (besides of the hard disk, which is already excluded I think) > has a variable power consumption, apparently, I'm not enough into > electronics yet :-D > > It was not that bad in the beginning of the h300-adaption, was it ? > How/when did this problem appear ? > And the very similar h100 does not suffer from this problem, so it > must be hidden in the very device/component part, which is certainly > not easy to get into. At least for me :-D > > Does anyone have a clue, a pointer, an idea where guys like me > can/could start to search ? I'm just asking because I never saw any > discussions on this topic here yet. > > ~lImbus
signature.asc
Description: This is a digitally signed message part
