[TIMOB-2891] Android: instances of "Can't open keycharmap file" seen in output
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2017-06-07T22:33:56.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android |
Labels | android, keycharmap |
Reporter | Thomas Huelbert |
Assignee | Ingo Muschenetz |
Created | 2011-04-15T03:32:11.000+0000 |
Updated | 2017-06-07T22:33:56.000+0000 |
Description
[INFO] Titanium SDK version: 1.6.0 (01/19/11 08:23 aa8c451) sim or device, exists in 1.5.1. noting behavior.
one way to see it:
1.Controls > checkbox > switch
2. tap swicth ro checkbox, then back out a level and check
output
W/KeyCharacterMap( 1663): Can't open keycharmap file
W/KeyCharacterMap( 1663): Error loading keycharmap file
'/system/usr/keychars/qtouch-touchscreen.kcm.bin'.
hw.keyboards.65538.devname='qtouch-touchscreen'
W/KeyCharacterMap( 1663): Using default keymap:
/system/usr/keychars/qwerty.kcm.bin
This is a general message. Moving to future just in case. I don't think it's titanium related.
This blocks display of the searchBar in 1.5.1 and 1.5.2 using Android 2.2.
W/KeyCharacterMap(10864): Can't open keycharmap file
W/KeyCharacterMap(10864): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65538.devname='qtouch-touchscreen'
W/KeyCharacterMap(10864): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
Keyboard shows for textareas, etc.
Searchbar has been working fine on device until this warning started to appear.
Never mind. Resolved with clean build.
Problem.
Customer gets the next error W/KeyCharacterMap( 206): No keyboard for id 0 W/KeyCharacterMap( 206): Using default keymap: /system/usr/keychars/qwerty.kcm.binSample Code:
Helpdesk
APP-478348This ticket was added so QE wouldn't report a non-issue. It is a warning from the Android OS.
Closing ticket due to time passed and lack of work.