Difference between revisions of "How to solve 3G data problems"

From WebOS Internals
Jump to navigation Jump to search
Line 14: Line 14:
 
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)
 
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)
 
* 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]
 
* 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]
* Likely you'll need an SQL Database editor. (reference needed)
+
* Likely you'll need an SQL Database editor. A free SQLite database will do (reference needed)
  
 
= How to Determine which Problem Case(s) is (are) Applicable =
 
= How to Determine which Problem Case(s) is (are) Applicable =

Revision as of 13:10, 21 February 2010

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

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

Tools needed

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)

  • If you have a PC, probably WebOS Quick Install is easy to install and use for beginners [1]
  • Likely you'll need an SQL Database editor. A free SQLite database will do (reference needed)

How to Determine which Problem Case(s) is (are) Applicable

This is tricky and needs some work.....

  1. Check whether your carrier/operator is listed in the Pre carrier database. If not, you will have to modify an existing other carrier's data into your carrier.
  2. Check whether the data section of a listed carrier contains the right information. If not you have to modify the data section of your carrier. Probably modifying it by manual settings under phone preferences is easiest. If that does not work you have to change the databases.

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.

  1. Best how-to so far: Modifying WebOS carrier network settings[2]
  2. APN Problems with 1.3.1/1.3.5 [3]
  3. Carrier/APN settings for 1.13 German and 1.21 US[4]
  4. Adjusting Carrier Settings / SSH into device guide/help for dummies...does it exist?[5]
  5. MMS not working MMS not working [6]
  6. Data still not working in 1.3.1 UK (Multi-page thread 1 2 3 ... Last Page)[7]
  7. Confirmed manual Carrier/APN settings in webOS 1.3[8]
  8. Any GSM pre that has a working voicemail shortcut (key 1)[9]

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
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

  • either 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.

Step 4) Reboot your Pre. That should be it.....

Case: all settings OK, yet no connection

(Thanks to xioq)

The steps:

  1. Fix CarrierNetworkSettings.db3, see Case Incorrect data base settings
  2. 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.

#noccp     
                                                          
#novj           
                                                   
#show-password      

#nobsdcomp      
               
#noipdefault      
                    
#nodeflate        
            
user "vodafone"     

password "vodafone"  


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)