Fixed
Status Update
No update yet.
Comments
am...@gmail.com
It seems like it's also not restarted when being killed due to a low memory condition. This is a serious issue!
vi...@gmail.com
Same as 63618 issue reported before.
ch...@google.com
Ruins battery notifications
ch...@google.com
Had to stop using this. Too bad, loved it.
am...@gmail.com
Why is this rated a "Priority-Small" ? This makes all applications that use a background service useless
ch...@gmail.com
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.
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.
ch...@google.com
[Comment deleted]
ch...@gmail.com
Yes, the service stops in any moment. I think it's a big problem. In lower versions no problem with the background service.
ch...@gmail.com
Same issues here. This is indeed a serious problem.
ko...@gmail.com
I'm having similar issues. Real problems also with the notificationlistener service just stopping sending notifications to apps without a reboot.
ji...@gmail.com
Must be fixed!
jh...@googlemail.com
[Comment deleted]
[Deleted User] <[Deleted User]>
[Comment deleted]
jh...@googlemail.com
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
Also, START_STICKY services attached to activities that are cleared out of the Recent Apps list are also being killed and never restarted (see
or...@gmail.com
I have same problem with app widgets, my app widget has a back-end service which on 4.4.2 stops and never restarts.
de...@googlemail.com
Confirmed fir the Nexus 4 as well.
Op 29 dec. 2013 08:07 schreef <android@googlecode.com>:
Op 29 dec. 2013 08:07 schreef <android@googlecode.com>:
dn...@google.com
Making the service a foreground service with startForeground() along with START_STICKY appears to circumvent this bug. This might not be the most appropriate path for all apps though, as it (appropriately) requires a notification icon to be displayed in exchange for the higher system resources priority.
yu...@gmail.com
Only Google apps aren't affected by this bug, really need to be prioritized!!
dn...@google.com
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..
Very high priority issue!! Please solve ASAP..
dn...@google.com
Same issue with all my devices running KitKat!! This needs a fast fix!
am...@google.com
Been experiencing this issue on my Nexus 5 and Nexus 7 for all kinds of apps. The background processes are killed and never restart!
ch...@google.com
Please fix this problem
am...@google.com
Got to wonder how Google get around this bug, must have secret APIs...
da...@gmail.com
please fix!
ja...@gmail.com
[Comment deleted]
st...@gmail.com
Wtf? If you know this bug, but to be fixed it should be voted for? Shouldn't developers fix all the bugs?
[Deleted User] <[Deleted User]>
@#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!
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!
ro...@gmail.com
fix this bug immediately.
ch...@google.com
Even translated into Chinese, and proposed to 'average' translated into "日均" or "平均".
竟然翻译成中文了，建议把‘average’翻译成“日均”或者“平均”。
竟然翻译成中文了，建议把‘average’翻译成“日均”或者“平均”。
vi...@gmail.com
Please fix this bug
ma...@gmail.com
This is just sad... :/
me...@gmail.com
Plesse fix.
rm...@gmail.com
Please stop spamming this issue. If you want it to be fixed, star it. Commenting "Please fix" doesn't help at all.
er...@gmail.com
Changing the priority to High might also help
Description
Version used: 22.2.1
Implementing ViewPager with the new Support Design Library the StatusBar disappears from 2nd page as you see in the pictures, but only in Lollipop devices with transparent status. I use android:fitsSystemWindows="true" but it does work only on first page.
No problem so far for older version: < API 21 (only because status bar is always present)
Full details on
Note: status bar padding not visible also when using app:layout_scrollFlags="scroll|enterAlwaysCollapsed|enterAlways|exitUntilCollapsed" in CollapsingToolbarLayout when you firstly scroll up and then down a bit.