WebOS Internals - User contributions [en]

Unofficial networks compatiblity list

2010-04-03T08:32:23Z

Czechdev: Czech Republic

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

The "App Catalog" column percent number represent the total number of available Catalog apps compared to the [http://www.precentral.net/app-gallery/app-catalog/ official PreCentral count]. You can get the available apps count by searching for an empty string on the main App Catalog app screen.

= Rebel SIM with webOS 1.4.0 =
'''Note that the Rebel SIM II is officially not compatible with webOS 1.4.0.''' Many users have experienced problems including "SOS only" mode, damaging their SIM cards, no data connection at all or the Always roaming problem. There is an ongoing discussion at [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working.html PreCentral.net forums].

The current best workaround (by user sconix) for this problem is to load the phone's modem with an older firmware from a previous webOS release (1.3.5.2 is sufficient), see [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working-10.html#post2277400 this post] for more info.

In short, you have to extract the ''castleumtsfw.tar'' from ''webOS.tar'' from the Doctor image. Then copy it to the ''/tmp'' directory on the phone a run ''PmModemUpdater -m -e -o </tmp/castleumtsfw.tar''.

= Pre GSM =

{| border="1"
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! App Catalog
! webOS version
! Notes
! Tested by
|-
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| Belgium
| Base
|
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
|
| bdagirl
|-
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
|
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes, 41 % w/ paid apps
| 1.4.1
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested voice/SMS roaming on A1 in Austria and Orange in Slovakia.
QWERTZ (Germany O2 Unlocked)
| Czechdev, Georgo
|-
| Finland
| Sonera
(FI Sonera)
| Yes
| Yes
| Yes
| Yes
| Yes
| No
| 1.1.3-1.4.0
| QWERTZ O2 unlocked
* App Catalog opens but no apps available
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
** USERNAME and PASSWORD should be left empty. Settings are saved OK, but when checking the settings, in the USERNAME field there is text ''hs_null'', just like in case of Tele2 Sweden. MMS works, nonetheless.
| Lemstil
|-
| Finland
| dna finland
|
|
|
|
|
|
|
|
| jmpre
|-
| France
| Bouygues Telecom (Nomad Card)
| Yes
| Yes
| N/T
| N/T
| Yes
|
| 1.3.1-1.3.5.2
| QWERTZ (German)Unlocked, (This Palm Pre was activated with Orange Sim Card the first time)
| Yannick56
|-
| Greece
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| Grenada
| LIME
|
|
|
|
|
|
|
|
| wikka
|-
| Honduras
| TIGO
| Yes
| Yes
| NT
| Yes
| No
| No
| 1.4.0
| QWERTZ German O2 unlocked (No need for rebel sim card)
* App Catalog changes on and off daily, can update my apps, but no other apps show.
* I am not sure how to test msm or 3G, but only E shows so far, internet is really fast though.
* I have been told it also works with Digicel and Claro networks without a rebel sim card.
| erapalo
|-
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
|
| kyll05, windflower
|-
| India
| Vodafone
|
|
|
|
|
|
|
|
| Sukh
|-
| India
| Vodafone
| Yes
| Yes
| N/T
| Yes
| N/T
|
| 1.3.1-1.3.5.2
| QWERTZ (Germany Unlocked)
| Rohit
|-
| Italy
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.3.x
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
| iDG
|-
| Malaysia
| Digi
|
|
|
|
|
|
|
|
| palmdoc2005
|-
| Malaysia
| Celcom
|
|
|
|
|
|
|
|
| Surrinder
|-
| Malaysia
| Maxis
|
|
|
|
|
|
|
|
| AHSS
|-
| The Netherlands
| KPN
|
|
|
|
|
|
|
|
| spud101
|-
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| New Zealand
| Vodafone
|
|
|
|
|
|
|
|
| kiwiterry
|-
| Philippines
| Globe
|
|
|
|
|
|
|
|
| alcarun, jester
|-
| Philippines
| Smart
|
|
|
|
|
|
|
|
| alcarun
|-
| Romania
| Orange
| Yes
| Yes
| N/T
| Yes
| Yes
| No
| 1.3.5.2 - 1.4.0
| QWERTZ O2 unlocked (first activated in Orange Ro)
| hertzi
|-
| Singapore
| starhub
|
|
|
|
|
|
|
|
| NiceGuy
|-
| Singapore
| M1
|
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| Sweden
| Tele2
| Yes
| Yes
| No
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| Sweden
| Telenor
|
|
|
|
|
|
|
|
| steveaw
|-
| Switzerland
| Orange
| yes
| yes
| yes
| yes
| yes
| yes (not complete)
| all up to 1.4
|
| Lux
|-
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
|
| Kenjo2009
|-
| Turkey
| Turkcell
| Yes
| Yes
| No/Yes*
| Yes
| Yes
| No
|1.3.5.2
| * After manually edit MMS settings in Carrier DB, it works... MMS APN=mms USERNAME=mms PASSWORD=mms MMSC=http://mms.turkcell.com.tr/servlets/mms MMS_PROXY=212.252.169.217 Max MMS Size= 500 KB
| cryptooth
|-
| UAE
| Etisalat
|
|
|
|
|
|
|
|
| p25o1
|}

* '''N/A''' -- not available
* '''N/T''' -- not tested
* '''AR''' -- always roaming

User talk:Anthonynate

2010-03-29T10:30:03Z

Czechdev:

hello everybody...i have a problem.i have Palm pre with O2,i want to use it in another country but i can't bypass activation screen and i can't write Konami code.somebody can help my pleaaaaaaaaaaaase....

Have you tried Meta-doctoring ([[Application:MetaDoctor]]) your Pre? [[User:Czechdev|Czechdev]]

Unofficial networks compatiblity list

2010-03-03T16:31:31Z

Czechdev: added RSC compatibility workaround using modem flash

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

The "App Catalog" column percent number represent the total number of available Catalog apps compared to the [http://www.precentral.net/app-gallery/app-catalog/ official PreCentral count]. You can get the available apps count by searching for an empty string on the main App Catalog app screen.

= Rebel SIM with webOS 1.4.0 =
'''Note that the Rebel SIM II is officially not compatible with webOS 1.4.0.''' Many users have experienced problems including "SOS only" mode, damaging their SIM cards, no data connection at all or the Always roaming problem. There is an ongoing discussion at [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working.html PreCentral.net forums].

The current best workaround (by user sconix) for this problem is to load the phone's modem with an older firmware from a previous webOS release (1.3.5.2 is sufficient), see [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working-10.html#post2277400 this post] for more info.

In short, you have to extract the ''castleumtsfw.tar'' from ''webOS.tar'' from the Doctor image. Then copy it to the ''/tmp'' directory on the phone a run ''PmModemUpdater -m -e -o </tmp/castleumtsfw.tar''.

= Pre GSM =

{| border="1"
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! App Catalog
! webOS version
! Notes
! Tested by
|-
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| Belgium
| Base
|
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
|
| bdagirl
|-
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
|
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| N/A
| Yes, 24 %
| 1.4.0
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested voice/SMS roaming on A1 in Austria and Orange in Slovakia.
| Czechdev
|-
| Finland
| Sonera (Teliasonera Finland)
| Yes
| Yes
| Yes
| Yes
| Yes
| No
| 1.1.3-1.4.0
| QWERTZ O2 unlocked
* App Catalog changes on and off daily
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
| Lemstil
|-
| Finland
| dna finland
|
|
|
|
|
|
|
|
| jmpre
|-
| France
| Bouygues Telecom (Nomad Card)
| Yes
| Yes
| N/T
| N/T
| Yes
|
| 1.3.1-1.3.5.2
| QWERTZ (German)Unlocked, (This Palm Pre was activated with Orange Sim Card the first time)
| Yannick56
|-
| Greece
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| Grenada
| LIME
|
|
|
|
|
|
|
|
| wikka
|-
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
|
| kyll05, windflower
|-
| India
| Vodafone
|
|
|
|
|
|
|
|
| Sukh
|-
| India
| Vodafone
| Yes
| Yes
| N/T
| Yes
| N/T
|
| 1.3.1-1.3.5.2
| QWERTZ (Germany Unlocked)
| Rohit
|-
| Italy
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.3.x
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
| iDG
|-
| Malaysia
| Digi
|
|
|
|
|
|
|
|
| palmdoc2005
|-
| Malaysia
| Celcom
|
|
|
|
|
|
|
|
| Surrinder
|-
| Malaysia
| Maxis
|
|
|
|
|
|
|
|
| AHSS
|-
| The Netherlands
| KPN
|
|
|
|
|
|
|
|
| spud101
|-
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| New Zealand
| Vodafone
|
|
|
|
|
|
|
|
| kiwiterry
|-
| Philippines
| Globe
|
|
|
|
|
|
|
|
| alcarun, jester
|-
| Philippines
| Smart
|
|
|
|
|
|
|
|
| alcarun
|-
| Singapore
| starhub
|
|
|
|
|
|
|
|
| NiceGuy
|-
| Singapore
| M1
|
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| Sweden
| Tele2
| Yes
| Yes
| No
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| Sweden
| Telenor
|
|
|
|
|
|
|
|
| steveaw
|-
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
|
| Kenjo2009
|-
| Turkey
| Turkcell
| Yes
| Yes
| No/Yes*
| Yes
| Yes
| No
|1.3.5.2
| * After manually edit MMS settings in Carrier DB, it works... MMS APN=mms USERNAME=mms PASSWORD=mms MMSC=http://mms.turkcell.com.tr/servlets/mms MMS_PROXY=212.252.169.217 Max MMS Size= 500 KB
| cryptooth
|-
| UAE
| Etisalat
|
|
|
|
|
|
|
|
| p25o1
|}

* '''N/A''' -- not available
* '''N/T''' -- not tested
* '''AR''' -- always roaming

Unofficial networks compatiblity list

2010-03-02T11:19:49Z

Czechdev: added 1.4.0 Rebel SIM incompatibility note

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

The "App Catalog" column percent number represent the total number of available Catalog apps compared to the [http://www.precentral.net/app-gallery/app-catalog/ official PreCentral count]. You can get the available apps count by searching for an empty string on the main App Catalog app screen.

= Rebel SIM with webOS 1.4.0 =
'''Note that the Rebel SIM II is officially not compatible with webOS 1.4.0.''' Many users have experienced problems including "SOS only" mode, damaging their SIM cards, no data connection at all or the Always roaming problem. There is an ongoing discussion at [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working.html PreCentral.net forums]. The current workaround is to [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working-4.html#post2264420 doctor your phone to Sprint 1.0.4] and then run the Update app to get Sprint 1.4.0 firmware. Some Telcel users also get their phone working by [http://forums.precentral.net/gsm-pre/233433-last-i-got-1-4-working-mexico-telcel-pre-d.html editing the Doctor image].

= Pre GSM =

{| border="1"
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! App Catalog
! webOS version
! Notes
! Tested by
|-
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| Belgium
| Base
|
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
|
| bdagirl
|-
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
|
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| N/A
| Yes, 23 %
| 1.3.5.2
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested voice/SMS roaming on A1 in Austria and Orange in Slovakia. No data at all + AR with webOS 1.4.0.
| Czechdev
|-
| Finland
| Sonera (Teliasonera Finland)
| Yes
| Yes
| Yes
| Yes
| Yes
| No
| 1.1.3-1.4.0
| QWERTZ O2 unlocked
* App Catalog changes on and off daily
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
| Lemstil
|-
| Finland
| dna finland
|
|
|
|
|
|
|
|
| jmpre
|-
| France
| Bouygues Telecom (Nomad Card)
| Yes
| Yes
| N/T
| N/T
| Yes
|
| 1.3.1-1.3.5.2
| QWERTZ (German)Unlocked, (This Palm Pre was activated with Orange Sim Card the first time)
| Yannick56
|-
| Greece
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| Grenada
| LIME
|
|
|
|
|
|
|
|
| wikka
|-
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
|
| kyll05, windflower
|-
| India
| Vodafone
|
|
|
|
|
|
|
|
| Sukh
|-
| India
| Vodafone
| Yes
| Yes
| N/T
| Yes
| N/T
|
| 1.3.1-1.3.5.2
| QWERTZ (Germany Unlocked)
| Rohit
|-
| Italy
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.3.x
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
| iDG
|-
| Malaysia
| Digi
|
|
|
|
|
|
|
|
| palmdoc2005
|-
| Malaysia
| Celcom
|
|
|
|
|
|
|
|
| Surrinder
|-
| Malaysia
| Maxis
|
|
|
|
|
|
|
|
| AHSS
|-
| The Netherlands
| KPN
|
|
|
|
|
|
|
|
| spud101
|-
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| New Zealand
| Vodafone
|
|
|
|
|
|
|
|
| kiwiterry
|-
| Philippines
| Globe
|
|
|
|
|
|
|
|
| alcarun, jester
|-
| Philippines
| Smart
|
|
|
|
|
|
|
|
| alcarun
|-
| Singapore
| starhub
|
|
|
|
|
|
|
|
| NiceGuy
|-
| Singapore
| M1
|
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| Sweden
| Tele2
| Yes
| Yes
| No
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| Sweden
| Telenor
|
|
|
|
|
|
|
|
| steveaw
|-
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
|
| Kenjo2009
|-
| Turkey
| Turkcell
| Yes
| Yes
| No/Yes*
| Yes
| Yes
| No
|1.3.5.2
| * After manually edit MMS settings in Carrier DB, it works... MMS APN=mms USERNAME=mms PASSWORD=mms MMSC=http://mms.turkcell.com.tr/servlets/mms MMS_PROXY=212.252.169.217 Max MMS Size= 500 KB
| cryptooth
|-
| UAE
| Etisalat
|
|
|
|
|
|
|
|
| p25o1
|}

* '''N/A''' -- not available
* '''N/T''' -- not tested
* '''AR''' -- always roaming

How to solve 3G data problems

2010-02-21T11:44:21Z

Czechdev: there is G for GPRS and E for EDGE shown

= 3G in General and APN =
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.
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.

= Type of 3G or APN Problems =
# 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 follow.
# Network operator not present in the Pre Carrier database: reported in the forum that this can be solved
# Network operator present, but entries in Database are wrong: reported in the forum that this can be solved
# Manual settings on Phone preferences cannot be saved: not sure, probably network operator not present in database
# Data connection not established while DB entries seem OK: can be solved in many cases
# Voicemail number wrong or not present: can be solved

= How to Determine which Problem Case(s) is (are) Applicable =
This is tricky and needs some work.....

= Forum threads that discuss or solve the 3G problem =
Since this How to is just starting, the following threads contains many working suggestions. Please add any thread you find valuable.
# Best how-to so far: Modifying WebOS carrier network settings[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079]
# 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]
# 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]
# 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]
# MMS not working MMS not working [http://forums.precentral.net/gsm-pre/220426-mms-not-working.html#post2100783]
# 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]
# 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]
# 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]

= Case: Incorrect data base settings: How to Modify WebOS carrier network settings =
(thanks palmdoc2005 for his excellent writeup)
Please WiKi-expert,format the lsist and sublists below

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.
Modifying the file CarrierNetworkSettings.db3 found in /usr/lib/luna/ may fix the problem
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 refenrence here of carrier settings ......

'''Step 1)''' Copying the carrier network database file to your PC
<br>Several methods

::''method a)'' Obtain the database from the webosdoctor image
:::Download the image appropriate for your device. Use 7zip to unpack the file.
:::The file is found in : webosdoctorp100eww-wr\resources\webOS\nova-cust-image-castle.rootfs.tar\nova-cust-image-castle.rootfs\usr\lib\luna\CarrierNetworkSettings.db3

::''method b)'' Obtain the database from the device itself. You can:
::: either 1) SSH to to your Pre using Putty, type
::::cp /usr/lib/luna/CarrierNetworkSettings.db3 /media/internal. This will copy the database file to the internal storage.
::::Put your Pre into USB disk mode and copy the database file to your machine.

:::or 2) use Internalz
::::navigate to /usr/lib/luna/ and copy CarrierNetworkSettings.db3 to /media/internal
::::Put your Pre into USB disk mode and copy the database file to your machine.

