1038276 - Not getting LTE on a Nexus 5

Status: RESOLVED FIXED

(Firefox OS Graveyard :: RIL, defect)

Description

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

I have a Nexus 5 running master that's only getting HSDPA or HSPA+, not LTE.  If I borrow another Nexus 5 running Android it gets LTE with no problems.  This is on T-Mobile's network in San Francisco, if that matters.

What logs/etc can I provide to debug?

Comment 1

[shawn ku [:sku]]

Hi Kyle:
 My guess is the default network type is unset, or incorrect.

1. Please help provide device/radio log beginning from boot.

Command:
adb logcat -b radio -b main -v threadtime > /tmp/1038276.log

2. Please also provide system property.

Command:
adb shell getprop > /tmp/properties.log

Comment 2

[shawn ku [:sku]]

AOSP uses below property to determine the preferred network type.

[ro.telephony.default_network]: [10]

And, FxOS uses below property to do the similar thing.

[ro.moz.ril.0.network_types]: [gsm,wcdma]
[ro.moz.ril.1.network_types]: [gsm]

Comment 3

[shawn ku [:sku]]

Hi Kyle:
 Please check comment 1/comment 2. Thanks!!

Shawn

Comment 4

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Thanks, I'll check that tomorrow.

Comment 5

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Attachment: radio.log

Comment 6

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Attachment: properties.log

Comment 7

[shawn ku [:sku]]

Attachment: 2014-06-21-15-32-25.png

Screenshot for adding LTE attribute to property on Dolphin.

Comment 8

[shawn ku [:sku]]

