KM == Kristopher Micinski krismicin...@gmail.com writes:
KM FYI 90 seconds would not really be a good fit for an
KM AlarmManager, it's not meant to be used with that kind of
KM granularity.
That's an interesting comment. I am using an alarm to wake myself every
60 seconds in order to
On Thu, Jan 10, 2013 at 8:54 AM, Jake Colman col...@ppllc.com wrote:
That's an interesting comment. I am using an alarm to wake myself every
60 seconds in order to check something. Are you saying this is not good
practice?
For me, 60 seconds is about the threshold where I start to wonder
MM == Mark Murphy mmur...@commonsware.com writes:
MM On Thu, Jan 10, 2013 at 8:54 AM, Jake Colman col...@ppllc.com wrote:
That's an interesting comment. I am using an alarm to wake myself
every 60 seconds in order to check something. Are you saying this
is not good practice?
On Thu, Jan 10, 2013 at 10:33 AM, Jake Colman col...@ppllc.com wrote:
How does a typical clock widget update itself to display a new time as
the minutes go by? Does it do nothing unless the user turns on the
screen (when the screen is off you don't need to know what time is) at
which time it
How does a typical clock widget update itself to display a new time as
the minutes go by? Does it do nothing unless the user turns on the
screen (when the screen is off you don't need to know what time is) at
which time it triggers an event and updates itself?
A cursory look at most of them
As far as I know Android tries to calculate an update plan among all
location requesting apps. It comes up with an update strategy according to
all these request parameters and therefore these values you specify can
just be seen as your best case scenario wishes. You cannot take them for
FYI 90 seconds would not really be a good fit for an AlarmManager,
it's not meant to be used with that kind of granularity.
Instead, if you absolutely need it you should instead request a finer
interval. At 90 seconds, your app will probably be a sort of battery
hog anyway..
Kris
On Wed, Jan
7 matches
Mail list logo
