Greenify Coalescing Timer and AquaMail

[BigLisy]

Hello,

I'm just wondering, does your app support or conflict with the Greenify option "Coalescing timer"?

And second question, what's the difference between the two Command batch sizes? Responsiveness and performance, both suggest performance to me lol. I mean, both sound to have the same result in the end - just judging by the name that is. Which would be optimal for least battery usage?

[Kostya Vasilyev]

>>> Greenify option "Coalescing timer"

Sorry, I've never heard about this option -- but then I don't use Greenify (or any other app like that)...

Maybe you could explain what the option does, and what makes you ask about it? Did you run into something?

>>> Command batch sizes

I think you'll only see any difference on very slow, high latency networks, like EDGE (not even 3G)...

[BigLisy]

Thank you.

The easiest way to describe it is this:

Let's say you have 5 apps that all have a wakeup timer, and they all wake up at different times fairly consistently.

Coalescing the wakeup timers tries to prevent all the individual wakeups for each app, and tries to make them all happen at the same time instead, so that you don't wind up with your device waking up 5 different times for 5 different apps, and instead 1 time for all of them.

With my Nexus 5 that completely depletes the battery in 4h screen time, I really need to min-max to get through the day. Coalescing timer does save me lots of awake time so that's good, but it seems it causes AquaMail to drop the imap idle connection fairly more often.

Probably it's just my really, really bad 3g unstable connection.

[Kostya Vasilyev]

Android does coalescing since 4.4, and my app takes advantage of the new feature -- except on Samsung's devices, where it's deliberately broken by Samsung's firmware developers (bug filed in May, nobody gave a flying care).

I've been developing on Android since 2010 or so, and having trouble imagining how a third party app (not system code) would be able to affect other apps' alarms...

Idle connections do need to be refresh to be kept alive -- the default is every 10 minutes -- and it's not something specific to Aqua, rather, most network providers (home and mobile) are too happy to drop network connections if they see no traffic (which IDLE connections don't, until there is a new message or some other change).

[BigLisy]

Thanks for the clarification.

As for how a third party app can do such a thing, I'd imagine it's tied to the fact Greenify handles the awakening of the apps you select, so it's able to make them awaken at the same time - or so I believe.

Just curious as I'm using the same option on my samsung tablet, what does it cause? I haven't seen anything in particular.

[Kostya Vasilyev]

>> Greenify handles the awakening of the apps you select

Alarms (as Android calls them) and their scheduling is implemented in system code.

When an app sets an alarm, it deals with system code.

It's system code that wakes up the device and the app to deliver an alarm.

I don't see a way for a third party app to get involved in this. Sounds like snake oil to me But I don't use those apps, so feel free to ignore me

>> Just curious as I'm using the same option on my samsung tablet, what does it cause? I haven't seen anything in particular.

If it works (and maybe the definition of "works" here is -- doesn't break anything) -- well, I suppose that's a good thing.