| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Bug: 218835043
Test: make
Change-Id: I2c19ca3b6e4773de533cceac6b5341ae964b4fd4
|
| |
|
|
|
|
|
|
| |
Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library.
Bug: 145132366
Test: m && diff unsupportedappusage_index.csv
Change-Id: I0c336de56bc4a041dc97ff9b7927f62f0b44b457
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL deprecates the following two classes.
* android.inputmethodservice.Keyboard
* android.inputmethodservice.KeyboardView
Most likely having these classes in the Android Framework does not
make much sense anymore, because basically it is just one
implementation of how keyboard-like UI can be implemented on top of
public Android APIs. Source code of these classes have been available
as part os AOSP. Thus it should not be that difficult for app
developers to have their own copy of these classes in their project or
re-implement a similar widget by themselves.
Fix: 116815596
Test: make -j checkbuild
Change-Id: Ie0cb0456c2cc4eacd4b188514508021774f60591
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For packages:
android.inputmethodservice
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: Ia0c5584247aa586cb30a4e4dd2618ec7f92f90ed
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
KeyboardView relies on deprecated Canvas#clipRect(Rect, Op.REPLACE).
This method is now unsupported and throws runtime exception.
Operations other than Difference and Intersect are unsupported.
This method call can be replaced by saving initial Canvas and calling
intersect operation of Canvas#clipRect(Rect).
Saving initial state can be achieved using Canvas.save() and
Canvas.restore().
Fixes: 79777033
Test: Manually verified with SoftKeyboard (which uses KeyboardView)
1. m SoftKeyboard
2. Set current keyboard to SoftKeyboard
3. SoftKeyboard runs fine
Test: Tested Canvas.getClipBounds() is consistent across save() &
.restore() operations
Change-Id: Id34c289f152b2ec06f37fffa9f940a909153447c
|
| |
|
|
|
|
|
|
|
| |
keyPreviewHeight.
Test: make ds-docs
Bug: 68838052
Change-Id: I25c58d2cfd2fe3637edcd6962202e5b0d1632e0e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will now be controlled by individual accessibility services.
We'll provide the password information to them, and they can
present or hide the information as it makes sense for their users.
Password information was anyway provided when a headset was
connected.
Bug: 28139568
Test: Manually verified that TalkBack now speaks passwords on the
lock screen and in text views. Since I'm removing functionality
that didn't have tests, it's tricky to have specific tests.
Change-Id: Ic3c724ccce5762ee9dcd9e7dcbd4eae6734dd05e
|
| |
|
|
|
|
|
| |
A recent change in how the handler is created in KeyboardView
caused the password change flow to crash in ChooseLockPassword.
Change-Id: Id5fcb256f9a09b75bf91c5c79614d8abfc29747f
|
| |
|
|
|
| |
Bug: 25116730
Change-Id: I4e394c281feef6f7987433298d66f2df11352416
|
| |
|
|
|
|
|
| |
Using CURRENT isn't always safe.
BUG: 18557273
Change-Id: I12e197ab25b8ffdc04c5e74836945177870698a2
|
| |
|
|
|
|
|
| |
Also fixes a typo in UserHandle's docs.
BUG: 18295054
Change-Id: I1f5384f84062b9ea7dcbebe1e5f64af331028d41
|
| |
|
|
|
|
|
| |
Also updates the constructor of every class that extends View.
BUG: 10676369
Change-Id: Ifaf27bf82028d180afa4931c0e906df88d858ac3
|
| |
|
|
|
|
|
|
| |
1. In latin IME key up types in - now the keyboad view does the same.
bug:6534935
Change-Id: I91cd40c5cd541199f3fb43e4d0bf26be511dcd09
|
| |
|
|
|
|
|
|
|
|
|
|
| |
By default we do not speak passwords if the user has no headset. However,
many users find this too restrictive and would like a way to enable
password announcement. While we cannot speak the passwords all the time
,to avoid leaking them, we expose a preference so each user can choose
the option that best works for him/her.
bug:5712607
Change-Id: I6eb0c40834abe5297f7dc74be02d180a5bef0174
|
| |
|
|
|
|
|
|
|
|
| |
A new patch checked in Latin IME makes it behave like any other Views. Touch
explore announces the letter under the finger and subsequent tap types in the
letter. Making KeyBoardView consistent with that.
bug:5552217
Change-Id: Ifeb6c3f071a5d64d0a16de584bf04ea40fff62fc
|
| |
|
|
|
|
|
|
|
|
|
|
| |
verbose.
If accessibility is enabled and there is no headset we do not speak the pressed keys.
In such a case we provide a prompt to the blind user to use a headset. This was announced
on every keypress which is quite annoying. Now this is announced only once.
bug:5342234
Change-Id: Ibe55ad991ad2153d09cde57b030544948fa0d73b
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The buttons on the lockscreen were sized at startup time,
before the actual size of the keyboard's container (KeyboardView)
was known. Also, horizontal/vertical gaps were not taken into
account in calculating perecent sizes of the keys. This change
causes resize events (including the first one where the container
size is finally known) to recalculate the keys' sizes and positions
according to correct sizing of the container and the keyboard's gaps.
Change-Id: I5ba7a401226ed4b100e5739f3405388955d97997
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1. The password lock screen is accessible and with this
change the PIN lock screen is accessibile as well.
This is enough to cover the enterprise use case of
imposed lock of the deivce. we will hide the options
for pattern since it is hard for use by a blind person.
We may reconsider this for subsequent releases.
bug:4978246
Change-Id: I069f8ebe1ff7ea1591cab42ea580f00f3d31b2e6
|
| |
|
|
|
| |
Revert "Adding accessibility support to the PIN lock screen."
This reverts commit 0d67c8900276494cd38539bce40342e11ed83508
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1. The password lock screen is accessible and with this
change the PIN lock screen is accessibile as well.
This is enough to cover the enterprise use case of
imposed lock of the deivce. we will hide the options
for pattern since it is hard for use by a blind person.
We may reconsider this for subsequent releases.
bug:4978246
Change-Id: I67ef783b799ffd64ebff6cdb614c03025fc911e6
|
| |
|
|
|
|
| |
Bug: 4310526
Change-Id: I67be4e69056faea9bdf4157ada9435dd326e52f0
|
| |
|
|
|
|
|
|
|
|
| |
Do not correct the touch point if it is within the range of
verticalCorrection from the top of KeyboardView, so that the touch
point will not have negative y-axis value.
Bug: 2659128
Change-Id: I91a3e65fc5dee1383dbbfb45690e307fc0adc1d1
|
| |
|
|
| |
bug: 2519903
|
| |
|
|
|
|
|
|
| |
cancel event.
Set a 70ms debounce time - i.e., if you spend less than 70ms on the touch-up key,
which was less time than the time spent on the previous key (assuming they weren't the same),
then don't emit the last key. Use the previous key that you lingered on for longer.
|
| |
|
|
|
|
|
|
|
|
|
| |
PasswordEntryKeyboardView
- Added new PasswordEntryKeyboardView to internal/widgets. Widget supports:
- alpha mode with symbols (latin-1 only).
- a numeric keyboard
- IME emulation that applies keyboard input to arbitrary top-level view widget.
- Added new transparent assets to framework resources.
- Modified Keyguard and Keyguard layouts to use new PasswordEntryKeyboardView.
|
| |
|
|
| |
Needed for predictive hit target correction in LatinIME.
|
| |
|
|
| |
See http://code.google.com/p/android/issues/detail?id=6374
|
| |
|
|
| |
Abort the repeat sequence until the next touch down event.
|
| |
|
|
| |
Needed for Extension keyboard feature.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Sometimes quickly touching the screen with two fingers will result
in the firmware thinking one finger moved very quickly. This code
tries to identify the difference between the two based on velocity
of the last N points versus the velocity of the last M points and
figure out if there was mostly acceleration or a sudden deceleration.
It's still not perfect and very dependent on the touch hardware.
|
| |
|
|
| |
messages.
|
| |
|
|
|
| |
Also lock repeatable keys so that you don't get space and 'v', for example,
when you move just a little bit off the spacebar.
|
| |
|
|
|
| |
Most users seem to expect the feedback to show up right away. So
remove the delay before the bubble shows up.
|
| |
|
|
| |
Also reduce garbage when switching between keyboards.
|
| |
|
|
|
| |
Use PX unit when setting the text size since we're getting the size from getTextSize()
Reduce delay for popup.
|
| |
|
|
|
| |
When switching keyboards in the IME view, make sure that any pending touches
don't generate up events when released.
|
| |
|
|
| |
Expose invalidateKey and invalidateAllKeys for subclasses to call when needed.
|
| |
|
|
| |
Automated import of CL 145778
|
| |
|
|
| |
Automated import of CL 143147
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|