Due to the addition of input language switching, the auto dictionary
will be re-created very frequently. We need to save it and restore it
during transitions, otherwise the data will be purged too often to be
of much use in the multi-lingual case.
This also fixes the case where a user frequently turns the phone off/on.
Auto dictionary data was not being saved in those situations either.
The dictionary will probably never grow too large since most of the
frequently used words will be moved to the user dictionary any way.
Also, now the input locale is different from the display locale, so
save the input locale in the UserDictionary class and insert words
into the user dictionary with the correct locale.
And NPE fix for bug: 2464573
The last change did not solve the bug completely, the spinner was still shown at times when no initialization dialog was shown
Change-Id: I43a5f8df4e333ffb6deb727c3bf45ed7b7a54069
This increases the chance of hitting the correct letter when typing a word
that exists in the dictionary, rather than only correct it after the fact.
It is most effective after 2 or 3 letters of a word have been typed and gets
more accurate with more typed letters in the word.
If 2 adjacent letters have similar probabilities of occuring, then there is no
hit correction applied.
Now there is a delay each time the voice recognition screen is opened, however, this is the correct behavior as microphone setup takes about 600ms.
The previous implementation, although being fast, was not actually recording the first 1/2 second of user's speech.
Change-Id: I8b8373a59658502f7451150ff4a4ffd1c8e83205
Shows the language on the spacebar and in the preview bubble. Allows
dragging of the spacebar from side to side to switch to previous or
next languages.
This CL now simply moves LatinIME to use the version of
LoggingEvents in android-common, rather than duplicating
the LoggingEvents class between VoiceSearch, Browser, and
LatinIME.
I also added in a TIMESTAMP to the START broadcast, so that
we would be able to evaluate if various events happened
after a user tried Voice Input.
Change-Id: Ic88ff40fcedf707abc3c5eb2e68dfd0fcdef3701
Open-sourced platform code shouldn't refer to Gservices. Use the
platform-standard Secure settings table instead (which we can still
push values into from the servers on google-experience devices, like
gservices), but can be populated by other mechanisms for non-ged
phones.
Change-Id: Id0b5830bfc78c1d10dc732dce46546cd09cd1422
Microphone button can be optionally moved to the symbols keyboard
to get your comma back. You can also completely disable voice input.
Now you can get your comma back but still use the swipe gesture to
activate voice input.