Re: [android-porting] RIL Issue for Making GSM call

[animesh arora]

Hi

am facing the problem while maiking GSM call.
I followed the link which i got from the below link.
https://groups.google.com/group/android-porting/browse_thread/thread/21d5d270a793e876?hl=ja 

And getting the below message after running logcat -b radio on the device with cupcake version.

is there any problem which i am getting in my log

 E/RILC    ( 1750): 1:Failed to get socket 'rild'

because firstly  rild was connected only later it is showing failed,


what is the problem for making call?

# logcat -b radio &
# I/RIL     ( 1621): Opening tty device /dev/ttyUSB0
I/RILC    ( 1621): libril: new connection
I/RILC    ( 1621): RIL Daemon version: android reference-ril 1.0
I/RILJ    ( 1676): Connected to 'rild' socket
D/RILJ    ( 1676): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED RADIO_UNAVAILABLE
W/GSM     ( 1676): Can't open /system/etc/voicemail-conf.xml
W/GSM     ( 1676): Can't open /system/etc/spn-conf.xml
D/GSM     ( 1676): [DSAC DEB] registerForPsRestrictedEnabled
D/GSM     ( 1676): [DSAC DEB] registerForPsRestrictedDisabled
D/RILJ    ( 1676): [0000]> GET_CURRENT_CALLS
D/RIL     ( 1621): onRequest: GET_CURRENT_CALLS
D/RILJ    ( 1676): [0000]< GET_CURRENT_CALLS error: com.android.internal.telephony.gsm.CommandException: RADIO_NOT_AVAILABLE
D/GSM     ( 1676): Poll ServiceState done:  oldSS=[1 home null null null ] newSS=[1 home null null null ] oldGprs=1 newGprs=1 oldType=unknown newType=unknown
D/GSM     ( 1676): [DataConnectionTracker] Radio is off and clean up all connection
D/GSM     ( 1676): [DataConnectionTracker] Clean up connection due to radioTurnedOff
D/GSM     ( 1676): [DataConnection] Stop poll NetStat
D/GSM     ( 1676): [DataConnectionTracker] setState: IDLE
D/GSM     ( 1676): [DataConnection] Stop poll NetStat
D/GSM     ( 1676): [DataConnectionTracker] ***trySetupData due to roamingOff
D/GSM     ( 1676): [DSAC DEB] trySetupData with mIsPsRestricted=false
D/GSM     ( 1676): [DataConnectionTracker] trySetupData: Not ready for data:  dataState=IDLE gprsState=1 sim=false UMTS=false phoneState=IDLE dataEnabled=true roaming=false dataOnRoamingEnable=false ps restricted=false
D/GSM     ( 1676): [GsmSimCard] Broadcasting intent SIM_STATE_CHANGED_ACTION NOT_READY reason null
D/RILJ    ( 1676): [0001]> RADIO_POWER
D/GSM     ( 1676): Notifying: radio available
D/RILJ    ( 1676): [0002]> SCREEN_STATE: true
D/AT      ( 1621): AT> ATE0Q0V1
D/AT      ( 1621): AT< ATE0Q0V1
D/AT      ( 1621): AT< OK
D/GSM     ( 1676): Poll ServiceState done:  oldSS=[1 home null null null ] newSS=[3 home null null null ] oldGprs=1 newGprs=1 oldType=unknown newType=unknown
D/RILJ    ( 1676): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED RADIO_OFF
D/AT      ( 1621): AT> ATE0Q0V1
D/AT      ( 1621): AT< 0
D/AT      ( 1621): AT< 4
D/RILJ    ( 1676): [0003]> BASEBAND_VERSION
D/RILJ    ( 1676): [0004]> GET_IMEI
D/RILJ    ( 1676): [0005]> GET_IMEISV
I/RIL     ( 1750): Opening tty device /dev/ttyUSB0
W/RILC    ( 1750): RIL_onUnsolicitedResponse called before RIL_register
D/AT      ( 1750): AT> ATE0Q0V1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> ATS0=0
E/RILC    ( 1750): 1:Failed to get socket 'rild'
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CMEE=1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CREG=2
D/AT      ( 1621): AT< OK

