Why emulator cannot recieve incoming call?

by bluebol...@gmail.com » Wed, 29 Apr 2009 01:07:48 GMT


Sponsored Links
 I make android source code and try to emulate the image.
A problem occurr when I dial.

MO call works well, but MT call always can't apply to UI.
On the other hand, Android SDK MT/MO both work well.
I found the problem is caused by
D/GSM     (   84): [CallTracker] (ringing) hangup waiting or
background
Up layer always send a hangup event when it get Incoming call state.
How can I fix it?


Here is the radio log

D/RILJ    (   84): [0103]< SIGNAL_STRENGTH {7, 99}
D/RILJ    (   84): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=1
D/RILJ    (   84): 0: [14] SET_NETWORK_SELECTION_AUTOMATIC
D/AT      (   21): AT< RING
D/RILJ    (   84): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ    (   84): [0104]> GET_CURRENT_CALLS
D/RIL     (   21): onRequest: GET_CURRENT_CALLS
D/AT      (   21): AT> AT+CLCC
D/AT      (   21): AT< +CLCC: 1,1,4,0,0,"5556",129
D/AT      (   21): AT< OK
D/RILJ    (   84): [0104]< GET_CURRENT_CALLS
[id=1,mt,INCOMING,voice,norm,129,0]
D/GSM     (   84): [GSMConn] acquireWakeLock
D/GSM     (   84): [CallTracker] (ringing) hangup waiting or
background
D/RILJ    (   84): [0105]> HANGUP_WAITING_OR_BACKGROUND
D/RIL     (   21): onRequest: HANGUP_WAITING_OR_BACKGROUND
D/AT      (   21): AT> AT+CHLD=0
D/AT      (   21): AT< OK
D/RILJ    (   84): [0105]< HANGUP_WAITING_OR_BACKGROUND
D/RILJ    (   84): [0106]> GET_CURRENT_CALLS
D/RIL     (   21): onRequest: GET_CURRENT_CALLS
D/AT      (   21): AT> AT+CLCC
D/AT      (   21): AT< OK
D/RILJ    (   84): [0106]< GET_CURRENT_CALLS
D/GSM     (   84): [CallTracker] missed/rejected call,
conn.cause=LOCAL
D/GSM     (   84): [CallTracker] setting cause to INCOMING_REJECTED
D/GSM     (   84): [GSMConn] onDisconnect: cause=INCOMING_REJECTED
D/GSM     (   84): [GSMConn] releaseWakeLock
D/RILJ    (   84): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ    (   84): [0107]> GET_CURRENT_CALLS
D/RILJ    (   84): [0108]> SIGNAL_STRENGTH
D/RIL     (   21): onRequest: GET_CURRENT_CALLS
D/AT      (   21): AT> AT+CLCC
D/AT      (   21): AT< OK
D/RIL     (   21): onRequest: SIGNAL_STRENGTH
D/AT      (   21): AT> AT+CSQ
D/RILJ    (   84): [0107]< GET_CURRENT_CALLS
D/AT      (   21): AT< +CSQ: 7,99
D/AT      (   21): AT< OK
D/RILJ    (   84): [0108]< SIGNAL_STRENGTH {7, 99}
D/RILJ    (   84): WAKE_LOCK_TIMEOUT  mReqPending=0 mRequestList=1
D/RILJ    (   84): 0: [14] SET_NETWORK_SELECTION_AUTOMATIC

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Update WTS: nexian journey dgn/ tanpa paket 3

Unit tinggal 1...  thx smuanya

back to desire from journey



-- 
===============
"

2. PAGING User Milestone/Droid : Milestone gw error.. need Help..

sebelumnya maaf ane memanggil temen2 user milestone/droid. soalnya ane
sendiri sudah dibikin pusing ama masalah ini dr kmrn siang.. ane
langsung aja yaa mastah2..

berawal (27/12) dari gw meng-remove batterystats.bin via terminal
(kmrn gw sempet ngelakuin ini: Go into terminal and type "su" and then
"rm /data/system/batterystats.bin" Then reboot.), setelah itu
berlangsung normal aja.

trus kmrn siang (28/12) ane charge full 100%, sempet sms dan ngegame
sebentar. setelah itu ane aktifin layanan internet bulanan XL dan
miley sync contact otomatis. selagi proses, tiba2 miley ane mati. dan
ga mau nyala ampe skrg.

ane cb charge (dalam keadaan sudah mati) dan hp terditek 5%. setelah
ane tinggalin 30 menit kok masih tetep 5%. lalu ane pindahin ke usb
laptop, tp gada tanda2 idup. miley ane msh matot.

saat itu ane msh pikir mgkn ada mslh sama batere ane. tp mlmnya tmn
ane yg pake miley dtg, dan ane cobain baterenya ternyata msh sama,
dicharge dlm keadaan mati tetep 5%. namun batery ane dicobain di miley
tmn ternyata full, dlm arti normal. so ane nyimpulin bukan batere nya.

setelah itu, ane cb masuk ke boot loader (dlm keadaan hp msh ke
charge) dan berhasil, tp keditek "battery low, cannot program". ane cb
cabut chargernya, dan kembali matot.

namun ane ngakalin biar bs idup. caranya ane masuk bootloader (kembali
sambil di charge) setelah masuk, ane lgsg tekan tombol power dan
akhirnya berhasil masuk/idup.. tp tetep batery indicator 5%. setelah
idup ane lgsg masuk OP, dan ganti custom ROM (yang awalnya dari CM
6.1.1 versi terbaru, dicoba pake versi lama. dan akhirnya td pagi cb
MIUI terbaru). tp hasilnya nihil tetep 5% ampe detik ini ane tancain
charger masih 5%.

indicator batter 5% dan battery voltage 2415 mV.

ane udah sharing di lounge motorola kaskus, dan merepotkan agan
dandangtohell aka danang prakoso. thx a lot gan udah ane bikin ikut
bingung.

ane bingung gan :(, miley ane garansi starhub (BM), dan baru beli 6
des ini..
moga kiranya ane share disini, temen2 bs bantu.. please help me.. :
( thanks semuanya..

-- 
===============
"

3. how to avoid cut off of words in TextView

4. [WTA] Aplikasi Aktif, tapi saya tak mengakrifkanya. .

5. Android SDK and AVD Manager - permission denied: connect

6. FYI : Kemudahan Fitur Navigasi di Ponsel Pintar HTC Desire HD

7. Writing a Date/Time Service