Unable to receive calls using Master build

[jseghers]

When trying to receive a call on an ADP1 using the current master
build, I get this indication in the normal logcat:
D/CallNotifier( 95): RING before NEW_RING, skipping
D/CallNotifier( 95): RING before NEW_RING, skipping

Looking at the radio log, I see this sequence with an exception:

D/HTC_RIL ( 31): (t=1239163028)>> AT+CLCC
D/HTC_RIL ( 31): (t=1239163028)<< +CLCC: 2,1,4,0,0,"12062640979",128
D/HTC_RIL ( 31): 0
D/HTC_RIL ( 31): ril_func_chk_call_state_until_none():called
D/HTC_RIL ( 31): ril_func_chk_call_state_until_none():clcc already
keeping polling (1)
D/HTC_RIL ( 31): req_rsp_pair_retry_default():(0, 0x00000000) 15-th
retries
D/RILJ ( 95): [0210]> GET_CURRENT_CALLS
D/HTC_RIL ( 31): ril_func_get_call_list():called
D/HTC_RIL ( 31): (t=1239163029)>> AT+CLCC
D/HTC_RIL ( 31): (t=1239163029)<< +CLCC: 2,1,4,0,0,"12062640979",128
D/HTC_RIL ( 31): 0
D/HTC_RIL ( 31): ril_func_chk_call_state_until_none():called
D/HTC_RIL ( 31): ril_func_chk_call_state_until_none():clcc already
keeping polling (1)
W/RILJ ( 95): [0210]< GET_CURRENT_CALLS exception, possible
invalid RIL response
W/RILJ ( 95): com.android.internal.telephony.ATParseEx: illegal
presentation 49
W/RILJ ( 95): at
com.android.internal.telephony.gsm.DriverCall.presentationFromCLIP
(DriverCall.java:140)
W/RILJ ( 95): at
com.android.internal.telephony.gsm.RIL.responseCallList(RIL.java:2360)
W/RILJ ( 95): at
com.android.internal.telephony.gsm.RIL.processSolicited(RIL.java:1791)
W/RILJ ( 95): at
com.android.internal.telephony.gsm.RIL.processResponse(RIL.java:1726)
W/RILJ ( 95): at com.android.internal.telephony.gsm.RIL.access
$300(RIL.java:186)
W/RILJ ( 95): at com.android.internal.telephony.gsm.RIL
$RILReceiver.run(RIL.java:512)
W/RILJ ( 95): at java.lang.Thread.run(Thread.java:1058)
D/RILJ ( 95): [0211]> GET_CURRENT_CALLS
D

Looking at the exception, it would appear that the radio driver data
parcel is out of sync with RIL.java.

I've tried both the 1.0 and 1.1 radio firmwares, but they both behave
the same.

What needs to be done to make this work?

[wjcs]

Hi jseghers:

I am not sure if your problem is the same as mine, cause I got more error messages in logcat than you did for incoming call. Following is the message log from logcat.

=========================================================

D/CallNotifier(   93): RING before NEW_RING, skipping

D/CallNotifier(   93): RINGING... (new)

D/CallNotifier(   93): onNewRingingConnection(): incoming

I/CallNotifier(   93): CallNotifier: rejecting incoming call: device isn't provisioned

D/CallNotifier(   93): DISCONNECT

D/CallNotifier(   93): - onDisconnect: cause = INCOMING_REJECTED, incoming = true, date = 1239167752109

=========================================================

As you can see, the problem is that my ADP1 is not provisioned. After I get the device  provisioned, I can receive call. Hope this'd help.

Best Regards,

wjcs 

[jseghers]

> As you can see, the problem is that my ADP1 is not provisioned. After I get
> the device  provisioned, I can receive call. Hope this'd help.

Do a google search for unlocking/activating ADP1 and you will find a
page that shows the
database entry to change...or (what I did to get around this in the
emulator) add a line
to packages/apps/Phone/src/com/android/phone/CallNotifier.java in
onNewRingingConnection()
set the boolean "provisioned" true after it gets the flag from the
settings.

I suspect, but am not sure, that this is the "provisioning" normally
done by associating a
gmail account with the phone--something I don't know how to do on the
Master build
(or even if it's possible since from what I've read you need to run
the Google Apps settings).

- John

[wjcs]

Hi John:

For now I'd rather add database entry than modify the source for device provisioning, cause, as far as I remembered, besides the NewRingingConnection the status of device_provisioned is also checked in few other places.

Provisioning is used in many places in telecommunication area (http://en.wikipedia.org/wiki/Provisioning , http://www.wisegeek.com/what-is-provisioning.htm), and I think provisioning here is related to the mobile subscriber or content provisioning. As you could see from the unlocking/activating ADP1 articles on the internet, device provisioning and Gmail account association are two different processes.

Steps on database entry modification are actually pretty much the same as the article you found on the internet. (For example http://android-tricks.blogspot.com/2009/01/using-adp1-without-sim-card.html)
But version 1.5 seemed to obsolete the device_provisioned in system table, so instead of
INSERT INTO system (name, value) VALUES ('device_provisioned', 1);
you need to use
INSERT INTO secure (name, value) VALUES ('device_provisioned', 1);

Hope this'd help.

Best Regards,
wjcs