summaryrefslogtreecommitdiffstats
path: root/services/accessibility
Commit message (Collapse)AuthorAgeFilesLines
* livedisplay: Moving LiveDisplay to CMSDKSteve Kondik2016-04-131-23/+1
| | | | | | | * Remove all LiveDisplay-related code from the framework, and update the QS tile for the new API. Change-Id: I41c04a254afa91c0ed26c050362b63049d489fba
* fw: Move Secure settings to CMSettingsd34d2015-11-122-4/+7
| | | | | | | | | | | | | | | | | | | | | | This moves all Settings.Secure.* settings that, were added to CyanogenMod, to CMSettings. * KEYBOARD_BRIGHTNESS * BUTTON_BRIGHTNESS * BUTTON_BACKLIGHT_TIMEOUT * DEV_FORCE_SHOW_NAVBAR * ADB_NOTIFY * ADB_PORT * DEVICE_HOSTNAME * KILL_APP_LONGPRESS_BACK * PROTECTED_COMPONENTS * LIVE_DISPLAY_COLOR_MATRIX * ADVANCED_REBOOT * POWER_MENU_ACTIONS * DEFAULT_THEME_COMPONENTS * THEME_PREV_BOOT_API_LEVEL Change-Id: I49e9160177ffc727b20008817ac2b5ce5e89ead5
* We should not change the time interval with two MotionEvent,guotao.deng2015-11-111-6/+1
| | | | | | or someothers can not use it correct. Change-Id: I6de2b39fe214e64479df1d411cb3e1c8af2c8894
* livedisplay: Implement active display adjustmentSteve Kondik2015-10-181-1/+23
| | | | | | | | | | | | | | | | | | | | * LiveDisplay is our new name for the various display technologies which adjust the screen based on environmental conditions other than the standard automatic backlight controls. * This patch implements automatic color temperature adjustment based on time of day. This is similar to f.lux or Redshift. My eyes are so happy now! * Automatic outdoor/SRE feature is now handled here. * Handling of CABC/CABL and color enhancements also handled here. * Manual RGB tweaking is handled here. * Can delegate to DisplayColor HAL if available, otherwise uses SurfaceFlinger's 1015 operation to apply changes. * Happily coexists with the new accessibility features for color blindness correction and color inversion. * All postprocessing will be disabled when powersave mode is activated. Change-Id: Iac1b74f410957f8e2d8290465c4ce9cc1fd97a88
* Add accessibility event for assist disclosureJorim Jaggi2015-06-301-0/+2
| | | | | Bug: 21568059 Change-Id: Ib51d4236fcc87acd54cb5d191197b9b2c6cc54ea
* Merge "Make node retrieval methods in AccessibilityManagerService use ↵Svetoslav Ganov2015-06-041-7/+30
|\ | | | | | | separate Region instances to make them thread safe." into mnc-dev
| * Make node retrieval methods in AccessibilityManagerService use separate ↵Nirmal Patel2015-06-031-7/+30
| | | | | | | | | | | | | | | | | | Region instances to make them thread safe. b/21087793 Change-Id: Ice690e3d7494788fb9e1e234a54f14831bd4e0d3 (cherry picked from commit ebd8eb4610d6bb9322a374f8965a78ba1c39ee63)
* | Fix calls to Rect.intersect(Rect)Doris Liu2015-06-021-4/+2
|/ | | | | | | | | | | This CL checks for the return value for Rect.intersect(Rect) for whether there is actually an intersection before taking the calling rect as the intersection. In the case of no intersection (Rect.intersect(Rect) returns false), the calling rect would not have been changed, so here in this CL it will be manually set empty. Bug: 7368679 Change-Id: I7494c1a1649eca09e34412f0a59b795e8b3a82aa
* Update use of procstate for services.Dianne Hackborn2015-04-291-1/+3
| | | | | | | | | | | | | | | | | | | | Now that we have a separate foreground service proc state (above a sleeping top app), update various system services to put their bindings into this state when appropriate. There are two new bind flags for this -- one that just always makes it a foreground service, another that only does it when the device is awake (useful for things like the wallpaper). And with all of that, tweak network policy manager to only include apps that are at least foreground service state when in power save and device idle modes. This will allow us to further reduce the set of apps that have network access (in particular not giving access to the current top app when the screen is off), hopefully leading to even better battery life. Change-Id: I91d85a5c5ed64e856149e9a5d94a634a7925ec7f
* Adjust display inversion matrix to account for luminanceAlan Viverette2015-04-281-5/+11
| | | | | Bug: 20346301 Change-Id: I10633705f2bfddbdeec063f9489a4f8679b9e8ee
* Added TYPE_APPLICATION_ABOVE_SUB_PANEL window type.Wale Ogunwale2015-04-141-0/+1
| | | | | | | | TYPE_APPLICATION_ABOVE_SUB_PANEL will be displayed on top of their attached window and any TYPE_APPLICATION_SUB_PANEL panels. Bug: 20135562 Change-Id: I711de3c19c01432c44de205bf09934a8b23b53fd
* Merge restored accessibility enable state, don't overwriteChristopher Tate2015-03-161-3/+45
| | | | | | | | | | | We do not want to accidentally disable the user's currently-enabled accessibility service(s); presumably they turned them on during setup for a reason. We now merge the prior + current states rather than simply replacing the current state with the former. Bug 19427367 Change-Id: I96eb47df57318c88066c5da6862f23f656639148
* Resolved conflict for merge of 4a0e0237 to masterCasey Burkhardt2015-02-181-7/+14
|\ | | | | | | Change-Id: I4a567f650103d1226c49a09f6b2c842a0f1ed6f2
| * am bdbd4736: Merge "Refinements to magnification for improved wearable ↵Casey Burkhardt2015-02-191-7/+14
| |\ | | | | | | | | | | | | | | | | | | support." into lmp-mr1-modular-dev * commit 'bdbd4736351231aac4da720ff7326ea2791e0b00': Refinements to magnification for improved wearable support.
| | * Refinements to magnification for improved wearable support.Casey Burkhardt2015-02-181-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change refactors ScreenMagnifier to use resources for its triple-tap adjustment and scale threshold values. New values more appropriate for wearable form factors are supplied. This also fixes a bug in the triple- tap detection logic where the incorrect ViewConfiguration value for the tap threshold was used, prematurely disqualifying some touch events as potential taps. Change-Id: If47e556aadb5beb1bad24644122560c6fbe33bad
* | | Fix broken activation of the selected view in accessibility mode. automerge: ↵Svetoslav2015-02-032-81/+42
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | ded133c automerge: b6b526e automerge: f8acd7a * commit 'f8acd7a961f3a36712519d0f925f86f3da8d0b7c': Fix broken activation of the selected view in accessibility mode.
| * | Fix broken activation of the selected view in accessibility mode. automerge: ↵Svetoslav2015-02-032-81/+42
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | | | | ded133c automerge: b6b526e * commit 'b6b526eaafdcc39e9d55a82f61f1e03c4a3487c3': Fix broken activation of the selected view in accessibility mode.
| | * Fix broken activation of the selected view in accessibility mode.Svetoslav2015-02-022-81/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were using an approximation to determine where to send a pair of down and up events to click on the view that has accessibility focus. We were doing reverse computation to figuring out which portion of the view is not covered by interactive views and get a point in this region. However, determining whether a view is interactive is not feasible in general since for example may override onTouchEvent. This results in views not being activated or which is worse wrong views being activated. This change swithes to a new approach to activate views in accessibility mode which is guaranteed to always work except the very rare case of a view that overrides dispatchTouchEvent (which developers shouldn't be doing). The new approach is to flag the down and up events pair sent by the touch explorer as targeting the accessibility focused view. Such events are dispatched such that views predecessors of the accessibility focus do not handle them guaranteeing that these events reach the accessibiliy focused view. Once the accessibiliy focused view gets such an event it clears the flag and the event is dispatched following the normal event dispatch semantics. The new approach is semantically equivalent to requesting the view to perform a click accessiblitiy action but is more generic as it is not affected by views not implementing click action support correctly. bug:18986806 bug:18889611 Change-Id: Id4b7b886c9fd34f7eb11e606636d8e3bab122869
* | | Accessibility: Sometimes cannot interact with nav bar items. automerge: ↵Svetoslav2015-01-231-6/+3
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | 10a053e automerge: db1983b automerge: cd2ed4e * commit 'cd2ed4e64c501a5dbf73941a4a1f1e4bc639ebf3': Accessibility: Sometimes cannot interact with nav bar items.
| * | Accessibility: Sometimes cannot interact with nav bar items. automerge: 10a053eSvetoslav2015-01-231-6/+3
| |\ \ | | |/ | | | | | | | | | | | | | | | automerge: db1983b * commit 'db1983b3f43e86acbf188961f53af794cce05219': Accessibility: Sometimes cannot interact with nav bar items.
| | * Accessibility: Sometimes cannot interact with nav bar items.Svetoslav2015-01-231-6/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If there is a window with the accessibility focus we want to click on the accessibility focused view in this window. The logic to compute the bounds of the window was using the wrong window id, hence getting an incorrect result. As a consequence in some cases the user could not click on accessiiblity focused controls in the nav bar. bug:18889611 Change-Id: I89aee3ae2ffe27fe29819049c287a7155154c65b
* | | Make talkback or other accessibility services updateable from playstoreJinsong Mu2015-01-071-1/+3
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | only when it's been enabled. The idea is to set accessibility services package status to disabled_until_used by default. Change the status to enabled once user turn the service on. It is first part of CL in framework, that returns installed accessibilityServices even they been set disabled_until_used Second part of CL will be in Settings, where we read/write package status based on the service has been turn on or off. The similiar logic has been used for preventing never used IME from auto updated b/18205549 Change-Id: I1a9cba0221e3de0499ba5ac91ca382696bcb7043
* | am 26c88954: am 14e3351a: Merge "Fix a NPE in AccessiiblityManagerService." ↵Svet Ganov2014-12-121-0/+3
|\ \ | |/ | | | | | | | | | | into lmp-mr1-dev * commit '26c8895465bbc94efb0cc96460e5eabe88382698': Fix a NPE in AccessiiblityManagerService.
| * Merge "Fix a NPE in AccessiiblityManagerService." into lmp-mr1-devSvet Ganov2014-12-121-0/+3
| |\
| | * Fix a NPE in AccessiiblityManagerService.Svet Ganov2014-12-111-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is possible that the accessibility windows list is null which is treated as if there is no window information. The getWindows method was accessing properties of the windows filed witgout a null check. bug:18522998 Change-Id: Ieefe678d3da3d6e8f96c0e4bedac0c55975621fa
* | | am e39fc96c: Merge "Ignore accessibility overlay when computing window\'s ↵Svet Ganov2014-12-101-2/+3
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | interactive region." into lmp-mr1-dev automerge: a706c90 * commit 'a706c9079a60531d79a3f32f263c37f386229564': Ignore accessibility overlay when computing window's interactive region.
| * | Ignore accessibility overlay when computing window's interactive region.Svet Ganov2014-12-091-2/+3
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | If an accessibility service opts-in for the new window introspection APIs when calling into a window for accessibility node infos we compute the window's interactive region, i.e. the portion that is touchable and not covered by other touchable windows, in roder to deterine whether these nodes are visible, i.e. the user can interact with them. There was a bug in the interactive region computation what we were not ignoring accessibility overlay windows which are intended to not change what an accessibility service can "see" and are put by such a service. bug:18652374 Change-Id: I24ce54069087af9bc308e0c6a7b2aa6b952a6136
* | am ed068f7c: am 3a0d878a: Ensure all events from a showing window are ↵Svetoslav2014-12-081-27/+0
|\ \ | |/ | | | | | | | | | | dispatched. * commit 'ed068f7c3047b3775647a6023c6960a4fc535144': Ensure all events from a showing window are dispatched.
| * Ensure all events from a showing window are dispatched.Svetoslav2014-12-051-27/+0
| | | | | | | | | | | | | | | | | | | | | | | | Accessibility services may opt-in to introspect the interactive windows on the screen. If window introspection is enabled there is a case where some events from a showing window are received before the updated window state from the window manager. Now the window manager sends over the windows before notifying the app for the focus change. bug:18625996 Change-Id: Ic481e01efbe12dc92f090f799feeb236672fc7b3
* | am bd6fabe2: Merge "APIs for an accessibility service to put interaction ↵Svetoslav2014-10-241-4/+31
|\ \ | |/ | | | | | | | | | | | | | | tracking overlays." into lmp-mr1-dev automerge: 89e7ffe * commit '89e7ffedadd20a3091e72b42f86c500452df193c': APIs for an accessibility service to put interaction tracking overlays.
| * APIs for an accessibility service to put interaction tracking overlays.Svetoslav2014-10-211-4/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An accessibility service may register to observe the interactive windows on the primary display. These windows are the one that has input focus and ones a sighted user can touch. It is sometimes beneficial for an accessibility service to overlay a window to intercept user interaction and based on that introspect and perform an action on the windows that are on the screen. This is problematic as overlaying a full screen window that is touchable prevents the accessibility service to introspect the content under this window. This change adds a special type of window that only an accessibility service can place which does not affect what an accessibility service can "see" on the screen. Hence, even putting such a window full screen the service will be able to interact with the other interactive windows it covers. Change-Id: I053ccc3a5c6360a98dc40bdb172b54dab35d8b31
* | am 2f6fd874: am 5f978bfa: Merge "Retire RecentApplicationsDialog" into ↵Adrian Roos2014-10-201-1/+0
|\ \ | |/ | | | | | | | | | | lmp-mr1-dev * commit '2f6fd874510cd333f7fc0b08e146d5d069fa2013': Retire RecentApplicationsDialog
| * Merge "Retire RecentApplicationsDialog" into lmp-mr1-devAdrian Roos2014-10-201-1/+0
| |\
| | * Retire RecentApplicationsDialogAdrian Roos2014-10-081-1/+0
| | | | | | | | | | | | | | | Bug: 5162991 Change-Id: I429da977502f33e2091496f3a075b2c507a88e1f
* | | am f08b7ce9: am f247b908: am 4183a2fc: am 5d604181: Merge "Let ↵Kristian Monsen2014-10-181-0/+1
|\ \ \ | |/ / | | | | | | | | | | | | | | | TYPE_ANNOUNCEMENT be sent from any window" into lmp-dev * commit 'f08b7ce9e9888fc77bfe8d4af70500a7530aedcb': Let TYPE_ANNOUNCEMENT be sent from any window
| * | Merge "Let TYPE_ANNOUNCEMENT be sent from any window" into lmp-devKristian Monsen2014-10-171-0/+1
| |\ \
| | * | Let TYPE_ANNOUNCEMENT be sent from any windowKristian Monsen2014-10-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Part of fix for bug 17905712 Change-Id: I4e4b09f6b6342a27744e42984d483ef8de18fbff
* | | | am 0ee9f361: am 0b5af04a: am ebb38bcc: am cd2b54e6: Merge "Accessibility no ↵Svetoslav2014-10-171-29/+0
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | longer overrides strong encryption." into lmp-dev * commit '0ee9f36140530cf8ee60613f4f057c2ec95fe498': Accessibility no longer overrides strong encryption.
| * | | Accessibility no longer overrides strong encryption.Svetoslav2014-10-171-29/+0
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the accessibility layer behavior to reflect the new model where accessibility no longer overrides strong encryption. Now enabling an accessibility service lowers the encryption level but the user can bump it up in settings if desired. bug:17881324 Change-Id: Ic60d760c267d3f934040a42e1963b179bd8b9f5f
* | | am 216d08ff: am 0ee1d87c: am 515f14d4: am b22552c3: Merge "Send ↵Svet Ganov2014-10-161-1/+3
|\ \ \ | |/ / | | | | | | | | | | | | | | | accessibility events with no window." into lmp-dev * commit '216d08ffd548d056101af14af4634f4d796cec51': Send accessibility events with no window.
| * | Send accessibility events with no window.Svet Ganov2014-10-161-1/+3
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An app can send an accessibility event by calling the send methods on view or directly asking the accessibility manager to do that. While the recommened way to send such events is calling the methods on view a legacy app or app whose developer did not read the docs carefully may be calling the accessibility manager APIs directly. In such a case the event does not have assigned window id and does not get send. Since events fired by using the accessibility manager directly lack context to determine whether thier source is important for accessibility we assume they come from an important view to avoid breaking backwards compatibility. bug:18001711 Change-Id: Ie1c298fa5a0670cbeaedfcd64f820961c296b6ca
* | am a8df007d: am 423bf3d0: am cf0e4706: am 8ff6d70d: Merge "Clear identity ↵Svetoslav2014-10-041-4/+9
|\ \ | |/ | | | | | | | | | | before calling into the mount service." into lmp-dev * commit 'a8df007dd468730fb581e135d46e0ddead9106fb': Clear identity before calling into the mount service.
| * Merge "Clear identity before calling into the mount service." into lmp-devSvetoslav2014-10-031-4/+9
| |\
| | * Clear identity before calling into the mount service.Svetoslav2014-10-031-4/+9
| | | | | | | | | | | | | | | | | | bug:17787265 Change-Id: I4b9268d101e9ccfc30876fbf54bf28bb41fb4be6
* | | am a12d4856: am 3eddddb5: am c3493f94: am 88676e0b: Merge "TouchExploer ↵Svetoslav2014-10-042-67/+41
|\ \ \ | |/ / | | | | | | | | | | | | | | | computes incorrectly the click location." into lmp-dev * commit 'a12d48567478265bc360f2c29cc194d8830c099f': TouchExploer computes incorrectly the click location.
| * | TouchExploer computes incorrectly the click location.Svetoslav2014-10-032-67/+41
| |/ | | | | | | | | | | | | | | | | | | | | If there is accessibilty focus and the user touch explores location that does not change accessibility focus that is not in the app window, e.g. system bar, double tap does not click on the system UI affordance. bug:17588024 Change-Id: I6c8c0f65b208ae1d3f31d7f06b0721dc223ec19f
* | am e53a3188: am 9ae2bca4: am 31deb67d: am 76716c5a: Revert "TouchExplorer ↵Svetoslav Ganov2014-10-032-32/+108
|\ \ | |/ | | | | | | | | | | computes incorrectly the click location." * commit 'e53a3188365550d17422e534f6aec80249dbc447': Revert "TouchExplorer computes incorrectly the click location."
| * Revert "TouchExplorer computes incorrectly the click location."Svetoslav Ganov2014-10-032-32/+108
| | | | | | | | | | | | | | | | | | This reverts commit 851a5059a47cbf76e530c9d050a677cb6e3f8657 as it creates a regression. Let us revert this and correctly fix the issue the original change was trying to address. bug:17789608 Change-Id: I8abb1a61d5310430e839e4ef60e7ca5cc0cbdd80
* | am 0671790c: am c088ecc3: am 304a3528: am d35b072d: Merge "Fix accessiblity ↵Svetoslav2014-10-021-10/+16
|\ \ | |/ | | | | | | | | | | introspection from the shell user regression." into lmp-dev * commit '0671790c2895865ff0cc7780027427d1a9b95667': Fix accessiblity introspection from the shell user regression.
| * Merge "Fix accessiblity introspection from the shell user regression." into ↵Svetoslav2014-10-011-10/+16
| |\ | | | | | | | | | lmp-dev
generated by cgit v1.1 at 2025-01-08 16:38:45 +0000