Fixes b/7652661

In some circumstnaces, when hiding the window, the logger tries to capture the TextView contents
and restore the cursor position based on the values stored in LatinIME.  However, the IME may not
know the cursor position.

This fix does two things 1) doesn't try to reposition the cursor if the TextView contents are not
to be captured, and 2) if the cursor position is unknown (i.e., == -1), doesn't try to move it back.

Change-Id: I3976aaccf58c18f892c3a8530218ae52bcac9989

Bug: 7601672
Change-Id: I15faa4829b98f7b4dd07013fdd58bc2c527bcd6f

Bug: 7548583
Change-Id: Id807af31f581c08ff8074ed1f6766337bea9469f

Bug: 7594165
Change-Id: I2854a49b2a2e5d3e36cafc5196191359fd2bf003

This reverts commit bdbe279c

Other half of this change couldn't be committed because of a inter-project directory migration.  Reverting until things settle down.

Change-Id: I3862fc8485dfca6d507f620e905cfa583aa0e39a

Bug: 7594165
Change-Id: I9dc42919bd196c249c79668570004d3f541cc9ec

Log statements are now recorded with a timestamp.  This is important for filtering out statements
not part of words that are sampled when spaces are inserted automatically.

multi-project commit with Change-Id: I68221a2528045d25632aef4bb716f92a4f4a56a4

Change-Id: I9f49c36391e1e1773b6d4876d7387c893024f87b

Previously, a logunit was considered a word only if it was all letters.  This is important for
tracking bigrams correctly.

Now, a logunit must have only at least one letter.  The dictionary check is still performed,
and punctuation, etc. still comes in as separate LogUnits.  But a word can contain a space,
which helps set up for logging words where spaces are inserted automatically, and other situations
in which text is committed with an additional space tacked onto the end.

Change-Id: Ia74094a99058890d20a9cdadf2d0989841a79a41

Change-Id: Id68de4c6b2df574a38bb5ca800a9b641b1d78200

Change-Id: I77bbd5e1888281e838d87824dc04a574b1a7ecb7

Change-Id: Ib2ade2bf51c293c65fc9206a9a16694e6d18da50

Change-Id: Id52baefb3d61eb46b3679e1ba3aa7ef7cd020efc

Change-Id: I03729506984f259dee63f3a66fd91963e3403d16

Change-Id: Id49eee7c38595ea312dc9a63341a376825030035

Change-Id: Ia6f41dc0ce7d3f3a1e4a8bbe838835cbdd94e6e9

Change-Id: Ic6d72b5a34ddfbc55317fa651f78af6f50c9a284

password data collection was too "sticky"; the next field wouldn't be collected either.

Change-Id: I739a956f663cff33216f83ac453b2a89d8c33dde

Change-Id: I23784117f77da54ee2a0670e65d86e26d762a687

Bug: 7594188
Change-Id: I1977acb7189f8eb186b9b20a3e5b64b4aaabf191

This is a follow up of I6f851248.

Change-Id: I3fe17f3c81ed35e7c38ac9701e73c6b2c1ca8d63

Bug: 7595187
Change-Id: I6f85124815f18706b2b2b5b5da2783dffd246e8c

Bug: 7594165
Change-Id: I7849d763e49b57716e8418fb8b6f90eca3a5d2ec

Change-Id: If7037f3e0606ee34d1a6739cc39da23de18cc35c

Bug: 7529860
Change-Id: Iec82459348722be358ae2ded15deafac21749dcd

Add Rial(ar), Indian Rupee(hi), Tugrik(mn), Baht(th), Hryvnia(uk),
Dong(vi) currency sign keys to symbol layout.

Bug: 7455289
Change-Id: I0f819631ff05c4a31d3a6868dea5e18a1797f103

Variations are not flags - they should not be OR'd in this way.
Only one variation may be active at a time.

Change-Id: I9d3d4c8fc04af56c914c65f9c55f1e7b9517fc68

Correctly check the variations to determine if we should
add automatic spaces (in manual picks and gestures) or not.

Bug: 7164981
Change-Id: I19e25af839b4062c217113cd804b1473912f22a5

The subtype locale name on the spacebar will be suppressed when only
one subtype is enabled and
 - Subtype locale is equal to the system locale.
or
 - Subtype language is equal to the system language but the subtype is
   implicitly enabled.

Thus the "es_ES" system locale chooses "es" subtype keyboard
implicitly but the keyboard doesn't have the subtype name on its
spacebar.

This change also removes Spanish Latin America keyboard.

Bug: 7531804
Change-Id: Ib929e8235d643c0ba039eb010e18ab721a734e15

Bug: 7531804
Change-Id: Idd66ee30e5228260540308a97c930185b48e775f

This reverts commit 6ce66d1c

Change-Id: I90004a5fea0bc7999ecf8742f883ff4dac264d8a
bug: 7565414

This reverts commit 6ce66d1c

Change-Id: I90004a5fea0bc7999ecf8742f883ff4dac264d8a
bug: 7565414

Change-Id: Ia5079368a1bc86ccdf0052445dc6945041c0abca

Bug: 7164981
Change-Id: Id672104a0fda99c52923913fb0e40c3a1ead4787

Bug: 7482766
Change-Id: Ifdfa110c44b95acfbcd3e0aa34f675c70b7d7285

Bug: 7075923
Change-Id: If139411db4aa65eed64337bf2a79387cfcd04496

Bug: 7075923
Change-Id: I306e1ff5d9f873541e84e1fafb64b9473947f623

Bug: 6672279
Change-Id: I120613e36ba6a690e54447fa6c9c90e131f2a155

Change-Id: I1ee258948a8335af7996f9e3afcc0508adbb1ac0

Not sure when this happens exactly, but it is possible that
InputConnection#getTextBeforeCursor returns null. This
happens for example upon rotating the screen with the
composing field empty in Gmail.
In this case, StringBuilder#append will convert the null
pointer into the string "null", which is sure better than a
crash, but can have a number of bad side-effects, like
auto-caps not working.

Bug: 7533034
Change-Id: Ia1cfab432c13a12ff1c2f013c59bac05a587f553

In this kind of series of calls, it's possible that an outer call to a
constructor fails, but the inner succeeded.
Example:
try {
    is = new A(new B());
} finally {
    if (null != is) is.close();
}
In this case, if new B() succeeds but new A() throws an
exception, is stays null and the intermediate object is never
closed. This is what was happening in this instance.

Bug: 7377336
Change-Id: I3fae9fec1135244982fcf5098c76d93f3e0f2add