b12smurf / acer-liquid-community-rom-bugtracker

Automatically exported from code.google.com/p/acer-liquid-community-rom-bugtracker
1 stars 1 forks source link

HTC_IME landscape fullscrean is not working in LCR-F 2.0 #260

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
!!!PLEASE WIPE BEFORE POSTING A BUG!!!

What steps will reproduce the problem?
1. I installed latest Froyo 2.2 OS_Acer4.002.14
2. I Installed Froyo LCR-F 2.0 via Malez Recovery (working fine)
3. Select HTC_IMEmod as keboard; Uncheck "No landscape fullscreen" (checking it 
does not change anything). 
4. i.e. use "Dolphin mini" or "android-hilfe.de"-app (or any other, other than 
the Google search bar widget) and type something in landscape mode.

What is the expected output? What do you see instead?
I expect the text field to use up the whole screen that is not occupied by the 
keyboard itself. (similar to 
http://fs01.androidpit.info/userfiles/30778/image/pics/snap20100516_104027.png) 

What is the bin file you are using ? (0.010, 0.014, 0.016, 1.100...)
OS_Acer_4.002.14.EMEA.GEN1_Pass_A1.bin (md5 ok)(Acer Liquid 256mb)

What version are you using ?
LCR-F_2.0-signed.zip (md5 ok)

What patch or addons pack have you installed ?
No.

If you use LCR 1.7 or LCR-F 1.1 attach le file LCR_UI.txt stored on your
sdcard or
answer :
|THIS_CONF_MUST_BE_APPLIED| ?? |
|RECOVERY| ?? |
|FULL_UI_ACER| ?? |
|FULL_UI_ANDROID| ?? |
|STATUS_BAR_AT_THE_BOTTOM| ?? |
|NOTIFICATION_TYPE_STREAM| ?? |
|STREAM_NOTIFICATION_ON_TOP| ?? |
|DIALER_TYPE_STREAM| ?? |
|LOCK_TYPE_STREAM| ?? |
|LAUNCHER_TYPE_STREAM| ?? |

Where are stored your apps (phone/sd default is phone) ?
phone

Where is stored your dalvik-cache (phone/sd default is phone) ?
phone

Where are stored your datas (phone/sd default is phone) ?
phone

Did you wipe dalvik ?
Yes

Did you wipe data (factory reset)
Yes

Please attach a log made with sendlog or log_debug tool (see wiki)

Please provide any additional information below.
There is not change when using the default keyboard.

Original issue reported on code.google.com by the.m...@googlemail.com on 7 Feb 2011 at 8:52

Attachments: