Want to Change the Smiley Key to Curly Apostrophe - T-Mobile Sidekick 4G

Hi, All,
With a rooted Sidekick 4G, I'd like to change the Smiley key to a smart-quote-style apostrophe. This thread is very helpful:
http://forum.xda-developers.com/showthread.php?t=1242993
but in \system\usr\keylayout\s3c-keypad.kl, I'm still lost. Does anyone know--using hex or text editor--the proper syntax for a curly apostrophe to take the place of SMILEY? (in advanced ascii, the code for a curly apostrophe is 92, but that doesn't seem to help in this matter)
Many thanks,
Jake

Related

Relocating smiley key on stock keyboard

I am attempting to relocate the smiley key to the comma key on the stock ICS keyboard.
I have located the smileys in strings.xml in the IME, but cannot find the location of where the long press key commands originate so I can move the function.
Can anyone help?
Thanks
Andy

[Q] Typing at Sense Home screen

Typing at home Sense screen do not find contact with accented character.
For example, if i type "beo", it does not find "béo"
How dumb is that!
Well the "e" and accented "é" are two different characters. It searches by looking for the string you search. Admittedly it makes it quite a simplistic search system, but you can see the logic behind it.

Can you edit the default text smileys?

I was wondering if it was possible to edit the default smileys when you press the smiley button on the keyboard. (I don't mean the actual graphic picture of an android character, but the actual text itself). I'd like to be able to change it so instead of the smiley being ": - )" it would be ": )" or "= )", so it DOESN'T show an android character, and it doesn't have the goofy dash nose. My phone is rooted, and I've been looking around in Root Explorer, but can't find where this would be (if its as simple as editing a few lines of text). I use Swiftkey, but I think it uses the same exact smileys. Help please?

Change default text smileys?

I am currently running: Rooted CM7 Tickerguy Edition on Motorola Triumph
I was wondering if it was possible to edit the default smileys when you press the smiley button on the keyboard. (I don't mean the actual graphic picture of an android character, but the actual text itself). I'd like to be able to change it so instead of the smiley being ": - )" it would be ": )" or "= )", so it DOESN'T show an android character, and it doesn't have the goofy dash nose. I've been looking around in Root Explorer, but can't find where this would be (if it's as simple as editing a few lines of text). I use Swiftkey, but I think it uses the same smiley file. Help is appreciated!
Bump

LG Optimus F3Q (D520) and remapping its hardware keyboard

The LG Optimus F3Q (D520) is a phone with "Five-Line Slide-Out QWERTY Keyboard with PC-Like Shortcuts" (LG website). Missing from the keyboard however, is the "Ctrl" key. This brief guide shall attempt to show how an arbitrary key may be remapped for it.
Root the phone. Saferoot by k1mu works for this phone, although I found that the phone did appear to hang should one try to reboot or power off using the hardware power button after rooting. Removing and replacing the battery boots up the phone without issue should that happen. Software-based rebooting works fine.
Install your favourite file explorer for root users. ES File Explorer File Manager worked well for me.
On the phone, navigate to the "/system/usr/keylayout" directory.
Make a copy of the "f3q-keypad.kl" file and put it somewhere safe in case you need to revert to it.
Edit the "f3q-keypad.kl" file using a text editor.
Look for the line "key 100 ALT_RIGHT WAKE_DROPPED". This corresponds to the fn key on the right side of the keyboard.
Replace "ALT_RIGHT" with "CTRL_RIGHT".
Exit the file and save. View it again to verify that your changes have been saved.
Reboot.
Try it out. Ctrl-C should work in a terminal emulator.
To have even greater control over the remapping, you would also need to edit the "f3q-keypad.kcm" file in the "/system/usr/keychars" directory.
Note! If you are using connectbot, please obtain at least version 1.8.1 from connectbot at GitHub. Version 1.7.1 of connectbot in the Google Play store did not recognise the Ctrl command when I tried. Thus, it may be possible that some other programs may also not recognise the Ctrl command.
Disclaimer: I mucked around a lot by trial and error as version 1.7.1 of connectbot was tripping me up, so I had changed a lot more things than what I had listed in the steps above. However, looking back at it, I doubt that any other changes I had made were truly necessary.
Helpful stuff:
appelflap has a button remapper app, which I installed, but didn't appear to be able to do what I wanted. However, the KeynrTracker.apk he linked is very helpful should you very quickly want to know which key corresponds to what.
References:
Key Layout Files
Key Character Maps Files
List of Unicode characters
Other thoughts:
I found Link2SD and Foldermount [ROOT] to be indispensible for this phone.
Thanks! I just might try replacing that pesky write and share app key with CTRL...
It would satisfy a request of mine for my F3Q ROM.
EDIT: Downloaded the app. Because pressing the key pushes the app to the background, it won't capture.
Last line of the file though says "WRITE_SHARE". Think I got somewhere.
Sure did, "WRITE_SHARE" now replaced with "CTRL_LEFT", and is working like a charm!
Glad this helped somebody !
joel.maxuel said:
Thanks! I just might try replacing that pesky write and share app key with CTRL...
It would satisfy a request of mine for my F3Q ROM.
EDIT: Downloaded the app. Because pressing the key pushes the app to the background, it won't capture.
Last line of the file though says "WRITE_SHARE". Think I got somewhere.
Sure did, "WRITE_SHARE" now replaced with "CTRL_LEFT", and is working like a charm!
Click to expand...
Click to collapse
Keth Tenderfoot said:
Glad this helped somebody !
Click to expand...
Click to collapse
how to deal with sticky keys?
Polish keyboard mapping on F3Q
Hi, I'm sharing my .kcm and .kl files of the F3Q used with the Polish characters mapped to the respective keys.
(Note to the German users of F3Q: you might edit my f3q-keypad.kcm file ,and map your äöüß characters to the aous keys, if you feel like having your language version of the mapping.)
Keyboard allocation modifications:
SEARCH key mapped to TAB
WRITE_SHARE key mapped to CTRL_LEFT
ALT_RIGHT key mapped to CTRL_RIGHT
PL layout: [ęąółżźćń] mapped on ctrl+[eaolzxcn]
PL layout: [„] mapped on ctrl+[k]
PL layout: [”] mapped on ctrl+[,]
The files have to replace /system/usr/keychars/f3q-keypad.kcm and /system/usr/keylayout/f3q-keypad.kl respectively to be active.
Hallo Pruszków,
Thanx for your polish Keymaps, great work!!!
At the moment I try to modfy them to German. It works fine so far, but now my question is, how can I use the right "fn" key (which is the new ctrl/alt key) without pressing at the same moment as the vowel/consonant, which I want to modify? With the left "fn" key I can first press the button, then release it and it holds its function.
Do you know what I mean?
Would be fantastic, if there is a solution too!
Best regards & dziękuję,
sÖren
fn/alt or ctrl?
Hi Sören,
Thanks for sharing your feedback. I'm glad my stuff could be of some help to you!
spacemoere said:
how can I use the right "fn" key (which is the new ctrl/alt key) without pressing at the same moment as the vowel/consonant, which I want to modify? With the left "fn" key I can first press the button, then release it and it holds its function.
Click to expand...
Click to collapse
Well, the "fn" labeled key was originally associated with the "alt" behavior. The "alt" keeps its mode when you press and release it. But I mapped the right "fn" to the "ctrl" bahavior, and... "ctrl" works just when you press and hold it. So, what to do in your case?
You might get back to the original "fn' mapping (in the .kl file) and keep the right "fn" as "alt", and then define äöüß (in the .kcm file) in combination with "alt" instead of "ctrl".
But...
there is a challenge with the special characters already mapped to the keys. E.g. let's take the key "u". Originally "alt" and "u" prints "+". When you'd map "alt" and "u" as "ü" then you'd loose any possibility to get "+". I have no good idea how to resolve that well. Maybe you'd map "+" to: "ctrl" and "u"? Then you'd use "ctrl" only from the key 59 (CTRL_LEFT), as the key 100 you'd map back to ALT_RIGHT.
The bottom line is: you'd need to choose between "alt" and "ctrl" stuff when deciding your settings.
In my case I took "ctrl" for my Polish mapping, as I'm used to press and hold the "fn" to print the Polish characters. If you're used to press and release, to print a German character, you might consider using "alt" instead.
I hope this helps.
Tschüs,
Bernard
Remapping IME
Thank you for the post Keth, very easy explained.
I am wondering about modifying not the standard character map, but the LG Keyboard IME.
I could not find any alternative input method with a good support for physical keyboard and good dictionaries, so I thought it may be better to modify the included input method than using a different one, correct me if I am wrong.
So I extracted the LGEIMEbin.apk from the system/apps directory, and opened it on the computer to figure out how to modify it.
Keyboard layout are saved in XML, so I supposed it should be easy to modify with a text editor like Notepad++, and just say for every key or combination of keys what kind of character do I want.
Well, I was wrong, as the xml do not contain any clear structure that is in any way possible to understand as it was for f3q-keypad.kcm and f3q-keypad.kl.
I tried to open all kind of xml files included in the LGEIMEbin.apk, and all of them presented non recognised characters, as you can see in the picture that can be found at this address:
img4web.com/i/D3RC42.png
Has anybody any hint of why notepad++ does not recognise those characters and how could I correctly visualise them?

Categories

Resources