|
225 | Core | Bug Report | Medium | ads7846 reports odd pressure values | Unconfirmed | |
Task Description
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... |
|
224 | Core | Bug Report | Low | Unresponsive start menu since HF5 | Closed | |
Task Description
Since hotfix 5, the start menu often pauses for a few seconds, not letting me select anything or move the mouse.
Other people have reported the issue as well:
http://boards.openpandora.org/index.php?/topic/2295-is-the-xfce-menu-trolling-anyone-else/page__gopid__42559#entry42559 |
|
223 | Core | Bug Report | High | op_power.sh kills gles context | Unconfirmed | |
Task Description
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. |
|
222 | Application | Bug Report | Low | Login Screen does not accept all symbols of the form Fn... | Unconfirmed | |
Task Description
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. |
|
221 | Core | Bug Report | Medium | 32MB worth of qt4 examples in /usr/bin/qt4 ? | Closed | |
Task Description
Hi, after upgrading to HF5, I accidentally discovered that there are 32MB of qt4 examples & demos in directory /usr/bin/qt4, those examples do work. For instance the /usr/bin/qt4/examples/webkit/fancybrowser/fancybrowser is a working WWW browser.
It is, without any dispute a very useful qt4 development help, but are you sure that you want to include all that in NAND ? |
|
219 | Core | Bug Report | Medium | wrong owner of /home/user/Desktop | Closed | |
Task Description
I just reflashed with HF5, and it turns out that I cannot make shortcuts on the desktop. It is very simple to fix:
sudo chown janek.janek Desktop/
I remember that this bug was also present in HF4, I fixed it so quickly that I didn't even remember to report it. |
|
215 | Core | Bug Report | Medium | Kingston 32GB Class6G2 SDHC card not working in pandora | Closed | |
Task Description
I have noticed errors like this, but not every time
[ 1455.612792] mmc2: card claims to support voltages below the defined range. These will be ignored.
[ 1455.621795] mmc2: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
[ 1455.665985] mmc2: new SDIO card at address 0001
This is me plugging in my 32GB SD6G2 Kingston SDHC card.
at [ 1114.484252] is when the file copy started
Errors continue from there until it bombs and remounts the filesystem readonly.
I have tried this with ext3 vfat in various configurations and all fail the same I/O errors
Let me know if I can do anything to help
-------------------------------------
[ 989.496459] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 989.504638] mmc1: new high speed SDHC card at address 0003
[ 989.510620] mmcblk1: mmc1:0003 SD32G 31514112KiB
[ 989.515625] mmcblk1: p1 p2 p3 p4 < p5 p6 >
[ 989.940490] FAT: invalid media value (0x00)
[ 989.944702] VFS: Can't find a valid FAT filesystem on dev mmcblk1.
[ 990.083190] FAT: invalid media value (0x00)
[ 990.087402] VFS: Can't find a valid FAT filesystem on dev mmcblk1.
[ 991.907562] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 991.922943] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 992.002563] mmci-omap mmci-omap.0: MMC IRQ 0x208002 : TC ERRI DCRC
[ 992.003143] mmcblk0: retrying using single block read
[ 992.028411] kjournald starting. Commit interval 5 seconds
[ 992.048553] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 992.092346] kjournald starting. Commit interval 5 seconds
[ 992.237091] kjournald starting. Commit interval 5 seconds
[ 992.259185] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 992.361999] FAT: bogus number of reserved sectors
[ 992.366760] VFS: Can't find a valid FAT filesystem on dev mmcblk1p4.
[ 992.400909] kjournald starting. Commit interval 5 seconds
[ 992.612945] EXT3 FS on mmcblk1p2, internal journal
[ 992.617797] EXT3-fs: mounted filesystem with ordered data mode.
[ 992.787475] EXT3 FS on mmcblk1p3, internal journal
[ 992.792449] EXT3-fs: mounted filesystem with ordered data mode.
[ 993.038940] EXT3 FS on mmcblk1p1, internal journal
[ 993.043884] EXT3-fs: mounted filesystem with ordered data mode.
[ 993.205749] EXT3 FS on mmcblk1p5, internal journal
[ 993.210632] EXT3-fs: mounted filesystem with ordered data mode.
[ 993.510253] FAT: bogus number of reserved sectors
[ 993.515045] VFS: Can't find a valid FAT filesystem on dev mmcblk1p4.
[ 1114.484252] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1114.484802] mmcblk0: retrying using single block read
[ 1115.763946] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1115.765594] mmcblk0: retrying using single block read
[ 1115.984649] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1115.984985] mmcblk0: retrying using single block read
[ 1116.039489] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.039916] mmcblk0: retrying using single block read
[ 1116.094329] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.094757] mmcblk0: retrying using single block read
[ 1116.150146] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.152343] mmcblk0: retrying using single block read
[ 1116.212127] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.212615] mmcblk0: retrying using single block read
[ 1116.267791] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.268280] mmcblk0: retrying using single block read
[ 1116.335723] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.337738] mmcblk0: retrying using single block read
[ 1116.410766] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.413360] mmcblk0: retrying using single block read
[ 1116.488250] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.490234] mmcblk0: retrying using single block read
[ 1116.581390] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.581939] mmcblk0: retrying using single block read
[ 1116.645721] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.646331] mmcblk0: retrying using single block read
[ 1116.933288] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.933715] mmcblk0: retrying using single block read
[ 1117.000518] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.002899] mmcblk0: retrying using single block read
[ 1117.068328] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.070526] mmcblk0: retrying using single block read
[ 1117.128326] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.128753] mmcblk0: retrying using single block read
[ 1117.194183] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.194488] mmcblk0: retrying using single block read
[ 1117.261566] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.262084] mmcblk0: retrying using single block read
[ 1117.328674] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.329956] mmcblk0: retrying using single block read
[ 1117.388061] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.390380] mmcblk0: retrying using single block read
[ 1117.451629] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.452087] mmcblk0: retrying using single block read
[ 1117.510467] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.512725] mmcblk0: retrying using single block read
[ 1117.714874] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.715301] mmcblk0: retrying using single block read
[ 1117.776550] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.778930] mmcblk0: retrying using single block read
[ 1117.841247] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.841674] mmcblk0: retrying using single block read
[ 1122.718658] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1122.719055] mmcblk0: retrying using single block read
[ 1123.265136] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1123.265441] mmcblk0: retrying using single block read
[ 1123.442230] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1123.442413] mmcblk0: retrying using single block read
[ 1126.759338] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1126.759399] mmcblk1: error -110 transferring data, sector 32669824, nr 8, card status 0xc00
[ 1126.807830] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1126.807891] end_request: I/O error, dev mmcblk1, sector 32669824
[ 1126.813934] Buffer I/O error on device mmcblk1p1, logical block 4083726
[ 1126.820556] lost page write due to I/O error on mmcblk1p1
[ 1127.630950] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1127.631011] mmcblk1: error -110 transferring data, sector 32686232, nr 8, card status 0xc00
[ 1127.715179] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1127.715240] end_request: I/O error, dev mmcblk1, sector 32686232
[ 1127.721282] Buffer I/O error on device mmcblk1p1, logical block 4085777
[ 1127.727935] lost page write due to I/O error on mmcblk1p1
[ 1133.399963] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.400024] Spurious DMA IRQ
[ 1133.403411] mmcblk0: retrying using single block read
[ 1133.504821] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.504943] mmcblk0: retrying using single block read
[ 1133.599304] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.599548] mmcblk0: retrying using single block read
[ 1133.767486] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.767578] mmcblk0: retrying using single block read
[ 1134.222564] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1137.074981] mmcblk0: retrying using single block read
[ 1137.465576] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1137.465667] mmcblk1: error -110 transferring data, sector 17316672, nr 72, card status 0xc00
[ 1137.509582] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1137.509643] end_request: I/O error, dev mmcblk1, sector 17316672
[ 1137.515686] end_request: I/O error, dev mmcblk1, sector 17316680
[ 1137.521728] end_request: I/O error, dev mmcblk1, sector 17316688
[ 1137.527770] end_request: I/O error, dev mmcblk1, sector 17316696
[ 1137.533813] end_request: I/O error, dev mmcblk1, sector 17316704
[ 1137.539855] end_request: I/O error, dev mmcblk1, sector 17316712
[ 1137.545867] end_request: I/O error, dev mmcblk1, sector 17316720
[ 1137.551910] end_request: I/O error, dev mmcblk1, sector 17316728
[ 1137.557952] end_request: I/O error, dev mmcblk1, sector 17316736
[ 1137.766906] Aborting journal on device mmcblk1p1.
[ 1137.997436] journal commit I/O error
[ 1138.001037] EXT3-fs error (device mmcblk1p1) in ext3_create: IO failure
[ 1138.225067] ext3_abort called.
[ 1138.228149] EXT3-fs error (device mmcblk1p1): ext3_journal_start_sb: Detected aborted journal
[ 1138.236785] Remounting filesystem read-only |
|
214 | Core | Bug Report | High | op_wifi pnd not exiting cleanly, with fix (one characte ... | Closed | |
Task Description
The op_wifi pnd does not exit out cleanly once the encased script executes,
the pndrun_op_wifi.out reports
umount: /mnt/utmp/op_wifi: device is busy.
umount: /mnt/utmp/op_wifi: device is busy.
umount UNION failed, didn't clean up. Process still using this FS :
3197 ? S 0:00 /bin/sh /etc/init.d/wl1251-init start
This op_wifi.sh just calls
/usr/pandora/scripts/op_wifi.sh
for some reason, the init.d/w.... start causes it to hang, I executed all this locally, and it doesn't appear to keep running
Appending " &" to the line which calls this init script, solves the problem. |
|
213 | Application | Bug Report | Low | Gigolo does not perform it's task | Closed | |
Task Description
In it's current state, Gigolo is flat out broken and (almost) useless. It pretends to to it's job, but can't because it's missing critical pieces of anatomy.
It can mount local filesystems correctly, but then so can thunar, so this is a redundant and useless function. The main reason to use Gigolo is to mount remote filesystems easily, and without having to use the terminal, and to save passwords in your keychain.
The solution to the problem is to perform the following tasks:
sudo opkg install gvfsd-sftp sshfs-fuse
sudo mousepad /etc/modutils/fuse
type "fuse" save and quit
sudo update-modules |
|
211 | Core | Bug Report | Low | x11vnc server (in xfce menu - > network) does not work! | Closed | |
Task Description
x11vnc launcher in xfce menu -> network does not work.
can this be fixed please. |
|
208 | Core | Bug Report | Critical | HOTFIX 4 and 5 Slow WIFI | Closed | |
Task Description
I'm getting 5kb/s with bursts up to 10kb/s if I am lucky.
I have attempted every channel on my router.
Tried every encryption even no encryption.
Tested with the router's wifi speed: 300Mbps 154Mbps and 45Mbps
I'm running Hotfix 5 RC2.
Wifi works fine with my android smartphone, and other wireless devices such as a laptop. |
|
207 | Core | Bug Report | Medium | Touchscreen calibration / use of nubs conflict | Closed | |
Task Description
When using certain apps like Basilisk 2 / Dosbox / Enigma the analogue stick and touchscreen are both available to use as a mouse cursor.
All is well with the touch until you decide to touch the analogue stick when then affects touchscreen alignment by about 2 - 3 CM.
This has been going on since first release. |
|
205 | Core | Bug Report | Medium | libpnd functions and dynamic libs missing | Closed | |
Task Description
tried to compile a simple test application that uses functions from libpnd, namely
pnd_evdev_open(pnd_evdev_e)
pnd_evdev_dpad_state(pnd_evdev_e)
pnd_evdev_closeall()
but all 3 seem to be missing.
yes, i'm linking to libpnd ... but no chance to get it running.
i'm using ivanovic's latest toolchain, which in turn installs "pandora-libpnd-dev_1.0-r40.5_armv7a.ipk" ...
also, there's only the static library available inside, no dynamic libraries. |
|
204 | Core | Bug Report | Medium | fonts issues | Unconfirmed | |
Task Description
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 :( |
|
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. |
|
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. |
|
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 |
|
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. |
|
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. |
|
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. |
|
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/ |
|
193 | Core | Bug Report | Low | Cannot reach button well in ubuntu x64 | Closed | |
Task Description
Window can also not be resized |
|
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 |
|
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. |
|
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. |
|
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 |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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 |
|
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 |
|
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 |
|
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}\" " |
|
169 | Core | Bug Report | Low | pidgin freezes all the time | Closed | |
Task Description
pidgin freezes all the time |
|
168 | Core | Bug Report | Low | qt-embedded doesn't work | Closed | |
Task Description
qt-embedded doesn't work |
|
167 | Application | Bug Report | Low | midori crashes all the time | Closed | |
Task Description
midori crashes all the time |
|
165 | Core | Bug Report | Low | VPNC does't work | Closed | |
Task Description
vpnc doesn't work |
|
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. |
|
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". |
|
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... |
|
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. |
|
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. |
|
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). |