:::or 3) Use WebOS Quick Install tool
::::Put your Pre in Developer Mode. Attach to PC and select Just Charge
::::Launch WOQI
::::Select Receive File from the menu
::::enter /usr/lib/luna/CarrierNetworkSettings.db3
::::select destination folder in your PC

'''Step 2)''' Editing the database on your PC

I suppose it is prudent to back up the file before making modifications

a) Obtain a free SQLite database editor
- SQLite Database Browser
or
-Firefox SQLite manager extension

b) Open the carrier network db3 file in SQLite database browser
Click on the Browse Data tab

- From the drop down menu, select the ..._CarrierNetworkSettings table
- Locate your carrier by browsing or searching the table
- Note the 13 digit number such as 2199023255831 ID value of the carrier at the end of the record on the right hand side
- Change the voicemail number if desired: Locate your carrier by browsing or searching the table
- check and enter the field voicemailNumber

- From the drop down menu, select the ..._DataConnectionSettings table
- Locate that same ID in the dataconnections table
Now you can edit the APN , username and password if these have been changed by your carrier but not updated in the Palm database

Save the file

Step 3) Copying the database back to the device

Use Jason Robitaille's WebOS Quick Install tool
Click on Tools - Send File and point it to the amended database file.
As the destination folder use /usr/lib/luna/ and click Send To Device!
Repeat this, only this time use /var/luna/data/ as the destination folder.

Reset your Pre. That should be it. I hope.

= Case: all settings OK, yet no connection =
(Thanks to xioq)

The steps:
# Fix CarrierNetworkSettings.db3, see Case Incorrect data base settings
# Modify /etc/ppp/options-gsm

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.
<pre><nowiki>
#noccp

#novj

#show-password

#nobsdcomp

#noipdefault

#nodeflate

user "vodafone"

password "vodafone"
</nowiki></pre>

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 the user/password lines in there and it still seem to work. There are also reports that just having empty strings for user and passwords (so just "") works. If not, fins the right settings for your network/operator. (need a web reference for those)

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)

Unofficial networks compatiblity list

2010-02-14T13:22:59Z

Czechdev: removed the Radio column, added App Catalog column to the table

Unofficial networks compatiblity list

2010-02-06T17:52:39Z

Czechdev:

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

= Pre =

