WebOS Internals - User contributions [en]

GSM & UMTS Frequencies

2011-05-04T15:24:16Z

Jho:

This is to track the frequencies available on different webOS phones.

<We should insert a table here but I don't know how>

[http://kb.palm.com/wps/portal/kb/na/pre/p100eww/att/solutions/article/65931_en.html%5DPalm%20Support%20:%20Palm%20Pre%20Plus%20for%20AT&T%20-%20Understanding%20network%20bands%20and%20frequencies%20for%20a%20GSM/UMTS%20phone Frequencies for Palm Pre/Pre Plus/Pre 2 US & RoW]
[http://www.worldtimezone.com/gsm.html GSM World Coverage Map]

GSM & UMTS Frequencies

2011-05-04T14:53:39Z

Jho: Created page with "This is to track the frequencies available on different webOS phones. <We should insert a table here but I don't know how> [http://kb.palm.com/wps/portal/kb/na/pre/p100eww/att/..."

WhoIsWho

2010-08-30T07:29:26Z

Jho:

This page lists all the WebOS Internals developers, and the projects and activities for which each is responsible. Names are listed in chronological order of officially joining the WebOS Internals team.

{{AboutMe|alias=rwhitby|realname=Rod Whitby|responsibility=Founder and Project Lead for WebOS Internals and Preware |aboutme=Homebrew Ecosystem Architect. Lead developer for Save/Restore. Co-Lead developer for Preware, Govnah and UberKernel. Co-developer for a number of other packages. Oh, and a family and full-time day job too.}}

{{AboutMe|alias=ka6sox|realname=Tom King|responsibility=Chief Server Infrastructure Architect and Sys-Admin Team Lead(aka BOFH)|aboutme=FT:High Power RF, VHDL/Verilog Design, Play Time: Dabble with Kernel development.}}

{{AboutMe|alias=rboatright|realname=Rick Boatright|responsibility=Chief Evangelist|aboutme=}}

{{AboutMe|alias=destinal|realname=Eric Duprey|responsibility=That would be telling|aboutme=Hacker, security geek, one of the original devs behind the WebOS Internals "Terminal" application}}

{{AboutMe|alias=PuffTheMagic|realname=Ryan Hope|responsibility=Play devil's advocate|aboutme=Research assistant / cognitive science grad student by day; webos developer by night }}

{{AboutMe|alias=egaudet|realname=Eric Gaudet|responsibility=AUPT architect and randomness|aboutme=Busy debugging}}

{{AboutMe|alias=oil|realname=Brandon VanBelle|responsibility=Minister of Awesomeness|aboutme=It's not my fault!}}

{{AboutMe|alias=dtzWill|realname=Will Dietz|responsibility=Various WebOS Internals games, X11, WIDK management|aboutme=CS grad student who spends entirely too much time on WebOS }}

{{AboutMe|alias=zsoc|realname=|responsibility=Multimedia subsystem architect|aboutme=}}

{{AboutMe|alias=uNiXpSyChO|realname=Marco Benton|responsibility=BOFH and Kernel hacker|aboutme=[[Full-time]]; SysAdmin, SAN Admin, Network Admin. [[Part-time]]; System integration and network design consulting. [[Free-time]]; programming - since that's what i used to do full-time 20 years ago. }}

{{AboutMe|alias=sbromwich|realname=Steve Bromwich|responsibility=Kernel developer|aboutme=Dilettante kernel programmer concentrating mostly on extending battery life.}}

{{AboutMe|alias=swisstomcat|realname=Markus Leutwyler|responsibility=Chief German Translator (ja, genau!) and Javascript Parts Donator to different Projects. Also European Propaganda Minister. |aboutme=Web and Mobile Developer}}

{{AboutMe|alias=jhojho|realname=|responsibility=Warthog kernel developer. Various patches.|aboutme=}}

{{AboutMe|alias=cryptk|realname=Chris Jowett|responsibility=Server administration and management|aboutme=I work as a full time linux systems administratior as my day job and lend that knowledge to keep the WebOS Internals servers running as well as they possibly can.}}

{{AboutMe|alias=sconix|realname=Janne Julkunen|responsibility=Creating nice patches and developing Mode Switcher|aboutme=Involved with Linux way too much :)}}

Patch webOS CPU Frequency or Voltage Scaling

2010-07-28T01:27:25Z

Jho: /* Enable SmartReflex */

{{template:patch}}
= Overview=
There are currently 2 methods to enable further power saving - neither is perfect. Note that '''these 2 methods CANNOT be used together''' so make sure you try only one solution at a time. Using both has been reported to brick your Pre, requiring a visit to the WebOS Doctor. Patches for these are now available in the gitorious repo. See [[Applying Patches]]

1 CPU Scaling
* This allows the Pre to scale the CPU clock speed up and down in response to changes in CPU utilization. Some people have reported glitching when using scaling when the CPU is under heavy load (lots of multitasking, playing video, etc).
2 SmartReflex
* This allows the Pre to vary the voltage inside the core in response to silicon characteristics, temperature, voltage, etc. This does not save that much power because it is supposed to be used along with CPU scaling to reduce voltage when the CPU is running slower, but the Pre's kernel is missing the modules to do this. This is why using both together will '''freeze''' the Palm Pre. (Remove the battery, restart with the USB plugged into your computer with NovaCom installed, During the phones boot procedure simply telnet to the phone through NovaCom's Proxy port 8023, remove the smartreflex files you installed in the events folder in /etc/ before WebOS panics)

= CPU Scaling=
== Default Setting==
Frequency scaling does not appear to be active by default on the Pre by default. The directory /sys/devices/system/cpu/cpu0/cpufreq contains information on the current state. The clock seems to be fixed at 500mHz for normal operation (according to cpuinfo_cur_freq), however several other frequencies exist:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# cat ./scaling_available_frequencies
600000 550000 500000 250000 125000
</nowiki></pre>
The file /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state shows that at some point (probably during startup) the frequency is raised to 550mHz for a short period of time.

== Enabling Scaling==
It is possible to enable frequency scaling using the 'ondemand' governor:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo ondemand > ./scaling_governor
</nowiki></pre>
this will cause the frequency to be reduced automatically while idle, and increased as needed during operation, potentially increasing battery life. Because higher frequencies may cause overheating, and TI has noted a significant decrease in the life of the processor when running above 500mHz, you should also restrict the frequency scaling to 500mHz and below by doing the following:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 500000 > ./scaling_max_freq
</nowiki></pre>
If your Pre seems sluggish after enabling scaling, you can try changing the values in /sys/devices/system/cpu/cpu0/cpufreq/ondemand as detailed below.

== 'ondemand' Configuration==
Increasing the value of 'scaling_min_freq' will prevent the CPU from going into extremely low speed configurations, which will significantly improve the responsiveness of the device when it first detects increased CPU usage, at the cost of a little bit of battery life.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 250000 > ./scaling_min_freq
</nowiki></pre>
Setting the value of 'up_threshold' lower will cause the frequency to be increased at lower levels of activity.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq/ondemand# echo 30 > ./up_threshold
</nowiki></pre>
Note: The default setting for 'up_threshold' is 80.

== Checking Performance and Stats==
To check how long your Pre has been running and at what frequency, do this:

<pre><nowiki>cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state</nowiki></pre>

You will see something like this:
<pre><nowiki>600000 906
550000 768
500000 380
250000 0
125000 180505</nowiki></pre>

The first number is the CPU frequency, the second is a time interval. In this example, my Pre has spent the most time @ 125mHz, but you can see it shoots up when needed. Note that if you are overclocking, it really doesn't spend much time at 600mHz, so overheating shouldn't be a problem, but you will definitely notice an improvement. These stats are reset after a reboot.

== Overclocking==
Overclocking is not recommended, as TI has reported a significant decrease in the life of the CPU at frequencies about 500mHz. However some users have reported better responsiveness, in addition to running cooler and using less battery while overclocking.

To overclock to the CPU's maximum speed, do:
<pre><nowiki>echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

To put it back, do:
<pre><nowiki>echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

== Making your changes stick after a reboot==
Create a file called '''cpu-scaling''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# Enables cpu scaling

start on stopped finish
stop on runlevel [!2]

console none

script
echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "30" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
end script
</nowiki></pre>

== Return to Stock Fixed Frequency==
The simple way is just to remove the '''cpu-scaling''' script from /etc/event.d (if you created it) and reboot. None of these changes are persistent without the "sticky" script shown above.

If you switch back to the 'userspace' governor without rebooting, your frequency could get stuck at a lower setting and the whole system get really bogged down. Here is a quick shell script to help you revert to userspace with the original frequency:

Copy/paste this whole line as one command:
<pre><nowiki>echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ; echo 500000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed </nowiki></pre>
Then confirm the frequency/governor are back the way you want.

== Comments and Caveats==
* "I tried this out but video playback was flickery and horrible. The up_threshold tweak setting to 30 seems to improve it a lot , but it's still flickery a bit. Some people may not be happy."

* "I found that setting the max freq to 600000 with the threshold helps this problem. See relevant warnings above first! I don't really watch video on my Pre, so it's not so big of a deal." -pEEf

* "A lot of people on the Precentral forums (myself included) are experiencing the phone locking up after a while of using this, and need to pull the battery to reset. (On webOS 1.0.3 at least.)"

* "I've been running my phone with scaling for nearly a week now without problems, but I'm not 'overlcocking' so to speak. Any specifics on what might cause the locks? (ok had my first locks tonight while attached to the touchstone, weird it never happened before now (and annoying))" -retry

* "I tried the folling over WebOSQuick Installer Linux Console: 1. root@castle: echo ondemand > ./scaling_governor 2. root@castle: echo 500000 > ./scaling_max_freq 3. root@castle: echo 125000 > ./scaling_min_freq 4. root@castle: echo 30 > ./up_threshold . But even after 7hours... nothing changed.. just used 500Mhz in Airplane mode over Night." -Ryo

= SmartReflex=
== Enable SmartReflex==
SmartReflex can be enabled in the VDD1 and VDD2 areas of the OMAP processor by setting two flags under /sys/power
<pre><nowiki>
root@castle:/sys/power# echo -n 1 > /sys/power/sr_vdd1_autocomp
root@castle:/sys/power# echo -n 1 > /sys/power/sr_vdd2_autocomp
</nowiki></pre>
[http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt This slide deck] has much of the pertinent information about SmartReflex and other power-saving technologies on the OMAP processor. Unfortunately the kernel modules that provide many of the features mentioned in the slide deck are not present on the Pre. This is the main reason that SmartReflex may not save a terribly large amount of power.

== Making your changes stick after a reboot==
To enable SmartReflex, create a file called '''smartreflex''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# -*- mode: shell-script; -*-
description "SmartReflex"
author "Alex Markson"
version 1.0

start on stopped finish
stop on runlevel [!2]

console none

script

# SmartReflex
# "SmartReflex™ driver allows for auto-compensation of VDD1 and
# VDD2 voltages (around the voltages specified by current OPP)
# by analyzing the silicon characteristics, temperature, voltage etc"
#
# Enable SmartReflex
echo -n 1 > /sys/power/sr_vdd1_autocomp
echo -n 1 > /sys/power/sr_vdd2_autocomp

end script
</nowiki></pre>

If you want to enable overclocking in addition to SmartReflex, add the following JUST BEFORE the '''end script''' line:
<pre><nowiki>
# according to the OEM shell script in /etc/miniboot.sh
# this seems like it needs to be set twice to make sure ?
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
</nowiki></pre>

== Comments and Caveats==
* "AFter using this for about a week, I find that using SmartReflex causes the Pre to stutter every so often"
* "webos 1.1 w/ no problems to start. Installed ondemand script, full 125-600mhz range, threshold 30: worked fine mostly but on the touchstone it gets hot and locks up kills battery, backlight on behind black screen, every time, within an hour. Switched to smartreflex with 600mhz, no problems, though only a few days so far and no video testing. Media player remix playing to car stereo via bluetooth is smooth." [[User:Bkw|Bkw]] 00:02, 15 September 2009 (UTC)

= Credits=
* Alex Markson for the SmartReflex find and the script.
* pEEf for numerous discoveries related to cpu scaling.
* sidamos for the info about 'up_threshold'
* garrettwp for the cpu scaling event.d script.
* Jauder Ho for gitorious patches

= Hacking=
There is still a lot of work to be done in making this work optimally. The following are some resources and thoughts.
* A paper about the ondemand governor http://www.linuxinsight.com/ols2006_the_ondemand_governor.html
* webOS 1.0.4 has CONFIG_PREEMPT set along with CONFIG_HZ=100. CONFIG_NO_HZ aka tickless is not set. In webOS 1.4.0 (Feb 2010), CONFIG_PREEMPT is not set, CONFIG_HZ=100 and CONFIG_NO_HZ=y (did not check in between).
* Possible patch for NOHZ / ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html
* Use PowerTop to observe what is going on inside the Pre:
** Install [[Next_steps|ipkg-opt]] then run these commands from a root command prompt to install and start powertop:
<div style="font-size:100%;">
<source lang=bash>
cd /opt/bin
./ipkg-opt update
./ipkg-opt install powertop
/opt/sbin/powertop
</source></div>
* http://www.lesswatts.org/
* http://wiki.davincidsp.com/index.php/Running_PowerTOP_on_OMAP35x_platform
* TI 3430 PM presentation http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt
* CPU frequency scaling in Linux with cpufreq. Details on cpufreq parameters http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* smartreflex patches http://www.mail-archive.com/linux-omap@vger.kernel.org/msg26629.html

=More Information=
Right now this is a [slow] collection of data --A2NY

Kernel Config File:
<pre><nowiki>
cat /boot/config-2.6.24-palm-joplin-3430
</nowiki></pre>

Kernel Config Freq:
<pre><nowiki>
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
</nowiki></pre>

Enabled Governors:
<pre><nowiki>
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand userspace
</nowiki></pre>

<pre><nowiki>
ONDEMAND is also called DVFS (Dynamic Voltage & Frequency Scaling)
</nowiki></pre>

# Newer kernels apparently have an improved ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html

Kernel Config PM:
<pre><nowiki>
#
# OMAP Power Management
#

#
# Power Management Options
#
CONFIG_OMAP3_PM=y
CONFIG_OMAP_VOLT_SR_BYPASS=y
# CONFIG_OMAP_VOLT_SR is not set
# CONFIG_OMAP_VOLT_VSEL is not set
# CONFIG_OMAP_VOLT_VMODE is not set

#
# Default VDD1 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD1_OPP1 is not set
# CONFIG_OMAP3ES2_VDD1_OPP2 is not set
# CONFIG_OMAP3ES2_VDD1_OPP3 is not set
CONFIG_OMAP3ES2_VDD1_OPP4=y
# CONFIG_OMAP3ES2_VDD1_OPP5 is not set

#
# Default VDD2 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD2_OPP2 is not set
CONFIG_OMAP3ES2_VDD2_OPP3=y
# CONFIG_ENABLE_VOLTSCALE_IN_SUSPEND is not set
# CONFIG_RESET_IVA_IN_SUSPEND is not set
CONFIG_MPU_OFF=y
CONFIG_OMAP34XX_OFFMODE=y
CONFIG_CORE_OFF=y
# CONFIG_CORE_OFF_CPUIDLE is not set
CONFIG_SYSOFFMODE=y
# CONFIG_HW_SUP_TRANS is not set
# CONFIG_TRACK_RESOURCES is not set
CONFIG_AUTO_POWER_DOMAIN_CTRL=y
# CONFIG_PREVENT_MPU_RET is not set
# CONFIG_PREVENT_CORE_RET is not set
# CONFIG_DISABLE_EMUDOMAIN_CONTROL is not set
</nowiki></pre>

TWL4030:
<pre><nowiki>
/sys/devices/platform/twl4030_registers.0/module_pm_receiver
</nowiki></pre>

Kernel info:
<pre><nowiki>
+ Please note, that by default SmartReflex is only
+ initialized. To enable the automatic voltage
+ compensation for VDD1 and VDD2, user must write 1 to
+ /sys/power/sr_vddX_autocomp, where X is 1 or 2.
</nowiki></pre>

Device Startup:
<pre><nowiki>
2009-11-02T02:40:01.263122Z [15] webos kern.warning kernel: OMAP: Initializing SmartReflex subsystem...
2009-11-02T02:40:01.263549Z [15] webos kern.info kernel: OMAP: SmartReflex subsystem initialized.
2009-11-02T02:40:01.282196Z [15] webos kern.err kernel: OMAP 3430 Power Management subsystem initializing.
2009-11-02T02:40:01.292083Z [15] webos kern.info kernel: OMAP: Setting up clocks.
2009-11-02T02:40:01.319152Z [15] webos kern.warning kernel: OMAP: OPP mismatch: current/target=2:4
2009-11-02T02:40:01.319702Z [15] webos kern.info kernel: OMAP: Change MPU speed: 250 => 550 MHz
2009-11-02T02:40:01.321044Z [15] webos kern.info kernel: OMAP: ARM/DSP clock at 550/396 MHz.
2009-11-02T02:40:01.321624Z [15] webos kern.info kernel: BogoMIPS: 547.88 @550000 KHz
2009-11-02T02:40:01.327911Z [15] webos kern.info kernel: OMAP CPU idle driver initializing.
2009-11-02T02:40:01.328277Z [15] webos kern.err kernel: create_proc_entry succeeded
2009-11-02T02:40:01.342102Z [15] webos kern.info kernel: Initialize power support module
2009-11-02T02:40:01.342742Z [15] webos kern.info kernel: OMAP3: PM: Sirloin target registered successfully.
</nowiki></pre>

SR autocomp is enabled in userspace:
<pre><nowiki>
2009-11-30T17:39:39.106658Z [329] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
2009-11-30T17:39:55.827423Z [345] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
</nowiki></pre>

SR autocomp is enabled in ondemand: (device wants off, will not wake if it goes off)
<pre><nowiki>
2009-11-30T17:27:37.676910Z [7523] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
2009-11-30T17:27:45.676269Z [7531] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
</nowiki></pre>

powersave_bias http://osdir.com/ml/kernel.cpufreq/2006-07/msg00137.html
<pre><nowiki>
This patch adds a "powersave_bias" tunable to ondemand
to allow it to reduce its target frequency by a specified percent.

By default, the powersave_bias is 0 and has no effect.
powersave_bias is in units of 0.1%, so it has an effective range
of 1 through 1000, resulting in 0.1% to 100% impact.

In practice, users will not be able to detect a difference between
0.1% increments, but 1.0% increments turned out to be too large.
Also, the max value of 1000 (100%) would simply peg the system
in its deepest power saving P-state, unless the processor really has
a hardware P-state at 0Hz:-)

For example, If ondemand requests 2.0GHz based on utilization,
and powersave_bias=100, this code will knock 10% off the target
and seek a target of 1.8GHz instead of 2.0GHz until the
next sampling. If 1.8 is an exact match with an hardware frequency
we use it, otherwise we average our time between the frequency
next higher than 1.8 and next lower than 1.8.
</nowiki></pre>

Howto memboot a kernel

2010-07-28T01:02:32Z

Jho: Howto memboot a kernel moved to How to memboot a kernel

#REDIRECT [[How to memboot a kernel]]

How to memboot a kernel

2010-07-28T01:02:32Z

Jho: Howto memboot a kernel moved to How to memboot a kernel

If you are testing out experiemental kernels, this is a very useful trick to know. What this will do is to boot a file (uImage) directly into memory for you. If something bad happens, simply reboot and the old installed kernel on the phone will be used.

novaterm
> tellbootie recover
novacom boot mem:// < uImage

How to memboot a kernel

2010-07-28T01:02:07Z

Jho: New page: If you are testing out experiemental kernels, this is a very useful trick to know. What this will do is to boot a file (uImage) directly into memory for you. If something bad happens, simp...

Testing Feeds

2010-07-07T06:51:09Z

Jho:

=Rules that you must agree to before using these feeds=

Before you use our testing feeds, please read and agree to the following rules:

# Anyone participating in WebOS Internals alpha testing of any kind must be prepared to fully erase and webOS Doctor their phone at a moment's notice without warning and without any regrets or complaints.
# They must be prepared to and able to log into the command line on the device and type Linux commands when instructed to do so. Knowing Linux commands ahead of time is preferred, but not required if you are willing to learn them when necessary or can follow instructions without making mistakes.
# They must be prepared to go to great and extraordinary lengths to try and reliably reproduce any problems they encounter.
# They must give full and detailed bug reports, leaving out no piece of information which could possibly be remotely connected to the problem.
# They must read any and all documentation and forums threads (in their entirety) before asking a question.
# They must fastidiously follow the forum threads where the alpha testing is being discussed by the authors, and follow precisely any instructions given there.

If you're not prepared to do *all* the above, and do it all in good spirit, then please wait for the public release of the item.

If you are prepared to do *all* the above, then by all means please participate in the alpha testing.

Note that everything above is a function of attitude, not of skill.

==Setting up the WebOS Internals testing feeds on your webOS 1.3.5+ device:==

===Using Preware===
With Preware versions 0.9.30 and above, users are now able to add custom feeds through Preware without the use of a computer. The following instructions will explain how to add the Webos-Internals Testing feed for all devices:
#Open Preware and wait for it to finish loading.
#Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.
#Scroll to the bottom until you see the New Feed box.
#Type or paste in the NAME text box. (from phone: shift-click on text to select, then gesture-c to copy, gesture-v to paste)
:webos-testing-all
#Type or paste the URL in the text box
:http://ipkg.preware.org/feeds/webos-internals/testing/all
#*Make sure to delete 'http://' before pasting the URL if the URL already contains 'http://'
#Make sure the IS COMPRESSED option is set to YES.
#Tap Add Feed and then tap Yes when the alert pops up.
#Scroll to the bottom until you see the New Feed box.
#Type or paste in the NAME text box.
:webos-testing-armv7
#Type or paste the URL in the text box
:http://ipkg.preware.org/feeds/webos-internals/testing/armv7
#Make sure the IS COMPRESSED option is set to YES.
#Tap Add Feed and then tap Yes when the alert pops up.
#Gesture swipe back, open the App Menu, and tap Update Feeds.
Congratulations, you have just added a custom feed! For adding other feeds, be sure to replace the name and URL in these instructions with the proper name and URL.

The following are the testing feed URLs specifically for Pre, Pixi, and Emulator respectively. These are separate from the 'all' testing feed (which contains packages that will run on all devices).

Replace 'armv7' with 'armv6' or 'i686' in the instructions above if you are using a Pixi or the Emulator.

:Pre:
:http://ipkg.preware.org/feeds/webos-internals/testing/armv7

:Pixi:
:http://ipkg.preware.org/feeds/webos-internals/testing/armv6

:Emulator:
:http://ipkg.preware.org/feeds/webos-internals/testing/i686

===Using a Computer===
1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the regular WebOS Internals Feed

2. Execute the following script:

<pre>
cd /media/cryptofs/apps/etc/ipkg
echo "src/gz webos-internals-testing-all http://ipkg.preware.org/feeds/webos-internals/testing/all" > webos-internals-testing-all.conf
echo "src/gz webos-internals-testing-armv7 http://ipkg.preware.org/feeds/webos-internals/testing/armv7" > webos-internals-testing-armv7.conf
</pre>

3. Once Preware is launched, selected the Update Feeds menu.

Replace 'armv7' with 'armv6' or 'i686' in the instructions above if you are using a Pixi or the Emulator.

Application:WarthogKernel

2010-06-29T07:10:14Z

Jho:

The warthog series of kernels are the kernels intended to explore performance and benchmarking in a stable manner. It will also cherry-pick patches as needed from sbromwich and unixpsycho kernels.

The kernels are only available at http://ipkg.preware.org/feeds/webos-kernels/testing/1.4.1.1/ and can be added using any standard package manager in the standard format (deducing this is left as an exercise for the reader).

= Patches applied for 1.4.1-61 =

* Various housekeeping for patches
* Top speed is now 1.05GHz, no more 800Mhz (may return later)
* Removed some debugging options
* Initial attempts at undervolting. Report if strangeness is experienced.

= Patches applied for 1.4.1-49 =

* Some makefile housekeeping
* Enabled all TCP congestion algorithms, CPU governors and IO schedulers.
* Testers wanted to help determine optimal configurations. If interested, join #webos-internals IRC channel on Freenode.

= Patches applied for 1.4.1-46 =

* Revised compcache makefile gcc flags
* Initial pixi build. Feedback wanted.

= Patches applied for 1.4.1-43 =

* Compcache included
* Using 2007q3 toolchain
* Use -Os -mtune=cortex-a8 -mcpu=cortex-a8 -march=armv7-a for kernel compile

This makes things about 6% faster @ 500Mhz. YMMV.

= Warnings (THIS IS A TESTING KERNEL) =

* This kernel may be less stable than Uber-Kernel although stability is still a key target.
* This kernel will '''only live in testing''' (meaning, '''no crying if this kernel eats your phone'''). Data and knowledge gleaned from this kernel will migrate to UK over time.
* Out of the testing kernels, warthog will most likely be the closest to uber-kernel. That is, it is intended to be less bleeding edge.

= Notes =

Just a scratchpad for now.

* http://david.woodhou.se/linux-combine-build.patch
* http://david.woodhou.se/olpc-config

Application:WarthogKernel

2010-06-23T02:30:43Z

Jho:

The warthog series of kernels are the kernels intended to explore performance and benchmarking in a stable manner. It will also cherry-pick patches as needed from sbromwich and unixpsycho kernels.

The kernels are only available at http://ipkg.preware.org/feeds/webos-kernels/testing/1.4.1.1/ and can be added using any standard package manager in the standard format (deducing this is left as an exercise for the reader).

= Patches applied for 1.4.1-49 =

* Some makefile housekeeping
* Enabled all TCP congestion algorithms, CPU governors and IO schedulers.
* Testers wanted to help determine optimal configurations. If interested, join #webos-internals IRC channel on Freenode.

= Patches applied for 1.4.1-46 =

* Revised compcache makefile gcc flags
* Initial pixi build. Feedback wanted.

= Patches applied for 1.4.1-43 =

* Compcache included
* Using 2007q3 toolchain
* Use -Os -mtune=cortex-a8 -mcpu=cortex-a8 -march=armv7-a for kernel compile

This makes things about 6% faster @ 500Mhz. YMMV.

= Warnings (THIS IS A TESTING KERNEL) =

* This kernel may be less stable than Uber-Kernel although stability is still a key target.
* This kernel will '''only live in testing''' (meaning, '''no crying if this kernel eats your phone'''). Data and knowledge gleaned from this kernel will migrate to UK over time.
* Out of the testing kernels, warthog will most likely be the closest to uber-kernel. That is, it is intended to be less bleeding edge.

= Notes =

Just a scratchpad for now.

* http://david.woodhou.se/linux-combine-build.patch
* http://david.woodhou.se/olpc-config

Application:WarthogKernel

2010-06-23T02:10:43Z

Jho:

The warthog series of kernels are the kernels intended to explore performance and benchmarking in a stable manner. It will also cherry-pick patches as needed from sbromwich and unixpsycho kernels.

The kernels are only available at http://ipkg.preware.org/feeds/webos-kernels/testing/1.4.1.1/ and can be added using any standard package manager in the standard format (deducing this is left as an exercise for the reader).

= Patches applied for 1.4.1-49 =

* Some makefile housekeeping
* Enabled all TCP congestion algorithms, CPU governors and IO schedulers.
* Testers wanted to help determine optimal configurations. If interested, join #webos-internals IRC channel on Freenode.

= Patches applied for 1.4.1-46 =

* Revised compcache makefile gcc flags
* Initial pixi build. Feedback wanted.

= Patches applied for 1.4.1-43 =

* Compcache included
* Using 2007q3 toolchain
* Use -Os -mtune=cortex-a8 -mcpu=cortex-a8 -march=armv7-a for kernel compile

This makes things about 6% faster @ 500Mhz. YMMV.

= Warnings (THIS IS A TESTING KERNEL) =

* This kernel may be less stable than Uber-Kernel although stability is still a key target.
* This kernel will '''only live in testing''' (meaning, '''no crying if this kernel eats your phone'''). Data and knowledge gleaned from this kernel will migrate to UK over time.
* Out of the testing kernels, warthog will most likely be the closest to uber-kernel. That is, it is intended to be less bleeding edge.

Application:WarthogKernel

2010-06-23T02:10:25Z

Jho:

The warthog series of kernels are the kernels intended to explore performance and benchmarking in a stable manner. It will also cherry-pick patches as needed from sbromwich and unixpsycho kernels.

The kernels are only available at http://ipkg.preware.org/feeds/webos-kernels/testing/1.4.1.1/ and can be added using any standard package manager in the standard format (deducing this is left as an exercise for the reader).

= Patches applied for 1.4.1-49 =

* Some makefile housekeeping
* Enabled all TCP congestion algorithms, CPU governors and IO schedulers.
* Testers wanted to help determine optimal configurations. If interested, join #webos-internals IRC channel on Freenode.

= Patches applied for 1.4.1-46 =

* Revised compcache makefile gcc flags
* Initial pixi build. Feedback wanted.

= Patches applied for 1.4.1-43 =

* Compcache included
* Using 2007q3 toolchain
* Use -Os -mtune=cortex-a8 -mcpu=cortex-a8 -march=armv7-a for kernel compile

This makes things about 6% faster @ 500Mhz. YMMV.

= Warnings (THIS IS A TESTING KERNEL) =

* This kernel may be less stable than Uber-Kernel although stability is still a key target.
* This kernel will '''only live in testing''' (meaning, '''no crying if this kernel eats your phone'''). Data and knowledge gleaned from this kernel will migrate to UK over time.
* Out of the testing kernels, warthog will most likely be the closest to uber-kernel. That is, it is intended to be less bleeding edge.

Application:WarthogKernel

2010-06-21T04:28:13Z

Jho:

Application:WarthogKernel

2010-06-20T09:16:09Z

Jho:

Application:WarthogKernel

2010-06-19T23:27:26Z

Jho:

Application:WarthogKernel

2010-06-19T23:27:00Z

Jho:

Application:WarthogKernel

2010-06-19T12:50:45Z

Jho:

Application:WarthogKernel

2010-06-19T11:20:08Z

Jho: New page: The warthog series of kernels are the kernels intended to explore performance and benchmarking in a stable manner. It will also cherry-pick patches as needed from sbromwich and unixpsycho ...

Application:Health

2010-06-17T04:53:13Z

Jho: Application:Health moved to Application:SysHealth: Proper name.

#REDIRECT [[Application:SysHealth]]

Application:SysHealth

2010-06-17T04:53:13Z

Jho: Application:Health moved to Application:SysHealth: Proper name.

{{application
|name=SysHealth
|type=webOS
|version=In Development
|tag=Utilities
|screenshot=
|description=}}

== Summary ==
{{icon||float:right;}}An app to do things

Application:SysHealth

2010-06-17T04:52:52Z

Jho:

{{application
|name=SysHealth
|type=webOS
|version=In Development
|tag=Utilities
|screenshot=
|description=}}

== Summary ==
{{icon||float:right;}}An app to do things

Patch webOS CPU Frequency or Voltage Scaling

2010-05-04T23:06:21Z

Jho: /* Hacking */

{{template:patch}}
= Overview=
There are currently 2 methods to enable further power saving - neither is perfect. Note that '''these 2 methods CANNOT be used together''' so make sure you try only one solution at a time. Using both has been reported to brick your Pre, requiring a visit to the WebOS Doctor. Patches for these are now available in the gitorious repo. See [[Applying Patches]]

1 CPU Scaling
* This allows the Pre to scale the CPU clock speed up and down in response to changes in CPU utilization. Some people have reported glitching when using scaling when the CPU is under heavy load (lots of multitasking, playing video, etc).
2 SmartReflex
* This allows the Pre to vary the voltage inside the core in response to silicon characteristics, temperature, voltage, etc. This does not save that much power because it is supposed to be used along with CPU scaling to reduce voltage when the CPU is running slower, but the Pre's kernel is missing the modules to do this. This is why using both together will '''freeze''' the Palm Pre. (Remove the battery, restart with the USB plugged into your computer with NovaCom installed, During the phones boot procedure simply telnet to the phone through NovaCom's Proxy port 8023, remove the smartreflex files you installed in the events folder in /etc/ before WebOS panics)

= CPU Scaling=
== Default Setting==
Frequency scaling does not appear to be active by default on the Pre by default. The directory /sys/devices/system/cpu/cpu0/cpufreq contains information on the current state. The clock seems to be fixed at 500mHz for normal operation (according to cpuinfo_cur_freq), however several other frequencies exist:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# cat ./scaling_available_frequencies
600000 550000 500000 250000 125000
</nowiki></pre>
The file /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state shows that at some point (probably during startup) the frequency is raised to 550mHz for a short period of time.

== Enabling Scaling==
It is possible to enable frequency scaling using the 'ondemand' governor:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo ondemand > ./scaling_governor
</nowiki></pre>
this will cause the frequency to be reduced automatically while idle, and increased as needed during operation, potentially increasing battery life. Because higher frequencies may cause overheating, and TI has noted a significant decrease in the life of the processor when running above 500mHz, you should also restrict the frequency scaling to 500mHz and below by doing the following:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 500000 > ./scaling_max_freq
</nowiki></pre>
If your Pre seems sluggish after enabling scaling, you can try changing the values in /sys/devices/system/cpu/cpu0/cpufreq/ondemand as detailed below.

== 'ondemand' Configuration==
Increasing the value of 'scaling_min_freq' will prevent the CPU from going into extremely low speed configurations, which will significantly improve the responsiveness of the device when it first detects increased CPU usage, at the cost of a little bit of battery life.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 250000 > ./scaling_min_freq
</nowiki></pre>
Setting the value of 'up_threshold' lower will cause the frequency to be increased at lower levels of activity.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq/ondemand# echo 30 > ./up_threshold
</nowiki></pre>
Note: The default setting for 'up_threshold' is 80.

== Checking Performance and Stats==
To check how long your Pre has been running and at what frequency, do this:

<pre><nowiki>cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state</nowiki></pre>

You will see something like this:
<pre><nowiki>600000 906
550000 768
500000 380
250000 0
125000 180505</nowiki></pre>

The first number is the CPU frequency, the second is a time interval. In this example, my Pre has spent the most time @ 125mHz, but you can see it shoots up when needed. Note that if you are overclocking, it really doesn't spend much time at 600mHz, so overheating shouldn't be a problem, but you will definitely notice an improvement. These stats are reset after a reboot.

== Overclocking==
Overclocking is not recommended, as TI has reported a significant decrease in the life of the CPU at frequencies about 500mHz. However some users have reported better responsiveness, in addition to running cooler and using less battery while overclocking.

To overclock to the CPU's maximum speed, do:
<pre><nowiki>echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

To put it back, do:
<pre><nowiki>echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

== Making your changes stick after a reboot==
Create a file called '''cpu-scaling''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# Enables cpu scaling

start on stopped finish
stop on runlevel [!2]

console none

script
echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "30" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
end script
</nowiki></pre>

== Return to Stock Fixed Frequency==
The simple way is just to remove the '''cpu-scaling''' script from /etc/event.d (if you created it) and reboot. None of these changes are persistent without the "sticky" script shown above.

If you switch back to the 'userspace' governor without rebooting, your frequency could get stuck at a lower setting and the whole system get really bogged down. Here is a quick shell script to help you revert to userspace with the original frequency:

Copy/paste this whole line as one command:
<pre><nowiki>echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ; echo 500000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed </nowiki></pre>
Then confirm the frequency/governor are back the way you want.

== Comments and Caveats==
* "I tried this out but video playback was flickery and horrible. The up_threshold tweak setting to 30 seems to improve it a lot , but it's still flickery a bit. Some people may not be happy."

* "I found that setting the max freq to 600000 with the threshold helps this problem. See relevant warnings above first! I don't really watch video on my Pre, so it's not so big of a deal." -pEEf

* "A lot of people on the Precentral forums (myself included) are experiencing the phone locking up after a while of using this, and need to pull the battery to reset. (On webOS 1.0.3 at least.)"

* "I've been running my phone with scaling for nearly a week now without problems, but I'm not 'overlcocking' so to speak. Any specifics on what might cause the locks? (ok had my first locks tonight while attached to the touchstone, weird it never happened before now (and annoying))" -retry

* "I tried the folling over WebOSQuick Installer Linux Console: 1. root@castle: echo ondemand > ./scaling_governor 2. root@castle: echo 500000 > ./scaling_max_freq 3. root@castle: echo 125000 > ./scaling_min_freq 4. root@castle: echo 30 > ./up_threshold . But even after 7hours... nothing changed.. just used 500Mhz in Airplane mode over Night." -Ryo

= SmartReflex=
== Enable SmartReflex==
SmartReflex can be enabled in the VDD1 and VDD2 areas of the OMAP processor by setting two flags under /sys/power
<pre><nowiki>
root@castle:/sys/power# echo -n 1 > ./sr_vdd1_autocomp
root@castle:/sys/power# echo -n 1 > ./sr_vdd2_autocomp
</nowiki></pre>
[http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt This slide deck] has much of the pertinent information about SmartReflex and other power-saving technologies on the OMAP processor. Unfortunately the kernel modules that provide many of the features mentioned in the slide deck are not present on the Pre. This is the main reason that SmartReflex may not save a terribly large amount of power.

== Making your changes stick after a reboot==
To enable SmartReflex, create a file called '''smartreflex''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# -*- mode: shell-script; -*-
description "SmartReflex"
author "Alex Markson"
version 1.0

start on stopped finish
stop on runlevel [!2]

console none

script

# SmartReflex
# "SmartReflex™ driver allows for auto-compensation of VDD1 and
# VDD2 voltages (around the voltages specified by current OPP)
# by analyzing the silicon characteristics, temperature, voltage etc"
#
# Enable SmartReflex
echo -n 1 > /sys/power/sr_vdd1_autocomp
echo -n 1 > /sys/power/sr_vdd2_autocomp

end script
</nowiki></pre>

If you want to enable overclocking in addition to SmartReflex, add the following JUST BEFORE the '''end script''' line:
<pre><nowiki>
# according to the OEM shell script in /etc/miniboot.sh
# this seems like it needs to be set twice to make sure ?
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
</nowiki></pre>

== Comments and Caveats==
* "AFter using this for about a week, I find that using SmartReflex causes the Pre to stutter every so often"
* "webos 1.1 w/ no problems to start. Installed ondemand script, full 125-600mhz range, threshold 30: worked fine mostly but on the touchstone it gets hot and locks up kills battery, backlight on behind black screen, every time, within an hour. Switched to smartreflex with 600mhz, no problems, though only a few days so far and no video testing. Media player remix playing to car stereo via bluetooth is smooth." [[User:Bkw|Bkw]] 00:02, 15 September 2009 (UTC)

= Credits=
* Alex Markson for the SmartReflex find and the script.
* pEEf for numerous discoveries related to cpu scaling.
* sidamos for the info about 'up_threshold'
* garrettwp for the cpu scaling event.d script.
* Jauder Ho for gitorious patches

= Hacking=
There is still a lot of work to be done in making this work optimally. The following are some resources and thoughts.
* A paper about the ondemand governor http://www.linuxinsight.com/ols2006_the_ondemand_governor.html
* webOS 1.0.4 has CONFIG_PREEMPT set along with CONFIG_HZ=100. CONFIG_NO_HZ aka tickless is not set. In webOS 1.4.0 (Feb 2010), CONFIG_PREEMPT is not set, CONFIG_HZ=100 and CONFIG_NO_HZ=y (did not check in between).
* Possible patch for NOHZ / ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html
* Use PowerTop to observe what is going on inside the Pre:
** Install [[Next_steps|ipkg-opt]] then run these commands from a root command prompt to install and start powertop:
<div style="font-size:100%;">
<source lang=bash>
cd /opt/bin
./ipkg-opt update
./ipkg-opt install powertop
/opt/sbin/powertop
</source></div>
* http://www.lesswatts.org/
* http://wiki.davincidsp.com/index.php/Running_PowerTOP_on_OMAP35x_platform
* TI 3430 PM presentation http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt
* CPU frequency scaling in Linux with cpufreq. Details on cpufreq parameters http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* smartreflex patches http://www.mail-archive.com/linux-omap@vger.kernel.org/msg26629.html

=More Information=
Right now this is a [slow] collection of data --A2NY

Kernel Config File:
<pre><nowiki>
cat /boot/config-2.6.24-palm-joplin-3430
</nowiki></pre>

Kernel Config Freq:
<pre><nowiki>
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
</nowiki></pre>

Enabled Governors:
<pre><nowiki>
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand userspace
</nowiki></pre>

<pre><nowiki>
ONDEMAND is also called DVFS (Dynamic Voltage & Frequency Scaling)
</nowiki></pre>

# Newer kernels apparently have an improved ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html

Kernel Config PM:
<pre><nowiki>
#
# OMAP Power Management
#

#
# Power Management Options
#
CONFIG_OMAP3_PM=y
CONFIG_OMAP_VOLT_SR_BYPASS=y
# CONFIG_OMAP_VOLT_SR is not set
# CONFIG_OMAP_VOLT_VSEL is not set
# CONFIG_OMAP_VOLT_VMODE is not set

#
# Default VDD1 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD1_OPP1 is not set
# CONFIG_OMAP3ES2_VDD1_OPP2 is not set
# CONFIG_OMAP3ES2_VDD1_OPP3 is not set
CONFIG_OMAP3ES2_VDD1_OPP4=y
# CONFIG_OMAP3ES2_VDD1_OPP5 is not set

#
# Default VDD2 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD2_OPP2 is not set
CONFIG_OMAP3ES2_VDD2_OPP3=y
# CONFIG_ENABLE_VOLTSCALE_IN_SUSPEND is not set
# CONFIG_RESET_IVA_IN_SUSPEND is not set
CONFIG_MPU_OFF=y
CONFIG_OMAP34XX_OFFMODE=y
CONFIG_CORE_OFF=y
# CONFIG_CORE_OFF_CPUIDLE is not set
CONFIG_SYSOFFMODE=y
# CONFIG_HW_SUP_TRANS is not set
# CONFIG_TRACK_RESOURCES is not set
CONFIG_AUTO_POWER_DOMAIN_CTRL=y
# CONFIG_PREVENT_MPU_RET is not set
# CONFIG_PREVENT_CORE_RET is not set
# CONFIG_DISABLE_EMUDOMAIN_CONTROL is not set
</nowiki></pre>

TWL4030:
<pre><nowiki>
/sys/devices/platform/twl4030_registers.0/module_pm_receiver
</nowiki></pre>

Kernel info:
<pre><nowiki>
+ Please note, that by default SmartReflex is only
+ initialized. To enable the automatic voltage
+ compensation for VDD1 and VDD2, user must write 1 to
+ /sys/power/sr_vddX_autocomp, where X is 1 or 2.
</nowiki></pre>

Device Startup:
<pre><nowiki>
2009-11-02T02:40:01.263122Z [15] webos kern.warning kernel: OMAP: Initializing SmartReflex subsystem...
2009-11-02T02:40:01.263549Z [15] webos kern.info kernel: OMAP: SmartReflex subsystem initialized.
2009-11-02T02:40:01.282196Z [15] webos kern.err kernel: OMAP 3430 Power Management subsystem initializing.
2009-11-02T02:40:01.292083Z [15] webos kern.info kernel: OMAP: Setting up clocks.
2009-11-02T02:40:01.319152Z [15] webos kern.warning kernel: OMAP: OPP mismatch: current/target=2:4
2009-11-02T02:40:01.319702Z [15] webos kern.info kernel: OMAP: Change MPU speed: 250 => 550 MHz
2009-11-02T02:40:01.321044Z [15] webos kern.info kernel: OMAP: ARM/DSP clock at 550/396 MHz.
2009-11-02T02:40:01.321624Z [15] webos kern.info kernel: BogoMIPS: 547.88 @550000 KHz
2009-11-02T02:40:01.327911Z [15] webos kern.info kernel: OMAP CPU idle driver initializing.
2009-11-02T02:40:01.328277Z [15] webos kern.err kernel: create_proc_entry succeeded
2009-11-02T02:40:01.342102Z [15] webos kern.info kernel: Initialize power support module
2009-11-02T02:40:01.342742Z [15] webos kern.info kernel: OMAP3: PM: Sirloin target registered successfully.
</nowiki></pre>

SR autocomp is enabled in userspace:
<pre><nowiki>
2009-11-30T17:39:39.106658Z [329] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
2009-11-30T17:39:55.827423Z [345] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
</nowiki></pre>

SR autocomp is enabled in ondemand: (device wants off, will not wake if it goes off)
<pre><nowiki>
2009-11-30T17:27:37.676910Z [7523] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
2009-11-30T17:27:45.676269Z [7531] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
</nowiki></pre>

powersave_bias http://osdir.com/ml/kernel.cpufreq/2006-07/msg00137.html
<pre><nowiki>
This patch adds a "powersave_bias" tunable to ondemand
to allow it to reduce its target frequency by a specified percent.

By default, the powersave_bias is 0 and has no effect.
powersave_bias is in units of 0.1%, so it has an effective range
of 1 through 1000, resulting in 0.1% to 100% impact.

In practice, users will not be able to detect a difference between
0.1% increments, but 1.0% increments turned out to be too large.
Also, the max value of 1000 (100%) would simply peg the system
in its deepest power saving P-state, unless the processor really has
a hardware P-state at 0Hz:-)

For example, If ondemand requests 2.0GHz based on utilization,
and powersave_bias=100, this code will knock 10% off the target
and seek a target of 1.8GHz instead of 2.0GHz until the
next sampling. If 1.8 is an exact match with an hardware frequency
we use it, otherwise we average our time between the frequency
next higher than 1.8 and next lower than 1.8.
</nowiki></pre>

Application:Govnah

2010-04-23T23:43:45Z

Jho:

{{application
|name=Govnah
|type=webOS
|version=In Development
|tag=Utilities
|screenshot=Govnah_ss1.png
|description=}}

== Summary ==
{{icon|Icon_WebOSInternals_Govnah.png|float:right;}}An App to do things.

Available in the WebOS Internals Testing Feed

== Design ==
* Main Scene
** Title Header (like preware/wirc/etc webos-internals apps)
** Current Governor (Tap to go to Governor Settings)
** Current Frequency
** Misc Stats
*** ...?
*** Graph of CPU temp over time

* CPU Governor Scene
** Dropdown to change governor (SelectList)
** Form of all current settings for selected governor (dynamically generated from information provided by service)

* IO Scheduler Scene
** Dropdown to select scheduler (cfq, noop, as etc.)

* TCP Congestion Algo Scene?

* App Icon (changes to display indication of CPU temp)

=== Load Reduction ===
* Govnah is saving data to an array which grows over time and sucks down CPU time/memory iterating over the array.
* Use sqlite db for saving?
* To reduce disk writes, have a preference option to save to /media/ramdisk if the user is only interested in the current session for pinch zooming - should reduce disk writes and improve performance though data will be lost on boot.
* Preference setting for frequency of polling.
* Use fixed array or circular buffer instead, though this will stop pinch scrolling from going back too far (another preference option?)

=== Governor Settings ===
* Generic items (needed for all)
** scaling_max_freq - Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
** scaling_min_freq - Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
* ondemand
** sampling_rate - This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
** sampling_rate_(min|max) - This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
** up_threshold - This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
** ignore_nice_load - This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
** powersave_bias - This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page)
* conservative
** freq_step - This describes what percentage steps the CPU freq should be increased and decreased smoothly by. By default the CPU frequency will increase in 5% chunks of your maximum CPU frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor.
** down_threshold - This is same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.
* userspace
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.
* powersave
** Nothing special
* performance
** Nothing special

== Links ==
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html

Application:Govnah

2010-04-23T17:17:12Z

Jho: added to design

{{application
|name=Govnah
|type=webOS
|version=In Development
|tag=Utilities
|screenshot=Govnah_ss1.png
|description=}}

== Summary ==
{{icon|Icon_WebOSInternals_Govnah.png|float:right;}}An App to do things.

Available in the WebOS Internals Testing Feed

== Design ==
* Main Scene
** Title Header (like preware/wirc/etc webos-internals apps)
** Current Governor (Tap to go to Governor Settings)
** Current Frequency
** Misc Stats
*** ...?
*** Graph of CPU temp over time

* CPU Governor Scene
** Dropdown to change governor (SelectList)
** Form of all current settings for selected governor (dynamically generated from information provided by service)

* IO Scheduler Scene
** Dropdown to select scheduler (cfq, noop, as etc.)

* TCP Congestion Algo Scene?

* App Icon (changes to display indication of CPU temp)

=== Load Reduction ===
* Govnah is saving data to an array which grows over time and sucks down CPU time/memory iterating over the array.
* Use sqlite db for saving?
* To reduce disk writes, have a preference option to save to /media/ramdisk if the user is only interested in the current session for pinch zooming - should reduce disk writes and improve performance though data will be lost on boot.
* Preference setting for frequency of polling.
* Use fixed array or circular buffer instead, though this will stop pinch scrolling from going back too far (another preference option?)

=== Governor Settings ===
* Generic items (needed for all)
** scaling_max_freq - Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
** scaling_min_freq - Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
* ondemand
** sampling_rate - This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
** sampling_rate_(min|max) - This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
** up_threshold - This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
** ignore_nice_load - This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
** powersave_bias - This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page)
* conservative
** freq_step - This describes what percentage steps the CPU freq should be increased and decreased smoothly by. By default the CPU frequency will increase in 5% chunks of your maximum CPU frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor.
** down_threshold - This is same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.
* userspace
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.
* powersave
** Nothing special
* performance
** Nothing special

== Links ==
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm

Application:Govnah

2010-04-23T17:08:24Z

Jho: added powersave_bias

{{application
|name=Govnah
|type=webOS
|version=In Development
|tag=Utilities
|screenshot=Govnah_ss1.png
|description=}}

== Summary ==
{{icon|Icon_WebOSInternals_Govnah.png|float:right;}}An App to do things.

Available in the WebOS Internals Testing Feed

== Design ==
* Main Scene
** Title Header (like preware/wirc/etc webos-internals apps)
** Current Governor (Tap to go to Governor Settings)
** Current Frequency
** Misc Stats
*** ...?
*** Graph of CPU temp over time

* Governor Scene
** Dropdown to change governor (SelectList)
** Form of all current settings for selected governor (dynamically generated from information provided by service)

* App Icon (changes to display indication of CPU temp)

=== Load Reduction ===
* Govnah is saving data to an array which grows over time and sucks down CPU time/memory iterating over the array.
* Use sqlite db for saving?
* To reduce disk writes, have a preference option to save to /media/ramdisk if the user is only interested in the current session for pinch zooming - should reduce disk writes and improve performance though data will be lost on boot.
* Preference setting for frequency of polling.
* Use fixed array or circular buffer instead, though this will stop pinch scrolling from going back too far (another preference option?)

=== Governor Settings ===
* Generic items (needed for all)
** scaling_max_freq - Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
** scaling_min_freq - Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
* ondemand
** sampling_rate - This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
** sampling_rate_(min|max) - This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
** up_threshold - This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
** ignore_nice_load - This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
** powersave_bias - This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page)
* conservative
** freq_step - This describes what percentage steps the CPU freq should be increased and decreased smoothly by. By default the CPU frequency will increase in 5% chunks of your maximum CPU frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor.
** down_threshold - This is same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.
* userspace
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.
* powersave
** Nothing special
* performance
** Nothing special

== Links ==
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm

Patch webOS CPU Frequency or Voltage Scaling

2009-12-05T04:27:39Z

Jho: /* More Information */

{{template:patch}}
= Overview=
There are currently 2 methods to enable further power saving - neither is perfect. Note that '''these 2 methods CANNOT be used together''' so make sure you try only one solution at a time. Using both has been reported to brick your Pre, requiring a visit to the WebOS Doctor. Patches for these are now available in the gitorious repo. See [[Applying Patches]]

1 CPU Scaling
* This allows the Pre to scale the CPU clock speed up and down in response to changes in CPU utilization. Some people have reported glitching when using scaling when the CPU is under heavy load (lots of multitasking, playing video, etc).
2 SmartReflex
* This allows the Pre to vary the voltage inside the core in response to silicon characteristics, temperature, voltage, etc. This does not save that much power because it is supposed to be used along with CPU scaling to reduce voltage when the CPU is running slower, but the Pre's kernel is missing the modules to do this. This is why using both together will '''freeze''' the Palm Pre. (Remove the battery, restart with the USB plugged into your computer with NovaCom installed, During the phones boot procedure simply telnet to the phone through NovaCom's Proxy port 8023, remove the smartreflex files you installed in the events folder in /etc/ before WebOS panics)

= CPU Scaling=
== Default Setting==
Frequency scaling does not appear to be active by default on the Pre by default. The directory /sys/devices/system/cpu/cpu0/cpufreq contains information on the current state. The clock seems to be fixed at 500mHz for normal operation (according to cpuinfo_cur_freq), however several other frequencies exist:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# cat ./scaling_available_frequencies
600000 550000 500000 250000 125000
</nowiki></pre>
The file /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state shows that at some point (probably during startup) the frequency is raised to 550mHz for a short period of time.

== Enabling Scaling==
It is possible to enable frequency scaling using the 'ondemand' governor:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo ondemand > ./scaling_governor
</nowiki></pre>
this will cause the frequency to be reduced automatically while idle, and increased as needed during operation, potentially increasing battery life. Because higher frequencies may cause overheating, and TI has noted a significant decrease in the life of the processor when running above 500mHz, you should also restrict the frequency scaling to 500mHz and below by doing the following:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 500000 > ./scaling_max_freq
</nowiki></pre>
If your Pre seems sluggish after enabling scaling, you can try changing the values in /sys/devices/system/cpu/cpu0/cpufreq/ondemand as detailed below.

== 'ondemand' Configuration==
Increasing the value of 'scaling_min_freq' will prevent the CPU from going into extremely low speed configurations, which will significantly improve the responsiveness of the device when it first detects increased CPU usage, at the cost of a little bit of battery life.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 250000 > ./scaling_min_freq
</nowiki></pre>
Setting the value of 'up_threshold' lower will cause the frequency to be increased at lower levels of activity.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq/ondemand# echo 30 > ./up_threshold
</nowiki></pre>
Note: The default setting for 'up_threshold' is 80.

== Checking Performance and Stats==
To check how long your Pre has been running and at what frequency, do this:

<pre><nowiki>cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state</nowiki></pre>

You will see something like this:
<pre><nowiki>600000 906
550000 768
500000 380
250000 0
125000 180505</nowiki></pre>

The first number is the CPU frequency, the second is a time interval. In this example, my Pre has spent the most time @ 125mHz, but you can see it shoots up when needed. Note that if you are overclocking, it really doesn't spend much time at 600mHz, so overheating shouldn't be a problem, but you will definitely notice an improvement. These stats are reset after a reboot.

== Overclocking==
Overclocking is not recommended, as TI has reported a significant decrease in the life of the CPU at frequencies about 500mHz. However some users have reported better responsiveness, in addition to running cooler and using less battery while overclocking.

To overclock to the CPU's maximum speed, do:
<pre><nowiki>echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

To put it back, do:
<pre><nowiki>echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

== Making your changes stick after a reboot==
Create a file called '''cpu-scaling''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# Enables cpu scaling

start on stopped finish
stop on runlevel [!2]

console none

script
echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "30" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
end script
</nowiki></pre>

== Return to Stock Fixed Frequency==
The simple way is just to remove the '''cpu-scaling''' script from /etc/event.d (if you created it) and reboot. None of these changes are persistent without the "sticky" script shown above.

If you switch back to the 'userspace' governor without rebooting, your frequency could get stuck at a lower setting and the whole system get really bogged down. Here is a quick shell script to help you revert to userspace with the original frequency:

Copy/paste this whole line as one command:
<pre><nowiki>echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ; echo 500000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed </nowiki></pre>
Then confirm the frequency/governor are back the way you want.

== Comments and Caveats==
* "I tried this out but video playback was flickery and horrible. The up_threshold tweak setting to 30 seems to improve it a lot , but it's still flickery a bit. Some people may not be happy."

* "I found that setting the max freq to 600000 with the threshold helps this problem. See relevant warnings above first! I don't really watch video on my Pre, so it's not so big of a deal." -pEEf

* "A lot of people on the Precentral forums (myself included) are experiencing the phone locking up after a while of using this, and need to pull the battery to reset. (On webOS 1.0.3 at least.)"

* "I've been running my phone with scaling for nearly a week now without problems, but I'm not 'overlcocking' so to speak. Any specifics on what might cause the locks? (ok had my first locks tonight while attached to the touchstone, weird it never happened before now (and annoying))" -retry

* "I tried the folling over WebOSQuick Installer Linux Console: 1. root@castle: echo ondemand > ./scaling_governor 2. root@castle: echo 500000 > ./scaling_max_freq 3. root@castle: echo 125000 > ./scaling_min_freq 4. root@castle: echo 30 > ./up_threshold . But even after 7hours... nothing changed.. just used 500Mhz in Airplane mode over Night." -Ryo

= SmartReflex=
== Enable SmartReflex==
SmartReflex can be enabled in the VDD1 and VDD2 areas of the OMAP processor by setting two flags under /sys/power
<pre><nowiki>
root@castle:/sys/power# echo -n 1 > ./sr_vdd1_autocomp
root@castle:/sys/power# echo -n 1 > ./sr_vdd2_autocomp
</nowiki></pre>
[http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt This slide deck] has much of the pertinent information about SmartReflex and other power-saving technologies on the OMAP processor. Unfortunately the kernel modules that provide many of the features mentioned in the slide deck are not present on the Pre. This is the main reason that SmartReflex may not save a terribly large amount of power.

== Making your changes stick after a reboot==
To enable SmartReflex, create a file called '''smartreflex''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# -*- mode: shell-script; -*-
description "SmartReflex"
author "Alex Markson"
version 1.0

start on stopped finish
stop on runlevel [!2]

console none

script

# SmartReflex
# "SmartReflex™ driver allows for auto-compensation of VDD1 and
# VDD2 voltages (around the voltages specified by current OPP)
# by analyzing the silicon characteristics, temperature, voltage etc"
#
# Enable SmartReflex
echo -n 1 > /sys/power/sr_vdd1_autocomp
echo -n 1 > /sys/power/sr_vdd2_autocomp

end script
</nowiki></pre>

If you want to enable overclocking in addition to SmartReflex, add the following JUST BEFORE the '''end script''' line:
<pre><nowiki>
# according to the OEM shell script in /etc/miniboot.sh
# this seems like it needs to be set twice to make sure ?
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
</nowiki></pre>

== Comments and Caveats==
* "AFter using this for about a week, I find that using SmartReflex causes the Pre to stutter every so often"
* "webos 1.1 w/ no problems to start. Installed ondemand script, full 125-600mhz range, threshold 30: worked fine mostly but on the touchstone it gets hot and locks up kills battery, backlight on behind black screen, every time, within an hour. Switched to smartreflex with 600mhz, no problems, though only a few days so far and no video testing. Media player remix playing to car stereo via bluetooth is smooth." [[User:Bkw|Bkw]] 00:02, 15 September 2009 (UTC)

= Credits=
* Alex Markson for the SmartReflex find and the script.
* pEEf for numerous discoveries related to cpu scaling.
* sidamos for the info about 'up_threshold'
* garrettwp for the cpu scaling event.d script.
* Jauder Ho for gitorious patches

= Hacking=
There is still a lot of work to be done in making this work optimally. The following are some resources and thoughts.
* A paper about the ondemand governor http://www.linuxinsight.com/ols2006_the_ondemand_governor.html
* webOS 1.0.4 has CONFIG_PREEMPT set along with CONFIG_HZ=100. CONFIG_NO_HZ aka tickless is not set.
* Possible patch for NOHZ / ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html
* Use PowerTop to observe what is going on inside the Pre
* http://www.lesswatts.org/
* http://wiki.davincidsp.com/index.php/Running_PowerTOP_on_OMAP35x_platform
* TI 3430 PM presentation http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt
* CPU frequency scaling in Linux with cpufreq. Details on cpufreq parameters http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html

=More Information=
Right now this is a [slow] collection of data --A2NY

Kernel Config File:
<pre><nowiki>
cat /boot/config-2.6.24-palm-joplin-3430
</nowiki></pre>

Kernel Config Freq:
<pre><nowiki>
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
</nowiki></pre>

Enabled Governors:
<pre><nowiki>
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand userspace
</nowiki></pre>

<pre><nowiki>
ONDEMAND is also called DVFS (Dynamic Voltage & Frequency Scaling)
</nowiki></pre>

# Newer kernels apparently have an improved ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html

Kernel Config PM:
<pre><nowiki>
#
# OMAP Power Management
#

#
# Power Management Options
#
CONFIG_OMAP3_PM=y
CONFIG_OMAP_VOLT_SR_BYPASS=y
# CONFIG_OMAP_VOLT_SR is not set
# CONFIG_OMAP_VOLT_VSEL is not set
# CONFIG_OMAP_VOLT_VMODE is not set

#
# Default VDD1 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD1_OPP1 is not set
# CONFIG_OMAP3ES2_VDD1_OPP2 is not set
# CONFIG_OMAP3ES2_VDD1_OPP3 is not set
CONFIG_OMAP3ES2_VDD1_OPP4=y
# CONFIG_OMAP3ES2_VDD1_OPP5 is not set

#
# Default VDD2 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD2_OPP2 is not set
CONFIG_OMAP3ES2_VDD2_OPP3=y
# CONFIG_ENABLE_VOLTSCALE_IN_SUSPEND is not set
# CONFIG_RESET_IVA_IN_SUSPEND is not set
CONFIG_MPU_OFF=y
CONFIG_OMAP34XX_OFFMODE=y
CONFIG_CORE_OFF=y
# CONFIG_CORE_OFF_CPUIDLE is not set
CONFIG_SYSOFFMODE=y
# CONFIG_HW_SUP_TRANS is not set
# CONFIG_TRACK_RESOURCES is not set
CONFIG_AUTO_POWER_DOMAIN_CTRL=y
# CONFIG_PREVENT_MPU_RET is not set
# CONFIG_PREVENT_CORE_RET is not set
# CONFIG_DISABLE_EMUDOMAIN_CONTROL is not set
</nowiki></pre>

TWL4030:
<pre><nowiki>
/sys/devices/platform/twl4030_registers.0/module_pm_receiver
</nowiki></pre>

Kernel info:
<pre><nowiki>
+ Please note, that by default SmartReflex is only
+ initialized. To enable the automatic voltage
+ compensation for VDD1 and VDD2, user must write 1 to
+ /sys/power/sr_vddX_autocomp, where X is 1 or 2.
</nowiki></pre>

Device Startup:
<pre><nowiki>
2009-11-02T02:40:01.263122Z [15] webos kern.warning kernel: OMAP: Initializing SmartReflex subsystem...
2009-11-02T02:40:01.263549Z [15] webos kern.info kernel: OMAP: SmartReflex subsystem initialized.
2009-11-02T02:40:01.282196Z [15] webos kern.err kernel: OMAP 3430 Power Management subsystem initializing.
2009-11-02T02:40:01.292083Z [15] webos kern.info kernel: OMAP: Setting up clocks.
2009-11-02T02:40:01.319152Z [15] webos kern.warning kernel: OMAP: OPP mismatch: current/target=2:4
2009-11-02T02:40:01.319702Z [15] webos kern.info kernel: OMAP: Change MPU speed: 250 => 550 MHz
2009-11-02T02:40:01.321044Z [15] webos kern.info kernel: OMAP: ARM/DSP clock at 550/396 MHz.
2009-11-02T02:40:01.321624Z [15] webos kern.info kernel: BogoMIPS: 547.88 @550000 KHz
2009-11-02T02:40:01.327911Z [15] webos kern.info kernel: OMAP CPU idle driver initializing.
2009-11-02T02:40:01.328277Z [15] webos kern.err kernel: create_proc_entry succeeded
2009-11-02T02:40:01.342102Z [15] webos kern.info kernel: Initialize power support module
2009-11-02T02:40:01.342742Z [15] webos kern.info kernel: OMAP3: PM: Sirloin target registered successfully.
</nowiki></pre>

SR autocomp is enabled in userspace:
<pre><nowiki>
2009-11-30T17:39:39.106658Z [329] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
2009-11-30T17:39:55.827423Z [345] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
</nowiki></pre>

SR autocomp is enabled in ondemand: (device wants off, will not wake if it goes off)
<pre><nowiki>
2009-11-30T17:27:37.676910Z [7523] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
2009-11-30T17:27:45.676269Z [7531] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
</nowiki></pre>

powersave_bias http://osdir.com/ml/kernel.cpufreq/2006-07/msg00137.html
<pre><nowiki>
This patch adds a "powersave_bias" tunable to ondemand
to allow it to reduce its target frequency by a specified percent.

By default, the powersave_bias is 0 and has no effect.
powersave_bias is in units of 0.1%, so it has an effective range
of 1 through 1000, resulting in 0.1% to 100% impact.

In practice, users will not be able to detect a difference between
0.1% increments, but 1.0% increments turned out to be too large.
Also, the max value of 1000 (100%) would simply peg the system
in its deepest power saving P-state, unless the processor really has
a hardware P-state at 0Hz:-)

For example, If ondemand requests 2.0GHz based on utilization,
and powersave_bias=100, this code will knock 10% off the target
and seek a target of 1.8GHz instead of 2.0GHz until the
next sampling. If 1.8 is an exact match with an hardware frequency
we use it, otherwise we average our time between the frequency
next higher than 1.8 and next lower than 1.8.
</nowiki></pre>

Patch webOS CPU Frequency or Voltage Scaling

2009-12-05T02:57:36Z

Jho: /* Hacking */

{{template:patch}}
= Overview=
There are currently 2 methods to enable further power saving - neither is perfect. Note that '''these 2 methods CANNOT be used together''' so make sure you try only one solution at a time. Using both has been reported to brick your Pre, requiring a visit to the WebOS Doctor. Patches for these are now available in the gitorious repo. See [[Applying Patches]]

1 CPU Scaling
* This allows the Pre to scale the CPU clock speed up and down in response to changes in CPU utilization. Some people have reported glitching when using scaling when the CPU is under heavy load (lots of multitasking, playing video, etc).
2 SmartReflex
* This allows the Pre to vary the voltage inside the core in response to silicon characteristics, temperature, voltage, etc. This does not save that much power because it is supposed to be used along with CPU scaling to reduce voltage when the CPU is running slower, but the Pre's kernel is missing the modules to do this. This is why using both together will '''freeze''' the Palm Pre. (Remove the battery, restart with the USB plugged into your computer with NovaCom installed, During the phones boot procedure simply telnet to the phone through NovaCom's Proxy port 8023, remove the smartreflex files you installed in the events folder in /etc/ before WebOS panics)

= CPU Scaling=
== Default Setting==
Frequency scaling does not appear to be active by default on the Pre by default. The directory /sys/devices/system/cpu/cpu0/cpufreq contains information on the current state. The clock seems to be fixed at 500mHz for normal operation (according to cpuinfo_cur_freq), however several other frequencies exist:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# cat ./scaling_available_frequencies
600000 550000 500000 250000 125000
</nowiki></pre>
The file /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state shows that at some point (probably during startup) the frequency is raised to 550mHz for a short period of time.

== Enabling Scaling==
It is possible to enable frequency scaling using the 'ondemand' governor:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo ondemand > ./scaling_governor
</nowiki></pre>
this will cause the frequency to be reduced automatically while idle, and increased as needed during operation, potentially increasing battery life. Because higher frequencies may cause overheating, and TI has noted a significant decrease in the life of the processor when running above 500mHz, you should also restrict the frequency scaling to 500mHz and below by doing the following:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 500000 > ./scaling_max_freq
</nowiki></pre>
If your Pre seems sluggish after enabling scaling, you can try changing the values in /sys/devices/system/cpu/cpu0/cpufreq/ondemand as detailed below.

== 'ondemand' Configuration==
Increasing the value of 'scaling_min_freq' will prevent the CPU from going into extremely low speed configurations, which will significantly improve the responsiveness of the device when it first detects increased CPU usage, at the cost of a little bit of battery life.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 250000 > ./scaling_min_freq
</nowiki></pre>
Setting the value of 'up_threshold' lower will cause the frequency to be increased at lower levels of activity.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq/ondemand# echo 30 > ./up_threshold
</nowiki></pre>
Note: The default setting for 'up_threshold' is 80.

== Checking Performance and Stats==
To check how long your Pre has been running and at what frequency, do this:

<pre><nowiki>cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state</nowiki></pre>

You will see something like this:
<pre><nowiki>600000 906
550000 768
500000 380
250000 0
125000 180505</nowiki></pre>

The first number is the CPU frequency, the second is a time interval. In this example, my Pre has spent the most time @ 125mHz, but you can see it shoots up when needed. Note that if you are overclocking, it really doesn't spend much time at 600mHz, so overheating shouldn't be a problem, but you will definitely notice an improvement. These stats are reset after a reboot.

== Overclocking==
Overclocking is not recommended, as TI has reported a significant decrease in the life of the CPU at frequencies about 500mHz. However some users have reported better responsiveness, in addition to running cooler and using less battery while overclocking.

To overclock to the CPU's maximum speed, do:
<pre><nowiki>echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

To put it back, do:
<pre><nowiki>echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

== Making your changes stick after a reboot==
Create a file called '''cpu-scaling''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# Enables cpu scaling

start on stopped finish
stop on runlevel [!2]

console none

script
echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "30" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
end script
</nowiki></pre>

== Return to Stock Fixed Frequency==
The simple way is just to remove the '''cpu-scaling''' script from /etc/event.d (if you created it) and reboot. None of these changes are persistent without the "sticky" script shown above.

If you switch back to the 'userspace' governor without rebooting, your frequency could get stuck at a lower setting and the whole system get really bogged down. Here is a quick shell script to help you revert to userspace with the original frequency:

Copy/paste this whole line as one command:
<pre><nowiki>echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ; echo 500000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed </nowiki></pre>
Then confirm the frequency/governor are back the way you want.

== Comments and Caveats==
* "I tried this out but video playback was flickery and horrible. The up_threshold tweak setting to 30 seems to improve it a lot , but it's still flickery a bit. Some people may not be happy."

* "I found that setting the max freq to 600000 with the threshold helps this problem. See relevant warnings above first! I don't really watch video on my Pre, so it's not so big of a deal." -pEEf

* "A lot of people on the Precentral forums (myself included) are experiencing the phone locking up after a while of using this, and need to pull the battery to reset. (On webOS 1.0.3 at least.)"

* "I've been running my phone with scaling for nearly a week now without problems, but I'm not 'overlcocking' so to speak. Any specifics on what might cause the locks? (ok had my first locks tonight while attached to the touchstone, weird it never happened before now (and annoying))" -retry

* "I tried the folling over WebOSQuick Installer Linux Console: 1. root@castle: echo ondemand > ./scaling_governor 2. root@castle: echo 500000 > ./scaling_max_freq 3. root@castle: echo 125000 > ./scaling_min_freq 4. root@castle: echo 30 > ./up_threshold . But even after 7hours... nothing changed.. just used 500Mhz in Airplane mode over Night." -Ryo

= SmartReflex=
== Enable SmartReflex==
SmartReflex can be enabled in the VDD1 and VDD2 areas of the OMAP processor by setting two flags under /sys/power
<pre><nowiki>
root@castle:/sys/power# echo -n 1 > ./sr_vdd1_autocomp
root@castle:/sys/power# echo -n 1 > ./sr_vdd2_autocomp
</nowiki></pre>
[http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt This slide deck] has much of the pertinent information about SmartReflex and other power-saving technologies on the OMAP processor. Unfortunately the kernel modules that provide many of the features mentioned in the slide deck are not present on the Pre. This is the main reason that SmartReflex may not save a terribly large amount of power.

== Making your changes stick after a reboot==
To enable SmartReflex, create a file called '''smartreflex''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# -*- mode: shell-script; -*-
description "SmartReflex"
author "Alex Markson"
version 1.0

start on stopped finish
stop on runlevel [!2]

console none

script

# SmartReflex
# "SmartReflex™ driver allows for auto-compensation of VDD1 and
# VDD2 voltages (around the voltages specified by current OPP)
# by analyzing the silicon characteristics, temperature, voltage etc"
#
# Enable SmartReflex
echo -n 1 > /sys/power/sr_vdd1_autocomp
echo -n 1 > /sys/power/sr_vdd2_autocomp

end script
</nowiki></pre>

If you want to enable overclocking in addition to SmartReflex, add the following JUST BEFORE the '''end script''' line:
<pre><nowiki>
# according to the OEM shell script in /etc/miniboot.sh
# this seems like it needs to be set twice to make sure ?
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
</nowiki></pre>

== Comments and Caveats==
* "AFter using this for about a week, I find that using SmartReflex causes the Pre to stutter every so often"
* "webos 1.1 w/ no problems to start. Installed ondemand script, full 125-600mhz range, threshold 30: worked fine mostly but on the touchstone it gets hot and locks up kills battery, backlight on behind black screen, every time, within an hour. Switched to smartreflex with 600mhz, no problems, though only a few days so far and no video testing. Media player remix playing to car stereo via bluetooth is smooth." [[User:Bkw|Bkw]] 00:02, 15 September 2009 (UTC)

= Credits=
* Alex Markson for the SmartReflex find and the script.
* pEEf for numerous discoveries related to cpu scaling.
* sidamos for the info about 'up_threshold'
* garrettwp for the cpu scaling event.d script.
* Jauder Ho for gitorious patches

= Hacking=
There is still a lot of work to be done in making this work optimally. The following are some resources and thoughts.
* A paper about the ondemand governor http://www.linuxinsight.com/ols2006_the_ondemand_governor.html
* webOS 1.0.4 has CONFIG_PREEMPT set along with CONFIG_HZ=100. CONFIG_NO_HZ aka tickless is not set.
* Possible patch for NOHZ / ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html
* Use PowerTop to observe what is going on inside the Pre
* http://www.lesswatts.org/
* http://wiki.davincidsp.com/index.php/Running_PowerTOP_on_OMAP35x_platform
* TI 3430 PM presentation http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt
* CPU frequency scaling in Linux with cpufreq. Details on cpufreq parameters http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html

=More Information=
Right now this is a [slow] collection of data --A2NY

Kernel Config File:
<pre><nowiki>
cat /boot/config-2.6.24-palm-joplin-3430
</nowiki></pre>

Kernel Config Freq:
<pre><nowiki>
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
</nowiki></pre>

Enabled Governors:
<pre><nowiki>
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand userspace
</nowiki></pre>

<pre><nowiki>
ONDEMAND is also called DVFS (Dynamic Voltage & Frequency Scaling)
</nowiki></pre>

Kernel Config PM:
<pre><nowiki>
#
# OMAP Power Management
#

#
# Power Management Options
#
CONFIG_OMAP3_PM=y
CONFIG_OMAP_VOLT_SR_BYPASS=y
# CONFIG_OMAP_VOLT_SR is not set
# CONFIG_OMAP_VOLT_VSEL is not set
# CONFIG_OMAP_VOLT_VMODE is not set

#
# Default VDD1 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD1_OPP1 is not set
# CONFIG_OMAP3ES2_VDD1_OPP2 is not set
# CONFIG_OMAP3ES2_VDD1_OPP3 is not set
CONFIG_OMAP3ES2_VDD1_OPP4=y
# CONFIG_OMAP3ES2_VDD1_OPP5 is not set

#
# Default VDD2 OPP Level Selection
#
# CONFIG_OMAP3ES2_VDD2_OPP2 is not set
CONFIG_OMAP3ES2_VDD2_OPP3=y
# CONFIG_ENABLE_VOLTSCALE_IN_SUSPEND is not set
# CONFIG_RESET_IVA_IN_SUSPEND is not set
CONFIG_MPU_OFF=y
CONFIG_OMAP34XX_OFFMODE=y
CONFIG_CORE_OFF=y
# CONFIG_CORE_OFF_CPUIDLE is not set
CONFIG_SYSOFFMODE=y
# CONFIG_HW_SUP_TRANS is not set
# CONFIG_TRACK_RESOURCES is not set
CONFIG_AUTO_POWER_DOMAIN_CTRL=y
# CONFIG_PREVENT_MPU_RET is not set
# CONFIG_PREVENT_CORE_RET is not set
# CONFIG_DISABLE_EMUDOMAIN_CONTROL is not set
</nowiki></pre>

TWL4030:
<pre><nowiki>
/sys/devices/platform/twl4030_registers.0/module_pm_receiver
</nowiki></pre>

Kernel info:
<pre><nowiki>
+ Please note, that by default SmartReflex is only
+ initialized. To enable the automatic voltage
+ compensation for VDD1 and VDD2, user must write 1 to
+ /sys/power/sr_vddX_autocomp, where X is 1 or 2.
</nowiki></pre>

Device Startup:
<pre><nowiki>
2009-11-02T02:40:01.263122Z [15] webos kern.warning kernel: OMAP: Initializing SmartReflex subsystem...
2009-11-02T02:40:01.263549Z [15] webos kern.info kernel: OMAP: SmartReflex subsystem initialized.
2009-11-02T02:40:01.282196Z [15] webos kern.err kernel: OMAP 3430 Power Management subsystem initializing.
2009-11-02T02:40:01.292083Z [15] webos kern.info kernel: OMAP: Setting up clocks.
2009-11-02T02:40:01.319152Z [15] webos kern.warning kernel: OMAP: OPP mismatch: current/target=2:4
2009-11-02T02:40:01.319702Z [15] webos kern.info kernel: OMAP: Change MPU speed: 250 => 550 MHz
2009-11-02T02:40:01.321044Z [15] webos kern.info kernel: OMAP: ARM/DSP clock at 550/396 MHz.
2009-11-02T02:40:01.321624Z [15] webos kern.info kernel: BogoMIPS: 547.88 @550000 KHz
2009-11-02T02:40:01.327911Z [15] webos kern.info kernel: OMAP CPU idle driver initializing.
2009-11-02T02:40:01.328277Z [15] webos kern.err kernel: create_proc_entry succeeded
2009-11-02T02:40:01.342102Z [15] webos kern.info kernel: Initialize power support module
2009-11-02T02:40:01.342742Z [15] webos kern.info kernel: OMAP3: PM: Sirloin target registered successfully.
</nowiki></pre>

SR autocomp is enabled in userspace:
<pre><nowiki>
2009-11-30T17:39:39.106658Z [329] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
2009-11-30T17:39:55.827423Z [345] webos kern.info kernel: Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
</nowiki></pre>

SR autocomp is enabled in ondemand: (device wants off, will not wake if it goes off)
<pre><nowiki>
2009-11-30T17:27:37.676910Z [7523] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
2009-11-30T17:27:45.676269Z [7531] webos kern.info kernel: Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
</nowiki></pre>

Applying Patches

2009-09-29T05:36:22Z

Jho: remove the removal of ncurses as psmisc and hence dropbear depends on it

==Introduction==

We cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license) therefore we need to manage our modifications as patches. Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied after-wards, we need a procedure and tools for doing this. This page documents this procedure.

Before asking questions about this procedure, please read the following documents fully:

An introduction to Quilt can be found at http://www.suse.de/~agruen/quilt.pdf

The manual for quilt is at http://linux.die.net/man/1/quilt

==Upgrading from quilt to quilt-lite==

If you have performed these instructions before the 8th Aug 2009, you will have installed a very heavyweight version of the quilt package which has a dependency on a very large perl package.

This dependency has been removed in a new quilt-lite package, which saves 26MB of space in /var as a result.

You can switch over to it as follows:

* ipkg-opt update
* ipkg-opt remove quilt perl libdb gdbm util-linux-ng e2fslibs ncursesw
* ipkg-opt install quilt-lite

Alternatively, the setup script below will prompt to uninstall quilt, perl, etc ..., and install quilt-lite, if quilt is installed.

==Setup Procedure (Scripted)==
The process of setting up quilt has been scripted. The script performs the following actions:
* Installs (or upgrades) git and any dependencies
* Installs (or upgrades) quilt (actually quilt-lite, a version of quilt that does not depend on perl) and any dependencies
* Configures quilt to store patches in /opt/src/patches
* Creates (or updates) a local clone of the webos-internals modifications repository

Each step is only performed if necessary. Please note that ipkg-opt needs to be installed. The instructions are found [[Next_steps|here]].

To get run the script, log into your Pre, gain root privileges and run the following commands:
<pre><nowiki>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</nowiki></pre>

==Setup Procedure (Manual Process)==
(Note: Even though you may have previously installed the optware quilt patch manager, it won't damage anything to follow the Setup procedure. Alternatively, if you KNOW FOR SURE these are installed and your packages are up-to-date, you can skip to Importing and Applying Patches).

* Log into your Pre, and gain root privileges. (Note: This command is not required when using the emulator)
<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode
<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt-lite' package, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt-lite git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:
<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:
<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Delete any existing webos-internals modifications directories
<pre><nowiki>
rm -rf /opt/src/modifications
</nowiki></pre>

* Clone the webos-internals modifications repository:
<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

==Importing and Applying Patches==

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>
** If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

** Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.
<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
# Use this to push all patches at once.
quilt push -a
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

==Listing Applied Patches==
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt applied
</nowiki></pre>

==Removing All Patches==

Before you accept an over-the-air (OTA) update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

==Reapplying all patches==

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

==Information for developing patches==

===Getting Authenticated with gitorious.org===
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next you'll need to generate a public key and share that with gitorious.org, your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.

Getting your key on window
* Download [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

* To commit changes to gitorious.org from the pre you will need to install openssh on the device.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # since dropbear doesn't do agent forwarding, you need to use openssh
</nowiki></pre>

Actually, it is possible to use dropbear with git but requires [http://tumblelog.jauderho.com/post/151678345/using-dropbear-with-git some hackery].

As an alternative, if you don't use the keys for anything else you could just generate them on the pre after installing open-ssh
<pre><nowiki>
sudo ssh-keygen -t rsa # follow the prompts
cat ~/.ssh/id_rsa.pub # display the public key you need to paste into gitorious
</nowiki></pre>

* Don't forget to upload your public key to gitorious.org after generating it.
Now you should be able to follow the steps below and contribute your code to gitorious.org.

* If you find yourself getting errors about your public key when you try to push changes, check to make sure your keys are under /var/home/root/.ssh/ and not under your regular user account.

===Creating a patch===

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

===Pushing the change back to gitorious.org===

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

==Extended, annotated sample session with quilt==
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create '''before''' you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

==Background info==

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

==Script for Updating/Installing Patches==

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
#!/opt/bin/bash

cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>

Application:Preware

2009-08-27T17:16:09Z

Jho: added update instructions

{{application
|name=Preware
|type=webOS
|version=Version: Alpha 0.7.4 <br />(26 Aug 2009)
|tag=Utilities
|screenshot=Application_Preware_List.png
|description=

== Summary ==
{{icon|Icon_Preware.png|float:right;}}
Preware is a package management application for the Palm Pre. Preware allows the user to install any package from any of the open standard package repositories on preware.org (or any other location that hosts an open standard package repository). Preware relies on a custom written service developed from community research which allows the mojo app to talk to the built-in ipkg tool.

This application was the result of extensive community-based design in [[IPKG Service]] and [[Preware Design]].

For application management, Preware can access more applications, and has more features, than any other on-device package installer.

And since it is open source, and has a completely open development process supported by a team of world-class WebOS Internals developers, it will continue to get better much faster than any other package management application.

Preware is the open application installer that has been written specifically to support a homebrew ecosystem where any developer can upload any application to any submission site, and that application can then be installed by any user. Developers no longer need to upload their applications to multiple submission sites, and users are no longer excluded from accessing applications from any open standard package repository.

== Status ==

This is alpha software. Even so, it is at least as useful for managing applications as any of the other application installer utilities.

== License ==

Please be aware that org.webosinternals.preware and org.webosinternals.ipkgservice are licensed under the GPLv2.

They cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the authors.

== Operating notes ==

=== Recent enhancements ===

0.7.4: Fixed remounting of root filesystem for post-install and pre-remove scripts on the Pre.

0.7.1: Fixed buttons and title on script view screen.

0.7.0: Initial support for post-install and pre-remove scripts, including secure informed user consent. Does not work properly with dependencies yet, so please install dependencies one at a time.

0.6.7: Fixed bug in category drop-down list.

0.6.6: Fixed bug in package size reporting.

0.6.5: Updated icon and other graphical annotations.

0.6.4: Categories drop-down bug fixed. Preware category updated.

0.6.2: Categories now work to some extent. Still a bug in the dropdown box.

0.6.1: Sorting by name or date is now available. Application details screen is much more organised.

0.6.0: No user visible changes. Preparation for the secure informed user consent functionality.

0.5.1: Filtering is now available on the list screens. Just start typing ...

=== Limitations ===

The Package Management Service does not yet fully handle postinst and prerm files (initial support is in alpha testing, but dependency handling for postinst and prerm still has to be added), so you will need to continue to use the [http://forums.precentral.net/homebrew-apps/194832-webos-quick-install.html WebOS Quick Install] tool to install advanced webos-internals packages that require commands to be run as the root user upon installation and removal. This limitation will be removed before the 1.0.0 release, and Preware will then be able to install any webOS application - even those that previously required root access.

=== Known bugs ===

No known bugs.

== Installation ==

You do not need to access the Linux command line or "root your Pre" to install or use Preware.

Note that you *must* use version 2.01 or later of WebOS Quick Install. Verision 2.0 had a bug which causes the installation of the Package Management Service to fail, and Preware then hangs on the initial "Updating" screen. A reinstallation with version 2.01 should fix that.

Please use the [http://forums.precentral.net/homebrew-apps/194832-webos-quick-install.html WebOS Quick Install] tool to install the Package Manager Service and the Preware application. You can find both of these in the WebOS Internals feed. Make sure you install the Package Manager Service first and the Preware application second, otherwise you will need to reboot your Pre after installation. Do *NOT* install anything else at the same time as the service.

No other application installer tool is sophisticated enough to install the custom Package Manager Service that Preware requires.

Note that Preware works just as well on the Emulator as it does on a real device, and is installed in exactly the same way.

=== Updating ===

Follow the removal instructions below, then repeat the installation instructions above. Preware will be able to update itself after the 1.0.0 version is released.

=== Removal ===

Please use the [http://forums.precentral.net/homebrew-apps/194832-webos-quick-install.html WebOS Quick Install] tool to remove Preware and the Package Manager Service (in that order).

== Repository ==

Preware is housed in the Applications section of the WebOS Internals git repository at http://gitorious.org/webos-internals/applications

Source code for the Mojo app can be browsed at http://gitorious.org/webos-internals/applications/trees/master/preware

Source code for the service can be browsed at http://gitorious.org/webos-internals/applications/trees/master/ipkgservice

For commit permission to the project, contact rwhitby on #webos-internals or email [[mailto:support@webos-internals.org support@webos-internals.org]]

== Alternative Installation (ADVANCED/CLI Method)==
This method is for '''LINUX EXPERTS ONLY''' and depends on the ipkg.preware.org/feeds/webos-internals repository. '''If you've already install [[Application:Terminal]] then please SKIP the first steps.'''

=== Setting up the repository ===
<source lang="text">
sudo su
mount -o remount,rw /
mkdir -p /var/etc/ipkg/
ln -s /etc/ipkg/arch.conf /var/etc/ipkg/
echo "src/gz all http://ipkg.preware.org/feeds/webos-internals/all" > /var/etc/ipkg/preware.conf
echo "src/gz armv7 http://ipkg.preware.org/feeds/webos-internals/armv7" >> /var/etc/ipkg/preware.conf
</source>

=== Installing via IPKG ===

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var install org.webosinternals.ipkgservice
/usr/bin/ipkg -o /var install org.webosinternals.preware
sh /var/usr/lib/ipkg/info/org.webosinternals.ipkgservice.postinst
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

mount -o remount,ro /
exit
</source>

=== Updating via IPKG ===

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var upgrade
sh /var/usr/lib/ipkg/info/org.webosinternals.ipkgservice.postinst
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

mount -o remount,ro /
exit
</source>

}}

EBook-Reader

2009-08-15T02:49:15Z

Jho: /* Data Structure */

===Application description from a users perspective ===
Scene 1: Splash image and 3 buttons: [[Image: Scene1.png|thumb|right]]

.. Where I left off ... -- Opens the last book you read at the place you stopped.

.. Bookmarks ... -- opens a list of the books you have bookmarks in and lets you open them to there. -- previews 2 lines above and below bookmark.

... Library ... -- opens a scrollable page of "shelves" Each shelf has a label which is user defined, and each shelf presents the books on it as a coverflow. Books can be moved between shelves by dragging and dropping. Each shelf has a context menu to control order, title, author or user defined. If user defined menu will present shelf as a draggable list instead of a coverflow when you want to re-order books. backswipe returns to coverflow.

in either the bookmarks view, tapping a book takes you to either the bookmark or the title page. upswipe downswipe provide smooth scrolling. Left and right swipe provide page at a time scrolling. Back swipe in gesture offers to bookmark with a dialog and returns to the shelf you came from.

When on a book, top left menu presents presentation options, which can be set book by book or globally. Type face (if I can figure out how), size, leading, justification, colors etc..

Images default to no larger than 1/4 screen, but touch results in lightbox like zoom.

Menu at splash or library offers import, and delete of books. When in a shelf, books can be deleted by dragging them to the recycle.

===Features Wish List===
# on-pc conversion of various formats to pre-compatible format -probably using plucker distiller. Should support
## html
## rde
## doc
## m4b
## pdb (palm-doc)
## pdb (isilo), prc (unencrypted mobipocket)
## prc (encrypted) # lots of people with a ton of fictionwise books want this
## epub [http://en.wikipedia.org/wiki/EPUB]
## plain text
## plucker
## .lit
# on Pre conversion of html and text docs by download from the cloud.
# Library supports user definable catagories for sorting and shelving
#: Shelves can be user defined to hold any collection of books a reader cares to:
#* By author
#* By Genre
#* By Geography
#* By cover color
#* By Series # very useful to group books in a series together
#: The ''user'' should define the sorting catagories. Shelf design can initially be a scroll list like the Contacts app.
# Book display page is minimally invasive making the most space available to read on as possible
# Typography is bifocal friendly. User definable print sizes, and if possible type faces.
# user defined foreground/background colors for text.
## Sepia
## Night mode
## Adjust screen brightness
# multiple bookmarks per doc.
# shallow menus
# smooth scrolling or page-at-a-time scrolling by gestures.
## plucker style button-based scrolling
## swipe gesture based scrolling
## auto-scrolling with user adjustable speed
### Pause auto-scrolling by tapping gesture area
# support for covers.
# coverflow view of shelves.
# easy rapid sorting of books onto shelves.
# Change text size
# Possibly be able to add books over Wi-Fi
# Copy & Paste words
## Dictionary search implemented

===Data Structure===

'''Table: Catalog'''
* catalogId: (globally unique ID - a system generated number)
* Title: string
* Author: string
* Genre: string
* catalogType: (B,S - book or series)
* ShelfId:
* CoverImage: Filename
* Encrypted: boolean
* Format: string (book format)

'''Table: BookSeries'''
* bookseriesId: (globally unique ID - a system generated number)
* catSeriesId: (must be present in book table and the catType must be 'S')
* catBookId: (must be present in book table and the catType must be 'B')

'''Table: Bookmarks'''
* bkmkId:
* bookId: (must be present in book table)
* Position: ( an integer, refering to the character in the file at the top of the screen.)

'''Table: BookShelf'''
* shelfId:
* ShelfName:
* ShelfOrder: (A, T, or U) Representing Author, Title or User Set

'''Table ShelfOrder'''
* shelfId:
* bookId:
* position: (integer representing the position of this book on this shelf)

'''Table: BookText'''
* BookId:
* BookText:

====Data Issues====

* This structure does not provide for books stored as chapters. This structure presumes a book is a single document. That document might have internal chapter indicators, but this structure does not divide the book up.
* This structure makes no provision for the internal storage of images.
* Should we actually store the text of the book in the DB or do we leave the book on the file system and just store a link to it?

There is some point, therefore to consider if in booktext, we want to simply store a plucker file, which CAN contain images and text intermingled.

====Book Format Issues====
* Can javascript on the device natively parse/navigate all of the above list formats?
** '''No.'''
* Can javascript on the device effectively parse/navigate the plucker format (if we settle on this one), or do we need our own format?
** '''Perhaps.''' plucker decoding sources in JAVA at http://www.fbreader.org/downloads.php
** Possible ePub since it's basically XHTML?
* Once we settle on a format, will the device be powerful enough to convert other formats to this one, or will we need a PC app to do the converting?
** on pc app
** some scripts found so far: ereader2html, pdbshred
** (include others as you find them)
* Has anyone found a free and open source method to unzip files or data streams in javascript??
** all i have found is a page that refers to the huffman compression technique (http://rumkin.com/tools/compression/compress_huff.php), but i don't know if that is how epub files are zipped and i don't know if we can get our hands on the source.

EBook-Reader

2009-08-13T06:11:23Z

Jho: /* Features Wish List */

===Application description from a users perspective ===
Scene 1: Splash image and 3 buttons:

.. Where I left off ... -- Opens the last book you read at the place you stopped.

.. Bookmarks ... -- opens a list of the books you have bookmarks in and lets you open them to there. -- previews 2 lines above and below bookmark.

... Library ... -- opens a scrollable page of "shelves" Each shelf has a label which is user defined, and each shelf presents the books on it as a coverflow. Books can be moved between shelves by dragging and dropping. Each shelf has a context menu to control order, title, author or user defined. If user defined menu will present shelf as a draggable list instead of a coverflow when you want to re-order books. backswipe returns to coverflow.

in either the bookmarks view, tapping a book takes you to either the bookmark or the title page. upswipe downswipe provide smooth scrolling. Left and right swipe provide page at a time scrolling. Back swipe in gesture offers to bookmark with a dialog and returns to the shelf you came from.

When on a book, top left menu presents presentation options, which can be set book by book or globally. Type face (if I can figure out how), size, leading, justification, colors etc..

Images default to no larger than 1/4 screen, but touch results in lightbox like zoom.

Menu at splash or library offers import, and delete of books. When in a shelf, books can be deleted by dragging them to the recycle.

===Features Wish List===
# on-pc conversion of various formats to pre-compatible format -probably using plucker distiller. Should support
## html
## rde
## doc
## pdb (palm-doc)
## pdb (isilo), prc (unencrypted mobipocket)
## prc (encrypted) # lots of people with a ton of fictionwise books want this
## epub [http://en.wikipedia.org/wiki/EPUB]
## plain text
## plucker
# on Pre conversion of html and text docs by download from the cloud.
# Library supports user definable catagories for sorting and shelving
#: Shelves can be user defined to hold any collection of books a reader cares to:
#* By author
#* By Genre
#* By Geography
#* By cover color
#* By Series # very useful to group books in a series together
#: The ''user'' should define the sorting catagories. Shelf design can initially be a scroll list like the Contacts app.
# Book display page is minimally invasive making the most space available to read on as possible
# Typography is bifocal friendly. User definable print sizes, and if possible type faces.
# user defined foreground/background colors for text.
## Night mode
# multiple bookmarks per doc.
# shallow menus
# smooth scrolling or page-at-a-time scrolling by gestures.
## plucker style button-based scrolling
## swipe gesture based scrolling
## auto-scrolling with user adjustable speed
# support for covers.
# coverflow view of shelves.
# easy rapid sorting of books onto shelves.

===Data Structure===

'''Table: Catalog'''
Title: string
Author: string
Shelfguid:
CoverImage: Filename
guid: (globally unique ID - a system generated number)

'''Table: Bookmarks'''
guid:
Position: ( an integer, refering to the character in the file at the top of the screen.)

'''Table: Shelves'''
guid:
ShelfName:
Shelving Order: (A, T, or U) Representing Author, Title or User Set

'''Table ShelfOrder'''
Shelfguid:
Bookguid:
Position: (integer representing the position of this book on this shelf)

'''Table: BookText'''
BookGuid:
BookText:

====Data Issues====

* This structure does not provide for books stored as chapters. This structure presumes a book is a single document. That document might have internal chapter indicators, but this structure does not divide the book up.
* This structure makes no provision for the internal storage of images.

There is some point, therefore to consider if in booktext, we want to simply store a plucker file, which CAN contain images and text intermingled.

Talk:EBook-Reader

2009-08-13T06:08:24Z

Jho: add commentary

I do not really care for coverflow (as it might slow things down). What I would love is an effective, bare bones way to read books. I am still using the treo 700p to read books via ereader.

Next, the cloud thing can be deferred. the shortcovers app is very bad IMO and I tend to read books where network access may not be possible i.e. plane, train etc.

EBook-Reader

2009-08-13T06:06:06Z

Jho: /* Features Wish List */

===Application description from a users perspective ===
Scene 1: Splash image and 3 buttons:

.. Where I left off ... -- Opens the last book you read at the place you stopped.

.. Bookmarks ... -- opens a list of the books you have bookmarks in and lets you open them to there. -- previews 2 lines above and below bookmark.

... Library ... -- opens a scrollable page of "shelves" Each shelf has a label which is user defined, and each shelf presents the books on it as a coverflow. Books can be moved between shelves by dragging and dropping. Each shelf has a context menu to control order, title, author or user defined. If user defined menu will present shelf as a draggable list instead of a coverflow when you want to re-order books. backswipe returns to coverflow.

in either the bookmarks view, tapping a book takes you to either the bookmark or the title page. upswipe downswipe provide smooth scrolling. Left and right swipe provide page at a time scrolling. Back swipe in gesture offers to bookmark with a dialog and returns to the shelf you came from.

When on a book, top left menu presents presentation options, which can be set book by book or globally. Type face (if I can figure out how), size, leading, justification, colors etc..

Images default to no larger than 1/4 screen, but touch results in lightbox like zoom.

Menu at splash or library offers import, and delete of books. When in a shelf, books can be deleted by dragging them to the recycle.

===Features Wish List===
# on-pc conversion of various formats to pre-compatible format -probably using plucker distiller. Should support
## html
## rde
## doc
## pdb (palm-doc)
## pdb (isilo), prc (unencrypted mobipocket)
## prc (encrypted) # lots of people with a ton of fictionwise books want this
## epub [http://en.wikipedia.org/wiki/EPUB]
## plain text
## plucker
# on Pre conversion of html and text docs by download from the cloud.
# Library supports user definable catagories for sorting and shelving
#: Shelves can be user defined to hold any collection of books a reader cares to:
#* By author
#* By Genre
#* By Geography
#* By cover color.
#: The ''user'' should define the sorting catagories.
# Book display page is minimally invasive making the most space available to read on as possible
# Typography is bifocal friendly. User definable print sizes, and if possibletype faces.
# user defined forground/background colors for text.
## Night mode
# multiple bookmarks per doc.
# shallow menus
# smooth scrolling or page-at-a-time scrolling by gestures.
## plucker style button-based scrolling
## swipe gesture based scrolling
## auto-scrolling with user adjustable speed
# support for covers.
# coverflow view of shelves.
# easy rapid sorting of books onto shelves.

===Data Structure===

'''Table: Catalog'''
Title: string
Author: string
Shelfguid:
CoverImage: Filename
guid: (globally unique ID - a system generated number)

'''Table: Bookmarks'''
guid:
Position: ( an integer, refering to the character in the file at the top of the screen.)

'''Table: Shelves'''
guid:
ShelfName:
Shelving Order: (A, T, or U) Representing Author, Title or User Set

'''Table ShelfOrder'''
Shelfguid:
Bookguid:
Position: (integer representing the position of this book on this shelf)

'''Table: BookText'''
BookGuid:
BookText:

====Data Issues====

* This structure does not provide for books stored as chapters. This structure presumes a book is a single document. That document might have internal chapter indicators, but this structure does not divide the book up.
* This structure makes no provision for the internal storage of images.

There is some point, therefore to consider if in booktext, we want to simply store a plucker file, which CAN contain images and text intermingled.

Applying Patches

2009-07-30T06:53:57Z

Jho: /* Getting Authenticated with gitorious.org */

==Introduction==

We cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license) therefor we need to manage our modifications as patches. Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied after-wards, we need a procedure and tools for doing this. This page documents this procedure.

==Setup Procedure (Scripted)==
The process of setting up quilt has been scripted. The script performs the following actions:
* Installs (or upgrades) git and any dependencies
* Installs quilt (or upgrades) and any dependencies
* Configures quilt to store patches in /opt/src/patches
* Creates (or updates) a local clone of the webos-internals modifications repository

Each step is only performed if necessary. Please note that ipkg-opt needs to be installed. The instructions are found [[Next_steps|here]].

To get run the script, log into your Pre, gain root privileges and run the following commands:
<pre><nowiki>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</nowiki></pre>

==Setup Procedure (Manual Process)==
(Note: Even though you may have previously installed the optware quilt patch manager, it won't damage anything to follow the Setup procedure. Alternatively, if you KNOW FOR SURE these are installed and your packages are up-to-date, you can skip to Importing and Applying Patches).

* Log into your Pre, and gain root privileges. (Note: This command is not required when using the emulator)
<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode
<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt packages, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:
<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:
<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Clone the webos-internals modifications repository:
<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

==Importing and Applying Patches==

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>
** If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

** Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.
<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
# Use this to push all patches at once.
quilt push -a
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

==Removing all patches==

Before you accept an OTA update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

==Reapplying all patches==

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

==Information for developing patches==

===Getting Authenticated with gitorious.org===
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next you'll need to generate a public key and share that with gitorious.org, your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.

Getting your key on windows
* Download [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

* To commit changes to gitorious.org from the pre you will need to install openssh on the device.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # since dropbear doesn't do agent forwarding, you need to use openssh
</nowiki></pre>

Actually, it is possible to use dropbear with git but requires [http://tumblelog.jauderho.com/post/151678345/using-dropbear-with-git some hackery].

As an alternative, if you don't use the keys for anything else you could just generate them on the pre after installing open-ssh
<pre><nowiki>
sudo ssh-keygen -t rsa # follow the prompts
cat ~/.ssh/id_rsa.pub # display the public key you need to paste into gitorious
</nowiki></pre>

* Don't forget to upload your public key to gitorious.org after generating it.
Now you should be able to follow the steps below and contribute your code to gitorious.org.

* If you find yourself getting errors about your public key when you try to push changes, check to make sure your keys are under /var/home/root/.ssh/ and not under your regular user account.

===Creating a patch===

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

===Pushing the change back to gitorious.org===

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

==Extended, annotated sample session with quilt==
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create '''before''' you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

==Background info==

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

==Script for Updating/Installing Patches==

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>