http://developer.android.com/sdk/android-3.1.html
Under "Launch controls on stopped applications":
>>>
Applications are in a stopped state when they are first installed but
are not yet launched and when they are manually stopped by the user (in
Manage Applications).
<<<
And yes, it's a real pain to deal with.
I have a free base app and an unlocker app, and had to structure it so
that the user actually runs the unlocker app.
As a consequence, the unlocker app has to have a button to "hide its
icon" where it calls PackageManager.setApplicationEnabledSetting for its
launcher/main activity (apparently it's a real tragedy for some users to
have an icon in the apps list that says "... Pro Key").
This works on most devices, but on the Samsung S5830 -- and I suspect
most/all Samsung devices with TouchWiz -- it only takes effect after a
reboot, and users think it's my code that's broken.
I really hate it how new Android versions break stuff that used to work
before, and the painful fallout from those changes.
-- Kostya
12.01.2012 14:39, Pent ?????:
I have a few apks on Market that are purely content holders for icons.
These apks usually respond to a broadcast receiver query with details
of what icons they contain etc.
On ICS, they don't respond after install so they're essentially
invisible to the host app that wants to use the icons.
I remember reading a while ago that apps are now in some kind of
'frozen' state until the user starts them up (or similar). Can anyone
point me to the documentation for this frozen state ?
Thanks,
Pent
--
Kostya Vasilyev
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
