All Projects

populating volatile requires execution of initialization script, which I had to minimally modify for it to start working. I am placing that file to /usr/pandora/init/ folder.

Any suggestions for better place for custom init scripts? :)

This script fixes utmp (and pndnotifyd) problem for systemd image

Noticed problems (TODO):
boot sequence recreates cache, run and tmp dirs before populate-volatile inits them. One of the solutions would be to deploy system with symlinks already in place (pointing to /var/volatile subdirs)

-------------
Deployment:

delete:
/etc/init.d/populate-volatile.sh
/etc/rcS.d/S37populate-volatile.sh
/var/{cache,lock,log,run,tmp}

add:
/etc/systemd/system/populate-volatile.service
/usr/pandora/init/populate-volatile.sh

symlink:
/etc/systemd/system/basic.target.wants/populate-volatile.service to /etc/systemd/system/populate-volatile.service

URLs for files:
http://dl.dropbox.com/u/18781412/next/populate-volatile.service
http://dl.dropbox.com/u/18781412/next/populate-volatile.sh

Since I don't have a Pandora, I used the videos that EvilDragon has shown to discover this issue. Nowhere did I see in the First Boot Wizard that it tells you what the default controls in XFCE does like for example how the mouse moves and clicking using the nubs. It also doesn't tell you what the gaming buttons do (L and R included).

Would be nice to know for first time users. It should also tell a user if they want to change these setting to look at a specific place after the wizard is done. We shouldn't have the users figure the controls and such out by trial and error. When is that ever fun? :)

Trashing a file/folder seems to MOVE it to a certain trash directory on the MAIN VOLUME, rather then the ORIGINATING VOLUME, hence this can result in a COPY RATHER THAN A MOVE operation, if the trashed file originates from a filesystem other than the main filesystem!

This is very inefficient and faulty as it is:
a) Very time consuming
b) And in case of large files this operation can even fail due to not enough free space on the main volume.

Please see this for GTK apps : http://library.gnome.org/devel/gdk/stable/gdk-Input-Devices.html
And see this thread : http://boards.openpandora.org/index.php?/topic/372-xournal-pdf-annotations/page__gopid__6836#entry6836

The patch implementing screen blanking uses the /usr/pandora/scripts/op_lid.sh script to control LCD backlit:
http://git.openpandora.org/cgi-bin/gitweb.cgi?p=openembedded.git;a=blob;f=recipes/xorg-driver/xf86-video-omapfb/pandora_backlight_dim.patch;h=4a0b8432d083c6e7297192a2920c7a777ae3d098;hb=16f3fff44323bd6b4349d909667b51a2fef3f278

The same result can be achieved by using the sys interface:
/sys/devices/platform/twl4030-pwm0-bl/backlight/twl4030-pwm0-bl/bl_power

This approach makes driver independent on particular distribution. The proposed patch is attached.

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.

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?

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.

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

Hi,

Upowerd spams each 10 seconds with warning "failed to open file '/proc/timer_stats'".

According to https://bugzilla.redhat.com/show_bug.cgi?id=826191 this feature can be activated in kernel. I'm not sure if upowerd can be told not to check this feature, I haven't been able to find an specific option for that so far. Activating this option in kernel, this warning should be eliminated.

It would help give upowerd data it needs, and also it will stop filling up the log, which then I guess interferes with power saving (active file access while writing into log...).

This seems to be the case with Hot-fix 5 and 6 alpha 4.

I've been able to repeat this bug by re-flashing..

On a fresh re-flash.. installed community codec pack.. Videos will play fine on Panplayer, VLC and Gnome-Mplayer with default settings, which I believe is XV or SDL out in the case of VLC.

Run the TV-out script it will cause a blank black screen during playback.. Disabling TV-out, switching modes, rebooting.. battery out, nothing seems to allows it to work with XV/SDL out again.. I know If I switch to X11 it will make it "work" again, but I notice a bit of lag during playback using X11 compared to XV/SDL out.

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

Should make up a simple zenity script tool ..

- backup -> pick SD -> backs up current user's homedor to SD. (tar.gz format so permissions can be kept; not cpio/etc, too annoying for user.) -> keep rolling, or just one copy?
- restore -> pick SD -> pick user -> confirm -> wipe home and restore with version from tarball? (or just unpack in-place, so existing new files are kept)
-> prepare SD -> pick SD -> mkdir /pandora/menu and /pandora/desktop

Thunar takes a long time going back to minimenu on exit. You don't notice this when in XFCE but then you are always in the GUI not returning to it.

This started in Hotfix 6 Alpha4 I believe

With both Hotfix 3 and Hotfix 4 Beta the Run PND Application menu item fails to do anything.

Possibly related problem is that PND files newly copied to SD card are not recognized and entered on desktop as expected.
When you go to Thunar and right click - execute the PND file, nothing happens.
Possible fix by copying the PND to another folder on the SD card with Thunar.
This makes at least two PND files I had work.

Still no response with "Run PND Application" menu, though.

If only 2 GUIs are available, skip the user selection and switch right into the only other GUI. What else would the user want?! Right!

If more than 2, already set the focus in the GUI list to the next possible item.

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.

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.

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

a) Host multiple volumes at once.
b) Select one for hosting first, later host additional ones. (I guess this scenario is more complicated)

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.

I call pnd_run.sh with a pnd. The application directory will invariably be /media/SD/pandora/appdata/<app-id>, no matter if the PXML.xml specifies a different appdata path. Also, the parameter -d for run_pnd.sh is not followed, either.

I tried with vlc.pnd from the app store and with Dosbox74.pnd.

UPDATE: Original submission contained a wrong filename reference. Corrected that typo to the filename intended by the submitter. Admin: porg.

If a PND has been run as root before (using pnd_run.sh from a root shell) and afterwards it is invoked the normal way, the PND doesn't start, because the .out file cannt be overwritten:

/usr/pandora/scripts/pnd_run.sh: line 26: /tmp/pndrun_firefox.out: Permission denied

Desired solution:
.out file is silently overwitten.
Maybe, if that's not possible, create another .out file with a different name (added counter, for example).

Seen in SuperZaxxon relese 1.5, not in Beta3 as this task is flagged, but there is no choice besides Beta3.

Try clearing shortcuts in Start->Settings->Window Manager->Keyboard. That doesn't work (for me).
This is a problem because these shortcuts are blocking key-combination in apps, like for example the keymapper in dosbox (CTRL+F1) or refreshing content (CTRL+F5). I tried manual editing or even deleting the configuration file, but changes are not recognized and the file recreated on reboot.

On OS Zaxon (hotfix 3).

With "xfconf-query", the resolution is 800x480@60 Hz.
But with the tool in the menu "Settings" -> "Display", the resolution is 800x480@0 Hz.

With Java (opensdk-6-jre 6b18-1.8),

GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getDisplayModes()

return 1 display mode that is 800x480@0 Hz with a BPP of -1.

It seems to be the reason that GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getDisplayMode() return null
and when closing a java application that goes in fullscreen mode to throw an exception (invalid display mode).