Htc Desire crash on incomming call

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Receive a call 
2.
3.

What is the expected output? What do you see instead?
Get a program crash notification. 

Please paste the application's log here (it shoI/BluetoothHandsfree(  155): 
ring(): 
mIgnoreRing = false mRingingCall.isRinging()true
D/CallCard(  155): updatePhotoForCallState(INCOMING)...
D/InCallScreen(  155): onWindowFocusChanged(true)...
I/BluetoothHandsfree(  155): ring(): mIgnoreRing = false 
mRingingCall.isRinging()true
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothEventLoop.cpp(   75): event_filter: Received signal 
org.bluez.Device:PropertyChanged from /org/bluez/10076/hci0/
dev_60_FB_42_80_2B_67
D/BluetoothA2dpService(   75): Received intent Intent { 
act=android.bluetooth.device.action.ACL_DISCONNECTED (has extras) }
D/BluetoothA2dpService(   75): Received intent Intent { 
act=android.intent.action.PHONE_STATE (has extras) }
D/CallNotifier(  155): onDisconnect()...  phone state: IDLE
E/BluetoothHandsfree(  155): onCallDisconnected()
D/BluetoothHandsfree(  155): audioOff(): mPendingSco: false, mScoSocket: , 
mA2dpState: 0, mA2dpSuspended: false
D/PhoneUtils(  155): setAudioMode(MODE_NORMAL)...
D/CallNotifier(  155): resetAudioStateAfterDisconnect()...
D/PhoneUtils(  155): turnOnSpeaker(flag=false, store=true)...
D/PhoneApp(  155): setScreenTimeout(MEDIUM)...
D/PhoneApp(  155): requestWakeState(SLEEP)...
D/PhoneApp(  155): updateProximitySensorMode: state = IDLE
D/PhoneApp(  155): updateProximitySensorMode: lock already released.
D/PhoneUtils(  155): setAudioMode(MODE_NORMAL)...
D/CallNotifier(  155): - callLogType: 3, UserData: 
com.android.phone.PhoneUtils$CallerInfoToken@46689e50
D/PhoneUtils(  155): modifyForSpecialCnapCases: initially, number=, 
presentation=1
D/PhoneUtils(  155): checkCnapSpecialCases, normal str. number: 
D/PhoneUtils(  155): modifyForSpecialCnapCases: returning number string=
D/CallNotifier(  155): getLogNumber: 
D/PhoneUtils(  155): startGetCallerInfo: updatedNumber initially = 
D/PhoneUtils(  155): startGetCallerInfo: No query to attach to, send trivial 
reply.
D/PhoneUtils(  155): startGetCallerInfo: CNAP Info from FW(3): name=null, 
Name/Number Pres=1
D/CallNotifier(  155): showMissedCallNotification: Querying for CallerInfo on 
missed call...
D/NotificationFlashLightUtility getIncomingCall(  155): load fail~~~~~~~~~~
D/PhoneApp(  155): setScreenTimeout(MEDIUM)...
D/PhoneApp(  155): requestWakeState(SLEEP)...
D/InCallScreen(  155): - onDisconnect: bailOutImmediately...
D/InCallScreen(  155): - delayedCleanupAfterDisconnect: phone is idle...
D/InCallScreen(  155): - delayedCleanupAfterDisconnect: finishing 
InCallScreen...
D/InCallScreen(  155): setInCallScreenMode: UNDEFINED
D/BluetoothHandsfree(  155): updatePhoneState()
D/CallNotifier(  155): onPhoneStateChanged: state = IDLE
D/PhoneApp(  155): updateProximitySensorMode: state = IDLE
D/PhoneApp(  155): updateProximitySensorMode: lock already released.
D/PhoneApp(  155): updateProximitySensorMode: state = IDLE
D/PhoneApp(  155): updateProximitySensorMode: lock already released.
D/PhoneUtils(  155): ConnectionHandler: updating mute state for each 
connection
D/PhoneUtils(  155): setMute: false
D/PhoneUtils(  155):  setMicrophoneMute: false
D/InCallScreen(  155): onPhoneStateChanged()...
D/InCallScreen(  155): updateScreen()...
D/InCallScreen(  155): dismissMenu(immediate = true)...
D/InCallScreen(  155): - updateScreen: updating the in-call UI...
D/CallCard(  155): updateState(Phone: Handler{464f1278}, personId: null)...
D/CallCard(  155): updateNoCall()...
D/CallCard(  155): displayMainCallStatus(phone Handler{464f1278}, call null)...
D/InCallScreen(  155): updateProviderOverlay: false
D/InCallScreen(  155): updateMenuButtonHint()...
D/PhoneApp(  155): setScreenTimeout(MEDIUM)...
D/PhoneApp(  155): requestWakeState(SLEEP)...
D/InCallScreen(  155): updateProviderOverlay: false
D/InCallScreen(  155): dismissMenu(immediate = true)...
D/InCallScreen(  155): dismissAllDialogs()...
E/PhoneApp(  155): mStatusBarDisableCount is already zero
D/PhoneApp(  155): setScreenTimeout(DEFAULT)...
D/PhoneApp(  155): requestWakeState(SLEEP)...
D/InCallScreen(  155): onWindowFocusChanged(false)...
D/InCallScreen(  155): - onWindowFocusChanged: faking onDialerKeyUp()...
D/InCallScreen(  155): onStop()...
D/InCallScreen(  155): onStop: state = IDLE
D/PhoneApp(  155): setIgnoreTouchUserActivity(false)...
I/BluetoothA2dpService(   75): RESUME_PHONE_STATE
I/BluetoothHandsfree(  155): ring(): mIgnoreRing = false 
mRingingCall.isRinging()false
E/BluetoothHandsfree(  155): Not allow to sent RING, ignore it
D/RemoteNotifier(10281): Using level 5 caller ID
I/RemoteNotifier(10281): Starting notification service
D/RemoteNotifier(10281): Using real bluetooth utils
D/RemoteNotifier(10281): Battery status: Charging
D/RemoteNotifier(10281): Got battery level: 72
D/RemoteNotifier(10281): Notifying of battery state change
D/RemoteNotifier(10281): Sending notification: 200145745b838796/
45d00a805c958/BATTERY/Charging, remaining charge: 72%
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothService.cpp(   75): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothService.cpp(   75): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(10281): Connecting to Bluetooth device Johan Björklunds 
MacBook Pro
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothEventLoop.cpp(   75): event_filter: Received signal 
org.bluez.Device:PropertyChanged from /org/bluez/10076/hci0/
dev_60_FB_42_80_2B_67
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothEventLoop.cpp(   75): event_filter: Received signal 
org.bluez.Device:PropertyChanged from /org/bluez/10076/hci0/
dev_60_FB_42_80_2B_67
D/BluetoothService(   75): updateDeviceServiceChannelCache(60:FB:42:80:2B:67)
D/BluetoothService(   75):  uuid(application): 7674047e-6e47-4bf0-831f-
209e3f9dd23f 1
D/BluetoothService(   75): Making callback for 7674047e-6e47-4bf0-831f-
209e3f9dd23f with result 1
V/BluetoothEventRedirector(  171): Received 
android.bleutooth.device.action.UUID
D/RemoteNotifier(10281): Sent notification over Bluetooth (0 retries).
V/BluetoothEventRedirector(  171): Received 
android.bleutooth.device.action.UUID
E/AndroidRuntime(  160): Crash logging skipped, already logging another crash
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothService.cpp(   75): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
I/RemoteNotifier(10281): Starting notification service
D/RemoteNotifier(10281): Battery status: Charging
D/RemoteNotifier(10281): Got battery level: 72
D/RemoteNotifier(10281): Got battery update, but state change was not relevant
D/WifiService(   75): ACTION_BATTERY_CHANGED pluggedType: 0
D/RemoteNotifier(10281): Battery status: NOT charging
D/RemoteNotifier(10281): Got battery level: 72
D/RemoteNotifier(10281): Notifying of battery state change
D/RemoteNotifier(10281): Sending notification: 200145745b838796/
45d00c9723e47/BATTERY/NOT charging, remaining charge: 72%
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothService.cpp(   75): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothService.cpp(   75): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(10281): Connecting to Bluetooth device Johan Björklunds 
MacBook Pro
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothEventLoop.cpp(   75): event_filter: Received signal 
org.bluez.Device:PropertyChanged from /org/bluez/10076/hci0/
dev_60_FB_42_80_2B_67
D/BluetoothService(   75): updateDeviceServiceChannelCache(60:FB:42:80:2B:67)
D/BluetoothService(   75):  uuid(application): 7674047e-6e47-4bf0-831f-
209e3f9dd23f 1
D/BluetoothService(   75): Making callback for 7674047e-6e47-4bf0-831f-
209e3f9dd23f with result 1
V/BluetoothEventRedirector(  171): Received 
android.bleutooth.device.action.UUID
V/BluetoothEventRedirector(  171): Received 
android.bleutooth.device.action.UUID
D/RemoteNotifier(10281): Read log
D/WifiService(   75): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@464bb5d8}
D/WifiService(   75): enable and start wifi due to updateWifiState
D/WifiService(   75): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@464bb5d8}
D/WifiService(   75): enable and start wifi due to updateWifiState
E/BluetoothEventLoop.cpp(   75): pollData[0] is revented, check next one
E/BluetoothService.cpp(   75): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
uld now be on your
clipboard):


