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

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.

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

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

The 'Nubs' application needs a setting for deadzone. Using the nubs in First person shooters the nubs trigger in directions when not even touched. An adjustment for deadzone would eliminate accidental movement caused by vibration.

Also, application profiles for the nubs would be very useful. Different apps use the nubs in different ways and it would be great to not have to go and change settings before launching each application.

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.

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

FAAD2 appears to not be compiled with fixed point decoding. My version of libfaad compiled with fixed point used 2-3x less cpu than the provided one. It's not enough to provide the switch to the configure script. the file libfaad/common.h has to be edited and a define uncommented. Line 68 in the v2.7 source.

/* COMPILE TIME DEFINITIONS */

/* use double precision */
/* #define USE_DOUBLE_PRECISION */
/* use fixed point reals */
//#define FIXED_POINT <<<<<------------

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

I added:
iface usb0 inet dhcp

And ran:
ifup usb0

But dhclient simply prints usage.

When the Pandora runs out of memory and the Out-Of-Memory killer fires, the Applications/Settings/xfce4/panel/panels.xml loses the entries for the menu button and the power monitor.

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.

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

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>

Zaxxon Hotfix 5.

Example (dropbear is running):

------------------------
~# nc -vvvv localhost 22
Notice: Real hostname for localhost [127.0.0.1] is localhost.localdomain
Total received bytes: 0
Total sent bytes: 0

~# telnet localhost 22
SSH-2.0-dropbear_0.51
------------------------

All required libraries seem present, strace output is inconclusive.

Problem - Login Screen does not accept all symbols of the form Fn+char
Reproducibility - always
Actual results - the characters :?#|$€"‘£¥@!_ do not work on the Login Screen with the Pandora's keyboard. When fn then the corresponding character is pressed, nothing is added to the string.
Expected results - these characters should appear just like any other character
Work Around - an external keyboard was able to enter these characters
Aditional Information - While the characters :?#|$€"‘£¥@!_ do not work, the characters ;/\'-+=`() work just fine.

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

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.

The command line environment of the default OS does not include the command "man" and the respective manpages of the installed programs.
I personally often use manpages, as I hardly remember the syntax/arguments of all programs I use.
Having them would be very convenient!

EVALUATING NEEDED STORAGE AMOUNT

Some may argue that storage space is quite limited on the NAND.

Yes I agree. Hence the number of included programs is limited too. Hence it would not be all too many manpages.

When I press TAB into an empty Terminal prompt, I get 1406 possibilities, which is about the amount of available commands/programs if we ignore aliases, etc.

Multiply that with an average of 20 kb per manpage, and you get about 30 MB in total. With compression this could possibly be brought down to 15-20 MB.

POSSIBLE SOLUTIONS

A) Store into the NAND the manpages of core OS CLI programs only, and not all the library/system/etc documentation.

B) Include only the man command into the core OS, and compile/configure it in such a fashion, that it finds the manpages within non-NAND media (SD card, USB volume, etc).
b1) Specify that it simply looks into a certain path within the /media/*/pandora/ structure.
b2) Or offer PND packages like man-core.pnd, man-extended.pnd,... you get the idea or even man-custom.pnd (which would look into its appdata or a certain path for custom added manpages, to somehow get the b1 approach within the PND approach).