IssueTracker

It seems like it's also not restarted when being killed due to a low memory condition. This is a serious issue!

Same as 63618 issue reported before.

Ruins battery notifications

Had to stop using this. Too bad, loved it.

Why is this rated a "Priority-Small" ? This makes all applications that use a background service useless

Same for apps showing widgets! Even those apps Google rated best apps from best developers, are affected by this!

Can only be a mistake. Or its like killing all Play Store apps, except games. Could it be intentional? I can't believe it yet.

[Comment deleted]

Yes, the service stops in any moment. I think it's a big problem. In lower versions no problem with the background service.

Same issues here. This is indeed a serious problem.

I'm having similar issues. Real problems also with the notificationlistener service just stopping sending notifications to apps without a reboot.

Must be fixed!

[Comment deleted]

[Comment deleted]

This is a significant problem. START_STICKY services are being killed by the Android system (presumably because resources are low?) and are never restarted. This behavior has been observed on multiple Nexus 5 devices running Android 4.4.2.

Also, START_STICKY services attached to activities that are cleared out of the Recent Apps list are also being killed and never restarted (see issue 36949180). This behavior has been observed on multiple Nexus 5 devices running Android 4.4, 4.4.1, and 4.4.2.

I have same problem with app widgets, my app widget has a back-end service which on 4.4.2 stops and never restarts.

Confirmed fir the Nexus 4 as well.
Op 29 dec. 2013 08:07 schreef <android@googlecode.com>:

This needs to be prioritized!

Only Google apps aren't affected by this bug, really need to be prioritized!!

In Nexus 7 (upgraded to 4.4.2), service is running in the background but not bring to front.
Very high priority issue!! Please solve ASAP..

Same issue with all my devices running KitKat!! This needs a fast fix!

Please

Been experiencing this issue on my Nexus 5 and Nexus 7 for all kinds of apps. The background processes are killed and never restart!

Please fix this problem

Got to wonder how Google get around this bug, must have secret APIs...

please fix!

[Comment deleted]

Wtf? If you know this bug, but to be fixed it should be voted for? Shouldn't developers fix all the bugs?

@#28
They are making a contest for bug which will annoy dev most. Share it on FB or G+ to convince people to vote for OUR bug!

Even translated into Chinese, and proposed to 'average' translated into "日均" or "平均".
竟然翻译成中文了，建议把‘average’翻译成“日均”或者“平均”。

Please fix this bug

This is just sad...  :/

Plesse fix.

Please stop spamming this issue. If you want it to be fixed, star it. Commenting "Please fix" doesn't help at all.

Changing the priority to High might also help

Requires entering the password for the awesome app TimePIN twice to unlock. Very aggravating. This is a high priority, IMO.

please fix

If comment 17 is correct, then this would appear to be a design choice instead of a bug.  Google may have reasoned that a background service which cannot be killed under memory pressure should either announce its presence with a permanent notification, or do its work every so often using as timer and take care to persist its state.  This seems reasonable to me, but 348 people starred this bug and Google ignored it which is a bigger problem than the bug.  At least close it as NOTABUG or WONTFIX along with an official statement about the correct way to program around this.  A 348-star bug that is not even triaged after two months is a little strange even for Google.

Same problem

Would like to see the notification gone in the pulldown for my timepin app.  Developer stated that it's required for right now so double pin entry is fixed.  It's a sort of trade off until Google fixes this I guess.

[Comment deleted]

[Comment deleted]

Please fix this bug soon

Please fix this.

Alta prioridad, hay que arreglar esto.

Please fix this.

Please fix this !!!

same prpblem - Please fix this

Same problem

Same problem as above, a fix would be appreciated.

[Comment deleted]

I have starred the issue.

I wonder how do other services, for example Facebook Messenger's MqttPushService, stay alive? My service uses START_STICKY with a background service (no notification) and I can confirm that due to this bug it is killed after some time and never restarted. My service shows as running in Running apps but with 0.00B memory usage.

EDIT: Nevermind, even facebook's services get killed and don't restart (right away if you swipe away from recent apps list). It shows 0 processes and 3 services, but it still shows 35MB memory usage. This renders useless all background services that are supposed to run continuously and are not foreground services.

Reply to #53
Facebook messenger doesn't stay alive. I stop getting notifications if I kill all from the change app screen...

GMail is the only app that just keeps working no matter what happens.

I might be mistaken but doesn't Facebook Messenger rely on GCM when not in
the foreground in order to wake up on push notifications?

In reply to #55, Nicholas:

So facebook services are killed (0 processes) when swiping away from recent apps list and is never restored. However, if you just use the app normally, and then don't use it for a long time, it still stays alive. My service is quickly killed by the system even without swiping it away from the recent apps list. This was always the case, but it would restart quickly in android previous to KitKat. My question is how does facebook's service manage to not get killed by the system?

Dangit, I starred this issue, but I don't want to be notified? How do I
stop it? Does anyone know?

I implemented this workaround: http://stackoverflow.com/questions/20636330/start-sticky-does-not-work-on-android-kitkat-edit-and-jelly-bean although it works und keeps the service alive (or at least restarts it), it's a really ugly workaround and i hope for a better solution...

[Comment deleted]

In reply to #58, Kappalo:

Mute this conversation in your mail client or change your setting for notification starred conversation.

It is design-intended function bacause of the user experience on Kitkat, perhaps...
https://code.google.com/p/android/issues/detail?id=56139

I hope Google may give us some words about it.