All Projects

When the taskbar is set to autohide, the Pandora button does not bring up the menu anymore.

With SuperZaxxon Final, I've noticed that stuff running on the Pandora like Thunar and bash are seeing a different interpretation of filenames on disk than when I remove the SD card and insert it into my desktop PC.

Specifically, the following two mismatches appear to be present when using a FAT32-formatted SD card:

First, the Pandora's VFAT support seems to be be operating with different case-handling settings than desktop Linux distros.

Filenames set in all uppercase are forced to all-lowercase on the Pandora (whether they're set on the desktop or the Pandora) but inserting the card into a PC reveals that the. All-lowercase filenames set by software on the Pandora risk appearing in all uppercase when the card is inserted into a PC. (I think the grsync PND is what created the files in question)

Among other things, this forces me to use EITHER the PND-based copy of grsync over the network OR a desktop-based copy of rsync with an SD card reader but not both because the kernel will preserve case differences like ALBION.BAT vs. albion.bat but rsync think they are separate files. (resulting in Flash-killing, time-wasting deletion and re-creation)

It also makes for irritating entries like "zzt" in DOSBox or "ddr" in PyDance where I can't capitalize the filename properly without employing Department of Redundancy Department with "DDR Songs" or "ZZT.The.Game" as an excuse for mixed case.

Second, SuperZaxxon Final seems to be using a different (though still Unicode-capable) filename encoding than all the desktop distros I've tried.

Filenames are preserved properly and all-ASCII filenames are displayed properly in all cases, but any non-ASCII characters appear as gibberish on whichever system was not used to set them.

I've confirmed this problem with these two filenames:
- 03 - The Foggy Dew with Sinéad O'Connor.flac
- Lucky Star - Native Misao (Touhou - Native Faith) ???????????????????×??????.mp4

As a Canadian user, my desktops use the "en_CA.utf8" locale and the only other distros I've found which have this problem are Slax and the 1.0 release of its successor, Porteus, both of which use ISO-8859-1 (latin1) for filenames.

As verified with xev, an attached bluetooth keyboard can not generate colon (shift semicolon). xmodmap shows that (unlike a standard Linux system) shift-semicolon is mapped to NoSymbol. While it's find that there's a special symbol to get semicolon on the built-in keyboard, the other binding really should be there in support of attached keyboards.

When a Wireless Network that is dropped because its signal strength isn't that good gets reconnected to, I am being asked to re-input the password for that network. It would be nice if it just used the password I gave to it when it was able to connect without popping up that dialog box.

Hi, sadly the XFCE bluetooth manager seems to have problems with pairing simple SPP devices (an BT GPS mouse here).

1. Enable BT
2. BT Manager -> Add new device
3. Confirm Dialog and wait for scanning
4. Pick device
5. Select PIN options -> "0000" (here for me)
In next step the dialog still asks you to enter a random PIN at your BT device (which is impossible here).

Thus it seems, that the XFCE dialog makes troubles, I tried it with 2 different GPS. Pairing the GPS manually works fine:
sudo rfcomm connect rfcomm0 00:18:E4:26:5F:14

I found a bug when I tried to debug my code with strace.

It happens when strace has to handle conditional SWI's.

Example: (ASM code) save as "condswi.s"
-----
.data
.text
_globl _start
_start:
mov r0,#0 @ return code
mov r7,#1 @ sys_exit
swine 0
swieq 0
.end
-----

The code assembles/links fine using 'as' and 'ld'.
> as condswi.s
> ld a.out -o condswi

When I want to strace the executable file I got the following error.
> strace ./condswi
'syscall: unknown syscall trap 0x1f000000'
As a result strace quits.

Thanks,
Dennis

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.

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).

Command is essencial when switching between kb layouts

I'm using https://github.com/openpandora/meta-openpandora-vendor/blob/master/recipes-openpandora/openpandora-system/openpandora-skel/pndXmodmap

strace (openbox process): https://gist.github.com/anonymous/9925061

xmodmap latest version (1:1.0.4-r0.5) reinstalled

Hi,

Evince 2.30 often crashes with the following error message:

