Michael:
Thanks for your concern!
I had found that, I missed the connection to the 'rild' socket. And modify
the code in RIL.java to make sure the host and client socket is matched.
BTW:
In RIL.java, class RILReceiver,
493 try {
494 InputStream is = mSocket.getInputStream();
495
496 for (;;) {
497 Parcel p;
498
499 length = readRilMessage(is, buffer);
500
501 if (length < 0) {
502 // End-of-stream reached
503 break;
504 }
505
506 p = Parcel.obtain();
507 p.unmarshall(buffer, 0, length);
508 p.setDataPosition(0);
509
510 Log.v(LOG_TAG, "Read packet: " + length + "
bytes");
511
512 processResponse(p);
513 p.recycle();
514 }
RIL.java can write packet to rild, and Read packet from rild.
But, when i dial, it shows that network is not registered.
What's the problem?
When it exec processResponse(p), processSolicited,
1871 if (rr.mResult != null) {
1872 AsyncResult.forMessage(rr.mResult, ret, null);
1873 rr.mResult.sendToTarget();
1874 }
Where dose the Message go? Which application will get the Message? How does
the application show the Message? I'm not clear about the android
application/framworks level. :-(
Thanks & best regards
On Sat, Oct 17, 2009 at 12:06 AM, Michael Trimarchi <
trimar...@gandalf.sssup.it> wrote:
>
> Xingwen Huang wrote:
> > any idea? please
> >
> > On Wed, Sep 30, 2009 at 10:18 AM, simon <hxwsi...@gmail.com
> > <mailto:hxwsi...@gmail.com>> wrote:
> >
> > hi, all experts:
> > my log:
> > D/AT ( 29): AT< +CREG: 1, "247C", "0E26", 0
> > D/RIL ( 29): in onUnsolicited *********reference-ril.c***
> > D/RIL ( 29): unsol_response_network_state_changed
> > D/RILC ( 29): sendResponseRaw in ril.cpp************
> > D/RILC ( 29): s_fdCommand socket number = -1*******
> > D/RILC ( 29): in internalRequestTimedCallback**************
> > D/RILC ( 29): ******fd = -1 in ril_event_set********
> > D/RILC ( 29): *************initialize an event in
> > ril_event_set,ril_event.cpp in libril
> > D/RILC ( 29): fd is -1, in internalRequestTimedCallback
> > D/RILC ( 29): *********triggerEvLoop in
> > ril.cpp*****s_fdWakeupWrite=7
> > D/RIL ( 29): out onUnsolicited*****************
> > D/RILJ ( 77): WAKE_LOCK_TIMEOUT mReqPending=0 mRequestList=0
> >
> > focused on this log, it received the CREG unsolicited response. It
> > will write datas to the socket-- s_fdCommand, then the application
> > will get it.
> > That's my idea!
> > But s_fdCommand is -1. I traced the code, and found that,
> > in ril.cpp, listenCallback func:
> > s_fdCommand = accept(s_fdlisten, (sockaddr *)&peeraddr, &socklen);
> >
> > this code doesn't run at any time!!!!!!
> > And, in my opinion, listenCallback is the func of the event
> > s_listen_event.
> > Is s_listen_event not triggered????? Or others?????
> > any idea???
> >
> Can you send a complete log of all the event. Seem the referecne ril go
> in timeout
> and close connection.
>
> Michael
> >
> > Thanks & regards
> >
> > simon
> >
> >
> >
> > >
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
