| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As CL[1] introduces diplayContext to address
IME service context's Resources / DisplayMetrics update when
switching IME window to another display after onConfigurationChange.
In LatinIME#onInitializeInterface, we only update keyboard theme context
and displayContent when the displayId is changed, but overlooked even
the displayId is the same, the display context's resource configuration
might changed like the device orientation changd.
It leads getDefaultKeyboardHeight will get wrong config_max_keyboard_height
fraction value when rotating to landcape because the context resources
didn't get updated.
Add a check to update keyboard theme context when the current display
configuation is changed accordingly.
[1]: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed
Fix: 186507147
Test: manual as issue steps
1) Turn on auto-rotate
2) Open Settings
3) Rotating the device to landscape mode
4) Tap “Search settings", verify if the soft-keyboard shown and the
size is expected.
Change-Id: I288a31baf04fa2e63d6b4a14ad81b401cb36ece5
Merged-In: I288a31baf04fa2e63d6b4a14ad81b401cb36ece5
|
|
|
|
|
|
|
| |
See https://source.android.com/setup/contribute/respectful-code for reference
Bug: 162536543
Change-Id: I5df9e60ec6caa2e1e3253532c2b59b74adfc1749
|
|
|
|
|
|
|
| |
See https://source.android.com/setup/contribute/respectful-code for reference
Bug: 161896447
Change-Id: I171bc299e660f96f20041a67a3052bd8a2ed781c
|
|
|
|
|
|
|
|
| |
See https://source.android.com/setup/contribute/respectful-code for reference
Bug: 161896447
Test: tapas LatinIME && m
Change-Id: I2ffb39ff70f61e579b62761d3da526a545dead1f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From Android Q, Talkback supports lift-to-type feature if the node claims
it is a text entry key via setTextEntryKey(). We implement this API to
show how this API is applied.
This CL uses AccessibilityNodeInfoCompat instead of AccessibilityNodeInfo
so that the same functionality can be used even on pre-Q devices when
the AccessibilityService supports it.
With that, this CL removes the legacy code of lift-to-type feature,
which was implemented in the AOSP Keyboard side.
Bug: 131644969
Test: manual - enable Talkback suporting lift-to-type,check Talback
perform click action when finger is lifted.
Change-Id: I1ec2928f5a9ba0bde999b09d4c0b9c922f179a2a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To address IME service context's Resources / DisplayMetrics update
when switching IME window to another display after onConfigurationChange.
We use Context#createDisplayContext to create display specific context when
display changed, to ensure soft keyboard can re-layout with correct resources.
Bug: 126930163
Test: manual with AOSP IME as below steps:
1) Settings > Developer options > enable "Simulated Display" & "Force desktop mode".
2) Reboot device
3) Launch app (i.e. Contacts) with bluetooth or usb mouse in Simulated display.
4) Tap EditText on app to see see if IME window layout correctly on simulated display.
5) Launch app (i.e Files) on primary display.
6) Tap EditText on app to see if IME window layout correctly on primary display.
Change-Id: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed
Merged-In: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed
|
|\
| |
| |
| |
| |
| | |
am: ff1db79a18
Change-Id: Ic162b5e20213a3f1b2aeaf77250bf1d7edc198c5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove EXTENDED_TOUCHABLE_REGION_HEIGHT from LatinIME#onComputeInsets
to prevent keyboard touch region covered navigation bar
when in split-window mode with display density < 240 case.
Fix: 134893742
Test: manual as below steps:
1) Set window density as 240 with "adb shell wm density 240"
2) Launch a app (i.e. Messages) from recents activity, set as split-screen mode.
3) Tap Search bar to show IME keyboard.
4) Press home / back / recents key if it works, expect it works.
Change-Id: I596b7276041fecc50d2bc095c7e51664f632368d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This CL demonstrates how an IME can show an Activity on the display
where the IME is shown. The key points are:
* The current display ID can be obtained as follows.
final int curentDisplayId = inputMethodService
.getSystemService(WindowManager.class)
.getDefaultDisplay()
.getDisplayId();
* When launching an Activity, specify the target display ID as
follows.
inputMethodService.startActivity(intent, ActivityOptions
.makeBasic()
.setLaunchDisplayId(curentDisplayId)
.toBundle());
Fix: 131718879
Test: Manually verified as follows.
1. Build aosp_blueline-userdebug and flash it.
2. adb shell settings put global force_desktop_mode_on_external_displays 1
3. adb shell settings put global overlay_display_devices 1920x1080/320
4. adb reboot
5. With a mouse, launch any application that has input field
in the secondary display.
6. Click that input field to bring up AOSP Keyboard.
7. Long click the comma key then select the gear icon.
8. Select "Android Keyboard Settings (AOSP)"
9. Make sure that the AOSP Keyboard Settings is launched in
the secondary display, not in the default display.
10. Go back to the step 7.
11. Select "Languages"
12. Subtype Enabler for AOSP Keyboard is shown in the secondary
display, not in the default display.
Change-Id: I9f89f371c38d9a7b5a06d018d4b41aa09815ea24
|
|\|
| |
| |
| |
| |
| | |
am: 6aed05232b
Change-Id: I558fb5ff22a7428d1d82eac82b4caba469ed48d4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This CL partially reverts
- Id88b02b74bdfe4ca05b08181ceb6b34d5652fc0c
- I05c7d8429e8d9a26139456763c77997340fea8c2
And followup (remove shortcut support)
- I73b7dc008a5acaf75a31a36a2d332b5afabd82d0
Bug: 28255684
Test: make -j10 dicttool_aosp
Change-Id: I2e01ed86b9517a1141aee35ea6d8ef39258981d1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PersonalDictionaryLookup has never been used. Usually proguard can
remove this class but it also makes it difficult to run unit tests.
We should just remove this unused class.
Bug: 111164993
Test: compile
Test: No new test failure
Change-Id: I732db94cb3aac4ed9c6b5954679b896334a12a9c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a preparation to deprecate frameworks/opt/inputmethodcommon
repository.
Currently repository 'inputmethodcommon' is used only from LatinIME.
Having such a repository only for one project is overkill. Also, to
add gradle build support to LatinIME project, it would be much easier
LatinIME didn't have such a dependency.
This CL mechanically copies files in 'inputmethodcommon' repository to
'LatinIME' repository. In theory there should be no behavior change.
Bug: 110741521
Test: tapas LatinIME && make -j
Change-Id: I3fabb038be9a944dcd9ef79ffcc89800a5f0bf5a
|
| |
| |
| |
| |
| |
| | |
Bug: 76692459
Test: mmma packages/inputmethods/LatinIME/
Change-Id: Ib76af6f6db1a0dd5cf64a06a4ea56151712e9692
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL a logical revert of a previous CL [1], which separated Java
files into common ones and overridable ones. Now that that overriding
concept is no longer used, there is no need to keep having separate
directory structure.
[1]: Ic734bd4d20aa050c688a3158b1a382ae0ac18991
fb74ab15c1343084740d65ef8744cad33a678e82
Fix: 79323502
Test: make -j aosp_taimen-userdebug && make -j
Test: tapas LatinIME && make -j
Change-Id: I2090bc25d18e6d4f24e91c2cbfe832755cbb4e8f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL introduces a custom intent action for apps to ask AOSP Keyboard to
close its software keyboard with guarding it with a signature-protected
permission.
Any app that is signed with the same signature as AOSP Keyboard can have
the following line in AndroidManifest.xml
<uses-permission
android:name="com.android.inputmethod.latin.HIDE_SOFT_INPUT"/>
to request AOSP Keyboard to close its software keyboard as follows.
sendBroadcast(new Intent("com.android.inputmethod.latin.HIDE_SOFT_INPUT")
.setPackage("com.android.inputmethod.latin"));
Test: Manually verified with a test app.
Fixes: 65270710
Change-Id: I4fd2e3a7336ec66c70582a2f274a200cbf035a7f
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
am: 947cc7d7cd
* commit '947cc7d7cd32417c016ef474889ed93114395c4e':
Follow class package change: LocaleList
Change-Id: I7e665d609267182bcfcf11e3fb309dbe9d02c830
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to avoid layering violation, LocaleList needs to be moved from
android.util package to android.os package [1]. This CL follows up that
package change.
No behavior change is intended.
[1]: Ia8de2ee9df3dd0a42b1fe84574439519b680fe18
Bug: 28819696
Change-Id: Ie795c191e299358c7c463693823f309ce61cc985
|
|/
|
|
|
|
|
|
| |
Bug introduced in 5ac4638f999db4fea8a9e24171dbceb640a10858.
Bug found by error prone:
Bug: 27723540
Change-Id: I4325f3bc1f1186bd24d4b0074f0c573cc5cb4e31
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LatinIME checks hardware keyboard presence and software keyboard
visibility to decide whether to start full screen mode.
This doesn't work well with the recent update on "Show input method"
(Bug: 22517687, Id4d332e3909590c68345e).
On the first tap, software keyboard is not shown and hardware keyboard
is connected; so full screen mode is not started. However,
onEvaluateInputViewShown may return true ant software keyboard may be
brought up.
In this care, on the second tap, software keyboard is visible so full
screen mode will be started regardless of hardware keyboard presence.
This CL checks onEvaluateInputViewShown to decide whether to start
full screen mode.
Bug: 27234709
Change-Id: I587262cc36e5fccc59620b4bd2d2c3c05c72232f
|
|
|
|
|
|
|
|
|
|
|
| |
We want to expose Serbian (Latin) layout as "sr-Latn" to the system,
while our internal logic may not be ready to deal with "sr-Latn" yet.
As a temporary workaround, we remap "sr-Latn" into "sr_ZZ" for our
internal use.
Bug: 27348943
Change-Id: I93ff0c75b3687bb1b913f451b9eb5f2820beefbc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 3e2670265e17e91c5a8cfff01711f973dccd2a0c.
It turns out that the behavior change in libcore was unintentional, and
it was already fixed [1]. Let's revert our workaround back to see if
the existing code is compatible with N.
[1]: Ibacb192abc37870c74a2500d65b94d68f9c2318e
5e7b572c2b494ab86ddd2baca3883a40a6064c1e
Bug: 26239281
Change-Id: I6cd2340492d93251231e7ee37c3d4f82c1721293
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 26239281
Change-Id: Ib30beb3548f8fb4a8e338b5da863ae28c252bc2b
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a follow up CL to the previous CL [1], in which we started
calling Window#setNavigationBarColor(int) when the window visibility is
changed.
One thing we missed is that calling Window#setNavigationBarColor(int) on
KitKant or prior devices would result in a runtime crash. Hence with
this CL we do not call that method unless the OS version is N or leter,
because specifying Color.TRANSPARENT would make sense on N+ devices.
[1]: I14d9490e00caa852035a05830e76114cbe6af8f2
6c04339c5aadb5118b0e0a8178b3d569956bbad7
Bug: 22564251
Bug: 27302540
Change-Id: Ib7299dd8c3dad4271f8fac453e690c83bda4a954
|
|
|
|
|
|
|
|
|
|
|
| |
This follows up to a recent CL [1] that removed #getPrimary() method
from LocaleList class.
[1] I75f77aea6b75e38793ed8477e5e5a4420d5e6d85
fee44846376c212114223fc4259382921e6dca7a
Bug: 26984092
Change-Id: Ied4678d35c4dcb380ce24e9bce9336dbbf6c16b8
|
|
|
|
|
| |
Bug: 23975618
Change-Id: I5933beaa5b28404f85e100461bdeab5496eb3c0e
|
|
|
|
|
|
|
|
|
|
|
| |
With this CL, LatinIME switches the current subtype from its enabled
subtypes based on the first locale in EditorInfo#hintLocales.
This functionality is still experimental, and will be triggered only
when EditorInfo#hintLocales is specified by the application.
Bug: 22859862
Change-Id: Ibd0559b370d8aa0d50d1bada8ecfdac0ed8db898
|
|
|
|
|
|
|
|
| |
This CL updates LatinIME's compatibility library so that we can access
EditorInfo#hintLocales without directly depending on unreleased SDK.
Bug: 22859862
Change-Id: I4ba7d294bc314002c3abf8842f097a4249783364
|
|
|
|
|
|
|
|
|
|
| |
With this CL, RichInputMethodSubtype#getLocale() starts returning
a Locale object that is initialized with "languageTag" when it is
specified. No behavior change is intended when "languageTag" attribute
is not available or specified.
Bug: 22858221
Change-Id: I23f2e479b8e284ce589c6950b071ba84c5dd8ce1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Starting in N, we are going to have new APIs to officially support the
situation where apps need to run before the user has unlocked their
device for the first time. For IME developers those APIs would be
important not only because IMEs developers may want to support other
apps that support that feature but also because IMEs developers have
already needed to pay attention to the same situation where the IME is
running so that the user can enter the initial password (e.g. for an
encrypted device).
Bug 11270326 is a perfect example of this scenario. Now we can disable
settings-key until the device is unlocked by using the new API when
running in Android N devices.
Bug: 11270326
Change-Id: Ie1c6efa63b60b91430f1a78dde624d0f3dff3c69
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When upgrading to a new version of APK we may find that the stored Emoji
category ID is no longer applicable. For example it happened when we
brought in the new Unicode 8.0 Emojis.
Also restore the "Symbols" emoji category on pre-kitkat devices which
was accidentally dropped when bringing in Unicode 8.0 Emojis.
b/25972978
Change-Id: I91c044603b0aac8757cb8597d3af995f84b822f3
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
am: 7674a65367
* commit '7674a653678b542d795b0bd05c241654ffe1015a':
Unicode 8.0 emoji additions to Google Keyboard.
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: e1d5012683
* commit 'e1d501268396e58bfdd37a0a50dfeb2ac48139a8':
Revert "Unicode 8.0 emoji changes to Google Keyboard."
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
am: 9cc42549d1
* commit '9cc42549d18f1e28ffc8dae94ff36728933f53f1':
Unicode 8.0 emoji changes to Google Keyboard.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change the way we decide whether we want to show on-screen keyboard by
not only paying attention to modifiers, but also keeping track whether
the key sequence started in the right state.
We are still misfiring if user presses a non-modifier key and then our
modifier hot-key, but such sequence is unlikely. Given the fact that we
do not want to store too much state I believe this deficiency is
acceptable.
Bug: 25087681
Bug: 24142161
Change-Id: I1a6b5e8e903c27a87134a6c9a7cd474a0607d5c8
(cherry picked from commit 7c513455918a52bd28c1c8181cb2880db0973b4b)
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The opaque navigation bar guard view does not make much sense when the
IME does not show software keyboard at all. LatinIME does not show
any UI when the hardware keyboard is connected.
With Iea77915ecc55eedaf19899e72c44f704ba9d852c, input method can change
the navigation bar visibility. This CL changes navigation bar invisible
when the hardware keyboard is connected.
Bug:22564251
Change-Id: I14d9490e00caa852035a05830e76114cbe6af8f2
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Squashed commit of the following:
commit 8e86347b024e2460a17264fbcaa20cd6e5fd6018
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Tue Nov 10 11:29:44 2015 -0800
Remove check for version code.
This was unnecessary and caused multi-codepoint
emoji to not show up on any device.
Bug: 25369504
Change-Id: Ia1e61c052444aaab824b18463c26b5a8066c65ed
commit 1b924816665a3a2c48307dbdd1078f61dd3179f2
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 18:12:58 2015 -0800
Fix Material icons for new tab.
Bug: 25369504
Bug: 16185905
Change-Id: I873eb9e8fc1259ac94a974c04a80a4f0d005f9c2
commit 956d5f86d2552d90d2c3240a85d5c1cddf05eda9
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 17:16:10 2015 -0800
Remove extraneous TalkBack descriptions.
Bug: 25369504
Bug: 16185905
Change-Id: Iec4f0f46cf9dda169c5827168ef207e56d619096
commit 07357bdec69b5fc118c82401d59b61ad7b802c22
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 16:01:34 2015 -0800
Better checking of whether to display new emoji.
Bug: 25369504
Bug: 16185905
Change-Id: I61f1b428e5a805f66eb4e9db346be8756fc84b8f
commit 666a92f17034f5a1948e70f40226ed995c72d81f
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 12:54:53 2015 -0800
Fix shading on emoji category icons.
Bug: 25369504
Bug: 16185905
Change-Id: I217af3d97120e7910e9850de7ea331a461ae7e56
commit 2712432c0e7a1b90ebb7ed6bde8f87eec7bf1094
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 19:06:57 2015 -0800
Add new emoji categories to Holo Blue.
Bug: 25369504
Bug: 16185905
Change-Id: Ie32af93e68e08b36a4a5861a06de511b2b190dca
commit 04c79b1f53912b263d7f7eb8b71ac802ed960a8a
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 18:06:35 2015 -0800
Fix default category, remove xxxhdpi Holo icons.
Bug: 25369504
Bug: 16185905
Change-Id: I9bca795675297dceb93777d998e8f2935f7031a6
commit 15c0b578343db2baa873096891a69305398eb830
Merge: 77bc6fc 8604ce3
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 00:59:08 2015 +0000
Merge changes into jb-ub-latinimegoogle
commit 77bc6fcfd760232757b5751993c0046f2a43626a
Merge: b0380a0 8604ce3
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 00:59:04 2015 +0000
Merge "Remove Kosovo from flags (no glyph)." into
jb-ub-latinimegoogle
commit b0380a0744647039278ad6648b7a1bc94eeab623
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 16:42:24 2015 -0800
Add icons for new emoji categories.
Bug: 25369504
Bug: 16185905
Change-Id: I1182e031994332b2e618406ad1cd467cb050766e
commit 8604ce3a34b65598101cac37a3ed3e8087fe38ca
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 16:29:33 2015 -0800
Remove Kosovo from flags (no glyph).
Bug: 25369504
Bug: 16185905
Change-Id: I92c9ace19d3600cfa1f27678ada0cf45af42d8f5
commit e0489eab47d3a6d138bfa00a668f02bcb473cf88
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 14:30:58 2015 -0800
Update emoji set to blacklist non-color glyphs.
Bug: 25369504
Bug: 16185905
Change-Id: I8b54217fa68da8ddaa1bbcd1845e0123ed106463
commit 9ffdcdff058d6b44cab70e4fb0bb301e39699483
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Wed Nov 4 17:18:22 2015 -0800
Add Unicode 8.0 emoji to emoji palette.
Currently all emoji category tabs use the flower
icon. A future CL will update these once the
icons are finalized.
If glyphs do not exist for new emoji, the old
categories will be shown.
Bug: 25369504
Bug: 16185905
Change-Id: Ie3759bfc4c8469a17f3205b45609ce6ef7510121
commit 4a4a042072790b19048a14d2ddab655b1be31a6e
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Sun Nov 1 18:38:20 2015 -0800
Add description strings for Unicode 8.0 new emoji.
Bug: 16185905
Bug: 25369504
Change-Id: I6048609ace715a23db5f82d47fefe4868ccb3d17
Change-Id: I30a043554b14531ab9cf89a1f663b6970d7d6863
|
| |/
|/|
| |
| |
| |
| | |
This reverts commit 9cc42549d18f1e28ffc8dae94ff36728933f53f1.
Change-Id: Ia3b037160e55bc54ef55194b967d9c91f6814ff8
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Squashed commit of the following:
commit 1b924816665a3a2c48307dbdd1078f61dd3179f2
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 18:12:58 2015 -0800
Fix Material icons for new tab.
Bug: 25369504
Bug: 16185905
Change-Id: I873eb9e8fc1259ac94a974c04a80a4f0d005f9c2
commit 956d5f86d2552d90d2c3240a85d5c1cddf05eda9
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 17:16:10 2015 -0800
Remove extraneous TalkBack descriptions.
Bug: 25369504
Bug: 16185905
Change-Id: Iec4f0f46cf9dda169c5827168ef207e56d619096
commit 07357bdec69b5fc118c82401d59b61ad7b802c22
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 16:01:34 2015 -0800
Better checking of whether to display new emoji.
Bug: 25369504
Bug: 16185905
Change-Id: I61f1b428e5a805f66eb4e9db346be8756fc84b8f
commit 666a92f17034f5a1948e70f40226ed995c72d81f
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 12:54:53 2015 -0800
Fix shading on emoji category icons.
Bug: 25369504
Bug: 16185905
Change-Id: I217af3d97120e7910e9850de7ea331a461ae7e56
commit 2712432c0e7a1b90ebb7ed6bde8f87eec7bf1094
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 19:06:57 2015 -0800
Add new emoji categories to Holo Blue.
Bug: 25369504
Bug: 16185905
Change-Id: Ie32af93e68e08b36a4a5861a06de511b2b190dca
commit 04c79b1f53912b263d7f7eb8b71ac802ed960a8a
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 18:06:35 2015 -0800
Fix default category, remove xxxhdpi Holo icons.
Bug: 25369504
Bug: 16185905
Change-Id: I9bca795675297dceb93777d998e8f2935f7031a6
commit 15c0b578343db2baa873096891a69305398eb830
Merge: 77bc6fc 8604ce3
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 00:59:08 2015 +0000
Merge changes into jb-ub-latinimegoogle
commit 77bc6fcfd760232757b5751993c0046f2a43626a
Merge: b0380a0 8604ce3
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Fri Nov 6 00:59:04 2015 +0000
Merge "Remove Kosovo from flags (no glyph)." into
jb-ub-latinimegoogle
commit b0380a0744647039278ad6648b7a1bc94eeab623
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 16:42:24 2015 -0800
Add icons for new emoji categories.
Bug: 25369504
Bug: 16185905
Change-Id: I1182e031994332b2e618406ad1cd467cb050766e
commit 8604ce3a34b65598101cac37a3ed3e8087fe38ca
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 16:29:33 2015 -0800
Remove Kosovo from flags (no glyph).
Bug: 25369504
Bug: 16185905
Change-Id: I92c9ace19d3600cfa1f27678ada0cf45af42d8f5
commit e0489eab47d3a6d138bfa00a668f02bcb473cf88
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Thu Nov 5 14:30:58 2015 -0800
Update emoji set to blacklist non-color glyphs.
Bug: 25369504
Bug: 16185905
Change-Id: I8b54217fa68da8ddaa1bbcd1845e0123ed106463
commit 9ffdcdff058d6b44cab70e4fb0bb301e39699483
Author: Chieu Nguyen <cvnguyen@google.com>
Date: Wed Nov 4 17:18:22 2015 -0800
Add Unicode 8.0 emoji to emoji palette.
Currently all emoji category tabs use the flower
icon. A future CL will update these once the
icons are finalized.
If glyphs do not exist for new emoji, the old
categories will be shown.
Bug: 25369504
Bug: 16185905
Change-Id: Ie3759bfc4c8469a17f3205b45609ce6ef7510121
Change-Id: Ia5a5879cea828ea4cb4c678765fe5d9e5ecbfcd2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If user has not used emojis we should not bring recents emoji tab on the
first invocation of the on-screen keyboard as it is confusing to see an
empty tab.
We will still be showing recents tab even if it is empty if user
actively switched to it when using on-screen keyboard.
Bug: 24497650
Change-Id: I68b4bf64441590858d246168cc4733a2875a1357
(cherry picked from commit 24d67eba27cb23c0d3aca44236247ec12380daa5)
|
|
|
|
|
|
|
|
|
|
|
| |
Out of the box, we want Alt-Left to toggle Emojis, while Alt-Right
toggles the shifted symbols layout.
Bug: 23954008
Bug: 24369173
Change-Id: I93dd66fb469e5d0a831359ff3a786fe68e1d73ea
(cherry picked from commit 411841b374aa04e333ea5a438dfd539f49ec589a)
|
|
|
|
|
|
|
| |
Bug 23900149.
Change-Id: Iff8a3892bb88f82736e5fa680c38d98cda4d2777
(cherry picked from commit e1641395e30de7b53b06fc5c820ea83bf04b3aad)
|
|
|
|
|
|
|
|
|
|
|
| |
Check to see if setup wizard is running before showing toast to
inform user that a download was started. Note that this will only
affect the device owner; when adding new users later, the toast
will still appear. (The USER_SETUP_COMPLETE flag is hidden from
the SDK, while DEVICE_PROVISIONED remains available.)
Bug: 22594336
Change-Id: I57c42d6f821714b71cbb066e82bba2a1dbab4951
|
|
|
|
|
|
| |
Bug: 23082844
Change-Id: I7baac5e5a0700280906fd0f5f9351fc8dfc4c2b3
(cherry picked from commit 990e9a75b6d88ba234131612f11eac6b69c1cf84)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This build has been compiled against API 23
This build is approved to go out with the M OTA, but may NOT be released
to the public until the Play Store has enabled API level 23 apps
Version: 4.1.2300x.build_id
1. Disable the settings.
2. Disable the feature.
3. Force reload the facilitator.
Bug: 22564048
Change-Id: Ic09742786c3e4efc034bceee836ae6a1e07307a1
(cherry picked from commit 031d04192080f0368f21c3371d1ec6af87375357)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This build has been compiled against API 23
This build is approved to go out with the M OTA, but may NOT be released
to the public until the Play Store has enabled API level 23 apps
Version: 4.1.2300x.build_id
1. Replaces the personalization is on information with the suggest
contacts.
2. Enables "Use Contacts" only if the app has permission to read
contacts.
3. Disables the contacts dictionary in the Facilitator.
4. Do not register/read the contacts in the contact observer.
Bug: 22236416
Change-Id: I9674e13d0d0f4a2014c5024fde0178de684c07e7
|
|
|
|
|
|
|
|
|
|
| |
FileUtils is being used for other non android projects
and hence breaks when built. Instead use the log statements
at caller to record Log.e messages. Hence there is no side
effect here.
Bug:22042371
Change-Id: Ieb100006ff38e013bc30542637465f58bfc0f2f2
|