Support and General Use > Hardware

5g Ipod - buttons problem :(

<< < (2/2)

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.

Navigation

[0] Message Index

[*] Previous page