D/AT      ( 1621): AT> AT+CGREG=1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CCWA=1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CMOD=0
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CMUT=0
D/AT      ( 1621): AT< +CMUT:
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CSSN=0,1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+COLP=0
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CSCS="HEX"
D/AT      ( 1621): AT< ERROR
D/AT      ( 1621): AT> AT+CUSD=1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CGEREP=1,0
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CMGF=0
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CFUN?
D/AT      ( 1621): AT< +CFUN: 1
D/AT      ( 1621): AT< OK
D/GSM     ( 1676): Notifying: Radio On
D/RILJ    ( 1676): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED SIM_NOT_READY
D/RILJ    ( 1676): [0006]> OPERATOR
D/RILJ    ( 1676): [0007]> GPRS_REGISTRATION_STATE
D/AT      ( 1621): AT> AT+CPIN?
D/AT      ( 1621): AT< +CPIN: READY
D/AT      ( 1621): AT< OK
D/GSM     ( 1676): Notifying: SIM ready
D/RILJ    ( 1676): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED SIM_READY
D/AT      ( 1621): AT> AT+CSMS=1
D/RILJ    ( 1676): [0008]> REGISTRATION_STATE
D/AT      ( 1621): AT< +CSMS: 1,1,1
D/AT      ( 1621): AT< OK
D/AT      ( 1621): AT> AT+CNMI=1,2,2,1,1
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: RADIO_POWER
D/RILJ    ( 1676): [0001]< RADIO_POWER
D/RIL     ( 1621): onRequest: SCREEN_STATE
D/RILJ    ( 1676): [0009]> QUERY_NETWORK_SELECTION_MODE
D/RILJ    ( 1676): [0002]< SCREEN_STATE error: com.android.internal.telephony.gsm.CommandException: REQUEST_NOT_SUPPORTED
D/RIL     ( 1621): onRequest: BASEBAND_VERSION
D/RIL     ( 1621): onRequest: GET_IMEI
D/AT      ( 1621): AT> AT+CGSN
D/AT      ( 1621): AT< 352679010163850
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: GET_IMEISV
D/RIL     ( 1621): onRequest: OPERATOR
D/AT      ( 1621): AT> AT+COPS=3,0;+COPS?;+COPS=3,1;+COPS?;+COPS=3,2;+COPS?
D/RILJ    ( 1676): [0003]< BASEBAND_VERSION error: com.android.internal.telephony.gsm.CommandException: REQUEST_NOT_SUPPORTED
D/RILJ    ( 1676): [0004]< GET_IMEI
D/RILJ    ( 1676): [0010]> GET_CURRENT_CALLS
D/AT      ( 1621): AT< +COPS: 0,0,"AirTel",0
D/AT      ( 1621): AT< +COPS: 0,1,"AirTel",0
D/AT      ( 1621): AT< +COPS: 0,2,"40440",0
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: GPRS_REGISTRATION_STATE
D/AT      ( 1621): AT> AT+CGREG?
D/AT      ( 1621): AT< +CGREG: 1,1,1F54,1DE3
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: REGISTRATION_STATE
D/RILJ    ( 1676): [0005]< GET_IMEISV error: com.android.internal.telephony.gsm.CommandException: REQUEST_NOT_SUPPORTED
D/RILJ    ( 1676): [0011]> OPERATOR
D/AT      ( 1621): AT> AT+CREG?
D/AT      ( 1621): AT< +CREG: 2,1,1F54,1DE3
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: QUERY_NETWORK_SELECTION_MODE
D/AT      ( 1621): AT> AT+COPS?
D/RILJ    ( 1676): [0006]< OPERATOR {AirTel, AirTel, 40440}
D/RILJ    ( 1676): [0012]> GPRS_REGISTRATION_STATE
D/AT      ( 1621): AT< +COPS: 0,2,"40440",0
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: GET_CURRENT_CALLS
D/AT      ( 1621): AT> AT+CLCC
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: OPERATOR
D/AT      ( 1621): AT> AT+COPS=3,0;+COPS?;+COPS=3,1;+COPS?;+COPS=3,2;+COPS?
D/AT      ( 1621): AT< +COPS: 0,0,"AirTel",0
D/AT      ( 1621): AT< +COPS: 0,1,"AirTel",0
D/AT      ( 1621): AT< +COPS: 0,2,"40440",0
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0007]< GPRS_REGISTRATION_STATE {1, 8020, 7651}
D/RILJ    ( 1676): [0008]< REGISTRATION_STATE {1, 8020, 7651}
D/RILJ    ( 1676): [0013]> REGISTRATION_STATE
D/RIL     ( 1621): onRequest: GPRS_REGISTRATION_STATE
D/AT      ( 1621): AT> AT+CGREG?
D/AT      ( 1621): AT< +CGREG: 1,1,1F54,1DE3
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0014]> QUERY_NETWORK_SELECTION_MODE
D/RILJ    ( 1676): [0009]< QUERY_NETWORK_SELECTION_MODE {0}
D/RIL     ( 1621): onRequest: REGISTRATION_STATE
D/AT      ( 1621): AT> AT+CREG?
D/AT      ( 1621): AT< +CREG: 2,1,1F54,1DE3
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: QUERY_NETWORK_SELECTION_MODE
D/AT      ( 1621): AT> AT+COPS?
D/AT      ( 1621): AT< +COPS: 0,2,"40440",0
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0010]< GET_CURRENT_CALLS 
D/RILJ    ( 1676): [0011]< OPERATOR {AirTel, AirTel, 40440}
D/RILJ    ( 1676): [0012]< GPRS_REGISTRATION_STATE {1, 8020, 7651}
D/RILJ    ( 1676): [0015]> SET_NETWORK_SELECTION_AUTOMATIC
D/RILJ    ( 1676): [0013]< REGISTRATION_STATE {1, 8020, 7651}
D/RIL     ( 1621): onRequest: SET_NETWORK_SELECTION_AUTOMATIC
D/AT      ( 1621): AT> AT+COPS=0
D/RILJ    ( 1676): [0014]< QUERY_NETWORK_SELECTION_MODE {0}
D/RILJ    ( 1676): [0016]> OPERATOR
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: OPERATOR
D/AT      ( 1621): AT> AT+COPS=3,0;+COPS?;+COPS=3,1;+COPS?;+COPS=3,2;+COPS?
D/AT      ( 1621): AT< +COPS: 0,0,"AirTel",0
D/AT      ( 1621): AT< +COPS: 0,1,"AirTel",0
D/AT      ( 1621): AT< +COPS: 0,2,"40440",0
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0017]> GPRS_REGISTRATION_STATE
D/RILJ    ( 1676): [0016]< OPERATOR {AirTel, AirTel, 40440}
D/RIL     ( 1621): onRequest: GPRS_REGISTRATION_STATE
D/AT      ( 1621): AT> AT+CGREG?
D/AT      ( 1621): AT< +CGREG: 1,1,1F54,1DE3
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0018]> REGISTRATION_STATE
D/RILJ    ( 1676): [0017]< GPRS_REGISTRATION_STATE {1, 8020, 7651}
D/RIL     ( 1621): onRequest: REGISTRATION_STATE
D/AT      ( 1621): AT> AT+CREG?
D/AT      ( 1621): AT< +CREG: 2,1,1F54,1DE3
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0019]> QUERY_NETWORK_SELECTION_MODE
D/RILJ    ( 1676): [0018]< REGISTRATION_STATE {1, 8020, 7651}
D/RIL     ( 1621): onRequest: QUERY_NETWORK_SELECTION_MODE
D/AT      ( 1621): AT> AT+COPS?
D/AT      ( 1621): AT< +COPS: 0,2,"40440",0
D/AT      ( 1621): AT< OK
D/GSM     ( 1676): [GsmSimCard] Broadcasting intent SIM_STATE_CHANGED_ACTION READY reason null
D/RILJ    ( 1676): [0019]< QUERY_NETWORK_SELECTION_MODE {0}
V/GSM     ( 1676): SIMRecords:fetchSimRecords 0
D/RILJ    ( 1676): [0020]> getIMSI:RIL_REQUEST_GET_IMSI 11 GET_IMSI
D/RIL     ( 1621): onRequest: GET_IMSI
D/AT      ( 1621): AT> AT+CIMI
D/AT      ( 1621): AT< 5600300002083733
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0020]< GET_IMSI
D/RILJ    ( 1676): [0021]> simIO: SIM_IO 0xc0 0x2fe2 0,0,15
D/RIL     ( 1621): onRequest: SIM_IO
D/AT      ( 1621): AT> AT+CRSM=192,12258,0,0,15
D/RILJ    ( 1676): [0022]> simIO: SIM_IO 0xc0 0x6f40 0,0,15
D/RILJ    ( 1676): [0023]> simIO: SIM_IO 0xc0 0x6fc9 0,0,15
D/AT      ( 1621): AT< +CRSM: 144,0,"0000000A2FE2040005FF5501020000"
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: SIM_IO
D/AT      ( 1621): AT> AT+CRSM=192,28480,0,0,15
D/RILJ    ( 1676): [0021]< SIM_IO SimIoResponse sw1:0x90 sw2:0x0
D/RILJ    ( 1676): [0024]> simIO: SIM_IO 0xc0 0x6fad 0,0,15
D/AT      ( 1621): AT< +CRSM: 144,0,"000000576F40040011FF550102011D"
D/AT      ( 1621): AT< OK
D/RIL     ( 1621): onRequest: SIM_IO
D/AT      ( 1621): AT> AT+CRSM=192,28617,0,0,15
D/RILJ    ( 1676): [0022]< SIM_IO SimIoResponse sw1:0x90 sw2:0x0
D/AT      ( 1621): AT< +CME ERROR: 22
D/RIL     ( 1621): onRequest: SIM_IO
D/AT      ( 1621): AT> AT+CRSM=192,28589,0,0,15
D/RILJ    ( 1676): [0023]< SIM_IO error: com.android.internal.telephony.gsm.CommandException: GENERIC_FAILURE
D/RILJ    ( 1676): [0025]> simIO: SIM_IO 0xc0 0x6fca 0,0,15
D/RILJ    ( 1676): [0026]> simIO: SIM_IO 0xc0 0x6f11 0,0,15
D/AT      ( 1621): AT< +CRSM: 144,0,"000000036FAD040005FF5501020000"
D/AT      ( 1621): AT< OK
D/RILJ    ( 1676): [0024]< SIM_IO SimIoResponse sw1:0x90 sw2:0x0
D/RIL     ( 1621): onRequest: SIM_IO
D/AT      ( 1621): AT> AT+CRSM=192,28618,0,0,15
D/AT      ( 1621): AT< +CME ERROR: 22
D/RILJ    ( 1676): [0025]< SIM_IO error: com.android.internal.telephony.gsm.CommandException: GENERIC_FAILURE
D/RIL     ( 1621): onRequest: SIM_IO
D/AT      ( 1621): AT> AT+CRSM=192,28433,0,0,15
D/RILJ    ( 1676): [0027]> simIO: SIM_IO 0xc0 0x6fcb 0,0,15
D/RILJ    ( 1676): [0028]> simIO: SIM_IO 0xc0 0x6f13 0,0,15
D/RILJ    ( 1676): [0029]> simIO: SIM_IO 0xc0 0x6f46 0,0,15
D/RILJ    ( 1676): [0030]> simIO: SIM_IO 0xc0 0x6fcd 0,0,15
D/RILJ    ( 1676): [0031]> simIO: SIM_IO 0xc0 0x6fc5 0,0,15
D/RILJ    ( 1676): [0032]> simIO: SIM_IO 0xc0 0x6f38 0,0,15
D/RILJ    ( 1676): [0033]> simIO: SIM_IO 0xc0 0x6f16 0,0,15
D/RILJ    ( 1676): [0034]> GET_SIM_STATUS
D/RILJ    ( 1676): [0035]> QUERY_FACILITY_LOCK
D/RILJ    ( 1676): [0036]> QUERY_FACILITY_LOCK
D/GSM     ( 1676): Poll ServiceState done:  oldSS=[3 home null null null ] newSS=[0 home AirTel AirTel 40440 ] oldGprs=1 newGprs=0 oldType=unknown newType=unknown
D/GSM     ( 1676): IMSI: 404400xxxxxxxxx
D/GSM     ( 1676): [GsmSimCard] Broadcasting intent SIM_STATE_CHANGED_ACTION IMSI reason null
D/RILJ    ( 1676): [0037]> simIO: SIM_IO 0xb0 0x2fe2 0,0,10
D/RILJ    ( 1676): [0038]> simIO: SIM_IO 0xb2 0x6f40 1,4,29
D/RILJ    ( 1676): [0039]> simIO: SIM_IO 0xb0 0x6fad 0,0,3
D/GSM     ( 1676): [DataConnectionTracker] ***trySetupData due to gprsAttached
D/GSM     ( 1676): [DSAC DEB] trySetupData with mIsPsRestricted=false
D/GSM     ( 1676): [DataConnectionTracker] trySetupData: Not ready for data:  dataState=IDLE gprsState=0 sim=false UMTS=false phoneState=IDLE dataEnabled=true roaming=false dataOnRoamingEnable=false ps restricted=false
D/RILJ    ( 1676): [0040]> simIO: SIM_IO 0xc0 0x6f17 0,0,15
D/RILJ    ( 1676): [0041]> REQUEST_GET_NEIGHBORING_CELL_IDS