(evince:2834): EvinceDocument-CRITICAL **: ev_image_save_tmp: assertion `GDK_IS_PIXBUF (pixbuf)' failed

Segmentation fault

How to reproduce: open Evince,  select a PDF file, go into fullscreen mode, then click into the body of the document.

Cheers, Magic Sam

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).

The appdata folder was corrupted on my SD card from an unclean eject this made the folder read only until i ran a repaired it. MiniMenu still displayed all my PND files.

When clicking to launch the app would try to load crash and then return to MiniMenu without any visible error. This was pretty confusing and i thought it might be a good fix for a troubleshooting guide.

Hi there,

Many games depend on sdl-perl. Perl and sdl are part of the base OS, but not not the connection between the two.

Cheers,
sebt3

When I have received my Pandora, I got an SD Card but it was not formated. I didn't have any card reader so I didn't now what was wrong (the Pandora or the SD Card).

When an unformated SD Card is inserted in the Pandora, it should be nice to ask if we want to format it.

That still need to be configurable, but chris_c does a good job I'ld like to see integraded in the main image :
http://www.gp32x.com/board/index.php?/topic/58794-a-script-to-shutdown-after-charging/
and :
http://chrisc.bedroomcoders.co.uk/?p=77

http://www.wader-project.org
http://trac.wader-project.org
http://trac.wader-project.org/wiki/Developers

this would be really usefull to monitor reception/network of mobile broadband dongle and it also counts ur mobile data usage (for those that have limits).

It'll have to be in the SKEL.
/etc/skel/Applications/Settings/Thunar/uca.xml

People can replace the contents of their current uca.xml file with the following to gain this functionality now.
/home/[USERNAME]/Applications/Settings/Thunar/uca.xml

<?xml encoding="UTF-8" version="1.0"?>
<actions>
<action>
<icon>Terminal</icon>
<name>Open Terminal Here</name>
<command>exo-open --working-directory %f --launch TerminalEmulator</command>
<description>Example for a custom action</description>
<patterns>*</patterns>
<directories/>
</action>
<action>
<icon>emblem-symbolic-link</icon>
<name>Mount PND</name>
<command>/usr/pandora/scripts/pnd_run.sh -p %f -m &amp;&amp; thunar /mnt/utmp/</command>
<description></description>
<patterns>*.pnd;*.PND</patterns>
<other-files/>
<text-files/>
</action>
<action>
<icon>gtk-jump-to-rtl</icon>
<name>Unmount PND</name>
<command>/usr/pandora/scripts/pnd_run.sh -p %f -u</command>
<description></description>
<patterns>*.pnd;*.PND</patterns>
<other-files/>
<text-files/>
</action>
</actions>

PROBLEM DESCRIPTION: In many GUI dialogues the default action button (OK, ACCEPT, YES, …) cannot be triggered with a simple key press. Pressing ENTER triggers the element which has focus (usually the first dialogue element), but not the default action, as most computer users would expect!

MY WORKAROUND MEANWHILE: Press ALT plus the underlined letter of your desired action. But that's not very convenient as the underlined letter needs to be looked upon first, as the button label can differ from situation to situation (ACCEPT, OK, YES, …) and then 2 keys need to be pressed.

SUGGESTED SOLUTION: The custom of many operating systems should be adapted on the OpenPandora as well. SPACE triggers the currently focused element (whatever that may be: list item, radio button, checkbox, etc), and ENTER triggers the default action of that dialogue.
Or even better use the Pandora specific A/B/Y/X keys cleverly in those dialogues/selections. I don't know whether there is a standard functionality assignment within this key-group, in MiniMenu "B" is start/confirm, I do not know of any other standard assignments yet.

I am suggesting the new option "Grid stop horizontal" for MiniMenu with the following possible settings and their effect.

Yes -> If the boundary is reached the focus remains there.
No -> If the boundary is reached the focus starts at the opposite side again.
Jump to next/prev line -> If the boundary is reached the focus jumps to the next/previous line and the opposite side.

If you set MiniMenu's option "Live (not exit) on app run?" to YES, and you quit an application and return to the still running MiniMenu, it runs in windowed mode, and takes about 2 seconds until it goes into full screen mode again.

This delay should at best be not noticeable at all, at most 0-1 seconds.