This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#5230 - Keypad HOLD doesn't let go until scrolling is used
Attached to Project:
Rockbox
Opened by Mateusz Radwan (mr666) - Monday, 24 April 2006, 22:14 GMT+2
Last edited by Torne Wuff (torne) - Wednesday, 24 February 2010, 13:21 GMT+2
Opened by Mateusz Radwan (mr666) - Monday, 24 April 2006, 22:14 GMT+2
Last edited by Torne Wuff (torne) - Wednesday, 24 February 2010, 13:21 GMT+2
|
DetailsWhenever the HOLD switch is turned off, the hold icon in rockbox disappears, but hold actually doesn't let go. I can't use any keys until scroling is used. Scrolling left or right is the only thing that actually switches off hold. It can be pretty annoying as I use HOLD a lot.
|
This task depends upon
Hopefully this will become fixed some point soon ^_^
Easily reproducible in file (tree) browser.
Possibly related problem.
Plug-ins that require you to use the hold to get to the menu frequently show same symptoms (“Whenever the HOLD switch is turned off, the hold icon in rockbox disappears, but hold actually doesn't let go.”) but scrolling doesn’t fix it. Controls are unresponsive. Sometimes after using the hold again or pressing random buttons it will resume function, other times I have to reset (select + menu). It doesn’t always happen but happens a lot in RockBoy especially when you go back and forth to the menu and use a buggy game from PDroms. I've also noticed it in RockDoom r18205 after I've been playing a while.
Good luck with Version 3.0 Thanks everyone for the wonderful firmware.
In reference to Eliot using the hold button to access the menu in rockboy is extremely unreliable and often takes more than 10 tries to successfully open the menu
What I see is a problem in button-clickwheel.c. Interrupts are occurring, but (status & 0x800000ff) != 0x8000001a. I found this by commenting out the backlight_on() statements in button.c and button-clickwheel.c and strategically adding new backlight_on() statements.
To reproduce the problem with SVN: In the file browser, turn hold hold on and then off. Press the centre (select) button without touching the wheel. About half the time, the first few presses are ignored.
With this patch, I am unable to reproduce the problem.
BTW. When this problem happens, values read from 0x7000c140 seem like garbage with many 0x55, 0xAA, 0x00 and 0xFF bytes.
But iPod Photo does not work.
iPod Photo did not work though the my patch in
FS#10098was applyed.For iPod Photo:
HOLD on
0x7000c100: 600a1f00
0x7000c104: 41000000
0x7000c140: 00000000
HOLD off
0x7000c100: 600a1f00
0x7000c104: 61001e00
0x7000c140: 55555555, aaaaaaaa, ffffffff (etc)
I don't like putting udelay(2000) in an interrupt handler. Any comments on that?
But for iPod 5G, the following problem found.
The HOLD switch is turned on, and the screen fades out.
After it waits for a while, the HOLD switch is turned off.
Then, the HOLD icon is sometimes displayed on the screen.
For original Rockbox firmware (r20674), r20674 + ipod_4g_button_int-variant2.patch such the problem did not occur.
FS#9890(5G iPod LCD sleep): if lcd_update() is called while the LCD is being initialized, that update will be ignored. The fix is in bcm_lcd_wakeup_improved.patch there. Alternatively, you can disable LCD sleep via LCD options and see if the problem still occurs.r20684+ipod_4g_button_int-variant2_v2.patch+ bcm_lcd_wakeup_improved.patch, the display is normal.
Both iPod Photo and iPod5G works fine.
thanks!!
P.S.
bcm_lcd_wakeup_improved.patch cannot be applyed to the source of the latest version. You should update it according to the source of the latest version.
FS#9890has corrected it.Is this awaiting more testing? What players does it still need to be tested on? It definitely fixes my 5.5G :)
I'm also wondering if it is okay to have udelay(2000) in an interrupt handler. I am hoping it is okay because it doesn't run often. It is only in the code path which is executed when this problem occurs, not in the normal code path which successfully reports key and wheel events.
I don't have my 3G ipod with me right now, but I do recall a similar issue with that one as well. I couldn't rewind a track in the WPS after releasing hold unless I waited a couple of seconds before holding the rewind button. If I was too speedy and pressed the button right away, and then continued to hold down the button, then released for only a short period of time, a second or third, or fourth attempt like this would fail. I also remember occasionally not being able to scroll until tapping the center button first, but that may not have been associated with the hold switch.
It's odd that only one person would report having the problem...
I'm not the only one who found a variant of "ipod_4g_button_int-variant2-v2.patch" useful. mg0rb did as well. His post is here in the forums: http://forums.rockbox.org/index.php?topic=23997.0
We know that that patch helped the button problem, what I meant is that you are the only person having that problem on ipodvideo; several people have reported it's not fixed on mini and it's expected that the other patch will work there, but you are the only person with any *other* model having an issue. The video is the most common ipod for rockbox and a lot of the developers have one, so it's rare that only one person reports a problem on it; some of the other models are rarely used and it's more likely there :)
100% times after HOLD button is used buttons (prev, next, play/pause, select) didn't respond for 2-6 clicks and after it works just fine.
If after unlock scrolling is used then all buttons respond normally. I can reproduce it any menu, directory list or WPS.
"I believe I observe a variant of this bug with Rockbox 3.7 on an ipod nano 2g. Keys stay locked unless I press select first."
This definitely didn't work for me.
I'm using Ubuntu and fail to install proper software to compile source code with ipodfix.diff.
.sh script getting stocked while installing GCC. Anyway if this possible i would like to ask some advanced rockbox user to send me proper version RB with this patch (no? ok :). Or wait couple weeks and i'll try to get it work at my PC.
P.S. Anyway i feel such a relieve not using iTunes. Thank you for all that work!
P.S. I installed GCC in January (take a look at my last post. Thx again Torne!) but it looks like .diff files that placed at this topic can't be automagically applied to source..
Also compiled source code from revision 21912 with Jonathan's Gordon "ipodfix.diff" (thank you Jonathan!) but for me nothing actually changed.
Maxime, the ipodfix.diff is already incorporated in the code.