http://wiki.webos-internals.org/api.php?action=feedcontributions&user=SmartDeviceResource1&feedformat=atomWebOS Internals - User contributions [en]2024-03-28T18:01:00ZUser contributionsMediaWiki 1.35.1http://wiki.webos-internals.org/index.php?title=Application_talk:ThemeManager&diff=21467Application talk:ThemeManager2012-01-19T20:29:35Z<p>SmartDeviceResource1: </p>
<hr />
<div>I have added links to the four families of currently compatible theme manager themes. I've added them to the resources section under the developer information as I was not sure of another location. Also two of the links are direct download (Sketch's PalmOS theme) it'd be nice if we could have a bit of a buffer (not sure if direct linking follows strict guidelines for this site as this was my first major edit)<br />
Thanks Rod :) @nergal2</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:ThemeManager&diff=21465Application:ThemeManager2012-01-19T20:26:10Z<p>SmartDeviceResource1: /* Glass Themes by Garrett */</p>
<hr />
<div><div style='position: relative;'><br />
{{application<br />
|name=Theme Manager<br />
|version=0.8.1<br />
|type=webOS<br />
|tag=Utilities<br />
|screenshot=theme_manager.png<br />
|description=<div style='position: absolute; bottom: 0; right: 0; padding-right: 28px; padding-bottom: 16px'>{{SconixDonation}}</div><br />
}}<br />
</div><br />
<br />
== Overview == <br />
[[image:Icon_Theme-Manager.png|frameless|left]]<br />
Theme Manager is a webOS ''(2.1+ w/Enyo installed)'' application that brings theme support to your device. Using Theme Manager, you will be able to browse locally downloaded themes and apply them to your device.<br /><br /><br />
<br />
<br />
== Installation == <br />
<br />
The following information will help you install Theme Manager.<br />
<br />
<br />
==== Overview ====<br />
<blockquote><br />
<span style="color:#8a0002">'''Stable Releases'''</span><br />
<br /><br />
The stable releases of Theme Manager can be found in the WebOS-Internals feed and are recommended for general public use.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Alpha/Beta Releases'''</span><br />
<br /><br />
The alpha/beta releases of Theme Manager can be found in the the WebOS-Internals Alpha or Beta feeds [http://www.webos-internals.org/wiki/Testing_Feeds WebOS-Internals Testing Feed].<br />
</blockquote><br />
<br />
<br />
==== Method ====<br />
<br />
The following method can be used to install Theme Manager.<br />
<br />
<br />
<blockquote><br />
===== [http://www.webos-internals.org/wiki/Application:Preware Preware] =====<br />
<br />
# Open Preware<br />
# Start typing “Theme Manager” (no quotes)<br />
# Tap the Theme Manager from the list<br />
# Tap the Install button<br />
# Restart your device ''(optional, but recommended)''<br />
<br />
'''Or'''<br />
<br />
# Open Preware<br />
# Tap Available Packages<br />
# Tap Application > System Utilities > Theme Manager<br />
# Tap the Install button<br />
# Tap the Ok button to restart Luna<br />
</blockquote><br />
<br />
<br />
==== Updating ====<br />
<br />
<blockquote><br />
===== <span style="color:#8a0002">webOS OTA Updates</span> =====<br />
Since Theme Manager is an app, it is OTA (over-the-air) update safe. When there is an OTA update to a newer version of webOS from your carrier/HP, you do not need to remove the app before updating. Themes applied with Theme Manager are also OTA safe. After an OTA update, you must re-apply the theme. '''Before applying a new OTA update, you might want to make sure that the themes you use are supported on the new webOS version.'''<br />
<br />
<br />
===== <span style="color:#8a0002">Application Updates</span> =====<br />
Updated versions of Theme Manager can be applied via Preware.<br />
</blockquote><br />
<br />
<br />
== Usage ==<br />
<br />
==== Adding Themes to your Device ====<br />
Theme Manager compatible themes come in two types: ZIP and IPK. Themes need to be added to your device before they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
To add a ZIP theme to your device, save the ZIP package to the Downloads folder on the USB partition of your device.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
To add an IPK theme to your device, save the IPK package to the USB partition of your device.<br />
</blockquote><br />
<br />
<br />
==== Installing Themes to the Theme Library ====<br />
Once themes are added to your device, they must be installed into the Theme Library so they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
#Tap Theme Library<br />
#Tap Install New Themes<br />
#Tap one or multiple ZIP themes in the file picker<br />
#Tap Ok<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
#Install the IPK package with Preware<br />
::''Note: If you have Theme Manager already open, you'll need to rescan for the newly installed theme(s).''<br />
::#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
::#Tap Theme Library<br />
::#Tap Re-Scan All Themes<br />
</blockquote><br />
<br />
<br />
====Applying your Theme(s) ====<br />
Now that you have your theme(s) added to your device and installed in the Theme Library, you can start applying the themes or various components from many themes to your device. '''''(NOTE: Be sure to remove any previous "non supported/non Theme Manager" themes prior to applying new themes with Theme Manager!)'''''<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''Applying A Complete Theme'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish to apply.<br />
# Tap the Select This Theme button<br />
# Tap the Apply Current Theme button<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Selecting Various Components From Many Themes'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish you select components from<br />
# Scroll down to and tap the Theme Components section<br />
# Tap the checkbox to select the components you wish to apply<br />
# Tap the Select Components button ''(Note: Repeat the above steps to select components from other themes before you apply the custom theme.)''<br />
# Tap the Apply Current Theme button<br />
</blockquote><br />
<br />
<br />
== Making Themes ==<br />
<br />
<blockquote><br />
First you should create a directory for your theme and you should name it in the following style to avoid any conflict with other themes: com.domain.theme-name (e.g. org.webosinternals.simple-test-theme). Even the theme can be set to support different devices you should make separate theme for different types of devices, i.e. most likely nobody wants to have files for TouchPad installed in his phone for example.<br><br />
<br><br />
The hierarchy inside of that directory is free but the example below uses following hierarchy (the theme.json file is the only one required and has to be named as theme.json):<br><br />
<br><br />
<pre><br />
org.webosinternals.simple-test-theme/<br />
data/<br />
images/<br />
patches/<br />
sounds/<br />
theme.json<br />
</pre><br />
<br><br />
Then the contents of the theme.json file is as below. The optional stuff if not used can be left out. You should make sure that the file contains valid json, i.e. don't use tabs or make typos :). Also you should leave out the comments.<br><br />
<br><br />
<pre><br />
{<br />
"name": "Theme Name", // Mandatory<br />
"version": "1.0.0", // Mandatory<br />
<br />
"description": "Description for the theme.", // Mandatory<br />
<br />
"creator": "Authors Name", // Mandatory<br />
"website": "", // Mandatory but can be left empty<br />
<br />
"donations": "", // Optional donation link<br />
<br />
"devices": [<br />
// Mandatory list of supported devices, valid devices are<br />
// emulator, touchpad, veer, pre3, pre (= pre,pre+,pre2)<br />
<br />
"emulator",<br />
"touchpad"<br />
],<br />
<br />
"screenshots": [ <br />
// Mandatory, at least one screenshot is required<br />
<br />
"data/default-view.png"<br />
],<br />
<br />
"themedata": { <br />
// Mandatory, different data can be set for different webOS versions, <br />
// every supported version must be listed, the components that does <br />
// not exist in the theme should be removed. Components can contain <br />
// images, sounds and patches.<br />
<br />
// Allowed files at the moment are, images: jpg/png, sounds: mp3/wav <br />
// and only files that can be patched are css files.<br />
<br />
"3.0.0": {<br />
// You can refer to other version with alias if the version is <br />
// compatible. At the moment if they differ even the slightest<br />
// amount you need to create new set, i.e. after alias you can<br />
// not set any "overrides" at the moment.<br />
<br />
"alias": "3.0.2"<br />
},<br />
"3.0.2": {<br />
// Path is always the path in the device and the file path to<br />
// to the file inside the theme directory.<br />
<br />
"app_icons": {<br />
"images": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.phone/icon.png",<br />
"file": "images/icon-phone.png"<br />
}<br />
]<br />
},<br />
"app_launcher": {<br />
"images": [<br />
{<br />
"path": "/usr/lib/luna/system/luna-applauncher/images/bg.png",<br />
"file": "images/search-bg.png"<br />
}<br />
]<br />
},<br />
"applications": {<br />
"sounds": [<br />
{<br />
"path": "/media/internal/ringtones/Silent.mp3",<br />
"file": "sounds/silent.mp3"<br />
}<br />
],<br />
"patches": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.messaging/stylesheets/messaging.css",<br />
"file": "patches/messaging-css.patch"<br />
}<br />
]<br />
},<br />
<br />
// If the component does not have images, sounds or patches then it can<br />
// be left out, but these are listed here just as an example what components<br />
// are supported.<br />
<br />
"enyo_widgets": {<br />
},<br />
"exhibition": {<br />
},<br />
"just_type": {<br />
},<br />
"keyboard": {<br />
},<br />
"lock_screen": {<br />
},<br />
"quick_launcher": {<br />
},<br />
"status_bar": {<br />
},<br />
"system_menus": {<br />
},<br />
"wallpapers": {<br />
"images": [<br />
{<br />
"path": "/media/internal/wallpapers/wallpaper.jpg",<br />
"file": "images/wallpaper.jpg"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br><br />
Once the theme is ready you should zip the directory with the directory name, e.g. com.mydomain.test-theme.zip. Its good practice also to include the device type in the zip name as well, e.g. com.mydomain.test-theme-tablet.zip / com.mydomain.test-theme-phone.zip. <br><br />
<br><br />
The zip file can be then installed with Theme Manager. Theme Manager unpacks the theme into /media/internal/.themes/ directory where you can even unpack your theme manually while in USB mode or edit/view the already installed themes (when in USB mode you should see .themes directory if you have installed themes).<br />
<br />
</blockquote><br />
<br />
<br />
== Troubleshooting/FAQs ==<br />
<blockquote><br />
'''Q: What webOS version or device is Theme Manager compatible with?'''<br />
<br /><br />
A: Theme Manager is available for any device running webOS 2.1 and later. '''(NOTE: Enyo must be installed for Theme Manager to work. This can be done on older devices by installing the updated Maps app available in the App Catalog.)'''<br />
</blockquote><br />
<blockquote><br />
'''Q: Where can a person find theme's compatible with Theme Manager?'''<br />
<br /><br />
A: While in the application is in beta, themes are being distributed independently. In the future, when the app is stable, a method, such as a preware and/or webosnation feed, will be in place. '''Some themes that are working with theme manager can be found below.'''<br />
</blockquote><br />
<br />
== Resources ==<br />
<br />
===== Supporting Development =====<br />
<blockquote><br />
{{SconixDonation}}<br />
<br /><br />
</blockquote><br />
<br />
===== Official Developer Project Page =====<br />
<blockquote><br />
* [[user:sconix|Current and Legacy Projects]]<br />
</blockquote><br />
<br />
===== Official Forum =====<br />
<blockquote><br />
* [http://forums.precentral.net/webos-internals/303050-theme-manager.html Official PreCentral Forum Thread]<br />
</blockquote><br />
<br />
===== Official Twitter Account =====<br />
<blockquote><br />
* Follow on Twitter: [http://twitter.com/therealsconix @therealsconix]<br />
</blockquote><br />
<br />
== Current Compatible Themes ==<br />
===== Black & White by Sconix and Pink Forever by Sconix =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad<br /><br />
'''Download:''' [http://rantsis.dyndns.info/public/themes/ Index of Public Themes]<br />
</blockquote><br />
===== Dark Glass by Michote =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad, Veer<br /><br />
'''Forum Thread:''' [http://forums.webosnation.com/webos-themes/305424-dark-glass-tm.html WebosNation]<br />
</blockquote><br />
<br />
===== Glass Themes by Garrett =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
'''Forum Thread:'''[http://forums.webosnation.com/webos-themes/286646-touchpad-glass-effect-suite-new-post.html Touchpad on WebosNation]<br><br />
'''Forum Thread:'''[http://forums.webosnation.com/webos-themes/309225-pre3-glass-effect-suite-new-post.html Pre3 on WebNation]<br />
</blockquote><br />
<br />
===== Classic PalmOS by Sketch42 =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
[http://dl.dropbox.com/u/19486634/com.sketch42.palmos-tribute.zip PalmOS-TouchPad] [http://dl.dropbox.com/u/19486634/com.sketch42.palmos.pre3.zip PalmOS-Pre3]<br />
</blockquote><br />
<br />
== Status ==<br />
<br />
:'''Changelog'''<br />
<blockquote><br />
:'''0.8.1 - Current Alpha Release''' - (''Oct. 30th, 2011'')<br />
:* Fixed patching/replacing of files located in cryptofs<br />
<br /><br />
:'''0.8.0'''<br />
:* Added searching/filtering of theme and made UI smoother<br />
<br /><br />
:'''0.7.0'''<br />
:* Logic changes and added list view mode for theme library<br />
<br /><br />
:'''0.5.1 - 0.6.9'''<br />
:* Fixed third party applications theming which was broken<br />
:* Couple small bug fixes for user interface and service<br />
:* Fixed a bug in theme applying that could have caused problems.<br />
:* Fixed serious bug that caused theme applying time get long<br />
:* More user interface fixes and polishing for phones<br />
:* Couple small bug fixes and fine tuned user interface<br />
:* Small fixes and added support for Boot Logo component<br />
:* Interface fine tuning for both phones and TouchPad<br />
:* Few interface fixes when running on Touchpad<br />
:* Few interface fixes and theme installation fix<br />
:* Couple small bug and typo fixes<br />
<br /><br />
:'''0.5.0'''<br />
:* First beta release with many changes<br />
<br /><br />
:'''0.2.0'''<br />
:* Added support for phones with enyo<br />
<br /><br />
:'''0.1.2'''<br />
:* Initial alpha release</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application_talk:ThemeManager&diff=21463Application talk:ThemeManager2012-01-17T17:19:48Z<p>SmartDeviceResource1: </p>
<hr />
<div>I have added links to the four families of currently compatible theme manager themes. I've added them to the resources section under the developer information as I was not sure of another location. Also Many of the links are direct download (Garret's and Sketch's) it'd be nice if we could have a bit of a buffer (not sure if direct linking follows strict guidelines for this site as this was my first major edit)<br />
Thanks Rod :) @nergal2</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:ThemeManager&diff=21461Application:ThemeManager2012-01-17T17:17:04Z<p>SmartDeviceResource1: /* Troubleshooting/FAQs */</p>
<hr />
<div><div style='position: relative;'><br />
{{application<br />
|name=Theme Manager<br />
|version=0.8.1<br />
|type=webOS<br />
|tag=Utilities<br />
|screenshot=theme_manager.png<br />
|description=<div style='position: absolute; bottom: 0; right: 0; padding-right: 28px; padding-bottom: 16px'>{{SconixDonation}}</div><br />
}}<br />
</div><br />
<br />
== Overview == <br />
[[image:Icon_Theme-Manager.png|frameless|left]]<br />
Theme Manager is a webOS ''(2.1+ w/Enyo installed)'' application that brings theme support to your device. Using Theme Manager, you will be able to browse locally downloaded themes and apply them to your device.<br /><br /><br />
<br />
<br />
== Installation == <br />
<br />
The following information will help you install Theme Manager.<br />
<br />
<br />
==== Overview ====<br />
<blockquote><br />
<span style="color:#8a0002">'''Stable Releases'''</span><br />
<br /><br />
The stable releases of Theme Manager can be found in the WebOS-Internals feed and are recommended for general public use.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Alpha/Beta Releases'''</span><br />
<br /><br />
The alpha/beta releases of Theme Manager can be found in the the WebOS-Internals Alpha or Beta feeds [http://www.webos-internals.org/wiki/Testing_Feeds WebOS-Internals Testing Feed].<br />
</blockquote><br />
<br />
<br />
==== Method ====<br />
<br />
The following method can be used to install Theme Manager.<br />
<br />
<br />
<blockquote><br />
===== [http://www.webos-internals.org/wiki/Application:Preware Preware] =====<br />
<br />
# Open Preware<br />
# Start typing “Theme Manager” (no quotes)<br />
# Tap the Theme Manager from the list<br />
# Tap the Install button<br />
# Restart your device ''(optional, but recommended)''<br />
<br />
'''Or'''<br />
<br />
# Open Preware<br />
# Tap Available Packages<br />
# Tap Application > System Utilities > Theme Manager<br />
# Tap the Install button<br />
# Tap the Ok button to restart Luna<br />
</blockquote><br />
<br />
<br />
==== Updating ====<br />
<br />
<blockquote><br />
===== <span style="color:#8a0002">webOS OTA Updates</span> =====<br />
Since Theme Manager is an app, it is OTA (over-the-air) update safe. When there is an OTA update to a newer version of webOS from your carrier/HP, you do not need to remove the app before updating. Themes applied with Theme Manager are also OTA safe. After an OTA update, you must re-apply the theme. '''Before applying a new OTA update, you might want to make sure that the themes you use are supported on the new webOS version.'''<br />
<br />
<br />
===== <span style="color:#8a0002">Application Updates</span> =====<br />
Updated versions of Theme Manager can be applied via Preware.<br />
</blockquote><br />
<br />
<br />
== Usage ==<br />
<br />
==== Adding Themes to your Device ====<br />
Theme Manager compatible themes come in two types: ZIP and IPK. Themes need to be added to your device before they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
To add a ZIP theme to your device, save the ZIP package to the Downloads folder on the USB partition of your device.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
To add an IPK theme to your device, save the IPK package to the USB partition of your device.<br />
</blockquote><br />
<br />
<br />
==== Installing Themes to the Theme Library ====<br />
Once themes are added to your device, they must be installed into the Theme Library so they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
#Tap Theme Library<br />
#Tap Install New Themes<br />
#Tap one or multiple ZIP themes in the file picker<br />
#Tap Ok<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
#Install the IPK package with Preware<br />
::''Note: If you have Theme Manager already open, you'll need to rescan for the newly installed theme(s).''<br />
::#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
::#Tap Theme Library<br />
::#Tap Re-Scan All Themes<br />
</blockquote><br />
<br />
<br />
====Applying your Theme(s) ====<br />
Now that you have your theme(s) added to your device and installed in the Theme Library, you can start applying the themes or various components from many themes to your device. '''''(NOTE: Be sure to remove any previous "non supported/non Theme Manager" themes prior to applying new themes with Theme Manager!)'''''<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''Applying A Complete Theme'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish to apply.<br />
# Tap the Select This Theme button<br />
# Tap the Apply Current Theme button<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Selecting Various Components From Many Themes'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish you select components from<br />
# Scroll down to and tap the Theme Components section<br />
# Tap the checkbox to select the components you wish to apply<br />
# Tap the Select Components button ''(Note: Repeat the above steps to select components from other themes before you apply the custom theme.)''<br />
# Tap the Apply Current Theme button<br />
</blockquote><br />
<br />
<br />
== Making Themes ==<br />
<br />
<blockquote><br />
First you should create a directory for your theme and you should name it in the following style to avoid any conflict with other themes: com.domain.theme-name (e.g. org.webosinternals.simple-test-theme). Even the theme can be set to support different devices you should make separate theme for different types of devices, i.e. most likely nobody wants to have files for TouchPad installed in his phone for example.<br><br />
<br><br />
The hierarchy inside of that directory is free but the example below uses following hierarchy (the theme.json file is the only one required and has to be named as theme.json):<br><br />
<br><br />
<pre><br />
org.webosinternals.simple-test-theme/<br />
data/<br />
images/<br />
patches/<br />
sounds/<br />
theme.json<br />
</pre><br />
<br><br />
Then the contents of the theme.json file is as below. The optional stuff if not used can be left out. You should make sure that the file contains valid json, i.e. don't use tabs or make typos :). Also you should leave out the comments.<br><br />
<br><br />
<pre><br />
{<br />
"name": "Theme Name", // Mandatory<br />
"version": "1.0.0", // Mandatory<br />
<br />
"description": "Description for the theme.", // Mandatory<br />
<br />
"creator": "Authors Name", // Mandatory<br />
"website": "", // Mandatory but can be left empty<br />
<br />
"donations": "", // Optional donation link<br />
<br />
"devices": [<br />
// Mandatory list of supported devices, valid devices are<br />
// emulator, touchpad, veer, pre3, pre (= pre,pre+,pre2)<br />
<br />
"emulator",<br />
"touchpad"<br />
],<br />
<br />
"screenshots": [ <br />
// Mandatory, at least one screenshot is required<br />
<br />
"data/default-view.png"<br />
],<br />
<br />
"themedata": { <br />
// Mandatory, different data can be set for different webOS versions, <br />
// every supported version must be listed, the components that does <br />
// not exist in the theme should be removed. Components can contain <br />
// images, sounds and patches.<br />
<br />
// Allowed files at the moment are, images: jpg/png, sounds: mp3/wav <br />
// and only files that can be patched are css files.<br />
<br />
"3.0.0": {<br />
// You can refer to other version with alias if the version is <br />
// compatible. At the moment if they differ even the slightest<br />
// amount you need to create new set, i.e. after alias you can<br />
// not set any "overrides" at the moment.<br />
<br />
"alias": "3.0.2"<br />
},<br />
"3.0.2": {<br />
// Path is always the path in the device and the file path to<br />
// to the file inside the theme directory.<br />
<br />
"app_icons": {<br />
"images": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.phone/icon.png",<br />
"file": "images/icon-phone.png"<br />
}<br />
]<br />
},<br />
"app_launcher": {<br />
"images": [<br />
{<br />
"path": "/usr/lib/luna/system/luna-applauncher/images/bg.png",<br />
"file": "images/search-bg.png"<br />
}<br />
]<br />
},<br />
"applications": {<br />
"sounds": [<br />
{<br />
"path": "/media/internal/ringtones/Silent.mp3",<br />
"file": "sounds/silent.mp3"<br />
}<br />
],<br />
"patches": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.messaging/stylesheets/messaging.css",<br />
"file": "patches/messaging-css.patch"<br />
}<br />
]<br />
},<br />
<br />
// If the component does not have images, sounds or patches then it can<br />
// be left out, but these are listed here just as an example what components<br />
// are supported.<br />
<br />
"enyo_widgets": {<br />
},<br />
"exhibition": {<br />
},<br />
"just_type": {<br />
},<br />
"keyboard": {<br />
},<br />
"lock_screen": {<br />
},<br />
"quick_launcher": {<br />
},<br />
"status_bar": {<br />
},<br />
"system_menus": {<br />
},<br />
"wallpapers": {<br />
"images": [<br />
{<br />
"path": "/media/internal/wallpapers/wallpaper.jpg",<br />
"file": "images/wallpaper.jpg"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br><br />
Once the theme is ready you should zip the directory with the directory name, e.g. com.mydomain.test-theme.zip. Its good practice also to include the device type in the zip name as well, e.g. com.mydomain.test-theme-tablet.zip / com.mydomain.test-theme-phone.zip. <br><br />
<br><br />
The zip file can be then installed with Theme Manager. Theme Manager unpacks the theme into /media/internal/.themes/ directory where you can even unpack your theme manually while in USB mode or edit/view the already installed themes (when in USB mode you should see .themes directory if you have installed themes).<br />
<br />
</blockquote><br />
<br />
<br />
== Troubleshooting/FAQs ==<br />
<blockquote><br />
'''Q: What webOS version or device is Theme Manager compatible with?'''<br />
<br /><br />
A: Theme Manager is available for any device running webOS 2.1 and later. '''(NOTE: Enyo must be installed for Theme Manager to work. This can be done on older devices by installing the updated Maps app available in the App Catalog.)'''<br />
</blockquote><br />
<blockquote><br />
'''Q: Where can a person find theme's compatible with Theme Manager?'''<br />
<br /><br />
A: While in the application is in beta, themes are being distributed independently. In the future, when the app is stable, a method, such as a preware and/or webosnation feed, will be in place. '''Some themes that are working with theme manager can be found below.'''<br />
</blockquote><br />
<br />
== Resources ==<br />
<br />
===== Supporting Development =====<br />
<blockquote><br />
{{SconixDonation}}<br />
<br /><br />
</blockquote><br />
<br />
===== Official Developer Project Page =====<br />
<blockquote><br />
* [[user:sconix|Current and Legacy Projects]]<br />
</blockquote><br />
<br />
===== Official Forum =====<br />
<blockquote><br />
* [http://forums.precentral.net/webos-internals/303050-theme-manager.html Official PreCentral Forum Thread]<br />
</blockquote><br />
<br />
===== Official Twitter Account =====<br />
<blockquote><br />
* Follow on Twitter: [http://twitter.com/therealsconix @therealsconix]<br />
</blockquote><br />
<br />
== Current Compatible Themes ==<br />
===== Black & White by Sconix and Pink Forever by Sconix =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad<br /><br />
'''Download:''' [http://rantsis.dyndns.info/public/themes/ Index of Public Themes]<br />
</blockquote><br />
===== Dark Glass by Michote =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad, Veer<br /><br />
'''Forum Thread:''' [http://forums.webosnation.com/webos-themes/305424-dark-glass-tm.html WebosNation]<br />
</blockquote><br />
<br />
===== Glass Themes by Garrett =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
'''Forum Thread-TouchPad:'''[http://forums.webosnation.com/webos-themes/286646-touchpad-glass-effect-suite.html WebosNation]<br><br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-black.zip Pre3 Black Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cerulean.zip Pre3 Cerulean Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cherry.zip Pre3 Cherry Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cobalt.zip Pre3 Colbalt Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-forest.zip Pre3 Forest Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-plum.zip Pre3 Plum Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-pumpkin.zip Pre3 Pumpkin Glass]<br />
</blockquote><br />
<br />
===== Classic PalmOS by Sketch42 =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
[http://dl.dropbox.com/u/19486634/com.sketch42.palmos-tribute.zip PalmOS-TouchPad] [http://dl.dropbox.com/u/19486634/com.sketch42.palmos.pre3.zip PalmOS-Pre3]<br />
</blockquote><br />
<br />
== Status ==<br />
<br />
:'''Changelog'''<br />
<blockquote><br />
:'''0.8.1 - Current Alpha Release''' - (''Oct. 30th, 2011'')<br />
:* Fixed patching/replacing of files located in cryptofs<br />
<br /><br />
:'''0.8.0'''<br />
:* Added searching/filtering of theme and made UI smoother<br />
<br /><br />
:'''0.7.0'''<br />
:* Logic changes and added list view mode for theme library<br />
<br /><br />
:'''0.5.1 - 0.6.9'''<br />
:* Fixed third party applications theming which was broken<br />
:* Couple small bug fixes for user interface and service<br />
:* Fixed a bug in theme applying that could have caused problems.<br />
:* Fixed serious bug that caused theme applying time get long<br />
:* More user interface fixes and polishing for phones<br />
:* Couple small bug fixes and fine tuned user interface<br />
:* Small fixes and added support for Boot Logo component<br />
:* Interface fine tuning for both phones and TouchPad<br />
:* Few interface fixes when running on Touchpad<br />
:* Few interface fixes and theme installation fix<br />
:* Couple small bug and typo fixes<br />
<br /><br />
:'''0.5.0'''<br />
:* First beta release with many changes<br />
<br /><br />
:'''0.2.0'''<br />
:* Added support for phones with enyo<br />
<br /><br />
:'''0.1.2'''<br />
:* Initial alpha release</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application_talk:ThemeManager&diff=21459Application talk:ThemeManager2012-01-17T17:15:55Z<p>SmartDeviceResource1: Created page with "I have added links to the four families of currently compatible theme manager themes. I've added them to the resources section under the developer information as I was not sure ..."</p>
<hr />
<div>I have added links to the four families of currently compatible theme manager themes. I've added them to the resources section under the developer information as I was not sure of another location</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:ThemeManager&diff=21457Application:ThemeManager2012-01-17T17:13:51Z<p>SmartDeviceResource1: /* Current Compatible Themes */</p>
<hr />
<div><div style='position: relative;'><br />
{{application<br />
|name=Theme Manager<br />
|version=0.8.1<br />
|type=webOS<br />
|tag=Utilities<br />
|screenshot=theme_manager.png<br />
|description=<div style='position: absolute; bottom: 0; right: 0; padding-right: 28px; padding-bottom: 16px'>{{SconixDonation}}</div><br />
}}<br />
</div><br />
<br />
== Overview == <br />
[[image:Icon_Theme-Manager.png|frameless|left]]<br />
Theme Manager is a webOS ''(2.1+ w/Enyo installed)'' application that brings theme support to your device. Using Theme Manager, you will be able to browse locally downloaded themes and apply them to your device.<br /><br /><br />
<br />
<br />
== Installation == <br />
<br />
The following information will help you install Theme Manager.<br />
<br />
<br />
==== Overview ====<br />
<blockquote><br />
<span style="color:#8a0002">'''Stable Releases'''</span><br />
<br /><br />
The stable releases of Theme Manager can be found in the WebOS-Internals feed and are recommended for general public use.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Alpha/Beta Releases'''</span><br />
<br /><br />
The alpha/beta releases of Theme Manager can be found in the the WebOS-Internals Alpha or Beta feeds [http://www.webos-internals.org/wiki/Testing_Feeds WebOS-Internals Testing Feed].<br />
</blockquote><br />
<br />
<br />
==== Method ====<br />
<br />
The following method can be used to install Theme Manager.<br />
<br />
<br />
<blockquote><br />
===== [http://www.webos-internals.org/wiki/Application:Preware Preware] =====<br />
<br />
# Open Preware<br />
# Start typing “Theme Manager” (no quotes)<br />
# Tap the Theme Manager from the list<br />
# Tap the Install button<br />
# Restart your device ''(optional, but recommended)''<br />
<br />
'''Or'''<br />
<br />
# Open Preware<br />
# Tap Available Packages<br />
# Tap Application > System Utilities > Theme Manager<br />
# Tap the Install button<br />
# Tap the Ok button to restart Luna<br />
</blockquote><br />
<br />
<br />
==== Updating ====<br />
<br />
<blockquote><br />
===== <span style="color:#8a0002">webOS OTA Updates</span> =====<br />
Since Theme Manager is an app, it is OTA (over-the-air) update safe. When there is an OTA update to a newer version of webOS from your carrier/HP, you do not need to remove the app before updating. Themes applied with Theme Manager are also OTA safe. After an OTA update, you must re-apply the theme. '''Before applying a new OTA update, you might want to make sure that the themes you use are supported on the new webOS version.'''<br />
<br />
<br />
===== <span style="color:#8a0002">Application Updates</span> =====<br />
Updated versions of Theme Manager can be applied via Preware.<br />
</blockquote><br />
<br />
<br />
== Usage ==<br />
<br />
==== Adding Themes to your Device ====<br />
Theme Manager compatible themes come in two types: ZIP and IPK. Themes need to be added to your device before they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
To add a ZIP theme to your device, save the ZIP package to the Downloads folder on the USB partition of your device.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
To add an IPK theme to your device, save the IPK package to the USB partition of your device.<br />
</blockquote><br />
<br />
<br />
==== Installing Themes to the Theme Library ====<br />
Once themes are added to your device, they must be installed into the Theme Library so they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
#Tap Theme Library<br />
#Tap Install New Themes<br />
#Tap one or multiple ZIP themes in the file picker<br />
#Tap Ok<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
#Install the IPK package with Preware<br />
::''Note: If you have Theme Manager already open, you'll need to rescan for the newly installed theme(s).''<br />
::#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
::#Tap Theme Library<br />
::#Tap Re-Scan All Themes<br />
</blockquote><br />
<br />
<br />
====Applying your Theme(s) ====<br />
Now that you have your theme(s) added to your device and installed in the Theme Library, you can start applying the themes or various components from many themes to your device. '''''(NOTE: Be sure to remove any previous "non supported/non Theme Manager" themes prior to applying new themes with Theme Manager!)'''''<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''Applying A Complete Theme'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish to apply.<br />
# Tap the Select This Theme button<br />
# Tap the Apply Current Theme button<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Selecting Various Components From Many Themes'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish you select components from<br />
# Scroll down to and tap the Theme Components section<br />
# Tap the checkbox to select the components you wish to apply<br />
# Tap the Select Components button ''(Note: Repeat the above steps to select components from other themes before you apply the custom theme.)''<br />
# Tap the Apply Current Theme button<br />
</blockquote><br />
<br />
<br />
== Making Themes ==<br />
<br />
<blockquote><br />
First you should create a directory for your theme and you should name it in the following style to avoid any conflict with other themes: com.domain.theme-name (e.g. org.webosinternals.simple-test-theme). Even the theme can be set to support different devices you should make separate theme for different types of devices, i.e. most likely nobody wants to have files for TouchPad installed in his phone for example.<br><br />
<br><br />
The hierarchy inside of that directory is free but the example below uses following hierarchy (the theme.json file is the only one required and has to be named as theme.json):<br><br />
<br><br />
<pre><br />
org.webosinternals.simple-test-theme/<br />
data/<br />
images/<br />
patches/<br />
sounds/<br />
theme.json<br />
</pre><br />
<br><br />
Then the contents of the theme.json file is as below. The optional stuff if not used can be left out. You should make sure that the file contains valid json, i.e. don't use tabs or make typos :). Also you should leave out the comments.<br><br />
<br><br />
<pre><br />
{<br />
"name": "Theme Name", // Mandatory<br />
"version": "1.0.0", // Mandatory<br />
<br />
"description": "Description for the theme.", // Mandatory<br />
<br />
"creator": "Authors Name", // Mandatory<br />
"website": "", // Mandatory but can be left empty<br />
<br />
"donations": "", // Optional donation link<br />
<br />
"devices": [<br />
// Mandatory list of supported devices, valid devices are<br />
// emulator, touchpad, veer, pre3, pre (= pre,pre+,pre2)<br />
<br />
"emulator",<br />
"touchpad"<br />
],<br />
<br />
"screenshots": [ <br />
// Mandatory, at least one screenshot is required<br />
<br />
"data/default-view.png"<br />
],<br />
<br />
"themedata": { <br />
// Mandatory, different data can be set for different webOS versions, <br />
// every supported version must be listed, the components that does <br />
// not exist in the theme should be removed. Components can contain <br />
// images, sounds and patches.<br />
<br />
// Allowed files at the moment are, images: jpg/png, sounds: mp3/wav <br />
// and only files that can be patched are css files.<br />
<br />
"3.0.0": {<br />
// You can refer to other version with alias if the version is <br />
// compatible. At the moment if they differ even the slightest<br />
// amount you need to create new set, i.e. after alias you can<br />
// not set any "overrides" at the moment.<br />
<br />
"alias": "3.0.2"<br />
},<br />
"3.0.2": {<br />
// Path is always the path in the device and the file path to<br />
// to the file inside the theme directory.<br />
<br />
"app_icons": {<br />
"images": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.phone/icon.png",<br />
"file": "images/icon-phone.png"<br />
}<br />
]<br />
},<br />
"app_launcher": {<br />
"images": [<br />
{<br />
"path": "/usr/lib/luna/system/luna-applauncher/images/bg.png",<br />
"file": "images/search-bg.png"<br />
}<br />
]<br />
},<br />
"applications": {<br />
"sounds": [<br />
{<br />
"path": "/media/internal/ringtones/Silent.mp3",<br />
"file": "sounds/silent.mp3"<br />
}<br />
],<br />
"patches": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.messaging/stylesheets/messaging.css",<br />
"file": "patches/messaging-css.patch"<br />
}<br />
]<br />
},<br />
<br />
// If the component does not have images, sounds or patches then it can<br />
// be left out, but these are listed here just as an example what components<br />
// are supported.<br />
<br />
"enyo_widgets": {<br />
},<br />
"exhibition": {<br />
},<br />
"just_type": {<br />
},<br />
"keyboard": {<br />
},<br />
"lock_screen": {<br />
},<br />
"quick_launcher": {<br />
},<br />
"status_bar": {<br />
},<br />
"system_menus": {<br />
},<br />
"wallpapers": {<br />
"images": [<br />
{<br />
"path": "/media/internal/wallpapers/wallpaper.jpg",<br />
"file": "images/wallpaper.jpg"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br><br />
Once the theme is ready you should zip the directory with the directory name, e.g. com.mydomain.test-theme.zip. Its good practice also to include the device type in the zip name as well, e.g. com.mydomain.test-theme-tablet.zip / com.mydomain.test-theme-phone.zip. <br><br />
<br><br />
The zip file can be then installed with Theme Manager. Theme Manager unpacks the theme into /media/internal/.themes/ directory where you can even unpack your theme manually while in USB mode or edit/view the already installed themes (when in USB mode you should see .themes directory if you have installed themes).<br />
<br />
</blockquote><br />
<br />
<br />
== Troubleshooting/FAQs ==<br />
<blockquote><br />
'''Q: What webOS version or device is Theme Manager compatible with?'''<br />
<br /><br />
A: Theme Manager is available for any device running webOS 2.1 and later. '''(NOTE: Enyo must be installed for Theme Manager to work. This can be done on older devices by installing the updated Maps app available in the App Catalog.)'''<br />
</blockquote><br />
<blockquote><br />
'''Q: Where can a person find theme's compatible with Theme Manager?'''<br />
<br /><br />
A: While in the application is in beta, themes are being distributed independently. In the future, when the app is stable, a method, such as a preware and/or webosnation feed, will be in place. Some themes that are working with theme manager can be found below.<br />
</blockquote><br />
<br />
== Resources ==<br />
<br />
===== Supporting Development =====<br />
<blockquote><br />
{{SconixDonation}}<br />
<br /><br />
</blockquote><br />
<br />
===== Official Developer Project Page =====<br />
<blockquote><br />
* [[user:sconix|Current and Legacy Projects]]<br />
</blockquote><br />
<br />
===== Official Forum =====<br />
<blockquote><br />
* [http://forums.precentral.net/webos-internals/303050-theme-manager.html Official PreCentral Forum Thread]<br />
</blockquote><br />
<br />
===== Official Twitter Account =====<br />
<blockquote><br />
* Follow on Twitter: [http://twitter.com/therealsconix @therealsconix]<br />
</blockquote><br />
<br />
== Current Compatible Themes ==<br />
===== Black & White by Sconix and Pink Forever by Sconix =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad<br /><br />
'''Download:''' [http://rantsis.dyndns.info/public/themes/ Index of Public Themes]<br />
</blockquote><br />
===== Dark Glass by Michote =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad, Veer<br /><br />
'''Forum Thread:''' [http://forums.webosnation.com/webos-themes/305424-dark-glass-tm.html WebosNation]<br />
</blockquote><br />
<br />
===== Glass Themes by Garrett =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
'''Forum Thread-TouchPad:'''[http://forums.webosnation.com/webos-themes/286646-touchpad-glass-effect-suite.html WebosNation]<br><br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-black.zip Pre3 Black Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cerulean.zip Pre3 Cerulean Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cherry.zip Pre3 Cherry Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cobalt.zip Pre3 Colbalt Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-forest.zip Pre3 Forest Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-plum.zip Pre3 Plum Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-pumpkin.zip Pre3 Pumpkin Glass]<br />
</blockquote><br />
<br />
===== Classic PalmOS by Sketch42 =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
[http://dl.dropbox.com/u/19486634/com.sketch42.palmos-tribute.zip PalmOS-TouchPad] [http://dl.dropbox.com/u/19486634/com.sketch42.palmos.pre3.zip PalmOS-Pre3]<br />
</blockquote><br />
<br />
== Status ==<br />
<br />
:'''Changelog'''<br />
<blockquote><br />
:'''0.8.1 - Current Alpha Release''' - (''Oct. 30th, 2011'')<br />
:* Fixed patching/replacing of files located in cryptofs<br />
<br /><br />
:'''0.8.0'''<br />
:* Added searching/filtering of theme and made UI smoother<br />
<br /><br />
:'''0.7.0'''<br />
:* Logic changes and added list view mode for theme library<br />
<br /><br />
:'''0.5.1 - 0.6.9'''<br />
:* Fixed third party applications theming which was broken<br />
:* Couple small bug fixes for user interface and service<br />
:* Fixed a bug in theme applying that could have caused problems.<br />
:* Fixed serious bug that caused theme applying time get long<br />
:* More user interface fixes and polishing for phones<br />
:* Couple small bug fixes and fine tuned user interface<br />
:* Small fixes and added support for Boot Logo component<br />
:* Interface fine tuning for both phones and TouchPad<br />
:* Few interface fixes when running on Touchpad<br />
:* Few interface fixes and theme installation fix<br />
:* Couple small bug and typo fixes<br />
<br /><br />
:'''0.5.0'''<br />
:* First beta release with many changes<br />
<br /><br />
:'''0.2.0'''<br />
:* Added support for phones with enyo<br />
<br /><br />
:'''0.1.2'''<br />
:* Initial alpha release</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:ThemeManager&diff=21455Application:ThemeManager2012-01-17T17:09:54Z<p>SmartDeviceResource1: /* Resources */</p>
<hr />
<div><div style='position: relative;'><br />
{{application<br />
|name=Theme Manager<br />
|version=0.8.1<br />
|type=webOS<br />
|tag=Utilities<br />
|screenshot=theme_manager.png<br />
|description=<div style='position: absolute; bottom: 0; right: 0; padding-right: 28px; padding-bottom: 16px'>{{SconixDonation}}</div><br />
}}<br />
</div><br />
<br />
== Overview == <br />
[[image:Icon_Theme-Manager.png|frameless|left]]<br />
Theme Manager is a webOS ''(2.1+ w/Enyo installed)'' application that brings theme support to your device. Using Theme Manager, you will be able to browse locally downloaded themes and apply them to your device.<br /><br /><br />
<br />
<br />
== Installation == <br />
<br />
The following information will help you install Theme Manager.<br />
<br />
<br />
==== Overview ====<br />
<blockquote><br />
<span style="color:#8a0002">'''Stable Releases'''</span><br />
<br /><br />
The stable releases of Theme Manager can be found in the WebOS-Internals feed and are recommended for general public use.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Alpha/Beta Releases'''</span><br />
<br /><br />
The alpha/beta releases of Theme Manager can be found in the the WebOS-Internals Alpha or Beta feeds [http://www.webos-internals.org/wiki/Testing_Feeds WebOS-Internals Testing Feed].<br />
</blockquote><br />
<br />
<br />
==== Method ====<br />
<br />
The following method can be used to install Theme Manager.<br />
<br />
<br />
<blockquote><br />
===== [http://www.webos-internals.org/wiki/Application:Preware Preware] =====<br />
<br />
# Open Preware<br />
# Start typing “Theme Manager” (no quotes)<br />
# Tap the Theme Manager from the list<br />
# Tap the Install button<br />
# Restart your device ''(optional, but recommended)''<br />
<br />
'''Or'''<br />
<br />
# Open Preware<br />
# Tap Available Packages<br />
# Tap Application > System Utilities > Theme Manager<br />
# Tap the Install button<br />
# Tap the Ok button to restart Luna<br />
</blockquote><br />
<br />
<br />
==== Updating ====<br />
<br />
<blockquote><br />
===== <span style="color:#8a0002">webOS OTA Updates</span> =====<br />
Since Theme Manager is an app, it is OTA (over-the-air) update safe. When there is an OTA update to a newer version of webOS from your carrier/HP, you do not need to remove the app before updating. Themes applied with Theme Manager are also OTA safe. After an OTA update, you must re-apply the theme. '''Before applying a new OTA update, you might want to make sure that the themes you use are supported on the new webOS version.'''<br />
<br />
<br />
===== <span style="color:#8a0002">Application Updates</span> =====<br />
Updated versions of Theme Manager can be applied via Preware.<br />
</blockquote><br />
<br />
<br />
== Usage ==<br />
<br />
==== Adding Themes to your Device ====<br />
Theme Manager compatible themes come in two types: ZIP and IPK. Themes need to be added to your device before they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
To add a ZIP theme to your device, save the ZIP package to the Downloads folder on the USB partition of your device.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
To add an IPK theme to your device, save the IPK package to the USB partition of your device.<br />
</blockquote><br />
<br />
<br />
==== Installing Themes to the Theme Library ====<br />
Once themes are added to your device, they must be installed into the Theme Library so they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
#Tap Theme Library<br />
#Tap Install New Themes<br />
#Tap one or multiple ZIP themes in the file picker<br />
#Tap Ok<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
#Install the IPK package with Preware<br />
::''Note: If you have Theme Manager already open, you'll need to rescan for the newly installed theme(s).''<br />
::#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
::#Tap Theme Library<br />
::#Tap Re-Scan All Themes<br />
</blockquote><br />
<br />
<br />
====Applying your Theme(s) ====<br />
Now that you have your theme(s) added to your device and installed in the Theme Library, you can start applying the themes or various components from many themes to your device. '''''(NOTE: Be sure to remove any previous "non supported/non Theme Manager" themes prior to applying new themes with Theme Manager!)'''''<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''Applying A Complete Theme'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish to apply.<br />
# Tap the Select This Theme button<br />
# Tap the Apply Current Theme button<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Selecting Various Components From Many Themes'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish you select components from<br />
# Scroll down to and tap the Theme Components section<br />
# Tap the checkbox to select the components you wish to apply<br />
# Tap the Select Components button ''(Note: Repeat the above steps to select components from other themes before you apply the custom theme.)''<br />
# Tap the Apply Current Theme button<br />
</blockquote><br />
<br />
<br />
== Making Themes ==<br />
<br />
<blockquote><br />
First you should create a directory for your theme and you should name it in the following style to avoid any conflict with other themes: com.domain.theme-name (e.g. org.webosinternals.simple-test-theme). Even the theme can be set to support different devices you should make separate theme for different types of devices, i.e. most likely nobody wants to have files for TouchPad installed in his phone for example.<br><br />
<br><br />
The hierarchy inside of that directory is free but the example below uses following hierarchy (the theme.json file is the only one required and has to be named as theme.json):<br><br />
<br><br />
<pre><br />
org.webosinternals.simple-test-theme/<br />
data/<br />
images/<br />
patches/<br />
sounds/<br />
theme.json<br />
</pre><br />
<br><br />
Then the contents of the theme.json file is as below. The optional stuff if not used can be left out. You should make sure that the file contains valid json, i.e. don't use tabs or make typos :). Also you should leave out the comments.<br><br />
<br><br />
<pre><br />
{<br />
"name": "Theme Name", // Mandatory<br />
"version": "1.0.0", // Mandatory<br />
<br />
"description": "Description for the theme.", // Mandatory<br />
<br />
"creator": "Authors Name", // Mandatory<br />
"website": "", // Mandatory but can be left empty<br />
<br />
"donations": "", // Optional donation link<br />
<br />
"devices": [<br />
// Mandatory list of supported devices, valid devices are<br />
// emulator, touchpad, veer, pre3, pre (= pre,pre+,pre2)<br />
<br />
"emulator",<br />
"touchpad"<br />
],<br />
<br />
"screenshots": [ <br />
// Mandatory, at least one screenshot is required<br />
<br />
"data/default-view.png"<br />
],<br />
<br />
"themedata": { <br />
// Mandatory, different data can be set for different webOS versions, <br />
// every supported version must be listed, the components that does <br />
// not exist in the theme should be removed. Components can contain <br />
// images, sounds and patches.<br />
<br />
// Allowed files at the moment are, images: jpg/png, sounds: mp3/wav <br />
// and only files that can be patched are css files.<br />
<br />
"3.0.0": {<br />
// You can refer to other version with alias if the version is <br />
// compatible. At the moment if they differ even the slightest<br />
// amount you need to create new set, i.e. after alias you can<br />
// not set any "overrides" at the moment.<br />
<br />
"alias": "3.0.2"<br />
},<br />
"3.0.2": {<br />
// Path is always the path in the device and the file path to<br />
// to the file inside the theme directory.<br />
<br />
"app_icons": {<br />
"images": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.phone/icon.png",<br />
"file": "images/icon-phone.png"<br />
}<br />
]<br />
},<br />
"app_launcher": {<br />
"images": [<br />
{<br />
"path": "/usr/lib/luna/system/luna-applauncher/images/bg.png",<br />
"file": "images/search-bg.png"<br />
}<br />
]<br />
},<br />
"applications": {<br />
"sounds": [<br />
{<br />
"path": "/media/internal/ringtones/Silent.mp3",<br />
"file": "sounds/silent.mp3"<br />
}<br />
],<br />
"patches": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.messaging/stylesheets/messaging.css",<br />
"file": "patches/messaging-css.patch"<br />
}<br />
]<br />
},<br />
<br />
// If the component does not have images, sounds or patches then it can<br />
// be left out, but these are listed here just as an example what components<br />
// are supported.<br />
<br />
"enyo_widgets": {<br />
},<br />
"exhibition": {<br />
},<br />
"just_type": {<br />
},<br />
"keyboard": {<br />
},<br />
"lock_screen": {<br />
},<br />
"quick_launcher": {<br />
},<br />
"status_bar": {<br />
},<br />
"system_menus": {<br />
},<br />
"wallpapers": {<br />
"images": [<br />
{<br />
"path": "/media/internal/wallpapers/wallpaper.jpg",<br />
"file": "images/wallpaper.jpg"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br><br />
Once the theme is ready you should zip the directory with the directory name, e.g. com.mydomain.test-theme.zip. Its good practice also to include the device type in the zip name as well, e.g. com.mydomain.test-theme-tablet.zip / com.mydomain.test-theme-phone.zip. <br><br />
<br><br />
The zip file can be then installed with Theme Manager. Theme Manager unpacks the theme into /media/internal/.themes/ directory where you can even unpack your theme manually while in USB mode or edit/view the already installed themes (when in USB mode you should see .themes directory if you have installed themes).<br />
<br />
</blockquote><br />
<br />
<br />
== Troubleshooting/FAQs ==<br />
<blockquote><br />
'''Q: What webOS version or device is Theme Manager compatible with?'''<br />
<br /><br />
A: Theme Manager is available for any device running webOS 2.1 and later. '''(NOTE: Enyo must be installed for Theme Manager to work. This can be done on older devices by installing the updated Maps app available in the App Catalog.)'''<br />
</blockquote><br />
<blockquote><br />
'''Q: Where can a person find theme's compatible with Theme Manager?'''<br />
<br /><br />
A: While in the application is in beta, themes are being distributed independently. In the future, when the app is stable, a method, such as a preware and/or webosnation feed, will be in place. Some themes that are working with theme manager can be found below.<br />
</blockquote><br />
<br />
== Resources ==<br />
<br />
===== Supporting Development =====<br />
<blockquote><br />
{{SconixDonation}}<br />
<br /><br />
</blockquote><br />
<br />
===== Official Developer Project Page =====<br />
<blockquote><br />
* [[user:sconix|Current and Legacy Projects]]<br />
</blockquote><br />
<br />
===== Official Forum =====<br />
<blockquote><br />
* [http://forums.precentral.net/webos-internals/303050-theme-manager.html Official PreCentral Forum Thread]<br />
</blockquote><br />
<br />
===== Official Twitter Account =====<br />
<blockquote><br />
* Follow on Twitter: [http://twitter.com/therealsconix @therealsconix]<br />
</blockquote><br />
<br />
== Current Compatible Themes ==<br />
===== Black & White by Sconix and Pink Forever by Sconix =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad<br /><br />
'''Download:''' [http://rantsis.dyndns.info/public/themes/ Index of Public Themes]<br />
</blockquote><br />
===== Dark Glass by Michote =====<br />
<blockquote><br />
'''Devices:''' Legacy(pre, pre+, Pre2 running 2.1.0), Pre2 (running 2.2.4) Pre3, TouchPad, Veer<br /><br />
'''Forum Thread:''' [http://forums.webosnation.com/webos-themes/305424-dark-glass-tm.html WebosNation]<br />
</blockquote><br />
<br />
===== Glass Themes by Garrett =====<br />
<blockquote><br />
'''Devices:''' Pre3, TouchPad<br /><br />
'''Forum Thread-TouchPad:'''[http://forums.webosnation.com/webos-themes/286646-touchpad-glass-effect-suite.html WebosNation]<br><br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-black.zip Pre3 Black Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cerulean.zip Pre3 Cerulean Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cherry.zip Pre3 Cherry Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-cobalt.zip Pre3 Colbalt Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-forest.zip Pre3 Forest Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-plum.zip Pre3 Plum Glass]<br />
[http://dl.dropbox.com/u/21803890/themes/com.choorp.ges-pre3-pumpkin.zip Pre3 Pumpkin Glass]<br />
</blockquote><br />
<br />
== Status ==<br />
<br />
:'''Changelog'''<br />
<blockquote><br />
:'''0.8.1 - Current Alpha Release''' - (''Oct. 30th, 2011'')<br />
:* Fixed patching/replacing of files located in cryptofs<br />
<br /><br />
:'''0.8.0'''<br />
:* Added searching/filtering of theme and made UI smoother<br />
<br /><br />
:'''0.7.0'''<br />
:* Logic changes and added list view mode for theme library<br />
<br /><br />
:'''0.5.1 - 0.6.9'''<br />
:* Fixed third party applications theming which was broken<br />
:* Couple small bug fixes for user interface and service<br />
:* Fixed a bug in theme applying that could have caused problems.<br />
:* Fixed serious bug that caused theme applying time get long<br />
:* More user interface fixes and polishing for phones<br />
:* Couple small bug fixes and fine tuned user interface<br />
:* Small fixes and added support for Boot Logo component<br />
:* Interface fine tuning for both phones and TouchPad<br />
:* Few interface fixes when running on Touchpad<br />
:* Few interface fixes and theme installation fix<br />
:* Couple small bug and typo fixes<br />
<br /><br />
:'''0.5.0'''<br />
:* First beta release with many changes<br />
<br /><br />
:'''0.2.0'''<br />
:* Added support for phones with enyo<br />
<br /><br />
:'''0.1.2'''<br />
:* Initial alpha release</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:ThemeManager&diff=21453Application:ThemeManager2012-01-17T16:40:53Z<p>SmartDeviceResource1: /* Troubleshooting/FAQs */</p>
<hr />
<div><div style='position: relative;'><br />
{{application<br />
|name=Theme Manager<br />
|version=0.8.1<br />
|type=webOS<br />
|tag=Utilities<br />
|screenshot=theme_manager.png<br />
|description=<div style='position: absolute; bottom: 0; right: 0; padding-right: 28px; padding-bottom: 16px'>{{SconixDonation}}</div><br />
}}<br />
</div><br />
<br />
== Overview == <br />
[[image:Icon_Theme-Manager.png|frameless|left]]<br />
Theme Manager is a webOS ''(2.1+ w/Enyo installed)'' application that brings theme support to your device. Using Theme Manager, you will be able to browse locally downloaded themes and apply them to your device.<br /><br /><br />
<br />
<br />
== Installation == <br />
<br />
The following information will help you install Theme Manager.<br />
<br />
<br />
==== Overview ====<br />
<blockquote><br />
<span style="color:#8a0002">'''Stable Releases'''</span><br />
<br /><br />
The stable releases of Theme Manager can be found in the WebOS-Internals feed and are recommended for general public use.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Alpha/Beta Releases'''</span><br />
<br /><br />
The alpha/beta releases of Theme Manager can be found in the the WebOS-Internals Alpha or Beta feeds [http://www.webos-internals.org/wiki/Testing_Feeds WebOS-Internals Testing Feed].<br />
</blockquote><br />
<br />
<br />
==== Method ====<br />
<br />
The following method can be used to install Theme Manager.<br />
<br />
<br />
<blockquote><br />
===== [http://www.webos-internals.org/wiki/Application:Preware Preware] =====<br />
<br />
# Open Preware<br />
# Start typing “Theme Manager” (no quotes)<br />
# Tap the Theme Manager from the list<br />
# Tap the Install button<br />
# Restart your device ''(optional, but recommended)''<br />
<br />
'''Or'''<br />
<br />
# Open Preware<br />
# Tap Available Packages<br />
# Tap Application > System Utilities > Theme Manager<br />
# Tap the Install button<br />
# Tap the Ok button to restart Luna<br />
</blockquote><br />
<br />
<br />
==== Updating ====<br />
<br />
<blockquote><br />
===== <span style="color:#8a0002">webOS OTA Updates</span> =====<br />
Since Theme Manager is an app, it is OTA (over-the-air) update safe. When there is an OTA update to a newer version of webOS from your carrier/HP, you do not need to remove the app before updating. Themes applied with Theme Manager are also OTA safe. After an OTA update, you must re-apply the theme. '''Before applying a new OTA update, you might want to make sure that the themes you use are supported on the new webOS version.'''<br />
<br />
<br />
===== <span style="color:#8a0002">Application Updates</span> =====<br />
Updated versions of Theme Manager can be applied via Preware.<br />
</blockquote><br />
<br />
<br />
== Usage ==<br />
<br />
==== Adding Themes to your Device ====<br />
Theme Manager compatible themes come in two types: ZIP and IPK. Themes need to be added to your device before they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
To add a ZIP theme to your device, save the ZIP package to the Downloads folder on the USB partition of your device.<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
To add an IPK theme to your device, save the IPK package to the USB partition of your device.<br />
</blockquote><br />
<br />
<br />
==== Installing Themes to the Theme Library ====<br />
Once themes are added to your device, they must be installed into the Theme Library so they can be accessed in Theme Manager.<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''ZIP Compatible Themes'''</span><br />
<br /><br />
#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
#Tap Theme Library<br />
#Tap Install New Themes<br />
#Tap one or multiple ZIP themes in the file picker<br />
#Tap Ok<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''IPK Compatible Themes'''</span><br />
<br /><br />
#Install the IPK package with Preware<br />
::''Note: If you have Theme Manager already open, you'll need to rescan for the newly installed theme(s).''<br />
::#Tap or Swipe down the Application Menu (left of the screen/top bar)<br />
::#Tap Theme Library<br />
::#Tap Re-Scan All Themes<br />
</blockquote><br />
<br />
<br />
====Applying your Theme(s) ====<br />
Now that you have your theme(s) added to your device and installed in the Theme Library, you can start applying the themes or various components from many themes to your device. '''''(NOTE: Be sure to remove any previous "non supported/non Theme Manager" themes prior to applying new themes with Theme Manager!)'''''<br />
<br />
<blockquote><br />
<span style="color:#8a0002">'''Applying A Complete Theme'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish to apply.<br />
# Tap the Select This Theme button<br />
# Tap the Apply Current Theme button<br />
<br /><br /><br />
<br />
<span style="color:#8a0002">'''Selecting Various Components From Many Themes'''</span><br />
<br /><br />
# Browse (swipe) to the theme you wish you select components from<br />
# Scroll down to and tap the Theme Components section<br />
# Tap the checkbox to select the components you wish to apply<br />
# Tap the Select Components button ''(Note: Repeat the above steps to select components from other themes before you apply the custom theme.)''<br />
# Tap the Apply Current Theme button<br />
</blockquote><br />
<br />
<br />
== Making Themes ==<br />
<br />
<blockquote><br />
First you should create a directory for your theme and you should name it in the following style to avoid any conflict with other themes: com.domain.theme-name (e.g. org.webosinternals.simple-test-theme). Even the theme can be set to support different devices you should make separate theme for different types of devices, i.e. most likely nobody wants to have files for TouchPad installed in his phone for example.<br><br />
<br><br />
The hierarchy inside of that directory is free but the example below uses following hierarchy (the theme.json file is the only one required and has to be named as theme.json):<br><br />
<br><br />
<pre><br />
org.webosinternals.simple-test-theme/<br />
data/<br />
images/<br />
patches/<br />
sounds/<br />
theme.json<br />
</pre><br />
<br><br />
Then the contents of the theme.json file is as below. The optional stuff if not used can be left out. You should make sure that the file contains valid json, i.e. don't use tabs or make typos :). Also you should leave out the comments.<br><br />
<br><br />
<pre><br />
{<br />
"name": "Theme Name", // Mandatory<br />
"version": "1.0.0", // Mandatory<br />
<br />
"description": "Description for the theme.", // Mandatory<br />
<br />
"creator": "Authors Name", // Mandatory<br />
"website": "", // Mandatory but can be left empty<br />
<br />
"donations": "", // Optional donation link<br />
<br />
"devices": [<br />
// Mandatory list of supported devices, valid devices are<br />
// emulator, touchpad, veer, pre3, pre (= pre,pre+,pre2)<br />
<br />
"emulator",<br />
"touchpad"<br />
],<br />
<br />
"screenshots": [ <br />
// Mandatory, at least one screenshot is required<br />
<br />
"data/default-view.png"<br />
],<br />
<br />
"themedata": { <br />
// Mandatory, different data can be set for different webOS versions, <br />
// every supported version must be listed, the components that does <br />
// not exist in the theme should be removed. Components can contain <br />
// images, sounds and patches.<br />
<br />
// Allowed files at the moment are, images: jpg/png, sounds: mp3/wav <br />
// and only files that can be patched are css files.<br />
<br />
"3.0.0": {<br />
// You can refer to other version with alias if the version is <br />
// compatible. At the moment if they differ even the slightest<br />
// amount you need to create new set, i.e. after alias you can<br />
// not set any "overrides" at the moment.<br />
<br />
"alias": "3.0.2"<br />
},<br />
"3.0.2": {<br />
// Path is always the path in the device and the file path to<br />
// to the file inside the theme directory.<br />
<br />
"app_icons": {<br />
"images": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.phone/icon.png",<br />
"file": "images/icon-phone.png"<br />
}<br />
]<br />
},<br />
"app_launcher": {<br />
"images": [<br />
{<br />
"path": "/usr/lib/luna/system/luna-applauncher/images/bg.png",<br />
"file": "images/search-bg.png"<br />
}<br />
]<br />
},<br />
"applications": {<br />
"sounds": [<br />
{<br />
"path": "/media/internal/ringtones/Silent.mp3",<br />
"file": "sounds/silent.mp3"<br />
}<br />
],<br />
"patches": [<br />
{<br />
"path": "/usr/palm/applications/com.palm.app.messaging/stylesheets/messaging.css",<br />
"file": "patches/messaging-css.patch"<br />
}<br />
]<br />
},<br />
<br />
// If the component does not have images, sounds or patches then it can<br />
// be left out, but these are listed here just as an example what components<br />
// are supported.<br />
<br />
"enyo_widgets": {<br />
},<br />
"exhibition": {<br />
},<br />
"just_type": {<br />
},<br />
"keyboard": {<br />
},<br />
"lock_screen": {<br />
},<br />
"quick_launcher": {<br />
},<br />
"status_bar": {<br />
},<br />
"system_menus": {<br />
},<br />
"wallpapers": {<br />
"images": [<br />
{<br />
"path": "/media/internal/wallpapers/wallpaper.jpg",<br />
"file": "images/wallpaper.jpg"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br><br />
Once the theme is ready you should zip the directory with the directory name, e.g. com.mydomain.test-theme.zip. Its good practice also to include the device type in the zip name as well, e.g. com.mydomain.test-theme-tablet.zip / com.mydomain.test-theme-phone.zip. <br><br />
<br><br />
The zip file can be then installed with Theme Manager. Theme Manager unpacks the theme into /media/internal/.themes/ directory where you can even unpack your theme manually while in USB mode or edit/view the already installed themes (when in USB mode you should see .themes directory if you have installed themes).<br />
<br />
</blockquote><br />
<br />
<br />
== Troubleshooting/FAQs ==<br />
<blockquote><br />
'''Q: What webOS version or device is Theme Manager compatible with?'''<br />
<br /><br />
A: Theme Manager is available for any device running webOS 2.1 and later. '''(NOTE: Enyo must be installed for Theme Manager to work. This can be done on older devices by installing the updated Maps app available in the App Catalog.)'''<br />
</blockquote><br />
<blockquote><br />
'''Q: Where can a person find theme's compatible with Theme Manager?'''<br />
<br /><br />
A: While in the application is in beta, themes are being distributed independently. In the future, when the app is stable, a method, such as a preware and/or webosnation feed, will be in place. Some themes that are working with theme manager can be found below.<br />
</blockquote><br />
<br />
== Resources ==<br />
<br />
===== Supporting Development =====<br />
<blockquote><br />
{{SconixDonation}}<br />
<br /><br />
</blockquote><br />
<br />
===== Official Developer Project Page =====<br />
<blockquote><br />
* [[user:sconix|Current and Legacy Projects]]<br />
</blockquote><br />
<br />
===== Official Forum =====<br />
<blockquote><br />
* [http://forums.precentral.net/webos-internals/303050-theme-manager.html Official PreCentral Forum Thread]<br />
</blockquote><br />
<br />
===== Official Twitter Account =====<br />
<blockquote><br />
* Follow on Twitter: [http://twitter.com/therealsconix @therealsconix]<br />
</blockquote><br />
<br />
<br />
== Status ==<br />
<br />
:'''Changelog'''<br />
<blockquote><br />
:'''0.8.1 - Current Alpha Release''' - (''Oct. 30th, 2011'')<br />
:* Fixed patching/replacing of files located in cryptofs<br />
<br /><br />
:'''0.8.0'''<br />
:* Added searching/filtering of theme and made UI smoother<br />
<br /><br />
:'''0.7.0'''<br />
:* Logic changes and added list view mode for theme library<br />
<br /><br />
:'''0.5.1 - 0.6.9'''<br />
:* Fixed third party applications theming which was broken<br />
:* Couple small bug fixes for user interface and service<br />
:* Fixed a bug in theme applying that could have caused problems.<br />
:* Fixed serious bug that caused theme applying time get long<br />
:* More user interface fixes and polishing for phones<br />
:* Couple small bug fixes and fine tuned user interface<br />
:* Small fixes and added support for Boot Logo component<br />
:* Interface fine tuning for both phones and TouchPad<br />
:* Few interface fixes when running on Touchpad<br />
:* Few interface fixes and theme installation fix<br />
:* Couple small bug and typo fixes<br />
<br /><br />
:'''0.5.0'''<br />
:* First beta release with many changes<br />
<br /><br />
:'''0.2.0'''<br />
:* Added support for phones with enyo<br />
<br /><br />
:'''0.1.2'''<br />
:* Initial alpha release</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:MetaDoctor&diff=18385Application:MetaDoctor2011-09-08T21:10:22Z<p>SmartDeviceResource1: /* Windows */</p>
<hr />
<div>[[Category:Application]]<br />
This page is currently available in four languages:<br />
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]<br />
:[[Image:France.png]] [[Application:MetaDoctor-FR]]<br />
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]<br />
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]<br />
<br />
= What is the Meta Doctor? =<br />
<br />
The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.<br />
<br />
'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''<br />
<br />
= Step 1: Setting up Meta-Doctor=<br />
<br />
== Windows ==<br />
<br />
'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''<br />
<br />
Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.<br />
<br />
# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''<br />
# Burn that file to a cd or mount to virtual drive<br />
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''<br />
# Click on '''Install Inside windows'''.<br />
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine. <br />
# Restart your computer and you can dual boot to Windows or Ubuntu <br />
<br />
The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.<br />
<br />
If you are still wondering what Wubi is, the following link should explain it to you better.<br />
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]<br />
<br />
Once you have installed WUBI, you should follow the instructions in the Linux section below.<br />
<br />
== Linux == <br />
<br />
# Open terminal from the ( Applications > Accessories ) menu.<br />
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.<br />
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].<br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre><br />
# Create a downloads directory. Type: <pre>mkdir downloads</pre><br />
<br />
== Mac OS X 10.6 ==<br />
<br />
#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site] or on your Mac OS X installation CDs/DVD.<br />
#Install md5sum: <pre>sudo port install md5sha1sum</pre><br />
#Install gnutar: <pre>sudo port install gnutar</pre><br />
#Install git: <pre>sudo port install git-core</pre><br />
#Install wget: <pre>sudo port install wget</pre><br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
#Install patch: <pre>sudo port install gpatch</pre><br />
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].<br />
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].<br />
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre><br />
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre><br />
<br />
= Step 2: Running the webOS Doctor=<br />
<br />
Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.<br />
<br />
'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''<br />
<br />
# Navigate to the meta-doctor directory in the terminal<br />
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .<br />
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)<br />
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre><br />
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].<br />
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.<br />
# Type one of the following: <br />
#: <pre>make DEVICE=pre CARRIER=wr all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pre CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre><br />
#: <pre>make DEVICE=pre CARRIER=telcel all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre><br />
#: depending on the carrier in question.<br />
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France<br />
<br />
This should begin a process within the terminal that should take 10 minutes max.<br />
<br />
<br />
<br />
=== Error conditions ===<br />
<br />
If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).<br />
<br />
=== If the build fails ===<br />
<br />
If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.<br />
<br />
The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar''.<br />
<br />
If you are running in Ubuntu or Cygwin, you can just run the new jar file now. <br />
<br />
If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS. <br />
<br />
CD to the folder where your new jar file is, and type something like: <br />
<br />
java -jar webosdoctorp302hstnhwifi.jar<br />
<br />
If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it. <br />
<br />
<br />
''Windows host:''<br />
<br />
[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]<br />
<br />
[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]<br />
<br />
''Mac OSX host:''<br />
<br />
[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]<br />
<br />
<br />
: ''NOTE: this only applies to WUBI Users'' <br />
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows <br />
<br />
Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre><br />
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.<br />
<br />
== Once the Doctor is running ==<br />
<br />
# Select your language<br />
# Accept the license agreement<br />
# Connect your Pre to your PC via USB and select "Next" when it becomes available<br />
<br />
After completion the device will reboot and present you with the activation set-up.<br />
<br />
If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:<br />
<br />
# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)<br />
# Hold down the Up button on the volume rocker<br />
# While holding the Up button, power on the Pre<br />
# "Next" should now be enabled - proceed with the recovery<br />
{{tux|Tux_with_Pre.png|float:right;}}<br />
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.<br />
<br />
When the process finishes, the Pre will reboot and your new modified image will have been installed.<br />
<br />
----<br />
<br />
After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:<br />
<br />
'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.<br />
<br />
'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.<br />
*'''1.''' Open the Phone App.<br />
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)<br />
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.<br />
*'''4.''' Select ''Edit''.<br />
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.<br />
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).<br />
*'''7.''' Select ''Save''.<br />
*'''8.''' Backswipe out of the the view.<br />
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.<br />
<br />
You should now be able to run the ''First Use'' application without any problems.<br />
<br />
=If the Doctor will not run=<br />
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.<br />
<br />
=Miscellaneous=<br />
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.<br />
Steps:<br />
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).<br />
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config<br />
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl<br />
4. Put com.palm.wifi.prefsDB.sl in the config directory.<br />
5. Continue following instructions in the makefile.<br />
<br />
==How to enable WIFI profiles==<br />
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile. <br />
<br />
# Move to the meta-doctor directory (cd meta-doctor)<br />
# Create a "config" folder in the meta-doctor directory (mkdir config)<br />
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.<br />
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes<br />
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.<br />
# Build the custom doctor by running the script, or otherwise building it.<br />
<br />
<br />
On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.<br />
<br />
See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].<br />
<br />
==How to get the optional ext3fs partition mounted at device boot==<br />
<br />
'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''<br />
<br />
Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.<br />
<br />
All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).<br />
<br />
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:<br />
<br />
<pre>mount -o remount,rw /<br />
mkdir -p /media/ext3fs</pre><br />
<br />
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.<br />
<br />
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.<br />
<br />
<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice<br />
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre><br />
<br />
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.<br />
<br />
<pre>mount -a</pre><br />
<br />
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.<br />
<br />
<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre><br />
<br />
== How to remove the ext3fs partition ==<br />
<br />
http://www.gadgetxplorer.com/2011/08/webos-how-to-remove-ext3fs-partition.html<br />
<br />
==How to change a provider's DB-entry so 3G data can be used on the Pre==<br />
<br />
[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1<br />
<br />
== Problems with Novacom ==<br />
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].<br />
<br />
== How to Install webOS 2.x on "unoffical" Devices==<br />
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Application:MetaDoctor&diff=18383Application:MetaDoctor2011-09-08T21:09:34Z<p>SmartDeviceResource1: /* Windows */</p>
<hr />
<div>[[Category:Application]]<br />
This page is currently available in four languages:<br />
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]<br />
:[[Image:France.png]] [[Application:MetaDoctor-FR]]<br />
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]<br />
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]<br />
<br />
= What is the Meta Doctor? =<br />
<br />
The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.<br />
<br />
'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''<br />
<br />
= Step 1: Setting up Meta-Doctor=<br />
<br />
== Windows ==<br />
<br />
'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''<br />
<br />
Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.<br />
<br />
# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''<br />
# Burn that file to a cd or mount to virtual drive<br />
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''<br />
# Click on '''Install Inside windows'''.<br />
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine. <br />
# Restart your computer and you can dual boot to Windows or Ubuntu <br />
<br />
The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.<br />
<br />
If you are still wondering what Wubi is the following link should explain it to you better.<br />
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]<br />
<br />
Once you have installed WUBI, you should follow the instructions in the Linux section below.<br />
<br />
== Linux == <br />
<br />
# Open terminal from the ( Applications > Accessories ) menu.<br />
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.<br />
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].<br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre><br />
# Create a downloads directory. Type: <pre>mkdir downloads</pre><br />
<br />
== Mac OS X 10.6 ==<br />
<br />
#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site] or on your Mac OS X installation CDs/DVD.<br />
#Install md5sum: <pre>sudo port install md5sha1sum</pre><br />
#Install gnutar: <pre>sudo port install gnutar</pre><br />
#Install git: <pre>sudo port install git-core</pre><br />
#Install wget: <pre>sudo port install wget</pre><br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
#Install patch: <pre>sudo port install gpatch</pre><br />
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].<br />
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].<br />
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre><br />
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre><br />
<br />
= Step 2: Running the webOS Doctor=<br />
<br />
Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.<br />
<br />
'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''<br />
<br />
# Navigate to the meta-doctor directory in the terminal<br />
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .<br />
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)<br />
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre><br />
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].<br />
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.<br />
# Type one of the following: <br />
#: <pre>make DEVICE=pre CARRIER=wr all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pre CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre><br />
#: <pre>make DEVICE=pre CARRIER=telcel all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre><br />
#: depending on the carrier in question.<br />
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France<br />
<br />
This should begin a process within the terminal that should take 10 minutes max.<br />
<br />
<br />
<br />
=== Error conditions ===<br />
<br />
If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).<br />
<br />
=== If the build fails ===<br />
<br />
If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.<br />
<br />
The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar''.<br />
<br />
If you are running in Ubuntu or Cygwin, you can just run the new jar file now. <br />
<br />
If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS. <br />
<br />
CD to the folder where your new jar file is, and type something like: <br />
<br />
java -jar webosdoctorp302hstnhwifi.jar<br />
<br />
If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it. <br />
<br />
<br />
''Windows host:''<br />
<br />
[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]<br />
<br />
[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]<br />
<br />
''Mac OSX host:''<br />
<br />
[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]<br />
<br />
<br />
: ''NOTE: this only applies to WUBI Users'' <br />
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows <br />
<br />
Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre><br />
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.<br />
<br />
== Once the Doctor is running ==<br />
<br />
# Select your language<br />
# Accept the license agreement<br />
# Connect your Pre to your PC via USB and select "Next" when it becomes available<br />
<br />
After completion the device will reboot and present you with the activation set-up.<br />
<br />
If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:<br />
<br />
# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)<br />
# Hold down the Up button on the volume rocker<br />
# While holding the Up button, power on the Pre<br />
# "Next" should now be enabled - proceed with the recovery<br />
{{tux|Tux_with_Pre.png|float:right;}}<br />
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.<br />
<br />
When the process finishes, the Pre will reboot and your new modified image will have been installed.<br />
<br />
----<br />
<br />
After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:<br />
<br />
'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.<br />
<br />
'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.<br />
*'''1.''' Open the Phone App.<br />
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)<br />
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.<br />
*'''4.''' Select ''Edit''.<br />
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.<br />
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).<br />
*'''7.''' Select ''Save''.<br />
*'''8.''' Backswipe out of the the view.<br />
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.<br />
<br />
You should now be able to run the ''First Use'' application without any problems.<br />
<br />
=If the Doctor will not run=<br />
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.<br />
<br />
=Miscellaneous=<br />
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.<br />
Steps:<br />
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).<br />
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config<br />
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl<br />
4. Put com.palm.wifi.prefsDB.sl in the config directory.<br />
5. Continue following instructions in the makefile.<br />
<br />
==How to enable WIFI profiles==<br />
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile. <br />
<br />
# Move to the meta-doctor directory (cd meta-doctor)<br />
# Create a "config" folder in the meta-doctor directory (mkdir config)<br />
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.<br />
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes<br />
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.<br />
# Build the custom doctor by running the script, or otherwise building it.<br />
<br />
<br />
On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.<br />
<br />
See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].<br />
<br />
==How to get the optional ext3fs partition mounted at device boot==<br />
<br />
'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''<br />
<br />
Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.<br />
<br />
All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).<br />
<br />
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:<br />
<br />
<pre>mount -o remount,rw /<br />
mkdir -p /media/ext3fs</pre><br />
<br />
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.<br />
<br />
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.<br />
<br />
<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice<br />
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre><br />
<br />
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.<br />
<br />
<pre>mount -a</pre><br />
<br />
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.<br />
<br />
<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre><br />
<br />
== How to remove the ext3fs partition ==<br />
<br />
http://www.gadgetxplorer.com/2011/08/webos-how-to-remove-ext3fs-partition.html<br />
<br />
==How to change a provider's DB-entry so 3G data can be used on the Pre==<br />
<br />
[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1<br />
<br />
== Problems with Novacom ==<br />
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].<br />
<br />
== How to Install webOS 2.x on "unoffical" Devices==<br />
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Testing_Feeds&diff=17531Testing Feeds2011-07-26T22:31:12Z<p>SmartDeviceResource1: /* Kernel Testing Feeds */</p>
<hr />
<div>=Rules that you must agree to before using these feeds=<br />
<br />
Before you use our testing feeds, please read and agree to the following rules:<br />
[[image:Tux_with_Warning.png|frameless|right]]<br />
# Anyone participating in WebOS Internals alpha testing of any kind must be prepared to fully erase and webOS Doctor their device at a moment's notice without warning and without any regrets or complaints.<br />
# 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.<br />
# They must be prepared to go to great and extraordinary lengths to try and reliably reproduce any problems they encounter.<br />
# They must give full and detailed bug reports, leaving out no piece of information which could possibly be remotely connected to the problem.<br />
# They must read any and all documentation and forums threads (in their entirety) before asking a question.<br />
# They must fastidiously follow the forum threads where the alpha testing is being discussed by the authors, and follow precisely any instructions given there.<br />
<br />
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.<br />
<br />
If you are prepared to do *all* the above, then by all means please participate in the alpha testing.<br />
<br />
Note that everything above is a function of attitude, not of skill.<br />
<br />
=Configuring the WebOS Internals Testing Feeds=<br />
<br />
===Using Preware===<br />
[[image:Tux_with_Pre.png|frameless|right]]<br />
With Preware versions 0.9.30 and above, incombination with webOS 1.3.5 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 feeds.<br />
<br />
Note that you will need to enable *TWO* feeds below. You need the *ALL* feed and you need the device-specific feed as well (armv7, armv6 or i686).<br />
<br />
{|<br />
|colspan="2" align="left"|'''Target Device:''' ALL<br />
|-<br />
|'''Name:'''||webos-testing-all<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/all/ http://ipkg.preware.org/feeds/webos-internals/testing/all]<br />
|-<br />
| &nbsp;<br />
|-<br />
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pre/Pre+/Pre2/Veer/TouchPad/Pre3</nowiki><br />
|-<br />
|'''Name:'''||webos-testing-armv7<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv7/ http://ipkg.preware.org/feeds/webos-internals/testing/armv7]<br />
|-<br />
| &nbsp;<br />
|-<br />
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pixi/Pixi+</nowiki><br />
|-<br />
|'''Name:'''||webos-testing-armv6<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv6/ http://ipkg.preware.org/feeds/webos-internals/testing/armv6]<br />
|-<br />
| &nbsp;<br />
|-<br />
|colspan="2" align="left"|'''Target Device:''' Palm SDK Emulator<br />
|-<br />
|'''Name:'''||webos-testing-i686<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/i686/ http://ipkg.preware.org/feeds/webos-internals/testing/i686]<br />
|}<br />
<BR><br />
#Open Preware and wait for it to finish loading.<br />
#Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.<br />
#Scroll to the bottom until you see the New Feed box.<br />
#Type or paste a name and corresponding URL from above in the appropriate text boxes. Make sure the URL does *not* have a slash at the end.<br />
#Make sure the IS COMPRESSED option is set to YES.<br />
#Tap Add Feed and then tap Yes when the alert pops up.<br />
#Repeat these steps for each feed you wish to enable.<br />
#Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.<br />
<BR><br />
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.<br />
<BR><br />
'''TIP:'''<br />
<br />
shift+tap (and drag) on text to select<br />
gesture+c to copy<br />
gesture+v to paste<br />
Make sure to delete 'http://' before pasting the URL if the URL already contains 'http://'<br />
<br />
<BR><br />
<br />
===Using a Computer===<br />
[[image:Tux_Chat.png|frameless|right]]<br />
1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the regular WebOS Internals Feed<BR><br />
2. Execute the following commands:<br />
<pre><br />
cd /media/cryptofs/apps/etc/ipkg<br />
echo "src/gz webosinternals-testing http://ipkg.preware.org/feeds/webos-internals/testing/all" > webos-internals-testing.conf<br />
echo "src/gz webosinternals-testing-armv7 http://ipkg.preware.org/feeds/webos-internals/testing/armv7" >> webos-internals-testing.conf<br />
</pre><br />
3. Once Preware is launched, select "Update Feeds" from the Application Menu.<br />
<br />
Replace 'armv7' with 'armv6' or 'i686' in the instructions above if you are using a Pixi or the Emulator respectively.<br />
<br />
<BR><br />
=Kernel Testing Feeds=<br />
[http://www.webos-internals.org/index.php?title=Testing_Feeds&action=submit#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]<br />
Also see http://forums.precentral.net/2532084-post3.html for further warnings up to and including your device wiping itself, (literally) melting, and/or eating your kitten. <br />
<br />
If you do not want a puddle of molten plastic and silicon where your Pre/Pixi once was, DO NOT CONTINUE. <br />
<br />
You have been warned. <br />
<br />
[http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ And Palm is not going to help you.]<br />
<br />
<br />
#Type 'webos-kernels-testing' (without the quotes, and using lower case letters and hyphens only) in the NAME field of the NEW FEED section of the Manage Feeds screen accessible from the Preware application menu. If you make any error in this feed name, the URL below will not be replaced by the real URL when the device is rebooted, and you will not get access to the feeds. MAKE SURE YOU GET THE FEED NAME CORRECT!<br />
#Put http://preware.is.awesome.com/ in the URL field. Note that this is not a real URL - it is a placeholder only. Again, you need to get the feed name correct for the real URL to be replaced correctly when the device is rebooted.<br />
#Leave the IS COMPRESSED toggled on.<br />
#Hit "Add Feed" and read the disclaimer carefully. Yes, the things you might find in kernel testing feeds are likely to completely wipe your device without warning. Hit the Ok button only if you are prepared to lose all your data and destroy your device without any regrets or complaints.<br />
#Immediately reboot the device by simultaneously pressing the Opt, Sym and R keys. If you don't reboot the device, or if you only do a Luna Restart instead of a Device Reboot, then placeholder URL will not be replaced by the real URL and you will not get access to the feeds. MAKE SURE YOU REBOOT THE DEVICE!<br />
#Wait for the device to boot. If you got the feed name correct, the placeholder URL will be replaced by the real feed URL automatically.<br />
#Open Preware, and hit Update Feeds. Make sure you have a working network connection for this.<br />
<br />
Preware will repair the URL field automatically when the device boots. Did I mention that you have to get the feed name precisely correct for this to happen? MAKE SURE YOU GET THE FEED NAME CORRECT AND REBOOT THE DEVICE!<br />
<br />
You must be running Preware 1.1.4 or later for this to work (yes, this has been possible for quite some time).</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Testing_Feeds&diff=17529Testing Feeds2011-07-26T22:29:28Z<p>SmartDeviceResource1: /* Rules that you must agree to before using these feeds */</p>
<hr />
<div>=Rules that you must agree to before using these feeds=<br />
<br />
Before you use our testing feeds, please read and agree to the following rules:<br />
[[image:Tux_with_Warning.png|frameless|right]]<br />
# Anyone participating in WebOS Internals alpha testing of any kind must be prepared to fully erase and webOS Doctor their device at a moment's notice without warning and without any regrets or complaints.<br />
# 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.<br />
# They must be prepared to go to great and extraordinary lengths to try and reliably reproduce any problems they encounter.<br />
# They must give full and detailed bug reports, leaving out no piece of information which could possibly be remotely connected to the problem.<br />
# They must read any and all documentation and forums threads (in their entirety) before asking a question.<br />
# They must fastidiously follow the forum threads where the alpha testing is being discussed by the authors, and follow precisely any instructions given there.<br />
<br />
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.<br />
<br />
If you are prepared to do *all* the above, then by all means please participate in the alpha testing.<br />
<br />
Note that everything above is a function of attitude, not of skill.<br />
<br />
=Configuring the WebOS Internals Testing Feeds=<br />
<br />
===Using Preware===<br />
[[image:Tux_with_Pre.png|frameless|right]]<br />
With Preware versions 0.9.30 and above, incombination with webOS 1.3.5 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 feeds.<br />
<br />
Note that you will need to enable *TWO* feeds below. You need the *ALL* feed and you need the device-specific feed as well (armv7, armv6 or i686).<br />
<br />
{|<br />
|colspan="2" align="left"|'''Target Device:''' ALL<br />
|-<br />
|'''Name:'''||webos-testing-all<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/all/ http://ipkg.preware.org/feeds/webos-internals/testing/all]<br />
|-<br />
| &nbsp;<br />
|-<br />
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pre/Pre+/Pre2/Veer/TouchPad/Pre3</nowiki><br />
|-<br />
|'''Name:'''||webos-testing-armv7<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv7/ http://ipkg.preware.org/feeds/webos-internals/testing/armv7]<br />
|-<br />
| &nbsp;<br />
|-<br />
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pixi/Pixi+</nowiki><br />
|-<br />
|'''Name:'''||webos-testing-armv6<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv6/ http://ipkg.preware.org/feeds/webos-internals/testing/armv6]<br />
|-<br />
| &nbsp;<br />
|-<br />
|colspan="2" align="left"|'''Target Device:''' Palm SDK Emulator<br />
|-<br />
|'''Name:'''||webos-testing-i686<br />
|-<br />
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/i686/ http://ipkg.preware.org/feeds/webos-internals/testing/i686]<br />
|}<br />
<BR><br />
#Open Preware and wait for it to finish loading.<br />
#Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.<br />
#Scroll to the bottom until you see the New Feed box.<br />
#Type or paste a name and corresponding URL from above in the appropriate text boxes. Make sure the URL does *not* have a slash at the end.<br />
#Make sure the IS COMPRESSED option is set to YES.<br />
#Tap Add Feed and then tap Yes when the alert pops up.<br />
#Repeat these steps for each feed you wish to enable.<br />
#Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.<br />
<BR><br />
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.<br />
<BR><br />
'''TIP:'''<br />
<br />
shift+tap (and drag) on text to select<br />
gesture+c to copy<br />
gesture+v to paste<br />
Make sure to delete 'http://' before pasting the URL if the URL already contains 'http://'<br />
<br />
<BR><br />
<br />
===Using a Computer===<br />
[[image:Tux_Chat.png|frameless|right]]<br />
1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the regular WebOS Internals Feed<BR><br />
2. Execute the following commands:<br />
<pre><br />
cd /media/cryptofs/apps/etc/ipkg<br />
echo "src/gz webosinternals-testing http://ipkg.preware.org/feeds/webos-internals/testing/all" > webos-internals-testing.conf<br />
echo "src/gz webosinternals-testing-armv7 http://ipkg.preware.org/feeds/webos-internals/testing/armv7" >> webos-internals-testing.conf<br />
</pre><br />
3. Once Preware is launched, select "Update Feeds" from the Application Menu.<br />
<br />
Replace 'armv7' with 'armv6' or 'i686' in the instructions above if you are using a Pixi or the Emulator respectively.<br />
<br />
<BR><br />
=Kernel Testing Feeds=<br />
[http://www.webos-internals.org/index.php?title=Testing_Feeds&action=submit#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]<br />
Also see http://forums.precentral.net/2532084-post3.html for further warnings up to and including your device wiping itself, (literally) melting, and/or eating your kitten. <br />
<br />
If you do not want a puddle of molten plastic and silicon where your Pre/Pixi once was, DO NOT CONTINUE. <br />
<br />
You have been warned. <br />
<br />
[http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ And Palm is not going to help you.]<br />
<br />
<br />
#Type 'webos-kernels-testing' (without the quotes, and using lower case letters and hyphens only) in the NAME field of the NEW FEED section of the Manage Feeds screen accessible from the Preware application menu. If you make any error in this feed name, the URL below will not be replaced by the real URL when the phone is rebooted, and you will not get access to the feeds. MAKE SURE YOU GET THE FEED NAME CORRECT!<br />
#Put http://preware.is.awesome.com/ in the URL field. Note that this is not a real URL - it is a placeholder only. Again, you need to get the feed name correct for the real URL to be replaced correctly when the phone is rebooted.<br />
#Leave the IS COMPRESSED toggled on.<br />
#Hit "Add Feed" and read the disclaimer carefully. Yes, the things you might find in kernel testing feeds are likely to completely wipe your device without warning. Hit the Ok button only if you are prepared to lose all your data and destroy your device without any regrets or complaints.<br />
#Immediately reboot the device by simultaneously pressing the Opt, Sym and R keys. If you don't reboot the phone, or if you only do a Luna Restart instead of a Phone Reboot, then placeholder URL will not be replaced by the real URL and you will not get access to the feeds. MAKE SURE YOU REBOOT THE PHONE!<br />
#Wait for the device to boot. If you got the feed name correct, the placeholder URL will be replaced by the real feed URL automatically.<br />
#Open Preware, and hit Update Feeds. Make sure you have a working network connection for this.<br />
<br />
Preware will repair the URL field automatically when the device boots. Did I mention that you have to get the feed name precisely correct for this to happen? MAKE SURE YOU GET THE FEED NAME CORRECT AND REBOOT THE PHONE!<br />
<br />
You must be running Preware 1.1.4 or later for this to work (yes, this has been possible for quite some time).</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=User_talk:SmartDeviceResource1&diff=17275User talk:SmartDeviceResource12011-07-14T00:34:49Z<p>SmartDeviceResource1: Created page with "Honestly, I'll not contribute too much (I ain't no Linux Genius like the majority of people here). Mostly I'll just fix little grammer mistakes. If I discover something not yet..."</p>
<hr />
<div>Honestly, I'll not contribute too much (I ain't no Linux Genius like the majority of people here). Mostly I'll just fix little grammer mistakes.<br />
<br />
If I discover something not yet published, I'll change things, but not often.</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=Patch_webOS_Boot_Themes&diff=17273Patch webOS Boot Themes2011-07-14T00:31:29Z<p>SmartDeviceResource1: /* NOTE: In webOS 2.x, the boot images are named hp-logo.png and hp-logo-bright.png. Be sure to make the necessary adjustments to your commands when following the steps below. */</p>
<hr />
<div>{{template:patch}}<br />
When the Pre is booting or shutting down, the screen fades between two images - ''/palm-logo.png'' and ''/palm-logo-bright.png'' located in ''/usr/palm/sysmgr/images''. By replacing either or both of these images, the boot logo can be customized. This requires [[Portal:Accessing_Linux | access to the Pre's OS]] if you follow the method outlined below "Replacing the Files". However, boot logos can now be installed via Quick Install...read the next paragraph to find out how.<br />
<br />
The easiest way to install a boot theme onto your phone is to use WebOS Quick Install, which can be found at http://forums.precentral.net/homebrew-apps/206905-webos-quick-install-v2-7-beyond.html. You can download any set of boot logos, and then install them with Quick Install via the Change Boot Logo tweak. Alternatively, if you use the website PreThemer, you can download the IPKG files and install them directly through Quick Install. To do this, simply download the IPK file from the website to wherever you want on your computer, and then drag it into the main field of Quick Install and hit Install. If you had a boot log installed previous to webOS 1.2 (or 1.2.1), it is recommended that you uninstall the old ones first with Quick Install if you want to install via that program. To do this, go to Tools > Device Management and then look over your installed applications. You should see the name of your installed boot logo on that list. You can uninstall it by checking its box and then clicking uninstall. <br />
<br />
Works with: 1.0.3, 1.1 <br />
<br />
<br />
==='''NOTE:''' In webOS 2.x and 3.X, the boot images are named ''hp''-logo.png and ''hp''-logo-bright.png. Be sure to make the necessary adjustments to your commands when following the steps below.===<br />
<br />
== Replacing the Files using Internalz==<br />
<br />
# Install Internalz (by Canuck Software) from Preware or WOSQI.<br /><br />
# Turn on "Master Mode" in the preferences menu of Internalz. (You can bork your phone messing around with this mode, so don't wander from the path. Pay attention to the pop-up warning when you enable Master Mode.)<br /><br />
# Place your desired boot images in your phone's USB partition and name them '''palm-logo.png''' and '''palm-logo-bright.png'''.<br /><br />
# Navigate to ''/usr/palm/sysmgr/images/'' and find '''palm-logo.png''' and '''palm-logo-bright.png'''. Rename them by adding ".orig" (without the quotes) to the end of the file name. (Example: palm-logo-bright.png.orig) You rename a file in Internalz by tapping the file, selecting "Info" from the menu, and then editing the name at the top of the screen.<br /><br />
# Navigate back to the folder where you placed your new images and copy each one individually to ''/usr/palm/sysmgr/images/''.<br /><br />
# Restart luna and see your new boot logo.<br />
<br />
== Replacing the Files using Linux Commands==<br />
<br />
'''Step One'''<br />
Log into the phone via ssh and copy the files to the USB drive.<br />
<pre><nowiki><br />
#/if your login account does not have root permission, you must sudo the commands...the following assumes you do not have root permission<br />
#/if you do not use sudo and do not have root permission, you will get Permission Denied errors...<br />
sudo mkdir /media/internal/bootlogo<br />
sudo cp /usr/palm/sysmgr/images/palm-logo* /media/internal/bootlogo<br />
</nowiki></pre><br />
<br />
'''Step Two'''<br />
Modify the files with your favorite editor (Gimp, Photoshop, ImageMagick, MS Paint, etc.)<br />
<br />
'''Step Three'''<br />
Save the new images to the ''bootlogo'' directory on the Pre's USB drive.<br />
<br />
'''Step Four'''<br />
Log into the phone via ssh, remount the root filesystem read-write, backup the existing files, copy the new images into place, and remount the root filesystem read-only.<br />
<pre><nowiki><br />
sudo mount -o rw,remount /<br />
sudo cp -ip /usr/palm/sysmgr/images/palm-logo.png /usr/palm/sysmgr/images/palm-logo.png.orig<br />
sudo cp -ip /usr/palm/sysmgr/images/palm-logo-bright.png /usr/palm/sysmgr/images/palm-logo-bright.png.orig<br />
sudo cp /media/internal/bootlogo/palm-logo.png /usr/palm/sysmgr/images/palm-logo.png<br />
sudo cp /media/internal/bootlogo/palm-logo-bright.png /usr/palm/sysmgr/images/palm-logo-bright.png<br />
sudo mount -o ro,remount /<br />
</nowiki></pre><br />
<br />
'''Step Five'''<br />
Restart Luna and watch your awesome new logo.<br />
<pre><nowiki><br />
pkill LunaSysMgr<br />
</nowiki></pre><br />
<br />
== Taking it to the Next Step==<br />
<br />
With a small bit of scripting, we can have separate boot and shutdown themes. The first thing to do is to create regular and "bright" images for booting and shutting down. Save the new images to the ''bootlogo'' directory on the Pre's USB drive. (Steps 1-3 above).<br />
<br />
'''Step One'''<br />
Log into the phone via ssh, remount the root filesystem read-write, and create a directory in /opt to store the new images. We're using /opt, as the script we'll modify later will copy files, and /usr is mounted read-only.<br />
<pre><nowiki><br />
sudo mount -o rw,remount /<br />
sudo mkdir -p /opt/share/bootimages<br />
</nowiki></pre><br />
<br />
'''Step Two'''<br />
Copy the new images to /opt/share/bootimages, naming them palm-logo-up.png, palm-logo-up-bright.png, palm-logo-down.png and palm-logo-down-bright.png. Additionally, copy the shutdown files to palm-logo.png and palm-logo-bright.png.<br />
<pre><nowiki><br />
cd /opt/share/bootimages/<br />
sudo cp /media/internal/bootlogo/<boot image> palm-logo-up.png<br />
sudo cp /media/internal/bootlogo/<bright boot image> palm-logo-up-bright.png<br />
sudo cp /media/internal/bootlogo/<shutdown image> palm-logo-down.png<br />
sudo cp /media/internal/bootlogo/<bright shutdown image> palm-logo-down-bright.png<br />
sudo cp palm-logo-down.png palm-logo.png<br />
sudo cp palm-logo-down-bright.png palm-logo-bright.png<br />
</nowiki></pre><br />
<br />
'''Step Three'''<br />
Backup the current logo images, if you haven't already.<br />
<pre><nowiki><br />
sudo cp -ip /usr/palm/sysmgr/images/palm-logo.png /usr/palm/sysmgr/images/palm-logo.png.orig<br />
sudo cp -ip /usr/palm/sysmgr/images/palm-logo-bright.png /usr/palm/sysmgr/images/palm-logo-bright.png.orig<br />
</nowiki></pre><br />
<br />
'''Step Four'''<br />
Delete the current logo images and replace them with symlinks to the files in our new directory in /opt<br />
<pre><nowiki><br />
cd /usr/palm/sysmgr/images/<br />
sudo rm palm-logo-bright.png<br />
sudo rm palm-logo.png<br />
sudo ln -s ../../../../../opt/share/bootimages/palm-logo-bright.png palm-logo-bright.png<br />
sudo ln -s ../../../../../opt/share/bootimages/palm-logo.png palm-logo.png<br />
</nowiki></pre><br />
<br />
'''Step Five'''<br />
Back up and edit /etc/init.d/start_animation, adding the switching of the files<br />
<pre><nowiki><br />
sudo cp -ip /etc/init.d/start_animation /etc/init.d/start_animation.orig<br />
sudo -e /etc/init.d/start_animation<br />
</nowiki></pre><br />
Before the line starting with ''if [ -x /usr/bin/luna-send'' add the following:<br />
<pre><nowiki><br />
ok=no<br />
if [ -f /opt/share/bootimages/palm-logo-up.png ] && \<br />
[ -f /opt/share/bootimages/palm-logo-up-bright.png ] && \<br />
[ -f /opt/share/bootimages/palm-logo-down.png ] && \<br />
[ -f /opt/share/bootimages/palm-logo-down-bright.png ] ; then<br />
cp /opt/share/bootimages/palm-logo-down.png /opt/share/bootimages/palm-logo.png<br />
cp /opt/share/bootimages/palm-logo-down-bright.png /opt/share/bootimages/palm-logo-bright.png<br />
ok=yes<br />
fi<br />
</nowiki></pre><br />
At the very end of the file, add the following:<br />
<pre><nowiki><br />
if [ "$ok" = "yes" ] ; then<br />
sleep 5<br />
cp /opt/share/bootimages/palm-logo-up.png /opt/share/bootimages/palm-logo.png<br />
cp /opt/share/bootimages/palm-logo-up-bright.png /opt/share/bootimages/palm-logo-bright.png<br />
fi<br />
</nowiki></pre><br />
<br />
'''Step Six'''<br />
Restart Luna and watch your awesome new logos.<br />
<pre><nowiki><br />
pkill LunaSysMgr<br />
</nowiki></pre><br />
<br />
== Boot Themes==<br />
<br />
You can find more boot themes at http://www.prethemer.com/logos. <br />
<br />
'''Title:''' Old Default Theme<br />
<br />
'''Author:''' Palm<br />
<br />
[[Image:Palm-logo.png]] <br />
[[Image:Palm-logo-bright.png]]<br />
<br />
'''Title:''' New Default Theme<br />
<br />
'''Author:''' HP<br />
<br />
[[Image:Hp-logo.png]] <br />
[[Image:Hp-logo-bright.png]]<br />
<br />
'''Title:''' HP-Palm Theme<br />
<br />
'''Author:''' cwgtex, credit to Palm and HP for original images<br />
<br />
[[Image:Hpalm-logo.png]] <br />
[[Image:Hpalm-logo-bright.png]]<br />
<br />
'''Title:''' Linux Inside Tux bright Edition<br />
<br />
'''Author:''' MmO<br />
<br />
[[Image:Linux-Inside.png]] <br />
[[Image:Linux-Inside-Bright.png]] <br />
<br />
'''Title:''' Tux - got root?<br />
<br />
'''Author:''' JackieRipper<br />
<br />
[[Image:Jackieripper-palm-logo.png]] <br />
[[Image:Jackieripper-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' Red and Green<br />
<br />
'''Author:''' JackieRipper<br />
<br />
[[Image:Jackieripper2-palm-logo-up.png]] <br />
[[Image:Jackieripper2-palm-logo-up-bright.png]] <br />
[[Image:Jackieripper2-palm-logo-down.png]] <br />
[[Image:Jackieripper2-palm-logo-down-bright.png]]<br />
<br />
<br />
'''Title:''' Blue Tux<br />
<br />
'''Author:''' pEEf<br />
<br />
[[Image:PEEf-palm-logo.png]] <br />
[[Image:PEEf-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' Glassy Tux<br />
<br />
'''Author:''' fish199902<br />
<br />
[[Image:Fish109902-palm-logo.png]] <br />
[[Image:Fish109902-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' GunTux<br />
<br />
'''Author:''' Xaeonis<br />
<br />
[[Image:Xaeonis-GunTux-palm-logo.png]]<br />
[[Image:Xaeonis-GunTux-palm-logo-bright.png]]<br />
<br />
'''Title:''' bleeding apples<br />
<br />
'''Author:''' predatory1<br />
<br />
[[Image:Apv-palm-logo.png]]<br />
[[Image:Apv-Palm-logo-bright.png ]]<br />
<br />
'''Title:''' Just Pre<br />
<br />
'''Author:''' JP_Money<br />
<br />
[[Image:Just-pre-palm-logo.png]]<br />
[[Image:Just-pre-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' Jumpman Pre<br />
<br />
'''Author:''' dave b<br />
<br />
[[Image:daveb-jumpman-pre-palm-logo.png]] <br />
[[Image:daveb-jumpman-pre-palm-logo-bright.png]]<br />
<br />
'''Title:''' Transform<br />
<br />
'''Author:''' Ahabenezer<br />
<br />
[[Image:autobot-palm-logo.png]] <br />
[[Image:decepticon-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' Linux<br />
<br />
'''Author:''' 473x15<br />
<br />
[[Image:linux2-palm-logo.png]]<br />
[[Image:Linux-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' Zombie Palm<br />
<br />
'''Author:''' Steel Shadow<br />
<br />
[[Image:Zombie-palm-logo.png]]<br />
[[Image:Zombie-palm-logo-bright.png]]<br />
<br />
<br />
'''Title:''' Serenity (Firefly)<br />
<br />
'''Author:''' HelloNNNewman<br />
<br />
[[Image:Serenity_4-4.png]]<br />
[[Image:Serenity_5-5.png]]<br />
<br />
<br />
'''Title:''' Serenity (Firefly)<br />
<br />
'''Author:''' HelloNNNewman<br />
<br />
[[Image:Firefly 1.png]]<br />
[[Image:Firefly 2_fire.png]]<br />
<br />
<br />
'''Title:''' Shodan (SS2)<br />
<br />
'''Author:''' osat3ch<br />
<br />
[[Image:Palm-logo_shodan.png]]<br />
[[Image:Palm-logo-bright_shodan.png]]</div>SmartDeviceResource1http://wiki.webos-internals.org/index.php?title=How_to_solve_3G_data_problems&diff=9236How to solve 3G data problems2010-02-28T22:41:53Z<p>SmartDeviceResource1: /* Case 6: Voice mail number not working on tap and hold key 1 */</p>
<hr />
<div>= 3G in General and APN =<br />
A working 3G data connection shows up in the top status row of the Pre. That row shows either 3G, G or E (both for 2G) on the left of the signal strength icon on GSM models, provided that the WiFi is off or WiFi is not connected. Once WiFI is connected its icon will overwrite the 3G icon. That way you always know what connection is active for data connections.<br />
Many have reported 3G data connection problems, especially when using the Pre on 'non-supported networks' (to be defined). An APN is an Access Point Name, that is required to connect to that named network. One of the contributing factors to 3G problems is that APN and information about that network such as a passwords are sometimes not correct in the Pre's database of networks/operators. This Wiki is intended to solve 3G (and APN) problems.<br />
<br />
= Type of 3G or APN Problems =<br />
# Connection to networks in countries where the Pre is not sold through Palm's channels: some work out of the box, some experience problems as follows.<br />
# Network operator not present in the Pre Carrier database: reported in the forum that this can be solved, see case 2<br />
# Network operator present, but entries in Database are wrong: reported in the forum that this can be solved, see case 3<br />
# Manual settings on Phone preferences cannot be saved: not sure, probably network operator not present in database, see case 2<br />
# Data connection not established while DB entries seem OK: can be solved in many cases, see case 5<br />
# Voicemail number wrong or not present: can be solved, see case<br />
<br />
= Tools needed =<br />
If the problem cannot be solved by using manual settings under Phone preferences, you need some tools to modify some Pre files. (List of tools to be added)<br />
* If you have a PC, probably WebOS Quick Install is easy to install and use for beginners [http://forums.precentral.net/canuck-software/228310-webos-quick-install-v3-01-a.html#post2194980]<br />
* Likely you'll need an SQL Database editor. A free SQLite database will do (reference needed)<br />
<br />
= How to Determine which Problem Case(s) is (are) Applicable =<br />
This is tricky and needs some work.....<br />
# Check whether your carrier/operator is listed in the Pre carrier database. Some copies of the carrier database are availablke in this thread [http://forums.precentral.net/gsm-pre/227466-adjusting-carrier-settings-ssh-into-device-guide-help-dummies-does-exist.html#post2184808]. If your carrier is not listed, you'll have to modify an existing other carrier's data into your carrier. It requires both a modified carrier DB entry and one or more modified data entries. See case 2.<br />
# Check whether the data section of a listed carrier contains the right information. If the settings are not right, you have to modify the data section of your carrier. Probably modifying it by manual settings under phone preferences is easiest, for some nice screen shots see Marc's Blog [http://blog.marc-seeger.de/2010/01/17/How_to_change_the_APN_on_the_Palm_Pre]. If manual settings does not work for you, you'll have to change the databases located on the Pre, see case 3.<br />
# Some have reported that even though all setting look OK, still there is no 3G data connection. One of the causes is that as of 1.3.1 some networks/carriers require PPP options for user name and password, see case 5.<br />
<br />
= Forum threads that discuss or solve the 3G problem =<br />
Since this How to is just starting, the following threads contains many working suggestions. Please add any thread you find valuable.<br />
# Best how-to so far: Modifying WebOS carrier network settings[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079]<br />
# APN Problems with 1.3.1/1.3.5 [http://forums.precentral.net/gsm-pre/222248-apn-problems-1-3-1-1-3-5-a.html#post2123450]<br />
# Carrier/APN settings for 1.13 German and 1.21 US[http://forums.precentral.net/gsm-pre/210030-carrier-apn-settings-1-13-german-1-21-us.html#post1982622]<br />
# Adjusting Carrier Settings / SSH into device guide/help for dummies...does it exist?[http://forums.precentral.net/gsm-pre/227466-adjusting-carrier-settings-ssh-into-device-guide-help-dummies-does-exist.html#post2184808]<br />
# MMS not working MMS not working [http://forums.precentral.net/gsm-pre/220426-mms-not-working.html#post2100783]<br />
# Data still not working in 1.3.1 UK (Multi-page thread 1 2 3 ... Last Page)[http://forums.precentral.net/gsm-pre/216478-data-still-not-working-1-3-1-uk.html#post2056591]<br />
# Confirmed manual Carrier/APN settings in webOS 1.3[http://forums.precentral.net/gsm-pre/214348-confirmed-manual-carrier-apn-settings-webos-1-3-a.html#post2032970]<br />
# Any GSM pre that has a working voicemail shortcut (key 1)[http://forums.precentral.net/gsm-pre/215208-any-gsm-pre-has-working-voicemail-shortcut-key-1-a.html#post2042178]<br />
<br />
= Case 2: carrier/operator not present in the Pre carrier database =<br />
(please record what to do)<br />
<br />
= Case 3: Incorrect data base settings: How to Modify WebOS carrier network settings =<br />
(thanks palmdoc2005 for his excellent writeup)<br />
Please WiKi-expert,format the lists and sublists below<br />
<br />
Assuming one has an unlocked GSM Pre which is activated, has network access via Wifi but may have 3G data connection problems due to incorrect carrier connection settings. Also assuming manual (data) setting under Phone preferences is OFF. (need a separate case how to handle ON)<br><br />
Modifying the file CarrierNetworkSettings.db3 found in /usr/lib/luna/ may fix the problem<br />
You of course also need to first check what the correct data network settings (APN/login/username etc) for your carrier are (call them up if you are unsure). Need some reference here of a list of carrier settings ......<br />
<br />
'''Step 1)''' Copying the carrier network database file to your PC<br />
<br>Several methods<br />
<br />
::''method a)'' Obtain the database from the webosdoctor image<br />
:::Download the image appropriate for your device. <br />
:::Use 7zip to unpack the file.<br />
:::The required DB file is found in : webosdoctorp100eww-wr\resources\webOS\nova-cust-image-castle.rootfs.tar\nova-cust-image-castle.rootfs\usr\lib\luna\CarrierNetworkSettings.db3<br />
<br />
::''method b)'' Obtain the database from the device itself. You can:<br />
::: either 1) use Putty<br />
::::*SSH to to your Pre using Putty, type<br />
:::::cp /usr/lib/luna/CarrierNetworkSettings.db3 /media/internal. This will copy the database file to the internal storage.<br />
::::*Put your Pre into USB disk mode and copy the database file to your machine.<br />
<br />
:::or 2) use Internalz<br />
::::*Navigate to /usr/lib/luna/ and copy CarrierNetworkSettings.db3 to /media/internal<br />
::::*Put your Pre into USB disk mode and copy the database file to your machine.<br />
<br />
:::or 3) Use WebOS Quick Install tool<br />
::::*Put your Pre in Developer Mode. Attach it to the PC through the USB cable and select Just Charge<br />
::::*Launch WebOS Quick Install<br />
::::*Select Receive File from the menu<br />
::::*Enter /usr/lib/luna/CarrierNetworkSettings.db3<br />
::::*Select destination folder in your PC<br />
<br />
<br />
'''Step 2)''' Editing the database on your PC<br />
<br />
I suppose it is prudent to back up the file before making modifications<br />
<br />
a) Obtain a free SQLite database editor<br />
:* either SQLite Database Browser<br />
:* or Firefox SQLite manager extension<br />
<br />
b) Open the carrier network db3 file in SQLite database browser<br />
Click on the Browse Data tab<br />
<br />
:* From the drop down menu, select the ..._CarrierNetworkSettings table<br />
:* Locate your carrier by browsing or searching the table<br />
::* If there are many entries, like for tmobile, find a local carrier that for sure is located in your country<br />
::* Note country code (need fieldname ref here) and find your carrier by finding a 'tmobile' that has the same country code<br />
::<br />
:* You might want to check the voicemail number <br />
::* Check the field voicemailNumber<br />
::* Change the voicemail number if needed<br />
:* Note the 13 digit number ID value of your carrier, such as 2199023255831, at the end of the record on the right hand side<br />
::<br />
:* From the drop down menu, now select another table: the ..._DataConnectionSettings table<br />
:* Locate that noted ID in the dataconnections table<br />
::Now you can edit the APN , username and password if these field to don contain the right information for your carrier<br />
:: Don't forget to save each changed field, if required by the tool used!<br />
:* Save the file<br />
<br><br />
'''Step 3)''' Copying the database back to the device<br />
<br />
:*Use Jason Robitaille's WebOS Quick Install tool<br />
::*Click on Tools - Send File and point it to the amended database file.<br />
::*As the destination folder use /usr/lib/luna/ and click Send To Device!<br />
::*Repeat this, only this time use /var/luna/data/ as the destination folder.<br />
<br />
'''Step 4)''' Reboot your Pre. That should be it.....<br />
<br />
= Case 5: all settings seem OK, yet no connection =<br />
(Thanks to xioq)<br />
<br> [[This problem seems to be solved as of webOS 1.4 (just one confirmation)]]<br />
<br />
A patch is available for solving this problem, see [http://forums.precentral.net/webos-patches/231903-patch-gsm-if-user-pw-required-ppp.html#post2241592http://forums.precentral.net/webos-patches/231903-patch-gsm-if-user-pw-required-ppp.html#post2241592]<br />
<br />
The following procedure is an alternative and results in the same modification as the patch does. The steps:<br />
# Fix CarrierNetworkSettings.db3, see Case Incorrect data base settings<br />
# Modify /etc/ppp/options-gsm<br />
<br />
The otions-gsm file has to be edited and put back on the Pre. The options are listed below, add them just before the end of file.<br />
<pre><nowiki><br />
#noccp <br />
#novj <br />
#show-password <br />
#nobsdcomp <br />
#noipdefault <br />
#nodeflate <br />
user "vodafone" <br />
password "vodafone" <br />
</nowiki></pre><br />
<br />
<br />
The lines that are marked with # in front of them seem not to be required. They have been tried out to solve this problem. So just add your user/password lines in there and that should solve the problem. There are also reports that just having empty strings for user and passwords (so just "") works sometimes. And there are reports that the vodafone setting works on other networks that would need a different setting. If it does notwork, find the right settings for your network/operator. (need a web reference for those)<br />
<br />
While no one is sure yet, why this problem has occurred since the 1.3.1 update - it's good to see it has been resolved. It has been reported in the forum this works for webOS 1.3.5.2 (GSM) and for 1.3.5.1 (Spint on a GSM model)<br />
<br />
=Case 6: Voice mail number not working on tap and hold key 1 =<br />
When tap & hold key 1, a stored voice mail number is automatically dialed. If the Pre does not have <br />
the voicemail number on record, it asks to provide one (as of webOS 1.4?). This <br />
procedure however does not seem to work for the GSM models.For GSM models there are voicemail number entries in the Pre carrier database. However, about 50% of the 350 provider entries in the Pre's Carrier database have not filled out that <br />
entry. <br />
* Manually entering a voice mail number into the CarrierDB makes the 1 short key working. Instructions to edit the voicemail number, see Case 3<br />
<br />
[[There is one exception.]] If manual settings on phone preferences has been activated once before the <br />
voicemail number is entered manually in the CarrierDB, the changed voice mail number will <br />
not be copied again to the manual settings DB. Manual setting apparently copies the complete <br />
record of the current provider as an override in a DB called PalmDatabase.db3. <br />
<br />
So if manual setting has been activated before the carrier DB is changed, this PalmDatabase.db3 has to be updated too! <br />
There is a fairly complicated way to do this for sure on the Pre itself, see[http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-7.html#post2046475] <br />
<br />
There is a simple way to check which record/database is being used. Just give the regular carrier DB a different voicemail number compared to the PalmDatabase. Check preferences on the phone App and it displays which voicemail number is active.<br />
<br />
If you are prepared to take some (limited?) risk, one could do the following. A small risk is that the DB will be changed on your Pre during the time you edit it on the PC. So close all apps on the Pre.<br />
<br>need more details here......<br />
# Try this procedure first, and stop before copying the DB back to the Pre. Then do it quickly all over again<br />
# Terminate all programs running on the Pre<br />
# The database to be changed is /var/luna/data/dbdata/PalmDatabase.db3<br />
# Copy the DB to your windows PC. <br />
# Run SQlite (freeware), open PalmDatabase.db3<br />
# Find the record/table called com_palm_data_carriernetworksettings_DataConnectionSettings (same name a normal procedure)<br />
# Change the voicemail (just by clicking, no SQL)<br />
# Copy the PalmDatabase back to the Pre.<br />
# Boot the Pre <br />
<br />
A small risk is that the DB will have been changed on your Pre during the time oine edits that DB on a PC. So close all apps <br />
first. Try this procedure first, then do it quickly all over again, I have done this <br />
and it worked.</div>SmartDeviceResource1