search

kailIII / android-notifier

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

Notifier service does not remove notification when terminated by android system #388

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start remote notifier with the persistent notification enabled
2. Use the phone a lot to eat up memory and get Android to kill off background 
processes.
3. ...
4. PROFIT!

What is the expected output? What do you see instead?
I'd expect the service to remove its notification or at least change it to 
indicate that its no longer running.

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

What version of Android are you using?
Cyanogenmod 6.1/ Droid (Android 2.2.1)

Original issue reported on code.google.com by abortretryfail@gmail.com on 9 May 2011 at 3:17

GoogleCodeExporter commented 9 years ago 
Notifications work fine before the service gets killed off by the OS:

I/ActivityManager( 1131): Process org.damazio.notifier (pid 5688) has died.
W/ActivityManager( 1131): Scheduling restart of crashed service org.damazio.noti
fier/.service.NotificationService in 48131ms
I/WindowManager( 1131): WIN DEATH: Window{45318098 org.damazio.notifier/org.dama
zio.notifier.NotifierMain paused=false}
I/ActivityManager( 1131): Start proc org.damazio.notifier for service org.damazi
o.notifier/.service.NotificationService: pid=7368 uid=10134 gids={3003, 3002, 30
01, 1007, 1015}
D/RemoteNotifier( 7368): Using level 5 caller ID

...Says it restarted, but i just sent myself a text, watched the notification 
hit the phone, but nothing is sent to the PC. The persistent notification still 
says "Remote Notifier: Listening and sending remote notifications" 

If i touch that notification it immediately sends a remote notification for 
battery level.

I/ActivityManager( 1131): Starting activity: Intent { cmp=org.damazio.notifier/.
NotifierMain bnds=[0,186][854,270] }
W/ActivityManager( 1131): startActivity called from non-Activity context; forcin
g Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { cmp=org.damazio.notifier/.Notifier
Main bnds=[0,186][854,270] }
D/RemoteNotifier( 7368): Restoring state
D/RemoteNotifier( 7368): Using real bluetooth utils
I/RemoteNotifier( 7368): Starting notification service
D/RemoteNotifier( 7368): Battery status: Charging
D/RemoteNotifier( 7368): Got battery level: 70
D/RemoteNotifier( 7368): Battery level change: 71
D/RemoteNotifier( 7368): Notifying of battery state change
I/ActivityManager( 1131): Displayed activity org.damazio.notifier/.NotifierMain:
 1075 ms (total 1075 ms)
D/RemoteNotifier( 7368): Sending notification: v2/5f025d36d46bd29/83adb29665b936
/BATTERY/70/Charging, remaining charge: 70%
D/RemoteNotifier( 7368): Sending wifi notification to IP 128.5.255.255
D/RemoteNotifier( 7368): Sending over UDP
D/RemoteNotifier( 7368): Sent over UDP
I/RemoteNotifier( 7368): Sent notification over WiFi.
D/RemoteNotifier( 7368): Battery status: Charging
D/RemoteNotifier( 7368): Got battery level: 70
D/RemoteNotifier( 7368): Battery level change: 0
D/RemoteNotifier( 7368): Got battery update, but state change was not relevant

Is the service not restarting properly?

Original comment by abortretryfail@gmail.com on 9 May 2011 at 3:39