Rockbox Technical Forums
Rockbox Development => New Ports => Topic started by: saratoga on August 24, 2011, 02:26:11 PM
-
The Sansa Clip Zip is the Sansa Clip+ replacement. Like the Clip+, it is based on the AS3525v2 SOC as can be seen by checking the AMS header on the firmware file:
http://mp3support.sandisk.com/firmware/clipzip/clipzip01.01.12.zip
The format does not appear to have changed significantly, as amsinfo happily unpacks the firmware revealing nearly the same firmware contents as the Fuzev2, with the addition of a few extra decoders and such. Since this appears to be another SansaAMS device, lets reuse that wiki:
http://www.rockbox.org/wiki/SansaAMS
Theres also some hardware information here:
http://www.rockbox.org/wiki/SansaClip
I'm too busy these days to contribute much to a port, but if someone else wants to take the lead on this I might be willing to chip in a bit.
-
Excellent news! I was about to start searching whether it was based off STMP3780 like the Fuze+, or like the AMS Sansas.
This means that SQ is exactly the same as the Clip+'s excellent SQ.
-
Anythingbutipod has a nice comparison between the clip+ and the clipzip: http://anythingbutipod.com/forum/showthread.php?t=64913
The relevant differences with the clip+ so far seem to be so far just the different display and RDS support.
The display is a 96x96 pixels colour LCD and in the abi article it shows some horizontal lines around high brightness features of the screen, which could point to it being a passive matrix lcd like in the sansa c200.
The radio has RDS support, possibly they are using a si4703 variant instead of the usual si4702 tuner chip (just a guess so far). Oddly I don't see a mention of RDS in the sansa clip zip user manual or on their product page.
-
Just letting you know that I am starting to create a basic framework to build the clip zip as a target for rockbox (to get something compiling, not working yet).
-
Ok, a basic framework has been committed. This makes it possible to at least *compile* a bootloader for the clip zip. The driver for the LCD and backlight is still a stub (i.e. empty functions). The driver for the buttons should basically work except the GPIO-to-button mapping is probably wrong (so UP may be LEFT, etc.)
I also updated mkamsboot to recognise the original firmware file for patching it with the rockbox bootloader. You can't actually create a flashable firmware yet because the dualboot part is still missing. The dualboot code is the code that checks a button/USB connection to decide whether either the original firmware or the rockbox bootloader should be started. This is tricky stuff because any error in this part can potentially brick the player so any new dualboot code needs thorough review.
Marvin the Martian has posted some screen shots from the diagnostic menu on the clip+:
http://www.anythingbutipod.com/forum/showpost.php?p=571421
This basically confirms that 1) diagnostic menu is still available 2) the DRAM memory configuration is the same as on the clip+ 3) it still uses a silabs tuner (si4702 or compatible) and 4) apparently the internal name of the hardware is "visionox".
The clip zip appears to support RDS, so perhaps sandisk put in an si4703 tuner chip. This is basically a si4702 (which we already support in rockbox) with RDS capability added.
-
4) apparently the internal name of the hardware is "visionox".
I assume this is the name of the screen manufacturer - http://www.visionox.com/en/product.aspx?PrID=4
-
dfkt, I think you're right.
It appears that the controller for the OLED is a SEPS114A and that the OLED itself is a Visionox M00230.
In the original firmware, near the Visionox text, there is also a mention of "WiseChip". I think this could be the alternative display supported by the original firmware, I haven't been able to match it yet to the display code.
-
Rockbox for the Clip Zip now boots and can play audio. The code for this is in SVN.
Beware that several things don't work yet, or don't work properly, see the SansaClip wiki.
For example, the display colours are wrong, it seems red and blue are swapped.
Audio playback works, but it takes up to 10 seconds for the first track to start.
This target seems to have the narrowest display we've seen so far. There is no WPS yet for the 96x96 pixel display. To be able to run plugins, many plugins will first need to be updated for the 96x96 resolution.
-
I don't know if i am allowed to write this here.
Because in the wiki the Port status is
"radio works, RDS support to be added later "
Does the ClipZip really has the RDS feature or not? For me i don't get RDS with the
original v01.01.17 Firmware.
The i found this Forum entry:
http://forums.sandisk.com/t5/Clip-Zip/Clip-Zip-RDS-not-working-in-UK/td-p/249506/page/2
(I live in germany not in the uk)
Can someone help me and other ClipZip Owners?
-
The hardware for RDS is there (at least in my player). Reception of RDS requires a pretty strong and clear signal as far as I know. In the original firmware I get a kind of station code (like "WREO"), the 8-character station name and a longer string with other info.
In rockbox, we can perhaps use the station code to select station "album art".
RDS sends data in 4x16-bit packets, the code to process these packets into useful information has not been written yet for rockbox. I plan a kind of generic approach, where the fm tuner driver can submit these raw RDS packets and receive notification when a full RDS message is complete.
BTW, the display colours are now what they're supposed to be and the delay when starting a track is gone.
-
Hey Bertrik, thanks for all your great work on the Zip so far.
BTW, the display colours are now what they're supposed to be and the delay when starting a track is gone.
I just test drove Rockbox on my 4 GB Zip and had both of those problems. There was either an excess of blue or an absence of yellow on my display, but I could normalize it somewhat by resetting the colors.
Can't speak for why the track delay is happening, but I tried shuffling all of my tracks and there was a good 5-6 seconds before each one started when skipped.
I used the current build (r30890), the Win32 version of mkamsboot, the 01.01.17 OF and the pre-compiled bootloader which dfkt made available here: http://www.anythingbutipod.com/forum/showthread.php?t=66292. I would have compiled the bootloader myself but, as far as I can tell, no "bootloader-clipzip.sansa" file has been released yet.
What could I be doing wrong?
-
Actually, the colour problem and the playback delay problem should both be fixed now.
Album art colours seem a bit washed out, but that's just a hardware limitation I think.
(Although maybe we can adjust gamma for to adjust the subjective contrast?)
The Clip Zip can have two different kinds of display, so far we've seen only the Visionox type (visible in the diagnostics menu of the original firmware flashed with a 'T' suffix). The other kind (WiseChip) has not been seen yet 'in the wild', but there is a driver for it. If/when the newer display type shows up, it will probably not work completely right.
-
There is no playback delay on mine, and the colors are OK, asides from what Bertrik describes as a slight washing out. I'm also on r30890 and using the bootloader dfkt shared. The only issue I've seen was a couple of freezes upon disconnect from the computer, although that may have been caused by a corrupted file that I've since removed from the player.
-
Actually, the colour problem and the playback delay problem should both be fixed now.
Album art colours seem a bit washed out, but that's just a hardware limitation I think.
(Although maybe we can adjust gamma for to adjust the subjective contrast?)
The Clip Zip can have two different kinds of display, so far we've seen only the Visionox type (visible in the diagnostics menu of the original firmware flashed with a 'T' suffix). The other kind (WiseChip) has not been seen yet 'in the wild', but there is a driver for it. If/when the newer display type shows up, it will probably not work completely right.
That would explain it. I have one of the WiseChip players. I confirmed this by running a diagnostic, as you described, where I saw this on the second page:
[HW Info]
FM SI4702
WiseChip
Since I, and others with the same display on their Clip Zip's, will undoubtably run into trouble running Rockbox, I'd like to help. Are there tests you could have me run on my device?
-
2facedmayor, for the Visionox display (which I have myself), I noticed that blue and red were swapped, can you check if this is the case for your display too? To check, go to Settings / Theme Settings / Colours / Background Colour and verify that the top bar (R) is indeed red, and that the bottom bar (B) is indeed blue.
Also, I may have made an error in the lcd initialisation sequence, I can double-check that.
-
2facedmayor, for the Visionox display (which I have myself), I noticed that blue and red were swapped, can you check if this is the case for your display too? To check, go to Settings / Theme Settings / Colours / Background Colour and verify that the top bar (R) is indeed red, and that the bottom bar (B) is indeed blue.
Also, I may have made an error in the lcd initialisation sequence, I can double-check that.
The R, as you had surmised, is being displayed as blue, and the B is red. The display colors are still swapped on my player.
-
The R-B swap should be easy to fix.
Can you join the #rockbox IRC channel on freenode.net around 20:00 UTC? I'll probably be on around that time and can send you a firmware that should fix the colour swap.
-
The R-B swap should be easy to fix.
Can you join the #rockbox IRC channel on freenode.net around 20:00 UTC? I'll probably be on around that time and can send you a firmware that should fix the colour swap.
Afraid not, as I work at that time. Instead, I'll send you a PM with my e-mail address and you can send me the firmware. I can respond ASAP.
-
I fixed the blue-red swap. I also added a check in lcd_enable to prevent re-enabling the display when it is already enabled, this should prevent the flickering.
I still don't know where the playback delay comes from, I had this problem in the very early stages of the port, but it mysteriously vanished when I enabled album art and jpeg support.
-
As you say, the R-B swap and flickering are now fixed on my player using the newest build (30922).
One thing I noticed about the track skip delay on my player--if I navigate out of the "Now Playing" screen, by using the back-arrow button for example, the track starts right away. Not something I want to be habitual, but maybe a clue as to the source of my problems.
-
Update: Not sure why I didn't think of this before, but I turned on the directory cache and that completely solved the track delay issue. I understand this has helped a few people having the same issue on different players with Rockbox.
-
Actually, the colour problem and the playback delay problem should both be fixed now.
Album art colours seem a bit washed out, but that's just a hardware limitation I think.
(Although maybe we can adjust gamma for to adjust the subjective contrast?)
The Clip Zip can have two different kinds of display, so far we've seen only the Visionox type (visible in the diagnostics menu of the original firmware flashed with a 'T' suffix). The other kind (WiseChip) has not been seen yet 'in the wild', but there is a driver for it. If/when the newer display type shows up, it will probably not work completely right.
I would *love* for the screen to be calibrated better (as compared to the OF). I've gone back and adjusted the contrast and gamma of embedded .jpgs and the Clip Zip display of album art looks so much better with deeper colors. I suspect the problem may a 1-255 vs. 16-235 brightness levels. I would think the Clip should be 1-255.
Use color bars as a test:
(http://www.mediacollege.com/video/test-patterns/images/colour-bars-smpte-75-640x480.gif)
note in the lower right corner -- there are three small bars -- one is blacker than black, one is black and other is just above black. The blacker than black should be absolutely black and should be just as dark as the black next to it. Only the third bar should be slightly visible.
-
I have been looking around here, but where do i get informations do get/compile the bootloader?
I found the rockbox build.
Can someone please help me? Thank you!
-
Hello.
I've got Rockbox build 30968 on my Clip Zip. So far, so good -- thanks for all the hard work you all have put in.
As I understand the situation with USB mass storage support, that does not work on the Zip and its close relatives the Clip and Clip+ when booted into Rockbox. I've seen some mention of a patch for (I think) the Clip+ which would allow it, but that capability has been turned off by default, because it's unstable when the device is connected to a Windows computer.
Since my Zip will probably never be connected to anything but a Linux computer, the Windows issues don't bother me. Does anyone know if this patch actually exists, and if so, if it can be applied when building the Zip? And if so, could someone please give me some pointers on how to apply it? I've figured out how to set up the build environment, and build the Zip firmware, but I'm pretty hazy yet on how to modify it.
Thanks.
Tony
-
I have been looking around here, but where do i get informations do get/compile the bootloader?
http://www.rockbox.org/wiki/DevelopmentGuide
Then at the configure step, when prompted choose bootloader instead of main build. And in the future if you just have questions about compiling, use the "Starting Development and Compiling" rather then a development thread.
Since my Zip will probably never be connected to anything but a Linux computer, the Windows issues don't bother me. Does anyone know if this patch actually exists, and if so, if it can be applied when building the Zip?
Uncomment the USE_ROCKBOX_USB line here: http://svn.rockbox.org/viewvc.cgi/trunk/firmware/export/config/sansaclipzip.h?revision=30970&view=markup
Expect a lot of file system corruption though.
-
Thank you for the prompt reply and instructions on enabling USB mass storage!
Your warning re filesystem corruption is appreciated -- I will back up!
Enjoy the rest of the weekend.
Tony
-
It would be interesting to know if the Clip Zip has the same problems with USB than the other AMSv2 (Fuzev2, Clipv2, Clip+)
-
I have uncommented the "USE_ROCKBOX_USB" line in sansaclipzip.h, per Saratoga's instructions from November 13, and rebuilt rockbox. After about five days, I can say that so far it's working OK. I have not had any filesystem corruption, but that's probably only a matter of time. The only anomaly I've found is that it won't get recognized properly when it's plugged into a USB hub -- it apparently needs to be plugged directly into my laptop's USB port.
I use Linux on my laptop, not Windows. I have no idea if this would work with Windows; in fact, I remember a posting somewhere that said that it wouldn't.
Tony
-
It's been a while since an update but any news on getting Rockbox to work on the "Clip Zip"
-
It's been a while since an update but any news on getting Rockbox to work on the "Clip Zip"
Please see item 4) in this post: http://forums.rockbox.org/index.php/topic,21176.0.html
-
Rockbox on the clip zip has been working well enough for a few weeks now to use for daily playback of audio, both from the internal memory and from external microsd card.
Most plugins work, but plugins can't be enabled until *all* of them work. There are about 10 or so left to get working, mostly waiting for modification of the code and graphics to adapt it to the relatively small screen of the clip zip.
There is a patch for radio RDS, but there appears to be a bug somewhere in the skin engine that prevents the RDS station name and radio text to be updated properly.
There is no official bootloader out yet, but I think you can safely install one of the pre-built bootloaders by dfkt from the anythingbutipod forums.
-
There is no official bootloader out yet, but I think you can safely install one of the pre-built bootloaders by dfkt from the anythingbutipod forums.
Do you want me to tag and then post an official bootloader?
-
Most plugins work, but plugins can't be enabled until *all* of them work. There are about 10 or so left to get working, mostly waiting for modification of the code and graphics to adapt it to the relatively small screen of the clip zip.
Plugins are enabled now, although some of them look like shit and would clearly need graphics work and/or tuning (tetris^Wrockblox and bubbles are OK but much too small)
Do you want me to tag and then post an official bootloader?
I'd like to know if my change to use (also) left key for dualboot works for other people before doing that.
-
I installed the Rockbox for ClipZip and it's very nice. Much better than Sansa's firmware. The radio works great -- can't wait for the implementation of RDS.
Observations:
The bootup looks a bit "messy" with the the multiple bootloader messages and the momentary inverted color.
Is it possible to improve upon the contrast of the displayed album art? The Clip Zip is capable of displaying a rich, colorful, dynamic picture but the current firmware settings wash the artwork out (same thing happened with the OF). The brightness setting doesn't help. There seems to be some issue with the gamma or contrast.
Thank you!
At bootup after the Rockbox logo:
data abort at 3005A1D0
FSR 0x0
(domain 0, fault address 0xA5D064
Needs a reset.
32GB microsdhc with about 5800 ogg files.
8GB Sansa Clip Zip.
If I reboot without the 32GB card, the reboot is successful, I can then reboot again with the 32GB card successfully but then the error appears on successive boots. I'll try another build (any other bootloaders?).
EDIT:
A Sandisk 16GB card (fewer files) seems to boot OK. The 32GB is a Kingston card so maybe that is the issue. Thinking about purchasing another microsdhc anyway.
EDIT:
Workaround (resolution?): set DIRCACHE to OFF.
-
I'd like to know if my change to use (also) left key for dualboot works for other people before doing that.
A couple people have confirmed that the new bootloader works as expected. I guess we should tag it so that people can use rbutil.
-
I'd like to know if my change to use (also) left key for dualboot works for other people before doing that.
It works for me.
-
Thank you so much for the port to the Sansa Clip Zip. To be honest, as I researched which player to purchase, one of the biggest factors was whether Rockbox was available. This port allowed Sandisk to get a sale that day.
I've been using these builds (and updating regularly) for almost a month now. I've noticed some strange playback issues with the newer builds, which I first mistakenly attributed to a bad set of IEMs. Basically, the audio was almost cutting out sometimes or was going back and forth between the left and right -- well beyond what some stereo music does.
As a test, I played the song from the Sansa firmware and it sounded fine. I reverted back to an older build of Rockbox, and it too sounded great. Below are details about versions, etc. Hopefully something sheds some light on the issue.
Consistent
Test Song: Lo Fidelity Allstars - Battleflag (FLAC - yes, I know it's overkill for a PMP)
Headphones (IEM): MEElectronics A151
Volume: -50 to -70 range for each test
Versions
Sansa 01.01.18 - sounds good
Sansa 01.01.17 - sounds good
Rockbox r31233 (latest) - problem occurs
Rockbox r31209 - problem occurs (I had hoped the changes to mpc were the reason, so I picked one before those changes in svn, but still no luck)
Rockbox r31107 - sounds good
Rockbox r31049 - sounds good
I haven't tested each and every version between r31107 (known good) and r31209 (known bad) but I hope this helps somehow.
Does anyone have any ideas? Would trying the versions between help somehow?
To be clear, I never changed any settings like EQ or anything, so that isn't the culprit either.
Thank you again for all of your hard work!
-
Does anyone have any ideas? Would trying the versions between help somehow?
Yes, r31207 (fixed 5.1 mixing for FLAC files) seems a bit off for stereo.
-
Does anyone have any ideas? Would trying the versions between help somehow?
Yes, r31207 (fixed 5.1 mixing for FLAC files) seems a bit off for stereo.
Thank you, saratoga. I just tried r31194 (the last build for the Sansa Clip Zip prior to r31207) and it sounds great! The next release is r31209 which I already tested and found to be bad.
I appreciate your insight. I hadn't considered that changes for 5.1 FLAC might affect regular stereo FLAC too like the one I was testing with.
I'll still test new builds (especially if they mention those type of changes), but it looks like r31194 is going to be the sweet spot for me for now.
You rock
-
I'd like to know if my change to use (also) left key for dualboot works for other people before doing that.
A couple people have confirmed that the new bootloader works as expected. I guess we should tag it so that people can use rbutil.
I'd like to wait a bit to see USB works great so we could enable it in bootloaders and have mkamsboot always boot rockbox even when powered by USB.
-
I just tried r31194 (the last build for the Sansa Clip Zip prior to r31207) and it sounds great! The next release is r31209 which I already tested and found to be bad.
Would you post your problem file to this task:
http://www.rockbox.org/tracker/task/12371
-
Hi all. Thanks for the great work on the Sansa Clip Zip port.
Is this in a state now where the standard RB utility will Rockbox it?
My situation is, my stepdaughter borrows my Clip+ a few times a week to take to school with her. I'd love to buy her a cute little red Clip Zip for Christmas, with microsdhc, and Rockbox it for her. I know the port doesn't meet the "stable" criteria, but I gather from this thread that it's pretty darn close. Does it take specialized procedures to Rockbox a Clip Zip?
Thanks
-
manual instructions (http://www.rockbox.org/wiki/SansaAMS#Installation) will work but you have to build the bootloader yourself.
Or you can use this one (http://people.videolan.org/~funman/bootloader-clipzip.sansa), or anythingbutipod instructions (http://anythingbutipod.com/forum/showthread.php?s=af4084e8a87fe915687b9a88aa521169&t=66292)
-
I just tried r31194 (the last build for the Sansa Clip Zip prior to r31207) and it sounds great! The next release is r31209 which I already tested and found to be bad.
Would you post your problem file to this task:
http://www.rockbox.org/tracker/task/12371
I'd be happy to post the file, but it looks like your request came before r31252 was published, so you may not need it anymore. I just tested r31263 and the FLAC file isn't having the same issue I described before. ::)
Cheers and thank you again, saratoga.
-
Hi, I am new here, and first of all I want to say hello to everybody. ;D
I have installed latest version r31359 with the bootloader (sadly enough, not a dual boot, as far as I see) by DFKT (http://www.anythingbutipod.com/forum/showthread.php?t=66292). Am amazed but also confused by the huge amount of options.
Problems encountered:
1) USB not compatible with M$ WIN XP
2) system freezes quite often, and I already got a couple of heart attacks fearing of having damaged the Clip Zip (one needs to press for at least 30 secs the top button for restart the MP3 player).
I have a strong impression the RDS system works, even if only partially, but the line where it is shown is below the visible area of the screen. I actually can see the top of some letters. Would it be possible to resize the screen? Or to delete the useless separation line that prevent seeing the RDS line?
-
...
Hi Gurglin,
The USB is definitely a work in progress, but you can still use the USB connection while booted in the Sansa firmware. The bootloader you mentioned is the same one that I use, and it just requires you to press the down volume as you turn it on to boot into the Sansa side.
As for RDS, it has been working for me and I didn't experience the issue you talked about, probably because I use a different theme. Try changing your theme to one of these: http://themes.rockbox.org/index.php?target=sansaclipzip I'm currently using lebellium Samsung-like, so I know that has RDS support.
As for your system freezes, I must say that I haven't experienced anything like that except when I was connected through USB. Even then it wasn't a true freeze since after disconnecting the USB, waiting for a bit since it doesn't automatically disconnect, and then pressing the power, everything was good. If this is the type of freeze you mean then that's the reason. Just use the USB from the Sansa side for now. Other than that, it's been super stable.
-
I have installed latest version r31359 with the bootloader (sadly enough, not a dual boot, as far as I see) by DFKT (http://www.anythingbutipod.com/forum/showthread.php?t=66292). Am amazed but also confused by the huge amount of options.
The bootloader is dual boot. You have to hold the left or vol- button for the OF to boot. I just uploaded an official v4.0 bootloader there, you might want to upgrade if you didn't already.
I have a strong impression the RDS system works, even if only partially, but the line where it is shown is below the visible area of the screen. I actually can see the top of some letters. Would it be possible to resize the screen? Or to delete the useless separation line that prevent seeing the RDS line?
Are you using my theme? If so, RDS works fine in the .fms - try to reload the theme. (I assume you are using at least some 3rd-party theme, otherwise you wouldn't have an .fms to delete lines from.)
In any case, you might want to run checkdisk on the Zip and SD card - maybe your memory is corrupted.
-
I just uploaded an official v4.0 bootloader there, you might want to upgrade if you didn't already.
Thanks for the new bootloader, dfkt. I'll have to try your theme sometime now that you updated it to support RDS.
I'd probably use your custom build with the extra patches as well, but the last item "channel swap" makes it seem as though the left and right channels would be swapped. Not sure why I'd need/want that, so I used your list of patches and compiled my own a few days ago.
-
dotrockbox, dfkt, thanks for your answers and advices. You are right. Everything works fine now.
-
I'd probably use your custom build with the extra patches as well, but the last item "channel swap" makes it seem as though the left and right channels would be swapped. Not sure why I'd need/want that, so I used your list of patches and compiled my own a few days ago.
Channel swap is of course optional, not mandatory. It's enabled/disabled in sound settings > channel modes.
-
I'd probably use your custom build with the extra patches as well, but the last item "channel swap" makes it seem as though the left and right channels would be swapped. Not sure why I'd need/want that, so I used your list of patches and compiled my own a few days ago.
Channel swap is of course optional, not mandatory. It's enabled/disabled in sound settings > channel modes.
Oh, that's awesome. I'll totally use it then. That way if I pick up a pair of IEMs that are more comfortable to wear the wrong way (like looped over the ear instead) I don't have to mess with a cable swap.
Thanks, dfkt.
Edit: By the way, I just installed the new bootloader and r31375 and found that it doesn't pick up any radio signals anymore at all. I'll have to revert back to previous versions to see what the culprit might be, because there were at least 20-25 stations before this. Must be a new bug somewhere. Anyone else experience this?
Edit 2: This is resolved and it was my own fault. I didn't have the headphones connected, so naturally the signal was extremely weakened.
-
I notice that with the clip zip white letters and graphics tend to take on a reddish tint at lower brightness levels (0-3).
I have two 8G clip zip -- one bought from Radio Shack USA which seems to have less of the problem, the other bought from Costco (slightly improved casing) which seems to exhibit the problem more. Could this situation be due to the two known OLED display manufacturers for this player?
Both players have the same Rockbox firmware.
Where in the Rockbox code should I look to adjust contrast, saturation, hue, etc. (if possible) for the clip zip?
-
Yes, it could very well be possible that the reddishness at low brightness differs between the two known OLED types.
Rockbox currently uses the same brightness curve as the original firmware (at least that's the intention). This is basically a simple linear curve, for each of the three R,G,B components. Possibly the B and R components are swapped for the brightness calculation, this is very hard to determine for the Visionox display I personally have, but should be easier to determine for the Wisechip type of display.
In principle, rockbox could implement a more advanced brightness curve, simply by creating a table with R,G,B intensities for each brightness level. The only concern then is whether this curve is reasonably the same for each individual display of a certain type, but it would probably be an improvement over the current situation anyway.
-
We now have working install directions on the SansaAMS wiki page (see first post of this thread). Alternatively you can also use one of the unofficial bootloaders on the ABI forums. As soon as a new release of rbutil comes out, that method will also work.
-
As soon as a new release of rbutil comes out, that method will also work.
Or use an svn build of Rockbox Utility (yes, still svn builds -- there are no builds from git yet). I've uploaded a build just a few days before the switch to git, so it's still rather current. See my signature for the link.
-
So the manual should be building now. I think once we have cabbie working for the Zip we can start taking screen shots in the sim and get those finished.
Bertrik: whats the status of the cabbie port?
-
The cabbie v2 port from http://www.rockbox.org/tracker/task/12390 looks fine to me.
I don't really know what to do now, it appears there is a bug in our theme loading code that loads everything about the theme, except the font.
-
The cabbie v2 port from http://www.rockbox.org/tracker/task/12390 looks fine to me.
I don't really know what to do now, it appears there is a bug in our theme loading code that loads everything about the theme, except the font.
This is something I ran into when originally committing cabbiev2 years ago. The issue is that at startup the default theme doesn't actually get applied like a normal theme does when you select it. So instead, one has to set the defaults in settings_list.c to correspond to the values needed for the theme (e.g. font, background color, etc).
-
Just a note to say I've joined the clip-zip testing fun. So far it looks pretty good for an 'unstable' release, although I note that a good few screens (including many applications) are struggling with the screen width. Also it 'failed to create file' for battery tester app, as well as failing to create a scrobbler log, and last played etc, although after a restart it then worked OK.
One annoyance, 'list playlist contents' only works for playlists on the main device - the ones on the micro SD card work as playlists, but don't show up in the 'playlist catlogue' menu.
I also had a couple of very long shutdowns, where it seems to have failed to save the option changes I had made.
Overall though, excellent (as usual) .. I haven't used Rockbox since an old X5 years ago, and am pleased to get back to it. Well done to all who contributed (the cheque is in the post).
-
Also it 'failed to create file' for battery tester app, as well as failing to create a scrobbler log, and last played etc, although after a restart it then worked OK.
Already fixed.
-
Already fixed.
How about the games some apps that wont fit on the screen.
ex. bubbles, etc.
Sorry if my next question is too off topic
do we have fonts japanese & korean some of my id3tags cant read by the player.
-
How about the games some apps that wont fit on the screen.
ex. bubbles, etc.
Not fixed.
do we have fonts japanese & korean some of my id3tags cant read by the player.
Sure, unifont and probably others.
-
Also it 'failed to create file' for battery tester app, as well as failing to create a scrobbler log, and last played etc, although after a restart it then worked OK.
Already fixed.
Good news, thanks.
Do I need to turn in some sort of bug report on the 'playlist catalog' issue, or does mentioning it here count?
Screen width is annoying in several places, OTOH one reason I picked it (over something like a Cowon J3) was the small size, for hauling up mountains (and the fact it runs Rockbox - the Original firmware on most players really struggles with large numbers of files, and the battery life is not even close to advertised for the sort of files I play).
-
Most images need to be edited by hand.
If you take the iriver h10 5gb image files and reduce by I think it was 75% you will get the right dimensions for those images.
If someone could tell me the plugins and the image files needed by each plugin I could easily adapt them.
-
It's not as simple as just reducing plugin images to 75%, you'll get severe blurring. Many images/icons have features that are aligned to pixels.
Also some of the unfinished plugins make assumptions about how many "tiles"/cards/blocks/etc you can fit horizontally or vertically, you need to take this into account (which means reading the code and try to understand the screen layout of a specific plugin, possibly modify code).
IIRC, the SansaClip wiki page has some info about the missing graphics for plugins.
-
I've got one .ogg file (Q=2, about 93 kb/sec) which RB refused to play on the clipzip, although external players (mediamonkey, for instance) could play the same file (from the clipzip flash memory) just fine. Is there some place I should send it to for debugging purposes (may not be specific to the clipzip I guess)?
-
I've got one .ogg file (Q=2, about 93 kb/sec) which RB refused to play on the clipzip, although external players (mediamonkey, for instance) could play the same file (from the clipzip flash memory) just fine. Is there some place I should send it to for debugging purposes (may not be specific to the clipzip I guess)?
File a bug report with a link to the file. Bug tracker is on the left side of your screen.
-
Done.
Another one, which may already be fixed (?) - if I connect the player with RB already running the PC doesn't see the drives correctly (it sees USB drives F and G, but both have zero size, and attempts to access them get a message 'please insert a disk in drive F:'. Connecting with player turned off (and therefore RB not running) works fine.
Not sure I can even flyspray this since there probably isn't a clip zip category yet (there having been no real release?).
-
I made graphics for the solitaire plugin:
http://dl.dropbox.com/u/9353289/sansa-cz-solitaire.zip (http://dl.dropbox.com/u/9353289/sansa-cz-solitaire.zip)
-
I made graphics for the solitaire plugin:
http://dl.dropbox.com/u/9353289/sansa-cz-solitaire.zip (http://dl.dropbox.com/u/9353289/sansa-cz-solitaire.zip)
Can you make a patch and post it in the tracker, please?
-
I made graphics for the solitaire plugin:
http://dl.dropbox.com/u/9353289/sansa-cz-solitaire.zip (http://dl.dropbox.com/u/9353289/sansa-cz-solitaire.zip)
Can you make a patch and post it in the tracker, please?
Can you make a patch for binary images?
-
Can you make a patch for binary images?
Yes, there are tools for this (like xdelta). However, since the source code for the plugin is GPL you need to distribute the sources for the binary as well.
Not sure I can even flyspray this since there probably isn't a clip zip category yet (there having been no real release?).
That's no real problem -- use "Another" and state the player in the description.
-
nkorth, I prepared a gerrit thingy with your graphics and it looks good on the clip zip.
See: http://gerrit.rockbox.org/r/#change,79
Can you tell us your real name so we can add you to docs/CREDITS for your contribution?
-
Can you tell us your real name so we can add you to docs/CREDITS for your contribution?
I'm Nathan Korth. Thanks for your help; I'm new to Rockbox development!
-
I think that is player had some big problems with APE files... when I run it after about 30 seconds it starts a terrifying disturbing sound... an hardware limitation maybe?
FLAC and OGG, for now, runs flawlessly, but I noticed that with an ALAC big file (96000hz/about 3000kbps) it stucks for a second... another hardware limitation?
I noticed generally that it runs good, but one time it stucks and I had to shutdown the player... but it's an unstable port, it can be normal right?
-
High compression APE is really, really expensive to decode, and many of our targets are not powerful enough to do it in realtime. FLAC is much cheaper.
-
I think WV is less expensive to decode... I use ape because it can read embedded covers, with FLAC files it can't. I think that WV works good, I will use it :)
-
I think WV is less expensive to decode... I use ape because it can read embedded covers, with FLAC files it can't. I think that WV works good, I will use it :)
http://www.rockbox.org/wiki/CodecPerformanceComparison#AMS_AS3525v2_w_47_24MHz_PClK_40ARM926EJ_45S_41
-
i just got a new clip zip and even though i installed rockbox v1.2.13 the sound level of the device is just too low. i hardly hear the music when i'm outside. so anyone knows how to get the sound higher?
-
Something is wrong. First thing I would do is boot into and check volume with the OF. That would help determine if you have some Rockbox setting way out of whack or if it is your unit. May also help to know what part of the world you are living in / purchased the unit.
-
Mmm... this not run flawlessly yet... rarely (also with flac files) it makes a little but loud fuzz and skip the song... it's rare, but happened... the first time it happened with a precise file at the same time, I reconverted the file and update the build and that song runs good... but now happened again with another song... I replayed the song and it plays good, what the hell :O
-
Hi,
Have any of you used brickmania on your Clip Zip?
It appears to be broken. I can play all the way to the end of
a level and break all of the visible bricks, but I can't get any further.
The ball and the paddle respect the visible boundaries of the screen,
but I think that the game may believe that there are still bricks further
out.
Note that there are fewer bricks on this the Clip Zip version than on
some other variants. See the screenshots that I took below from the simulator
version of the Clip Zip and Ipod Nano 2G.
-
It appears to be broken. I can play all the way to the end of
a level and break all of the visible bricks, but I can't get any further.
Wouldn't surprise me. The wiki says it still needs to be ported to the Zip's smaller screen.
-
I'm looking to purchase (and Rockbox) either a Clip+ or a Clip Zip, and am inclined toward the second, but what's holding me back is the port status on the Zip, which is described as "fine for day-to-day audio playback," although the status seems to be a bit outdated. I know the Clip+ is stable, but just how stable is the Clip Zip port (are there any outstanding issues compared to Rockbox on the Clip+). Should I opt for one or the other?
-
I'm looking to purchase (and Rockbox) either a Clip+ or a Clip Zip, and am inclined toward the second, but what's holding me back is the port status on the Zip, which is described as "fine for day-to-day audio playback," although the status seems to be a bit outdated. I know the Clip+ is stable, but just how stable is the Clip Zip port (are there any outstanding issues compared to Rockbox on the Clip+). Should I opt for one or the other?
Well, I'm having an annoying issue with Clip Zip (auto-skip tracks randomly but it's very rare and it's not a common issue) but for the rest is almost stable, except for the USB connection, a little bit slow.
-
It works just fine for me. I bricked one recently, but I think it was not caused by RockBox anyway.
-
USB works one time out of 10 for me, it is extremely annoying. Or more likely, it works once and then never works again (sometimes it is detected by the computer but all transfers freeze) until I reinstall Rockbox from scratch.
-
I recently manually Rockboxed my Clip Zip and everything is more or less functional. There is one bug I have encountered, though, that freezes the player (displays only the USB graphic with no status bar, until I am forced to power if off) when I connect it to my computer via USB, but this only happens when the Clip is already powered on beforehand. When I connect it while it is powered off, everything works well after it boots and the computer detects the device correctly. Interestingly, the status bar is not obscured when the Clip is connected the right way.
I'm thinking of updating to the latest Rockbox build. When I extract the latest .zip, do I just overwrite my current .rockbox folder with the contents of the latest one? Or do I totally replace it? Also, do I have to re-install the bootloader as well? Thanks.
-
Newegg is having a sale on Clip Zip 1.1s and I always wanted to try Rockbox so I figured I would give it a shot, but then I noticed some guides don't include version 1.1, is it just the same as 1 or will it not work?
-
I know the Clip Zip can come in a few hardware configurations, for example possibly using different FM tuner chips and different display types ("Visionox" or "Wisechip"). I haven't seen any reference to a "1.1" version yet and I'm curious what the difference could be. Do you have a direct link to a place where the 1.1 version is mentioned?
-
I know the Clip Zip can come in a few hardware configurations, for example possibly using different FM tuner chips and different display types ("Visionox" or "Wisechip"). I haven't seen any reference to a "1.1" version yet and I'm curious what the difference could be. Do you have a direct link to a place where the 1.1 version is mentioned?
http://www.newegg.com/Product/Product.aspx?Item=N82E16855125168&nm_mc=EMC-IGNEFL072612&cm_mmc=EMC-IGNEFL072612-_-EMC-072612-Index-_-MP3MP4Players-_-55125168-L0H
Though someone elsewhere told me that the 1.1 is referring to the screen size, which I notice now the quotation mark indicating inches.
-
I've been using Rockbox on my Zip for around 2 weeks and love it. The learning curve was a bit overwhelming at first with all the configurable options and navigation but after a while it's become second nature.
I have noticed one oddity but I'm not sure it has anything to do with Rockbox.
None of the EQ functions nor the Bass and Treble controls work when listening to FM Radio. They work fine when not in FM Mode.
I'm inclined to think it's a limitation of the device rather than a Rockbox issue. Trying to isolate and troubleshoot I booted into the the original Sansa Firmware and tried EQ with FM and got the same results.
Would be nice to have some tweaking with it in FM Mode but not a big deal. I figured I'd post anyway just in case or someone else might try it and wonder what's going on.
-
Indeed, none of the tone controls has any effect on FM radio.
For audio coming from (for example) an mp3 file, we have full control over the data, so we can implement digital filter (bass, treble, equalizer), stereo panning etc. We don't have the FM radio signal available as data, so we can't apply any digital effects.
-
Hi, I just joined the RockBox community, so forgive me if I seem out of the loop, because I probably am. :D
I did a manual install onto my AMSv2r1 4GB Zip, and I love it. Every so often, though, I have a shutdown hang. It's hard to reproduce, but I think it may have something to do with the setting's configuration files. It usually powers down without a hitch.
This may not be related, but I had a memory glitch in what I think was the actual hardware while using the original Sansa firmware. It caused the Zip to stop responding, forcing a reset and reformat. Among other things, it duplicated all my files and erased the internal memory. Everything else it locked out and I couldn't access it. The next firmware update may have covered up the flaw. I'm convinced that it still exists, but I don't know how to confirm it. Any sort of memory testing utility that may help?
Is there some sort of documentation on the bootup/shutdown processes? That might help tremendously.
Thanks in advance,
D.J.
-
[edit2]I'm leaving my original post to document my stupidity. I should have RTFM. To be fair, I figured the the wiki had the info I needed. I'm not about to use my real name or some made up 'real name' to change the wiki page, however it needs to be changed to point out that in order to uninstall you MUST use the dual boot feature. As they stand the uninstallation instructions in the wiki do not work, and as we've learned today not everyone wants to read through a manual for information that's supposed to be in the wiki.
[original post]
I searched this thread for "uninstall" and couldn't find anything. First thing I tried was the uninstall option in rockbox utility, it uninstalled rockbox but the bootloader was still there and just comes up "file not found" and "plug USB cable". Rockbox utility couldn't uninstall the bootloader. I tried putting the fireware file in the root directory as per sandisks method of updating the firmware but I guess the rockbox bootloader doesn't autorun a firmware update if the file is there. I've tried deleting everything, and formating, but no matter what I do I can't get rid of the rockbox bootloader in order to restore the original firmware. Maybe I should have read the site instructions first, but they're more or less what I did and they didn't work and don't still.
Now, I could just carry on using rockbox. If I could figure out how to simply play a folder and it's subfolders instead of having to drill right down to a specific album or such then I'd be happy with that. But it would be nice to know how to restore this thing.
[edit]I should add that I really think the wiki should be updated if uninstallation is impossible or requires steps not listed, it's not like I would have installed if the instructions hadn't been as easy as 'use the utility' and 'copy the file'. I apologize if this is too much like a tech support question, but I am at least pointing out that the uninstallation routines need development, or at least a warning added to the wiki.
-
You should be using the manual for directions. The wiki is only updated if users want to, and may not be current or correct once the manual is written.
-
i just put rockbox on my clip zip and it is working fine. I love that I can still boot into the original software if i want...
if Sandisk released a firmware update for the zip, how would that affect rockbox on my zip? would I have to reflash both?
-
if Sandisk released a firmware update for the zip, how would that affect rockbox on my zip? would I have to reflash both?
I doubt there will be anymore firmware updates for the Zip, but if there are you will have to wait for an updated version of rbutil and then reinstall the bootloader using the newer firmware version.
-
What's the latest status of the Clip Zip port? I'm leaning towards buying one. I'd get a Clip+ but the screen looks miniscule.
Is it still manual install only? (The RB user manual says it is, so I assume yes)
Are there going to be any more fixes for the apps?
Anything I'm missing?
If nothing's changed since November and the Clip Zip never gets to stable port status (or won't by March 13) then I'll get the Clip+.
Cheers!
-
Just one or two plugins are not working yet, and apparently the color of the screen is a bit off for some people (but we can't reproduce that). Other than that, it's as stable as the clip+.
-
What's the latest status of the Clip Zip port?
http://www.rockbox.org/wiki/SansaClip#Sansa_Clip_Zip_port_status
-
Thanks for the replies. I wish the RockboxUI simulator were working so I could see what the screen looks like. Maybe I can find some screenshots.
-
I wish the RockboxUI simulator were working so I could see what the screen looks like. Maybe I can find some screenshots.
Sim works fine, and there are screenshots in the manual ...
-
Last time I looked, I swear there wasn't a sim for the clip zip. Maybe I'm fat-fingering it somehow, but I can't get all of the buttons to work. It seems like their locations or size isn't right. Might just be this computer though, it's been a little off the last few days. Time for a chkdsk.
-
I'd probably use your custom build with the extra patches as well, but the last item "channel swap" makes it seem as though the left and right channels would be swapped. Not sure why I'd need/want that, so I used your list of patches and compiled my own a few days ago.
Channel swap is of course optional, not mandatory. It's enabled/disabled in sound settings > channel modes.
I know that this is an old thread, but I just wanted to say thanks to you dfkt! I needed to be able to swap channels on my rockboxed clip zip. I found this post, which led me to your anythingbutipod post here:
http://anythingbutipod.com/forum/showthread.php?t=66292
I was able to get your patch onto my zip, and I now have the channel swap that I was looking for. Awesome!
Thanks again!