1. Removed the global toggle switch - now each accessibility
feature has to be turned on or off separately.
2. Added a setting for the screen rotation (same as Dispaly)
since most of blind users want that behavior.
bug:5166161
bug:5127475
Change-Id: I659aef62a8499461075f43520a3008fa7b8ff911
1. Reimplemented accessibility settings accrding to UX design.
NOTE: The strings are not final, rather reasonable placeholders
to avoid blocking on them. Will submit another CL with string
updates and any necessary polishes.
bug:5065409
Change-Id: I3ba229a624298dbf238bc8562b42616b386f8c34
Also re-arrange the UI a bit to clearly put the button for
enabling/disabiling accessibility services along-side said
services.
Change-Id: Ica1ddecddf6e97800909ba6bea9ce4e124b59c01
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.
This is part 3 of the fix for bug 2364220 "Accessibility improvements for
ending calls".
This change adds a checkbox under "Accessibility settings" to control the
new Settings.Secure.INCALL_POWER_BUTTON_BEHAVIOR value, which allows the
user to specify that the Power button should hang up while in-call
(instead of just turning off the screen.) The checkbox is only shown on
devices that actually have a POWER button.
Yeah, it's a little strange having this under Accessibility (since it's not
that obvious *why* this feature is accessibility-related), but there's no
obvious better place. See discussion in the bug for more info.
Bug: 2364220
Change-Id: I0fd7cf357972519b390575b9c06a4bbe46ff1c9b
