OpenPandora Main OS

SPAM

The script does not handle brightness "0".

If you try to decrease brightness if it's already at 0, it produces errors:

~ # /usr/pandora/scripts/op_bright_down.sh

/usr/pandora/scripts/op_bright_down.sh: line 18: [: : integer expression expected

/usr/pandora/scripts/op_bright_down.sh: line 22: echo: write error: Invalid argument

Not sure how to attach a patch here, but you can get the change with:

git pull git://git.assembla.com/openpandora-oe.git bug-333

I also changed the script to use /bin/sh since it's a valid posix script.

/usr/pandora/scripts/op_lidsettings.sh and /usr/pandora/scripts/op_power.sh fail for some usernames due to poor shell scripting

these scripts find their config files by grepping /etc/passwd for the uer currently running xfce4-session, but the loose regexp matches too much. this shell fragment from op_lidsettings.sh:

grep /etc/passwd -e $(ps u -C xfce4-session | tail -n1 | awk '{print $1}')| cut -f 6 -d ":"

when a use called "me" is logged in, returns

/home/root

/usr/games

/var/run/dbus

/home/me

rather than just "/home/me"

all instances of that construct (reading and writing settings, in both op_lidsettings.sh and op_power.sh) should be changed to

grep /etc/passwd -e ^$(ps u -C xfce4-session | tail -n1 | awk '{print $1}'): | cut -f 6 -d ":"

to correctly match only the complete username field in /etc/passwd

When selecting no OS in the OS Selector you're returned to the login screen where you have to reauthenicate. (Pressing Enter without selecting an OS does this)

I happen to do this a lot and it drives me mad :P

Since some PNDs provide nonstandard categories like GTK or GNOME, it is desirable to extend the libpnd category mapping with the ability to suppress individual categories completely.

Currently only the main category and the first sub category of the main category can be overridden using a .ovr file while libpnd uses additional PXML supplied category date to construct the desktop file. This makes it difficult to work with PNDs that supply unwanted data in these additional fields.

On my Pandora, due to bad internal WiFi, I use an Edimax EW-7811Un USB WiFi adapter, which has a status-LED, flickering according to the network activity.
After disabling USB-host through the settings menu, the WiFi functionality is gone, but the device's LED is still on. So some current must still flow into the USB device.
The LED now has a permanent light, no flickering! This lack of "device intelligence" indicates that the device was indeed turned off, just current flowing directly to the LED circuit unaltered).

I can repeat the aforementioned steps many times, the behavior is the same.
As soon as I then first physically unplug and reinsert the device, the LED remains off eventually.
From then on, every further issuing of "Disable USB-host" through the settings menu turns the device LED completely off.

Smells like a kernel bug to me! As it requires one real un/re-plugging, from then on works ok.

If you enable the "disapear automaticaly" feature in the XFCE panel, the Pandora button doesn't open the main menu anymore and you need to open it manually with the cursor.

The first time WiFi is enabled after boot, using either the the config button menu or the Toggle WiFi menu option the WiFi LED does not light up. (though the WiFi itself does work)

Once it has been enabled and disabled for the first time, it will work normally for subsequent uses of the WiFi toggle.

If the Toggle WiFi script is launched for the first time from the terminal the LED does light up.

This is the case in SuperZaxxon 1.53 with all current upgrades applied, and reportedly since the introduction of SuperZaxxon.

checking /sys/class/leds/pandora::wifi/trigger while the WiFi is enabled but the LED off shows that the trigger has been successfully set to phy0radio

Also noted while investigating this:

If Wifi is enabled for the first time from the terminal the following errors are generated by /etc/init.d/wl1251-init

Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
Usage: insmod filename [args]
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]

The commands that generate these errors are only executed if the mac80211 module is not already loaded - and that module is not unloaded when wifi is disabled. This seems to be unrelated to the issue being reported, however I can't see any cause for the issue at all, so I figured it was worth including it in the report anyway.

problem:
setting a username and password using first setup wizzard it's possible to set special character like @#*%/ ect...
the login manager don't support this characters, so you need to reset the device.

possible solution:
1. disable the possibility of setting special characters.
2. implement special characters in login manager.

Not my work, but since I think my reply to ED on the forums will get buried I made this report.
The post with patch: http://boards.openpandora.org/index.php/topic/11189-its-arrived-questions/?p=210363

When a partition is bigger than 2 or 4 GiB (can't recall now) it makes a "default" 1GiB filesystem. Propably missing large file support in the build. Also, the pandora sd card formatter is missing -F 32 so it makes (i think, it is some time from when I noticed this) FAT16 partitions...