Bug: 8159728
Change-Id: Ifb08b62e11008ad56715a07825c0fbc719130ebd

Bug: 8159728
Change-Id: I578014912fa63c4c9b4c2c89aeae7ffec836b06c

Bug: 8159728
Change-Id: I0306efe99aa8db97ec6a1888240f0538480ebea5

Bug: 8159728
Change-Id: Ief8d7197879d24ccef529e975c23d6f11c7aa458

bug: 7167303

Change-Id: I45ca9d31cf4f8492dde367f997d8e36f4a07cffe

This reverts commit cb0d1c4c

Change-Id: Ie2c8e01c25bd051b6157e8f32ab84392a0c7252a
bug: 8954116

Bug: 8915171
Change-Id: Iabdeb7920f67f89246087c3ee06240406ecfbc3d

Change-Id: If353869720895ee5355079c15c724132762dd70c

When the keyboard is hidden, the suggestion strip is
never visible.

Bug: 8954116
Change-Id: I9f242d07b49ad60b625a22429bb013251e814905

For a while, the ResearchLogger supported comprehensive recording of the
last few words in case the user wished to upload this data to give
developers feedback.  However, this mechanism was not implemented well
(keeping a separate copy of the data), did not make the collected data
clear to the user, and was not working properly in the latest build (NPEs).
The mechanism in fact was deprecated in favor of the "userRecording"
mechanism in which the user explicitly turned on comprehensive recording,
demonstrated the issue they were experiencing, and then turned it off.

This change removes the vestiges of the FeedbackLogging mechanism.
A feedback log is still used to hold the user's message, but it is created
in a local variable as-needed, and not persisted in ResearchLogger.

Change-Id: I6a09d0ed36e1eddb6e57895e7428d22107f75f49

The IS_INHIBITING_AUTO_UPLOAD flag is tested in isPossibleToUpload, so it inhibits all uploads, not
just automatic ones.  Renaming to IS_INHIBITING_UPLOAD.

Change-Id: Iceed79260d4b062147f40c09f0c5bb06b2519b1b

Change-Id: I9b70a81c1f507e5e9a2bfdcb179dea1cc03e0517
Auto-generated-cl: translation import

Bug: 8556975
Change-Id: If7839c5764f7a269243a9570c0b7782b6f7ee73b

Bug: 8556975
Change-Id: I793dd90223f4da091a212ff54a02d19f03e49d6c

This change registers the functional key when sliding input mode is
end at the functional key itself.

Bug: 8915171
Change-Id: I2031e2aa4ebf33684221fc44d4a808112489724f

Bug: 8556975
Change-Id: I11260a64dc13c102bac7a9742dc66f2b05fd32de

This is a follow up of I275c99db8a.

Bug: 8556975
Change-Id: Ia6c2ab878760523da767036ce0bfc6c8350e1a92

Bug: 8915171
Change-Id: Id8685f90766c7de55b56476de83abf97150a186d

Bug: 8915171
Change-Id: I04f84c29f10abc0207072d2165c75dd20f053f92

Bug: 8556975
Change-Id: Iffc53d6a40dd77860434c5f7f4f59af5cd1ba92b

Bug: 8556975
Change-Id: I29d3a305b6ac3d8e3620c6d8592d85047d62bf48

Try reducing some confusions between GesturePreviewTrail.java and GestureTrailsPreview.java

Change-Id: I5fe2ee740cf1b32210530188153f6f6937e34b68

JsonWriter requires that its clients pass it only a single top-level object.
The existing implementation tries to make code cleaner by having mJsonWriter
never be null, and instead use a global static "NULL_JSON_WRITER" that just
discards data.  But because JsonWriter complains if more than one top-level
object is passed, making this a global object does not work.  This change
instead copes with mJsonWriter being null.

Change-Id: Ia37ccfc8646e91f11a64713dd92d2846eb86ac54

Bug: 8556975
Change-Id: I275c99db8a0d10594a5a8c0c27ebc1a87495c307

Bug: 8336068
Change-Id: I90a0f259129a3f3319b158b060154cc43960c234

Bug: 8336068
Change-Id: I35b94dd87c5b01d3e927da8f918a5398dd565d33

Bug: 8336068
Change-Id: I183b8e3fd1b3898d5f8dbbb13a0c93c64341fc38

This is an optimization. It also happens to work around what
seems to be a framework bug in JB MR1 / MR1.1.

Bug: 8771179
Change-Id: I62cc7acdc8656d75f8a50c068c4e9d8c6ceb74a0

Bug: 8885165
Change-Id: I85c78b23955169972fb0f5395463b6fe47f12c9c

Bug: 8897600
Change-Id: Ibf245e32468e5740ad9d65b8ff1f1e87b430d287

Previously, mMainResearchLog and mMainLogBuffer were set up
when the user moved to a new TextView, and set to null when
the user left the TextView.  This change causes
mMainResearchLog, mMainLogBuffer, mFeedbackLog, and
mFeedbackLogBuffer to be non-null forever after init() is
called.  start() no longer sets up these fields; instead
they are cleared and reset every time stop() is called.
Checks for null values are now removed.

The earlier code just didn't initialize these variables if
the user disabled logging, but since the new version
invariantly keeps these variables valid, we add a check for
whether the user has enabled logging in publishLogUnits().

Change-Id: Ifde3517f1cf924cfa33cda95fec24529b52b3c08

Change-Id: I192c67e9e8de44f073abc70ec85ebcdb36356c2e

This is a bug; the ResearchLogger uses ResearchSettings.readResearchLoggerEnabledFlag() instead,
which the user cannot change.  (We assume they will just switch to a different keyboard.)

Change-Id: Ib5731c9eeb2bc29d9cf8608033326674f5eb6f7b

Change-Id: Iea11a095adb15fbf4be38f34542119f8bc7bcbff

Bug: 8556775
Change-Id: I46a10f8dc938cab493933f0f2b4e1f7779b24f6f

Bug: 8556775
Change-Id: I9069b2b44356bbae9fa4aaf0b99c3d723a8c9c58

Bug: 8450279
Change-Id: Ib8433442ae6ca6c28da2652bff687cdeaf7c196e

Bug: 8159728
Change-Id: I458df60cb39f81cde3c08190af0ab08d304f9d98

Bug: 8336068
Change-Id: Ifac84361e4e37b4aa106cbdbfffb83883ec2f8e6

Change-Id: I77a0aed9771ecc28a56226bb5f9776c1e1cf8b4d
Auto-generated-cl: translation import