Rockbox Development > New Ports
Cowon D2
RockBoxy:
I'm not a programmer myself but may I ask you guys a question?
I'm really interested in the wavpack lossles recording function for my cowon D2+.
Do you think there is a chance the voice record function will be ready soon?
If not would someone be so kind to start working on this function?
BasculeTheFule:
Hi.
I have just bought what I am guessing is one of the last new Cowon D2+ to be had in the UK.
I've been using an X5 and latterly an X5L with Rockbox for some time and had forgotten how frustrating the default Cowon UI can be.
I'd like to Rockbox the D2+ but note that the D2 port is currently unstable. Given that the D2 seems to be making way for the D3, what are the chances of the port progressing to a stable state and further developed?
Also, just how usable is the unstable build, and is there any risk associated with installing it at this point? Is it correct that I will need to get an SD card if I want to be able to save any changes I make to Rockbox (should I install it) at this point?
Cheers,
BTF
shotofadds:
--- Quote from: BasculeTheFule on July 31, 2010, 12:57:31 PM ---I'd like to Rockbox the D2+ but note that the D2 port is currently unstable. Given that the D2 seems to be making way for the D3, what are the chances of the port progressing to a stable state and further developed?
Also, just how usable is the unstable build, and is there any risk associated with installing it at this point? Is it correct that I will need to get an SD card if I want to be able to save any changes I make to Rockbox (should I install it) at this point?
--- End quote ---
Unfortunately the D2/D2+ port has reached a bit of a dead-end, as there is really only one developer (me) involved in the port, and it works "well enough" for me as it is. Since no-one else seems to be interested in developing it, this is where it will stay for the time being. All the good work done by the rest of the Rockbox team will still be built into the D2 port, but there might not be any D2-specific updates for a while.
Having said that, the port is quite usable in its current state (especially if you download one of the designed-for-touchscreen themes from the themes site). "Unstable" just means that some significant features are missing, it doesn't mean that the player is unstable while running Rockbox.
And yes, the recommended way to run the D2 port at the moment is to install Rockbox to an SD card - you will need this to save settings/playlists etc as Rockbox can only access the internal memory in read-only mode.
I hope that helps, and you aren't scared off trying Rockbox by the "unstable" tag. If you have any trouble there are some very helpful people around here or at the iAudiophile forums. 8)
BasculeTheFule:
Thanks for the update!
I had a feeling the project might have ground to a halt, hence the post.
I am waiting for an SD card to arrive in the post and will load up Rockbox just as soon as it gets here in the hope that it does a better job than the 2.13 firmware I currently have installed!
I was thinking about selling my X5L, but to be honest would have to think twice about that if it meant being stuck with the Cowon UI on the D2+.
Cheers,
BTF
cowonoid:
I am curious: there were so many hours and days of work spent on backwards-engineering the D2 by disassembling the firmware;
wouldn't it be more effective to find out about the exact shematic? Look for some defect D2s or buy one (everyone interested spents a few $) or even use the own one cautiously and disassemble it (like the guys from anythingbutipod)? Measure each pin of a chip with an ohmeter and look where it is connected to and during that tipping the information into Eagle layout designer?
With the shematic and the datasheets one could do the greatest things! Even get more out of the hardware than Cowon does (f.e. unused ports of ICs). The "rockbox module" could then be built on a platform, which has the most basic controls over the hardware and is not driven by pieces of disassembled code (which is maybe the reason for annoying "bugs" like just 20% of battery life).
Knowing all the hardware and how it is connected would give a feeling like I build the whole device myself. That would contribute to motivation and speed of development.
I mean: this device is really nice! With a better firmware than the original one I probably would use it for the next 40 years without getting tired of it (buying 2 more now for spare :)).
Wouldn't it be worth it to get fully familiar with all the devices structure? I even guess, that doing that from the beginning would have spared time.
Or am I wrong?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version