multi-project commit with If6b9f8990d7cdbf570740a81096513698d0e0f4c

Change-Id: I124aed24be0beb4c472869594184ecf003c2fed4

Change-Id: If1b78183b24fa0029bc28e5f56a988372182903e

Change-Id: I44ec5bd3b2a00087603316f14d732164dbcf399f

This change moves dismiss timer of gesture floating preview text from
PreviewPlacerView to KeyboardView.

Bug: 7967461
Change-Id: I0ca5beddc93cb4bc4a405f914d217d37b997402b

Bug: 5037589
Change-Id: I9e1ff92df7d0c58eb7a0f33603adebc9efb86585

Change-Id: I4d1647b971b0e7a4cf1a96f341236f6ab1d2ab16

Tests have been broken again by recent changes to subtype
choice within Latin IME. This fixes the problem and all tests
pass again.

This change also includes a small fix to one test that was
checking for something irrelevant.

Change-Id: I6a03dea24f99b0d2ad84c4161a8413f3060bb811

Bug: 7972004
Change-Id: Ie5db5910efba851976da2284cafc69be2910d354

Previously, a logbuffer only held an n-gram.  Data went in and out of it, FIFO, until privacy
conditions were met (i.e. data not collected too frequently), and then an n-gram was saved.
E.g., if n=2, and only 10% of data is collected, then 18 words went through the logbuffer before
it captured the next 2 words.

However, if a user then went back and edited the n-gram, these edits were not captured.

This change changes the logbuffer size to temporarily hold data about words that are not recorded,
so that if the user backs up over them, the edits to an n-gram that we do eventually capture are
stored.  If the example above, instead of a logbuffer holding 2 words, it holds 20.  The system
waits until all the words not needed for the n-gram have been gathered (i.e. the buffer is full),
so the user has adequate time to edit, before shifting out the n-gram.  The buffer is still flushed
when the user closes the IME.  See the comment for MainLogBuffer for an explanation.

multi-project commit with I45317bc95eeb859adc1b35b24d0478f2df1a67f3

Change-Id: I4ffd95d08c6437dcf650d866ef9e24b6af512334

Change-Id: Ia3fca4881370ffcdd5f2b14d2d1094c51f4330ae

Change-Id: I508679c2ad21b2624760d37a9503e21733964d4c

Change-Id: I0161e5844dd325af9afba80ac54a569b16c80660

Change-Id: I7001d8b6200a5cefcf84630d663da8316422026f

multi-project commit with Ia4ec213e8356897807cb6a278fccdbaa945732f0

Change-Id: Ib3fe886dc889954a31586ab81d00a21d8d55efd2

Change-Id: If2fe6f0f4f88a6ae1f22664ded61cec6942c18b9

This is a preparatory change to fix bug 7969231

Change-Id: I44604ae75192a17b4e75a01f3e3d679d4901299e

Change-Id: I750a07c0c564a95ceac734afa873ca3da9626a7f

And add a test to make sure it stays not-broken.

Bug: 7946604
Change-Id: I996da3d5507d591ec25a13fb57434f39843f1df5

Bug: 7911739
Change-Id: Id2cd98385371fd98435943ed66ec5381dfaa48e0

Bug: 7964225
Change-Id: I4c572527b6f399282bdd963e38c147c7e69815ac

Change-Id: I6c6087580b67f497eaaf16900f8df7a4a895b8e3

- Now includes all historical data stored in a motionEvent
- Simpler API, refactored to move extraction code to JsonUtils

Change-Id: I52d9756ddbeaa14d1704787da59bf1aad18f0335

Change-Id: Ib7129692c673b3bce253120ee709e0253aeafa52

Change-Id: Id30828a141de86d9bcf8bce586d2adb468cc59e1

Change-Id: If5bc53efc67be507663091de0f569f604c03e719

Change-Id: Ica4e3193f369330da62a259c718b779ddf9fbde5

Bug: 7656666
Change-Id: I4b271af636f6103cb5287336229581365841d778

multi-project commit with I684ba5fed8c653777942e6b0366113ca40dfa37c

Change-Id: Id3804e6cfa97b4cdde212b8eebc413f76fa4772c

This change moves gesture preview text code from PreviewPlacerView.java
to separate classes.

Change-Id: Id8d17eff38e714c3b06aafd0b24985a9bd2d2f52

Change-Id: I16a27f2ed6ea66184bfdc9903180372cd7ea2fd1

Multi-project commit with I249d5fbe

Change-Id: Ia28c4e970992aa1299a30e604eaa5d096655c3a5

Bug: 7939324
Change-Id: I11b7af54893cb645f8a06266a0b0ba95dd0b02f9

Cleanup and prepare for replaying

Change-Id: Ie09e912c6e9c0d7375168c575ccf1cfd9375dd31

- Default keypress volume is set to 0.2f in resource.
- Default keypress vibration duration is set to 10 msec in resource.

Bug: 7055329
Change-Id: I83bd6288d171d9787d52e2b02e4e5305f1435681

Change-Id: Id8e08a1d5ec5efb2baf96a2634111619fcb9fd4e

It's useless to setAutoCorrection(getTypedWord()). Every time the
contents of the word composer are altered, the auto-correction is
reset, and at use time if it's null then the typed word is used
anyway.

Change-Id: I0870657a1ab3f456f376995b27e70703f7a5d23a

Essentially this does activate auto-correction with a hardware
keyboard, although a lot of things are still left to implement.
No proximity is used yet which means only missing and excessive
letters are considered. Dead keys are not handled. No combiner
is supported. No suggestions are displayed. Resuming suggestions
does not work correctly with a hardware key (because the view
holds a temporary hardware event 'onKeyPreIme' and the event
from the IME won't be handled until this is handled which won't
happen until after the IME said that it did handle the event).

Bug: 5037589
Change-Id: Idcb5c7b26d56717ed772d53c062362807f11cdae

Bug: 5037589
Change-Id: I829f70a258de58ef8d2b836a9b435198a226e37f

Change-Id: Ib0de800599ae7f12c86270a627616d5b52366414

In this test, it's impossible that start < 0 so the test is useless.
I'm not sure what the cursor test was for, but it's very old code, and
it seems the assumption was either misled or doesn't hold any more:
testing for the absolute cursor position against the length of the
word against the cursor makes no sense.

The net result of this was that when the cursor index got large
enough, resuming suggestion would not work any more.

Bug: 7586467
Change-Id: I3462082374fe9579bec7698f4d424de6ff5f2ded