{| border="1"
! Radio
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! webOS version
! Notes
! Tested by
|-
| GSM
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| GSM
| Belgium
| Base
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| GSM
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
| bdagirl
|-
| GSM
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| GSM
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| N/A
| 1.3.5.2
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested roaming on A1 in Austria.
| Czechdev
|-
| GSM
| Finland
| Sonera (Teliasonera Finland)
| Yes
| Yes
| Yes
| Yes (EDGE & GPRS)
| Yes
| 1.3.5.2
| QWERTZ O2 unlocked
* App Catalog empty / not working since 1.3.5.2
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
| Lemstil
|-
| GSM
| Finland
| dna finland
|
|
|
|
|
|
|
| jmpre
|-
| GSM
| Greece
| Wind
| Yes
| Yes
| Not Tested
| Yes
| Yes
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| GSM
| Grenada
| LIME
|
|
|
|
|
|
|
| wikka
|-
| GSM
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
| kyll05, windflower
|-
| GSM
| India
| Vodafone
|
|
|
|
|
|
|
| Sukh
|-
| GSM
| Italy
| Wind
| Yes
| Yes
| Not tested
| Yes
| Yes
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| GSM
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| GSM
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| 1.3.x
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
| iDG
|-
| GSM
| Malaysia
| Digi
|
|
|
|
|
|
|
| palmdoc2005
|-
| GSM
| Malaysia
| Celcom
|
|
|
|
|
|
|
| Surrinder
|-
| GSM
| Malaysia
| Maxis
|
|
|
|
|
|
|
| AHSS
|-
| GSM
| The Netherlands
| KPN
|
|
|
|
|
|
|
| spud101
|-
| GSM
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| GSM
| New Zealand
| Vodafone
|
|
|
|
|
|
|
| kiwiterry
|-
| GSM
| Philippines
| Globe
|
|
|
|
|
|
|
| alcarun, jester
|-
| GSM
| Philippines
| Smart
|
|
|
|
|
|
|
| alcarun
|-
| GSM
| Singapore
| starhub
|
|
|
|
|
|
|
| NiceGuy
|-
| GSM
| Singapore
| M1
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| GSM
| Sweden
| Tele2
| Yes
| Yes
| Nope
| Yes
| Yes (always roaming)
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| GSM
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes (always roaming)
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| GSM
| Sweden
| Telenor
|
|
|
|
|
|
|
| steveaw
|-
| GSM
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
| Kenjo2009
|-
| GSM
| Turkey
| Turkcell
|
|
|
|
|
|
|
| cryptooth
|-
| GSM
| UAE
| Etisalat
|
|
|
|
|
|
|
| p25o1
|}

Unofficial networks compatiblity list

2010-02-03T00:26:17Z

Czechdev: added China Unicom

Portal:Research

2010-02-02T00:11:52Z

Czechdev:

