After installing the latest version of RandomROM Thunderhawk today, my keyboard isn't functioning properly at all. Whenever I open it, random characters enter the text box and pressing keys causes it to enter strings of characters uncommanded. Anyone else having this issue?
Related
I found something out guys...
I'm on JG1 but with the JFF CSC which apparantly fixes the swype bug.
All was working fine, however when I was typing a long sms (which turns into an mms after 3 pages 0_0 never knew that), the phone recommended to me to change the "input mode" to "automatic.
So I went into messaging > settings, and changed "input mode" to "automatic. Suddenly the swype bug was back...
Changed "input mode" back to "gsm alphabet" and all was working again.
So I have a suspicion that the swype bug is caused by "automatic" input mode, which is probably the default mode for JG1 CSC. On the other hand I suspect that the automatic input mode for JFF CSC is "gsm alphabet".
If my suspicions are correct.. then you can fix JG1 swype bug without firmware flash, by changing the input mode to "gsm alphabet".
Anyone try?
Genious,
Thank you!
I just updated to JG1 yesterday to install the Modaco rom. Swype not working was really annoying me!!
Recently installed Swype ver. 2.4.44.XXXX (had a previous version of swype prior, so installation is correct)
-keyboard shows up
-everything works, but the Swype style typing (leaves Swype trail, but words do not show up in text box)
-also letters and words show up if typed like a regular keyboard
Any suggestions or solutions?
That's a symptom of a non-authorized beta installation. Although, annoyingly, my official beta copy has a tendency to de-authorize every now and then, requiring a reinstall/Titanium backup restore.
Hi:
After working correctly from awhile (some weeks) with Aurax ROM (8.4) I started to have the following issue:
- Suddenly the phone reboots; when using Google Navigator, Dolphin, or any action i a non regular way.
I re-flash the rom => didn't help
I re-format the SD (default one, 4GB) => 1 day without rebooting, however I cannot tell if it's finally fixed.
In order to solve this issue, one of the things I did is S-OFF (alpharev), and after doing this I started to have the other following problem:
- The Menu key is acting like if I press "HOME+Vol-up" together! (weird)
- The trackpad is acting like if I press "Vol-down" !
I didn't have this issue before, just happend after making S-OFF, I don't know if it's a coincidence or something else "confused" the keys.
Can you help me on this please? Any clue?
thanks
SCesar
I just installed Condemned's CM7 V1.4 from 3/4, and it appears that the CM feature of "Stop app via long-press" is not working for me. I noticed this on a previous CM7.2.0 Kang a few weeks ago (can't rememeber who's), restored an even earlier CM 7.2 Kang backup, and it was working again. Can anyone else confirm this?
If it helps, when I press the back button I get the following logcat entries:
Can't open keycharmap file
Error loading keycharmap file '/system/usr/keychars/atmel-touchscreen.kcm.bin'. hw.keyboards.65537.devname='atmel-touchscreen'
Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I get the same entries regardless of whether I have the option checked or not. Thanks in advance for any thoughts/ideas.
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
xlJohnnyIcelx said:
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
Click to expand...
Click to collapse
How about you try to flash back to the stock rom using the lg flash tool?
I fixed it with a work around. I used exposed additions to force haptic feedback and also to map the q button key. Hopefully if anyone else has this problem it will help them.