Seeing this in the logcat a couple of times: I/Gecko ( 115): RIL Worker: Error processing operator tuple: TypeError: networkTuple is null Operator name and network status seem to be reported correctly; at least eventually. But it seems there's still some state confusion in there somewhere.
Created attachment 634970 [details] [diff] [review] networkTuple error fix - v1 The REQUEST_OPERATOR handler no longer tries to parse the network tuple when the returned operator data is NULL (i.e. not currently registered with any operator) Also moved code into a new _processOperator function for consistency / separation.
Comment on attachment 634970 [details] [diff] [review] networkTuple error fix - v1 Nice! r=me I haz a sad because not testable with emulator rite nao. :'(
(In reply to Philipp von Weitershausen [:philikon] from comment #2) > > I haz a sad because not testable with emulator rite nao. :'( Yeah.. unfortunately the emulator's network selection doesn't seem to ever change an operator from being "available", even if it is the current selection (or if there is no selection at all). This could probably be fixed, but it would take a fair amount of code. IMO, it might make more sense to start trying to figure out how to use mock-ril..
(In reply to Marshall Culpepper [:marshall_law] from comment #3) > IMO, it might make more sense to start trying to figure out how to use > mock-ril.. +1 It's in JS, too!