|
143 | Core | Bug Report | Low | LED triggers timer and heartbeat cause freezing when us ... | Closed | |
Task Description
Summary is about all i can dug out now. Somehow related to the PWM driving, because SD, bt and wifi leds work with trigger=timer.
NOTE: power and charger leds are driven by PWM (just so you all know what I'm talking about).
All i wanted to do was to add blinking power led to low power mode and all i get is a frozen pandora :/. |
|
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. |
|
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. |
|
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 |
|
278 | Core | Bug Report | Low | Kernel 3.2.x: broken middle click on right nub | Closed | |
Task Description
Using kernel 3.2.x middle click with the right nub is no longer working. With the "old" kernel you get a middle click when pushing the right nub down, this is no longer the case when eg using SuperZaxxon Beta3 (was already the case in SuperZaxxon Beta1 with kernel 3.2.1). As long as you are using kernel 2.6.27.x middle click is working as expected. |
|
276 | Core | Feature Request | Low | Kernel 3.2.x: add script to activate zram | Closed | |
Task Description
Please add a script to activate zram (RAM compression) when using the new kernel. More info about how to do this is available in this post:
http://boards.openpandora.org/index.php?/topic/7844-superzaxxon-beta-3-released/#entry138834
http://boards.openpandora.org/index.php?/topic/7226-superzaxxon-beta-11-released/page__st__20#entry128665
Please be aware though that Linux-SWAT had to explicitly set a value in "/sys/block/zram0/disksize" to get it work with Slackware. Over here the following is automatically set:
pandora:~$ cat /sys/block/zram0/disksize
61648896
Sadly I can *not* change this value, even using sudo:
pandora:~$ ls -l /sys/block/zram0/disksize
-rw-r--r-- 1 root root 4096 Apr 9 12:51 /sys/block/zram0/disksize
pandora:~$ cat /sys/block/zram0/disksize
61648896
pandora:~$ sudo echo 61648888 > /sys/block/zram0/disksize
-bash: /sys/block/zram0/disksize: Permission denied
Basically the following commands are required in a startup script to automatically create the "compressed swap inside RAM" aka zram (possibly a check if the modprobe was successful makes sense as well as checking for the size of the created ramdisk):
modprobe zram
mkswap /dev/zram0
swapon -p 5 /dev/zram0 |
|
264 | Core | Bug Report | Low | Issues with HOTFIX 6 R1 Beta | Closed | |
Task Description
I started with hotfix 5 and when I used the Left Nub for mouse movement it performed well.
I installed HOTFIX 6 R1 Beta and the Nub works fine except pushing up. It moves the cursor very slow and all other directions just fine. The other nub works just fine as well.
This only began after I installed HF6R1B.
I also had to install the Hotfix twice due to sustained system freeze upon start up on the first attempt.
I enabled gui choice but minimenu does not function it just cycles back to GUI choice. |
|
306 | Core | Bug Report | Low | Issue with Network Notification pop-ups | Closed | |
Task Description
Clicking on the button in a notification used when WiFi is enabled (such as the one stating that Wireless Networks were found), doesn't close the notification. In order to close it, I have to click the X button that's in the top-left. |
|
63 | Core | To Do (Reminder) | Low | Include new panel-setup for XFCE4 | Closed | |
Task Description
I enhanced the XFCE4-Panel setup a bit, since we now have working ALSA mixer and a battery monitor.
The files inside the attached archive should go to
/etc/xdg/op/xfce4/panel/*
in the image. |
|
60 | Core | To Do (Reminder) | Low | Include new menufile (Setting) for XFCE4 | Closed | |
Task Description
I just built a nice menu file which features subdirectories for games and emulators :)
I attached it, the old one should be replaced:
/etc/xdg/menus/xfce-applications.menu |
|
325 | Core | Bug Report | Low | Impossible to not set password at first boot | Unconfirmed | |
Task Description
The Wiki states that the Pandora can be used without setting a user password on first boot. But when the password and password confirmation field are left empty, an error pops up saying that there is a password missmatch.
(Please don't fix this bug by just changing the statement in the Wiki ;-) |
|
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. |
|
331 | Core | Bug Report | Medium | Hold switch key continuously sends X11 KeyPress events ... | Unconfirmed | |
Task Description
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). |
|
259 | Core | Bug Report | High | Hold switch does NOT lock keyboard! Especially crucial ... | Closed | |
Task Description
Apps, which operate with the Pandora in closed lid mode, such as audio players, server processes, etc, in a button-press-probably environment (as i.e. your pocket) still CAN receive the shoulder button L + R key presses, and if they have a meaning in these programs, they could trigger undesired actions.
And also in the current implementation of the Low Power Mode (See: FS#260) key presses may still be received.
Therefore I strongly propose to implement the HOLD switch to en/dis-able a keyboard lock.
IN DETAIL: This shall be global, meaning that the input processing software (however this is implemented on the Pandora: kernel, driver, … ) keeps the lock state (on/off), and if the keyboard state is off,
a) discards all input, or
b) if it makes sense for some reason/applications (any ideas?) just writes them into a queue/buffer, which gets (partially) executed or made accessible to certain software after the keyboard gets unlocked again.
FYI: I have tested the hold switch with the Pandora Input-Tester, and it is recognized. So my report is definitely a software (and not an hardware) issue. |
|
268 | Core | Bug Report | Low | HF6: error in op_power.sh | Closed | |
Task Description
When powering the system off after it has been in low power state once, an error is reported by op_power.sh, line 173.
Unfortunately I don't have the full message as it's visible on the console only for a short time before the screen turns off.
From looking at the script, the "fi" in the last line might be superfluous. |
|
267 | Core | Bug Report | High | HF6-Updater.pnd loses pnd_run.sh | Closed | |
Task Description
Several users have reported that running HF6-Updater.pnd leads to a missing /usr/pandora/scripts/pnd_run.sh
Possibly the file is locked by the Updater itself when installing pandora-libpnd_1.0-r56.5_armv7a.ipk
Forum thread:
http://boards.openpandora.org/index.php?/topic/5652-hotfix-6-final-released/page__view__findpost__p__99313 |
|
232 | Core | Bug Report | Low | HF6 - charged completed with lid closed causing keyboar ... | Closed | |
Task Description
HF6 - It seems as when charging finishes with pandora on then charge light goes out (charge completed assuming) keyboard not functioning just gamepad. Can't use letters to cycle through in mini minimenu or use space to pull up ovr settings.
Will test further |
|
290 | Core | Bug Report | Medium | gnome-mount not available | Unconfirmed | |
Task Description
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? |
|
37 | Core | Bug Report | Very Low | Game doesn't start in No-X mode (pnd_run.sh) (Permissi ... | Closed | |
Task Description
EDIT:
Some more information from notaz:
it's failing because it can't find controlling tty (/dev/tty is a "virtual" gateway device, so setting permissions gave no effect)
do "ps ax" on your desktop and it has the tty column
so SDL fbdev driver wants to get a real tty fo be able to read keys
So we need to somehow give it a real tty?
yeah, but I don't know why as pnd start from X and that gives virtual tty
*don't know how*
maybe something can be done using openvt, chvt and similar tools
------
What happens if you run a script in no-X mode:
1. It stops slim
2. It mounts all the directories as needed (works fine).
3. It DOES NOT start the app
4. It unmounts all the directories
5. It restarts slim (and therefore X)
I can confirm the path is correctly and the filesystem is mounted there (did an ls -l).
I can also confirm the game is working fine, as the same PND does work within X if I run it from the terminal using pnd_run supertux_noX.pnd
So it looks like the line that actually executes the game does work when run in X, but not when run outside of X.
Maybe it tries to execute the game on the screen where the script is actually started (X) and therefore can't run it as X is not running anymore?
The line working in X-mode but not working in non-X-Mode:
LD_LIBRARY_PATH=/mnt/utmp/$BASENAME ./$EXENAME $ARGUMENTS
The game I tried was SuperTux (SDL-Game) with a no-X=1 parameter in the PXML. |
|
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 :( |
|
39 | Core | Bug Report | High | file doesn't work (missing magic files) in image from F ... | Closed | |
Task Description
It seems there's a bug in the latest package "file 5.04-r0.5" of the Angström repository:
It's missing the magic files and therefore doesn't work.
Unfortunately, pnd_run.sh depends on it and therefore it breaks the PND-system.
Installing an older stable version (http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv7a/base/file_4.21-r0.1_armv7a.ipk) does make it work again.
First appeared on image from Feb 13th, not fixed in image from Feb 22nd yet. |
|
12 | Core | To Do (Reminder) | Low | file association for .pnd | New | |
Task Description
Build the xml file and defaults.list so that pnd_run is file-assocated to .pnd |
|
235 | Core | Bug Report | Low | File /tmp/currentuser cannot be deleted by other users | Closed | |
Task Description
The system creates a file /tmp/currentuser at the first login of a user. After logging out and in as another user the file still contains the previous user name. An cannot be deleted/overwritten by the new user.
Steps To Reproduce:
At least two users are available and have XFCE GUI enabled.
1. Login as user (eg. guest), a file /tmp/currentuser is created (containing guest)
2. Log out
3. Log in as another user (eg. jgeiss), the file still contains the old name
4. Change GUI to PMenu
5. Log out
6. Log in as first user (guest)
Now the first user (guest) has PMenu as GUI which was set by the second user (jgeiss).
Maybe the permission should be 0666 for this file? |
|
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}\" " |
|
47 | Core | To Do (Reminder) | Medium | evmapperd: Blinking LED and charging control | Closed | |
Task Description
evmapperd should start blinking when the power is getting low.
Ideally, the blinking speed should increase with decreasing battery power and should start maybe at 5% as default (would be nice to have the settings configurable by the user).
As soon as the AC adaptor is connected, blinking should stop.
When the battery power is at 0% it should immediately shutdown and poweroff (NOT to be overridden by the user!)
Aditionally, we should have some charging control (or would it be better using a different daemon for that?)
Here's part of my conversation with MichaelW:
when the charge current was below a threshold, it would reduce the charger input current allowed and take it down to about what the system needs
it would be an active thing constantly sampling the system and constantly updating the input current to match the system
the alternative is that when the battery is full, the charge path is cut off until the battery drops down a bit, maybe 90% |
|
229 | Core | Bug Report | High | Enable wake on alarm interrupts | Unconfirmed | |
Task Description
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??? |
|
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. |
|
100 | Core | Bug Report | Low | Demos & Examples - remove from image | Closed | |
Task Description
/usr/bin/qt4/demos is 9Mb in size and /usr/bin/qt4/examples is 11Mb.
I'm guessing these are only useful for developers. Can they safely be removed?
edit: additionally, /usr/share/vim is 12M. Can those of us who are never going to use VIM remove it? |
|
227 | Core | Bug Report | Low | Delete button won't delete, and function lock doesn't w... | Unconfirmed | |
Task Description
If you hit the function button, then hit it again to lock the function keys, it doesn't lock the function key.
The delete key, hold shift and hit the back space button, it won't delete, meaning it won't remove the character to the right of the cursor. I saw this on the forum, and confirmed it on my pandora also. |
|
87 | Core | Bug Report | Medium | default /etc/network/interfaces is causing problems | Closed | |
Task Description
The default /etc/network/interfaces has 192.168.1.0/24 subnet set up for usb0 which causes wifi connectivity to fail for users that have wifi on the same subnet.
All addresses should be edited out from /etc/network/interfaces, eth* stuff should probably be dropped too. |
|
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/ |
|
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. |
|
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. |
|
48 | Core | To Do (Reminder) | Low | Create the TV Out Enable / Disable scripts | Closed | |
Task Description
The commands do exist, I just need to wrap them round some zenity scripts. |
|
302 | Core | Bug Report | Low | Correct keymap not available during login process | Closed | |
Task Description
The correct keymap, as matching the characters printed on the keys, is available when running the First Boot Wizard, but not during login.
This means that special characters like ! ( ) and so on, which you enter via Fn-[2nd key] cannot currently be used in a username nor password.
My first experience with my Pandora was therefore that I had to reflash the OS due to this as I had locked myself out because I used a special character in my first chosen password.
Also reported here:
http://boards.openpandora.org/index.php?/topic/10112-question-mark/#entry188179 |
|
327 | Core | Feature Request | Low | Context menu for the XFCE menu | Unconfirmed | |
Task Description
Right now. the XFCE menu handles right clicks like left clicks. It would be more logical to either not do anything on a right click, or open a context menu that e.g. lets the user generate a link to an application on the desktop. |
|
11 | Core | Bug Report | High | Console keymap: Two keys not mapped yet | Closed | |
Task Description
INS (Fn + Del) is not working in console yet.
ALT and CTRL are not working in console yet.
The rest of the console keys are fine (tested in nano).
Keys in X are mapped completely. |
|
234 | Core | Feature Request | Medium | Changeable behaviour when closing the lid | Closed | |
Task Description
As it was requested on forum.gp2x.de and I think it's a good idea I've written some scripts to allow the user to change what happens when the lid is opened/closed.
There are 3 Settings:
-The old behaviour (turning off the screen)
-Go into low power mode
-Shutdown
Default behaviour is still the same: Turn the screen off. Maybe we could change this to low power mode? I don't know.
I made a lot of changes to op_lid.sh: http://pastebin.com/GT3qxWSx (diff: http://pastebin.com/Z8GwpDj8 )
I changed line 11 in op_power.sh to: if [ $powerstate -ne 0 ]; then
And wrote a gui for changing the setting using zenity: http://pastebin.com/9JvSTqfQ
(I still can't upload any files, don't know if it's the fault of my browser, that's why I use this paste service) |
|
49 | Core | To Do (Reminder) | Low | Change some of our scripts into internal PNDs | Closed | |
Task Description
Some of our scripts (CPU Speed, Switch Default GUI, Enable TV Out) should be changed into PND format so that pmenu can also run them. |
|
307 | Core | Feature Request | Medium | Change how Automatic Shutdown works | Unconfirmed | |
Task Description
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. |
|
236 | Core | Bug Report | Low | Cannot unmount SD-Card | Unconfirmed | |
Task Description
SD-Card in Pandora can only be unmounted by guest (uid=1000) but not by jgeiss (uid=1001).
Steps To Reproduce:
Insert SD-Card (or boot with SD-Card inserted),
Login as jgeiss (uid=1001),
Try to unmount SD-Card via XFCE-Popup-Menu (right mouse click on SD-Card-Icon and select unmount). |
|
101 | Core | Bug Report | High | Cannot unmount SD card or USB stick through the GUI | Closed | |
Task Description
When I rightclick and select "unmount" I always get an error, see below.
unmounting from a terminal window works fine.
Also see:
http://www.gp32x.com/board/index.php?/topic/54353-unmount-sd-card-hdd/
"Unable to unmount .... Cannot open /media/.hal-mtab" |
|
193 | Core | Bug Report | Low | Cannot reach button well in ubuntu x64 | Closed | |
Task Description
Window can also not be resized |
|
292 | Core | Bug Report | Low | Can't seek in ogg files using pygame / SDL | Unconfirmed | |
Task Description
Using pygame I try to play a music file starting from some position in the middle::
import pygame
pygame.init()
pygame.mixer.init()
pygame.mixer.music.load('some_file.ogg')
pygame.mixer.music.play(0,60)
This should start playing the file from the firs minute, instead on the pandora the file plays from the start.
I've tried the same code in a debian (sid) chroot (from extend utils) and it works correctly, as it does on my pc (debian wheezy).
I suspect that the issue may be present also in .next (I've done a very quick test on a friend's pandora).
Some relevant version numbers:
* libogg.so.0.6.0 (on debian libogg.so.0.8.0)
* libSDL_mixer-1.2.so.0.10.1 (on debian libSDL_mixer-1.2.so.0.12.0) |
|
6 | Core | Bug Report | Medium | Calibrate Touchscreen within the Settings-Menu of XFCE ... | Closed | |
Task Description
It doesn't run. |
|
245 | Core | Feature Request | Low | BugTracker: Submitter shall be able to edit bug after p ... | Closed | |
Task Description
I accidentally posted a "feature request" as a "bug report" within the FlySpray BugTracker.
I wanted to correct my mistake.
It was not possible to edit it.
I assigned the bug to myself.
Then I could edit it.
But now I cannot un-assign it from me.
I merely wanted to suggest a feature but not take development responsibility (yet).
For original submitters, who later realize a mistake in their post, there should be a possibility to correct their mistake.
Please un-assign me from #237 #241 #243 and this one #245. Thanks. |
|
226 | Core | Feature Request | High | Boot from /dev/sda devices requested | Closed | |
Task Description
Boot from usb hard disk not supported. This should be a rather simple fix of adding the sdx devices and adjust the boot scripts??
I was able to put this autoboot.txt on mmc 0:1
setenv bootargs debug root=/dev/sda1 rw rootdelay=2 console=ttyS0,115200n8 vram=6272K omapfb.vram=0:3000K
ext2load sda 0:1 0x80300000 /boot/uImage
bootm 0x80300000
This failed with amongst other things "Block device sda 0 not supported" and something about failing to load kernel
So I then changed the autoboot file to this
setenv bootargs debug root=/dev/sda1 rw rootdelay=2 console=ttyS0,115200n8 vram=6272K omapfb.vram=0:3000K
ext2load mmc 0:3 0x80300000 /boot/uImage
bootm 0x80300000
All this did was die after the kernel loaded.
I believe I could much better make use of this device if I could boot from some faster storage, please advise :) |
|
304 | Core | Bug Report | Low | bluetooth serial port sleep causes lost / frozen connec ... | Closed | |
Task Description
I experienced (reliably) 3 times that if I had an idle ppp/rfcomm connection to my phone, it would eventually freeze so that the phone reported no active bluetooth connection and the pandora ppp would still think that the connection is active, but no data would flow. Killing pppd and re-trying would fail opening of the rfcomm link with "Host is down".
Disabling & enabling bluetooth "fixed" this so that pppd worked again (so it is not the phone that was "down").
Adding these lines to op_bluetooth_work.sh (apparently atleast) fixed it for me:
add between lines 14-15:
echo 0 > /sys/devices/platform/omap_uart.0/sleep_timeout
(or at any place during enable for that matter)
And to disable (before exit 0, line 30) to save power when bluetooth is off and restore normal settings:
echo 10 > /sys/devices/platform/omap_uart.0/sleep_timeout
I remember mentioning this way back when I last tested bluetooth, but got a reply that this should not be needed because we have flow control between the bt chip and pandora. But if a sleeping serial port loses a character when somebody sends a burst to it, what could flow control do? If it reported not ready to receive, the character would never be sent (and things would freeze...). If it reports ready to receive (what I think it does) the character will be lost. One would need to periodically disable the serial port sleep (and enable ready to receive) for a moment to check for pending data, but I think this would use more power than keeping the serial port active and/or possibly cause way too big delays.
I'm not really certain of this thing (whether this is a workaround, hack or a real fix... and whether my interpretation of what is happening is correct - i have no real proof), but I think that reporting what I've found is better than not. (And am I the only user of bluetooth with an old phone for internet (ppp+rfcomm, not pan)? ...) |
|
131 | Core | Bug Report | Medium | bluetooth drivers read timeout too trigger-happy/logic ... | Closed | |
Task Description
Shamelessly plugged from the forums, to get proper bug tracking and notifications on this. My post:
@notaz:
+ /* there hould be no rx in progress at this point */
+ if (info->rx_skb != NULL) {
+ dev_err(info->dev, "Receive timed out, %i done, %li left, "
+ "LSR=%02x, IER=%02x\n", info->rx_skb->len + 1,
+ info->rx_count, hci_h4p_inb(info, UART_LSR),
+ hci_h4p_inb(info, UART_IER));
+ info->rx_timed_out = 1;
+ }
Could you share your rationale for that comment in drivers/bluetooth/hci_h4p/core.c? (Oh and there's a typo, too :P )
EDIT: Asking this because commenting that block out changed status of bluetooth (for me) from unusable (can receive ~20-500kB of data before ppp connection halting) to fully working - used to have big problems playing 32kbps AAC stream (max 2 min), now already 4 mins of 96kbps, but i still think we need some receive timeout mechanism, but this one (as it currently stands) doesnt work.
Notaz's reply:
I don't really remember, it was more than 1.5 years ago. That driver is a hack, will need to review it, does it work stable with that code removed?
My reply:
For the non-IRC people:
urjaman on IRC said:
(22:47:45) urjaman: notaz: about stability: i'm on irc atm with that driver, its been playing internet radio for a few hours without problems now, but i don know for sure.
(22:48:00) urjaman: *dont know
(22:50:11) urjaman: my logic: if the serial port _never_ misses a byte it should be ok - IMO scary without some receive timeout, but works for me |
|
320 | Core | Bug Report | Low | Bluetooth connection lost after wake-up from sleep mode | Unconfirmed | |
Task Description
When an internet connection was established through a mobile phone (Android, tethering) via bluetooth, the internet connection will not be re-established when the Pandora was sent to sleep and woken up again. The Pandora seems to be connected to the mobile phone, but no internet connection can be established, not even when manually trying to connect. The only way out is to disable bluetooth and enable it again.
I had similar problems with WiFi, before notaz tweaked the system (http://boards.openpandora.org/index.php/topic/11416-wifi-mysteries-resolved-once-and-for-all-—-power-saving-is-clearly-the-culprit/?p=249036). |