//message while trying to make GSM call using dialer app.
# D/RILJ    ( 1676): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=17
D/RILJ    ( 1676): 0: [15] SET_NETWORK_SELECTION_AUTOMATIC
D/RILJ    ( 1676): 1: [26] SIM_IO
D/RILJ    ( 1676): 2: [27] SIM_IO
D/RILJ    ( 1676): 3: [28] SIM_IO
D/RILJ    ( 1676): 4: [29] SIM_IO
D/RILJ    ( 1676): 5: [30] SIM_IO
D/RILJ    ( 1676): 6: [31] SIM_IO
D/RILJ    ( 1676): 7: [32] SIM_IO
D/RILJ    ( 1676): 8: [33] SIM_IO
D/RILJ    ( 1676): 9: [34] GET_SIM_STATUS
D/RILJ    ( 1676): 10: [35] QUERY_FACILITY_LOCK
D/RILJ    ( 1676): 11: [36] QUERY_FACILITY_LOCK
D/RILJ    ( 1676): 12: [37] SIM_IO
D/RILJ    ( 1676): 13: [38] SIM_IO
D/RILJ    ( 1676): 14: [39] SIM_IO
D/RILJ    ( 1676): 15: [40] SIM_IO
D/RILJ    ( 1676): 16: [41] REQUEST_GET_NEIGHBORING_CELL_IDS
select 1725 (app_process), adj 14, size 3480, to kill
select 1735 (app_process), adj 15, size 4088, to kill
send sigkill to 1735 (app_process), adj 15, size 4088

//
# D/RILJ    ( 1676): [0042]> SIGNAL_STRENGTH
D/RILJ    ( 1676): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=18
D/RILJ    ( 1676): 0: [15] SET_NETWORK_SELECTION_AUTOMATIC
D/RILJ    ( 1676): 1: [26] SIM_IO
D/RILJ    ( 1676): 2: [27] SIM_IO
D/RILJ    ( 1676): 3: [28] SIM_IO
D/RILJ    ( 1676): 4: [29] SIM_IO
D/RILJ    ( 1676): 5: [30] SIM_IO
D/RILJ    ( 1676): 6: [31] SIM_IO
D/RILJ    ( 1676): 7: [32] SIM_IO
D/RILJ    ( 1676): 8: [33] SIM_IO
D/RILJ    ( 1676): 9: [34] GET_SIM_STATUS
D/RILJ    ( 1676): 10: [35] QUERY_FACILITY_LOCK
D/RILJ    ( 1676): 11: [36] QUERY_FACILITY_LOCK
D/RILJ    ( 1676): 12: [37] SIM_IO
D/RILJ    ( 1676): 13: [38] SIM_IO
D/RILJ    ( 1676): 14: [39] SIM_IO
D/RILJ    ( 1676): 15: [40] SIM_IO
D/RILJ    ( 1676): 16: [41] REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ    ( 1676): 17: [42] SIGNAL_STRENGTH


