What is this?

Rockbox is an open source firmware replacement for a growing number of MP3 players. Rockbox aims to be considerably more functional and efficient than your device's stock firmware while remaining easy to use and customizable. Rockbox is written by users, for users.

This site is for a branch of Rockbox, by Jack (chrisjs162216). The difference between this branch and the official version of Rockbox is this branch has patches added to it, so it has more features. These patches are updated every so often, with new ones added every few days.

How often is this branch updated?

While it should be automatically updating every time there's a change to the official Rockbox code, there's been a problem that is causing it to not do that. I know the cause of the problem and am working to fix it. Whenever there's a new patch added, the build is manually updated, and usually is manually updated at least once a day to ensure that it is building properly.

How can I find that the build was updated?

Usually, there's a build log, although due to the current problem with the automatic updates, the build log displays very little information. The build log is not updated on manual updates. Another way to find if you have an updated version is to look at the rockbox-info.txt file in the .rockbox directory of the zip file. The line beginning with 'version' will tell you the date your copy was generated. In addition, I am currently thinking of generating an image with the date and time of the last update.

Helping with the build

While I generally am able to keep the build up to date and add new patches, I will be starting school in the next few weeks. If you would like to help me add patches and keep the build working, let me know, and I may give you access to the build source.

Source code

The GPL states that I need to provide the source code to anyone who asks for it. Since the build is usually updated at least once a day, if not more, I do not automatically create a copy of the source code. However, if you want the source code, let me know, and I will make a copy of it. I will warn you however, I will not make backups of specific directories for you - it's either all of it or none of it. The source code with all SVN information is a few hundred megs, so I suggest you simply follow the links to the patches, and patch a copy of the source yourself. If you are a 'builder'/'patcher' and are having problems patching your copy, or you would like a copy of a custom patch, I will give you the individual files for it, to cut down on bandwidth.

Adding patches

I mostly rely on the people using my build to determine if I should add patches. If you want a patch added, contact me, either by the contact form (that I hope to add shortly..) or via the comments.

Old build copies

Around the end of July, I started saving copies of the build. I plan to add a script to fetch these copies soon.

MD5 Checksums

For those who want an MD5 checksum (I don't exactly know why you'd need it, if the zip doesn't open, it means there's a problem, and if it doesn't boot properly on your Sansa, just download another copy) you can view the last few lines of the build log to see the md5sum for the latest build. If you want the md5sum of an older build, the server will generate it when you request the download. MD5sums provided are only for the zip archive, not individual files.

Contact Me

If you want to contact me, I suggest you use the contact form that I plan to add soon, or via the comments. I suggest you don't try to email me directly, as emails will be sent to a catch-all address, which I don't often check.