This is a follow up to 0708d9e119. The setHasOptionsMenu has
to be set for the back button to work and this needs to happen
regardles if the fragment has an help uri or not.
Bug: 28237921
Change-Id: Icec7a94312bdab5470efa0893a339d753c995eb1
When an app is blacklisted, its switch toggle is disabled, but previous
the onClick() method was still being called, which would launch the data
usage screen but also call setIsWhitelist().
BUG: 27481520
Change-Id: Id8df3d65eee286d1aecb4ae2a0417d6932d91441
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: I54d49ec96a10bab3e31198e162230fb277426e66
When user blacklists an app for background data access, the
"Unrestricted data access" list should not display the whitelist toggle
option, but rather explain background access is turned off and offer the
option to open the app's data usage screen to turn it back on.
It still does not handle changed received by DataSaverBackend, so the UI
will be stale when the user removes a blacklist and navigates back to
the list.
BUG: 27481520
Change-Id: I9d0fa9f0180a69ce9bd1417921bf89ec3ba31f01
The background thread is not stopping listening fast enough and is
resulting in first a receiver leak message followed by a crash when
trying to finally unregister the receiver.
Fix this by adding a registerReceiver to SummaryLoader that will
automatically unregister the receiver on the main thread to ensure
it happens in time.
Change-Id: I0104e929d5505eb53993f6765e4c90120df35cf6
Fixes: 28211606
am: fb9ff81
* commit 'fb9ff81d2d43986190c640f8a77f3fa722214ae8':
Use IME service logo or icon if exists.
Change-Id: Iefd60417a51e1536695649eeb35ebf0546f1a35c
am: bd06816
* commit 'bd068163e36ed470a34655025cd01324540ab6e2':
Use IME service logo or icon if exists.
Change-Id: Idf451086fba5e3cf8d31fe5904564340c482711a
am: bd06816
* commit 'bd068163e36ed470a34655025cd01324540ab6e2':
Use IME service logo or icon if exists.
Change-Id: I32e04748622bae27482639510b2269f0210ed5b9
am: 08f6425
* commit '08f64254c8c308d41147f078bff5fb1b996406a2':
Set the minimum speech rate to a value of ten instead of zero.
Change-Id: Iad560acc24cc59e18533c9d28a3f844e8df12e6c
am: c01beed
* commit 'c01beed396e24b689708fcb7a979a07108818426':
Set the minimum speech rate to a value of ten instead of zero.
Change-Id: I5bd59b771e81981b035e261dfd3181dc6d2f737b
am: 8852b82
* commit '8852b823a41df9340b8fa8a84ee577dbef9e244b':
Set the minimum speech rate to a value of ten instead of zero.
Change-Id: I56be44e770a536c0ee41019e6864d41ceccf1fd0
am: 8852b82
* commit '8852b823a41df9340b8fa8a84ee577dbef9e244b':
Set the minimum speech rate to a value of ten instead of zero.
Change-Id: I4cc345757114c28e04cdd5b9f9f72ea31e3d549f