Please help me out for it.

Regards

ANI

[animesh arora]

Hi  Nimit

[Rajesh Kadhiravan Nagaiah]

Hi,

Looks like the AT channel is blocked because of some blocking AT command. Thats the reason there is a timeout in couple of

occasions and also lot of requests pending in queue. Looks like you are using only one AT channel to send these commands

to the modem, which will block the whole communication when some blocking AT commands like CSQ etc is issued.

By the time you make the phone call, the AT channel is already not responding.

Can share the whole ril log and also capture the app side logs ?

Also try issuing the dial when there is no such blocking in the channel.

BR,

Rajesh

Hi  Nimit

--
unsubscribe: android-porti...@googlegroups.com
website: http://groups.google.com/group/android-porting

[Hamilton Vera]

It looks like your modem does not support some AT commands like " AT+CSCS="HEX".

Make sure that these commands are not locking the device.

Try out some alternatives like at_send_command("AT+CSCS=\"UCS2\"", NULL);

[]'s

Hamilton Vera

> --
> unsubscribe: android-porti...@googlegroups.com
> website: http://groups.google.com/group/android-porting
>

--
Hamilton Vera
int Administrator (char Network[],char ComputationalSystems[])
http://hvera.wordpress.com

[animesh arora]

Ok Thanks i will try out it.

Regards

ANI.

[animesh arora]

Hi

i applied AT+CSCS=\"UCS2\"", NULL);
than also i am just getting dialing screen,but other side i am not able to receive call.

But i think AT channel is responding because by standalone c program i am able to call after booting of android.

is there any possibility of java application side some calls are missing in android cupcake version??

Suggest me how to solve this problem?

Regards

ANI

[Rajesh Kadhiravan Nagaiah]

Hi,

That TE character set AT command was just an example, but anyways thats not blocking it because as it returned ERROR immediately.

Can you share both the Apps side logs and the Ril logs ?

BR,

Rajesh

[animesh arora]

I already shared the complete log with the first post itself?
is there anyway to check the baudrate after boots up of android?
What is exactly happen while calling through dialer inside the complete android stack.
Because when i am calling dialing screen i am able to see,but i am not able to get call at other side.
is there anyway for debugging complete stack after dial the no. through dialer????

Regards

ANI

[Maffiou]

From what I can tell, your log doesn't reach a point where it is
trying to make a call. You seem to have some issue much before that
point. And from what I can tell, it's definitely RIL/Modem level, not
likely anything to do with the rest of the android SW.

It would be interesting to see how long it takes for all those SIM
request to be processed, there are quite a few piled up and you seem
to get stuck while processing one of those. Maybe adding "-v time"
when capturing the logcat can show some relevant information.

I don't think the sim io's are essential, so I would shunt these
temporarily and see if that improves things as first step.

Cheers.
M.

On Mar 2, 4:05 pm, animesh arora <animesharora...@gmail.com> wrote:
> I already shared the complete log with the first post itself?
> is there anyway to check the baudrate after boots up of android?
> What is exactly happen while calling through dialer inside the complete
> android stack.
> Because when i am calling dialing screen i am able to see,but i am not able
> to get call at other side.
> is there anyway for debugging complete stack after dial the no. through
> dialer????
>
> Regards
>
> ANI
>
> On Tue, Feb 22, 2011 at 1:23 PM, Rajesh Kadhiravan Nagaiah <
>
>
>
>
>
>
>
> rajesh.kadhira...@gmail.com> wrote:
> > Hi,
>
> > That TE character set AT command was just an example, but anyways thats not
> > blocking it because as it returned ERROR immediately.
> > Can you share both the Apps side logs and the Ril logs ?
>
> > BR,
> > Rajesh
>

> >>>>https://groups.google.com/group/android-porting/browse_thread/thread/...

> ...
>
> read more »

[animesh arora]

Hi

 

Find the latest log for Making GSM call with the help of dialer in android.

 

Help me out for it i am getting this message after making a call through dialer,is there any solution to make a call.Is the log is proper which i am getting after dial up a mobile no.???

 

# I/ActivityManager( 1650): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.android.contacts/com.android.contacts.DialtactsActivity} }
I/ActivityManager( 1650): Displayed activity com.android.contacts/.DialtactsActivity: 8688 ms
I/ActivityManager( 1650): Starting activity: Intent { action=android.intent.action.CALL_PRIVILEGED data=tel:(ANY PHONE NO>)flags=0x10000000 comp={com.android.phone/com.android.phone.PrivilegedOutgoingCallBroadcaster} }
I/ActivityManager( 1650): Starting activity: Intent { action=android.intent.action.CALL data=tel:988-406-0406 flags=0x10000000 comp={com.android.phone/com.android.phone.InCallScreen} (has extras) }
D/GSM     ( 1748): [GSMConn] acquireWakeLock
D/RILJ    ( 1748): [0066]> SET_MUTE false
D/RILJ    ( 1748): [0067]> DIAL
I/AudioHardwareLittleton( 1623): *************************AudioHardwareMarvell::setMode(2)***************************
request_suspend_state: wakeup (0->0) at 3920133668884 (1970-01-01 01:05:20.133668884 UTC)
W/PowerManagerService( 1650): mDimDelay=-1 while trying to dim
W/NotificationService( 1650): STOP command without a player
D/RILJ    ( 1748): [0068]> SET_MUTE false
request_suspend_state: sleep (0->3) at 3920959810233 (1970-01-01 01:05:20.959779716 UTC)
W/ActivityManager( 1650): Activity pause timeout for HistoryRecord{4379e248 {com.android.phone/com.android.phone.InCallScreen}}
stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
W/ActivityManager( 1650): Activity idle timeout for HistoryRecord{43853cc0 {com.android.phone/com.android.phone.PrivilegedOutgoingCallBroadcaster}}
D/dalvikvm( 1650): GC freed 4936 objects / 289256 bytes in 1650ms
W/ActivityManager( 1650): Activity idle timeout for HistoryRecord{4379e248 {com.android.phone/com.android.phone.InCallScreen}}
D/RILJ    ( 1748): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=23
D/RILJ    ( 1748): 0: [36] SET_NETWORK_SELECTION_AUTOMATIC
D/RILJ    ( 1748): 1: [47] SIM_IO
D/RILJ    ( 1748): 2: [48] SIM_IO
D/RILJ    ( 1748): 3: [49] SIM_IO
D/RILJ    ( 1748): 4: [50] SIM_IO
D/RILJ    ( 1748): 5: [51] SIM_IO
D/RILJ    ( 1748): 6: [52] SIM_IO
D/RILJ    ( 1748): 7: [53] SIM_IO
D/RILJ    ( 1748): 8: [54] SIM_IO
D/RILJ    ( 1748): 9: [55] GET_SIM_STATUS
D/RILJ    ( 1748): 10: [56] QUERY_FACILITY_LOCK
D/RILJ    ( 1748): 11: [57] QUERY_FACILITY_LOCK
D/RILJ    ( 1748): 12: [58] SIM_IO
D/RILJ    ( 1748): 13: [59] SIM_IO
D/RILJ    ( 1748): 14: [60] SIM_IO
D/RILJ    ( 1748): 15: [61] SIM_IO
D/RILJ    ( 1748): 16: [62] REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ    ( 1748): 17: [63] SCREEN_STATE
D/RILJ    ( 1748): 18: [64] SIGNAL_STRENGTH
D/RILJ    ( 1748): 19: [65] SCREEN_STATE
D/RILJ    ( 1748): 20: [66] SET_MUTE
D/RILJ    ( 1748): 21: [67] DIAL
D/RILJ    ( 1748): 22: [68] SET_MUTE
D/RILJ    ( 1748): [0069]> SET_MUTE false
D/RILJ    ( 1748): [0070]> SET_MUTE false
select 1854 (app_process), adj 15, size 4005, to kill
send sigkill to 1854 (app_process), adj 15, size 4005
I/ActivityManager( 1650): Process com.android.settings (pid 1854) has died.
D/RILJ    ( 1748): [0071]> DTMF_STOP
I/ActivityManager( 1650): Low Memory: No more background processes.
W/ActivityManager( 1650): Activity pause timeout for HistoryRecord{4379e248 {com.android.phone/com.android.phone.InCallScreen}}
D/dalvikvm( 1753): GC freed 2455 objects / 121888 bytes in 2357ms
D/dalvikvm( 1650): GC freed 3303 objects / 352520 bytes in 1966ms

