| Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Idab5d09722e584c5ffcc5ff574c28bcbbf729aa5
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I352b26ea8bf0231df70390d717acd2d1d594b1c5
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I38b91f6946820fcaa1f28323085f54676ce12615
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I32470cb45f56eb8bdc8f2b2e055e649d34c5e7f3
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I2d3706b2fa62b1f3b561db60763e895910b1cbbc
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I714e7c7937c2377d86ee7f2a514117d0255f4761
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I096be536dd6bf947ea5c2d2adb37a905a790027f
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Id00265bae5aa6cd705f6b685dc5482cf28be48ef
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I8cc15dd237c6e8313d997b37829b7924e2bb9c6a
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I5de46104c83a4d2efc933d473ec29e19c18684c4
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I70c1aad8f2ad45a20eb55fee33619a3f4e319939
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I27597dd25043d3dd0b14a7e3a359a2b15f35164d
|
|
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
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I5a1e14997b62527fe4b7c902855c999e06fee399
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I28ede254065c4491af0c8f82f724e1f83d5a8c69
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Icf4d8be7d9322b87d1d2eebe55c6b7d270f47a2b
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I582cc100421d415defcd817a96191f6608eea8ad
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ibd1ea3ad66df1032a70a90f0f38df532b1f8e7a2
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ia43a2ac5c29cef680fb4e44ef12da74176726b3b
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I3dee70ec398ce7e6f4bfb4b677a97153906a9b19
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I4a2e1950cd5eff7f1a64b023a15ec591f43b13c0
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I3ffc9f82edaa14bc34372a9107e71e834a494c57
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Id5f69f9696d57630083976b6e0b438409fc8b59e
|
|
Change-Id: I904d86d309ea2d7f9580b5e09dca41bfb60cff40
Auto-generated-cl: translation import
|
|
Change-Id: I1d2df81d65ab959a10b2de2988384f8fb75715af
Auto-generated-cl: translation import
|
|
Change-Id: I142d2d3f4b1426baab015fb8d915bb40d0de16d7
Auto-generated-cl: translation import
|
|
Change-Id: I3636200116fa13979c6414f7d9d427f460d10b72
Auto-generated-cl: translation import
|
|
Change-Id: I08d454ae10fb1013bdf04bdece7a0d9b04862681
Auto-generated-cl: translation import
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I6539176814c71b06abe32ee6b8205f9500ed50f9
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I7437c061744c3a3ff86c6b476ac1a87525fc74d8
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I37bb584aec85ed5299a8033b75b81b330a2ab783
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ic1c492d7ebd6718099bc2b12f3daed09596218cd
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I5d712356e5bc9cc77bbaa3a1f65ecdef6284b4a8
|
|
Change-Id: I4f02f5f4ccc6ff864fb5120dc7766755fb773fcf
Auto-generated-cl: translation import
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I2b984642494033f59d02cf4c640793b47e63c6b3
|
|
Change-Id: I48a6f3055d8dd3182ff98a6edace3a4e35b4326d
Auto-generated-cl: translation import
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I7809654384cc42e87999e222316e25f4bd70641f
|
|
Change-Id: Icdaeac3123fef5ca97a44cc155d4f428138ae985
Auto-generated-cl: translation import
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I136d94f85222806b5104a16b6d544dc1c377c5e3
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I6e496165fde5ea66dda1559f39a0c02c949265b0
|
|
Change-Id: Iaaf42624b7933d8a479a9eea71aedbc3711de6cb
Auto-generated-cl: translation import
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ied44fc2e6b9256a6744387ca511946b21fd44524
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I9edb7e3ebf58bdf8fe5b12096c37815e58a39e40
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I05cf27d7d1a197dde37d6dc69433c26e62c88458
|
|
Change-Id: I3962401c95664f199216b443e27bf07871b20d07
Auto-generated-cl: translation import
|
|
Change-Id: If684531601502dce2fa4c0fe36a1af2086226faa
Auto-generated-cl: translation import
|
|
This is a follow up CL to my previous CL [1], which enabled us to test
Direct-Reply with EditTextVariations.
What this CL does are:
* Specyfing min_sdk_version to avoid INSTALL_FAILED_OLDER_SDK error
when installing on older devices.
* Avoiding NoSuchMethodError on pre-O devices where
Notification.Builder does not have a constructor that takes
notification channel.
* Fixing a race condition where notification can be sent before
notification channel is created.
[1]: Iafffcc7d138b0f502116a5e557f0c3f17e9d0b73
da2486fd63d7d46e982d0e2fb2eba3dac07aff32
Bug: 122957841
Test: Made sure that we can install EditTextVariations on N devices
and "Direct-Reply" on EditTextVariations works there.
Change-Id: Ib4fbd447608b111e763fde4287226cf7e206e65e
|
|
Change-Id: I58ea73335befe5324077a7775c4ff78f04ed1a4b
Auto-generated-cl: translation import
|
|
Change-Id: I09408d72060cc69d3734647abe7969528539c1cc
Auto-generated-cl: translation import
|