am: 4b91148
* commit '4b91148b3d2d3126cb5463f4401d651af7f0206f':
Remove fullstop at end of phrases
Change-Id: I22eb5096a610569007e09fe5b7f3e96fdfe5c2af
am: bd5eb13
* commit 'bd5eb1331ecc741bae84b1d1093c5102877f36b9':
Remove fullstop at end of phrases
Change-Id: I79391dfad9814397dc6276ffb70042ba67a0543a
am: 6cd645a
* commit '6cd645a4879c58fb19a1a9713088c31c652e7b35':
Mark UI components for tests to find.
Change-Id: I8f0075afaccbcf7ec718bc09c847eb3e23860b27
am: 9069181
* commit '9069181c847168896c6fac97e8869944c97f0f2e':
Mark UI components for tests to find.
Change-Id: Ie822df10d4a0c64727f46a29fbb6e07e366de702
am: fb43d8d
* commit 'fb43d8d1002dce58ec7ed4dfe9f7dc62b3b29d2e':
Revert "Fix no keyboard on N builds"
Change-Id: I6be5e343e3ce25fdcd8cb3e66b8e0f77e3265801
am: 3ace856
* commit '3ace856ed788349f1e8e343fc6fb4e3bc2a26033':
Revert "Fix no keyboard on N builds"
Change-Id: I622451e204e0277d9190c6c3ab72b6595b47f6c6
This reverts the previous commit [1] since the keyboard shows up without
such a workaround. Presumably someone might have fixed something in
somewhere.
[1]: Ifd588bf7db76f9ea5d6a90854f8e92f86f4c2910
250faf9243.
Bug: 25942488
Bug: 26190615
Change-Id: Ie0e0ead960473a3504fc88a4f7d4d18108ef0e18
With ag/899084 TextView no longer automatically sets the
LinkMovementMethod when setText is called with a ClickableSpan.
So in LinkTextView we do that manually instead.
Bug: 27973982
Change-Id: I86626bd71bf2ca41cb7e73d479ba764e809b0190
am: ea4ca2e
* commit 'ea4ca2e09622610d3ee0cfbfc5405949e7d00e4d':
MVNO value is not grayed out when MVNO type is none
Change-Id: I7f492f1cf5aea400ac0a6df719975be531e1b48d
am: e652b7b
* commit 'e652b7b0cade699a396f55602f5d7a282466c705':
MVNO value is not grayed out when MVNO type is none
Change-Id: I12079a64d44b8578d258ef0afd4391b53016c709
MVNO type is judged as none by comparing key string to "None",
but this logic does not work when language setting is non English
because key is not "None" due to translation.
Bug: 27267663
Change-Id: Ic39a084cd77f661f833b13106dc28444926487d8
Bug: 27927402
Also add a TabLayout to show title for these fragments, inspired by
http://goo.gl/aOt51Q
Change-Id: I40bab3075480670558ac9a896337109f10e8c90c
- Added "wifi-only" option to the list of wifi calling modes.
- Added code in settings initialization to check whether the carrier
supports including the wifi-only option. If it does not, changes the
entries/values to a ser which does not include the wifi-only option.
Bug: 27858149
Change-Id: Ib02a97afcf6f2722c28b7a4d9c241774944c52d0
The root cause of crash bug #27749932 is that the state mismatch between
when a Loader is created and when the Loader object finishes background
task. We can easily reproduce this crash by:
1. Pair two hardware keyboard A and B.
2. Open Physical Keyboard settings.
3. Press the power button to turn off the display.
4. Move keyboard A far away so that it is unpaired.
5. Press the power button to turn on the display.
6. Unlock the device.
One of the reasons PhysicalKeyboardFragment was unstable is that loader
ID reuse. PhysicalKeyboardFragment starts background data loading
because of many events such as #onResume() and #onInputDeviceAdded() but
there are chances that loader ID was reused because we specified
hardware keyboard device index as the loader ID. This was dangerous
also because device index can change when a device is added and removed.
With his CL each loader object has an unique ID and
PhysicalKeyboardFragment keeps tracking the list of active Loader IDs
only from which PhysicalKeyboardFragment should accept data.
Also, this CL removes dependencies on PhysicalKeyboardFragment from each
loader object so that we can have a clear boundary of responsibility
between data loader and data consumer.
Bug: 27749932
Change-Id: I53fcb2426d028a492c775bb2b4ec6a5419e33bb4
