OpenPandora Main OS

Quick Actions
Notice: Undefined index: tasklist_type in /srv/www/vhosts/openpandora.org/domains/bugs.openpandora.org/httpdocs/includes/class.tpl.php(136) : eval()'d code on line 228 Notice: Undefined index: tasklist_type in /srv/www/vhosts/openpandora.org/domains/bugs.openpandora.org/httpdocs/includes/class.tpl.php(136) : eval()'d code on line 233
  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Core
  • Operating System Release 1 (Zaxxon)
  • Severity Medium
  • Reported Version Hotfix 5
Attached to Project: OpenPandora Main OS
Opened by Stefan Nowak - 2011-09-01

FS#260 - Low Power Mode: Input (keyboard, nub) still taken. Application execution still running?

Tags:

This is the related documentation: http://pandorawiki.org/Power_modes#Low_Power (Please update accordingly as part of the issue resolution) FROM MY USER EXPERIENCE: If you put the Pandora into Low Power Mode, then press some keys, and then wake the Pandora back into Normal Mode, your input (both keys and nubs, haven't tried with USB input yet) seem to have triggered something while the device was in Low Power Mode! What does really happen in Low Power Mode concerning execution and input? a) Input is received AND triggers as application execution continues or b) Kernel/driver queues the input signals into a buffer, and executes them on wake? If supposition a) or b) is true, then this would be one more reason to properly implement:  FS#259  OBSERVANCE EXAMPLE 1: 1) Start MiniMenu. Mentally note down your active tab. 2) Put Pandora to Low Power Mode. 3) Press shoulder button R once. 4) Wake Pandora to Normal Mode. You are now one tab to the right of where you left. Input must have been caught in Low Power Mode, but wether execution of it happened while Low Power Mode or later after wake in Normal power Mode is unclear. OBSERVANCE EXAMPLE 2: 1) Start gedit (a text editor). Insert the digit "1". 2) Put Pandora to Low Power Mode. 3) Press: CTRL-N 2 CTRL-N 3 CTRL-N 4. (Without the spaces) 4) Wake Pandora to Normal Mode. 5) For a fraction of a second you see the tabs building up. Either the input was really received AND executed while Low Power Mode and what you see is just a delayed window manager refreshment, or the input was queued in Low Power Mode, and only executed on wake.
Stefan Nowak

Friday, 21 October 2011, 21:29 GMT
Meanwhile I realized it is even worse: In low power mode ALL MAYOR code execution continues! This has the following dissatisfying consequences for gamers: You play, are at a very good state (level, highscore, etc). Suddenly you have to interrupt (i.e. exit your bus). In your wrong belief, you use the Low Power Mode as a universal "Pause" method for any arbitrary app. Then you wake the Pandora. The game has continued, and meanwhile you lost substantially/completely! Your game state/record is gone! :-(

Loading...


Notice: Undefined variable: effort in /srv/www/vhosts/openpandora.org/domains/bugs.openpandora.org/httpdocs/includes/class.tpl.php(136) : eval()'d code on line 18 Notice: Trying to get property of non-object in /srv/www/vhosts/openpandora.org/domains/bugs.openpandora.org/httpdocs/includes/class.tpl.php(136) : eval()'d code on line 18 Warning: Invalid argument supplied for foreach() in /srv/www/vhosts/openpandora.org/domains/bugs.openpandora.org/httpdocs/includes/class.tpl.php(136) : eval()'d code on line 18
Date User Effort (H:M)