- Status Closed
- Percent Complete
- Task Type Bugs
- Category User Interface
- Assigned To No-one
- Operating System Android
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#12670 - In Rockbox for Android the hardware back button exits Rockbox (instead of only going back)
I use Rockbox for Android since some time now on my Samsung Galaxy S running Android 2.3.6.
The behavior of the hardware back key has been changed in some of the last versions. Usually, when pressing the hardware back key rockbox goes up e.g. one menu level or it leaves the wps screen to the browse menu. Now when pressing the hardware back key rockbox exits the application so you can’t use this key any longer to go back through the browse menus.
I use at the moment version a12b2a5 which has the old (and correct?) behavior. Version c9c1349 has e.g. the new (wrong?) behavior.
Closed by kugel.
2012-05-13 19:06
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
2012-05-13 19:06
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
5f7d5b8
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I can confirm this. Need to see which commit introduced this regression.