Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • trie-js-dumping protected
  • hitbox-boosting protected
  • model-metadata protected
  • lm-2-finetuning-whisperggml protected
  • lm-2-finetuning protected
  • lm-2 protected
  • language_model_experiments protected
  • 0.1.24.2 protected
  • 0.1.24.2-rc1 protected
  • 0.1.24.1 protected
  • 0.1.24.1-rc1 protected
  • 0.1.24 protected
  • 0.1.24-rc1 protected
  • 0.1.23.2 protected
  • 0.1.23.1 protected
  • 0.1.23 protected
  • 0.1.22 protected
  • 0.1.21 protected
  • 0.1.20 protected
  • 0.1.19 protected
  • 0.1.18 protected
  • 0.1.17 protected
  • 0.1.16 protected
  • 0.1.15 protected
  • 0.1.14.1 protected
  • 0.1.14 protected
  • 0.1.13 protected
28 results
Search by author
  • Any Author
  • Aleksandras Kostarevas Aleksandras Kostarevas alex
  • Dean Dean dean
  • Tom Folbrecht Tom Folbrecht tom
  • sameer sameer sameer
4 authors
  1. Jun 23, 2015
    • Tom Ouyang's avatar
      Workaround for preserving responsiveness on a slow InputConnection. · 912016b6
      Tom Ouyang authored 
      1. Add mechanism to detect a slow or non-resonsive InputConnection (IC)
2. When IC slowness is detected, skip certain IC calls that are known
   to be expensive (e.g., getTextAfterCursor).
3. Similarly, disables learning / unlearning on a slow IC.
4. IC slowness flag is reset when starting input on a new TextView or
   when a fixed amount of time has passed.

Note: These are mostly temporary workarounds. The permanent solution is
to refactor RichInputConnection so that it is less sensitive to IC
slowness in general.

Bug: 21926256
Change-Id: I383fab0516d3f3a8e0f71e5d760a8336a7730f7c
      912016b6
    • Dan Zivkovic's avatar
      Detection and logging of slow input connections. · 73aaf683
      Dan Zivkovic authored 
      Also adds a hook to log using StatsUtils.
Proto change is coming in a separate CL.

Bug 22010482.

Change-Id: I08065fc7a5cd116e50ff84cb14bbbc44c4f14bc7
      73aaf683
  3. Jun 22, 2015
  5. Jun 20, 2015
  7. Jun 19, 2015
    • Dan Zivkovic's avatar
      Cleanup before fixing getTextAfterCursor(). · 0232e73d
      Dan Zivkovic authored 
      We never delete text after the cursor, so constrain the API accordingly.
Define the number of characters to read before and after.
Set them to reasonable values.
The next CL will start caching text after the cursor.

Bug 21926256.

Change-Id: Idd58daf68614de4a69344aa3c8a4323720c5d3a0
      0232e73d
  9. Jun 17, 2015
  11. Jun 16, 2015
  13. Jun 15, 2015
  15. Jun 10, 2015
  17. Jun 08, 2015
  19. Jun 03, 2015
  21. Jun 01, 2015
  23. May 28, 2015
  25. May 21, 2015
  27. May 19, 2015
  29. May 13, 2015
  31. May 12, 2015
  33. May 08, 2015
  35. May 06, 2015
  37. May 05, 2015
  39. May 04, 2015
  41. May 02, 2015
  43. May 01, 2015