element.
Several files associated with a future CL contain extra whitespace.
I've made a separate CL here to avoid inflating the "changed lines"
count within this future CL.
Change-Id: Ie8199abd2a61b77d0fb349435983050e0e06afc7
Abandoned-Change-Id: I92f75ba0ef08e10210434f824fd99caee3703b5e
Introduced new error codes so that Instrumentation can
include the correct message in the exception.
Bug: 28216630
Change-Id: I93ee77153cdad11fa208c74c28c6790db27c9753
am: 7ecd767
* commit '7ecd7671b75b2ae7c4d20928722b4a1d41bd62ff':
Delete emojis before and after ZWJ at the same time.
Change-Id: Icd274fe183f211a5488169852f90c8ad23be6b6c
BatteryStats uses a mix of microseconds and milliseconds, and keeping
which one is which straight is difficult. The internal bookkeeping
is left using us where it already does, for the extra precision. But
having the API be mixed will only make it harder for developers, and
lead them to make the same mistake that I did in the API where I
missed some conversions.
Bug: 28197858
Change-Id: I99114bae259b9bdd47ce5c22e724d87bbd63336d
am: 9c211a3
* commit '9c211a339689a2e54da3315ccdbf22add472c76a':
Work on issue #28221912: Starting service as foreground might...
Change-Id: Id0001c009bd4fc70d0aa34647171763aa0990d08
am: adfa806
* commit 'adfa806cfbd6ad51fe3ec8c4cea808ebd2967038':
Ignore user serial numbers in core-only mode.
Change-Id: I461d11b28027773b080c6e996faf540f22c67204
- When picking up a task view to dock it, we should animate remove the
dim on the task view so that when you drop it, there is no jump from
the dimmed version to non-dimmed app.
Bug: 27154882
Change-Id: Ifa1493227593dd950e49650b69f178cef82bc82e
When booting in core-only mode, our data partition is a tmpfs which
doesn't support xattrs, so we can't set/enforce user serial numbers.
Bug: 28254840
Change-Id: Id83c551c7c603a4cd5043e06f7161441b2dfaa8b
am: 20e84c7
* commit '20e84c750f7ef783344f9890764906e20b0df822':
Fixed a rebase gone wrong with pageindicator
Change-Id: I08bfc4b3c0cb3a8159645c7ff6d017daa8db6c9e
am: 0529197
* commit '0529197e9df8837ac63b011937391ff29426e6b5':
Use adjusted popup window position when calculating best-fit
Change-Id: Ib6688f23f3bf86519fcada8c274c2e2462e8d201
Google TTS currently does not support language auto-switching.
Also, not all languages are available in TTS at all times.
This means that TTS cannot properly handle text in other languages / scripts
than the current language.
Languages with different scripts would not be read at all, and the others
would be read with "bad pronunciation", to the point of being unrecognizable.
This change is not a full fix, but makes things slightly better by using
the default locale for the contentDescription in the language / region lists.
This might be a bit unsettling, as the label will not match the sound.
The label will show "Deutsch" or "Русский" and text-to-speech will say "German"
or "Russian" (for English UI), or "Allemand" or "Russe" (if the UI is French).
Might also say nothing, if the current UI language has no text-to-speech engine.
But this is the best we can do, and better that what we get if we do nothing.
Bug: 28087937
Change-Id: I7390a063708647e022be29161c2f2bedc19896ae
