Change-Id: I5f85a7a0f94ea9ecbe0c4a8caebcf551fa9c9669

Change-Id: Ie69d84e090f69dc3ea1f5de73ad8c954ecd2c6a7

Bug: 10920165
Change-Id: I340759eadbde7fb64cb3b9a3c619ee3a768cedf8

Bug: 6669677
Bug: 10667710

Change-Id: I6cdc6a6c9cacc7f276fda3a26ec31e3eb928471c

Bug: 10920165
Change-Id: I6372492e97297baad4c5aeeb3fb36dcccd7a944b

Change-Id: Ic586e46e5a9f59de53d53e59886d635345940974

Bug: 11032428
Change-Id: I5d422f1c15a582015770ef9a652348ca6eb8ab85

Change-Id: Iaf1556fec194d17cb4318f2bdcc837f8d79449ef

Bug: 6669677

Change-Id: Ib465fa7e1a7f289a07843535ba89d0dd5259e803

What's happening here is, setAlphabetKeyboard sets the
keyboard to AUTOMATIC_SHIFTED and updates the keyboard, then
restoring the keyboard old state sets it back to UNSHIFTED without
updating it. When we finally know what the correct value is,
we try to set it to UNSHIFTED, but since that's already the currently
recorded state, it skips updating the keyboard forever.

The solution is to avoid setting the shift state without updating the
keyboard.

Bug: 10948582
Change-Id: Ic8670401e378f8284e851281f91a9ad93eac8e90

Bug: 10118761
Change-Id: Ia7d1c6c526dae849f447c26387e96a4fb4d6042f

Bug: 10920165
Change-Id: Ie9008452ee292fb0b1fec66e2ffed228c4af6c3e

When there are too many bigrams, we stop reading the file,
so the file pointer is in an inconsistent place. This means we
have no idea what's going to happen next. It's better to crash
right away.

Change-Id: Id3b7b78cbe4fda3493b3c9c46758763e1ab5f6a3

Bug: 9059617
Change-Id: I066abf018df5aaeabf415425dd822ebe233e6008

Change-Id: I042ff041b68572182c87dc87db6a6aa2bbbefc6c

Bug: 9059617
Change-Id: I7e4e05ffa8c68cfebbe362a977fd176555cad12a

Bug: 10831272

Change-Id: I995c619dc18a9120a47f547d31045cb73a9353ec

cherrypick of Iaa9b79fc770d8ae2ec9d7c362c90c28bc9f65ea8

Bug: 10964805
Change-Id: Id5e67b00bf9594be0591c87407a78146297e0e78

Groundwork and implement simple decay.
Increment probability when typed and decrement probability
at GC.

Bug: 6669677

Change-Id: Ib12caead0cbeef4ce7808fe8ac0b00ee331523fe

Bug: 10964805
Change-Id: Iaa9b79fc770d8ae2ec9d7c362c90c28bc9f65ea8

Bug: 10920165
Change-Id: I42eb7f228994a56c2f31a1c83904c8c360b6d088

Bug: 6669677
Change-Id: I8fbae190dd44a6bdbee7e9b6d3a16208322727f7

Change-Id: I1371d41760b38834d1d5ff40e682ac0a6fc9f2e9

It was possible that fetchNextTasks() would be called by multiple
threads concurrently.
If it happens, some tasks in the task queues might be ignored.

cherrypick of Idc81c43c45e382da3850cc55b9a42c281548d2a8

bug: 10957075
Change-Id: I41bf90dda15306ee879350f96a791d940ea31da1

Bug: 6669677

Change-Id: I2462777eaa07600f1c774226adfc4f351882f523

BUG: 8669376
Change-Id: Id71b2c2835daa7a8c9d6c92c57a7e302551c289d

Cherrypick of Iead7268a9371b48d729a5f65074ccbc05f3185db

Bug: 10831272
Change-Id: Ib6f314ac68696616532ff9c05c7f35813137bf9f

Bug: 6669677
Change-Id: I05ea2201d822dddf062b08c8467daa336760e16c

Bug: 10831272

Change-Id: Iead7268a9371b48d729a5f65074ccbc05f3185db

This is not enough to really fix behavior with TYPE_NULL,
but it does make things a bit better.

Bug: 10949594
Change-Id: Ia359f781cdd76a2e2c5a4c9f166025d81b931174

It was possible that fetchNextTasks() would be called by multiple
threads concurrently.
If it happens, some tasks in the task queues might be ignored.

Change-Id: Idc81c43c45e382da3850cc55b9a42c281548d2a8

Change-Id: I542db0c717c0bc05c8baa08f1e9db0a05946a99b

Bug: 10920165
Change-Id: I749dd0269e788799e30b10beb2671813d40ce15f

Bug: 6669677
Change-Id: I46d23deee1fd091678f4593561cb8687eb815212

Followup to If4e44eca3cdc5bb02cf2e0c8c44ecd4bf27fae57

bug: 10622489
Change-Id: If98b2c75725f8692f0c2b41c33e448086404479b

Bug: 6669677
Change-Id: I859be934f0c60485e04cdc4cab288a18242fa04e

Bug: 10920165
Change-Id: I86017456ea9fa5d6e12b57172c34f5ed4f88ef94

Bug: 6669677
Change-Id: Ie90417fa9b726454fe729a665fcd549efabb9e94

Bug: 8967766
Change-Id: Id40f54f4d9f43d1f796377983a5fc0ca3417e133

Bug: 7963631
Change-Id: I2eb110949f3d3b7817dbd9448654954fdee39ac2