| 58d37b55bd228032355360ea3303e46a804e0516 |
|
18-Sep-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Multi-user support for the accessibility layer.
1. This change converts the accessibility manager service to
maintain a state per user. When the user changes the services
for the user that is going away are disconnected, the local
accessibility managers in the processes for this user are
disabled, the state is swapped with the new user's one, and
the new user state is refreshed.
This change updates all calls into the system to use their
user specific versions when applicable. For example, regisetring
content observers, package monitors, calls into other system
services, etc.
There are some components that are shared across users such
as UI created by the system process and the SystemUI package.
Such components are managed as a global state shared across
all users and are updated accordingly on a user switch. Since
the SystemUI is running in a normal app process this change
adds hidden APIs on the local window manager to allow the
SystemUI to notify the accessibility layer that it will run
accross users.
Calls to AccessibiltyManager's isEnabled(), isTouchExplorationEnabled()
and sendAccessibilityEvent return false or a are a nop for a
background user sice he should not send accessibility events,
and should not perform touch exploration.
Update the internal accessibility tests due to changes in the
AccessibilityManager.
This change also fixes several issues that were encountered
such as calling out the accessibility manager service with a
lock held.
Removed some incorrect debugging code from the TouchExplorer
that was leading to a system crash.
bug:6967373
Change-Id: I2cf32ffdee1d827a8197ae4ce717dc0ff798b259
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|
| 00aabf7d187bc05408199bd687a538b2e68bdc17 |
|
21-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Touch exploration state set to clients asynchronously and depended on talking service being enabled.
1. Upon registration of an accessibility client the latter received only
the accessiiblity state and waiting for the touch exploration state
to be sent by the system in async manner. This led the very first
check of touch exploration state is checked a wrong value to be reported.
Now a state of the accessibility layer is returned to the client
upon registration.
2. Removing the dependency on talking accessibility service to be enabled
for getting into touch exploration mode. What if the user wants to use
an accessibility service that shows a dialog with the text of the touched
view?
bug:5051546
Change-Id: Ib377babb3f560929ee73bd3d8b0d277341ba23f7
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|
| 35bfedeaba724aeadc6f6c890269cb6bf7ef42f5 |
|
15-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Touch exploration separate setting and API to poll the latter state.
1. Seperated touch exploration to be a seperate setting rather being
magically enabled by the system of accessiiblity is on the there
is at leas one accessibility service that speaks enabled. Now
there is a setting for requesting touch exploration but still the
system will enabled it only if that makes sense i.e. accessibility
is on and one accessibility service that speaks is enabled.
2. Added public API for checking of touch exploration is enabled.
3. Added description attribute in accessibility service declaration
which will be shown to the user before enabling the service.
4. Added API for quick cloning of AccessibilityNodeInfo.
5. Added clone functionality to SparseArray, SparseIntArray, and
SparseBooleanArray.
bug:5034010
bug:5033928
Change-Id: Ia442edbe55c20309244061cd9d24e0545c01b54f
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|
| cc4053e031371456fe54d51bbad1db721db4ae38 |
|
23-May-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility serviceconfiguration via meta-data
Note: This is a part of two CL change and contains the
system changes without updates to the settings.
1. Added a mechanism for configuring an accessibility service via
XML file specified in a meta-data tag (similar to IMEs).
2. Added property for specifying a settings activity for an
accessibility service.
3. Refactored the APIs in AccessibilityManager to return
lists of AccessiblityServiceInfo instead ServiceInfo
since the former describes an AccessibilityService in
particular (similar to IMEs).
Change-Id: Ie8781bb7e0cdb329e583b6702a612a507367ad7b
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|
| 383742c16d3dcbfcf748a89f0cb88ac8d2b31bb5 |
|
09-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
3205857 java.lang.ExceptionInInitializerError at java.lang.Class.newInstanceImpl(Native Method)
Change-Id: I72ab33da2f5cc0bbaa89f3b996ff4ac48deadf73
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|
| 5637745e59e1c0c22ec2e0adb1f48f8f4edcb7be |
|
07-Jun-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
2744878 com.android.server.AccessibilityManagerServiceTest:testInterrupt is failing
Change-Id: I73d056c7dcf8edddae2ef9cb28ec7d2b3203bb9b
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|
| 0b29a587142b19ed25dd6489cfa037d06145afd1 |
|
17-Apr-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
2604226 Add test cases for the internal accessibility infrastructure.
Change-Id: Iaeb2c11b6c2167632086b50d9c79e6459cc072b8
/frameworks/base/services/tests/servicestests/src/com/android/server/AccessibilityManagerServiceTest.java
|