| 71c8fb92a151f2f64ffbaf551c072179bc46c0da |
|
07-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
am 2b27ef97: am c969450a: am 840c8474: Merge "Add config_supportAutoRotation." into klp-modular-dev
* commit '2b27ef979dba3808cdae6dce32fe27b59197e34c':
Add config_supportAutoRotation.
|
| bcdfc62ae3ac3809e883fc0b4c71ab52a0cdacf8 |
|
07-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
Add config_supportAutoRotation.
On some products, it may not make sense to use the accelerometer
to perform auto-rotation. In that case, the product's config.xml
framework resource overlay should set config_supportAutoRotation
to false.
Setting this to false also disables auto-rotation settings.
Bug: 13211999
Change-Id: If9d7d72f2a2c576b14a4ff0afb61ea52c42c3357
/frameworks/base/core/java/com/android/internal/view/RotationPolicy.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/core/java/com/android/internal/view/RotationPolicy.java
|
| 6090995951c6e2e4dcf38102f01793f8a94166e1 |
|
19-Nov-2013 |
John Spurlock <jspurlock@google.com> |
Remove unused imports from frameworks/base.
Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
/frameworks/base/core/java/com/android/internal/view/RotationPolicy.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/core/java/com/android/internal/view/RotationPolicy.java
|
| 5e08af03a3dffff8b8fc098790e5133589601d8f |
|
22-Sep-2012 |
Christopher Tate <ctate@google.com> |
Respect per-user rotation lock et alia
Various per-user settings such as rotation lock are relevant to the
singleton PhoneWindowManager object. We now listen for user-switch
broadcasts and reconfigure the active state based on the newly-
active user's settings.
The RotationPolicy toolset has also been updated to do the right
thing, as has the Quick Settings UI.
Bug 7213638
Change-Id: Iee2109e48df550b4c979d3f9c91b5d2b71a6a08e
/frameworks/base/core/java/com/android/internal/view/RotationPolicy.java
|
| 98365d7663cbd82979a5700faf0050220b01084d |
|
20-Aug-2012 |
Jeff Brown <jeffbrown@google.com> |
Refactor for multi-display support.
Split WindowManagerImpl into two parts, the WindowManager
interface implementation remains where it is but the global
communications with the window manager are now handled by
the WindowManagerGlobal class. This change greatly simplifies
the challenge of having separate WindowManager instances
for each Context.
Removed WindowManagerImpl.getDefault(). This represents the
bulk of this change. Most of the usages of this method were
either to perform global functions (now handled by WindowManagerGlobal)
or to obtain the default display (now handled by DisplayManager).
Explicitly associate each new window with a display and make
the Display object available to the View hierarchy.
Add stubs for some new display manager API features.
Start to split apart the concepts of display id and layer stack.
since they operate at different layers of abstraction.
While it's true that each logical display uniquely corresponds to a
surface flinger layer stack, it is not necessarily the case that
they must use the same ids. Added Display.getLayerStack()
and started using it in places where it was relatively easy to do.
Change-Id: I29ed909114dec86807c4d3a5059c3fa0358bea61
/frameworks/base/core/java/com/android/internal/view/RotationPolicy.java
|
| 207673cdbb536b9bdd9ff7f9ce953c5485d11f5a |
|
06-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Implement new rotation policy.
Rotation lock does not override NOSENSOR mode anymore.
Centralize the rotation policy settings into a new class shared by
the System UI and Settings applications.
Add a new setting to specify whether rotation-lock is being hidden
because the "auto-rotate screen" option has been toggled in the
Accessibility settings panel.
Bug: 6523269
Change-Id: I15173280d25bc5d101e89a9c65913aefc53fc33a
/frameworks/base/core/java/com/android/internal/view/RotationPolicy.java
|