I understand that Rockbox does not support playback of DRM. I understand this completely and I get that an open source, freeware project could not possibly pay or obtain the licensing required to enable Audible DRM or Microsoft PFS DRM used by Rhapsody, Napster, and similar subscription services.
What I don’t understand at ALL is why DRM is broken when I boot into original firmware. The Fuze V1 and V2 can be booted into Sansa firmware, and for some reason DRM is broken even in this mode.
I had a rockboxed E280R and that played the Rhapsody tracks perfectly when booted into OF. Does this have to do with the fact that the E280R read .rax formatted tracks and the DRM playback was “hardware based” somehow?
Can someone who is really familiar with Fuze/Clip architecture tell me why the mere installation of Rockbox disables all DRM playback even if the unit is booted in original firmware?
If I could find a way to boot into OF to use Rhapsody channels, I would be more than happy. I would simply reboot in OF and play my rhapsody tracks.
Does the installation of the rockbox bootloader somehow screw up the secure clock? I’d really like someone who is in the know explain it to me?
Not that I expect it to change, I just don’t like mysteries
Rockbox dev’s never answer questions about DRM. I am really looking for either a Sansa tech, or a very experienced user like myself that may have more insight in the architecture of the Fuze.
I am suspecting that the modification the bootloader makes to the original firmware file somehow disables the secure clock or interferes with the certificate. If I format the device and reload original unmodified firmware, the unit functions normally.
When I load rockbox and boot into original firmware, rhapsody “seems” to recognize the device initially but then tells me the unit is not functioning properly.
I know I will get no answer from Rockbox devs, but I’ll ask there anyway.
Rockbox dev’s never answer questions about DRM. I am really looking for either a Sansa tech, or a very experienced user like myself that may have more insight in the architecture of the Fuze.
I am suspecting that the modification the bootloader makes to the original firmware file somehow disables the secure clock or interferes with the certificate. If I format the device and reload original unmodified firmware, the unit functions normally.
When I load rockbox and boot into original firmware, rhapsody “seems” to recognize the device initially but then tells me the unit is not functioning properly.
I know I will get no answer from Rockbox devs, but I’ll ask there anyway.
Well, Rockbox requires you to be in MSC USB mode and Rhapsody requires MTP, but I don’t know if the answer is as simple as that.
