|
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. |
|
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. |
|
212 | Core | Feature Request | Low | Add curl to core installed programs | Closed | |
Task Description
I wish for curl to be installed by default on the upcoming pandora FWs,
As reported by the angstrom repo, where I install using the command:
$sudo su
...
#opkg update
#opkg install curl
curl 7.21.2-r4.0.9 is 78.57 Kilobytes with the dependencies
Depends:libcurl4, libgnutls26, libgcrypt11, libgpg-error0, libc6, libz1
I do not know which is installed by default, but I'm sure libc6 is, so I'm going to state the info on the rest of the packages for its memory space usage on the NAND
libcurl4(142.99 Kilobytes):
Command line tool and library for client-side URL transfers.
Depends:libc6, libgnutls26, libz1, libgcrypt11, libgpg-error0, as you can see, it has the same dependencies as above, so it seems both curl and libcurl are probably exclusive from the others, but I will go forward and state the rest of the dependencies
libgnutls26 2.8.6-r10.0.5 (291.44 Kilobytes)
Depends:libz1, libgcrypt11, libgpg-error0, libc6, (again, it looks like the above depends on this)
libgcrypt11 1.4.1-r0.9 (220.35 Kilobytes)
Depends: libgpg-error0, libc6, (Oh look, we're not looking at libz1 anymore)
libgpg-error0 1.4-r7.1.9 (5.78 Kilobytes)
Depends:libc6
now to the lone libz1
libz1 1.2.3-r7.0.9 (41.95 Kilobytes)
Depends:libc6
So, in the case we already have the gpg stuff, then the installation is only 221.56KB, however, with the zlib and the gpg included, the total comes to 781.08KB
So, now that the cost is out of the way, What are the goods and bads?
Good:
Its a very versatile CLI program to get and send information over http through the network, and is tolerant of network issues
It doesn't take too much space relative to things that have been pulled out, like abiword.
The libcurl is a very good library, and could be of great benefit to some future projects.
Bad:
Well, we already have wget, which is not as configurable, and wget hates Craig's appstore
Here's the link to curl on the repo
http://www.angstrom-distribution.org/repo/?pkgname=curl |
|
220 | Core | Feature Request | Low | Please include /usr/bin/xkbset | Closed | |
Task Description
One of the first things after installing HF5 was downloading xkbset, because it is necessary for proper L-R buttons mapping as mouse buttons. Could you please include that in the system?
I am using urjaman's executable from here:
http://www.gp32x.com/board/index.php?/topic/55124-remapping-the-mouse-buttons-etc/page__st__15__p__896576&#entry896576
Even better would be a GUI that allows mapping of L-R buttons for mouse, just like GUI for nubs :) But including xkbset will be already good. |
|
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 :) |
|
241 | Application | Feature Request | Low | MiniMenu shall remember state for next start | Closed | |
Task Description
With the setting "Live (not exit) on app run?" set to "NO" the currently selected tab and item shall be remembered, so that you return to the same state, in which you left MiniMenu. |
|
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. |
|
248 | Core | Feature Request | Medium | Support for hibernation by caching to SD card | Closed | |
Task Description
It would be very desirable that the PandoraOS could hibernate, and that this action can easily be accessed/triggered with either a hotkey or as an action for the max-idle-time-event or lid-close-event.
That would be the battery friendly universal action to quickly pause/resume any arbitrary application/task.
The current standby mode is far to power consuming for breaks longer than ~ 1 hour. Improving standby mode to be more battery-friendly would of course be too highly appreciated and practical.
If hibernation is triggered, RAM content gets written to a special file or partition on a SD card. The boot-manager of course needs to recognize such a RAM-file on SD-cards. In case it finds more than 1, i.e.: multiple cards/partitions, the one with the newest timestamp gets priority.
256MB RAM with about 10-20 MB/s read/write time to SD, would result in 25-12 seconds for going into or out of hibernation, which would be acceptable for me. In practice it would mean, that if I quickly have to pause me OpenPandora operation (i.e. train stop), I just close my lid, and put the Pandora into my pocket (2-4 seconds), and I am then trusting that the rest reliable happens in my pocket (10-20 seconds). |
|
275 | Core | Feature Request | Low | User should be a member of the cdrom group | Closed | |
Task Description
These permissions are needed for CD/DVD burning/player apps.
From bdc88595d8af726b3bf4745ece310f92299d8759 Mon Sep 17 00:00:00 2001
From: Paul Dersey
Date: Sun, 19 Feb 2012 17:22:41 -0500
Subject: [PATCH] pandora-first-run-wizard: add user to cdrom group
---
recipes/pandora-system/pandora-first-run-wizard.bb | 2 +-
.../pandora-first-run-wizard/first-run-wizard.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes/pandora-system/pandora-first-run-wizard.bb b/recipes/pandora-system/pandora-first-run-wizard.bb
index 904dc4a..a63dc0c 100755
--- a/recipes/pandora-system/pandora-first-run-wizard.bb
+++ b/recipes/pandora-system/pandora-first-run-wizard.bb
@@ -6,7 +6,7 @@ RDEPENDS = "hsetroot zenity dbus pandora-wallpaper-official tslib tslib-calibrat
COMPATIBLE_MACHINE = "omap3-pandora"
-PR = "r28"
+PR = "r29"
SRC_URI = " \
file://first-run-wizard.sh \
diff --git a/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh b/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh
index a801e3f..f30b80e 100755
--- a/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh
+++ b/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh
@@ -88,7 +88,7 @@ while ! username=$(zenity --title="Enter your username" --entry --text "Please c
zenity --title="Error" --error --text="Please try again." --timeout 6
done
-while ! useradd -c "$name,,," -G adm,audio,video,netdev,wheel,plugdev,users "$username" ; do
+while ! useradd -c "$name,,," -G adm,audio,cdrom,netdev,plugdev,users,video,wheel "$username" ; do
username=$(zenity --title="Please check username" --entry --text "Please ensure that your username consists of only\nletters and numbers and is not already in use on the system." --entry-text "$username")
done
--
1.7.8.3 |
|
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 |
