FS#6707 - H300 freezes on buttonpress when playing with backlight off

Attached to Project: Rockbox
Opened by Peter D'Hoye (petur) - Wednesday, 28 February 2007, 10:07 GMT
Task Type Bugs
Category Operating System/Drivers
Status Closed
Assigned To No-one
Operating System Iriver H300 series
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


When the H300 is playing and backlight is off, pressing a button freezes the player solid - backlight doesn't come on and a hard reset is all that helps.
Note: doesn't happen all the time, I seem to have it only when it is playing for some time as I can't reproduce it just like that.

Possibly related: on other occasions, pressing a button only makes the backlight come on, the key itself is not processed. I have the 'First keypress' option off. This also doesn't happen always.
This task depends upon

Closed by  Peter D'Hoye (petur)
Saturday, 19 May 2007, 16:54 GMT
Reason for closing:  Out of Date
Additional comments about closing:  no longer happens for me and other reporter doesn\'t respond
Comment by Steve Bavin (pondlife) - Friday, 02 March 2007, 16:32 GMT
I've not seen this, although sometimes it can take a long time for the player to react to the button press (e.g. 5 seconds). (The main problem I have is that I press SELECT once, and then get impatient and press it a second time - the net result is that the current track is selected and restarted...)

Does this maybe only happen if you've been recording?
Comment by Jonathan Gordon (jdgordon) - Sunday, 04 March 2007, 08:50 GMT
I dont think its ever crashed on mine. but I do hate waiting for the backlight to turn on again.. is there anything we can do to speed that up?
Comment by Peter D'Hoye (petur) - Friday, 09 March 2007, 08:42 GMT
I haven't seen this issue again since the day I posted this bugreport, I had it several times before that. Go figure.
Either some change fixed this or this bug comes from a race condition somewhere. Let's hope it is case 1....
Comment by Chris Olin (Landus) - Thursday, 05 April 2007, 04:26 GMT
I had this happen today. Wasn't the first time that cause it either. As stated, it's completely random and I've got no steps to reproducing this, except waiting.
Comment by Peter D'Hoye (petur) - Thursday, 12 April 2007, 21:33 GMT
Weird, I haven't seen this since my initial report.
Landus, are you using a recent build?