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 <
> > animesharora...@gmail.com> wrote:
>
> >> 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
>
> >> 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 »
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