D/RILJ    ( 1748): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=26

D/RILJ    ( 1748): 0: [36] SET_NETWORK_SELECTION_AUTOMATIC
D/RILJ    ( 1748): 1: [47] SIM_IO
D/RILJ    ( 1748): 2: [48] SIM_IO
D/RILJ    ( 1748): 3: [49] SIM_IO
D/RILJ    ( 1748): 4: [50] SIM_IO
D/RILJ    ( 1748): 5: [51] SIM_IO
D/RILJ    ( 1748): 6: [52] SIM_IO
D/RILJ    ( 1748): 7: [53] SIM_IO
D/RILJ    ( 1748): 8: [54] SIM_IO
D/RILJ    ( 1748): 9: [55] GET_SIM_STATUS
D/RILJ    ( 1748): 10: [56] QUERY_FACILITY_LOCK
D/RILJ    ( 1748): 11: [57] QUERY_FACILITY_LOCK
D/RILJ    ( 1748): 12: [58] SIM_IO
D/RILJ    ( 1748): 13: [59] SIM_IO
D/RILJ    ( 1748): 14: [60] SIM_IO
D/RILJ    ( 1748): 15: [61] SIM_IO
D/RILJ    ( 1748): 16: [62] REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ    ( 1748): 17: [63] SCREEN_STATE
D/RILJ    ( 1748): 18: [64] SIGNAL_STRENGTH
D/RILJ    ( 1748): 19: [65] SCREEN_STATE
D/RILJ    ( 1748): 20: [66] SET_MUTE
D/RILJ    ( 1748): 21: [67] DIAL
D/RILJ    ( 1748): 22: [68] SET_MUTE
D/RILJ    ( 1748): 23: [69] SET_MUTE
D/RILJ    ( 1748): 24: [70] SET_MUTE
D/RILJ    ( 1748): 25: [71] DTMF_STOP
I/ActivityManager( 1650): Displayed activity com.android.phone/.InCallScreen: 21628 ms
D/RILJ    ( 1748): [0072]> DTMF_STOP
D/dalvikvm( 1748): GC freed 2277 objects / 141480 bytes in 1504ms
D/RILJ    ( 1748): [0073]> SCREEN_STATE: false
D/RILJ    ( 1748): [0074]> SET_MUTE false
D/GSM     ( 1748): [DataConnection] Stop poll NetStat
W/ActivityManager( 1650): Activity idle timeout for HistoryRecord{4379e248 {com.android.phone/com.android.phone.InCallScreen}}
D/RILJ    ( 1748): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=29
D/RILJ    ( 1748): 0: [36] SET_NETWORK_SELECTION_AUTOMATIC
D/RILJ    ( 1748): 1: [47] SIM_IO
D/RILJ    ( 1748): 2: [48] SIM_IO
D/RILJ    ( 1748): 3: [49] SIM_IO
D/RILJ    ( 1748): 4: [50] SIM_IO
D/RILJ    ( 1748): 5: [51] SIM_IO
D/RILJ    ( 1748): 6: [52] SIM_IO
D/RILJ    ( 1748): 7: [53] SIM_IO
D/RILJ    ( 1748): 8: [54] SIM_IO
D/RILJ    ( 1748): 9: [55] GET_SIM_STATUS
D/RILJ    ( 1748): 10: [56] QUERY_FACILITY_LOCK
D/RILJ    ( 1748): 11: [57] QUERY_FACILITY_LOCK
D/RILJ    ( 1748): 12: [58] SIM_IO
D/RILJ    ( 1748): 13: [59] SIM_IO
D/RILJ    ( 1748): 14: [60] SIM_IO
D/RILJ    ( 1748): 15: [61] SIM_IO
D/RILJ    ( 1748): 16: [62] REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ    ( 1748): 17: [63] SCREEN_STATE
D/RILJ    ( 1748): 18: [64] SIGNAL_STRENGTH
D/RILJ    ( 1748): 19: [65] SCREEN_STATE
D/RILJ    ( 1748): 20: [66] SET_MUTE
D/RILJ    ( 1748): 21: [67] DIAL
D/RILJ    ( 1748): 22: [68] SET_MUTE
D/RILJ    ( 1748): 23: [69] SET_MUTE
D/RILJ    ( 1748): 24: [70] SET_MUTE
D/RILJ    ( 1748): 25: [71] DTMF_STOP
D/RILJ    ( 1748): 26: [72] DTMF_STOP
D/RILJ    ( 1748): 27: [73] SCREEN_STATE
D/RILJ    ( 1748): 28: [74] SET_MUTE
D/dalvikvm( 1753): GC freed 475 objects / 17720 bytes in 2359ms
request_suspend_state: wakeup (3->0) at 3977003267267 (1970-01-01 01:06:17.003267267 UTC)
request_suspend_state: wakeup (0->0) at 3977573701840 (1970-01-01 01:06:17.573701840 UTC)
D/RILJ    ( 1748): [0075]> SET_MUTE false
D/RILJ    ( 1748): [0076]> SCREEN_STATE: true
W/KeyCharacterMap( 1748): No keyboard for id 0
W/KeyCharacterMap( 1748): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/GSM     ( 1748): [DataConnection] Stop poll NetStat
I/ActivityManager( 1650): moveTaskToBack: 7
D/RILJ    ( 1748): [0077]> DTMF_STOP
D/RILJ    ( 1748): [0078]> DTMF_STOP

 

 

