<div dir="ltr">+"disable push notifications" +"battery life" +"android" > Google, for instance (I presume you use this).<br><br><div>There are also several companies clamming that their push notifications services (including geo-fencing) drain less battery, etc., etc.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 3:11 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Miguel, do you have any references? If there are hundreds posts about it, I would love to read.</div><div class="gmail_extra">
<div><div class="h5"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 11:01 AM, Miguel Lemos <span dir="ltr"><<a href="mailto:miguel21op@gmail.com" target="_blank">miguel21op@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">That's not the experience we have... There are hundreds (thousands?) of posts about this matter. There are several strategies to keep the processor alive to do its work and Android (using GCM) minimizes the overload, it's more or less a consensual idea. You'll find in the Internet several articles about this too.<br>
<br></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 2:41 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div>
<div>On 04/01/2014 09:22 AM, Miguel Lemos
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">?! I can do it worse: uninstall the app because it
drains the battery.</div>
</blockquote></div>
Push messages don't drain the battery that much. They all come in
over the GCM socket which is refresh every 15 minutes or so.<br>
<br>
Keeping an open socket doesn't drain the battery that badly. IN a
(contrived) experiment I had a socket which sent a packet every 5
minutes to the device. Over the course of 5 hours the app didn't
even register on things which had drained the battery.<div><div><br>
<br>
<blockquote type="cite">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Apr 1, 2014 at 2:14 PM, Summers
Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 03/31/2014 02:03 PM, Miiguel Lemos wrote:<br>
> Using the GCM for push notifications has a very
important advantage: it minimizes the battery consumption,
since it reduces the processor overload, it's not needed
to open a socket to check the server on a regular basis,
etc. In my opinion this a critical matter, minimizing the
probability of the user turning the notifications off.<br>
</div>
On Android you can't turn notifications off in the same way
as iOS.<br>
<div>
<div>><br>
><br>
> Enviado do meu iPad<br>
><br>
> No dia 31/03/2014, às 18:51, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>>
escreveu:<br>
><br>
>> I would vote for A<br>
>><br>
>> --<br>
>> abstractj<br>
>><br>
>> On March 31, 2014 at 10:59:01 AM, Summers
Pittman (<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>)
wrote:<br>
>>>> Y'all,<br>
>>> So there has been some concerns with the
complexity of the build<br>
>>> especially where including the Google GCM
(push) libraries<br>
>>> are<br>
>>> concerned. Additionally there have been
some requests for a<br>
>>> separate<br>
>>> "push" module which won't need the full
aerogear android library.<br>
>>><br>
>>> The full modularization of the library
along with several other<br>
>>> improvements is scheduled for the "2.0"
epic.<br>
>>><br>
>>> So my question is a) Should we make a 2.0
which is only the<br>
>>> modularization sooner and iterate on that a
few times before<br>
>>> we include<br>
>>> our improvements in a 3.0 or b) Should we
create a "fork" project<br>
>>> which<br>
>>> is only a push module? This new project
will get merged back into<br>
>>> the<br>
>>> main project when we have our complete
modularizations.<br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
</div>
</div>
<div>--<br>
Summers Pittman<br>
>>Phone:<a href="tel:404%20941%204698" value="+14049414698" target="_blank">404 941 4698</a><br>
>>Java is my crack.<br>
<br>
</div>
<div>
<div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
<br>
<pre cols="72">--
Summers Pittman
>>Phone:<a href="tel:404%20941%204698" value="+14049414698" target="_blank">404 941 4698</a>
>>Java is my crack.
</pre>
</div></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><br></div></div>
</div><span class="HOEnZb"><font color="#888888">-- <br>
"The measure of a man is what he does with power" - Plato<br>-<br>@abstractj<br>-<br>Volenti Nihil Difficile
</font></span></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>