All Projects

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

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? :)

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

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.

.desktop files only include the English stuff right now (using the .desktop default tags.)

Be nice if in addition to 'title', we also include 'title[de]' type extras, whatever is in the PXML.xml

pnd_pxml_t includes all the goods, but pnd_disco_t has only the summarized english stuff.

When booting the pandora-OS from sd-card by using the official tar, you will end up with your sd-card being mounted twice: once as / and once as /media/<label>. I solved this by adding "/dev/mmcblk0" to "/etc/udev/mount.blacklist". Maybe this should be added to the default tarball? I'm not sure as it might be used in other ways maybe (beside SD-card-installation)?

Background: I ran "updatedb" as root and have been notified by a message that there was a mount-loop. After adding the above modification the system still booted fine and "updatedb" ran nicely without a warning.

I am running PandoraOS from sd-card installed with the official tarball "pandora-rootfs.tar.bz2".

I noticed that the control/keyboard-mapping in vi does not work correctly after switching to root (for example sudo su-). I solved this by copying over my users .vimrc to root-homedir. This should already be included in the tarball.

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.

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.

Ok, I just want to say that there is something missing about the font on the base image. I cant get what (at least for now)

Here is an issue : http://www.gp32x.com/board/index.php?/topic/54282-getting-vnc-viewer-to-work/

With my current Ogre build I get :
Warning: Unable to load any usable ISO8859 font
Error: Aborting: no font found

I've googled but so far no solution :(

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

opengles and op_power.sh don't like each other very much.
whenever returning from low power to full power mode again, opengles rendering is just dead.

the reason for this issue are following 2 lines within op_power.sh

18 echo 0 > /sys/devices/platform/omapfb/graphics/fb0/blank
...
66 echo 1 > /sys/devices/platform/omapfb/graphics/fb0/blank

if these lines are removed/commented, the gles rendering just resumes fine.

using evdev xorg drivers and not the tslib drivers you can receive pressure axis data however there is
a problem with the values reported by the ads7846 module and the evdev driver has no calibration property for pressure

using
xinput test touchscreen
you can see the pressure axis ranging from 120-ish for hard press to about 150-170 for light press (low pressure values can
be quite erratic)

I could possibly hack the evdev module to possibly do something with this odd and narrow range of values, but I rather think looking
at the source that the ads7846 module needs some work.

is there a git tag that has a known working configuration? as I've had problems getting the kernel to compile the last few times I attempted...

If you hit the function button, then hit it again to lock the function keys, it doesn't lock the function key.

The delete key, hold shift and hit the back space button, it won't delete, meaning it won't remove the character to the right of the cursor. I saw this on the forum, and confirmed it on my pandora also.

SD-Card in Pandora can only be unmounted by guest (uid=1000) but not by jgeiss (uid=1001).

Steps To Reproduce:

Insert SD-Card (or boot with SD-Card inserted),
Login as jgeiss (uid=1001),
Try to unmount SD-Card via XFCE-Popup-Menu (right mouse click on SD-Card-Icon and select unmount).

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

If the power cable is plugged and the user chooses "Shutdown Pandora" from a menu, there should be a warning that this is without purpose, as the device will automatically restart.

The resulting user choices should be "Cancel shutdown" and "Shutdown nevertheless".

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.

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.

Built-in keyboard input is a central thing on the Pandora, as it concerns almost all user interfaced apps!
I realized that I myself and also others submitted quite many reports concerning this issue.
Hence this meta issue is intended as an overview/accumulation/aid for those devs who are willing to overwork the whole issue.
If you realize new related issues, feel free to add them here.
If this my effort is contradicting the OpenPandora workflow, then pardon me, and instruct me, how else to handle issues of that kind. Thanks!

Keyboard low level: Driver, keyboard layout, post processing (hotkeys, input support, etc)
FS#138 FS#227 FS#242  FS#259 

Keyboard mid level: Application interfacing
 FS#102  FS#123 FS#238

Keyboard application internal level
 FS#157  (dupe:  FS#249 ) FS#243 FS#256

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

STATUS QUO:

If you are in XFCE and hold the power slider for 3 seconds, you thereby trigger the shutdown command.
For 3 more seconds a dialogue box gives you the chance to abort the shutdown ("Shutting down in 3…2…").

Now in MiniMenu no direct shutdown key is available. You first have to quit the running app (via PANDORA key), then call up the menu (via SELECT key), and then navigate to "Shutdown" and confirm it (by B or ENTER).

INQUIRED BEHAVIOR:

1) Thanks to the very recent MiniMenu speedups, these 4 consecutive user interaction steps can now at least be be executed a lot faster.
Nevertheless, offering a 1-button-interaction (via power slider) too, would be nice. Could you please make that available to MiniMenu?
And in general: Make this power-slide-event available to any possible GUI, so that not each GUI has to implement this by itself, but rather the OS catches this event and handles it uniformly, except if a certain GUI WANTS to establish an exception to the rule.

2) Also the "Lid-Close-Settings" seem to be ignored by MiniMenu. MiniMenu seems to have the action "Turn off screen" hardcoded to that event. Please make MiniMenu observe the user settings from "Lid-Close-Settings".

RELATED SOURCE CODE FILES (to my knowledge):

op_lid.sh
op_power.sh
op_bright_up.sh
op_bright_down.sh

In GTK applications, such as Truecrypt, NoteCase Pro or Mousepad, the file open / file save dialogs have shortcuts to mounted file systems on the left side.
If clicking such a shortcut entry, the corresponding file system's contents are shown in the right dialog pane.
This works for file systems, which were available at boot time.
For file systems mounted after booting, e.g. by inserting an SD card or connecting a USB drive, when clicking such an entry, an error message appears saying
"Could not mount [volumen name]
Failed to execute child process 'gnome-mount' (No such file or directory)"

This is healed by
sudo opkg install gnome-mount
(which instals gnome-mount, nautilus, gvfsd-ftp, gvfs (upgrade), and a lot of libs (upgrades)..

This has been seen in SuperZaxxon release 1.5, not in Beta3 (but Beta3 is the only choice in Flyspray's dropdown currently).

I reported that error for HF6 I think, and it seemed to be fixed in SuperZaxxon Beta5. A regression?

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.