Sansa Fuze+

[sdf5]

What I would like to see in the Fuze+ port is the ability to operate the player (that is, to go to the next/previous item, increase/decrease volume, start/stop playback) without the use of touchpad, only using the player's buttons. This would allow to put the player in the playback mode, lock the screen and then only use the player's buttons to operate it -- a useful functionality to have if you carry the player in your pocket.

Since the player has only three (3) buttons (Volume Up, Volume Down and On/Off) some creativity would be needed to implement the above. Perhaps it could be done the following way:

   Volume Down pressed for less than 1 sec = go to the previous playback item
   Volume Down pressed for more than 1 sec = decrease volume
   Volume Up pressed less than 1 sec = go to the next playback item
   Volume Up pressed more than 1 sec = increase volume
   On/Off pressed for less than 1 sec while in playback mode = start/stop the playback
   On/Off pressed for more than 1 sec while in playback mode = unlock the screen
   On/Off pressed for less than 1 sec while NOT in playback mode = lock the screen

Nobody thinks it's a good idea? The touchpad works pretty poor for me, it'd be nice to be able to avoid using it in the playback mode.

[pamaury]

I'm sorry but I don't see the point of it. If you don't like the touchpad, why did you bought the Fuze+ in the first place ? With custom keymaps, I think it is possible to achieve something close to what you want but it will never make it to our codebase I'm afraid, at best you would need to write it yourself (maybe with some help) and compile your own version of Rockbox.

[sdf5]

If you don't like the touchpad, why did you bought the Fuze+ in the first place ?

I didn't know that  the touchpad would be that inconvenient to use before I bought the player. Besides, this feature would allow to operate the player without having to look at it, a nice feature to have if you carry the player in your pocket and don't want to take it out every time you want to start/stop/skip ahead/go back. I thought it'd be  simple to implement something like that and It could be an optional feature too, that is, the user would change a config setting to enable it.

[saratoga]

You're welcome to implement it yourself, but those kind of options are generally not welcome in the official code.

[bthomson]

@bthomsonl:
can you try with this build https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip and report here exactly what is written on the crash screen please ?

Thanks for your help! I really appreciate it. I tried that build today but I think I borked the install because the bootloader now says "Bad Checksum". This weekend I will try to download again and give it another shot.

Hello, I am sorry I have not replied for a couple weeks. About a week ago I got this build working and today the player has locked up again. Here is what happened:

1) Audio playback stopped. Player was still on the "while playing screen", but the counter was no longer advancing.

2) Buttons were still working at this stage. I was able to hit back to go from the "while playing screen" to the menu and then back to the "while playing screen" again.

3) Now buttons have stopped working, sorta. All the buttons including volume up, down, power, and the touchpad will light up the backlight, but the player doesn't respond otherwise. It's stuck on the while playing screen. The backlight turns off after the configured delay period (10s).

4) Player has been in this state for more than the 5 minute idle shutdown so that is not activating. I force shut down the player by holding power button.

When I installed the build pamaury provided last week my settings were reset to default (I think that's because settings are stored in the .rockbox directory. I moved my old rockbox directory to .rockbox-old before unzipping). I decided to stick with the default settings for a while and did not experience any lockups while in default settings. However, yesterday I started changing the settings back to my preferences and today it has locked up. This could be a coincidence or it could be one of the settings I chose is the problem. So unless anyone has anything they would like me to try, my next step will be to reinstall pamaury's build and use the player with the default settings for a few weeks to see if I can reproduce the lock up that way.

I used this same SD card in a Rockbox Clip Zip for a while before installing pamaury's build on the Fuze+ and didn't experience any problems during that time. Well, except that Clip Zip sucks compared to Fuze+ 

[halonachos117]

Perhaps you should create a bug report in Flyspray, as this forum isn't really meant to be used to discuss bugs. I would recommend uploading your config.cfg file, which is usually located in .rockbox (or in your case, .rockbox-old). From there, perhaps the individual settings could be tested one-by-one. I would also try posting a hyperlink right here to said bug report, so as to allow the rest of us to know this report exists.

[gevaerts]

Perhaps you should create a bug report in Flyspray, as this forum isn't really meant to be used to discuss bugs.

While a bug report would certainly be useful, this is a development thread, and as such I'd say bug reports can be relevant here

[ildarion]

Hey, it's been a while since I just annoy you with a function that does not work (just for me?) and probably rarely used by users: alarm clock.

Am I the only one? Do you will fix this? (if it's not too much work)

[pamaury]

@bthomson: I'm sorry but without more details, I simply cannot find the bug. If you think it might be related to a setting, you should reset them all and change them one by one until you trigger the bug. Otherwise I'm blind, I cannot know what is crashing.

@ildarion: I was not aware that there was a problem with the alarm clock, I will have a look.

[halonachos117]

Ildarion, what exactly is happening (or not happening) with the alarm? Have you updated you bootloader to the newest version?

[ildarion]

My bootloader have ~2 months old (I can"t upgrade for now)

So basicly, the alarm don't trigger. I choos the time, press the right touch for confirm, rockbox say alarm will be trigger in XXmins but never do.

[pamaury]

@ildarion: can you be more specific ? If you read the documenation http://download.rockbox.org/daily/manual/rockbox-sansafuzeplus/rockbox-buildch11.html#x14-17100011, you will see that powering down and up the player after having specified an alarm will cancel it. I am also unsure of the behaviour of the alarm in case you specify it and don't power off. Anyway, alarm works on mine if I just setup the alarm and power off. I'm running bootloader V2 and latest version of Rockbox.

[ildarion]

I just setup the alarm and power off.

I do the same (no power ON, just setup and power OFF) and don't work. I try regularly this since 1 year. But actually I don't have the last update (few months old) so if they work for you, it's just me.

[metaphys]

I still don't understand how this is possible, especially with both SD and eMMC. And if you suffered from it, potentially anyone could, your custom build does nothing special about SD and MMC. And I don't see how Rockbox could possibly brick a SD card which is an issue. Metaphys, could you send me (again) the SD card so I can have a look at it ?

Given the rate at which it's happening a lot of people should be suffering of it, if it was a common problem. The Sd card burned in only a few months! (just as the intern if I remember correctly). I'm starting to think it may be related to some storage controller on the device (is there any common micro-controller for eMMC and SD on the F+?)
Before I send it to you (it might take a while, i'm living in Romania now...) Are there some stuff you would like me to test first?

[pamaury]

No, the eMMC/SD controller is the SoC itself and it has dedicated hardware, plus all transfers are CRC protected so it's unlikely that the host be able to send strange commands that would somehow brick the card. Did you try to contact the company that produced the card ? They might be interested or even know about issues. Appart from this, no I don't have any other suggestion because if it doesn't work when plugged to your computer, something must be seriously wrong with it.