5g Ipod - buttons problem :(

[condictio]

 Hi all,
I hope that I'm posting this in the right forum, sorry if not. Anyway I got a problem with buttons and this is - in my opinion - a hardware problem.
I'd like to stress, that I really  like rockbox and it's  much better than  original firmware, so I'd like it to work properly.

Here's the problem. Since I've installed rockbox, there is a continuous problem with responding of the buttons. Shortly - they almost never  respond on the first and next few  keypresses. I know there is an option "first keypress backlight only" - but it's turned off and it still happens. And it's not only the first keypress.  The wheel itself works OK, so it's only the buttons. Sometimes - but very rarely - it reacts properly on the first keypress.I haven't noticed it when using  original firmware and I wonder what is the possible cause of this problem, which is really annoying. :-(  If someone has an idea how to fix it, I'd be very grateful.

[Mthrsuperior]

I've noticed this too.
For me, it's not that the buttons don't respond it's that there is a delay of 1-2 seconds and I tend to get impatient and keep pressing.

I too thought I may have had the first press = backlight enabled but I don't.

Any suggestions are appreciated.

Thx

...edit to add:   it seems that the delay is in the display, not the action of the buttons.  For example, I press "pause" and the music pauses instantly but the display icon doesn't change to the pause icon for 1-2 seconds.
...edit again.....I read in another thread about current technical limitations impacting the display refresh speed.
I guess there's our answer.
 

[bascule]

...edit to add:   it seems that the delay is in the display, not the action of the buttons.  For example, I press "pause" and the music pauses instantly but the display icon doesn't change to the pause icon for 1-2 seconds.

Not necessarily, that particular effect may be to do with crossfade. I get that all the time and also next track info disappearing from the WPS before that track starts, even though I only have it set to 'crossfade on skip only'

[condictio]

In my case, there is also this delay (about 1-2 sec.), but it's something different than non responding at all. In the first case I push the button and nothing happens, but after a few seconds it reacts.  In the second case I push the button, nothing happens, I wait and still nothing happens. If it's only a delay you can feel the disk starting to spin after keypress, what means that it reacts, but the reaction itself is slightly delayed. If there's no reaction - exactly nothing happens after keypress, you can wait and wait and still nothing, the disk doesn't spin and it looks like the device doesn't "know" that the key has been pressed.   I tried to wait, but after a minute you can't say that it's a delay - it obviously doesn't react at all. If it's only the firmware  I can live with it hoping that sooner or later this problem will be solved. But I'm a bit scared that maybe something is wrong with my ipod itself, that it's broken or something...

[Krellion]

Please remember that Rockbox on the iPod is still a major work in progess.

A lot of the code hasn't been tweaked to run the best it can, so there will be times where there'll be a delay in an event happening, especially if there is music playing. Sometimes the button press event won't be seen at all and you'll just have to try again.

[xelli]

Sorry for reviving this old topic.

I recently installed rockbox on my 5g 30gb ipod and I'm experiencing the exact same issue. Not to be rude or anything, but after two years I thought more people would be annoyed by this. Is there still no solution?

[Llorean]

Rockbox is entirely a volunteer effort. Things get fixed  by the people who are annoyed by things. If the people who are annoyed by things instead say things like "I'm amazed this isn't fixed" then go on to say "But I don't know how to fix it" when it's suggested they could work on it, it just doesn't happen.

Rockbox is a project entirely by volunteers. They work in their spare time, doing things that interest them. "Not to be rude or anything" but if you really want to see the problem fixed, start learning C.

I would guess, though, that you're either waiting on disk spinup (enable dircache) or experiencing the fact that the iPod Video isn't terribly fast for its screen size. Since you haven't said anything about your problem other than it's the "exact same issue" (and noting that their symptoms are slightly different for each of the two posters, I don't know who it's the same as) it's hard to even begin to offer suggestions.

Maybe you'd like to type out when your player is and isn't slow, what you're doing at the time, and possibly even what settings you've changed from the default, as well as exactly what SVN revision you have installed?

[dreamlayers]

The button issue is distinct from disk spinup.  Sometimes my iPod totally ignores a button push.  This happens much less or even not at all with the original firmware. It used to be annoying when I first started using Rockbox, but it's not a problem right now.  Either it has been fixed or I've adapted to it.

It only seems to happen to very short button pushes.  My first thought was that the buttons weren't polled often enough, but they're handled by GPIO interrupts.  I see potential issues there however:

• Each time an interrupt happens, buttons start out as BUTTON_NONE, so an interrupt may erase a previous button press.
• What does the undocumented outl code in ipod_4g_button_int do?  If it acknowledges the interrupt there, a second interrupt that happened between the button read and that point might be missed.
• Because of the clickwheel, a there may be interrupts in quick succession, as the user touches the clickwheel and then presses the button.

[Llorean]

If it happens less with the original hardware, but still happens, then it's a hardware problem. This more or less means your problem is different from the rest of these peoples'.

The other issues may be concerns, but it's impossible to investigate properly on a player with hardware issues since you won't know when they're causing the problems vs when the code is causing the problem.