Sansa Clip Zip

[dotrockbox]

...

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.

[dfkt]

I have installed latest version r31359 with the bootloader (sadly enough, not a dual boot, as far as I see) by DFKT. 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.

[dotrockbox]

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.

[Gurglin]

dotrockbox, dfkt, thanks for your answers and advices. You are right. Everything works fine now.

[dfkt]

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.

[dotrockbox]

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.

[TexasRockbox]

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?

[bertrik]

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.

[saratoga]

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.

[bluebrother]

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.

[saratoga]

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?

[bertrik]

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.

[saratoga]

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). 

[GSV3MiaC]

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).

[saratoga]

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.