--

[arindam das]

Hi Animesh,
                  I can see in ur log

D/RILJ    ( 1748): [0067]> DIAL

but it didnt result to any AT command(hoping that the IPC mechanism is AT).

No log is coming from reference-ril.so(or whatever logtag you ahve given in reference-ril.c code)

Please check first those logs are enabled or not...may be something is failing from there itself.

And I totally agree with maffiou,comment out the SIM_IO(at+crsm calls) request from your ril code and check whether it proceeds with  the MO call or not

[animesh arora]

Hi Arrin/Moffiou

 

Please tell me clearly i what i need to comment out,are you telling about to comment out the particular SIMIO related AT Command.

 

Tell me is there possiblity of blocking GSM AT interfaced channel,so i am not able to call.If yes tell me how we can test it out wheather it is got blocked or not?

 

Is there any procedure to test it out?

 

Regards

 

ANI 

[arindam das]

animesh,
i could not see any AT log ....please enable the logs first and collect one

second thing is comment out sim_io

[animesh arora]

where we can enable AT log message by default it is coming for RIL layer,i dont know where we can enable for JAVA layer which i am getting after pressing the call button.

[arindam das]

JAVA logs are coming by default but not the refernce ril log.
 
go to hardware/ril/reference-ril.c

and check log_tag is defined or not??
If in this file LOG_TAG is defined something other than "RIL",then u have to give
logcat-b radio&logcat& to get log

similarly in same path u can check for the at parser files for the logs.

I presume due to some at commands ur modem is hanging and nothing proceeds...

[Maffiou]

Hello Ani.

I'm assuming your using the reference ril...

The simplest way of removing sim ios is to comment the case
RIL_REQUEST_SIM_IO in onRequest in hardware/ril/reference-ril/
reference-ril.c

Not sure it will solve your issues, but I think it is worth a try.

M.

On Mar 4, 12:28 pm, animesh arora <animesharora...@gmail.com> wrote:
> Hi Arrin/Moffiou
>
> Please tell me clearly i what i need to comment out,are you telling about to
> comment out the particular SIMIO related AT Command.
>
> Tell me is there possiblity of blocking GSM AT interfaced channel,so i am
> not able to call.If yes tell me how we can test it out wheather it is got
> blocked or not?
>
> Is there any procedure to test it out?
>
> Regards
>
> ANI
>
>
>
>
>
>
>
> On Fri, Mar 4, 2011 at 12:08 PM, arindam das <das.ar...@gmail.com> wrote:
> > Hi Animesh,
> >                   I can see in ur log
>
> > D/RILJ    ( 1748): [0067]> DIAL
>
> > but it didnt result to any AT command(hoping that the IPC mechanism is AT).
>
> > No log is coming from reference-ril.so(or whatever logtag you ahve given in
> > reference-ril.c code)
>
> > Please check first those logs are enabled or not...may be something is
> > failing from there itself.
>
> > And I totally agree with maffiou,comment out the SIM_IO(at+crsm calls)
> > request from your ril code and check whether it proceeds with  the MO call
> > or not
>
> >   On Fri, Mar 4, 2011 at 11:50 AM, animesh arora <

> >> On Thu, Mar 3, 2011 at 8:48 PM, Maffiou <maff...@gmail.com> wrote:
>
> >>> From what I can tell, your log doesn't reach a point where it is
> >>> trying to make a call. You seem to have some issue much before that
> >>> point. And from what I can tell, it's definitely RIL/Modem level, not
> >>> likely anything to do with the rest of the android SW.
>
> >>> It would be interesting to see how long it takes for all those SIM
> >>> request to be processed, there are quite a few piled up and you seem
> >>> to get stuck while processing one of those.  Maybe adding "-v time"
> >>> when capturing the logcat can show some relevant information.
>
> >>> I don't think the sim io's are essential, so I would shunt these
> >>> temporarily and see if that improves things as first step.
>
> >>> Cheers.
> >>> M.
>
> >>> On Mar 2, 4:05 pm, animesh arora <animesharora...@gmail.com> wrote:
> >>> > I already shared the complete log with the first post itself?
> >>> > is there anyway to check the baudrate after boots up of android?
> >>> > What is exactly happen while calling through dialer inside the complete
> >>> > android stack.
> >>> > Because when i am calling dialing screen i am able to see,but i am not
> >>> able
> >>> > to get call at other side.
> >>> > is there anyway for debugging complete stack after dial the no. through
> >>> > dialer????
>

> ...
>
> read more »

[animesh arora]

Now i able to make a call with my device no. after commenting SIM_IO functionality,but i am not able to recieve the call, if i am calling through my mobile to that device no..only 2 rings are going after that call is droping out.
What may be the issue.
What will be the uses of SIM_IO functionality,which i commented,is it useful for recieving the call????

Regards

ANI.

[Maffiou]

There can be multiple reason for the incoming call not working... I
don't think it is linked to your commenting of the SIM_IO (but I could
be wrong!)...
Does the call drop as you try to answer it or just by itself? What
modem do you use? I would check the documentation to make sure it
supports the generic at commands used by the ref ril (maybe you can
try the use case stand alone, without the ril to validate at command
support).

If that doesn't get you anywhere, then, you may need to share some
logs as a next step. Remember to include the timestamps as they help
understand the dynamics.

M.

On Mar 7, 9:30 am, animesh arora <animesharora...@gmail.com> wrote:
> Now i able to make a call with my device no. after commenting SIM_IO
> functionality,but i am not able to recieve the call, if i am calling through
> my mobile to that device no..only 2 rings are going after that call is
> droping out.
> What may be the issue.
> What will be the uses of SIM_IO functionality,which i commented,is it useful
> for recieving the call????
>
> Regards
>
> ANI.
>
>
>
>
>
>
>
> On Fri, Mar 4, 2011 at 7:07 PM, arindam das <das.ar...@gmail.com> wrote:
> > JAVA logs are coming by default but not the refernce ril log.
>
> > go to hardware/ril/reference-ril.c
>
> > and check log_tag is defined or not??
> > If in this file LOG_TAG is defined something other than "RIL",then u have
> > to give
> > logcat-b radio&logcat& to get log
>
> > similarly in same path u can check for the at parser files for the logs.
>
> > I presume due to some at commands ur modem is hanging and nothing
> > proceeds...
>

