| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 26932948
Change-Id: Ic8bcec523fc6cd0db847a4575724fbe465e65c5d
|
|
|
|
| |
Change-Id: I7ec15992587b0036030386be35eedc095055b6eb
|
|
|
|
| |
Change-Id: Ib5d7f57c47e79359174c0a24f72b1a8d509a6f4e
|
|
|
|
|
| |
Bug: 4770335
Change-Id: Iceef40eb1bf01457d715a21a5ebef942de484195
|
|
|
|
| |
Bug: #2361749.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main activity was managing the state transitions during
installation/uninstallation which was actually not needed.
Just make the activities independent and start sub activities
without waiting for activity result codes in the main activity.
If the user enables development setting to immediately destroy activities,
and sideloads an app, the ActivityManager tries to destroy the
main activity while it starts sub activities to finish installation
and this results in UI bizarreness based on the current state of
the installer.
Also move InstallConfirmation to the main activity.
Converge InstallDone and InstallProgress into one screen. Just enable
or disable launch/close buttons. This is how it should have been in the
first place..
Same set of issues with uninstall code path as well.
|
| |
|
| |
|
|
|