| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 7232014, 7231331, 7231198
Change-Id: Iea055cfa58edb253b55fe30bf294994ad338cfa4
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: Id52d7e4f735a2a289533fc9d8461f70218601764
|
|
|
|
| |
Change-Id: Ibc3889e2ab0569f851ec46fe4d1cb1b4920ea5be
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| | |
Change-Id: Id9c258165d9bb326271218a562d782fa52608213
|
| |
| |
| |
| | |
Change-Id: Ibaaf3418ec2c97a99495eca7ea546af415370c3e
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|
|
|
| |
change or other transitions.
|
| |
|
| |
|
| |
|
|
|