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

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

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.

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

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.

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 :(

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.

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

FLAWED BEHAVIOUR:

Copy and paste only works between 2 active applications. This is very limiting!
If you are in the single task oriented MiniMenu you have no chance at all to share the clipboard between apps!
If you are in the multi tasking oriented XFCE desktop environment you can only share between apps running in parallel! Not with apps which started after the source app has been terminated.

DESIRED BEHAVIOUR:

The clipboard content (within reasonable limits of course) should remain, regardless of the source application, so that you can paste at any later moment into any application.

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.

EXAMPLE: MiniMenu with the option "Subcategories as folders" YES, and the current active tab i.e. "Game" lists:

Subgenre folders: ActionGame, AdventureGame, ArcadeGame, BlocksGame, …
App items: Abuse, Amoeboax, Arkaniod, Bloqus, …

THE BUG: Pressing "A" multiple times only cycles the focus between folders (ActionGame, AdventureGame, ArcadeGame), but never reaches the app items (Abuse, Amoeboax, Arkaniod).

BESIDES THIS BUG in the current keyboard item selection logic, I kindly inquire to implement: FS#243

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.

Steps to reproduce the bug(s):

1) In MiniMenu select an arbitrary app.
2) Press SPACE to bring up the contextual menu.
3) Select "Edit notes line 1".
4) Insert your string and confirm.
5) Now at a later time you may decide to remove your note line again. Therefore you select the same app again in MiniMenu, then repeat steps 2-3, but this time:

a) Erase all characters so that you get an empty string and then confirm. RESULT: Your change is simply ignored! There should be a possibility within MiniMenu to remove/reset note lines, the simplest being to simply accept an empty string as an input, that's what an average user will try if s/he does not find a dedicated "Delete note line" command.

b) As a workaround I tried something and detected yet another bug! As I could not create an empty string, I simply created a note line only containing 1 SPACE character (=the string " ") and confirmed. This got accepted.

If MiniMenu is in detailed view mode (press the A-button or TAB in order to bring it up, if it is not already there) and you slide over an app whose note line is " ", MiniMenu crashes!

Maybe the bug is connected with the writing to / the parsing from the .OVR (override) files which MiniMenu creates for the affected files, as the separating value in OVR files seems to be TAB, and SPACE is also WHITESPACE, therefore some parsers probably skip/misinterpret this, and MiniMenu then catches an unexpected situation!

WORKAROUND: If you ran into the problem, that you cannot get rid of the note lines anymore, simply start a file browser of your choice, navigate to the location of the affected .PND file and find its sister .OVR (override) file and delete it or edit it accordingly!

I assigned personal subcategories to some of my games.
Some of those subcategories share the same beginning string, i.e: Shooter, ShooterBallistic ShooterScoller.
MiniMenu displays those subcategories with flaws! See the ASCII screenshots below.
Note: The star symbols indicate the currently active selection.

The main category tab "Game" being active:

----------------------------------------------------------
| All | Audio | AudioVideo | Education |*Game*| Graphics |
----------------------------------------------------------
ActionGame AdventureGame ArcadeGame BlocksGame ...
Shooter ShooterBallistic ShooterScroller ...
GameA GameB GameC ...
----------------------------------------------------------

Now if I navigate into the sub-category "Shooter", everything normal:

----------------------------------------------------------
|*Shooter*|
----------------------------------------------------------
.. ShooterA ShooterB ShooterC ...
----------------------------------------------------------

But if I navigate to the sub-category "ShooterBallistic", strangely MiniMenu shows 2 tabs, "Shooter" and "ShooterBallistic", and jumps right into "Shooter".

----------------------------------------------------------
|*Shooter*| ShooterBallistic |
----------------------------------------------------------
.. ShooterA ShooterB ShooterC ...
----------------------------------------------------------

In order to reach my intended tab "ShooterBallistic" I need to navigate to it again. Annoying. There the contents are as expected:

----------------------------------------------------------
| Shooter |*ShooterBallistic*|
----------------------------------------------------------
.. ShooterBallisticA ShooterBallisticB ShooterBallisticC
----------------------------------------------------------

The flaw is the same for all other sub-categories beginning with "Shooter...". All have the flaw as shown in the example "ShooterBallistic", only that it is themselves instead of "ShooterBallistic". One more example to be perfectly clear:

----------------------------------------------------------
| Shooter |*ShooterScroller*|
----------------------------------------------------------
.. ShooterScrollerA ShooterScrollerB ShooterScrollerC
----------------------------------------------------------

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