Closed Bug 795508 Opened 12 years ago Closed 6 years ago

[b2g-ril] RIL does not degrade gracefully on losing socket connection to rilproxyd

Categories

(Firefox OS Graveyard :: RIL, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
blocking-basecamp -

People

(Reporter: qdot, Unassigned)

References

Details

Repro:

- Turn on phone with SIM card in
- Let SIM card register with network
- adb shell into phone
- 'touch /dev/local/rilproxyd'
- kill rilproxyd process

Expected:

Phone shows some sort of error for RIL status

Actual:

Phone continues to act like it's connected to the network even though there's nothing talking to the radio now.
Rare that anything will go wrong with rild or rilproxy, but if it does, we should know. Marking blocking on those grounds.
blocking-basecamp: --- → ?
While this sort of error handling would be great to have (required?), we discussed it during triage and decide it's not a blocker.
blocking-basecamp: ? → -
After killed rilproxyd process, rilproxyd process will be recreated and the RIL functions again. This function was implemented for bug 711315.
(https://bugzilla.mozilla.org/show_bug.cgi?id=711315) 

If the worst case is happened, the rilproxyd can not recreated any more. I think we should let device rebooting instead of sending error message, because it is the biggest problem that RIL functions does not work in a mobile device. 

How do you think??
Component: DOM: Device Interfaces → RIL
Product: Core → Boot2Gecko
Version: Trunk → unspecified
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.