Hot unplug of SIM make the SIM not detected anymore, even after reboot
Bug #1329926 reported by
ybon
This bug report is a duplicate of:
Bug #1321627: Wrong WWAN value in saved-states if ofono 'Online' toggle fails.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ofono (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
- when the phone is on and the SIM unlocked (PIN has been entered), hot unplug the SIM
- plug the SIM again, the line "Unlock SIM" is not visible in the Network top panel and the network icon is grey like when no network is available
- restart the phone, the lien "Unlock SIM" is still not visible and the network icon is grey
- run the script /usr/share/
Reproduced three times in two phones, both Nexus 4, both on image #79
To post a comment you must log in.
I can reproduce the first part SIM_STATUS_ CHANGED events coming out of the RIL API), or
> - when the phone is on and the SIM unlocked
> (PIN has been entered), hot unplug the SIM
> - plug the SIM again, the line "Unlock SIM" is not
> visible in the Network top panel and the network
> icon is grey like when no network is available
also in a new mako image 116. I'll try to find out what is the expected behaviour, either
A) all SIM card ejects / re-insertions are properly recognized on all layers (currently, there are no proper UNSOL_RESPONSE_
b) inform the user that the device should be rebooted (Android does that on the same Nexus 4 hardware).
I can not reproduce the second part ofono/scripts/ online- model, /lists. launchpad. net/ubuntu- phone/msg08558. html . ybon, do you still see this behaviour?
> - restart the phone, the lien "Unlock SIM" is still not
> visible and the network icon is grey
> - run the script /usr/share/
> the "Unlock SIM" line is now visible in the top panel, and
> "SIM Llocked" is visible in the top notification bar, which
> is the expected behavior
, after reboot I see the "SIM Locked" line immediately. This sounds like a more general "cellular stack does not start up" problem which we have had in the last weeks, discussed in bug 1321627 and on the mailing list https:/