It's close to being how it works by default in 6.0 without Play Services. Apps need to ask for battery optimization exceptions.
-
-
Replying to @CopperheadOS @RichFelker
These APIs can bypass it but have very coarse granularity with coalescing: https://developer.android.com/reference/android/app/AlarmManager.html#setAndAllowWhileIdle%28int,%20long,%20android.app.PendingIntent%29 … https://developer.android.com/reference/android/app/AlarmManager.html#setExactAndAllowWhileIdle%28int,%20long,%20android.app.PendingIntent%29 ….
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Could have been a nice feature if it wasn't ruined by using it as a bludgeon to make everything adopt Google Cloud Messaging...
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
Well I want a bludgeon to get rid of all notifications. If I want to see what's new on Twitter I'll run the Twitter app, thx.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @CopperheadOS
Unfortunately even with notifs turned off in-app, they still constantly run in the bg, unless/until you forcibly kill them.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
On 6.0, the only way they can continue to do that is migrating to sending endless GCM high priority messages (and we lack GCM).
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Many apps are doing exactly that, but they're @ mercy of Google's policing high priority messages. Even if some users want it.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
The whole GCM thing is really irritating. Their own service shouldn't have an exception from these rules... not playing fair.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Anyway, point is just that they actually gave you what you want in AOSP but then ruined it with GCM to push their own service.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
And hard to be happy about it in AOSP, since it just means everything is going to adopt GCM to bypass this. Not progress really.
1 reply 0 retweets 0 likes
Seems the right solution is just dummying-out the API for GCM except to whitelisted apps.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.