Phone connectivity disabled when on Wifi and using an UMTS-only carrier.

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
5 years ago
5 years ago

People

(Reporter: hub, Assigned: kchang)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
I put my Koodo SIM card into an Inari device. The phone at the back says UMTS 850/1900 which is what is needed for Koodo / Telus. The network is found.

I couldn't receive calls or SMS.

This is with the 1.0.1 builds that came with it and updated from today OTA.

I rebooted the phone again and I received the SMS.

But I still can't call.
(Reporter)

Comment 1

5 years ago
Following this, without rebooting I tried to get to receive another SMS from the same sender and I couldn't get it. Call was sent directly to voice mail as well. Not notification on the phone.

And then I lost network.
(Reporter)

Comment 2

5 years ago
I believe the problem might be this:

When I'm connected to wifi it seems that the phone get off the network. It started working when I left the house... This also would explain why I received the SMS on reboot (before it go on the wifi) but then didn't work afterwards...

It should be noted that my carrier, like almost all but one in Canada only have UMTS. No GSM.

I'll do other test later when I swap the SIM card again. (I only have one, it is my main phone)
(Reporter)

Updated

5 years ago
Depends on: 882159
(Reporter)

Updated

5 years ago
Summary: SMS not received with Koodo (Telus - Canada) until I rebooted. Can't call → Phone connectivity disabled when on Wifi and using an UMTS-only carrier.
(Reporter)

Comment 3

5 years ago
I did the test this morning.

First I encountered bug 882159 which is bad.

I enabled Wifi.

Asked somebody to send me a SMS. Didn't get it.

Disabled Wifi. When the phone managed to get back on the network, I received the SMS.

This is a blocker for dogfooding. Can't use that phone at all.
(Reporter)

Comment 4

5 years ago
It is with the OTA that comes from inari/1.0.1/nightly channel.
(Reporter)

Comment 5

5 years ago
And to outline how bad it is, let me summarize the situation in Canada.

We have 3 nation wide telco that share 2 networks. One of the network is GSM + UMTS in the 850/1900 bands, Rogers. The other that is shared by 2 of the telcos (Bell and Telus) is UMTS only in the 850/1900 bands (they opened it in November 2009 so that they could have iPhone and get a slice of the oligopolistic marketshare)

To add icing in the cake, the smaller "new carriers" operate UMTS only in the AWS (1700 MHz) band. No GSM either - but this is irrelevant here as we don't have an AWS capable phone.

So this bug actually prevent most Canadian to dogfood FxOS properly.
(Assignee)

Comment 6

5 years ago
Hi Hubert, can you please provide the ril log to us. By the way, I am not sure if dogfood supports 850 band.
(Reporter)

Comment 7

5 years ago
How can I get these RIL log?

The sticker under the battery (the one with the IMEI) says "UMTS 850/1900/2100". If it doesn't support UMTS 850, then the sticker is a lie.
(Reporter)

Updated

5 years ago
Flags: needinfo?(kchang)
(Reporter)

Comment 8

5 years ago
The problem DO NOT occur on a Geekphone Keon GP-002(fx)
(Assignee)

Comment 9

5 years ago
Hi, 
Here are thee steps to get the log. And band 850 is supported.
1. adb remount
2. adb pull /system/b2g/omni.ja
3. unzip omni.ja
4. find ./ -name ril_consts.js
   edit that file to set this.DEBUG_ALL = true
5. zip -r omni.ja *
6. adb push omni.ja /system/b2g
7. adb reboot
8. adb shell logcat > logcat.txt
9. upload logcat.txt onto bugzilla
Flags: needinfo?(kchang)
(Assignee)

Updated

5 years ago
Assignee: nobody → kchang
(Assignee)

Comment 10

5 years ago
If this problem is happened again, please reopen it.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.