All Projects

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?

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.

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.

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.

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?

PyGame is damn slow (games with scrolling are not at all playable).
Would be nice if Hardware surface could be used :)

My suggestion instead of a full menu, would be to have a tiny overlay over the current running application which allows you to:
- relogin (to close all running applications)
- quit (stop the active application)
- shows the last notifications / toaster messages which you missed while being in a fullscreen app.
- possibly even something like plugin support or icons to check out the wifi-strength etc. from fullscreen apps.

Implementation wise this could possibly be done using
- a topmost window and the same content rendered in screenspace in a GLES hook (which should draw over most applications)
or
- one of the DSS2 overlays maybe

It's definitely something to consider as it was requested on the forums a few times (~"xbox like menu in games").

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

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

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

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

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

The appdata folder was corrupted on my SD card from an unclean eject this made the folder read only until i ran a repaired it. MiniMenu still displayed all my PND files.

When clicking to launch the app would try to load crash and then return to MiniMenu without any visible error. This was pretty confusing and i thought it might be a good fix for a troubleshooting guide.

Battery remaining percentage in MiniMenu does not update unless you change tabs back and forth.

This is only really an issue when leaving the unit charging and not using it. It gives the appearance that it is not charging until you swap tabs around.

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

ldconfig

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.

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

When the lid is closed the only remaining buttons on the Pandora are the L + R shoulder buttons and the power slider.
Applications operating in this mode should utilize that few available buttons!

Example for button utilization in a audio playback software:
L + R at once: Toggle Play/Pause
L hold: fast backward
R hold: fast forward
L click: jump to previous song
R click: jump to next song
L double click: jump to previous album/artist
R double click: jump to next album/artist

Since the default inputrc doesn't contain any functionality (simple cli movements like ctrl-left or crtrl-right to skip words don't work) this diff may be useful to add to the cli-experience. I've also been trying to get the delete-key to work, but this is apparently already a known issue (see FS#227). I can remove this from the diff if you want. (I couldn't attach a file to the task somehow)

31,32c31,33
< # "\e[3~": delete-char
< # "\e[2~": quoted-insert
---
> #"\e[3~": delete-char
> "\e[^?": delete-char
> "\e[2~": quoted-insert
44,47c45,50
< # "\e[5C": forward-word
< # "\e[5D": backward-word
< # "\e\e[C": forward-word
< # "\e\e[D": backward-word
---
> "\e[1;5C": forward-word
> "\e[1;5D": backward-word
> "\e[5C": forward-word
> "\e[5D": backward-word
> "\e\e[C": forward-word
> "\e\e[D": backward-word

I found a bug when I tried to debug my code with strace.

It happens when strace has to handle conditional SWI's.

Example: (ASM code) save as "condswi.s"
-----
.data
.text
_globl _start
_start:
mov r0,#0 @ return code
mov r7,#1 @ sys_exit
swine 0
swieq 0
.end
-----

The code assembles/links fine using 'as' and 'ld'.
> as condswi.s
> ld a.out -o condswi

When I want to strace the executable file I got the following error.
> strace ./condswi
'syscall: unknown syscall trap 0x1f000000'
As a result strace quits.

Thanks,
Dennis

The update mode functions have moved from the DSS layer to omapfb implementaion.
This patch exports the new function symbols for use by the TI drivers.

--- a/drivers/video/omap2/omapfb/omapfb-ioctl.c
+++ b/drivers/video/omap2/omapfb/omapfb-ioctl.c
@@ -22,6 +22,7 @@

#include <linux/fb.h>
#include <linux/device.h>
+#include <linux/module.h>
#include <linux/uaccess.h>
#include <linux/platform_device.h>
#include <linux/mm.h>
@@ -359,6 +360,7 @@ int omapfb_set_update_mode(struct fb_info *fbi,

return r;
}
+EXPORT_SYMBOL(omapfb_set_update_mode);

int omapfb_get_update_mode(struct fb_info *fbi,
enum omapfb_update_mode *mode)
@@ -381,6 +383,7 @@ int omapfb_get_update_mode(struct fb_info *fbi,

return 0;
}
+EXPORT_SYMBOL(omapfb_get_update_mode);

/* XXX this color key handling is a hack... */
static struct omapfb_color_key omapfb_color_keys[2];

The last release of TI Graphics SDK Product to support the 1.0.3 SGX core is 4.04.00.03
The overlay needs to peg the package selection to this version.