I just tried installing an update with "adb install -r" and it kept the set of disabled applications. You will need to provide more details about what you are doing.
Also, I have no idea what a "BOTA upgrade" is, so I don't know if I am even understanding your question. On Tue, Jun 26, 2012 at 11:14 AM, Sudeep Sharma <[email protected]>wrote: > No it should not be the case because when you buy a new android phone > Google Google Setup Wizard package runs which has a Home category > activity(com.google.android.setupwizard/.SetupWizardActivity having > higher priority than home screen) which activates the phone, ask for > setting up google account and then disables the Home category > activity(com.google.android.setupwizard/.SetupWizardActivity) and > actual Home screen comes. For this case manifest doesnt have any > explicit state enabled/disabled. The default value android:enabled is > true if not stated. Disabling of SetupWizardActivity in this case > happens at run time only. > > Now if you upgrade the phone to a higher android version and phone > reboots, SetupWizardActivity should start again but that is not the > case and Home intent is recieved by HomeScreen. It means in upgrade > the activity which is disabled will remain disabled. > > So i am wondering if I am disabling correctly or not ? But as per API > I am disabling it correctly because until upgrade happens my activity > is disabled. > > pm.setComponentEnabledSetting(name, > PackageManager.COMPONENT_ENABLED_STATE_DISABLED, > PackageManager.DONT_KILL_APP); > > I think somebody from google android framework team should comment. > > Thanks , > Sudeep > > On 6/26/12, jc <[email protected]> wrote: > > On Tuesday, June 26, 2012 10:40:28 AM UTC-5, MagouyaWare wrote: > >> > >> > >>> There is no state mentioned in manifest for the upgraded component, it > >>> should be in Disabled state until user enables it or Factory reset of > >>> phone is done. > >>> > >> Why? I didn't read it that way. I agree that it is not well-defined, > but > >> > >> the docs do not say that this should be the case. > >> > > > > I would suspect that upgrading doesn't retain your runtime setting > because > > it resets back to the manifest value, or in your case the DEFAULT value > > since you don't have it defined in your manifest. > > > > > http://developer.android.com/guide/topics/manifest/application-element.html > > > > http://developer.android.com/guide/topics/manifest/activity-element.html > > > > > > > > > > -- > > 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 > > -- > 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 > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