> > On Fri, Mar 4, 2011 at 6:27 PM, animesh arora <animesharora...@gmail.com>wrote:
>
> >> where we can enable AT log message by default it is coming for RIL layer,i
> >> dont know where we can enable for JAVA layer which i am getting after
> >> pressing the call button.

> >> On Fri, Mar 4, 2011 at 6:04 PM, arindam das <das.ar...@gmail.com> wrote:
>
> >>> animesh,
> >>> i could not see any AT log ....please enable the logs first and collect
> >>> one
>
> >>> second thing is comment out sim_io
>

> >>> On Fri, Mar 4, 2011 at 5:58 PM, animesh arora <animesharora...@gmail.com

> >>> > wrote:
>
> >>>> Hi Arrin/Moffiou
>
> >>>> Please tell me clearly i what i need to comment out,are you telling
> >>>> about to comment out the particular SIMIO related AT Command.
>
> >>>> Tell me is there possiblity of blocking GSM AT interfaced channel,so i
> >>>> am not able to call.If yes tell me how we can test it out wheather it is got
> >>>> blocked or not?
>
> >>>> Is there any procedure to test it out?
>
> >>>> Regards
>
> >>>> ANI
>

> >>>> On Fri, Mar 4, 2011 at 12:08 PM, arindam das <das.ar...@gmail.com>wrote:
>
> >>>>> Hi Animesh,
> >>>>>                   I can see in ur log
>
> >>>>> D/RILJ    ( 1748): [0067]> DIAL
>
> >>>>> but it didnt result to any AT command(hoping that the IPC mechanism is
> >>>>> AT).
>
> >>>>> No log is coming from reference-ril.so(or whatever logtag you ahve
> >>>>> given in reference-ril.c code)
>
> >>>>> Please check first those logs are enabled or not...may be something is
> >>>>> failing from there itself.
>
> >>>>> And I totally agree with maffiou,comment out the SIM_IO(at+crsm calls)
> >>>>> request from your ril code and check whether it proceeds with  the MO call
> >>>>> or not
>
> >>>>>   On Fri, Mar 4, 2011 at 11:50 AM, animesh arora <

> ...
>
> read more »

[arindam das]

SIM_IO is used for reading writing to sim e.g. MS-ISDN list,reading writing SMSC number,reading writing sim contacts,try  to capture some logs..without which it will very difficult to suggest anything

[animesh arora]

Call is automatically droping whenever i am trying to call that no.after 2 rings.its automatically using AT+CHLD=0,and droping the call.Not able to find why it is going automatically in that case of reference-ril.

Can anyone suggest how we can check the flow for these type of Unsollicited calls like incoming call,incoming SMS.Is there any proper way to check it.And how it is communicating through JNI/JAVA for these UNSOLICITED calls.i know it is using socket,but is there any procedure to check this flow,and where we are strucking.

Please let me know any type of Debugger also for target debugging for RIL.

Regards

ANI.

[arindam das]

collect one log...will be interesting to see how telephony framework can reject a call automaticaly....my hunch is its getting any unsol indication from the modem.


