Closed Bug 792521 Opened 12 years ago Closed 11 years ago

Can't establish HSDPA or 3G connection with T-Mobile SIM card

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cjones, Unassigned)

Details

(Keywords: dogfood)

This is very high-priority dogfooding issue for US folks, but not a release blocker by definition.

One possibility is that the otoro modem doesn't support t-mo's high speed networks.  I seem to recall that either at&t or t-mo is a special snowflake.

Another possibility might be that we're not using the right APN conf for t-mo.  kaze suggests the problem might be that gnome's DB doesn't have settings that are in android's.

The best thing we can do here is test
 (1) T-Mo SIM
 (2) otoro
 (3) with stock android

tchung, can someone from QA see if otoro is able to get 3g or HSDPA with stock android?  That will settle the modem-or-apn-conf question.
No longer depends on: 772747
The Gnome DB we’re using suggests the correct settings for T-Mobile should be:

  APN: epc.tmobile.com
  DNS: 10.177.0.34
  DNS: 10.164.103.44

If 'epc.tmobile.com' is not enough, then we might have to support static DNS IPs…? That would surprise me, though.

FWIW, the Android database gives the same APN info for T-Mobile US except that it doesn’t mention any static DNS IP.
https://github.com/cyanogenmod/android_vendor_cm/blob/ics/prebuilt/common/etc/apns-conf.xml#L560

Another question: in Gaia → Settings ⇒ Carrier & Data → APN Settings, do you see a list of three T-Mobile items?

If you can access the APN settings on your iOS or Android device, it would help to enter them manually in the “custom” section of the APN Settings on the Otoro.
Before investing too much time in the apn fixes (unless they benefit something else), we should find out whether the otoro modem is capable of high-speed data on t-mo's network.
I get 3g and HSDPA on HW that supports it now, with T-Mo.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.