| Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ic2f680a72dc473a3ea9e63ba2781519c0bb0d189
Auto-generated-cl: translation import
|
|
Change-Id: I52324e9458f9b928e2827ea70097b0eb93054467
Auto-generated-cl: translation import
|
|
Change-Id: I9b10a94aff23f6ea9158bc5a62ac044c99002777
Auto-generated-cl: translation import
|
|
Change-Id: Ib5d118c530a2f1a8a7671dcd5e5c3b77526b2582
Auto-generated-cl: translation import
|
|
Change-Id: Ic8c8b74c22d74c43897762200e7b0c925ce1e5c0
Auto-generated-cl: translation import
|
|
Change-Id: I35067db3dbae5228b51d48383eae67eba48a6717
Auto-generated-cl: translation import
|
|
Change-Id: I8735b7149146b06e4f2df15c746c24ca83b97b94
Auto-generated-cl: translation import
|
|
Change-Id: I25500c09630cd8037896424a30086207d489467b
Auto-generated-cl: translation import
|
|
Change-Id: I15b1a2d1ad1b939ef39ef2484f779668c54a1bf8
Auto-generated-cl: translation import
|
|
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
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I576eae018336f225d9e6c9dce6eaba6742ce9581
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ie12258d268be80afd21cf01c8fb2c32d5d522ecb
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I3dd765cbdc830f4e9d4f3dd8495f56a28d8938ba
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Iae08b9b0a5055f1c29a678764af6d2f3c849d5ec
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ib15edbefa78b413711bc9a114c035e4f042029d8
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I5d3e002b9c8b5b9163674ee55b0a78c86d7a4367
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I613207e83ccb3a460ea770af79796d4addc01839
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I4a08d8777d4cd8f487a7dfd197e5722b6931232c
|
|
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
|