B2G/QA/Tips And Tricks: Difference between revisions

Jump to navigation Jump to search
→‎COMRIL vs MOZRIL checking: updating how to check for RIL on Flame and Spark devices
(→‎COMRIL vs MOZRIL checking: updating how to check for RIL on Flame and Spark devices)
Line 489: Line 489:
== COMRIL vs MOZRIL checking ==
== COMRIL vs MOZRIL checking ==
* changes were made in COMRIL, that should be available in AU 112(v 1.0.1)/AU 103 (for v1.1) and  beyond, where if the comril fails, it fails over to the mozril.  You must have ril debugging turned on in the preference.  See https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Changing_preferences
* changes were made in COMRIL, that should be available in AU 112(v 1.0.1)/AU 103 (for v1.1) and  beyond, where if the comril fails, it fails over to the mozril.  You must have ril debugging turned on in the preference.  See https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Changing_preferences
** |adb logcat -b radio| will help in terms of determining failover.
** With Gecko RiL debugging enabled in Developer Settings, run |adb logcat| , if QContentHelper is present you are on COM RiL, otherwise you're utilizing MozRiL
** example of success vs fail over : https://gist.github.com/anonymous/5620923


==  Dealing with the Commercial RIL ==
==  Dealing with the Commercial RIL ==

Navigation menu