Rockbox General > Rockbox General Discussion

Sansa Fuze v2 button responsiveness

(1/2) > >>

expos1994:
I've been running rockbox for gosh, years it seems now. Most of that time was on a Sansa E200 model.  I wore out another volume wheel on my last E280 and decided to upgrade to the Sansa Fuze v2 about a year ago. Well it seemed to work well most of that time, but I've noticed now that the buttons aren't very responsive. Sometimes I have to push the button 6 times to get it to process the keypress. Other times it will work fine. I don't believe this to be a hardware problem. The button 'clicks' just fine, the unit hasn't been abused and sometimes it operates just fine.

Another thing I've observed it doing is going to the playlist viewer intermittently. And it also turns the backlight on. I notice this most when I'm driving down the highway at night and I keep seeing a light come on and it's the Fuze showing the playlist viewer. This is annoying... but also a drain on the battery. Any ideas why that is?

And here's another observation while I'm on a roll. Sometimes when I switch to a track, the imbedded album art won't display. Seems to be kind of random. Well if I skip to the next track and then back again, the art will display "coming from the other direction".  Does that make any sense to anyone? It could be a theme problem I suppose I use that thinmod theme. But never used to have a problem.

I have gone back to build 3.12. But I might go back even further to see if I can find a build that doesn't do this. But does anyone have any ideas? Anyone else seen these 'bugs' on the Fuze or other hardware? Could this be a hardware problem?

expos1994:
Went back to 3.11, which is from April 2012 and it appears I'm not having nearly the problems. I haven't put it through a rigorous test, but initially it seems to be running better.

I haven't observed the album art problem yet and the buttons are responsive.

I have noticed that occasionally when pressing 'next track' it will jump to the playlist viewer. I'm not sure why that might be. Maybe somehow that button is getting temporarily mapped to skip the track and open the playlist viewer. As far as I know the only button that is supposed to open the playlist viewer is the 'home' button.

Going all the way back to April, I'm not sure what enhancements I'm missing, but this right now seems to be more stable than the more recent builds.

expos1994:
Update:

Well I will say that the buttons are more responsive with this older build, which further leads me to believe this is a software problem. They aren't perfect... but I don't have to hammer on the 'next' button 6 times to go to the next track.

I am still seeing the problem where the 'now playing' screen will jump to the playlist viewer and turn on the backlight seemingly at random. When was this 'feature' added.

Am I the only person reading these forums that uses a Fuze v2? It'd be nice to know if anyone else is seeing these problems. Rockbox has always been pretty stable. I mean a data abort crash here and there I can see, but these type of bugs are just not normal for this project.

Sakura90:
I've had a Fuze v2 for a long time and always worked like a dream (except, while connecting the USB, some crashes and a "semi" brick once, but now it seems more stable). Everything else works as expected. I'm on 3.12 and the buttons work fine.

expos1994:
Thought I should update this...

My problem was getting progressively worse... to the point where I wanted to smash it on the sidewalk. Very frustrating to push a button 10 times before it does anything. And the screen coming on at random moments was killing my battery life.
I was about to chalk this fuze up as a lemon and buy another one... or go back to the E200.

Anyways, my last resort today was to go all the way back to stock. I put the original firmware back on it and deleted the .rockbox folder. Then I put a new bootloader on it and downloaded the latest dev build. I powered it up and everything seemed fine! Thank God. So I started pulling over the config file, Eq settings, themes, fonts, icons etc. I've been using it all day today and everything is working as it should again. So I'm pleased and if it happens again I know how to fix it.

However, something got corrupted in there. I have no idea what. Is there some kind of NVM that can get corrupted? I'm not familiar with it. This was a very real bug though... and it was a software problem.

Navigation

[0] Message Index

[#] Next page