Mic92 / android-notifier

Automatically exported from code.google.com/p/android-notifier
1 stars 0 forks source link

notification error when receiving a phone call and call will auto answer. #335

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Connected my Xperia X10 Mini Pro by bluetooth to windows xp laptop and start 
apps.
2. Receive phone call
3. Error message on pc and phone will autoanswer.

What is the expected output? What do you see instead?
I would expect a notification. Instead I get error message on pc. In the same 
time the phone will answer the call all by itself.

Please paste the application's log here (it should now be on your
clipboard):

E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(13446): Sending notification: 
v2/20000b39988a3cda/481dcf4dc7539/PING//Test notification
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(13446): Connecting to Bluetooth device JOYBOOK
D/RemoteNotifier(13446): Sent notification over Bluetooth (0 retries).
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Battery status: Charging
D/RemoteNotifier(13446): Got battery level: 100
D/RemoteNotifier(13446): Battery level change: 0
D/RemoteNotifier(13446): Got battery update, but state change was not relevant
D/RemoteNotifier(13446): Using donut SMS decoder
D/RemoteNotifier(13446): Using level 5 caller ID
D/RemoteNotifier(13446): Received Sms: SMS from xxx xxx - Mobile 
(+42077xxxxxxx): test
D/RemoteNotifier(13446): Sending notification: 
v2/20000b39988a3cda/8bb9bdccb4c020/SMS/+420775xxxxxx/SMS from xxx xxx - Mobile 
(+420775xxxxxx): xxx
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(13446): Connecting to Bluetooth device JOYBOOK
D/RemoteNotifier(13446): Sent notification over Bluetooth (0 retries).
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:Playing from /org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
D/BluetoothA2dpService( 1186): A2DP state : device: 00:19:7D:E3:86:5E State:2->4
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:Stopped from /org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
D/BluetoothA2dpService( 1186): A2DP state : device: 00:19:7D:E3:86:5E State:4->2
D/RemoteNotifier(13446): Sending notification: 
v2/20000b39988a3cda/8bb9bef62be45e/RING/+420775xxxxxx/xxx xxx - Mobile 
(+420775xxxxxx)
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(13446): Connecting to Bluetooth device JOYBOOK
I/Bluetooth AT sent( 1290): RING
I/Bluetooth AT recv( 1290): AT+CKPD=200
I/Bluetooth AT sent( 1290): OK
V/SemcInCallScreen( 1290): onNewIntent: intent=Intent { 
act=android.intent.action.MAIN flg=0x10c40000 
cmp=com.android.phone/.SemcInCallScreen }
I/Bluetooth HeadsetBase( 1290): headset read error 5
D/RemoteNotifier(13446): Waiting to retry
D/RemoteNotifier(13446): java.io.IOException: Connection timed out
D/RemoteNotifier(13446):    at 
android.bluetooth.BluetoothSocket.connectNative(Native Method)
D/RemoteNotifier(13446):    at 
android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:204)
D/RemoteNotifier(13446):    at 
org.damazio.notifier.notification.BluetoothNotificationMethod.doSendNotification
(BluetoothNotificationMethod.java:174)
D/RemoteNotifier(13446):    at 
org.damazio.notifier.notification.BluetoothNotificationMethod.sendNotification(B
luetoothNotificationMethod.java:120)
D/RemoteNotifier(13446):    at 
org.damazio.notifier.notification.Notifier.runNotificationThread(Notifier.java:1
69)
D/RemoteNotifier(13446):    at 
org.damazio.notifier.notification.Notifier.access$0(Notifier.java:165)
D/RemoteNotifier(13446):    at 
org.damazio.notifier.notification.Notifier$1.run(Notifier.java:91)
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.Device:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:Disconnected from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.AudioSink:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
D/BluetoothA2dpService( 1186): A2DP state : device: 00:19:7D:E3:86:5E State:2->0
D/RemoteNotifier(13446): Connecting to Bluetooth device JOYBOOK
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.Device:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.Device:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
D/RemoteNotifier(13446): Sent notification over Bluetooth (1 retries).
D/SemcInCallScreen( 1290): onDisconnect:  incoming: true state: DISCONNECTED 
post dial state: NOT_STARTED, cause=NORMAL
E/BluetoothEventLoop.cpp( 1186): event_filter: Received signal 
org.bluez.Device:PropertyChanged from 
/org/bluez/12689/hci0/dev_00_19_7D_E3_86_5E
D/BluetoothA2dpService( 1186): Auto-connecting A2DP to sink 00:19:7D:E3:86:5E
D/BluetoothA2dpService( 1186): connectSink(00:19:7D:E3:86:5E)
E/BluetoothService.cpp( 1186): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)

What version of Android are you using?

Original issue reported on code.google.com by soliton...@gmail.com on 10 Jan 2011 at 7:16

GoogleCodeExporter commented 8 years ago
I forgot to mention that my Xperia X10 mini pro runs android 2.1.

Original comment by soliton...@gmail.com on 10 Jan 2011 at 7:21

GoogleCodeExporter commented 8 years ago
Can anyone please help me with this issue??

I have an Android Sony Ericssion Xperia X10 - Version 1.6 (not mini, big one) 
and its been just two months after purchase that lately the 'call charge' 
balance (notification) amount seems to appear on my phone, without usage (i.e. 
if I have been charged or not, the balance still shows up with varied 
deductions that appear very often-like 2 msgs in a minute) I am unable to 
identify which is the actual balance and which is the error msg. So every time 
I have to check my balance by calling the service provider. But the account 
balance seems to be the same - meaning the error msgs are like spam 
notifications like the phone has a virus or something. I already had an anti 
virus installed but since this behavior was recent I even had the phone cleaned 
out from ALL apps and also ran a virus check and phone seems to be clean. But I 
get notified wrongly with these balances pop ups so many times that the phone 
freezes, and im unable to do anything but restart EVERytime I pick up the phone 
to use it!! Not sure how to fix this. 

Do you think upgrading the Android software to 2.x will fix the issue?? Or is 
there any other solution to this? 

Please help/comment/advise. Greatly appreciate your time.

Thanks,
Tanya.

Original comment by sonia.ba...@gmail.com on 26 Jan 2011 at 10:51