- Move dismiss suggestion logic into feature provider
- In DashboardData, use hashcode as suggestion's stable id. This is much
more likely to provide a truely stable id for each suggestion card.
Eventually I want to use hash for all tiles to provide stable id.
- Add a SuggestionDismissionController to handle swipe to dismiss
callbacks
Change-Id: If3770f07a90c5469a0b86fc28f3eb5e4c17227cd
Fix: 35159816
Test: make RunSettingsRoboTests
This crash occurs because the background loader is loading
the storage for an app which is currently being moved off of
the device. In the native code which is calculating the storage,
it throws an InstallerException which is caught and rethrown as an
IllegalStateException.
We handle this in the view by reporting that we could not calculate
the size of the app.
Change-Id: I109b1be60ae60f8ef31b08cb4392b576261fa806
Fixes: 35922033
Test: Robotest
App info used to use the old ApplicationsState path. This
removes the size query and replaces it with an AsyncTask to
load the sizes.
Fixes: 35805032
Test: Robotest
Change-Id: Ica1c88da2b407c3cbd4d7f970c7c44e4064393b3
Bug: 30681771
Test: SettingsUnitTests
Refactor visibility logging from InstrumentedFragment into a mixin. And
apply mixin in remaining fragments.
Change-Id: Ibbb59904336254a3e4bb9e8c7d0b36e5a6bc2622
An app with a storage manager would be able to launch Manage Storage
from application settings, but when the app was disabled, the
activity would be null.
Test: In order to properly unit test this function, a large redesign is
needed in this class, and is outside the scope of this bug.
Change-Id: Ia6b78bc6761bac8b701c904a6e438bbd951b63e8
Fixes: 30457616
When the home screen selected by the user isn't encryption aware, we
still need to put something on the ActivityStack. For now, let's use
an empty activity that knows how to dismiss itself when the
credential-encrypted storage is unlocked; that's enough for the
system to re-resolve the home intent and find the real home screen.
Also follow method refactoring.
Bug: 22358539
Change-Id: Iebc4ad8d2dd62ada079cab03d5765f7631fd4beb
Use frozen state as a proxy for knowing if a package is currently
being moved, and block any new move requests until the current move
is finished.
Bug: 22069486
Change-Id: I50a70353132c1035b969982f0b7779f5dcb2251d
Don't create dialog if we don't have one to create, and make sure
that storage-related prefs are removed when they aren't needed.
Bug: 22571238
Change-Id: I452cbf75313cd14572fc7b57bd6164292cf17209
Also take InterestingConfigChanges along for the ride
and delete unused AppPermissionSettings
b/21328967
Change-Id: I4d0c1a27054845a54cf68e95a92024d2e46f636e
- Fix button theme
- Hide move dropdown when can't move
- Cleanup by switching to using a horizontal preference layout, rather
than custom layouts
Bug: 21060534
Change-Id: I2cc3ab4063ff6b4dfe873f9152b34130d702faae
We now kick off the move immediately, and pass along the "ID" of the
move in progress. This allows the progress activity to be completely
destroyed and recreated without kicking off a second conflicting move
operation.
Also uses new cleaner movement API that accepts direct VolumeInfo.
Bug: 19993667
Change-Id: I28bc268fcb42dfc9152020b16ef7058d63157597
We now allow moving packages between all possible candidate volumes,
as determined by the framework. Moving now jumps through wizard to
help user understand what's going on.
Bug: 19993667
Change-Id: I5416ed2865f400b1d718c68a3f0e033080fefa0e
Things are mostly in the right places, may need some minor location
adjustment on everything and styling for the buttons.
Bug: 19511439
Change-Id: If7730285d6ddc36e32cc8bc119885a8e215c0eb5
The root screen now only has the uninstall/force stop/disable buttons
and the rest has moved to sub screens listed in a preference list.
The root screen as UI approximate to the new mocks, but the separated
screens (storage, launch by default, etc.) have yet to receive their
visual overhaul.
Bug: 19511439
Change-Id: I4e01fbaefc69e0652edea2429d9e9b028c78e825
