Custom patched Rockbox builds for Fuze v1/v2 - DFKT

[saratoga]

Originally Posted by mamamia88

i thought it would be as simple as downloading patch file entering the terminal changing directory to the source code with the patch file moved to the root directory of the source code and running the patch command then compiling

Yes thats pretty much the process.

[CrowdAds]

[mamamia88]

then why do i keep getting an error message telling me that the patch.diff file doesn't contain the info on the file that it is supposed to be modifying?

[saratoga]

Originally Posted by mamamia88

then why do i keep getting an error message telling me that the patch.diff file doesn't contain the info on the file that it is supposed to be modifying?

Post the console log and I'll tell you.

[mamamia88]

[mamamia88]

effing heck this is driving me crazy. i know i have everything right now i have the patch in the same folder as the sansafuzev2.h file and changed every instance of sansaclip to sansafuzev2 on the patch code. now when i go to apply patch it tells me it's read only filesystem. what am i doing wrong?

[saratoga]

Thats not the right command. You need to use the -p option:

http://www.rockbox.org/wiki/WorkingW...plying_A_Patch

[mamamia88]

so do i count how many characters are between the start of directory in the patch and put that number after p?

[Progweed]

No, the p-option specifies the number of directory levels to chop off in order to match the directory structure of your installation.

So if the patch file resides in your /root/rockbox directory and for example references firmware/export/config/sansafuzev2.h, then there is no need to cut something off, because firmware (the first directory level) is a subfolder of your rockbox directory, meaning that p0 should work for you.

You can also use the following in order to test different options (without actually applying the patch):

patch --dry-run -p0 < patchfile

Hope that helps. I'm myself very new to compiling Rockbox.

[Progweed]

Ah yes, to be more precise:

Originally Posted by mamamia88

i have the patch in the same folder as the sansafuzev2.h file

Don't do this. Copy the patch to your root/rockbox directory instead.

[saratoga]

If you look at the error message, it tells you the path it was trying to use to find the file to patch:

a/firmware/export/configure/sansaclipplus.h

So if you want to patch using the command you gave, you'd probably need to have your entire rockbox folder inside another folder called 'a'. Or you can use the p option (probably with 1 as the argument) to chop off the leading 'a'. Then you just need to be in your source check out folder. That said patches can be screwy, so sometimes you just need to try p0 or p1 to get them to work.

[mamamia88]

allright i will give it another go

[mamamia88]

managed to successfully patch it with the -p1 option but once compiled it won't run weird.

[Progweed]

So the compiled build is working, but USB isn't?

[heinrichh]

Originally Posted by dfkt

Builds have USB enabled, backlight on keypress, permanent sleep timer, and Meier crossfeed. Not tested - I have no Fuze.

Meier Crossfeed v2: r28830M-101214-sansafuzev2 (FS#9305, FS#11042, FS#11304, FS#11577-Meier_v2, FS#11664) - dfkt.zip
Meier Crossfeed v3: r28830M-101214-sansafuzev2 (FS#9305, FS#11042, FS#11304, FS#11664, FS#11767) - dfkt.zip

Only want to say many thanks for this builds! They are running very well on my new Fuze V2!

[tony3011]

Hey all, I just rockboxed my Sansa Fuze V2 only to discover that the main build does not include USB support. Luckily, a little bit of googling got me to this thread.

Here's my question: Is it possible to combine the features of this patch (in particular the USB support and permanent sleep timer) and the new features of Rockbox 3.8 (of which I'm absolutely in love with automatic resume due to my erratic podcast listening habits). If not, any word on when a patched version of 3.8 might be released?

Thanks! :-)

[dfkt]

Some of the patches used in this build are out of sync now, meaning they can't be applied to a newer Rockbox version anymore without some more serious in-depth tinkering. USB support and permanent sleep timer are among the out-of-sync patches, unfortunately. (At least last time I looked, maybe someone re-synced them already.)

[akbarhash]

The USB support thing is being neglected maybe because the OF has USB and it is functional.
Still i would have loved to have had USB in rockbox and it does not take away the fact that it is being neglected.

[TackyTiger]

Until recently I was keeping both my original FS#10849 and the branched FS#11042 patches synced, but after a year with no interest from anyone with commit rights, it's become a bit tedious. As there are some design flaws with FS#11042, I've decided to only bother keeping FS#10849 synced (it's the one I use, after all).

Sorry about that. Hopefully one day I'll find the energy to get FS#11042 up to scratch and request FS#10849 closed.

Edit: Should have mentioned, these are the permanent sleep timer patches.

[akbarhash]

atleast there is some activity going on in fs#11042
there has been no activity in the usb patch for a month...

[saratoga]

Originally Posted by akbarhash

The USB support thing is being neglected maybe because the OF has USB and it is functional.
Still i would have loved to have had USB in rockbox and it does not take away the fact that it is being neglected.

By all means, if you have some idea why it fails, feel free to stop neglecting it. Otherwise its probably just going to have to wait until theres some breakthrough and someone realizes why the controller seems to randomly decide to drop connections for no apparent reason.