Next clue... I disabled network-manager via a manual upstart override file, and rebooted. When I try to activate a GPRS context directly via the ofono script ( /usr/share/ofono/scripts ) 'activate-context', an error is returned:
At the same time, I see the following syslog error messages from ofono:
Jun 26 15:46:39 ofonod[1518]: ril_setup_data_call_cb: no DNS in context of type 1
Jun 26 15:46:39 ofonod[1518]: ril_gprs_context_deactivate_primary: couldn't remove call_list listener for apn: nxtgenphone.
Jun 26 15:46:39 ofonod[1518]: ril_deactivate_data_call_cb: reply failure for apn: nxtgenphone - GENERIC_FAILURE
My bet is that the data failure is related to the "unable to get dsi hndl" error, not the devices being re-named. The next thing we should try and reverting the device-rename to see allows data calls to be made.
Next clue... I disabled network-manager via a manual upstart override file, and rebooted. When I try to activate a GPRS context directly via the ofono script ( /usr/share/ ofono/scripts ) 'activate-context', an error is returned:
Error activating /ril_0/context1: org.ofono. Error.Failed: Operation failed
At the same time, I see the following syslog error messages from ofono:
Jun 26 15:46:39 ofonod[1518]: ril_setup_ data_call_ cb: no DNS in context of type 1 context_ deactivate_ primary: couldn't remove call_list listener for apn: nxtgenphone. data_call_ cb: reply failure for apn: nxtgenphone - GENERIC_FAILURE
Jun 26 15:46:39 ofonod[1518]: ril_gprs_
Jun 26 15:46:39 ofonod[1518]: ril_deactivate_
Here's the corresponding ril trace:
ofonod[12095]: [0,0143]> RIL_REQUEST_ SETUP_DATA_ CALL (13,0,nxtgenpho ne,,,0, IP) SETUP_DATA_ CALL {version=9,num=1 [status= 65535,retry= -1,cid= 0,active= 0,type= ,ifname= ,address= ,dns=,gateways= ]}
ofonod[12095]: [0,0143]< RIL_REQUEST_
So the DATA_CALL is clearly failing.
And yet another clue from the logcat radio log whenever I try to activate a context:
E/RILQ ( 1160): (0/20): [main] qcril_data_ request_ setup_data_ call: unable to get dsi hndl request_ setup_data_ call: qcril_data_ request_ setup_data_ call: EXIT with FAILURE request_ deactivate_ data_call: no valid CID [-1] match found response_ generic_ failure: qcril_data_ response_ generic_ failure: ENTRY response_ generic_ failure: qcril_data_ response_ generic_ failure: EXIT request_ deactivate_ data_call: qcril_data_ request_ deact_data_ call: EXIT with err
E/RILQ ( 1160): (0/20): [main] qcril_data_
E/RILQ ( 1160): (0/20): [main] qcril_data_
E/RILQ ( 1160): (0/20): [main] qcril_data_
E/RILQ ( 1160): (0/20): [main] qcril_data_
E/RILQ ( 1160): (0/20): [main] qcril_data_
This might be related to the following kernel error in the syslog:
Jun 26 15:42:46 ubuntu-phablet kernel: [ 13.529528] mipi_dsi_ controller_ cfg: DSI status=8 failed
My bet is that the data failure is related to the "unable to get dsi hndl" error, not the devices being re-named. The next thing we should try and reverting the device-rename to see allows data calls to be made.