Two related questions that probably apply equally to all Sansa s being rockboxed:
When rockbox switches into the OF , or the user holds down the left button to start in OF , is it invoking the OF portion of the rockbox -modified OF firmware, or a copy of the earlier OF firmware that’s somehow kept somewhere when the rockbox firmware is installed?
When installing a rockboxed firmware, does the version of the OF that was on the Fuze just before the rockbox installation have any relevance?
Why not put reminders to this effect on the lower part of the screen, which is not in use during a file rename operation?
@summerlove wrote:
I assume because it’s in the manual? Admittedly, I try to read as few manuals as humanly possible.
aarons510 doth write:
I guess we should all carry printouts of the manual along with our Fuzes. Or we can carry around a notebook computer with a copy of the manual on it. :wink:
Correct. Theres a charging circuit which is turned on and off via the firmware which monitors the charge progress and temperature. Its like this on most modern MP3 players, though a few older ones have pure hardware charges that turn themselves on and off automatically.
About the keyboard, that seems like a good idea, but its pretty far outside of the parts of rockbox I usually look at. If someone wants to submit a patch I’ll get it reviewed. My guess is the main reason is that a lot of players have small screens and no one ever bothered to improve it on larger screens.
Two related questions that probably apply equally to all Sansa s being rockboxed:
When rockbox switches into the OF , or the user holds down the left button to start in OF , is it invoking the OF portion of the rockbox -modified OF firmware, or a copy of the earlier OF firmware that’s somehow kept somewhere when the rockbox firmware is installed?
When installing a rockboxed firmware, does the version of the OF that was on the Fuze just before the rockbox installation have any relevance?
mkamsboot injects a tiny bit of assembly code into the sandisk firmware, and then compresses the whole thing so that its much smaller. The combined code is then sent to the player which recognizes it as a firmware update. On boot the injected assembly decompresses the entire firmware, which includes the sandisk software and a bit of code that determines if you get the rockbox bootloader or the sandisk firmware based on a button press. Since the sandisk firmware is decompressed, it can be booted as normal without any impact from the rockbox code.
So whatever version you inject with mkamsboot is the version you’ll have on the Fuze after installing.
Two related questions that probably apply equally to all Sansa s being rockboxed:
When rockbox switches into the OF , or the user holds down the left button to start in OF , is it invoking the OF portion of the rockbox -modified OF firmware, or a copy of the earlier OF firmware that’s somehow kept somewhere when the rockbox firmware is installed?
When installing a rockboxed firmware, does the version of the OF that was on the Fuze just before the rockbox installation have any relevance?
The way I understand it is:
Rockbox is simply additional alternative firmware that sits alongside of the OF (original firmware). It does not replace or modify anything, least of which the OF. It creates a ‘dual-boot’ system.
When you hold down the Left/REW button while powering up, this causes the player to boot into the OF. Conversely, depending on how you use your player and your preference with the 2 systems, you can install a reverse-bootloader that will make it boot into the OF unless you hold the the Left/REW button at the same time.
As far as your 2nd question, I would say not. As I said RB sits alongside of the OF, and does not rely or depend on it for anything, so the version of the OF would be irrelevant.
mkamsboot injects a tiny bit of assembly code into the sandisk firmware, and then compresses the whole thing so that its much smaller. The combined code is then sent to the player which recognizes it as a firmware update. On boot the injected assembly decompresses the entire firmware, which includes the sandisk software and a bit of code that determines if you get the rockbox bootloader or the sandisk firmware based on a button press. Since the sandisk firmware is decompressed, it can be booted as normal without any impact from the rockbox code.
So whatever version you inject with mkamsboot is the version you’ll have on the Fuze after installing.
Thanks for the response.
I guess the immediately important part of your answer is the last sentence. I started writing some questions regarding the longer paragraph, but decided that I’ll look for more info on the rockbox.org site when I have the time, rather than using your time and mine now.
BTW, does what you wrote apply to the e200’s and other players as well?
So far all the AMS players work like that (hence the name mk ams boot). Mostly they use such a complicated process since theres no recovery mode and we didn’t want to risk having people brick players.
My compliments to all who worked on the rbutilqt (Rockbox Utility). This is the first time using it and it works flawlessly. I updated to the latest release my Fuze, e250v1, e280v2 and both 3G iPods with ease and simplicity.
Just a quick post to say that with my Fuze (v1) coming up to it’s year anniversary, I decided to install Rockbox.
I used the Rockbox Utility and pointed it at a downloaded fuze 01.02.26 firmware. The rest was done automatically.
Once I’d chosen the skin and got the fonts right, I was ready.
So far (two weeks in), I’ve had no major problems and it’s a delight to have gapless playback (with mp3, flac and ogg).
For those who are a bit wary, if the Fuze is off and you plug it into your pc, it boots into the Sansa firmware so you can charge it and transfer files. If you turn it on normally it boots into Rockbox.
There are probably lots of other things it can do, but it has more than I need.
Some may remember me as the guy that accidentally blew up his v2 Fuze. Bought a replacement on Ebay and it was a V1.
Thought about RB, but decided not to.
Last night I decided to try it.
NO LOOKING BACK.
IMO, no offense Sandisk, the Fuze has gone from Mediocre to AMAZING! I’ve never had RB on anything befre. It has just about every option you can possibly think of. And the level of control over everything is just mind bending.
Not to even mention it looks like DRM was not broken, so I can still boot back into the Sansa firmware for AudioBooks.
I am just totally blown away. Finally I have TRUE PLAYLISTING on my Fuze! WOOHOO! And some excellent “DJ-like” play options.
I just want to know since they have evidently fixed a lot of things . . . Is it very stable, or stable at all? If my Fuze passes its 1 year warranty (I still have yet to have one do this), I plan on installing Rockbox.
In my opinion, the Fuze and e200v2 port of RB is more stable than any of the others I’ve tried, which includes the 3gen iPod, Toshiba F40, e200v1, c200v1. The Fuze and e200v2 port are likely the best ports available…except for what I read about video playing.
@saxmaster765 wrote:
I just want to know since they have evidently fixed a lot of things . . . Is it very stable, or stable at all? If my Fuze passes its 1 year warranty (I still have yet to have one do this), I plan on installing Rockbox.
It is at least as stable as the original Sandisk firmware, and if there are any problems with Rockbox on your Fuze there’s a genuine chance of it getting fixed (unlike things in the original firmware).
I suppose you would lose your warranty if your Fuze broke while having Rockbox on it, but as long as it works you can always reinstall the original firmware, delete the .rockbox directory and there will be no sign of Rockbox ever having been on your Fuze.
Mine has crashed maybe two times. Can’t remember the error because it was a non-issue. Turned it off, turned it on and it picked right back up playing the song it was playing when it crashed. One time it looked like it was frozen when I tried switching to a new theme. Once again, turn it off and back on and it was just fine.
So I would say it is still not 100% stable, but certainly stable enough for 99% of folks. IMO.
Plus being able to boot right back to the Sansa OS is a nice feature, though if I could no longer do that and was stuck with RB full time, I wouldn’t mind at all. It’s that good.
I finally ran into a consistent problem with RB on my Fuze. About every 45th song I skip to causes the player to freeze. I’m using FLAC on a Lexar 16GB card.
EDIT - Actually I think it’s tied to the database update process. The update process can take a significant amount of time and there is no indication of its progress. This is usually the cause of any freezing I have seen before, skipping through songs and then the Fuze freezes.