On the whole, that's not a good idea. Popping up an Activity in the
middle of whatever the user is doing will not be popular. There are
certain circumstances where this is appropriate -- incoming VOIP calls,
etc. -- but should not be done in general. Users will attack you with
sharp pointy
AuxOne wrote:
On the whole, that's not a good idea. Popping up an Activity in the
middle of whatever the user is doing will not be popular. There are
certain circumstances where this is appropriate -- incoming VOIP calls,
etc. -- but should not be done in general. Users will attack you with
Sorry if I seem confused...
Call getContentResolver() in your Service.
I'm also doing things like .sendBroadcast() to refresh the photo
gallery, .openFileInput() from the Activity. So doesn't that mean
GetContentResolver() won't work for me?
Your example code has the Alarm scheduled from
AuxOne wrote:
Like, what If the phone
boots up and that starts the Alarm, but then the app is closed and
manually restarted. Won't the previous alarm still be in memory?
No, outstanding alarms are flushed on a reboot.
--
Mark Murphy (a Commons Guy)
http://commonsware.com |
Is there any advantages / disadvantages to having the Service start
the AlarmManager, as opposed to the AlarmManager starting the Service?
I though Services were more robust.
On Mar 19, 10:50 am, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
Like, what If the phone
boots up and
5 matches
Mail list logo
