Closed
Bug 1191226
Opened 9 years ago
Closed 9 years ago
[Shinano][Yukon] Define supported network types for devices
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
FxOS-S4 (07Aug)
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
(Whiteboard: [systemsfe])
Attachments
(2 files, 2 obsolete files)
After AOSP port cleanup there is no more ro.telephony.default_network value being defined on those platforms. We should add our own property on both so that user can select proper radio technology: - ro.moz.ril.0.network_types=gsm,wcdma,lte
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8643630 -
Flags: review?(mwu)
Assignee | ||
Comment 2•9 years ago
|
||
Attachment #8643631 -
Flags: review?(mwu)
Assignee | ||
Comment 3•9 years ago
|
||
Edgar confirmed me on IRC that without either ro.moz.ril.X.network_types nor ro.telephony.default_network, it is expected we fallback on a small set of radio technologies. He also confirmed me that the preferred way to handle this is via ro.moz.ril property.
Comment 4•9 years ago
|
||
How does the AOSP port determine the default set of radio technologies? ro.telephony.default_network seems to be what AOSP uses, so if that's not set, the AOSP port shouldn't be working either. (unless they've added a new mechanism for this..)
Comment 5•9 years ago
|
||
After reading the previous comments, I guess my question is really: why don't we have ro.telephony.default_network anymore?
Assignee | ||
Comment 6•9 years ago
|
||
(In reply to Michael Wu [:mwu] from comment #5) > After reading the previous comments, I guess my question is really: why > don't we have ro.telephony.default_network anymore? Because this was needed upto AOSP KK. With L I have been told it's not useful anymore.
Comment 7•9 years ago
|
||
Does this mean AOSP doesn't use it anymore? If that's the case, do we know what new thing AOSP uses?
Assignee | ||
Comment 8•9 years ago
|
||
(In reply to Michael Wu [:mwu] from comment #7) > Does this mean AOSP doesn't use it anymore? If that's the case, do we know > what new thing AOSP uses? I don't know but I'm asking Alin :). Hsin-Yi or Edgar, do you know?
Flags: needinfo?(htsai)
Flags: needinfo?(echen)
Assignee | ||
Updated•9 years ago
|
Attachment #8643630 -
Flags: review?(mwu)
Assignee | ||
Updated•9 years ago
|
Attachment #8643631 -
Flags: review?(mwu)
Assignee | ||
Comment 9•9 years ago
|
||
Right, change of plan, turns out this is still used in L: http://androidxref.com/5.1.1_r6/xref/frameworks/base/telephony/java/android/telephony/TelephonyManager.java#915 So we'll PR Sony's upstream repo to add it back (Shinano, Rhine and Yukon platform) and then we'll merge the Shinano and Yukon.
Flags: needinfo?(htsai)
Flags: needinfo?(echen)
Assignee | ||
Comment 10•9 years ago
|
||
Right so there's something I am misunderstanding here. We have ro.telephony.default_network that looks to be interpreted by B2G as the maximum capacities of the device: setting it to 7 makes me unable to select above H+; setting it to 1 makes me stuck on GSM only. Yet the naming of this property suggests that this is used to select the default value, not the capacities. Does this means our RIL expects absolutely to have ro.moz.ril.X.network_types to be defined, and only fallback on the ro.telephony.default_network as a safe fallback maximum value for the device's capacities?
Flags: needinfo?(htsai)
Flags: needinfo?(echen)
Comment 11•9 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #10) > Right so there's something I am misunderstanding here. We have > ro.telephony.default_network that looks to be interpreted by B2G as the > maximum capacities of the device: setting it to 7 makes me unable to select > above H+; setting it to 1 makes me stuck on GSM only. Yet the naming of this > property suggests that this is used to select the default value, not the > capacities. > > Does this means our RIL expects absolutely to have > ro.moz.ril.X.network_types to be defined, and only fallback on the > ro.telephony.default_network as a safe fallback maximum value for the > device's capacities? Exactly, our RIL expects to have `ro.moz.ril.X.network_types` defined. If not defined, we will try to get the *possible* capability from `ro.telephony.default_network` (which is from AOSP). [1] [1] https://dxr.mozilla.org/mozilla-central/source/dom/mobileconnection/gonk/MobileConnectionService.js#507-545
Flags: needinfo?(htsai)
Flags: needinfo?(echen)
Assignee | ||
Comment 12•9 years ago
|
||
And you use this possible as the maximum value, right?
Flags: needinfo?(echen)
Comment 13•9 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #12) > And you use this possible as the maximum value, right? That's right.
Flags: needinfo?(echen)
Assignee | ||
Comment 14•9 years ago
|
||
Attachment #8643631 -
Attachment is obsolete: true
Attachment #8644289 -
Flags: review?(mwu)
Assignee | ||
Comment 15•9 years ago
|
||
The Shinano merge also include a couple of Camera-related header commit that landed. I can do a separate PR if you prefer.
Attachment #8643630 -
Attachment is obsolete: true
Attachment #8644290 -
Flags: review?(mwu)
Updated•9 years ago
|
Attachment #8644289 -
Flags: review?(mwu) → review+
Updated•9 years ago
|
Attachment #8644290 -
Flags: review?(mwu) → review+
Assignee | ||
Comment 16•9 years ago
|
||
https://github.com/mozilla-b2g/device-sony-yukon/commit/885b19f0d2f16a0afd667ea013f56f66244efa76 https://github.com/lissyx/device-sony-shinano/tree/bug1191226
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Whiteboard: [systemsfe]
Target Milestone: --- → FxOS-S4 (07Aug)
You need to log in
before you can comment on or make changes to this bug.
Description
•