Closed Bug 1174213 Opened 9 years ago Closed 9 years ago

[Aries][RIL] Spark Dogfood builds utilize the Qualcomm RIL

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: AdamA, Unassigned)

Details

(Keywords: smoketest, Whiteboard: [Spark])

Attachments

(1 file)

Attached file RIL Log
Description:
On dogfood builds the qualcomm RIL is present.


Repro Steps:
1) Update a Aries to 20150612054732
2) Run the command "adb logcat -b radio"
3) Observe the log output

Actual:
The Qualcomm RIL is present on dogfood builds

Expected:
It is expected that the qualcomm RIL is not present on firefox OS builds

Environmental Variables:
Device: Aries 3.0 (Full Flash)
Build ID: 20150612054732
Gaia: 9f36b711af7597a6a32471c3305cf1e2d6947d39
Gecko: 0093691d3715
Gonk: 75c7e6ca80d0c7a53f346ecfcde2343be95808c9
Version: 41.0a1 (3.0)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Repro frequency: 10/10
See attached: logcat
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Whiteboard: [Spark]
Keywords: smoketest
Summary: [Spark][RIL] Spark Dogfood builds utilize the Qualcomm RIL → [Aries][RIL] Spark Dogfood builds utilize the Qualcomm RIL
[Blocking Requested - why for this release]:
We should be on Moz RIL.
blocking-b2g: --- → spark?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
That's rild/libril level stuff. That's not the Gecko-level RIL code.
I wasn't sure any more so early they had discussed it with me and I asked them to write it up.

There were some explanations given from Hsinyi:

It's mozRIL and only the mozRIL on Spark, or on any other on-market android devices we are flashing by ourselves. We won't ever get QCRIL on Spark. 

the log message you saw is coming from ril daemon not from the gecko RIL we were really talking about. Seeing the string "qualcomm" can't actually indicate if QCRIL or mozRIL is used. If you like, you could enable "gecko ril debugger" (you could do that in  "Settings" app), and then use "adb logcat" to capture messages. If you see "QContentHelper" in log, then it's QCRIL; if you get "RIL Worker" it's MozRIL.

Related bug 1166278
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
I checked using the steps from Comment 3 and I was not able to see and "QContentHelper" messages in the log. I saw "RIL Worker" appearing in the log so we are on MozRIL.
Status: RESOLVED → VERIFIED
blocking-b2g: spark? → 2.5?
removing flags since it's invalid
blocking-b2g: 2.5? → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: