|
151 | Base OS | Feature Request | Medium | [PATCH] Turn Off LCD when closing the lid | Closed | |
Task Description
Just added a few lines to op_lid.sh, will power off the LCD when you close the LID. Patch attached. |
|
152 | Core | Bug Report | High | Data transfer issued between SD slot 1 and 2 | Closed | |
Task Description
It appears that any users are having trouble transferring files from SD cards in slot 1 to SD cards in Slot 2.
Full details here.
http://www.gp32x.com/board/index.php?/topic/55077-looks-like-the-is-a-readtiming-problem-with-sd-reading-when-high-cpu/ |
|
153 | Application | Feature Request | Low | [PATCH] HACK: change OPP level according to set Mhz | Closed | |
Task Description
It's a hack, use on your own risk as always. I feel like abusing the tracker dropping all my patches here, but whatever. Patch attached. |
|
154 | Core | Bug Report | High | Vpn doesn't work | Closed | |
Task Description
When clicking on the Network Manager Applet Symbol, then selecting "VPN Connections" and then "Configure VPN", all the buttons in the following dialoge are greyed out. There is no way to add a new vpn connection. Restarting the system or deactivating the WiFi and then reactivaing it doesn't help. |
|
155 | Core | Bug Report | Medium | Critical problems after rescaling GLES2 X windows | Unconfirmed | |
Task Description
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. |
|
156 | Base OS | Feature Request | Very Low | Ask to format SD Card | Unconfirmed | |
Task Description
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. |
|
157 | Core | Bug Report | Low | Thunar and stilus | Closed | |
Task Description
With Thunar 1.1 and OS Zaxon (hotfix 3) :
- with detail view
- I open Thunar
- I click with the stilus to select the SD card
- I double click with the stilus to open a folder
=> click with the stilus doesn't select file/folder anymore
(I know it is a known bug, but it is not in the list) |
|
158 | Base OS | Bug Report | Medium | Refresh rate and BPP | Unconfirmed | |
Task Description
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). |
|
159 | Base OS | Bug Report | Medium | System > Run PND Application menu item does nothing | Unconfirmed | |
Task Description
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. |
|
160 | Base OS | Bug Report | Low | bug in date/time setting window | Closed | |
Task Description
first time i changed the date/time with no problems afterward every time when i try to change it it gives me "Please select month ..." this happens after selecting the time zone window. |
|
161 | Base OS | Feature Request | Low | Add ftp to base OS | Closed | |
Task Description
Include the netkit-ftp package so the Pandora has at least basic ftp functionality out of the box. |
|
162 | Core | Bug Report | Medium | XFCE Setting date | Closed | |
Task Description
The tool to setup the date/time in XFCE doesn't work properly :
- Menu -> Settings -> Date and Time
- The tool show up
- Select the time zone
Now an error window spam every seconds... |
|
163 | Base OS | Bug Report | Low | DPMS related "display problems" | Closed | |
Task Description
Currently it looks like DPMS is active in xorg (eg when using XFCE). DPMS is normally used for stuff like turning the screen off to save energy. There seems to be no way to configure this while in XFCE. So the default xorg server values are used.
At the moment the screen is turned off after 10mins of inactivity. Problems with this are
a) that the time till it is turned off can not be configured
b) after wakeup from such a DPMS related display shutdown the brightness is set to maximum.
Solution to this:
Deactivate the sleep values via xorg.conf. I am attaching a diff to "[openembedded.git] / recipes / xorg-xserver / xserver-xorg-conf / omap3-pandora / xorg.conf" changing those to "default off". |
|
164 | Core | Bug Report | Low | Display brightness not restored at booting, HF4beta3 | Closed | |
Task Description
The update from Hotfix3 to Hotfix4 beta3 broke restoring of display brightness at boot time. Restoring of brightness after "powersave mode" (aka flipping the power switch for a short time) does work nicely. This might be related to bug #163 ( http://bugs.openpandora.org/index.php?do=details&task_id=163 ) where shutting the display down via DPMS does result in the brightness being lost when getting the display on again.
This is related to the desktop mode (XFCE). Don't know if it does happen for minimenu, too, not tested yet. |
|
165 | Core | Bug Report | Low | VPNC does't work | Closed | |
Task Description
vpnc doesn't work |
|
167 | Application | Bug Report | Low | midori crashes all the time | Closed | |
Task Description
midori crashes all the time |
|
168 | Core | Bug Report | Low | qt-embedded doesn't work | Closed | |
Task Description
qt-embedded doesn't work |
|
169 | Core | Bug Report | Low | pidgin freezes all the time | Closed | |
Task Description
pidgin freezes all the time |
|
170 | Core | Bug Report | Medium | Executable directories broken | Closed | |
Task Description
Directory type packages fail to run. i.e. dropping a directory containing PXML.xml and a bunch of files onto the SD card rather than a .pnd package.
The application is detected and menu entries created correctly, however pnd_run.sh fails to bind mount the directory due to bogus double quoting. Looks like a failed attempt to handle spaces in the path. Patch below removes these incorrect quotes.
--- pnd_run.sh
+++ pnd_run.sh.old
@@ -161,2 +161,2 @@
elif [ $DFS = directory ]; then
- mntline="sudo mount --bind -o ro ${PND} "
+ mntline="sudo mount --bind -o ro \"${PND}\" " |
|
171 | Core | Feature Request | Medium | Update clock from hardware when restoring from low powe ... | Closed | |
Task Description
The clock occasionally does weird things during low power mode, sometimes gaining time, sometimes losing. This is most likely a result of the CPU being reduced to 14Mhz and the system clock being unable to keep up.
A convenient work around is to make a call to "/sbin/hwclock --hctosys" during wake-up to load the hardware clock back into the system clock. This may add an extra second or two to the wake-up time but will prevent confusion caused by clock being very incorrect. |
|
172 | Core | Bug Report | Low | Angstrom repo's bison is borked (FYI) | Closed | |
Task Description
This is how it tries to call m4 (strace -fF'd):
[pid 4231] execve("/OE/angstrom-dev/sysroots/x86_64-linux/usr/bin/m4", ["/OE/angstrom-dev/sysroots/x86_64"..., "/usr/share/bison/m4sugar/m4sugar"..., "-", "/usr/share/bison/yacc.c"], [/* 38 vars */]) = -1 ENOENT (No such file or directory)
Problem = obvious.
This is here because a) it is the bison that i get with opkg install bison and b) because i could find a general purpose bugtracker for stuff in the angstrom repo with a single googling.
Added info on bison version, etc:
pandora:/media/mmcblk0p3/dev/avrdude-5.6# opkg info bison
Package: bison
Version: 2.3-r5.0.5
Depends: libc6
Provides:
Status: install user installed
Section: devel
Architecture: armv7a
MD5Sum: c8e62fa82a96e9bba4c014c4345062ed
Size: 181368
Filename: bison_2.3-r5.0.5_armv7a.ipk
Description: GNU Project parser generator (yacc replacement).
Installed-Time: 1283127122 |
|
173 | Core | Bug Report | High | X uses 100% cpu in low power mode | Closed | |
Task Description
After 10 minutes in low power mode X seems to go nuts and use 100% CPU. Obviously this is bad ;-) 14MHz isn't *that* slow, so there's obviously something getting wedged.
I haven't been able to figure out exactly what's happening, but the fact that it always occurs after exactly 10 minutes suggests its power management related. Maybe we're getting stuck trying to kick off the screensaver, or something?
Hacking op_power.sh do disable screen blanking shows that, unsurprisingly, the screen freezes at the same time X goes AWOL.
Pressing the power switch brings the device out of low power mode, though there is often a few seconds additional delay as the event handling scripts take longer than normal to run because the CPU is already busy.
I've attached the results of
top -b -d 60 > toplog &
while sleep 60 ; do cat /proc/loadavg; done > loadlog |
|
174 | Base OS | Feature Request | Low | Include modem-manager in base image | Closed | |
Task Description
Please consider including the modemmanager package in the base distibution.
This allows 3G wireless dongles to work out of the box (configured via network-manager). |
|
175 | Core | To Do (Reminder) | Very Low | Test | Closed | |
Task Description
Test if the edit button in the bug tracker works now. //Edit: Blah |
|
176 | Core | Bug Report | Medium | op_power.sh: problematic display brightness restoring a ... | Closed | |
Task Description
Since hotfix4 it is possible to reduce the value for display brightness below '3'. Thus the script op_power.sh (the one used for low power mode) has to be adjusted accordingly. Currently line 25 in this script looks like this:
if [ $oldbright -ge 3 ] && [ $oldbright -le $maxbright ]; then
Please change the "-ge 3" part to "-ge 1" so that lower modes are possible, too. Otherwise the screen will be set to max brightness if you have selected a value of '1' when going into powersave mode.
Somehow it looks like what is possible to select via the hotkeys and what is possible via the "application" differs. In the script op_lcdsettings.sh in line 11 a minimum brightness of 3 seems to be defined, with the hotkeys it is even possible to go down to 0 (screen off) or values like 1 and 2. This is the relevant line:
minbright=3
Brightness restoring appears to be problematic in op_lid.sh, too. Just have a look at line 25 in this script:
if [ $oldbright -ge 3 ] && [ $oldbright -le $maxbright ]; then
Another issue is that the clockrate of 14MHz is simply too low to be reasonable. Please do adjust it to 125MHz instead, since this seems to be what TI recommends and what makes most sense since starting with hotfix4 this is where the lowest powermode (OPP0) is entered. When clocking down to 14MHz issues like the clock not working correctly come up.
Relevant lines in op_power.sh:
line 14, restoring old clockrate:
if [ $oldspeed -gt 14 ] && [ $oldspeed -le 900 ]; then
line 72, setting the clockrate for low power mode:
echo 14 > /proc/pandora/cpu_mhz_max |
|
177 | Core | Bug Report | Medium | no x or xfce after shutdown and reboot | Closed | |
Task Description
often but not always after shutting down the system (xfce logout, choose shutdown) there´s a problem when booting again.
i got the normal bootscreen but when x an xfce should start the screen remains black. i cannot say if the x or xfce didn´ start or if it is a problem with the backlight intensity.
rebooting with pandora key and power key leads to the same situation. the only thing that seems to help is to remove the battery shortly.
so, what is the difference beetween reboot after powerdown and reboot after replacing the battery? there could be the point to fix this problem. |
|
178 | Core | Bug Report | Low | Mount-loop when booting from SD-card | Unconfirmed | |
Task Description
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/. 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. |
|
179 | Core | Bug Report | Low | .vimrc-preset for user but not for root | Unconfirmed | |
Task Description
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. |
|
180 | Core | Bug Report | Medium | LCD Brightness Lower = Flashing, Dies. | Closed | |
Task Description
Just try and lower with the Fn+Br- until it starts to flashing and just dies if you go lower. It does go back if you raise it again. Feels wrong. Also no real feel in the brightness getting lower. |
|
181 | Application | Bug Report | Low | Triple click in Thunar crash | Closed | |
Task Description
Triple tapping (with the stylus) a directory in Thunar in icon or compact mode (not detail view) causes Thunar to close (crash)
This is consistently repeatable: tapping three times in rapid succession on the same spot of the file causes the crash. It must be the exact same spot, as if double clicking, but a third tap is added. This can be triggered especially when a user becomes frustrated at mistapping, gets carried away, and taps too much. |
|
182 | Core | Bug Report | Medium | Ctrl + F5 (Fn Lock) Fail | Closed | |
Task Description
So I've tried this a while now with no success. I'm assuming its when Fn is triggered and then pressing Ctrl or Alt it goes away. |
|
183 | Core | Bug Report | High | Left mouse click and hold = fail | Closed | |
Task Description
When I want to hold and select multiple files its not working. Not with the nubs or the touchscreen.
I can try an easy test by making the select rectangle on the desktop. It only becomes very very tiny. If I try very fast diagonal drag motion on the touchscreen. It becomes a little larger.
Trying to grab scrollbar is the same issue. |
|
184 | Core | Feature Request | Medium | libpnd: Add a function to get all mounted PNDs | Closed | |
Task Description
Add a function to get all mounted PNDs. Because it's very annoying to check all the menu/desktop folders on all of the SD-Cards. |
|
185 | Core | Bug Report | Low | Xorg driver should not be dependant on user environment | Unconfirmed | |
Task Description
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. |
|
186 | Application | Bug Report | Medium | unusable "Manage LCD Gamma" tool | Closed | |
Task Description
Pandora Menu -> Settings -> LCD-Settings -> Manage LCD Gamma
Removing all the profiles listed there will make the user unable to even create a new one. The tool becomes unusable. I hope a re-flash would fix the problem.
The last profile in the list, or the Default one, shouldn't be deletable at all. |
|
187 | Core | Bug Report | High | LCD turns off after "rdate" updated the date | Closed | |
Task Description
running "sudo rdate -s time.ien.it" will set the brightness of the LCD to 0.
User has to use FN + I to increase it back to a usable level.
"rdate" asks for the super-user password as expected, updates the date as expected, but turns off the screen. |
|
188 | Core | Bug Report | High | "rdate" sets the time exactly 3 hours in advance | Closed | |
Task Description
"rdate -s time.ien.it" will set the date (hour) 3 hours in advance.
The time (and timezone) can be adjusted manually using the "Settings -> Date and Time" tool, but on the next rdate-update the issue will occur again |
|
189 | Core | Bug Report | Medium | pnd-run.sh does not work correctly for very long <pathn ... | Closed | |
Task Description
When unmounting, the pnd-run-script greps the output of "losetup -a" at some point. But if you have a very long pathname and filename for the pnd (like "/media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_EN.pnd" then the endpart is cut off in the output, grep can't find the right part and the script get's confused.
Example:
mounting works:
/usr/pandora/scripts/pnd_run.sh -p /media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_EN.pnd -b scummvm -m
unounting does not work:
/usr/pandora/scripts/pnd_run.sh -p /media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_EN.pnd -b scummvm -u
(see /tmp/pndrun*-logs for output)
The problem is that the outut of losetup looks like this in such a case:
"/dev/loop7: [b309]:157081 (/media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_*)"
And because the pnd-name is not fully shown, grepping the name does not work. After i renamed th pnd to a much shorter name (somi_amiga_en.pnd) it worked nicely. Still this should be fixed. |
|
190 | Core | Bug Report | Medium | Removing desktop-shortkeys does not work | Unconfirmed | |
Task Description
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. |
|
192 | Core | Bug Report | Medium | [U-Boot] ext2fs_devread() read error - block (boot from ... | Closed | |
Task Description
[U-Boot] ext2fs_devread() read error - block
Description:
Formatted two different Transcend 8GB SD cards as EXT2 using both GParted and also with Mkfs.ext2, extracted pandora-rootfs.tar.bz2 to the root of the SD and added 'autoboot.txt' as described here: http://openpandora.org/firmware/README.txt
This issue appears to be same as mentioned here, looks like a patch maybe required in drivers/mmc/omap3_mmc.c):
http://lists.denx.de/pipermail/u-boot/2010-June/072198.html
Output on boot :
mmc1 is available
reading autoboot.txt
** Unable to read "autoboot.txt" from mc1 0:1 **
Loading file "autoboot.txt" from mmc1 device 0:! (xxa1)
184 bytes read
** Executing plain script at 82000000
Loading file "/boot/uImage-2.6.27.46-omap1" from mmc device 0:1 (xxa1)
** ext2fs_devread() read error - block
** Unable to read "/boot/uImage-2.6.27.46-omap1" from mmc 0:1 **
## Booting kernel from Legacy Image at 8030000 ...
Image Name: Angstrom/2.6.27-pandora+r21+git4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2325740 Bytes = 2.2 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
syntax error |
|
193 | Core | Bug Report | Low | Cannot reach button well in ubuntu x64 | Closed | |
Task Description
Window can also not be resized |
|
194 | Core | Bug Report | Low | python ctypes broken (and fix) | Closed | |
Task Description
run python and type import ctypes
cant find _ctypes it says....
for further details and a fix see
http://www.gp32x.com/board/index.php?/topic/57102-python-ctypes-stopped-working/ |
|
195 | Core | Feature Request | High | Start re-recharge of battery sooner | Closed | |
Task Description
Increase battery LVL_4 and LVL_3 threshold.
After reaching 100%, in some cases the charge circuit enters "battery full" state, stops charging, and begins to discharge. This is not entirely unexpected behavior according to the spec sheet, although I don't fully understand exactly the situations in which it completes charging. Once the battery is full, the battery will begin discharging. The charge circuit automatically restarts the recharge once the voltage has gone below a certain level (crosses below the LVL_3 voltage threshold)
The default LVL_3 voltage threshold is 3.902 volts which is at about 80-85% battery level as recorded by bq27500 chip. In my opinion, this is way too low.
Setting the BCIMFTH2 register to 0xCB increases the voltage threshold to about 4.003 volts which is about 93%.
Setting it to 0xDC may also be worthwhile, which is just over 95%.
By default, if a user leaves their Pandora plugged in overnight, they may wake up to find their Pandora has stopped charging and the capacity has dropped to almost 80%, which can be quite startling to some users who will then report it as a bug.
This change will ensure that it never drops below 93-95%, a much more acceptable level.
Specific code changes suggested, in the /drivers/power/twl4030_bci_battery.c file, somewhere in the twl4030_bci_battery_probe function (or a function called by it), add the lines:
/********************************/
#define KEY_FTH2 0x7F
#define REG_BCIMFTH2 0x017
ret = twl4030_i2c_write_u8(TWL4030_MODULE_MAIN_CHARGE, KEY_FTH2, REG_BCIMFKEY);
if (ret)
return ret;
ret = twl4030_i2c_write_u8(TWL4030_MODULE_MAIN_CHARGE, 0xDC, REG_BCIMFTH2);
if (ret)
return ret;
/********************************/
(Move defines to the top, as appropriate) |
|
196 | Core | Feature Request | Medium | [PATCH] Add tablet support into kernel | Closed | |
Task Description
Hi,
This should be a quite simple thing, but my first time touching
the OE repo and i cant test it, so be careful. |
|
197 | Core | Bug Report | High | [PATCH] Fix opp if booting with wrong settings in hw | Closed | |
Task Description
Hi,
This should help with cases like this
http://www.gp32x.com/board/index.php?/topic/57303-overclocking-broke-my-pandora/
Patch attached. |
|
198 | Application | Bug Report | Low | Mousepad: 'Find' works only once | Closed | |
Task Description
Mousepad 0.2.16
Find (Ctrl+F) works once, the next time it is used the button 'Find' is and stays grayed out. |
|
200 | Core | Bug Report | Low | After opening the lid, the backlight is not reset to th ... | Closed | |
Task Description
Using the hotkeys to set the backlite, after closing and then opening the lid, the backlight is not reset to the same level it was before closing it.
It seems to set it to a fixed value. |
|
201 | Core | Bug Report | High | PND apps still use memory after they've quit | Closed | |
Task Description
After running and quitting a PND app, not all of the used memory is being freed.
This eats more and more memory over time. Just run 5 or 6 apps and you only have half of the memory left.
Sounds like either aufs or unionfs don't free the memory after unmounting.
This has been reported with HF4 and still is the case with HF5 Beta 2
-- downgraded to 'Researching' and 'Normal' priority until confirmed and details found |
|
202 | Core | Bug Report | Low | Set Date and Time won't let you cancel or close | Closed | |
Task Description
The Date and Time application in MiniMenu by won't let you use the cross or the cancel button to close the application without changing anything.
If you use one of those buttons then a new window opens that says: "Error: Please select a timezone" and equally so for the date and time. |
|
203 | Core | Bug Report | Low | Video-out setting window does not exit on OK | Closed | |
Task Description
The "video-out" window opens again if you choose OK button. |