__notoc__
{{portal-header|
The Research Portal is for bleeding edge things being done with the device.

Title all pages: '''Research [description]''' or '''Reference [description]'''
}}
{{portal-two-columns
|column1=
===Research:===

* [[Applications Bundled on the Pre]]
* [[Application_Framework|Application Framework]]
* [[Application Signing|Application Signing]]
* [[Blocking Updates]]
* [[New Bluetooth|BlueZ (Replacing Palm Bluetooth)]]
* [[Boot_Chain|Boot Chain]]
* [[Bootie]]
* [[ClassicFilesystem]]
* [[Decrypt SSL (trusted man-in-the-middle technique)|Decrypt SSL (trusted man-in-the-middle technique)]]
* [[FirstUse Application Functionality]]
* [[Fonts available on board the Pre]]
* [[Gstreamer]]
* [[Hidd]]
* [[Introspecting_Dbus|Introspecting Dbus]]
* [[Key Codes|Key Codes]]
* [[Network Management|Network Management]]
* [[OpenGL|OpenGL research]]
* [[OpenGL_Triangle_of_Doom|OpenGL coding and demo Triangle of Doom]]
* [[Pre Specific Hash Codes|Pre Specific Hash Codes]]
* [[Research_Pre_Keyboard | Pre keyboard scancodes and keycodes]]
* [[Proximity Sensor]]
* [[Pictures from Self-Test|Pictures from Self-Test]]
* [[Restore Debug Log|Restore Debug Log]]
* [[Reverse_Engineering_WebOS_Doctor|Reverse Engineering WebOS Doctor]]
* [[Rooted Pre Issues|Rooted Pre Issues]]
* [[Research_Securing_Pre|Securing your Pre]]
* [[Running Processes|Running Processes]]
* [[Symlink Applications|Symlink Applications]]
* [[System Sounds|System Sounds]]
* [[TestApps|TestApps]]
* [[Facebook timezone issue|The annoying Facebook timezone issue]]
* [[Update Service Trace|Update Service Trace]]
* [[Tidbits|Tidbits]]
* [[VideoRecording]]
* [[WebOS Exploration - Various Information|WebOS Exploration - Various Information]]
* [[Research_Pre_GSM_Modem | Pre GSM modem device informations]]
* [[Research_Pre_GSM_Modem_Protocol | Pre GSM modem protocol informations]]
* [[Research_Pre_Audio | Audio routing and setup on the Pre]]
* [[Research_mpt | MSM modem passthru mode ]]
* [[Research_Pre_Boot_Process | Boot process]]
* [[LibSDL Research| SDL LibSDL research which lead to Quake and Doom running]]
* [[LibPDL Research| PDL LibPDL research ties into palm's device hooks]]
* [[Unofficial networks compatiblity list]]

|column2=
===Reference===
* [[Packaging Standards|Packaging Standards]]
* [[webkit_transform|Webkit Transform]]- a powerful set of commands for manipulating elements.
}}

Unofficial networks compatiblity list

2010-02-01T13:45:10Z

Czechdev: New page: This page is shows compatibility information regarding webOS devices use on a non-official networks. '''Please, add only one entry per network/phone model.''' = Pre = {| border="1" ! Ra...

WebOS Hash Codes

2010-01-06T00:10:07Z

Czechdev: added GSM Pre info

Hash codes (so called because they are prefixed and suffixed with "#" 'hash' characters) are entered into the phone dialer to invoke information displays and behaviors on the phone which can not be reached through menu choices.

As of webOS 1.3.5 the hash codes can be found in the following file on the phone: /usr/palm/applications/com.palm.app.phone/app/models/DialStringParser.js

== GSM Pre note ==
The GSM Pre accepts only some of the following codes. You also have to change the preceding double hash '##' to '#*', e.g. ##HELPHELP# becomes #*HELPHELP#.

==Display Information==

*'''##DEBUG# (33284)''' (CMDA only)
:This opens a "Debug Parameters" page that contains technical data on your current signal and tower connection. Signal strength is given as RSSI, which stands for Received Signal Strength Indicator. The closer to zero the RSSI value, the better the signal.

*'''##GPS# (477)''' (CMDA only but there's a [http://gitorious.org/webos-internals/modifications/commit/f14eb152e9bad8eac7fefa4fb1e33e762c1446c2 patch], available in Preware, for that)
:This opens a "GPS Information" page that will give you location, altitude, speed, and accuracy information gathered via GPS.

*'''##HELPHELP# (43574357)'''
:This opens the "Device Information" page.

*'''##RADIO# (72346)'''
:This displays your telephony radio firmware version.

*'''##RTN# (786)''' (CMDA only)
:This opens a "Reverse Logistics Support" page that tells you how many minutes the unit has on it, how much data has transpired, the warranty date, ESN, phone number, software and hardware revisions, refurbished status, etc.

==Collect Logs & Perform Tests==
*'''##8011183#'''
:This application is used to collect logging information from Palm's software running on a webOS device into a single file that caan be emailed to Palm's developers to analyze the reason for an issue.

*'''##5647#'''
:This application is used to collect logging information from Palm's software running on a webOS device into a single file that caan be emailed to Palm's developers to analyze the reason for an issue.

*'''##TEST# (8378)'''
:This opens a "Diagnostic Tests" page with options for manual tests and automatic tests.

==Change Settings==
===Safe===
*'''##8327633696#'''
:This enables/disables the "Sticky Dialer" feature. The sticky dialer feature, when enabled, allows the phone app to run in the background. It is enabled by default. When it is disabled, the phone application closes when it is not the "focused" card. This means that if you open the phone app, then go to browse the net, the phone app closes.

*'''##EVDO# (3836)''' (CMDA only)
:This opens a "EVDO Mode" page that controls your phone's EVDO Settings. It gives you the options to force your pre into the following options: 1xRTT only, EVDO Rev 0 only, Hybrid Rev 0, EVDO only, or Hybrid Rev A (meaning pick the best available). Hybrid Rev A is likely to get you the best speed, but if you don't have good reception in your area, you may want to choose something else to conserve battery life.

*'''##SID6581# (7436581)'''
:This enables/disables "Number Masking." Number masking, when enabled, masks all incoming call numbers as to ensure total privacy for the user.

*'''##TTY# (889)'''
:This enables/disables TTY.

*'''##VPON# (8766)''' (CMDA only)
:This enables "Voice privacy."

*'''##VPOFF# (87633)''' (CMDA only)
:This disables "Voice privacy."

===Use Caution (you may disable your phone)===

*'''##AKEY# (2539)''' (CMDA only)
:Allows you to re-enter the 26-digit AKey on CDMA devices. Note: An incorrect AKey will deactivate the phone and you will need to contact technical support for the AKey. MSL is required.

*'''##DATA# (3282)''' (CMDA only)
:This stores all of your Sprint Data login information, including default gateway, etc. I don't recommend changing these settings unless your data services are not working. MSL is required.

*'''##DEMO# (3366)'''
:This allows you to put your phone into "Demo" mode. '''WARNING: Enabling the Palm demo will erase all of your personal settings and enable an instructional demo.'''

*'''##(MSL)# (Whatever your phone's MSL is)''' (CMDA only)
:This allows you to see/change your number. Do NOT change this to a number without notifying Sprint, or your phone will no longer work.

*'''##OFF# (633)'''
:This turns off the phone radio.

*'''##OMADM# (66236)''' (CMDA only)
:Open Mobile Alliance Device Management provisioning. MSL is required.

*'''##PREV# (7738)''' (CMDA only)
:This opens a Mobile Protocol Revision menu. MSL is required.

*'''##USBPASS# (8727277)'''
:Opens 'USB pass through Control' which makes it easier to switch into diag mode. MSL is required.

==Unknown Functionality==

*'''##66338#'''
:ondevlog

*'''##6346843277#'''
:CDTEST- Toggle Experimental Mode.

*'''##2355273667#'''
:PPTEST- Toggle Experimental Mode.

*'''##FTP# (387)'''
:ftp

'''Research credit to users LarrySteeze and MarkhamDev'''

WebOS Doctor Versions

2010-01-02T01:24:45Z

Czechdev: Sprint section split to Pre/Pixi, added Movistar Spain because it's the same file as O2's release, changed the links list order to reflect the MD5 sums order

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

=== Sprint ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
==== Pixi ====
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar

=== Bell Mobility ===
* version 1.2.1 (Pre) http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 (Pre) http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar

=== O2 Germany, UK and Ireland / Movistar Spain ===
* version 1.1.3 (Pre) http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 (Pre) http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar

=== Telcel GSM, Mexico ===
* version 1.2.5 (Pre) http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of the versions that we know about (with md5sums for each, and the date of release or when they were first spotted and recorded here):

=== Sprint ===

==== Pre ====

4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar (10 June 2009)
0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar (24 June 2009) (changes in [[WebOS_Doctor_version_1.0.3]])
32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar (9 July 2009) (changes in [[WebOS_Doctor_version_1.0.4]])
fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar (24 July 2009) (changes in [[WebOS_Doctor_version_1.1.0]])
3123efda0a40821bd03daf1dd11cf2e3 webosdoctorp100ewwsprint-1.2.0-0830.jar (4 Sep 2009 - accidentally released early) (changes in [[WebOS_Doctor_version_1.2.0-0830]])
93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar (29 September 2009)
e7600251e12e5b96f3143138ba61b9eb [http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint-1.2.1.jar] (9 October 2009)
8261682a25ac21bb2f3107ec5c50dc84 [http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint_1.3.1.jar] (17 November 2009)
4daef882c96461dc1c60cc907c4dfbf0 [http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.ja webosdoctorp100ewwsprint_1.3.5.jar] (30 December 2009)

==== Pixi ====

1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar (18 November 2009)
063c2f66682dd246fa3bf518adae0f53 [http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar webosdoctorp200ewwsprint-1.3.1.jar] (17 November 2009)
eb33e68b07ccad81847d96f546303880 [http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar webosdoctorp200ewwsprint-1.3.2.jar] (3 December 2009)

=== Bell Mobility ===

ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar (27 August 2009)
c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar (29 September 2009)
52f4a4cd9b182004a7060cfaa5be2c6f [http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.2.1.jar] (9 October 2009)
c4202a32ca49a1c843f30b77515cac46 [http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.1.jar] (17 November 2009)

=== O2 Germany, UK and Ireland / Movistar Spain ===
WR = World ready 1.0

bc29e1144823afc05a50dcdc2c84475d [http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar webosdoctorp100eww-wr-1.1.3.jar] (12 October 2009)
9bb8e7547996b5b62ce8742198a9d8bb [http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar webosdoctorp100ueu-wr-1.3.1.jar] (17 November 2009)

=== Telcel GSM, Mexico ===

477f6c3d2ff1673aa9a9d1670aa5e88f [http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar webosdoctorp100ewwtelcel-1.2.5.jar] (25 November 2009)

== Notes ==

1.0.3 is the last version to contain PmModemFactory

WebOS Doctor Versions

2009-11-27T21:16:40Z

Czechdev: better formating, removed links from the MD5 sums list

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

=== Sprint ===
* version 1.3.1 (Pre) http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 (Pixi) http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.2.1 (Pre) http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar

=== Bell Mobility ===
* version 1.3.1 (Pre) http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.2.1 (Pre) http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar

=== O2 Germany, UK and Ireland ===
* version 1.3.1 (Pre) http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.1.3 (Pre) http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of the versions that we know about (with md5sums for each, and the date of release or when they were first spotted and recorded here):

=== Sprint ===

==== Pre ====

4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar (10 June 2009)
0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar (24 June 2009) (changes in [[WebOS_Doctor_version_1.0.3]])
32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar (9 July 2009) (changes in [[WebOS_Doctor_version_1.0.4]])
fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar (24 July 2009) (changes in [[WebOS_Doctor_version_1.1.0]])
3123efda0a40821bd03daf1dd11cf2e3 webosdoctorp100ewwsprint-1.2.0-0830.jar (4 Sep 2009 - accidentally released early) (changes in [[WebOS_Doctor_version_1.2.0-0830]])
93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar (29 September 2009)
e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar (9 October 2009)
8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint_1.3.1.jar (17 November 2009)

==== Pixi ====

1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar (18 November 2009)
063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar (17 November 2009)

=== Bell Mobility ===

ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar (27 August 2009)
c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar (29 September 2009)
52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar (9 October 2009)
c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar (17 November 2009)

=== O2 Germany, UK and Ireland ===
WR = Word ready 1.0

bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar (12 October 2009)
9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar (17 November 2009)

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Patch webOS Bypassing Activation

2009-10-01T21:30:51Z

Czechdev: some typos, clarification, new findings

{{template:patch}}
If you are outside of Sprint's service area in the United States and would like to still be able to use your Pre, you are required to possess a Palm profile. The phone will not let you past the "create profile" screen because it cannot hit Palm's servers over the non-working EV-DO connection.

This modification will allow you to enable WiFi and use that to create your Palm Profile. The phone is otherwise unchanged and would still work if it was brought back into a Sprint service area.

NOTE: You may need to use a Mac or Linux machine to do the file editing, otherwise the /dev folder will be empty and YOUR PHONE WILL NOT BOOT.
= Procedure with a good ESN phone =
== Verified Working Procedure: ==

'''Note: These instructions and patches were created for WebOSdoctor 1.0.2, so the locations of lines may be different on later versions.'''

1. Download the [http://palm.cdnetworks.net/rom/pre_p100eww/webosdoctorp100ewwsprint.jar WebOS image].

2. Rename this file to .zip, and extract it.

3. Untar resources\webOS\nova-cust-image-castle.rootfs.tar.gz.

4. Check to see that /dev has files in it after untarring. If it does not, try untarring as root.

5. Open file /usr/palm/applications/com.palm.app.firstuse/app/controllers/app-assistant.js.

6. Change the setUpFirstUse() function.

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
isDevice = true;
}</nowiki></pre>

7. Apply the diff's to the following 2 files:

command:

patch foo.js < patch

files to patch:

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/controllers/firstuse-util.js
95a96
> {label: $L('Enable WiFi'), command: 'peef-hack-mode'},
105a107,108
> } else if (value == "peef-hack-mode") {
> AppAssistant.accountService.peefMode();
</nowiki></pre>

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/models/account-service.js
389a390,399
> peefMode: function() {
> return new Mojo.Service.Request("palm://com.palm.applicationManager/open", {
> parameters: {
> id: 'com.palm.app.wifi',
> params: {
> }
> }
> });
> },
</nowiki></pre>

8. Edit /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js.

md5sum (file.js)

9. Edit /md5sums file and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js, and /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums. (These two steps are not necessary, but if you don't do them, the flashing will fail. The phone should still reboot and work as normally though.)

10. Pack the nova-cust-image-castle.rootfs folder into nova-cust-image-castle.rootfs.tar.gz (make sure that the tar's root contains the root file system, and not a folder containing the root file system).

tar cvpzf ../nova-cust-image-castle.rootfs.tar.gz ./

11. Pack the webOS folder into webOS.tar. Make sure that the root of the .tar contains the files in webOS and not a folder containing the files in webOS.

tar cvf ../webOS.tar ./

12. Remove JARKEY.RSA and JARKEY.SF from \META-INF.

13. Edit the MANIFEST.MF in \META-INF. Remove all of the SHA-1 hashes and leave just the following three lines at the top of the file.

<pre><nowiki>Manifest-Version: 1.0
Created-By: 1.6.0_04 (Sun Microsystems Inc.)
Main-Class: com.palm.nova.installer.recoverytool.RecoveryTool
</nowiki></pre>

14. Pack the .jar back up. You can use zip to do this. NOTE: If zipping it is resulting in an unusable jar file, make sure you have the JDK installed and use:

jar cvMf flasher.jar * #if you are in the folder containing resources, META-INF and com folders

15. Hold the volume up button while plugging in USB cable.

16. Flash it by starting the flasher tool.
java -jar flasher.jar

17. Once you get to the "Create Palm Profile" screen, tap the little phone icon down in the lower right notification area.

18. Choose the "Enable WiFi" menu item.

19. When the WiFi control opens, enable WiFi and connect to your local WiFi network (must allow internet accesss).

20. Close the WiFi panel and then proceed normally to create your new Palm Profile. NOTE: If you find yourself unable to close the WiFi panel, remove the battery and reboot. Your phone will still connect to the network.

== Bypassing modem errors ==

If your CDMA modem somehow gets into a bad state, firstuse will still fail with generic error messages (loading the "error" scene when it fails to initialize the modem).

Apparently changing (commenting out the isDevice line?)

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
// isDevice = true;
}
</nowiki></pre>

and changing both instances of

<pre><nowiki>
if (PalmSystem.version.match("desktop")) {
</nowiki></pre>

to

<pre><nowiki>
if (true) {
</nowiki></pre>

will cause firstuse to use the same mechanism it does on the emulator and skip testing the CDMA modem.

FIXME: Would someone please validate this method and perhaps come up with a unified patch to solve both problems in fewer lines?

== Credits ==
Courtesy of pEEf.
Verified by Ajax.

= Procedure with an bad ESN phone =

The bad ESN phone (can be for example bought off eBay) is quite a good choice for a developer if you know how to get around the activation process. If you follow the 'good ESN' procedure, the phone will end at the "Profile Creation Failed" screen with no possibility to get around it.

'''NOTE:''' The following instructions were tested on webOS 1.1.0 and may not work on the later releases, but you can obtain the 1.1.0 Doctor and upgrade to a newer version using the Update app later (updated to 1.2.0, the phone works great).'''

== Bypass the First Use app after booting ==

You can
* use a developer ROM (Was available on [http://prerelease.palm.com/sdk-beta/release20090515/PalmDeviceInstaller-SDK47.jar Early Access], now offline. The updated public ROMs are still in the works.) with comparable functions with webOS 1.0.2 minus some profile-related stuff to get access to the phone while it's displaying the First Use app (and edit the file described below after the flashing) and then upgrade to a stock ROM. '''No need to edit the JAR file'''
* reflash it with a modified stock ROM (the JAR packing and unpacking procedure is same as described above but with a different modified file). '''You need to edit the JAR file'''

=== Stock ROM procedure ===

If you modify the ''/etc/event.d/LunaSysMgr'' the following way (comment out some lines), the First Use app will not launch after the reboot and you'll be able to use the phone normally...kind of. The application requiring the Palm Profile may not work as the supposed to do until you continue with the 'Create a Palm Profile' procedure described below.
<pre><nowiki>
start on started java-serviceboot

# Stop when the Software Update tool is about to install an update. The tool
# uses upstart to restart jobs when the installation is complete.
stop on started start_update

respawn

pre-start script
echo "1" > /proc/sys/vm/overcommit_memory
mkdir -p /var/luna/preferences
# if [ ! -f /var/luna/preferences/ran-first-use ]
# then
# echo " -u minimal -a com.palm.app.firstuse" > /var/luna/preferences/sysmgr-args
# else
echo "" > /var/luna/preferences/sysmgr-args
# fi
end script
</nowiki></pre>

=== Developer ROM procedure ===

Just download the developer ROM from somewhere and flash the phone. Then you can do an update to the latest stock ROM by launching the Update application. You only need to create ''/var/luna/preferences/ran-first-use'' (''touch /var/luna/preferences/ran-first-use'' command) file to be able to pass trough the First Use app after the boot, othervise you'll get stuck again ;-) '''One big catch: The system only shows version 1.1.0 as a maximal upgrade, it's currently not possible to update to 1.2.0+'''

'''NOTE:''' (confirmed on a clean reflashed phone two times) I've tried the developer ROM procedure (dev 1.0.2 => stock 1.1.0) and after the system update finished, my phone suddenly stopped responding to keyboard and touchscreen input though the remote access still worked. I discovered that there was some problem with installing the ''hidd'' (Human Interface Device Daemon aka touchscreen/keyboard/proximity sensor/accelerometer driver) libraries. If you also run accross this problem, you need to copy ''/usr/lib/lib/libhidkeypad.so'' and ''/usr/lib/libhidproximity.so'' from the webOS doctor image to the device. These files are missing and therefore the daemon cannot start.

== Create a Palm Profile ==
You have to apply these changes from the remote shell (novaterm) directly on the running phone. Just update to the latest webOS version, enable the developer mode and connect to the device.

=== Procedure for both ROM types ===
'''This procedure has to be done either for the stock ROM and the developer ROM.'''
You need to add the following two lines to ''/usr/palm/applications/com.palm.app.firstuse/app/controllers/provision-assistant.js'' file (webOS 1.1: line 50):

<pre>
this.deviceIdRequest = AppAssistant.accountService.getDeviceId(
this.readDeviceId.bind(this),
this.deviceIdRequestFailed.bind(this), this.controller);

this.setupProgressBar();

this.provisionComplete(); // <==== add this line
return; // <==== add this line

ProvisionUtil.setScene(this);

if((!isActivated) && (activationFailed)) {
</pre>

This modification will let you activate the phone without actually checking if it could be activated (you'll get Cannot Activate Your Phone screen if you don't do that).

=== Stock ROM procedure ===
No need to modify anything else. Just continue with the Finalization part.

=== Developer ROM procedure ===
If you're upgrading from the developer ROM, you need to modify the ''/dev/tokens/DMSETS'' file. in order to be able to create a Palm Profile. If you're running the stock ROM from the beginning, you don't have to issue this modification.

'''before modification:'''
<pre>
{"sets":"94"}
</pre>
'''after modification:'''
<pre>
{"sets":"base"}
</pre>

The phone will then think that it's not a developer device (for the sake of Profile creation process) and allow the Profile to be created.

Finally, you gotta kill the ''java'' (''pkill java'') and ''luna-prefs-service'' (''pkill prefs'') processes. When you do that, the phone will use load the edited DMSETS value and provide it to the Profile creation process.

=== Finalization ===
You have to install the SDK in order to be able to use the ''palm-launch'' command. After you issue one or both of the following modifications (stock ROM => only the first, dev ROM => both), you have to run the Firstuse app to create a Palm Profile. This can be done using the ''palm-launch com.palm.app.firstuse''. The phone will launch the classical Firstuse app screen and let you create the Profile.

'''NOTE:''': If the phone still complains about something, reboot it or try killing the ''java'' and ''prefs'' processes (as described in the previous step).

== Credits ==
* xxrake for the [http://forums.precentral.net/general-webos-chat/194423-new-way-bypassing-pres-activation-palm-profile.html original PreCentral forums post]
* czechdev for finding out what the "Profile Creation Screen" does really mean and how to solve it, SDK to stock ROM update process

Patch webOS Bypassing Activation

2009-08-16T22:26:27Z

Czechdev: corrected some typos

{{template:patch}}
If you are outside of Sprint's service area in the United States and would like to still be able to use your Pre, you are required to possess a Palm profile. The phone will not let you past the "create profile" screen because it cannot hit Palm's servers over the non-working EV-DO connection.

This modification will allow you to enable WiFi and use that to create your Palm Profile. The phone is otherwise unchanged and would still work if it was brought back into a Sprint service area.

NOTE: You may need to use a Mac or Linux machine to do the file editing, otherwise the /dev folder will be empty and YOUR PHONE WILL NOT BOOT.
= Procedure with a good ESN phone =
== Verified Working Procedure: ==

'''Note: These instructions and patches were created for WebOSdoctor 1.0.2, so the locations of lines may be different on later versions.'''

1. Download the [http://palm.cdnetworks.net/rom/pre_p100eww/webosdoctorp100ewwsprint.jar WebOS image].

2. Rename this file to .zip, and extract it.

3. Untar resources\webOS\nova-cust-image-castle.rootfs.tar.gz.

4. Check to see that /dev has files in it after untarring. If it does not, try untarring as root.

5. Open file /usr/palm/applications/com.palm.app.firstuse/app/controllers/app-assistant.js.

6. Change the setUpFirstUse() function.

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
isDevice = true;
}</nowiki></pre>

7. Apply the diff's to the following 2 files:

command:

patch foo.js < patch

files to patch:

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/controllers/firstuse-util.js
95a96
> {label: $L('Enable WiFi'), command: 'peef-hack-mode'},
105a107,108
> } else if (value == "peef-hack-mode") {
> AppAssistant.accountService.peefMode();
</nowiki></pre>

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/models/account-service.js
389a390,399
> peefMode: function() {
> return new Mojo.Service.Request("palm://com.palm.applicationManager/open", {
> parameters: {
> id: 'com.palm.app.wifi',
> params: {
> }
> }
> });
> },
</nowiki></pre>

8. Edit /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js.

md5sum (file.js)

9. Edit /md5sums file and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js, and /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums. (These two steps are not necessary, but if you don't do them, the flashing will fail. The phone should still reboot and work as normally though.)

10. Pack the nova-cust-image-castle.rootfs folder into nova-cust-image-castle.rootfs.tar.gz (make sure that the tar's root contains the root file system, and not a folder containing the root file system).

tar cvpf ../nova-cust-image-castle.rootfs.tar.gz ./

11. Pack the webOS folder into webOS.tar. Make sure that the root of the .tar contains the files in webOS and not a folder containing the files in webOS.

tar cvf ../webOS.tar ./

12. Remove JARKEY.RSA and JARKEY.SF from \META-INF.

13. Edit the MANIFEST.MF in \META-INF.

<pre><nowiki>Manifest-Version: 1.0
Created-By: 1.6.0_04 (Sun Microsystems Inc.)
Main-Class: com.palm.nova.installer.recoverytool.RecoveryTool
</nowiki></pre>

14. Pack the .jar back up. You can use zip to do this. NOTE: If zipping it is resulting in an unusable jar file, make sure you have the JDK installed and use:

jar cvMf flasher.jar * #if you are in the folder containing resources, META-INF and com folders

15. Hold the volume up button while plugging in USB cable.

16. Flash it.

17. Once you get to the "Create Palm Profile" screen, tap the little phone icon down in the lower right notification area.

18. Choose the "Enable WiFi" menu item.

19. When the WiFi control opens, enable WiFi and connect to your local WiFi network (must allow internet accesss).

20. Close the WiFi panel and then proceed normally to create your new Palm Profile. NOTE: If you find yourself unable to close the WiFi panel, remove the battery and reboot. Your phone will still connect to the network.

== Bypassing modem errors ==

If your CDMA modem somehow gets into a bad state, firstuse will still fail with generic error messages (loading the "error" scene when it fails to initialize the modem).

Apparently changing (commenting out the isDevice line?)

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
// isDevice = true;
}
</nowiki></pre>

and changing both instances of

<pre><nowiki>
if (PalmSystem.version.match("desktop")) {
</nowiki></pre>

to

<pre><nowiki>
if (true) {
</nowiki></pre>

will cause firstuse to use the same mechanism it does on the emulator and skip testing the CDMA modem.

FIXME: Would someone please validate this method and perhaps come up with a unified patch to solve both problems in fewer lines?

== Credits ==
Courtesy of pEEf.
Verified by Ajax.

= Procedure with an bad ESN phone =
== Bypass the First Use app after booting ==
The bad ESN phone (can be for example bought off eBay) is quite a good choice for a developer if you know how to get around the activation process. If you follow the 'good ESN' procedure, the phone will end at the "Profile Creation Failed" screen with no possibility to get around it.

You can either use a developer ROM (currently only on at [http://prerelease.palm.com/sdk-beta/release20090515/PalmDeviceInstaller-SDK47.jar Early Access], the updated public ROMs are still in the works) with comparable functions with webOS 1.0.2 minus some profile-related stuff to get access to the phone while it's displaying the First Use app (and edit the file described below after the flashing) OR reflash it with a modified stock ROM (the procedure described above but only with one file) with the following change:

If you modify the ''/etc/event.d/LunaSysMgr'' the following way (comment out some lines), the First Use app will not launch after the reboot and you'll be able to use the phone normally...kind of. The application requiring the Palm Profile may not work as the supposed to do until you continue wit the 'Create a Palm Profile' procedure described below.
<pre><nowiki>
start on started java-serviceboot

# Stop when the Software Update tool is about to install an update. The tool
# uses upstart to restart jobs when the installation is complete.
stop on started start_update

respawn

pre-start script
echo "1" > /proc/sys/vm/overcommit_memory
mkdir -p /var/luna/preferences
# if [ ! -f /var/luna/preferences/ran-first-use ]
# then
# echo " -u minimal -a com.palm.app.firstuse" > /var/luna/preferences/sysmgr-args
# else
echo "" > /var/luna/preferences/sysmgr-args
# fi
end script
</nowiki></pre>

'''NOTE1:''' You can do an update from the developer SDK ROM to the latest stock ROM by launching the Update application. You only need to create ''/var/lina/preferences/ran-first-use'' (''touch /var/lina/preferences/ran-first-use'' command) file to be able to pass trough the First Use app after the boot, othervise you'll get stuck again ;-)

'''NOTE2:''' (after update to webOS 1.1) I've tried the developer ROM procedure and after the system update finished, my phone suddenly stopped responding to keyboard and touchscreen input though the remote access still worked. I discovered that there was some problem with installing the ''hidd'' (Human Interface Device Daemon aka touchscreen/keyboard/proximity sensor/accelerometer driver) libraries. If you also run accross this problem, you need to copy ''/usr/lib/lib/libhidkeypad.so'' and ''/usr/lib/libhidproximity.so'' from the webOS doctor image to the device. These files are missing and therefore the daemon cannot start.

== Create a Palm Profile ==
This may not be the everybody's case, but in my case, I needed to issue two modifications to the system to be able to create a Palm Profile with an bad ESN phone. First, you need to add the following two lines to ''/usr/palm/applications/com.palm.app.firstuse/app/controllers/provision-assistant.js'' file (webOS 1.1: line 50):

<pre>
this.deviceIdRequest = AppAssistant.accountService.getDeviceId(
this.readDeviceId.bind(this),
this.deviceIdRequestFailed.bind(this), this.controller);

this.setupProgressBar();

this.provisionComplete(); // <==== add this line
return; // <==== add this line

ProvisionUtil.setScene(this);

if((!isActivated) && (activationFailed)) {
</pre>

This modification will let you activate the phone without actually checking if it could be activated (you'll get Cannot Activate Your Phone screen if you don't do that).

To be able to create the Palm Profile, you need to modify the ''/dev/tokens/DMSETS'' file.

'''before modification:'''
<pre>
{"sets":"94"}
</pre>
'''after modification:'''
<pre>
{"sets":"base"}
</pre>

Then, you gotta kill the ''java'' (''pkill java'') and ''luna-prefs-service'' (''pkill prefs'') processes. When you do that, the phone will load the edited DMSETS value and provide it to the Profile creation process.

Finnally, you can launch the First Use app by issuing the ''palm-launch com.palm.app.firstuse'' command on your desktop (you need to have developer mode enabled).

== Credits ==
* xxrake for the [http://forums.precentral.net/general-webos-chat/194423-new-way-bypassing-pres-activation-palm-profile.html original PreCentral forums post]
* czechdev for finding out what the "Profile Creation Screen" does really mean and how to solve it, SDK to stock ROM update process

Patch webOS Bypassing Activation

2009-08-16T22:15:41Z

Czechdev: added Palm Profile creation workaround

{{template:patch}}
If you are outside of Sprint's service area in the United States and would like to still be able to use your Pre, you are required to possess a Palm profile. The phone will not let you past the "create profile" screen because it cannot hit Palm's servers over the non-working EV-DO connection.

This modification will allow you to enable WiFi and use that to create your Palm Profile. The phone is otherwise unchanged and would still work if it was brought back into a Sprint service area.

NOTE: You may need to use a Mac or Linux machine to do the file editing, otherwise the /dev folder will be empty and YOUR PHONE WILL NOT BOOT.
= Procedure with a good ESN phone =
== Verified Working Procedure: ==

'''Note: These instructions and patches were created for WebOSdoctor 1.0.2, so the locations of lines may be different on later versions.'''

1. Download the [http://palm.cdnetworks.net/rom/pre_p100eww/webosdoctorp100ewwsprint.jar WebOS image].

2. Rename this file to .zip, and extract it.

3. Untar resources\webOS\nova-cust-image-castle.rootfs.tar.gz.

4. Check to see that /dev has files in it after untarring. If it does not, try untarring as root.

5. Open file /usr/palm/applications/com.palm.app.firstuse/app/controllers/app-assistant.js.

6. Change the setUpFirstUse() function.

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
isDevice = true;
}</nowiki></pre>

7. Apply the diff's to the following 2 files:

command:

patch foo.js < patch

files to patch:

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/controllers/firstuse-util.js
95a96
> {label: $L('Enable WiFi'), command: 'peef-hack-mode'},
105a107,108
> } else if (value == "peef-hack-mode") {
> AppAssistant.accountService.peefMode();
</nowiki></pre>

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/models/account-service.js
389a390,399
> peefMode: function() {
> return new Mojo.Service.Request("palm://com.palm.applicationManager/open", {
> parameters: {
> id: 'com.palm.app.wifi',
> params: {
> }
> }
> });
> },
</nowiki></pre>

8. Edit /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js.

md5sum (file.js)

9. Edit /md5sums file and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js, and /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums. (These two steps are not necessary, but if you don't do them, the flashing will fail. The phone should still reboot and work as normally though.)

10. Pack the nova-cust-image-castle.rootfs folder into nova-cust-image-castle.rootfs.tar.gz (make sure that the tar's root contains the root file system, and not a folder containing the root file system).

tar cvpf ../nova-cust-image-castle.rootfs.tar.gz ./

11. Pack the webOS folder into webOS.tar. Make sure that the root of the .tar contains the files in webOS and not a folder containing the files in webOS.

tar cvf ../webOS.tar ./

12. Remove JARKEY.RSA and JARKEY.SF from \META-INF.

13. Edit the MANIFEST.MF in \META-INF.

<pre><nowiki>Manifest-Version: 1.0
Created-By: 1.6.0_04 (Sun Microsystems Inc.)
Main-Class: com.palm.nova.installer.recoverytool.RecoveryTool
</nowiki></pre>

14. Pack the .jar back up. You can use zip to do this. NOTE: If zipping it is resulting in an unusable jar file, make sure you have the JDK installed and use:

jar cvMf flasher.jar * #if you are in the folder containing resources, META-INF and com folders

15. Hold the volume up button while plugging in USB cable.

16. Flash it.

17. Once you get to the "Create Palm Profile" screen, tap the little phone icon down in the lower right notification area.

18. Choose the "Enable WiFi" menu item.

19. When the WiFi control opens, enable WiFi and connect to your local WiFi network (must allow internet accesss).

20. Close the WiFi panel and then proceed normally to create your new Palm Profile. NOTE: If you find yourself unable to close the WiFi panel, remove the battery and reboot. Your phone will still connect to the network.

== Bypassing modem errors ==

If your CDMA modem somehow gets into a bad state, firstuse will still fail with generic error messages (loading the "error" scene when it fails to initialize the modem).

Apparently changing (commenting out the isDevice line?)

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
// isDevice = true;
}
</nowiki></pre>

and changing both instances of

<pre><nowiki>
if (PalmSystem.version.match("desktop")) {
</nowiki></pre>

to

<pre><nowiki>
if (true) {
</nowiki></pre>

will cause firstuse to use the same mechanism it does on the emulator and skip testing the CDMA modem.

FIXME: Would someone please validate this method and perhaps come up with a unified patch to solve both problems in fewer lines?

== Credits ==
Courtesy of pEEf.
Verified by Ajax.

= Procedure with an bad ESN phone =
== Bypass the First Use app after booting ==
The bad ESN phone (can be for example bought off eBay) is a quite good choice for a developer if you know how to get around the activation process. If you follow the 'good ESN' procedure, the phone will end at the "Profile Creation Failed" screen with no possibility to get around it.

You can either use a developer ROM (currently only on at [http://prerelease.palm.com/sdk-beta/release20090515/PalmDeviceInstaller-SDK47.jar Early Access], the updated public ROMs are still in the works) with comparable functions with webOS 1.0.2 minus some profile-related stuff to get access to the phone while it's displaying the First Use app (and edit the file described below after the flashing) OR reflash it with a modified stock ROM (the procedure described above but only with one file) with the following change:

If you modify the ''/etc/event.d/LunaSysMgr'' the following way (comment out some lines), the First Use app will not launch after the reboot and you'll be able to use the phone normally...kind of. The application requiring the Palm Profile may not work as the supposed to do with a Palm Profile set up.
<pre><nowiki>
start on started java-serviceboot

# Stop when the Software Update tool is about to install an update. The tool
# uses upstart to restart jobs when the installation is complete.
stop on started start_update

respawn

pre-start script
echo "1" > /proc/sys/vm/overcommit_memory
mkdir -p /var/luna/preferences
# if [ ! -f /var/luna/preferences/ran-first-use ]
# then
# echo " -u minimal -a com.palm.app.firstuse" > /var/luna/preferences/sysmgr-args
# else
echo "" > /var/luna/preferences/sysmgr-args
# fi
end script
</nowiki></pre>

'''NOTE1:''' You can do an update from the developer SDK ROM to the latest stock ROM by launching the Update application. You only need to create ''/var/lina/preferences/ran-first-use'' (''touch /var/lina/preferences/ran-first-use'' command) file to be able to pass trough the First Use app after the boot, othervise you'll get stuck again ;-)

'''NOTE2:''' (after update to webOS 1.1) I've tried the developer ROM procedure and after the system update finished, my phone suddenly stopped responding to keyboard and touchscreen input though the remote access still worked. I discovered that there was some problem with installing the ''hidd'' (Human Interface Device Daemon aka touchscreen/keyboard/proximity sensor/accelerometer driver) libraries. If you also run accross this problem, you need to copy ''/usr/lib/lib/libhidkeypad.so'' and ''/usr/lib/libhidproximity.so'' from the webOS doctor image to the device. These files are missing and therefore the daemon cannot start.

== Create a Palm Profile ==
This may not be the everybody's case, but in my case, I needed to issue two modifications to the system to be able to create a Palm Profile with an bad ESN phone. First, you need to add the following two lines to ''/usr/palm/applications/com.palm.app.firstuse/app/controllers/provision-assistant.js'' file (webOS 1.1: line 50):

<pre>
this.deviceIdRequest = AppAssistant.accountService.getDeviceId(
this.readDeviceId.bind(this),
this.deviceIdRequestFailed.bind(this), this.controller);

this.setupProgressBar();

this.provisionComplete(); // <==== add this line
return; // <==== add this line

ProvisionUtil.setScene(this);

if((!isActivated) && (activationFailed)) {
</pre>

This modification will let you activate the phone without actually checking if it could be activated (you'll get Cannot Activate Your Phone screen if you don't do that).

To be able to create the Palm Profile, you need to modify the ''/dev/tokens/DMSETS'' file.

'''before modification:'''
<pre>
{"sets":"94"}
</pre>
'''after modification:'''
<pre>
{"sets":"base"}
</pre>

Then, you gotta kill the ''java'' (''pkill java'') and ''luna-prefs-service'' (''pkill prefs'') processes. When you do that, the phone will load the edited DMSETS value and provide it to the Profile creation process.

Finnally, you can launch the First Use app by issuing the ''palm-launch com.palm.app.firstuse'' command on your desktop (you need to have developer mode enabled).

== Credits ==
* xxrake for the [http://forums.precentral.net/general-webos-chat/194423-new-way-bypassing-pres-activation-palm-profile.html original PreCentral forums post]
* czechdev for finding out what the "Profile Creation Screen" does really mean and how to solve it, SDK to stock ROM update process

Patch webOS Bypassing Activation

2009-08-13T22:52:33Z

Czechdev: solved the developer ROM -> stock ROM update problem

{{template:patch}}
If you are outside of Sprint's service area in the United States and would like to still be able to use your Pre, you are required to possess a Palm profile. The phone will not let you past the "create profile" screen because it cannot hit Palm's servers over the non-working EV-DO connection.

This modification will allow you to enable WiFi and use that to create your Palm Profile. The phone is otherwise unchanged and would still work if it was brought back into a Sprint service area.

NOTE: You may need to use a Mac or Linux machine to do the file editing, otherwise the /dev folder will be empty and YOUR PHONE WILL NOT BOOT.
= Procedure with a good ESN phone =
== Verified Working Procedure: ==

'''Note: These instructions and patches were created for WebOSdoctor 1.0.2, so the locations of lines may be different on later versions.'''

1. Download the [http://palm.cdnetworks.net/rom/pre_p100eww/webosdoctorp100ewwsprint.jar WebOS image].

2. Rename this file to .zip, and extract it.

3. Untar resources\webOS\nova-cust-image-castle.rootfs.tar.gz.

4. Check to see that /dev has files in it after untarring. If it does not, try untarring as root.

5. Open file /usr/palm/applications/com.palm.app.firstuse/app/controllers/app-assistant.js.

6. Change the setUpFirstUse() function.

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
isDevice = true;
}</nowiki></pre>

7. Apply the diff's to the following 2 files:

command:

patch foo.js < patch

files to patch:

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/controllers/firstuse-util.js
95a96
> {label: $L('Enable WiFi'), command: 'peef-hack-mode'},
105a107,108
> } else if (value == "peef-hack-mode") {
> AppAssistant.accountService.peefMode();
</nowiki></pre>

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/models/account-service.js
389a390,399
> peefMode: function() {
> return new Mojo.Service.Request("palm://com.palm.applicationManager/open", {
> parameters: {
> id: 'com.palm.app.wifi',
> params: {
> }
> }
> });
> },
</nowiki></pre>

8. Edit /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js.

md5sum (file.js)

9. Edit /md5sums file and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js, and /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums. (These two steps are not necessary, but if you don't do them, the flashing will fail. The phone should still reboot and work as normally though.)

10. Pack the nova-cust-image-castle.rootfs folder into nova-cust-image-castle.rootfs.tar.gz (make sure that the tar's root contains the root file system, and not a folder containing the root file system).

tar cvpf ../nova-cust-image-castle.rootfs.tar.gz ./

11. Pack the webOS folder into webOS.tar. Make sure that the root of the .tar contains the files in webOS and not a folder containing the files in webOS.

tar cvf ../webOS.tar ./

12. Remove JARKEY.RSA and JARKEY.SF from \META-INF.

13. Edit the MANIFEST.MF in \META-INF.

<pre><nowiki>Manifest-Version: 1.0
Created-By: 1.6.0_04 (Sun Microsystems Inc.)
Main-Class: com.palm.nova.installer.recoverytool.RecoveryTool
</nowiki></pre>

14. Pack the .jar back up. You can use zip to do this. NOTE: If zipping it is resulting in an unusable jar file, make sure you have the JDK installed and use:

jar cvMf flasher.jar * #if you are in the folder containing resources, META-INF and com folders

15. Hold the volume up button while plugging in USB cable.

16. Flash it.

17. Once you get to the "Create Palm Profile" screen, tap the little phone icon down in the lower right notification area.

18. Choose the "Enable WiFi" menu item.

19. When the WiFi control opens, enable WiFi and connect to your local WiFi network (must allow internet accesss).

20. Close the WiFi panel and then proceed normally to create your new Palm Profile. NOTE: If you find yourself unable to close the WiFi panel, remove the battery and reboot. Your phone will still connect to the network.

== Bypassing modem errors ==

If your CDMA modem somehow gets into a bad state, firstuse will still fail with generic error messages (loading the "error" scene when it fails to initialize the modem).

Apparently changing (commenting out the isDevice line?)

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
// isDevice = true;
}
</nowiki></pre>

and changing both instances of

<pre><nowiki>
if (PalmSystem.version.match("desktop")) {
</nowiki></pre>

to

<pre><nowiki>
if (true) {
</nowiki></pre>

will cause firstuse to use the same mechanism it does on the emulator and skip testing the CDMA modem.

FIXME: Would someone please validate this method and perhaps come up with a unified patch to solve both problems in fewer lines?

== Credits ==
Courtesy of pEEf.
Verified by Ajax.

= Procedure with an bad ESN phone =
The bad ESN phone (can be for example bought off eBay) is a quite good choice for a developer if you know how to get around the activation process. If you follow the 'good ESN' procedure, the phone will end at the "Profile Creation Failed" screen with no possibility to get around it.

You can either use a developer ROM (currently only on at [http://prerelease.palm.com/sdk-beta/release20090515/PalmDeviceInstaller-SDK47.jar Early Access], the updated public ROMs are still in the works) with comparable functions with webOS 1.0.2 minus some profile-related stuff to get access to the phone while it's displaying the First Use app (and edit the file described below after the flashing) OR reflash it with a modified stock ROM (the procedure described above but only with one file) with the following change:

If you modify the ''/etc/event.d/LunaSysMgr'' the following way (comment out some lines), the First Use app will not launch after the reboot and you'll be able to use the phone normally...kind of. The application requiring the Palm Profile may not work as the supposed to do with a Palm Profile set up.
<pre><nowiki>
start on started java-serviceboot

# Stop when the Software Update tool is about to install an update. The tool
# uses upstart to restart jobs when the installation is complete.
stop on started start_update

respawn

pre-start script
echo "1" > /proc/sys/vm/overcommit_memory
mkdir -p /var/luna/preferences
# if [ ! -f /var/luna/preferences/ran-first-use ]
# then
# echo " -u minimal -a com.palm.app.firstuse" > /var/luna/preferences/sysmgr-args
# else
echo "" > /var/luna/preferences/sysmgr-args
# fi
end script
</nowiki></pre>

'''NOTE1:''' You can do an update from the developer SDK ROM to the latest stock ROM by launching the Update application. You only need to create ''/var/lina/preferences/ran-first-use'' (''touch /var/lina/preferences/ran-first-use'' command) file to be able to pass trough the First Use app after the boot, othervise you'll get stuck again ;-)

'''NOTE2:''' (after update to webOS 1.1) I've tried the developer ROM procedure and after the system update finished, my phone suddenly stopped responding to keyboard and touchscreen input though the remote access still worked. I discovered that there was some problem with installing the ''hidd'' (Human Interface Device Daemon aka touchscreen/keyboard/proximity sensor/accelerometer driver) libraries. If you also run accross this problem, you need to copy ''/usr/lib/lib/libhidkeypad.so'' and ''/usr/lib/libhidproximity.so'' from the webOS doctor image to the device. These files are missing and therefore the daemon cannot start.

== Credits ==
* xxrake for the [http://forums.precentral.net/general-webos-chat/194423-new-way-bypassing-pres-activation-palm-profile.html original PreCentral forums post]
* czechdev for finding out what the "Profile Creation Screen" does really mean and how to solve it, SDK to stock ROM update process

Patch webOS Bypassing Activation

2009-08-13T05:28:09Z

Czechdev: Bad ESN phone procedure added

Portal:Tools

2009-08-08T20:57:45Z

Czechdev: added the appinstaller link

__notoc__
{{portal-header|
This page lists tools used in any form.
}}
{{portal-two-columns
|column1=
==webOS Internal Related Tools==

* [[Getting started|Accessing Developer Mode]]
* [[Backing_Up_via_Rsync|Backing Up via Rsync]]
* [[Com Palm Appinstaller]]
* [[Com Palm Downloadmanager|Com Palm Downloadmanager]]
* [[Crond|Crond]]
* [[Detecting Application Errors, Syslog|Detecting Application Errors, Syslog]]
* [[/usr/bin/lunaprop|/usr/bin/lunaprop]]
* [[Java Services|Java Services]]
* [[Luna Send|Luna Send]]
* [[PalmDatabase.db3 File|PalmDatabase.db3 File]]
* [[Profile.d|Profile.d]]
* [[Webos Doctor Versions|Webos Doctor Versions]]

==Cross-Compiling and Kernels==
* [[Cross Compiling|Cross Compiling]]
* [[Custom Kernels|Custom Kernels]]
* [[Optware Cross Compilation|Optware Cross Compilation]]
* [[Building_a_cross_toolchain|Building a cross-toochain for armv7 on Gentoo]]

|column2=
==SDK Related Tools==

===Eclipse===

[http://www.eclipse.org/downloads/ Eclipse] is the editor officially supported by Palm. You can find the Eclipse WebOS plugin [http://developer.palm.com/index.php?option=com_content&view=article&id=1639 here].

===Komodo Edit===

[http://www.activestate.com/komodo_edit/ Komodo Edit] is an easy to use cross platform open source editor. Use along side the webOS [http://www.webos.templarian.com/komodo/ Toolbox] for easier development. Complete [http://www.webos.templarian.com/komodo/ Code Completion] is also available for Mojo.

===Aptana Studio===

[http://www.aptana.com/studio/download Aptana Studio] is a standalone version of an Eclipse plugin. Very easy to use. '''Recommended for Beginners'''. You can install the Aptana WebOS plugin by directing Aptana to check [https://cdn.downloads.palm.com/sdkdownloads/1.1/eclipse-plugin/eclipse-3.4/site.xml this link]. If you do not know how to set this up, please look at official Palm documentation [http://developer.palm.com/index.php?option=com_content&view=article&id=1639 here].
}}

Com Palm Appinstaller

2009-08-08T20:56:39Z

Czechdev: Written the appinstaller summary

= Description =
Appinstaller (com.palm.appinstaller) is a Palm D-Bus service that enables the user to manage the packages installation, uninstallation and some other things connected with package management. You can use the service from your application by calling the JavaScript API or from command-line application luna-send.

Found out using an hexa editor, as for sdk62 (webOS 1.1.0) the interesting code in LunaSysMgr starts at 000e:5880 (the methods listing begins at 000e:79c0).

= Available methods =
The appinstaller offers these service methods:

== IPK installation with signature verification ==
The package needs to be created using the SDK or by following the [[Packaging Homebrew Apps for Stock Pre without Rooting]] guide.
palm://com.palm.appinstaller/install {"target":"/ipk/to/install"}

Installation output example:
luna-send -n 5 palm://com.palm.appinstaller/install '{"target":"/tmp/com.test_1.0.0_all.ipk","subscribed":true}'
** Message: serviceResponse Handling: 2, { "returnValue": true, "subscribed": true, "ticket": "6" }
** Message: serviceResponse Handling: 2, { "ticket":6 , "status":"CREATE_TMP" }
** Message: serviceResponse Handling: 2, { "ticket":6 , "status":"VERIFYING" }
** Message: serviceResponse Handling: 2, { "ticket":6 , "status":"IPKG_INSTALL" }
** Message: serviceResponse Handling: 2, { "ticket":6 , "status":"SUCCESS" }

== IPK installation without signature verification ==
The package doesn't have to have a signature. The installation output is the same as when using the verified install method.
palm://com.palm.appinstaller/installNoVerify {"target":"/ipk/to/install"}

== Package removal ==
Removes a package.
palm://com.palm.appinstaller/remove {"packageName":"com.package.name"}

Removal output example:
luna-send -n 3 palm://com.palm.appinstaller/remove '{"packageName":"com.test","subscribed":true}'
** Message: serviceResponse Handling: 2, {"returnValue":true , "ticket":2, "subscribed":true}
** Message: serviceResponse Handling: 2, { "ticket":2 , "status":"IPKG_REMOVE" }
** Message: serviceResponse Handling: 2, { "ticket":2 , "status":"SUCCESS" }

== User-installed package listing ==
Shows the user-installed apps.
palm://com.palm.appinstaller/getUserInstalledAppSizes {}

Listing output example:
luna-send -n 1 palm://com.palm.appinstaller/getUserInstalledAppSizes {}
** Message: serviceResponse Handling: 2, { "returnValue":true , "apps":[ { "appName":"com.palmdts.lightweightapplication", "size":29696},{ "appName":"com.test", "size":112640} ] , "totalSize":142336 }

== Application presence test ==
Probably shows if the application is installed (doesn't work in the emulator; LunaSysMgr consumes 100% CPU and no result). The required parameters are not known.
palm://com.palm.appinstaller/isInstalled {???}

== Notify on application change ==
Probably notifies when the application is changed (installed/removed/etc), not realy sure what it does.
palm://com.palm.appinstaller/queryInstallCapacity {"appId":"com.package.name"}

== Query install capactity ==
Probably finds out how much space is available on the device for the apps installation.
palm://com.palm.appinstaller/queryInstallCapacity {"appId":"com.package.name"}

== Install progress query ==
Probably watch the installation progress, doesn't work in the emulator either. The required parameters are not known.
palm://com.palm.appinstaller/installProgressQuery {???}

----
Found out by czechdev

Talk:Patch webOS Bypassing Activation

2009-07-31T11:05:10Z

Czechdev: New page: What is the last version this was tested on? Would it still work on ROM 1.1? ~~~~

What is the last version this was tested on? Would it still work on ROM 1.1?
[[User:Czechdev|Czechdev]] 11:05, 31 July 2009 (UTC)