(In reply to Kyle Huey [:khuey] ([e-mail]) from comment #6)
> Created attachment 8456284 [details]
> properties.log

Hi Kyle:
 After checking, there is no properties set properly on N5.
And, there is no SET_PREFERRED_NETWORK_TYPE (9|10) via Gecko/Gaia for sure.

(see [1] for below definition)
9: GECKO_PREFERRED_NETWORK_TYPE_LTE_WCDMA_GSM
10: GECKO_PREFERRED_NETWORK_TYPE_LTE_WCDMA_GSM_CDMA_EVDO


You can try the steps below to see if it works for you.
1. adb pull /system/build.prop /tmp
2. # modify build.prop in /tmp
   # add below line
   ro.moz.ril.0.network_types=gsm,wcdma,lte
3. adb remount
4. adb push /tmp/build.prop /system/build.prop
5. adb shell
   chmod 644 /system/build.prop
6. reboot

[1] - http://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/ril_consts.js?from=ril_consts.js&case=true#424

Comment 9

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

That still doesn't work.

On my Nexus 5 it's set at Auto 2G/3G in the screenshot from comment 7.  If I change the setting to either Automatic or LTE I get 4G.

Comment 10

[Jessica Jong [:jessica] (inactive)]

Attachment: [screenshot] 4G on nexus-5

Hi Kyle, after following the instructions in comment 8 and selecting 'Automatic' or 'LTE' in Network type settings, I can get LTE on my nexus-5.
Are you still having problems with this? Note that, for now, we must select the network type manually in Settings to make it work.

Comment 11

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Yeah, if I go select the network type manually it works just fine and I get 4G.

But why is the default "Auto (2G/3G)" instead of just "Automatic"?

Comment 12

[Jessica Jong [:jessica] (inactive)]

(In reply to Kyle Huey [:khuey] ([e-mail]) from comment #11)
> Yeah, if I go select the network type manually it works just fine and I get
> 4G.
> 
> But why is the default "Auto (2G/3G)" instead of just "Automatic"?

As far as I remember, on first boot, gaia will try to select the option that covers most of the hardware supported network types. Since on first boot, there wasn't 'lte' in the supported network types, 'Automatic' doesn't get selected (not even shown on the list). Maybe wiping user data after the instructions in comment 8 will get you 'Automatic' selected by default, haven't tried it yet though.

Comment 13

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

I guess I could try that next time I flash my phone before I put my data back on there.

Comment 14

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Ok, if I do the steps from comment 8 before the first run everything works: Gaia properly detects that the phone can do 4G and selects the fully Automatic network and I get a 4G connection.

So what do you want to do with this bug?  Is the build.prop something that the OEM is expected to set up correctly?

Comment 15

[Jessica Jong [:jessica] (inactive)]

(In reply to Kyle Huey [:khuey] ([e-mail]) from comment #14)
> Ok, if I do the steps from comment 8 before the first run everything works:
> Gaia properly detects that the phone can do 4G and selects the fully
> Automatic network and I get a 4G connection.
> 
> So what do you want to do with this bug?  Is the build.prop something that
> the OEM is expected to set up correctly?

Since there is no OEM for Nexus 5, I think we can add this property on our own. I will send a PR to address this.

Comment 16

[Jessica Jong [:jessica] (inactive)]

Attachment: mozilla-b2g/device-hammerhead PR#4

Hi Michael, may we add a system property on hammerhead for LTE to work by default? Thanks.

Comment 17

[Michael Wu [:mwu]]

Why don't we use ro.telephony.default_network if it's available?

Comment 18

[Kai-Zhen Li [:seinlin][:kli]]

I think the reason could be this,
http://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/RadioInterfaceLayer.js#2069

Comment 19

[Michael Wu [:mwu]]

Yeah, it's not a good solution when you have more than one sim, but for the very common case where your phone only has one sim slot, using ro.telephony.default_network is better than not.

Comment 20

[Jessica Jong [:jessica] (inactive)]

(In reply to Michael Wu [:mwu] from comment #19)
> Yeah, it's not a good solution when you have more than one sim, but for the
> very common case where your phone only has one sim slot, using
> ro.telephony.default_network is better than not.

In fact, ro.telephony.default_network is for AOSP, b2g gecko deals with ro.moz.ril.x.network_types. Not all of our devices have ro.telephony.default_network, e.g. sprd devices don't seem to have this property, and some devices have the wrong value set, e.g. flame has this property set to 5 (CDMA only). So if we are going to use ro.telephony.default_network, we will need to revise our gecko ril's code to handle single/multi sim differently and recheck all of our supported devices' build.prop. I am not sure if it's a good idea.

Comment 21

[Michael Wu [:mwu]]

(In reply to Jessica Jong [:jjong] [:jessica] from comment #20)
> In fact, ro.telephony.default_network is for AOSP, b2g gecko deals with
> ro.moz.ril.x.network_types. Not all of our devices have
> ro.telephony.default_network, e.g. sprd devices don't seem to have this
> property, and some devices have the wrong value set, e.g. flame has this
> property set to 5 (CDMA only). So if we are going to use
> ro.telephony.default_network, we will need to revise our gecko ril's code to
> handle single/multi sim differently and recheck all of our supported
> devices' build.prop. I am not sure if it's a good idea.

The flame sets this to 5 because we don't read this value. If we started reading the value, it would have to be set correctly.

I'm not saying we should handle single/multi sim properties differently though. I'm proposing a fallback when our preferred property (ro.moz.ril.x.network_types) isn't available. We should check our preferred one first, but if nothing is set, then check ro.telephony.default_network. If nothing else, this will make it easier for any vendors trying to port single SIM devices to Firefox OS. It's not worth forcing every vendor to set ro.moz.ril.x.network_types if they already use the standard one correctly.

Comment 22

[Jessica Jong [:jessica] (inactive)]

(In reply to Michael Wu [:mwu] from comment #21)
> (In reply to Jessica Jong [:jjong] [:jessica] from comment #20)
> > In fact, ro.telephony.default_network is for AOSP, b2g gecko deals with
> > ro.moz.ril.x.network_types. Not all of our devices have
> > ro.telephony.default_network, e.g. sprd devices don't seem to have this
> > property, and some devices have the wrong value set, e.g. flame has this
> > property set to 5 (CDMA only). So if we are going to use
> > ro.telephony.default_network, we will need to revise our gecko ril's code to
> > handle single/multi sim differently and recheck all of our supported
> > devices' build.prop. I am not sure if it's a good idea.
> 
> The flame sets this to 5 because we don't read this value. If we started
> reading the value, it would have to be set correctly.
> 
> I'm not saying we should handle single/multi sim properties differently
> though. I'm proposing a fallback when our preferred property
> (ro.moz.ril.x.network_types) isn't available. We should check our preferred
> one first, but if nothing is set, then check ro.telephony.default_network.
> If nothing else, this will make it easier for any vendors trying to port
> single SIM devices to Firefox OS. It's not worth forcing every vendor to set
> ro.moz.ril.x.network_types if they already use the standard one correctly.

Hmm, sounds reasonable. I will work on it soon, thanks Michael!

Comment 23

[Jessica Jong [:jessica] (inactive)]

Attachment: patch, v1.

Hi Edgar, if mozRIL system property is not available, we'll try to fallback to AOSP system property. May I have your review? Thanks.

Comment 24

[Edgar Chen [:edgar]]

Comment on attachment 8483302 [details] [diff] [review]
patch, v1.

Review of attachment 8483302 [details] [diff] [review]:
-----------------------------------------------------------------

Please see my comments below. Thank you.

::: dom/system/gonk/RadioInterfaceLayer.js
@@ +2073,5 @@
> +    // If mozRIL system property is not available, fallback to AOSP system
> +    // property for support network types.
> +    if (supportedNetworkTypes.length === 1 && supportedNetworkTypes[0] === "") {
> +      key = "ro.telephony.default_network";
> +      let indexString = libcutils.property_get(key, "0");

How if "ro.telephony.default_network" isn't available?
Should we fall back to GECKO_SUPPORTED_NETWORK_TYPES_DEFAULT?
If so, we should not give "0" as default value, maybe ""?

@@ +2078,5 @@
> +      let index = parseInt(indexString, 10);
> +      if (DEBUG) this.debug("Fallback to " + key + ": " + index)
> +
> +      let networkTypes = RIL.RIL_PREFERRED_NETWORK_TYPE_TO_GECKO[index];
> +      supportedNetworkTypes = networkTypes ? networkTypes.split("/") :

Just split("/") isn't enough.
We need to filter out "-auto" for "gsm-auto" [1]. :(

[1] http://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/ril_consts.js?from=ril_consts.js#405

Comment 25

[Jessica Jong [:jessica] (inactive)]

(In reply to Edgar Chen [:edgar][:echen] from comment #24)
> Comment on attachment 8483302 [details] [diff] [review]
> patch, v1.
> 
> Review of attachment 8483302 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> Please see my comments below. Thank you.
> 
> ::: dom/system/gonk/RadioInterfaceLayer.js
> @@ +2073,5 @@
> > +    // If mozRIL system property is not available, fallback to AOSP system
> > +    // property for support network types.
> > +    if (supportedNetworkTypes.length === 1 && supportedNetworkTypes[0] === "") {
> > +      key = "ro.telephony.default_network";
> > +      let indexString = libcutils.property_get(key, "0");
> 
> How if "ro.telephony.default_network" isn't available?
> Should we fall back to GECKO_SUPPORTED_NETWORK_TYPES_DEFAULT?
> If so, we should not give "0" as default value, maybe ""?

Oh, I just though "0" is the same as GECKO_SUPPORTED_NETWORK_TYPES_DEFAULT now. But yes, it would be safer to fallback to GECKO_SUPPORTED_NETWORK_TYPES_DEFAULT. Will do it in the next version.

> 
> @@ +2078,5 @@
> > +      let index = parseInt(indexString, 10);
> > +      if (DEBUG) this.debug("Fallback to " + key + ": " + index)
> > +
> > +      let networkTypes = RIL.RIL_PREFERRED_NETWORK_TYPE_TO_GECKO[index];
> > +      supportedNetworkTypes = networkTypes ? networkTypes.split("/") :
> 
> Just split("/") isn't enough.
> We need to filter out "-auto" for "gsm-auto" [1]. :(

Sure, will do that. Thanks.

> 
> [1]
> http://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/ril_consts.
> js?from=ril_consts.js#405

Comment 26

[Jessica Jong [:jessica] (inactive)]

Attachment: patch, v2.

Address review comment 24:
- empty string as default value if ro.telephony.default_network is not available.
- filter out unused parts in network types, e.g. -auto.

Comment 27

[Edgar Chen [:edgar]]

Comment on attachment 8483925 [details] [diff] [review]
patch, v2.

Review of attachment 8483925 [details] [diff] [review]:
-----------------------------------------------------------------

::: dom/system/gonk/RadioInterfaceLayer.js
@@ +2079,5 @@
> +      if (DEBUG) this.debug("Fallback to " + key + ": " + index)
> +
> +      let networkTypes = RIL.RIL_PREFERRED_NETWORK_TYPE_TO_GECKO[index];
> +      supportedNetworkTypes = networkTypes ? networkTypes.split("/") :
> +        RIL.GECKO_SUPPORTED_NETWORK_TYPES_DEFAULT.split(",");

'-auto' should only be allowed when we take RIL_PREFERRED_NETWORK_TYPE as supported type.
So let's handle '-auto' here.
You can use replace() [1] to remove it, eg. networkTypes.replace("-auto", "", "g").split("/");

@@ +2087,5 @@
> +      let type = supportedNetworkTypes[i];
> +      // Remove unsed part, e.g. '-auto' in 'gsm-auto'.
> +      let index = type.indexOf("-");
> +      if (index != -1) {
> +        supportedNetworkTypes[i] = type = type.substring(0, index);

As mention above, please remove this.
Thank you.

Comment 28

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar][:echen] from comment #27)
> Comment on attachment 8483925 [details] [diff] [review]
> patch, v2.
> 
> Review of attachment 8483925 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> ::: dom/system/gonk/RadioInterfaceLayer.js
> @@ +2079,5 @@
> > +      if (DEBUG) this.debug("Fallback to " + key + ": " + index)
> > +
> > +      let networkTypes = RIL.RIL_PREFERRED_NETWORK_TYPE_TO_GECKO[index];
> > +      supportedNetworkTypes = networkTypes ? networkTypes.split("/") :
> > +        RIL.GECKO_SUPPORTED_NETWORK_TYPES_DEFAULT.split(",");
> 
> '-auto' should only be allowed when we take RIL_PREFERRED_NETWORK_TYPE as
> supported type.
> So let's handle '-auto' here.
> You can use replace() [1] to remove it, eg. networkTypes.replace("-auto",
> "", "g").split("/");

[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace

> 
> @@ +2087,5 @@
> > +      let type = supportedNetworkTypes[i];
> > +      // Remove unsed part, e.g. '-auto' in 'gsm-auto'.
> > +      let index = type.indexOf("-");
> > +      if (index != -1) {
> > +        supportedNetworkTypes[i] = type = type.substring(0, index);
> 
> As mention above, please remove this.
> Thank you.

Comment 29

[Jessica Jong [:jessica] (inactive)]

Attachment: patch, v3.

Address review comment 28:
- use replace() for filtering '-auto' and do it only when we take RIL_PREFERRED_NETWORK_TYPE as supported network type.

Comment 30

[Edgar Chen [:edgar]]

Comment on attachment 8484008 [details] [diff] [review]
patch, v3.

Review of attachment 8484008 [details] [diff] [review]:
-----------------------------------------------------------------

Thank you. :)

Comment 31

[Jessica Jong [:jessica] (inactive)]

Thanks Edgar.

try green: https://tbpl.mozilla.org/?tree=Try&rev=d63e8e94aad2

Comment 32

[Jessica Jong [:jessica] (inactive)]

https://hg.mozilla.org/integration/b2g-inbound/rev/32cf494262d2

Comment 33

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/32cf494262d2