The feedback string was not being inserted in the feedback logs.  Also changed the tag to
"UserFeedback" from "UserTimestamp" to better reflect the data recorded.

Change-Id: Iccf781b25e2573168c36e729419468f5bd73903e

Bug: 7969231
Change-Id: I75d495ee1ea126da9be4e269ee990ee0a97793c1

Change-Id: Ie11ff000675601acff5fbb00e9e9f48eb32c5071

Bug: 8001868
Change-Id: I0e5aab266bbaad8c68e4a900b8d5572977a0379d

multi-project commit with If6b9f8990d7cdbf570740a81096513698d0e0f4c

Change-Id: I124aed24be0beb4c472869594184ecf003c2fed4

Change-Id: I5ef20476318979f99f543f9300cf6198d18f6244

- Normal delete events are recorded
- Includes number of characters deleted for both batch and normal delete

Change-Id: I422da3ddc94fa0ccd6c7586eaacf14c62dd16679

Change-Id: Ia6f793611d4b18aecb1a635655af5edb639e1ecf

Change-Id: Iab2a422b367e7521f346481c7fe5e2575f2e9de3

- Fix function calls to happen at more resilient times
- In the case of phantom spaces, ensure that the logStatement goes to the
  correct logUnit

Change-Id: Ida8f6eba1e4f33d9f9b4735316e3c6316ed316c0

Normally logUnits are committed to a log when the word that their data
corresponds to is complete.   However, if the user reverts a word, or goes
back to edit it, then the system may "uncommit" the logUnit, and append
additional editing steps to the end of it.  When this happens, we want to
make a note of it in the log, which is what this patch does.

Change-Id: If2bbb948469824c76facf5f06ed8a6da8ff9777c

Remove the subtypes that don't get a dictionary any more in AOSP.
Also prepare for all downloadable-dictionary supported subtypes.

Bug: 7673670
Change-Id: I5b754a791233c270237b8f7e5e2208f7282ad294

Change-Id: I7802f07192a4cba4f3cfb5c08ce6d5d2d85a46c1

Change-Id: I65ecdead7e7bdeb8a5f1748e27068ddbd5d3ce00

Change-Id: Idcea4cd0256581e9868ac987fd1fa281ff074483

Change-Id: I07b18b5db81784dca32683e5f208088181c5eed9

Change-Id: I07c817061a0cc060197e0fea45195ca07a9bf276

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