History log of /frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/RotationLockController.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
8852905b0b3837e326127c6dfef6f699124ce715 04-Nov-2016 Jason Monk <jmonk@google.com> Unit testing for fragments.

Set up a base class for testing fragments that will generate the host
and run the fragment through some lifecycle checks to make sure it
does ok with standard lifecycle.

Fragment tests will also automatically check for any sort of leaks
related to bindings, receivers, or other callbacks in sysui. This
requires changing the statusbar.policy classes with callbacks to
have a common interface.

Lastly also fixes a few lifecycle bugs in QS found from the above
tests.

Bug: 32609190
Test: runtest systemui
Change-Id: I52007c696c2fd41914bba4ba9d8055f2b564a7d8
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/RotationLockController.java
ccb6b9a90f228cc4e31a9442ed28756ff474c080 17-May-2014 John Spurlock <jspurlock@google.com> QuickSettings: only listen when expanded.

Register for active state updates only when the quick settings
panel is open.

Don't allow a dual-target tile and single-target tile on the same row.

Bug:14133785
Change-Id: I8a5ad3df9b67b5bc3518210d62b705483a422d8e
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/RotationLockController.java
af8d6c44f06d2f8baac2c5774a9efdae3fc36797 07-May-2014 John Spurlock <jspurlock@google.com> New quick settings implementation.

Bug:14133785
Change-Id: I7f57f8e7ebcc3e1a06fa5204f477470f14299e1f
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/RotationLockController.java
8ab172e8d9c2e926921bb52838c2322142fb3c65 19-Dec-2013 John Spurlock <jspurlock@google.com> Add rotation-lock to Quick Settings on phones.

Make the rotation-lock QS tile available for display on phones.

Devices < sw600dp are only allowed to lock rotation to their
natural orientation (i.e. portrait on most phones), so tweak
the QS tile label to make this clear. e.g. "Locked to Portrait"
instead of "Rotation Locked" on portrait phones.

Simplify RotationLockController now that the sw600 check is no
longer hardcoded in RotationPolicy.

Remove redundant sw600dp check in SystemUI, everything driven
from the RotationPolicy helper, though SystemUI can still
choose not to display the tile at all with a resource config.

Clean up some of the docs in RotationPolicy to make clear the
subtle distinction between the two ways of locking rotation:
- From Accessibility (locks to natural orientation on all devices)
- From System UI (locks to natural < sw600dp, else current rotation)

Bug:11062710

Change-Id: I5caa4485c9501315da9fed964d6667d3012b43cb
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/RotationLockController.java
79578b29bf4ba1d210586b9d7bb832eddf0960b7 30-Apr-2013 Svetoslav <svetoslavganov@google.com> Remove Auto-rotate screen setting if a required feature is missing.

It is possible that a device running Android does not support rotation,
for example a Google TV box. The change adds a check to the rotation
policy to take this into account.

The SystemUI was not respecting the fact that the user has turned off
screen rotation, i.e. locked the rotation, from the accessibility
settings. In this case we should not show the affordance to toggle
screen rotation in the quick settings to minimize the risk of a blind
user accidentally turning screen rotation on. For a blind person
screen rotation adds 2X complexity since he/she should learn two
different layouts for the app.

bug:8051556

Change-Id: If1b3c092476932f91b0345fb9bfbbf6ed33d0df9
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/RotationLockController.java