Bug: 30681771
Test: SettingsUnitTests
Refactor visibility logging from InstrumentedFragment into a mixin. And
apply mixin in remaining fragments.
Change-Id: Ibbb59904336254a3e4bb9e8c7d0b36e5a6bc2622
Battery, Development moved to main menu.
Unknown sources moved to Security.
Main menu links directly to ManageApplications.
ApplicationSettings was kept in case an other app referenced it.
Change-Id: I0271d4222cfc192f9235f21e06bf3b56f77db1a4
Since external keyboards can be connected, we should always show the
quick launch settings. Unfortunately they still need to be fragmentized.
Change-Id: I1342ef3892a8b1b465ecc5c1346049f8b1ff73cd
Added a base class SettingsPreferenceFragment from which the settings activities should
be derived so that they can behave like fragments. It contains some commonly called
utility methods and dialog conversion to DialogFragment.
Some of the top-level activities can be launched directly without the left pane.
Settings.java acts as a proxy activity that contains just that settings fragment without
the left pane.
There are still a lot of second and third level activities that need to be fragmentized.
This is just the first pass to test the 2-pane layout.
Disable move when manifest option for install location is unspecified
and install location is auto/internal
Change-Id: Ic7a493ecbbed6017326e2ec728e25c6ea9de8223
Settings for Manage Applications that allow the user to choose default application installaction location.
Options are: internal flash, SD card, or automatic.