What version of Android are you using?
2.1 

Original issue reported on code.google.com by wh...@me.com on 4 May 2010 at 12:53

[GoogleCodeExporter]

E/AndroidRuntime(  160): Crash logging skipped, already logging another crash

This is sad, it didn't log the crash :( I'm not sure if I can do much without 
that log.
If you do manage to get a log which includes the crash, can you post it?

Original comment by rdamazio@gmail.com on 6 May 2010 at 1:31

• Added labels: OpSys-Android, Priority-High, Stability, Type-Defect

[GoogleCodeExporter]

Hmm, I'm a bit clueless on how to capture the crashlog in a reliable way. Still 
trying to get the hang of the 
Android SDK, trying to capure logs with ddms didn't do the trick. Though, I 
have done some more testing and 
have these two scenarios now:

Crash scenario: call my Desire from an hidden number (done by prefixing #31# to 
the telephone number).
Working scenario: call my Desire from a known number in the phonebook.

Next step is to call from an unknown number and see if it that leads to crashes.

Original comment by wh...@me.com on 14 May 2010 at 8:02

[GoogleCodeExporter]

Does this still happen with the latest version of the app?

Original comment by rdamazio@gmail.com on 23 Aug 2010 at 5:07

[GoogleCodeExporter]

No, it works just fine now.

Original comment by wh...@me.com on 23 Aug 2010 at 1:57

[GoogleCodeExporter]

Cool, thanks!

Original comment by rdamazio@gmail.com on 23 Aug 2010 at 2:30

• Changed state: Verified