Age | Commit message (Collapse) | Author |
|
For some reason or another, Google made it so when you enable the
developer QS tiles they move into the active spot. This makes for
a bad experience becuase it throws all your QS tiles out of order.
This partially reverts commit fb71550128aff2505ba4a06088b0297782a214d8.
Change-Id: I11f559dc2332007811bb84562a0f63c569837222
|
|
Having consistent import order will reduce chance of merge
conflict between internal and external master
Test: rebuild
Change-Id: I0b1a170967ddcce7f388603fd521f6ed1eeba30b
|
|
* Notification access page
* VR Listener page
* Feature flags in dev options
* QS Tile developer options
* User dictionary
* Billing cycle
* Some accessibilty pages
Bug: 70720645
Test: robotests
Change-Id: I4f7d3d65b2803cebf178ac345a79721232df707c
|
|
Test: rebuild
Change-Id: I178485c84ae7146f991fd77b6d7504b029942a68
|
|
Test: make Settings
Bug: 76692459
Change-Id: I941dea40562170649bf056e675cc32e5163c0e39
|
|
Bug: 73496681
Test: make RunSettingsRoboTests ROBOTEST_FILTER=DevelopmentTilePreferenceControllerTest
Test: flash device and manually test by enabling dev options
Change-Id: Ib7f53128c79de9550d4f68274312e731c01ebd4f
|
|
- The tile activity is internal to Settings and nobody should launch it
externally, thus it doesn't need to have its own activity. Preference
framework can launch the fragment as a SubSetting
Fixes: 67603649
Test: robotests
Change-Id: I9ba2fc55eb7f571f816ec045567f2dd2714c44e8
|