Closed
Bug 1113054
Opened 10 years ago
Closed 10 years ago
[B2G][RIL] Support RIL version 10
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(feature-b2g:2.2+, firefox36 wontfix, firefox37 wontfix, firefox38 fixed, b2g-v2.2 fixed, b2g-master fixed)
People
(Reporter: edgar, Assigned: edgar)
References
Details
(Keywords: verifyme)
Attachments
(4 files, 3 obsolete files)
25.48 KB,
patch
|
Details | Diff | Splinter Review | |
15.30 KB,
patch
|
edgar
:
review+
|
Details | Diff | Splinter Review |
14.93 KB,
patch
|
edgar
:
review+
bajaj
:
approval-mozilla-b2g37+
|
Details | Diff | Splinter Review |
1.28 KB,
patch
|
hsinyi
:
review+
tauzen
:
feedback+
bajaj
:
approval-mozilla-b2g37+
|
Details | Diff | Splinter Review |
From AOSP 5.0 (Lollipop), the version of RIL is using v10 [1].
We should add corresponding const or handler in MOZ_RIL for the new parcels introduced in RIL v10.
And also some partner's specific parcel may get conflict with those new parcels, we should fix them as well.
[1] https://android.googlesource.com/platform/hardware/ril/+/lollipop-release/include/telephony/ril.h
Assignee | ||
Updated•10 years ago
|
Blocks: gonk-L-RIL
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
Hi Edgar, do you think this issue can be done by sprint 3(~Jan/9)?thanks.
Flags: needinfo?(echen)
Updated•10 years ago
|
feature-b2g: --- → 2.2+
Updated•10 years ago
|
feature-b2g: 2.2+ → ---
Comment 4•10 years ago
|
||
Per discussion with EPM, |Bug 1107303 - (gonk-L-RIL) [meta] RIL Android L Porting (feature-b2g:2.2)| focuses on nexus5-L porting for now. As this bug is for the future DSDS device, flame-L, and more RIL feature support, this isn't the blocker of bug 1107303. I'll remove the dependency for now. Please correct me if I get something wrong, thank you.
No longer blocks: gonk-L-RIL
Assignee | ||
Comment 5•10 years ago
|
||
Per comment #4, it is not in 2.2+ list, remove n?.
Flags: needinfo?(echen)
Assignee | ||
Comment 6•10 years ago
|
||
Attachment #8541450 -
Attachment is obsolete: true
Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8561848 -
Attachment is obsolete: true
Assignee | ||
Comment 8•10 years ago
|
||
Comment on attachment 8561861 [details] [diff] [review]
Patch, v3
Review of attachment 8561861 [details] [diff] [review]:
-----------------------------------------------------------------
I did some basic tests in nexus-5-l and flame-kk (with also applying the patch of bug 1130938), both of two devices works good.
Although I don't know if the secure element related parcel [1] works as expected, but we could track them in bug 1120177 and fix the issue there.
Hi Hsinyi, may I have your review? Thank you.
[1] TRANSMIT_APDU_BASIC, OPEN_CHANNEL and CLOSE_CHANNEL
Attachment #8561861 -
Flags: review?(htsai)
Updated•10 years ago
|
blocking-b2g: --- → backlog
Comment 9•10 years ago
|
||
This could be a solution for NFC 2.2 feature testing.
Comment 10•10 years ago
|
||
Comment on attachment 8561861 [details] [diff] [review]
Patch, v3
Review of attachment 8561861 [details] [diff] [review]:
-----------------------------------------------------------------
Looks really great!
::: dom/system/gonk/ril_worker.js
@@ +6389,5 @@
> + this.sendChromeMessage(options);
> +};
> +RilObject.prototype[REQUEST_SIM_CLOSE_CHANNEL] = function REQUEST_SIM_CLOSE_CHANNEL(length, options) {
> + if (options.rilRequestError) {
> + options.error = RIL_ERROR_TO_GECKO_ERROR[options.rilRequestError];
oops... how did we end up with this :P
b.t.w, let's just use |this.sendDefaultResponse(options)| for the whole function REQUEST_SIM_CLOSE_CHANNEL.
@@ +6399,5 @@
> + this.sendChromeMessage(options);
> +};
> +RilObject.prototype[REQUEST_SIM_TRANSMIT_APDU_CHANNEL] = function REQUEST_SIM_TRANSMIT_APDU_CHANNEL(length, options) {
> + if (options.rilRequestError) {
> + options.error = RIL_ERROR_TO_GECKO_ERROR[options.rilRequestError];
A flaw has existing for a while...
s/options.error/options.errorMsg/
Attachment #8561861 -
Flags: review?(htsai) → review+
Assignee | ||
Comment 11•10 years ago
|
||
(In reply to Hsin-Yi Tsai (Chinese new year OOO Feb. 18 ~ Feb. 27) [:hsinyi] from comment #10)
> Comment on attachment 8561861 [details] [diff] [review]
> Patch, v3
>
> ::: dom/system/gonk/ril_worker.js
> @@ +6389,5 @@
> > + this.sendChromeMessage(options);
> > +};
> > +RilObject.prototype[REQUEST_SIM_CLOSE_CHANNEL] = function REQUEST_SIM_CLOSE_CHANNEL(length, options) {
> > + if (options.rilRequestError) {
> > + options.error = RIL_ERROR_TO_GECKO_ERROR[options.rilRequestError];
>
> oops... how did we end up with this :P
>
> b.t.w, let's just use |this.sendDefaultResponse(options)| for the whole
> function REQUEST_SIM_CLOSE_CHANNEL.
>
This reminds me bug 991582, I should continue the work there. :p
> @@ +6399,5 @@
> > + this.sendChromeMessage(options);
> > +};
> > +RilObject.prototype[REQUEST_SIM_TRANSMIT_APDU_CHANNEL] = function REQUEST_SIM_TRANSMIT_APDU_CHANNEL(length, options) {
> > + if (options.rilRequestError) {
> > + options.error = RIL_ERROR_TO_GECKO_ERROR[options.rilRequestError];
>
> A flaw has existing for a while...
> s/options.error/options.errorMsg/
Thanks for catching this.
Assignee | ||
Comment 12•10 years ago
|
||
Address review comment #10.
- Use |this.sendDefaultResponse(options)| for REQUEST_SIM_CLOSE_CHANNEL.
- s/options.error/options.errorMsg/
Attachment #8561861 -
Attachment is obsolete: true
Attachment #8564889 -
Flags: review+
Assignee | ||
Comment 13•10 years ago
|
||
Assignee | ||
Comment 14•10 years ago
|
||
Comment 15•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S6 (20feb)
Updated•10 years ago
|
blocking-b2g: backlog → ---
Comment 17•10 years ago
|
||
If we want to use this for 2.2 NFC/SecureElement testing as Wesley wrote in comment 9, this needs to be uplifted to 2.2. Is this possible?
Flags: needinfo?(echen)
Updated•10 years ago
|
Flags: needinfo?(vchang)
Comment 18•10 years ago
|
||
I think this should be uplifted to 2.2 to unblock SecureElement feature testing.
Edgar, could you ask for approval?
feature-b2g: --- → 2.2+
Assignee | ||
Comment 20•10 years ago
|
||
(In reply to Krzysztof Mioduszewski[:tauzen] from comment #17)
> If we want to use this for 2.2 NFC/SecureElement testing as Wesley wrote in
> comment 9, this needs to be uplifted to 2.2. Is this possible?
(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #18)
> I think this should be uplifted to 2.2 to unblock SecureElement feature
> testing.
> Edgar, could you ask for approval?
Sure, I will ask for approval and provide patch for 2.2 if needed.
Flags: needinfo?(echen)
Assignee | ||
Comment 22•10 years ago
|
||
Comment on attachment 8572511 [details] [diff] [review]
[b2g37_v2_2] Patch, v1, r=hsinyi
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Feature
User impact if declined: User cannot use secureElement feature
Testing completed: Try server and manually test on real device
Risk to taking this patch (and alternatives if risky): Low
String or UUID changes made by this patch: No
Try Server result: https://treeherder.mozilla.org/#/jobs?repo=try&revision=d217e734497e
Attachment #8572511 -
Flags: approval-mozilla-b2g37?
Updated•10 years ago
|
Attachment #8572511 -
Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
Comment 23•10 years ago
|
||
status-b2g-v2.2:
--- → fixed
status-b2g-master:
--- → fixed
status-firefox36:
--- → wontfix
status-firefox37:
--- → wontfix
Comment 24•10 years ago
|
||
Master version is working fine for me. Was trying to verify the 2.2 version, and I'm getting a TypeError, on closing the channel.
>I/Gecko ( 2921): RIL Worker: [0] Handling parcel as REQUEST_SIM_CLOSE_CHANNEL
>I/Gecko ( 2921): RIL Worker: Parcel handling threw TypeError: this.sendDefaultResponse is not a function
>I/Gecko ( 2921): REQUEST_SIM_CLOSE_CHANNEL@resource://gre/modules/ril_worker.js:6689:3
Do we need a separate bug for that, or can we fix this here?
Flags: needinfo?(echen)
Assignee | ||
Comment 25•10 years ago
|
||
(In reply to Krzysztof Mioduszewski[:tauzen] from comment #24)
> Master version is working fine for me. Was trying to verify the 2.2 version,
> and I'm getting a TypeError, on closing the channel.
>
> >I/Gecko ( 2921): RIL Worker: [0] Handling parcel as REQUEST_SIM_CLOSE_CHANNEL
> >I/Gecko ( 2921): RIL Worker: Parcel handling threw TypeError: this.sendDefaultResponse is not a function
> >I/Gecko ( 2921): REQUEST_SIM_CLOSE_CHANNEL@resource://gre/modules/ril_worker.js:6689:3
>
> Do we need a separate bug for that, or can we fix this here?
Let me provide a follow-up patch to fix it here (Keeps ni? to me for tracking). Thank you.
Assignee | ||
Comment 26•10 years ago
|
||
Flags: needinfo?(echen)
Assignee | ||
Comment 27•10 years ago
|
||
Comment on attachment 8574480 [details] [diff] [review]
[b2g37_v2_2] (follow-up) Fix TypeError, v1
Review of attachment 8574480 [details] [diff] [review]:
-----------------------------------------------------------------
Hi :tauzen, would you mind helping to verify this patch? Thank you.
Attachment #8574480 -
Flags: feedback?(kmioduszewski)
Assignee | ||
Comment 28•10 years ago
|
||
Comment on attachment 8574480 [details] [diff] [review]
[b2g37_v2_2] (follow-up) Fix TypeError, v1
Review of attachment 8574480 [details] [diff] [review]:
-----------------------------------------------------------------
Hi Hsinyi, |sendDefaultResponse| haven't yet be introduced in 2.2, I should use the old way to handle RIL solicited response when preparing 2.2 patch. Would you mind reviewing this follow-up patch? Thank you.
Attachment #8574480 -
Flags: review?(htsai)
Comment 29•10 years ago
|
||
Comment on attachment 8574480 [details] [diff] [review]
[b2g37_v2_2] (follow-up) Fix TypeError, v1
Review of attachment 8574480 [details] [diff] [review]:
-----------------------------------------------------------------
Thank you!
Attachment #8574480 -
Flags: review?(htsai) → review+
Comment 30•10 years ago
|
||
Comment on attachment 8574480 [details] [diff] [review]
[b2g37_v2_2] (follow-up) Fix TypeError, v1
Review of attachment 8574480 [details] [diff] [review]:
-----------------------------------------------------------------
Verified using demo wallet app. I'm now able to successfully close channel, everything work fine. Thanks!
Attachment #8574480 -
Flags: feedback?(kmioduszewski) → feedback+
Assignee | ||
Comment 31•10 years ago
|
||
Comment on attachment 8574480 [details] [diff] [review]
[b2g37_v2_2] (follow-up) Fix TypeError, v1
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Patch for b2g37_v2_2
User impact if declined: NFC/SecureElement gets a TypeError on closing the channel.
Testing completed: Try server and manually test.
Risk to taking this patch (and alternatives if risky): Low
String or UUID changes made by this patch: None
Try result: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b2fb0cbebed9
Attachment #8574480 -
Flags: approval-mozilla-b2g37?
Comment 32•10 years ago
|
||
Comment on attachment 8574480 [details] [diff] [review]
[b2g37_v2_2] (follow-up) Fix TypeError, v1
Thanks for adding the try result :)
Attachment #8574480 -
Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
Assignee | ||
Comment 33•10 years ago
|
||
(In reply to bhavana bajaj [:bajaj] from comment #32)
> Comment on attachment 8574480 [details] [diff] [review]
> [b2g37_v2_2] (follow-up) Fix TypeError, v1
>
> Thanks for adding the try result :)
Hi Ryan, could you help to merge this follow-up patch? I missed tracking this, sorry about that.
Flags: needinfo?(ryanvm)
Comment 34•10 years ago
|
||
Flags: needinfo?(ryanvm)
Comment 36•9 years ago
|
||
backend fix. unable to verify.
QA Whiteboard: QAExclude
Flags: needinfo?(jmercado)
Updated•9 years ago
|
Flags: needinfo?(jmercado)
You need to log in
before you can comment on or make changes to this bug.
Description
•