All Projects

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.

Found I'd kept some notes about making the Pandora's wake on alarm function work...

drivers/rtc/rtc-twl4030.c

twl4030_rtc_remove (for when the driver is removed) and twl4030_rtc_
shutdown (for when the system is shutdown) functions need to change. Or at least the shut down does.

oh YUK who's been using goto....

changes in drivers/rtc/rtc-twl4030.c

twl4030_rtc_remove
commented out //mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_ALARM_M);

twl4030_rtc_shutdown
replaced
// mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M |
// BIT_RTC_INTERRUPTS_REG_IT_ALARM_M);
with
mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M);

twl4030_rtc_suspend
replaced
// mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M |
// BIT_RTC_INTERRUPTS_REG_IT_ALARM_M);
with
mask_rtc_irq_bit(BIT_RTC_INTERRUPTS_REG_IT_TIMER_M);

twl4030_rtc_init
added (before return!)
twl4030_rtc_alarm_irq_set_state(true);

Should probably check reg 0x2B with mask 0x08 to see if alarm should be left enabled or not ?
but only in twl4030_rtc_shutdown and ?remove? NOT in twl4030_rtc_init
should remove ever happen ???

I'm guessing it's best to not enable the alarm irq's all the time???

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

When a X window which is displaying GLES2 render output is:
- Either dragged out of the visibile screen region (?)
- Is made larger than it was at the creation time of the GLES2 context
then:
- The performance will drop significantly as the EGL buffer swaps won't occur as fast as before,
- The render output will be corrupted and flicker
- In rare occasions crashes the application or locks up the entire system (which forces you to remove the battery)

The problem can not be solved without restarting the application (Possibly forcing players to complete the same goals again as they were unable to reach a savepoint or similar things).

This was confirmed in Mupen64Plus and the PowerVR GLES Samples and some of my own projects (which are, however, based on the PowerVR samples).
As I didn't see any other reports about this problems (but had it confirmed by other Pandora users too) I would expect that it can be fixed by using a newer X, kernel or combination of them as other OMAP users would be effected too.

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

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

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.

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.

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 thee Pandora is shutting down because its almost out of power, it should check to make sure that the nub inputs are set to the default mode (which is mouse movement for the left nub and mouse buttons for the right nub). If not, it should change them to be like that.

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

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

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

Build the xml file and defaults.list so that pnd_run is file-assocated to .pnd

If you boot the system with the lid closed, the backlight will still be on when you get to the desktop. You have to lift the lid for an instant and then close again to shut it off. Perhaps this is because of the lack of trigger for an interrupt since the sensor is already activated. Can there be one extra check of the lid sensor after boot to cover this static position?

The title says everything: The 'del' key does not work. In theory you should have a del "event" when hitting shift+backspace. This is not the case in all progs I tested so far (terminal and default text editor with gui).

cat >/etc/ld.so.conf<<END
/lib
/usr/lib
END

ldconfig

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.