This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#7202 - Power and A button functionality switched between each other
Attached to Project:
Rockbox
Opened by Oleg (giraffe) - Tuesday, 22 May 2007, 20:20 GMT+2
Last edited by Tom Ross (midgey34) - Monday, 30 July 2007, 22:26 GMT+2
Opened by Oleg (giraffe) - Tuesday, 22 May 2007, 20:20 GMT+2
Last edited by Tom Ross (midgey34) - Monday, 30 July 2007, 22:26 GMT+2
|
DetailsI have a Gigabeat F40 and just be sure just today I upgraded to Today's (May 22nd 07) build (this issue was still happening before the upgrade) and the latest boot loader. It seems that the functionality of the Power button and the A button is switched between the two buttons. In the manual for this Firmware it states that pressing Power while having music playing and while in WPS will stop playback and display the file list and that pressing the A button will keep the music playing and display the file list. In reality the Power button does not stop the playback and the A button does. Same behavior occurs when using Virtual Keyboard: according to the manual pressing Power exits the virtual keyboard without saving any changes and pressing the A button; what happens is reversed: pressing Power saves the change and pressing A cancels the change. Either the manual or the key mappings have to be changed.
Also want to thank everyone involved in this project, I absolutely love it :) |
This task depends upon
Closed by Tom Ross (midgey34)
Monday, 30 July 2007, 22:26 GMT+2
Reason for closing: Not a Bug
Additional comments about closing: The functionality of A and Power were switched and the manual was updated accordingly.
Monday, 30 July 2007, 22:26 GMT+2
Reason for closing: Not a Bug
Additional comments about closing: The functionality of A and Power were switched and the manual was updated accordingly.
The behaviour of the power and A buttons were switched on Apr 13 in the code and later in the manual, so what you read in the
manual is correct and the behaviour that you describe is not.
Please try to reinstall a new build, and test again.