Rockbox Development > New Ports

SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

<< < (98/386) > >>

funman:
Hello, some time has elapsed without updates, so I'll give you the status on the SansaV2:

ROCKBOX DOES NOT WORK YET not even for casual use; so really there is no point in using it if you're not going to develop and make it better.

A lot of people have been asking for status recently, i hope it's made clear.
For future reference, you can track the status here

Recently we have been working on the FM radio, and it has been tested on M200v4 and Clip (radio in Fuze and e200v2 should 'just work' when we'll be able to test it)

Here is what is missing at this day:


* BUTTONS on e200v2 and Fuze (work in progress by kugel and daniel_at)
* STORAGE : we can access fully 1GB and 2GB models, but we can only access up to 1GB on >2GB devices
* RECORDING
* USB : could be pretty hard since we do not have any form of documentation, so long and tedious reverse engineering might be our only way
* BUFFERING : sound has only been tested on target with buttons (and which happen to only have 2MB of SDRAM) and random crashes appear, maybe due to buffering since applying FS#9332 helps a lot => needs to be investigated
* PLUGINS : Fuze and m200v4 miss keymaps in the plugins. Note if you are not a programmer but know how to build rockbox you can definitely help here by testing your work in a simulator !
* MANUAL : Rockbox proudly ships with a very decent manual, and the Sansa AMS shall make no exception, the manual should list what are the specific issues/capabilities on these models
* KEYMAP : The e200v2 uses the same keymap than e200v1, but other models will need reflexion on a good keymap to use. Note : this is a point where non programmers can help too
* ART : some plugins might need screen-size specific bitmaps and/or a new wps
* REVERSE ENGINEERING : The Clipv2, c200v2, and Fuzev2 (announced a short time ago on Sandisk Sansa forums) have currently no code in SVN because we need to figure at least one button for dual boot to work. If you are willing to modify a few lines of assembly code and risk definitely bricking your device you can step up here.
* RBUTIL : mkamsboot should be integrated into rbutilqt, and a howto for manual install written in the wiki

Hillshum:
Manual is another thing non-coders can write

battlemac:
when you are referring to storage are you referring to the built in storage or are you referring to the SD card storage?

gabe565:
It is the internal storage with the no more than 1GB problem.

Hillshum:
is that 1GB as in 109 or 10243?

Navigation

[0] Message Index

[#] Next page

[*] Previous page