Change-Id: I5a32882a088e4ff5bfe973a86465d6ff839113d9

Change-Id: I00f45d8dd7feb6c34c0a65a8545cddd2751796d0

Bug: 9127749
Change-Id: I96db15a3138e6b522c4c6ad16cc7faad577d3772

Bug: 8556775
Change-Id: I7e0516b344937b84b7d57cc4e5009b7f88e7dc98

Bug: 9112465
Change-Id: I6cd63007287b5a1a57cfbabff35d53f66fc5620e

Bug: 9112465
Change-Id: I63eb4115f393444560e80220d4c90f0f7101b934

Change-Id: I0737fb0b68f411f4db06014f2d94804935808922

Change-Id: I6da180cfa1b9e5aa39600e78e3bc41209a40f583
Signed-off-by: Keisuke Kuroyanagi <ksk@google.com>

Addresses b/9074239

Change-Id: I91a3bfcbd32b03e4891ff5f65be01383a3fb8975

Change-Id: Ie600993db561afb7891aac4765377fe4a8c4636a

Change-Id: Idd3647bb1a1d40df8bb89eda715d45427a58d0cd

Bug: 6522943
Change-Id: I181f7e8722bf1b3042d7f384ae8ebf87f29458a9

Change-Id: Ie59f08db947ca5314935c6b723cf498129b4515c

Bug: 7167303
Change-Id: I9a75b1b9b9127c5364da49b2a04b22c16a7ad535

Word boundaries are currently logged, but only if all the
details of a word pass the privacy filter and are logged.

This change records when a word is committed in all cases,
but does not disclose the word contents or any data used in
its construction.

Addresses b/9070768

Change-Id: I573679d0685c088aca65af99e46337a2f429f816

Change-Id: I803aa6c2160bfa1ffe992b28e7eb6e8a320c9762

Currently isAllowedToLog only checks the state of the
ResearchLogger, and does not consider which log the data is
going to.  This causes problems with the logs for Feedback.
The Feedback log should inhibit normal logging procedures,
but the system needs to be able to write specific data
directly to it.

This change renames to isAllowedToLogTo and adds the
destination ResearchLog as a parameter.  A FeedbackLog is also
added as a new class so it can be distinguished from other
ResearchLogs.

Change-Id: I5a1eea05bb040c26bf816b89179f44b3024fa2ad

Bug: 9054063
Change-Id: I092ab6e0077578d0aca57d2e41dfbc00b46e1ba4

Change-Id: Ie16d9514092d6d6f42881b975420e5d1431b776c

Change-Id: I843fd6bc20da95e61d1a05b5b34d6e4c9db59dab

Bug: 8944307
Change-Id: I8986622554f30aaf4f595099c4ab5652b75c972c

Bug: 8944307
Change-Id: Iaff9dd03d3d856a6bdaa2b16c4e71e95cd2b6349

Punctuation is currently put into the same LogUnit as the
following word.  This is counter-intuitive and makes
post-processing more complicated.

This change causes punctuation to be put into its own
LogUnit.

A tricky case is the phantom space.  A phantom space is
inserted right before other text, whose MotionEvents have
already been collected and inserted into mCurrentLogBuffer.
Phantom spaces are handled by creating their own LogUnit and
inserting it into the LogBuffer right before
mCurrentLogBuffer is shifted in.

Change-Id: I102d7cd93982ad37ba0abb6c1ac0f66b85b5f95d

* commit 'f1dcf725':
  Don't process recorrection or resets when not shown

* commit '96a9f357':
  Fix unintentional setup step advance in orientation change

* commit '769427cf':
  Adjust aspect ratio of setup image

Bug: 8954116
Change-Id: Ica27dbfc570643bb81e6cdf34cc7c796ea080d71

Bug: 8159728
Change-Id: I53e7d7c8fb5cc231ea94474b091e550f77ae8dab

Bug: 8159728
Change-Id: I578014912fa63c4c9b4c2c89aeae7ffec836b06c

When the user reverts a commit, this causes the committed
word to be changed. The user usually then goes back to edit
that word.  Going back to edit causes an uncommit, so that
the editing actions are added onto the LogUnit containing
the operations used to construct the word.

But currently, reverting also involves its own
commit/uncommit pair, with the caller performing the
uncommit, and the commit happening inside the revert
command.  This may have been necessary in the past, when
revert was called in different situations, but is
unnecessary now.  Furthermore, the guarding conditions are
currently such that the uncommit doesn't always undo the
effects of the commit, corrupting the log output.

Change-Id: I74af41f4f1db2fcabfa496dcc4a2d7bd0af19b3a

This is a follow-up to I7c01c3dd3ac33d7e96c00836256bae9c14b124ed

Change-Id: I9e3f8968c4bbf9525d5dfe101f71373c42f88361

Bug: 8159728
Change-Id: Ief8d7197879d24ccef529e975c23d6f11c7aa458

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

Bug: 8556975
Change-Id: If7839c5764f7a269243a9570c0b7782b6f7ee73b

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

Bug: 8915171
Change-Id: I2031e2aa4ebf33684221fc44d4a808112489724f