Merge commit '979f8690967ff5409fe18f5085858ccdb8e0ccf1' into gingerbread-plus-aosp
* commit '979f8690967ff5409fe18f5085858ccdb8e0ccf1':
DO NOT MERGE. Backport LatinIME from master to Gingerbread
Merge commit '6511376ff6f06aba15cdd1ab598a96924bae16ad' into gingerbread-plus-aosp
* commit '6511376ff6f06aba15cdd1ab598a96924bae16ad':
Fix a bug in backspace handling for the "Tap again to save"
Merge commit '6558253160e2039c87f424bd814f402ecd31de3b' into gingerbread
* commit '6558253160e2039c87f424bd814f402ecd31de3b':
Fix a bug in backspace handling for the "Tap again to save"
Merge commit '7faf89f8015ebf4b1873b7e42c93c8149ec4316b' into gingerbread-plus-aosp
* commit '7faf89f8015ebf4b1873b7e42c93c8149ec4316b':
Import revised translations. DO NOT MERGE
Merge commit '1812bcebd653ce7ba7d89ca163954e57b5c67021' into gingerbread-plus-aosp
* commit '1812bcebd653ce7ba7d89ca163954e57b5c67021':
Backport https://android-git.corp.google.com/g/#change,52371 to Froyo. Fix bug: 2693836 - Russian keyboard is missing a letter
Merge commit '88e7b49fc8657544380620729eb28966669103a2' into gingerbread
* commit '88e7b49fc8657544380620729eb28966669103a2':
Backport https://android-git.corp.google.com/g/#change,52371 to Froyo. Fix bug: 2693836 - Russian keyboard is missing a letter
Merge commit 'f02964264f196447b03a88591a2964b67c318718' into froyo-plus-aosp
* commit 'f02964264f196447b03a88591a2964b67c318718':
Don't auto-select the system language in IME language selection screen.
Fixes http://b/2650378
On entering the selection screen, don't add the system language in addition
to other selected languages.
Change-Id: Id7a3b45df39a8493d17be668029eee139bf00ff3
Sometimes the only motion event that is above the keyboard is the UP
event. In that case we can't expect one more event to come that will
dismiss the extension. So don't show the extension if the only Y < 0
event is an UP event.
Change-Id: I04a8b742dea03cd700006dc5df740ac7d9620c0b
Merge commit 'f9d0f3a81ad4220672f90a8799a79e63e53c46d3' into froyo-plus-aosp
* commit 'f9d0f3a81ad4220672f90a8799a79e63e53c46d3':
Fix for: For Voice IME busy circle displayed below waveform
bugfix for: http://b/issue?id=2568048
[Sapphire] ]For Voice IME busy circle displayed below waveform.
STEPS TO REPRODUCE:
1. launch Calendar . -> Select menu -> New Event.
2. Switch soft keyboard to Number view.
3. Tap on mic symbol of to speak
4. Speak any word to enter in Text field .
5. Verify busy icon ( circular icon ) displayed in "working " screen.
EXPECTED RESULTS:
Busy circle should be displayed in center of waveform
OBSERVED RESULTS:
Busy circle displayed below waveform
ADDITIONAL INFORMATION:
Spoken word is enetering in text field correctly.
Change-Id: I043ce6a985f526cade0e9f63525619a92d918485
Merge commit 'c2b8c16bdf392c81785031483d21740c5e883046' into froyo-plus-aosp
* commit 'c2b8c16bdf392c81785031483d21740c5e883046':
Possible fix for monkey bug: 2529350
Merge commit '3e0c82ec80a69c4adbd60546c3c56c83c43ec7eb' into froyo-plus-aosp
* commit '3e0c82ec80a69c4adbd60546c3c56c83c43ec7eb':
Fix for 2568664 : Slide gesture on spacebar is not reliable anymore
This was due to the multi-touch error correction code that was recently
added. Make sure that one of the move points is in the upper 3 rows
to allow for fast swipe on spacebar.
Change-Id: I420bdb83a4cd8833c4158bc37a2d806b8c83b948
Detect sudden moves that have a large delta that would not be a typical drag
by the user when hunting for a key. Drop move events until the user releases
the touch and register both starting and ending keys instead of only the
ending key. This reduces the frequency of dropped keys on touch hardware that
isn't able to detect multi-touch reliably.
This also takes into account diagonal moves or right angled moves due to
pseudo-multi-touch.
It weakens the swipe gestures (to swipe, you'll need to swipe slowly and fully,
otherwise it will trigger 2 keys)
Change-Id: Ieba3a0bef4c8910f0f17aa20baedb3581d1de12b
Keep a reference to the openhelper around across locale and input language
changes. Also, share the openhelper between the queries and updates. Creating
a new one in a separate thread could cause it to be closed at the wrong time.
Monkey bugs, probably dupes.
Bug: 2560471
Bug: 2544169
Change-Id: I6eb39145de7191732ddde455728bf147a2d1ba31