Nexus One: The returned keyboard has the wrong width! Keyboard width: 320, device width:480

[GoogleCodeExporter]

when running logcat on my device (Nexus One)
I get the following logs entries which indicate some kind of problem with 
the resolution the keyboard is expecting:

D/AnySoftKeyboard(  152): onFinishInput()
D/AnySoftKeyboard(  152): updateSuggestions: has mSuggest:true, 
isPredictionOn:false, mPredicting:false, mCorrectionMode:2
W/InputManagerService(   92): Window already focused, ignoring focus gain 
of: com.android.internal.view.IInputMethodClient$Stub$Proxy@463eb598
D/dalvikvm(  152): GC freed 2204 objects / 114328 bytes in 191ms
D/AnySoftKeyboard(  152): onStartInput(EditorInfo:0,0, restarting:false)
D/AnySoftKeyboard(  152): updateSuggestions: has mSuggest:true, 
isPredictionOn:false, mPredicting:false, mCorrectionMode:2
D/AnySoftKeyboard(  152): Alphabet keyboard width is 320, while view width 
is 480. Recreating.
D/AnySoftKeyboard(  152): About to create keyboard: eng_keyboard
W/AnySoftKeyboard(  152): NOTE: The returned keyboard has the wrong width! 
Keyboard width: 320, device width:480
D/AnySoftKeyboard(  152): AnyKeyboard.setImeOptions
D/AnySoftKeyboard(  152): setTextVariation
D/AnySoftKeyboard(  152): Changing smiley key to smiley.
D/AnySoftKeyboard(  152): Changing question mark key to question.
W/AnySoftKeyboard(  152): NOTE: The SET keyboard has the wrong width! 
Keyboard width: 320, device width:533
D/AnySoftKeyboard(  152): setShifted: shiftState:false. result:false

is that a problem? I may be wrong but I think the keys are not rendered at 
high resolution as it seems like the default keyboard keys look a lot more 
crisp.

Thanks...
   --Mor

What steps will reproduce the problem?
1. Nexus One
2. adb logcat
3.

Original issue reported on code.google.com by mor.himi on 2 Mar 2010 at 1:47

• Blocking: #257

[GoogleCodeExporter]

On Motorola milestone there is the same issue.

Original comment by francisc...@gmail.com on 2 Mar 2010 at 8:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I had similar issue on HTC Tattoo,
which caused the keyboard view to be truncated, when changed orientation from
portrait to landscape, see screen shot attached.

I found a fix for this issue, a dirty one, but works.
In file AnySoftKeyboard.java, line: 250
i changed this line: mKeyboardSwitcher.makeKeyboards(false);
to this one: mKeyboardSwitcher.makeKeyboards(true);

This causes the keyboard to be recreated, and it's created with correct width.

Original comment by Str3...@gmail.com on 7 Mar 2010 at 12:12

Attachments:

• Screenshot-5554:tattoo.png

[GoogleCodeExporter]

The guys with Nexus and Droid, do you have the truncated keyboard problem 
Str3l0k
reports?
@Str3l0k, you are using the latest version?

Original comment by menn...@gmail.com on 7 Mar 2010 at 2:30

[GoogleCodeExporter]

Hi,

actually I don't have the truncated keyboard issue.
however when in numbers only keyboard view, its clear that the numbers are not
rendered for high resolution displays.

Thanks...
   --Mor

Original comment by mor.himi on 7 Mar 2010 at 3:58

[GoogleCodeExporter]

I think so.
The screen shot posted above, is the code from svn trunk running on emulator,
which also occurred on the real htc tattoo device.

The fix i posted above, works very well for me, i was afraid
it will cause a delay when changing orientation, but it's fast as usual.

Original comment by Str3...@gmail.com on 7 Mar 2010 at 7:25

[GoogleCodeExporter]

I think our problems unrelated, for me it printed the following in the log cat:

W/AnySoftKeyboard(  152): NOTE: The SET keyboard has the wrong width! 
Keyboard width: 0, device width:480

Sorry, i don't have more logs.
But if you want, i can revert to original version, and paste more logs.

Original comment by Str3...@gmail.com on 7 Mar 2010 at 7:27

[GoogleCodeExporter]

@mor, the rendering problem is unrelated, please open a new issue about this.
Also, beside the Log lines you pasted in the first comment, do you experience 
any
problem?

@Str3l0k, could you revert to the original version (or to the lasted version in 
the
SVN), and reproduce it and attach the logs here?

Thanks.

Original comment by menn...@gmail.com on 7 Mar 2010 at 7:38

[GoogleCodeExporter]

Here are the logs.
Strange thing though, when i installed the latest version, after removing the 
fixed
one, it worked good, no problem where found. i had to revert to nandroid backup 
to
the state where i didn't have anysoftkeyboard installed at all, then install the
latest version to reproduce the problem.

Original comment by Str3...@gmail.com on 8 Mar 2010 at 8:19

Attachments:

• logcat.log

[GoogleCodeExporter]

Original comment by menn...@gmail.com on 13 Mar 2010 at 9:04

• Changed state: Started

[GoogleCodeExporter]

Please try now:
http://softkeyboard.googlecode.com/files/AnySoftKeyboard_20100313.apk

It seems that I forgot a flag. I believe it should not display this message 
anymore,
and the keyboard should look even better in hi-res devices (like nexus).

Original comment by menn...@gmail.com on 13 Mar 2010 at 6:07

• Changed state: HaveSolution

[GoogleCodeExporter]

Using the latest version I don't see that warning anymore.

Thanks!

Original comment by mor.himi on 14 Mar 2010 at 9:36

[GoogleCodeExporter]

And how is the rendering?
Does the fonts seems crispier?
And the keys?

Original comment by menn...@gmail.com on 14 Mar 2010 at 9:54

[GoogleCodeExporter]

the rendering looks better in all views except for the "Numpad Like" view where 
all
the numbers looks very ugly ( like they were resized from x to 2x ).

Original comment by mor.himi on 14 Mar 2010 at 12:45

[GoogleCodeExporter]

OK.
You are right, the images were created for mid-resolution devices.

Original comment by menn...@gmail.com on 14 Mar 2010 at 12:47

• Changed state: Fixed