Apologies, as this is a re-reported issue. I had difficulty fully reporting my
previous issue post.
What steps will reproduce the problem?
1. Sent myself a text via an external email client.
2. Received text on phone with no notification appearing on the external
computer
3. Selected the "Remote Notifier" application on the smartphone.
4. The "Remote Notifier" application opened.
5. A battery usage notification appeared on the external computer.
What is the expected output? What do you see instead?
I had expected to see the "Remote Notifier" dialogue window appear on the host
computer when sending myself a test text from an external client to the phone.
I had opened, set and used "Remote Notifier" previously (within the last 15
minutes) and it was working quite brilliantly. Previously, I noticed that I
had received a text on my phone, but a dialogue had failed to display on my
computer. I have the "Growl" notifications set for permanent display, so all
notifications are left until manually recognized and removed.
Once I noticed an issue, I sent myself a "test" text and that is when I noticed
the application failure. I proceeded to open the "Remote Notifier" application
on my phone. After the application opened, I received a "Remote Notifier"
dialogue (and sound) notification on my host computer. I then proceeded to
send myself a test SMS from my email client (blah_blah@vtext.com). The "Remote
Notifier" dialogue fired on my host computer.
I've gone into the Android Terminal Emulator and performed a "pgrep
org.damazio.notifier" command, testing the application in various states.
1. Application running - Returned standard application ID
2. Quit application from "Task Manager" - Returned nothing
3. Application running for some time, but failing to send notifications to
host computer - Returned standard application ID
I'm inferring, from testing the application states, that something within the
package is timing out. I've utilized "Tasker" to automatically "pgrep" the
application ID on a timed basis and I noticed, again, that the notification
failure issue appears after some time elapses.
Please paste the application's log here (it should now be on your
clipboard):
I/WifiMonitor( 349): Event [ SCAN-RESULTS ]
I/WifiMonitor( 349): Event [ SCAN-RESULTS ]
I/WifiMonitor( 349): Event [ SCAN-RESULTS ]
I/WifiMonitor( 349): Event [ SCAN-RESULTS ]
V/WifiProgressStore( 7961): WifiProgressStore Created
I/SyncmlDcmoConnectorCallback( 7972): Get the local Bluetooth adapter is success
I/PhoneDataService( 998): start PhoneDataService!!!
I/PhoneDataService( 998): start PhoneDataService!!! Handler{405db970}
I/PhoneDataService( 998): start PhoneDataService!!! Handler{405d2ae0}
D/SyncmlLawmoConnectorCallback( 7972): SyncmlLawmoConnectorCallback()
D/PhoneDataService( 998): in getOemData
D/PhoneDataService( 998): imei = 990000238654570
I/PhoneDataService( 998): getImei = 990000238654570
D/PhoneDataService( 998): imei = 990000238654570
I/PhoneDataService( 998): getImei = 990000238654570
D/PhoneDataService( 998): Handle Message : 20
D/PhoneDataService( 998): in OEM_HIDDEN_GET_VERSION
D/PhoneDataService( 998): in OEM_HIDDEN_GET_VERSION : 15098
D/RemoteNotifier( 8023): Using level 5 caller ID
D/RemoteNotifier( 8023): Using real bluetooth utils
I/RemoteNotifier( 8023): Starting notification service
V/WifiProgressStore( 8023): WifiProgressStore Created
D/RemoteNotifier( 8023): Battery status: Discharging
D/RemoteNotifier( 8023): Got battery level: 100
D/RemoteNotifier( 8023): Battery level change: 101
D/RemoteNotifier( 8023): Notifying of battery state change
D/RemoteNotifier( 8023): Sending notification:
v2/26291a168af1b194/86bedd3cfa34ad/BATTERY/100/Discharging, remaining charge:
100%
D/RemoteNotifier( 8023): Sending wifi notification to IP 192.168.1.103
D/RemoteNotifier( 8023): Sending over UDP
D/RemoteNotifier( 8023): Sending wifi notification to IP 140.192.234.154
D/RemoteNotifier( 8023): Sending over UDP
D/RemoteNotifier( 8023): Sent over UDP
D/RemoteNotifier( 8023): Sending over TCP
D/RemoteNotifier( 8023): Sent over UDP
D/RemoteNotifier( 8023): Sending over TCP
D/RemoteNotifier( 8023): Sent over TCP
I/RemoteNotifier( 8023): Sent notification over WiFi.
D/RemoteNotifier( 8023): Sent over TCP
I/RemoteNotifier( 8023): Sent notification over WiFi.
D/RemoteNotifier( 8023): Battery status: Discharging
D/RemoteNotifier( 8023): Got battery level: 100
D/RemoteNotifier( 8023): Battery level change: 0
D/RemoteNotifier( 8023): Got battery update, but state change was not relevant
D/RemoteNotifier( 8023): Battery status: Discharging
D/RemoteNotifier( 8023): Got battery level: 100
D/RemoteNotifier( 8023): Battery level change: 0
D/RemoteNotifier( 8023): Got battery update, but state change was not relevant
Sent from my Droid Charge on Verizon 4G LTE
What version of Android are you using? Gingerbread - 2.3.6
Original issue reported on code.google.com by jevri...@gmail.com on 23 Dec 2011 at 11:33
Original issue reported on code.google.com by
jevri...@gmail.comon 23 Dec 2011 at 11:33