ima afraid that logs are the only possible way to debug. :(

-ari

[animesh arora]

That only i am not getting.Log only is not helpful to debug.Need inside technical solution how we can do it.
Have anybody debuged these type for problems for RIL?????

[arindam das]

dude..i dnt know which board you are using for testing and it gives you any port to debug android ril realtime or not....
but im pretty much sure you have to start getting accustomed with logs for debugging

[animesh arora]

Its surley supports voice calls,for time beeing i am commenting the AT+CHLD=0,so able to get call continously,but not able to get why incoming call screen is not coming???

Can anybody suggest how we can debug the code for telephony to ril code flow.

[Maffiou]

Have you provisioned voice call in your sqlite DB?

In an adb root shell:

$ cd /data/data/com.android.providers.settings/databases
$ sqlite3 settings.db
<sqlite> INSERT INTO secure (name, value) VALUES
('device_provisioned', 1);
<sqlite> .exit
$ reboot

I think that should probably take care of your problem.

m.

[animesh arora]

Now able to recieve and send call,but in both the cases the call timer will not stop even we will cut the call from other side.

Is there any more service we need to run?

[Maffiou]

There are several possible things:

Does the problem happen on outgoing calls as well as incoming calls (
all remote hangup, of course)

If it's only on incoming call, you may need to check if your modem is
generating multiple ring indications, i think there is a setting you
can use to let the framework know.

If it's on all calls, then it may be a network thing, which is not
explicitely terminating calls when the remote party hangs up. BT
Cellnet used to do that, maybe that still the case on some networks...

In all, a set of logs would tell you.

M.

[animesh arora]

ya its happening for all the calls either incoming or outgoing the call timer GUI will not go even we will cut the call from other side.

[animesh arora]

Can you tell me more clear what you told in this sentance

" network thing, which is not explicitely terminating calls when the remote party hangs up."

Please let me know how we can solve this problem.

[Maffiou]

Well, If I remember well, some networks aren't terminating calls
explicitely when the remote party is hanging up... I remember that
this was the case on BT cellnet in the UK about 10 years ago... Could
it be that one of the network where you are could still be configured
like that, don't know...

What happens if you put your sim card into a reference phone? Does it
release the call? If not, then I don't think there is much you can
do... (maybe try on a different network?)

If the reference phone releases the call, then you should study your
modem documentation to see if there is a way to configure these
notifications... If not, then you may have to poll the call state
regularly with a command like at+clcc

M.

On Mar 25, 2:29 pm, animesh arora <animesharora...@gmail.com> wrote:
> Can you tell me more clear what you told in this sentance
> " network thing, which is not explicitely terminating calls when the remote
> party hangs up."
> Please let me know how we can solve this problem.
>

> On Fri, Mar 25, 2011 at 7:26 AM, animesh arora <animesharora...@gmail.com>wrote:
>
>
>
>
>
>
>
> > ya its happening for all the calls either incoming or outgoing the call
> > timer GUI will not go even we will cut the call from other side.
>

> > On Thu, Mar 24, 2011 at 9:12 AM, Maffiou <maff...@gmail.com> wrote:
>
> >> There are several possible things:
>
> >> Does the problem happen on outgoing calls as well as incoming calls (
> >> all remote hangup, of course)
>
> >> If it's only on incoming call, you may need to check if your modem is
> >> generating multiple ring indications, i think there is a setting you
> >> can use to let the framework know.
>
> >> If it's on all calls, then it may be a network thing, which is not
> >> explicitely terminating calls when the remote party hangs up. BT
> >> Cellnet used to do that, maybe that still the case on some networks...
>
> >> In all, a set of logs would tell you.
>
> >> M.
>

> >> On 24 March 2011 15:37, animesh arora <animesharora...@gmail.com> wrote:
> >> > Now able to recieve and send call,but in both the cases the call timer
> >> will
> >> > not stop even we will cut the call from other side.
> >> > Is there any more service we need to run?
>

> >> > On Thu, Mar 17, 2011 at 8:25 AM, Maffiou <maff...@gmail.com> wrote:
>
> >> >> Have you provisioned voice call in your sqlite DB?
>
> >> >> In an adb root shell:
>
> >> >>     $ cd /data/data/com.android.providers.settings/databases
> >> >>     $ sqlite3 settings.db
> >> >>     <sqlite> INSERT INTO secure (name, value) VALUES
> >> >> ('device_provisioned', 1);
> >> >>     <sqlite> .exit
> >> >>     $ reboot
>
> >> >> I think that should probably take care of your problem.
>
> >> >> m.
>

> >> >> On 17 March 2011 15:02, animesh arora <animesharora...@gmail.com>

> >> wrote:
> >> >> > Its surley supports voice calls,for time beeing i am commenting the
> >> >> > AT+CHLD=0,so able to get call continously,but not able to get why
> >> >> > incoming
> >> >> > call screen is not coming???
>
> >> >> > Can anybody suggest how we can debug the code for telephony to ril
> >> code
> >> >> > flow.
>

> >> >> > On Thu, Mar 17, 2011 at 1:13 AM, arindam das <das.ar...@gmail.com>

> >> >> > wrote:
>
> >> >> >> dude..i dnt know which board you are using for testing and it gives
> >> you
> >> >> >> any port to debug android ril realtime or not....
> >> >> >> but im pretty much sure you have to start getting accustomed with
> >> logs
> >> >> >> for
> >> >> >> debugging
>
> >> >> >> On Wed, Mar 16, 2011 at 9:35 PM, animesh arora

> >> >> >> <animesharora...@gmail.com>

> >> >> >> wrote:
>
> >> >> >>> That only i am not getting.Log only is not helpful to debug.Need
> >> >> >>> inside
> >> >> >>> technical solution how we can do it.
> >> >> >>> Have anybody debuged these type for problems for RIL?????
>

> >> >> >>> On Wed, Mar 16, 2011 at 9:00 AM, arindam das <das.ar...@gmail.com>

> >> >> >>>>> On Tue, Mar 8, 2011 at 2:42 AM, arindam das <das.ar...@gmail.com

>
> >> >> >>>>> wrote:
>
> >> >> >>>>>> SIM_IO is used for reading writing to sim e.g. MS-ISDN
> >> list,reading
> >> >> >>>>>> writing SMSC number,reading writing sim contacts,try  to capture
> >> >> >>>>>> some
> >> >> >>>>>> logs..without which it will very difficult to suggest anything
>
> >> >> >>>>>> On Mon, Mar 7, 2011 at 3:00 PM, animesh arora
> >> >> >>>>>> <animesharora...@gmail.com> wrote:
>
> >> >> >>>>>>> Now i able to make a call with my device no. after commenting
> >> >> >>>>>>> SIM_IO
> >> >> >>>>>>> functionality,but i am not able to recieve the call, if i am
> >> >> >>>>>>> calling through
> >> >> >>>>>>> my mobile to that device no..only 2 rings are going after that
> >> >> >>>>>>> call is
> >> >> >>>>>>> droping out.
> >> >> >>>>>>> What may be the issue.
> >> >> >>>>>>> What will be the uses of SIM_IO functionality,which i
> >> commented,is
> >> >> >>>>>>> it
> >> >> >>>>>>> useful for recieving the call????
>
> >> >> >>>>>>> Regards
>
> >> >> >>>>>>> ANI.
>
> >> >> >>>>>>> On Fri, Mar 4, 2011 at 7:07 PM, arindam das <

> >> das.ar...@gmail.com>

> >> >> >>>>>>> wrote:
>
> >> >> >>>>>>>> JAVA logs are coming by default but not the refernce ril log.
>
> >> >> >>>>>>>> go to hardware/ril/reference-ril.c
>
> >> >> >>>>>>>> and check log_tag is defined or not??
> >> >> >>>>>>>> If in this file LOG_TAG is defined something other than
> >> >> >>>>>>>> "RIL",then u
> >> >> >>>>>>>> have to give
> >> >> >>>>>>>> logcat-b radio&logcat& to get log
>
> >> >> >>>>>>>> similarly in same path u can check for the at parser files for
> >> >> >>>>>>>> the
> >> >> >>>>>>>> logs.
>
> >> >> >>>>>>>> I presume due to some at commands ur modem is hanging and
> >> nothing
> >> >> >>>>>>>> proceeds...
>
> >> >> >>>>>>>> On Fri, Mar 4, 2011 at 6:27 PM, animesh arora
> >> >> >>>>>>>> <animesharora...@gmail.com> wrote:
>
> >> >> >>>>>>>>> where we can enable AT log message by default it is coming
> >> for
> >> >> >>>>>>>>> RIL
> >> >> >>>>>>>>> layer,i dont know where we can enable for JAVA layer which i
> >> am
> >> >> >>>>>>>>> getting
> >> >> >>>>>>>>> after pressing the call button.
> >> >> >>>>>>>>> On Fri, Mar 4, 2011 at 6:04 PM, arindam das

> >> >> >>>>>>>>> <das.ar...@gmail.com>

> ...
>
> read more »

[animesh arora]

i dont think the service provider side will be any issue,its working in my mobile.So is there any problem on JAVA (RIL.java) in framework any problem?
DTMF Stop error is coming continuously.Is there any possibility that audio service is not killing automatically when we are making /receiving call, because audio flinger still not working,so thats why call gui also not going off automatically even we will cut the call.

> ...
>
> read more »

[Maffiou]

On Mar 27, 6:04 pm, animesh arora <animesharora...@gmail.com> wrote:
> i dont think the service provider side will be any issue,its working in my
> mobile.So is there any problem on JAVA (RIL.java) in framework any problem?

If you don't receive any end of call notification from the modem (I
think that what you said, but check your logcat!) then surely, the
framework can't guess that the call is over.. Pretty sure you problem
is a modem configuration issue.

> DTMF Stop error is coming continuously.Is there any possibility that audio
> service is not killing automatically when we are making /receiving call,
> because audio flinger still not working,so thats why call gui also not going
> off automatically even we will cut the call.

Are you talking about DTMF at ril level? These don't do any audio
locally, they just request the signalling to the remote party through
the modem. Once again, there is a chance that the reference RIL is not
suitable for your modem (it wasn't for mine !)

> ...
>
> read more »

[animesh arora]

All AT commands are properly suiting to my modem and getting the OK response also from modem side,what may be other issue at ril level?

> ...
>
> read more »

[nidroid]

Please check whether the communication channel (socket) between RIL.java and this layer is hapening properly....put logs and then check...