Last Comment Bug 743370 - B2G RIL: Removing SIM card results in endless "connecting..." message
: B2G RIL: Removing SIM card results in endless "connecting..." message
Product: Core
Classification: Components
Component: DOM: Device Interfaces (show other bugs)
: unspecified
: ARM Gonk (Firefox OS)
-- normal (vote)
: mozilla15
Assigned To: Guillermo López :willyaranda (probably SLOW response)
: Andrew Overholt [:overholt]
Depends on:
Blocks: b2g-ril
  Show dependency treegraph
Reported: 2012-04-06 15:12 PDT by Jeff Vier [:jvier]
Modified: 2012-05-24 09:19 PDT (History)
5 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Check for ICC status (1.39 KB, patch)
2012-05-23 02:03 PDT, Guillermo López :willyaranda (probably SLOW response)
philipp: review+
Details | Diff | Splinter Review

Description User image Jeff Vier [:jvier] 2012-04-06 15:12:07 PDT
Phone: Samsung Galaxy S II
Build: 6 April

Booting up with no SIM results in a "No SIM" message in the upper-left.  If I remove the SIM from a running system, it never figures out that that's the problem and thinks it's "connecting..." for forever.

If I re-insert it, it also fails to pick it back up (same as bug 743368).
Comment 1 User image Guillermo López :willyaranda (probably SLOW response) 2012-05-23 02:03:24 PDT
Created attachment 626369 [details] [diff] [review]
Check for ICC status

Fixes the problem by checking the status of the ICC when a message of UNSOLICITED_RESPONSE_VOICE_NETWORK_STATE_CHANGED is sent from the RIL.
Comment 2 User image Fernando Jiménez Moreno [:ferjm] 2012-05-23 02:56:46 PDT
Comment on attachment 626369 [details] [diff] [review]
Check for ICC status

Review of attachment 626369 [details] [diff] [review]:

Looks good to me. I am asking philikon for his approval too.
Comment 3 User image Philipp von Weitershausen [:philikon] 2012-05-23 22:26:05 PDT
Comment 4 User image Ed Morley [:emorley] 2012-05-24 09:19:35 PDT

Note You need to log in before you can comment on or make changes to this bug.