I don't understand what you mean about persistent alarms -- alarms are
persistent, until a reboot, at which point yes if you want to have alarms
scheduled you need to handle BOOT_COMPLETED.
Also the next version of the platform should allow an app to be told when it
is updated, though you still
All nice and well - if the API for AlarmManager supported persistent
alarms.
Currently, if you update an application your alarms will go bye bye
until the phone reboots - no?
Requiring a reboot just to reset a few silly alarms seems quite
excessive to me - and definitely prevents us from taking
On Feb 23, 8:35 pm, Dianne Hackborn hack...@android.com wrote:
No, there is deliberately no API for this. You should let yourself be
started when the user explicitly launches your app.
But Diane, I just don't understand this position. Android allows apps
to be started on BOOT_COMPLETED,
On Tue, Feb 24, 2009 at 3:38 PM, Peter Jeffe pje...@gmail.com wrote:
There are many apps that aren't just simple foreground processes, and
by limiting what developers can do in this way you're not allowing us
to take full advantage of the platform.
That seems quite an exaggeration to me.
The use of BOOT_COMPLETED allows an app to be started even if the user
never explicitely launched it, isn't it?
Sylvain
Dianne Hackborn wrote:
No, there is deliberately no API for this. You should let yourself be
started when the user explicitly launches your app.
On Mon, Feb 23, 2009
Google team, is there a way for a application to get started or auto
start itself when it is installed for the first time ?
Reading through the forum it appears that the application being
installed used to get the PACKAGE_ADDED broadcast in an earlier
release, but I cannot get it to work in the
No, there is deliberately no API for this. You should let yourself be
started when the user explicitly launches your app.
On Mon, Feb 23, 2009 at 5:17 PM, sandy8531 mathur...@gmail.com wrote:
Google team, is there a way for a application to get started or auto
start itself when it is
I agree; this is an unnecessary limitation in the api IMO. It is fair
enough to require user input to start any code *the very first time
they install*, but what about during upgrades? With the way things
work now, it's possible for an app to stop working after an upgrade
due to the user not
No, you should let the user decide to run you when they want.
On Thu, Feb 12, 2009 at 10:43 AM, Peter Jeffe pje...@gmail.com wrote:
I'd like my app to be run immediately after being installed (it has a
service that ideally would run before the user runs the app). In
On Feb 12, 1:54 pm, Dianne Hackborn hack...@android.com wrote:
No, you should let the user decide to run you when they want.
We certainly let the user decide when they want to run our activity
and interact with it, but we also have a service that we want to run
after we are installed and at
10 matches
Mail list logo
