OpenPandora Main OS

When an internet connection was established through a mobile phone (Android, tethering) via bluetooth, the internet connection will not be re-established when the Pandora was sent to sleep and woken up again. The Pandora seems to be connected to the mobile phone, but no internet connection can be established, not even when manually trying to connect. The only way out is to disable bluetooth and enable it again.

I had similar problems with WiFi, before notaz tweaked the system (http://boards.openpandora.org/index.php/topic/11416-wifi-mysteries-resolved-once-and-for-all-—-power-saving-is-clearly-the-culprit/?p=249036).

The sticky keys option is disabling itself for the shift key. It continues to work with the left shoulder button though.

Unfortunately I have no idea what triggers the  sticky option to be disabled. Sometimes it happens after 1-2 minutes, sometimes it takes longer.

I would also like to point out that using the shoulder button instead of the shift button it _not_ an option! This issue has been reported in the forums, but apperantly was never fixed.

The Wiki states that the Pandora can be used without setting a user password on first boot. But when the password and password confirmation field are left empty, an error pops up saying that there is a password missmatch.

(Please don't fix this bug by just changing the statement in the Wiki ;-)

The XFCE menu does not always show submenues like "Emulators" when being clicked on with the stylus. It only works if the click lasts long or after all menues have been clicked at once with a long click.

Also, tipping on a scroll arrof of menues that are higher than the screen causes the click to be registered as a "click and hold". This leads to the menu being scrolled all the way to the end.

Right now. the XFCE menu handles right clicks like left clicks. It would be more logical to either not do anything on a right click, or open a context menu that e.g. lets the user generate a link to an application on the desktop.

It looks like XFCE cannot find the icons for links/launchers on the desktop, when the user logs on too quickly. This happens either when the session chooser at start-up is disabled, or when the session is being chosen quickly after the session chooser is being displayed (e.g. by pressing enter as soon as the chooser window pops up). The icons are probably not generated yet at that time point.

A simple workaround is adding the command "xfdesktop --reload" to autostart. Couls this be included in the next SuperZaxxon release or a hotfix?

Issue: The screen accidentally turns on even when the lid is closed.

How to reproduce: "Screen blanking" must be enabled! Close the lid, wait more than 10 minutes, tap either shoulder button.  This behaviour happens whether on charge or battery, at the desktop or running an application, provided that the "screen blanking" option is enabled.

Desired outcome: When the Pandora comes out of "screen blanking", it should restore the brightness to the same value that it was before blanking.

Suspend to RAM uses less power than the low power mode, but the NetworkManager crashes often after the Pandora woke up from suspend to RAM.

This could be fixed with an update of NetworkManager.

When put into Hold mode, X11 handles the power switch as if it's being pressed, and it generates lots of keypress events, passing them to the foreground application. Since /dev/input/eventX does not seem to continuously trigger, I'm guessing it's due to key repeat.

To reproduce:

• Install xev and open it in the terminal
• Put the power key in HOLD mode
• Notice the "time" value changing rapidly

In addition to causing more work to X, it also floods the active application with key presses, resulting in increased CPU usage. In my test, switching to HOLD while Firefox is in the foreground causes it to use 6% CPU and X an additional 2.5%.

In addition, the key-press events continue even after the switch is taken off HOLD until another key is pressed.

A possible solution to this is to blacklist the power-button event device, to prevent evdev from listening to it (the key is handled by pndevmapperd).

The touch screen requires to be used with the stylus or another sharp object. Even if I need to click a desktop icon, and could as well use my finger, the touch screen won't react to my finger at all (even if pressed quite hard).