LatinIME container height too small

by Joerie » Mon, 27 Dec 2010 23:13:02 GMT


Sponsored Links
 Hi,

I'm having some trouble with the (revamped) LatinIME keyboard on 2.3 -
it's height is somehow incorrect. In both portrait and landscape mode,
it displays at roughly 1/5th of the screen height (whereas I'd expect
it to be ~50%). The width is fine, spanning the full width of either
portait or landscape mode.

- The Japanese IME displays fine, which - I suppose - isolates the
issue to being somewhere in the LatinIME
- My screen size is 480x800, and I've set ro.sf.lcd_density
accordingly (240).

Has anyone got an idea where I should start looking?

Joerie

-- 



Other Threads

1. MediaPlayer Breaks in FroYo

I have an mp4 from youtube that I'm trying to stream. It works
perfectly in Android 2.1, but in Android 2.2 it reports a http 303
error. But If I dump the headers of the file, it reports a 200 (OK).
Any Idea why the new mediaplayer in 2.2 would report this error, when
everything works fine in 2.1?

Here's a example:

CODE
-----
url = "http://www.youtube.com/get_video?
video_id=FyljLIeajbs&t=vjVQa1PpcFNBUUHnpqWCySeF0h3BP-
xLlLPqbumzoBk==&fmt=17";

mp.reset();
mp.setDataSource(url);
mp.prepare();

RESULT IN ANDROID 2.1
---------------------
Song streams correctly, as usual

RESULT IN ANDROID 2.2
----------------------
05-26 04:22:36.087: INFO/StagefrightPlayer(33):
setDataSource('http://www.youtube.com/get_video?
video_id=FyljLIeajbs&t=vjVQa1PpcFNBUUHnpqWCySeF0h3BP-
xLlLPqbumzoBk==&fmt=17')

05-26 04:22:36.407: ERROR/HTTPDataSource(33): HTTP request failed w/
http
status 303

05-26 04:22:36.407: INFO/AwesomePlayer(33): mConnectingDataSource-

05-26 04:22:36.447: ERROR/MediaPlayer(265): error (1, -1004)

05-26 04:22:36.447: WARN/System.err(265): java.io.IOException:
Prepare
failed.: status=0x1

-- 

2. XML imageBlob to drawable?

How do I convert an XML imageBlob to a drawable?

Thanks,
 Mike

-- 

3. How to get the soft keyboard input with out edit text?

4. Penampakan Froyo untuk Hero

5. Salam kenal dari newbie

6. Making the Account API better

7. Paging desire user