Rockbox Release - MUST READ BEFORE POSTING NEW THREADS

[Febs]

Folks-

Rockbox 3.0 will be released when the developers believe it is in a release-ready state. It is not there yet, as there are still some bugs to iron out in the playback engine, as well as the still-unresolved issue as to what is causing the H300 power drain.

I promise that there will be an announcement made here as soon as Rockbox is released. Likewise, if there are any other significant developments, they will be posted in the Official Rockbox Progress Thread. Until then, PLEASE DO NOT START NEW THREADS ASKING ABOUT THE RELEASE. I will delete any new threads asking about the Rockbox release, no questions asked.

If you would like more information on the status of the release and the issues that need to be addressed before the release happens, please read this thread from the Rockbox developers' mailing list: http://www.rockbox.org/mail/archive/...-05/0169.shtml

[RTYUI333]

Hmm... so mine was deleted then...
But I'm just glad that I'll be able to get rockbox without H300 Power sucking bug

Go RB devs!!

[Industrial_chickens]

Fair enough!
We should all be very greatfull for all the hard work thats gone into it all so far. If the freeze that was due on the first of may is still not done it means that all these devs are STILL workin hard on it with no time off.
Praise be to them!!!!
Lets just be patient...

[D-Sub]

but...when will it be done?

sorry febs. just kidding. last one.

heck...delete any posts whatsoever asking that! amazing how people simply refuse to read anything else and just go straight to posting. pretty common on most boards I frequent. wonder why

[andrewmel]

From what I have been reading, they may drop the H300 from the release as they are having problems fixing the power bug....

a

[Gaston]

Originally Posted by andrewmel

From what I have been reading, they may drop the H300 from the release as they are having problems fixing the power bug....

a

and what i understood is that nobody is really working on this issue... right ?

somebody to debug? Rockbox needs you!

[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.

[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)

[baobab68]

or reverse engineering the iRiver firmware to see how it inits things?

[Llorean]

Well, one difficulty is that there's still not a proper question to ask them. Also as far as I know, they haven't been formally contacted for help regarding Rockbox, but I've heard of people making casual inquiries and getting indifferent or negative responses.

So we'd have to figure out where the problem is so we'd know what to ask about, and once that's done it can probably be fixed more easily than getting help from them may be.

[RTYUI333]

Originally Posted by Llorean

Well, one difficulty is that there's still not a proper question to ask them. Also as far as I know, they haven't been formally contacted for help regarding Rockbox, but I've heard of people making casual inquiries and getting indifferent or negative responses.

So we'd have to figure out where the problem is so we'd know what to ask about, and once that's done it can probably be fixed more easily than getting help from them may be.

Maybe tweaking firmware might help? Or comparing two FW. I remember that one of FW had slight problem with battery life...

[Mad_Big_Sausage]

Originally Posted by RTYUI333

Maybe tweaking firmware might help? Or comparing two FW. I remember that one of FW had slight problem with battery life...

1.27 is the fw that fixed the issue.

[RTYUI333]

Originally Posted by Mad_Big_Sausage

1.27 is the fw that fixed the issue.

Yes that one. So comparing 1.27 with former one might help

[Kezza]

you said it ..... MIGHT HELP ..... the operative word here being might.

[andrewmel]

I doubt it would help. The battery problem was introduced with 1.25. The only features it added, IIRC, was video ff and rw, and as Rockbox doesnt have video, this is unlikely to be related.

a

[Kezza]

oh its your move a

EDIT: chess game

[Industrial_chickens]

i read recently that the source of the power drain has been identified so any time now....

[schwab002]

Originally Posted by Industrial_chickens

i read recently that the source of the power drain has been identified so any time now....

well it's been fixed for a little while now, i wonder what else they're waiting for?
i guess it doesn't matter though...

[DD]

Originally Posted by schwab002

well it's been fixed for a little while now, i wonder what else they're waiting for?

http://www.rockbox.org/twiki/bin/view/Main/ReleaseTodo

[schwab002]

ah thank you

[mr.levi]

What is the Rockbox stuff?

[Febs]

Originally Posted by mr.levi

What is the Rockbox stuff?

Open source jukebox firmware. Read the "Sources of Rockbox Info" link in my signature.