Change-Id: I6d91f3b086470b79306dbe2874db9748b9e0eb5f

bug: 6181736

Change-Id: I6522f19555c27f33c9ff4eaa8b2559a51a38f015

Bug: 4343280

Change-Id: I6adaf560f7a4f1f96dcb6ec2f61f20ee3001167e

Bug: 5964777
Change-Id: Id12c75966f6302e6f4ebbd4a8f474e05c601c88a

This isn't used any more.

Change-Id: Ie63ae621bcac9342b869b9f236f35bf66ec3a09b

UserBigramDictionary now assumes both functionalities. It will
be renamed to UserHistoryDictionary in a future change.

There are several reasons to do this. First, there is a lot of
duplicate code in User{Unigram,Bigram}Dictionaries that are
factored by the few lines of code in this change. Also, other
dictionaries like BinaryDictionary or ContactsDictionary all
assume both responsibilities, as should be the case
theoretically.

It is also possible to do this because previous versions don't
write any unigram data that we'd want to reuse. For even older
versions that do write data, we can't really make any sense out
of it. Bigram data however can be useful, and this allows us to
reuse it easily.

Change-Id: I755525f92744e1536eaef097527e8151b7859a30

Bug: 4343280
Change-Id: I4e2dfb00d9c843a8a285d409ac5ab8fca5fb1694

A lot of things don't really make sense in the old code.
Let's streamline it for now so that we have a cleaner interface
to work with. This is preliminary work for bug 4192129.

Change-Id: If01a5974cfadc43afced610c57fcf7fde67c1346

The keys' blinking that mentioned in the bug is caused by switching
keyboard layout resets the animation's alpha value to opaque but the
animation is still running and changing the alpha value
asynchronously.

I think that switching keyboard layout between alphabet and symbols
doesn't imply that the user stops typing. So the keyboard view should
continue typing state timer to keep animations' alpha values changing
and never reset the value.

Bug: 6174273
Change-Id: Id795feaf44750358f30c1b3dc8e783a7e62aefe8

Change-Id: I128134e201273b00478beb3d091952dd5530230c

* commit 'f87df70c':
  Fix centering more suggestions panel on tablet (DO NOT MERGE)

KeyDetector should use the distance from the hit box to detect the
key.

Bug: 6174250
Change-Id: Id1745d90222d1d1a10467f194b45307c12449944

Change-Id: I78f22bb38222fea54a55e460fcf728bf941d15e9

Bug: 6174065
Change-Id: I702760d44ead0eeb60d06360aa3bb03c2ec73325

Exit-fast, update comment, make a method private

Change-Id: Id103bf03aeef43a1a4d064ecabb819490dc5d39a

I tracked all the calls to the constructor, and the passed
list is never null. It's also final, so it's safe.

Change-Id: I320f907acee0b237bb286a9a183c18106809174a

Change-Id: Ia1c80eeff00a55573bb311f07e1275da23bdcf98

Change-Id: I58de87c1ba4cd1130419191f63ff83b685604356

All calls to this methods are made with an actual String. No sense
beating ourselves with an interface stick.

Change-Id: I6ef98286be6f81f73864b04f3a17e68f36a6e542

Change-Id: I6950897d262f610d502b7f8293b9dd8d2b53e6e8

This has been moved to the SuggestedWords object and is now
represented by a single flag instead of a flag in each suggestion.

Change-Id: I6e9a7cff5a7701de7e61b4de13baac25c9a87b1b

Also, the first word in a sugestions list can never be
obsolete.

Change-Id: Ib21439aac8db4e6ce5b15b7a2aabe4222bc354db

Change-Id: I9684c7b08244b34853ce8a99b6e9d885389f6687

Change-Id: I43dae30774c40a9d6e7396f8fa73ed4b82a7c777

Change-Id: I5aee4c36ceaacbb1dbfc47c011f1e4aec4b9dca6

Change-Id: I792cacc137b1b782c28b258bf91bf475bd0ced89

Bug: 4343280

Test:  I11f8518d9ee

Change-Id: I4b90bdffffed9736af223ac83c1a54019add70bb