CyanogenMod - Service termination/crash

[GoogleCodeExporter]

IMPORTANT: PLEASE search the existing issues (including closed ones) for
something similar before filing a new one.

What steps will reproduce the problem?
1. Needed CyanogenMod 6.1
2. Running the android-notifier service
3. Do not enable the icon in the status bar

What is the expected output? What do you see instead?
Well, I have now switched roms from Sense Roms (on my HTC Desire) to the 
CyanogenMod 6.1, and everything (all services from 3rd party apps) work just 
fine. 

However, the android-notifier service seems to terminate OR crash from time to 
time. It gets starts just after boot, and I see the battery notification on the 
computer, but after 5-10 minutes, it just doesnt work. 

I have excluded the service from the task-killer, and I repeat, it used to work 
on the Sense Rom (LeeDroid2.2f), but not on the CyanogenMod6.1 - I think it 
crashes.

What version of the product are you using? On what operating system?

Windows 7 64bit, Mac 10.6 64bit, Ubuntu 10.10 32bit, HTC Desire CyanogenMod 6.1

Please provide the log output if possible (from the alogcat app on android,
Show Log menu on the multiplatform client, or Console on native mac app):

Please provide any additional information below.

If you could tell me how I could get the log out of the HTC desire, I would 
paste it here :)

Original issue reported on code.google.com by mofir...@gmail.com on 26 Nov 2010 at 10:23

[GoogleCodeExporter]

Also, just tried it on DeFrost 6.0j, and it seems like it crashes.

My guess is that it crashes due to not finding the icons for specific apps?? 

The reason I know that the service crashes is that, once you go into the 
RemoteNotifier app, a little battery notification is sent and instantly shown 
on the computer, but before doing this, no notifications would be shown.

PLEASE PLEASE PLEASE fix this bug. It is so annoying that you can't rely on the 
app right now!

Thank you.

Original comment by mohammed...@gmail.com on 2 Dec 2010 at 11:40

[GoogleCodeExporter]

This is normal Android behaviour - background services can get killed if it's 
running low on memory. The notifier will restart on certain events, but not all 
of them. Your alternative is to make it a foreground service by enabling the 
notification icon. That doesn't prevent this behaviour, just makes it less 
frequent.
I have no idea why people use Task killers, also, since there's no point in 
killing tasks in Android.

If it actually crashes, please file a bug with proper logs.

Btw, CyanogenMod is not officially supported since it didn't pass Google's CTS, 
so it may be behaving differently from regular Android.

Original comment by rdamazio@gmail.com on 9 Dec 2010 at 11:58

• Changed state: Invalid