[RTYUI333]

Originally Posted by Llorean

It's not that nobody is working on the issue.
It's that the issue refuses to be indentified. It's not something that is simply a function of the amount of energy you put into it. If you take a blind person and put him in an unending hallway with one door on one side, there's no guarantee he'll ever find the door. If he just walks forever down one wall, and it's on the other, he will miss it. Since there is no end to the hallway, he can't just walk up one side and back down the other.

Some problems require luck to solve, or intuition. Right now nobody has been able to identify what is causing the problem. Every now and then somebody has a good idea. The idea gets tested. So far each test has come up negative, and we're back to square one. So it's not so much as "nobody's working on it" as "until we figure out what it is" (where the door in the hallway is), the problem simply can't be solved.

It was unfortunate that resolving that problem was listed in the 3.0 release, because really it was unrealistic to put a deadline on solving something that still needed to be identified, and now there are a lot of people expecting 3.0 to solve their battery woes when in reality there is an increasing chance that it won't. Until someone identifies exactly where the big problem is (and it's very likely one significant problem, considering the vast differences in efficiencies between the H100 and H300, and how small a part of that difference the power drain from the LCD was when measured) it's just going to be a matter of people thinking about it, and then trying things.

How bout asking stuff to iriver?? (excuse me if you already have)