[B2G] [Buri] Need system properties specifying the supported network types

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
5 years ago
4 years ago

People

(Reporter: arthurcc, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Dependency tree / graph
Bug Flags:
in-moztrap -

Firefox Tracking Flags

(b2g-v1.3T unaffected, b2g-v1.4 unaffected, b2g-v2.0 unaffected)

Details

(Whiteboard: [POVB], burirun1.4-1, [2.0-flame-test-run-1])

For all supported devices, we need system properties specifying the supported network types. Please refer to this comment[1] for the format.

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=952043#c12

Updated

5 years ago
See Also: → bug 952043
Arthur,

What is the expectation here?

Should this be part of version notes?
Flags: needinfo?(arthur.chen)
We should have system properties as described in https://bugzilla.mozilla.org/show_bug.cgi?id=952043#c63 in the build, so that we can display correct network types in the list. Based on the comment the properties should be added by the partners.
Flags: needinfo?(arthur.chen)
1.3+ - blocking a blocker
blocking-b2g: 1.3? → 1.3+
Marco, can this be done by the device team or need help from the partners?
Flags: needinfo?(mchen)

Comment 5

5 years ago
Hi Shawn,

As we discussed, could you help to follow up this bug?

Thanks.
Flags: needinfo?(mchen) → needinfo?(sku)

Comment 6

5 years ago
Hi Arthur,
 Please let me know which projects still needing me to inform partner?
I believe codeaurora and SPRD are already aware of this.

See https://bugzilla.mozilla.org/show_bug.cgi?id=952043#c63

Thanks!!
Shawn
Flags: needinfo?(sku)

Comment 7

5 years ago
Please check Comment 6.
Flags: needinfo?(arthur.chen)
Thanks for communicating this, Shawn! All devices should have these properties.

As the blocked bug 950185 was reported on Buri. How can we get the base image of Buri with the properties?
Flags: needinfo?(arthur.chen) → needinfo?(sku)

Comment 9

5 years ago
Hi Arthur:
 I think Buri partner is also aware of this too.
(See https://bugzilla.mozilla.org/show_bug.cgi?id=952043#c58)

Add "anshulj@codeaurora.org" into CC list.
Thanks!!
Shawn
Flags: needinfo?(sku)
Is this a POVB bug (i.e. vendor bug)?
Whiteboard: [POVB]
Unblocking this as this is a vendor bug.
blocking-b2g: 1.3+ → ---
Component: Hardware → Vendcom

Updated

5 years ago
status-b2g-v1.4: --- → affected
Whiteboard: [POVB] → [POVB], burirun1.4-1

Updated

5 years ago
Blocks: 969079

Updated

4 years ago
Blocks: 988979
We need to have the following new property added into the base image:

ro.moz.ril.0.network_types=gsm,wcdma
Summary: [B2G] Need system properties specifying the supported network types → [B2G] [Buri] Need system properties specifying the supported network types
Hi Vance, could you please communicate this with our partner?
Flags: needinfo?(vchen)

Updated

4 years ago
No longer blocks: 988979
(In reply to Hsin-Yi Tsai  [:hsinyi] from comment #13)
> Hi Vance, could you please communicate this with our partner?

Sure, and also let me check with QCT to see if they already integrated this into 7x27/8x10 1.3 release.

Dear Anshul, could you help to check if you have added the following property into the 1.3 release of 7x27 and 8x10?

ro.moz.ril.0.network_types=gsm,wcdma

Thanks

Vance
Flags: needinfo?(vchen) → needinfo?(anshulj)

Comment 15

4 years ago
(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #14)
> (In reply to Hsin-Yi Tsai  [:hsinyi] from comment #13)
> > Hi Vance, could you please communicate this with our partner?
> 
> Sure, and also let me check with QCT to see if they already integrated this
> into 7x27/8x10 1.3 release.
> 
> Dear Anshul, could you help to check if you have added the following
> property into the 1.3 release of 7x27 and 8x10?
> 
> ro.moz.ril.0.network_types=gsm,wcdma
> 
> Thanks
> 
> Vance
What's the need for this property when there already exist an RIL API RIL:GetSupportedNetworkTypes that we already support?
Flags: needinfo?(anshulj)
(In reply to Anshul from comment #15)
> (In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #14)
> > (In reply to Hsin-Yi Tsai  [:hsinyi] from comment #13)
> > > Hi Vance, could you please communicate this with our partner?
> > 
> > Sure, and also let me check with QCT to see if they already integrated this
> > into 7x27/8x10 1.3 release.
> > 
> > Dear Anshul, could you help to check if you have added the following
> > property into the 1.3 release of 7x27 and 8x10?
> > 
> > ro.moz.ril.0.network_types=gsm,wcdma
> > 
> > Thanks
> > 
> > Vance
> What's the need for this property when there already exist an RIL API
> RIL:GetSupportedNetworkTypes that we already support?

Hi Anshul, correct, gaia gets the supportedNetworkTypes through the RIL API. But gecko depends on correct hardware configuration to expose the types to gaia. That's why we are asking for this. Does that make sense?
per Comment#16, ni Anshul for feedback
Flags: needinfo?(anshulj)

Comment 18

4 years ago
Vance, we don't support this property as the name looks very specific to moz ril.
Flags: needinfo?(anshulj)
(In reply to Anshul from comment #18)
> Vance, we don't support this property as the name looks very specific to moz
> ril.

Thanks for the feedback Anshul

Dear Hsin-Yi -

Is this property specific for Moz RIL only? if so, we need to ask partners to add this property to each device in order to make that device working with Moz RIL

Thanks

Vance
Flags: needinfo?(htsai)
(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #19)
> (In reply to Anshul from comment #18)
> > Vance, we don't support this property as the name looks very specific to moz
> > ril.
> 
> Thanks for the feedback Anshul
> 
> Dear Hsin-Yi -
> 
> Is this property specific for Moz RIL only? if so, we need to ask partners
> to add this property to each device in order to make that device working
> with Moz RIL
> 

Yes, this is for MozRIL. Per my understanding, we've asked tarako, fugu, madai to add this.
For Buri case, I think we are fine to set our default value as "wcdma/gsm" instead of the world phone types. That is, we should be fine without buri base image updated. Please see Bug 990383.

> Thanks
> 
> Vance
Flags: needinfo?(htsai)
status-b2g-v2.0: --- → affected
Whiteboard: [POVB], burirun1.4-1 → [POVB], burirun1.4-1, [2.0-flame-test-run-1]
For today's Tarako build : 
adb shell getprop ro.moz.ril.0.network_types
gsm

Gaia      33025a8b1e458ef48cb8b7fb81bdaba28c86b183
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/161d4b0448c6
BuildID   20140606014002
Version   28.1
ro.build.version.incremental=eng.cltbld.20140606.050809
ro.build.date=Fri Jun  6 05:08:16 EDT 2014
Tarako

I would think this needs to block ship if the configuration isn't set right...
blocking-b2g: --- → 1.3T?
status-b2g-v1.3T: --- → affected
hsinyi, does it impact tarako? and what is the end user impact of this if any? thanks
Flags: needinfo?(htsai)
(In reply to Joe Cheng [:jcheng] from comment #22)
> hsinyi, does it impact tarako? and what is the end user impact of this if
> any? thanks

Tarako needs different configurations. We already have the right configuration for tarako.
See https://bugzilla.mozilla.org/show_bug.cgi?id=980831, so this shouldn't block 1.3T.
blocking-b2g: 1.3T? → ---
status-b2g-v1.3T: affected → unaffected
status-b2g-v1.4: affected → unaffected
status-b2g-v2.0: affected → unaffected
Flags: needinfo?(htsai)
I close this bug as WONTFIX since we provided a gecko solution on bug 990383 so buri doesn't have any problem now. But note that if any other device needs particular configurations, then bask.mk still needs modification.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX

Comment 25

4 years ago
Not enough information with current STR to write test case to address bug.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(rmitchell)
No test case added. We don't know how we could test this properly and the bug has been resolved as WNF.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(rmitchell)
Flags: in-moztrap-
You need to log in before you can comment on or make changes to this bug.