Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IME crashes when using US International hardware keyboard #248

Closed
GoogleCodeExporter opened this issue Apr 22, 2015 · 6 comments
Closed

IME crashes when using US International hardware keyboard #248

GoogleCodeExporter opened this issue Apr 22, 2015 · 6 comments
Labels
auto-migrated OpSys-Android Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 


Version: 1.15.1785-3-arm

Steps to reproduce:
1. Attach USB hardware keyboard to phone
2. Set keyboard layout to US, International style
3. Select a text input field, Japanese IME opens
4. Press the ` key  (on US International style, this is used also for entering 
diacritics)

Expected result:
The character ` is displayed

Actual result:
Crash with below stack trace


09-13 14:16:24.802  2559  2559 E AndroidRuntime: FATAL EXCEPTION: main
09-13 14:16:24.802  2559  2559 E AndroidRuntime: Process: 
com.google.android.inputmethod.japanese, PID: 2559
09-13 14:16:24.802  2559  2559 E AndroidRuntime: 
java.lang.IllegalArgumentException: Invalid code point: -2147482933
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
java.lang.Character.checkValidCodePoint(Character.java:1551)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
java.lang.Character.access$100(Character.java:100)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
java.lang.Character$UnicodeBlock.of(Character.java:1512)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
com.google.android.inputmethod.japanese.c.e.f(SourceFile:410)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
com.google.android.inputmethod.japanese.MozcService.onKeyDown(SourceFile:820)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.view.KeyEvent.dispatch(KeyEvent.java:2640)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.inputmethodservice.AbstractInputMethodService$AbstractInputMethodSession
Impl.dispatchKeyEvent(AbstractInputMethodService.java:136)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.inputmethodservice.IInputMethodSessionWrapper$ImeInputEventReceiver.onIn
putEvent(IInputMethodSessionWrapper.java:213)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:185)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.os.MessageQueue.nativePollOnce(Native Method)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.os.MessageQueue.next(MessageQueue.java:138)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.os.Looper.loop(Looper.java:123)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
android.app.ActivityThread.main(ActivityThread.java:5001)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
java.lang.reflect.Method.invokeNative(Native Method)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
java.lang.reflect.Method.invoke(Method.java:515)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
09-13 14:16:24.802  2559  2559 E AndroidRuntime:    at 
dalvik.system.NativeStart.main(Native Method)
09-13 14:16:26.392   775  7834 I WindowState: WIN DEATH: Window{4380a2e0 u0 
InputMethod}

Hardware: Nexus 5 'hammerhead'

Build: KTU84P
Build fingerprint: 
'google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys'
Bootloader: HHZ11k
Radio: msm
Network: NTT DOCOMO
Kernel: Linux version 3.4.0-gd59db4e (android-build@vpbs1.mtv.corp.google.com) 
(gcc version 4.7 (GCC) ) #1 SMP PREEMPT Mon Mar 17 15:16:36 PDT 2014

Original issue reported on code.google.com by c...@daydream.org.uk on 13 Sep 2014 at 5:51
@GoogleCodeExporter
Copy link
Author 

Thank you for the report.

Matsuzaki-san, can you take a look?

Original comment by yukawa@google.com on 15 Sep 2014 at 2:33

@GoogleCodeExporter
Copy link
Author 

Taken.

Original comment by matsuza...@google.com on 15 Sep 2014 at 1:43

@GoogleCodeExporter
Copy link
Author 

Status update:
We are not able to reproduce this issue yet.  The stack trace indicates that 
you are receiving an unexpected code point "-2147482933".  Are you using a 
custom keymap file on your device?  If so, can you tell me what keyboard layout 
is selected on your device?

Original comment by yukawa@google.com on 18 Sep 2014 at 2:49

@GoogleCodeExporter
Copy link
Author 

OK.  Now I'm able to reproduce the reported issue reliable.  Seems that the 
original report lacked some important steps.

Steps to reproduce:
1. Flush KTU84P to Nexus5
2. Install Mozc 1.15.1874.102 (r328)
3. Attach USB US hardware keyboard to phone
4. In the system hardware keyboard settings, Choose "English (US), 
International style" (see the attached screenshot: 
system-hardware-keyboard-layout.png)
5. In the Mozc hardware keyboard settings, choose "System Default" (see the 
attached screenshot: mozc-hardware-keyboard-layout.png)
6. Select a text input field
7. Press the ` key

Original comment by yukawa@google.com on 20 Sep 2014 at 5:21

  • Changed state: Started

Attachments:

@GoogleCodeExporter
Copy link
Author 

Note that this is not specific to Android 4.4.  I can reproduce this issue on 
Android 5.0.  Updated the summary accordingly.

Original comment by yukawa@google.com on 19 Dec 2014 at 7:07

  • Changed title: IME crashes when using US International hardware keyboard

@GoogleCodeExporter
Copy link
Author 

This issue was closed by revision r463.

Original comment by yukawa@google.com on 21 Dec 2014 at 2:46

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated OpSys-Android Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter