Hi all,
I was trying to modify the ActionMenu that pops up when you slide the querty out. This is on a HTC S740, but I suppose it would be the same for all HTC devices with a slide out keyboard. My intention was to edit it in a way that option nr. 3 (messenger) brings up a different messenger than WLMessenger, as I never use this one.
My findings so far are that the information to the links are stored in a dll called ActionMenu in the windows folder. I was able to open it with notepad, however editing the path for the messenger somehow broke the whole dll so ActionMenu won't pop up at all anymore when sliding the keyboard open. I also tried editing it with XN Resource Editor, but there nothing is displayed. So for now I am at my wits end.
Maybe someone else could help out here? Would truly be appreciated.
Regards,
.-ombre-.
Dll is a compiled library and therefore a binary file... If you would like to edit it this brute way you should use hex editor and only REPLACE links. That means, new link must have the same lenght as the old one and none of bytes should be moved. Then obviously, final file must have the same size as the old one.
Anyway, then it mustn't work either.
yeah, thats something I tried in the meantime and no, that doesnt work either..
Oh well..
Iv'e been at this sense last night and haven't gotten anywhere! Its getting frustrating so i decided to try and branch out for some advice.
Im using an LG Optimus V with Bobzhome Cynagenmod 7, I am trying to get my ThinkOutside Universal BluTooth Keyboard to work a little more like it should with my device. It will pair and connect no problem and all the keys work, Its just that some of them don't work the way there suppose to.
Ive been trying to get my Ctrl Esc and < > keys working properly. The resources ive been using are
Cant post the links becuase im a new user, but its a blog about the kl and kcm.bin files and an android dev page about porting KBs and writing drivers for them.
Anyways i'm basically just editing the /system/usr/keylayout/qwerty.kl file, by using nano from the command line from debian on the phone. Nothing i seem to do works it either totally breaks the keyboard totally or it just doesn't anything. My file is just the basic qwerty.kl right now and i added a line that says
Code:
Key 29 VOLUME_DOWN
Im using a program on my phone to get the KeyCodes and ScanCodes from my keyboard. Im sure 29 is the right scancode for my Ctrl key. Once I edit the qwerty.kl reset the phone and reconnect and pair the KB the ctrl key still comes up ass scancode 39 keycode 0 when i press it, which is what it was before i wrote the new file.
i know there also the kcm.bin file but im not sure what that does, im under the assumption thats only for editing the shift and alt modifiers for key right?
sorry mods for bringing up this thread after so long, i'm facing a similar problem and would like to know what's the
program on my phone to get the KeyCodes and ScanCodes from my keyboard
Click to expand...
Click to collapse
please.
Thanks in advance
Hi,
I've installed CM7.2 on my RHOD but the layout of HW keyboard is wrong. How can I change it to us layout?
Cheers,
Tom
It should 'detect' your keyboard layout.
Do other NAND ROM's have this issue?
I'm not sure, only NAND I tried was the CM7.2
_eph said:
I'm not sure, only NAND I tried was the CM7.2
Click to expand...
Click to collapse
At least give OMGB a shot...
Although, IIRC CM7.2 from Mr. Walter detected my keyboard no problemo. I'm sure we can get the right one shoehorned in, I'm just curious if it happens to you on other ROM's.
Ok, I've tried OMGB. The layout of normal letters/numbers seems to be correct but the function keys seem to be broken. Fn types @, Ctrl lights up the FN led but doesn't act like Fn, arrows are wrong (up is left, right is up, left is down, down is left).
Any more ideas?
Thanks
You could try copying the keyboard map file from the rom that worked to the one that didn't.
_eph said:
Ok, I've tried OMGB. The layout of normal letters/numbers seems to be correct but the function keys seem to be broken. Fn types @, Ctrl lights up the FN led but doesn't act like Fn, arrows are wrong (up is left, right is up, left is down, down is left).
Any more ideas?
Thanks
Click to expand...
Click to collapse
You never even stated which RHOD you have... I kind of assumed "US" layout meant one of the US RHOD's, but it sounds like you have something different.
So which one is it?
wizardknight said:
You could try copying the keyboard map file from the rom that worked to the one that didn't.
Click to expand...
Click to collapse
CM & OMGB were the only android roms I tried. Keyboard didn't work properly with neither of them. I used haret with win6.5 rom before. Can I use keyboard map from win rom?
_eph said:
CM & OMGB were the only android roms I tried. Keyboard didn't work properly with neither of them. I used haret with win6.5 rom before. Can I use keyboard map from win rom?
Click to expand...
Click to collapse
WM and Android are totally different. Haret and nand android will probably work ok though.
arrrghhh said:
You never even stated which RHOD you have... I kind of assumed "US" layout meant one of the US RHOD's, but it sounds like you have something different.
So which one is it?
Click to expand...
Click to collapse
I've got RHOD110 (got it in New Zealand).
The 100's have a awful time with issues, and you have an odd subset of that. No wonder you are having trouble.
You will probably have to make your own keyboard map.
_eph said:
I've got RHOD110 (got it in New Zealand).
Click to expand...
Click to collapse
wizardknight said:
The 100's have a awful time with issues, and you have an odd subset of that. No wonder you are having trouble.
You will probably have to make your own keyboard map.
Click to expand...
Click to collapse
This ^^.
I think someone might've made a layout for F22's rootfs - you can poke around there and re-use it perhaps. Otherwise, you will have to make your own layout. There's really not many with the 110, at least not interested in this project... so the layout isn't solid. I think the 100 still has layout issues with the FN and CAPS key as well.
arrrghhh said:
This ^^.
I think someone might've made a layout for F22's rootfs - you can poke around there and re-use it perhaps. Otherwise, you will have to make your own layout. There's really not many with the 110, at least not interested in this project... so the layout isn't solid. I think the 100 still has layout issues with the FN and CAPS key as well.
Click to expand...
Click to collapse
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
_eph said:
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
Click to expand...
Click to collapse
One nice thing about NAND, the files are easily edited before flashing.
For example, CM7.2.0-RC1-rhodium-GSM-kernel-3.3.6-201200523.zip\system\etc\keymaps\ is where the keymaps are.
I'm not sure which one your device is getting mapped to... and I'm also unsure of what you need to do to get yours detected properly. Sorry I can't really help more...
_eph said:
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
Click to expand...
Click to collapse
http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html
arrrghhh said:
One nice thing about NAND, the files are easily edited before flashing.
For example, CM7.2.0-RC1-rhodium-GSM-kernel-3.3.6-201200523.zip\system\etc\keymaps\ is where the keymaps are.
I'm not sure which one your device is getting mapped to... and I'm also unsure of what you need to do to get yours detected properly. Sorry I can't really help more...
Click to expand...
Click to collapse
I am having the same problem of an incorrect HW Keyboard layout on GBX0* + 3.4.17 kernel - update 11/7/12 using a UK Rhod 100. In system/usr/keylayout/ the qwerty.kl file is correct and can be editted and the changes persist after a reboot. I was able to map the end call key to home.
However the microp-keypad.kl file which contains the keymap for the HW keyboard is incorrect and matches the default layout in system/etc/keymaps/default. Any changes made to this file have no effect and after a reboot the files changes back to the default one. The files I need are in system/etc/keymaps/rhod100_uk. i have also tried editing the default layout files with no success. Again after a reboot they revert to the original files.
I had a similar problem with the CM7.2 NAND ROM. While using the 2.6.27 I was able the use the correct keyboard layout however after flashing a kernel update to 3.3.6 the keyboard layout was incorrect (and was the default layout).
I am unable to find any .kl files in the GBX0 zip and therefore I am unable to make any changes prior to flashing.
Thanks all those still developing for the Rhod.
akk29 said:
I am having the same problem of an incorrect HW Keyboard layout on GBX0* + 3.4.17 kernel - update 11/7/12 using a UK Rhod 100. In system/usr/keylayout/ the qwerty.kl file is correct and can be editted and the changes persist after a reboot. I was able to map the end call key to home.
However the microp-keypad.kl file which contains the keymap for the HW keyboard is incorrect and matches the default layout in system/etc/keymaps/default. Any changes made to this file have no effect and after a reboot the files changes back to the default one. The files I need are in system/etc/keymaps/rhod100_uk. i have also tried editing the default layout files with no success. Again after a reboot they revert to the original files.
I had a similar problem with the CM7.2 NAND ROM. While using the 2.6.27 I was able the use the correct keyboard layout however after flashing a kernel update to 3.3.6 the keyboard layout was incorrect (and was the default layout).
I am unable to find any .kl files in the GBX0 zip and therefore I am unable to make any changes prior to flashing.
Thanks all those still developing for the Rhod.
Click to expand...
Click to collapse
GBX0* is a different rom than CM7.2, and will have many files in a different place. You would be better off making a new thread, or posting the the thread for that rom.
I see that this issue has now been tackled in the ROM development thread. I will download the new package. (Sorry I was unable to post in that thread)
Methods tried thus far:
Have tried the ServiceMode menu by dialing *#197328640# and looking in debug menu for network lock but network unlock menu is missing.
Have flashed with a stock 4.1.2 image
Have tried adb and scouting around for pin codes as per this method but no bml5.img file.
trying this
adb
su
cat mmcblk0p14 >> /sdcard/mmcblk0p14
exit
exit
pull /sdcard/mmcblk0p12
Click to expand...
Click to collapse
found this with a hex editor
Broadcom rhea_ss_nevisp board
chosen pinmux !21654B1-pinmux
with some interesting encoded text after this:
eg:
L L C
possibly related to the system on a chip
Broadcom BCM2835 GPIO (and pinmux) controller
mmcblk0p17 has this string
++++556764!&%%.//012223.//0122233321+$
mmcblk0p4 has this string
0000644.0001751.0001751.000000007054.12123752176.013126. 0.........
ubuntupunk said:
Methods tried thus far:
Have tried the ServiceMode menu by dialing *#197328640# and looking in debug menu for network lock but network unlock menu is missing.
Have flashed with a stock 4.1.2 image
Have tried adb and scouting around for pin codes as per this method but no bml5.img file.
trying this
found this with a hex editor
Broadcom rhea_ss_nevisp board
chosen pinmux !21654B1-pinmux
with some interesting encoded text after this:
eg:
L L C
possibly related to the system on a chip
Broadcom BCM2835 GPIO (and pinmux) controller
mmcblk0p17 has this string
++++556764!&%%.//012223.//0122233321+$
mmcblk0p4 has this string
0000644.0001751.0001751.000000007054.12123752176.013126. 0.........
Click to expand...
Click to collapse
still no answer
ubuntupunk said:
still no answer
Click to expand...
Click to collapse
just acquired the same phone, got the same problem
polite bump
please help!
I have same problem. no reply from anyone here, looks like il have to buy a code from fastgsm.
Still no solution...
How to unlock rooted S6810?
i got the samee issue
Hi Mate !
same here
i hope u found a solution ! i pm u if its allright
ubuntupunk said:
Methods tried thus far:
Have tried the ServiceMode menu by dialing *#197328640# and looking in debug menu for network lock but network unlock menu is missing.
Have flashed with a stock 4.1.2 image
Have tried adb and scouting around for pin codes as per this method but no bml5.img file.
trying this
found this with a hex editor
Broadcom rhea_ss_nevisp board
chosen pinmux !21654B1-pinmux
with some interesting encoded text after this:
eg:
L L C
possibly related to the system on a chip
Broadcom BCM2835 GPIO (and pinmux) controller
mmcblk0p17 has this string
++++556764!&%%.//012223.//0122233321+$
mmcblk0p4 has this string
0000644.0001751.0001751.000000007054.12123752176.013126. 0.........
Click to expand...
Click to collapse
For the sake of giving this old question an answer, and for any future reader (if there is any), I'll say that:
RegionLock Away works for this device (and also the Lite variant, GT-S6790L)
Hey guys,
My pen input has stopped working and I was investigating max1187x_pen_ file and there was just "# Device Type
touch.deviceType = touchScreen" and nothing more. Can someone please open the file in system/use/idc an check the values for me?
gabsporto said:
Hey guys,
My pen input has stopped working and I was investigating max1187x_pen_ file and there was just "# Device Type
touch.deviceType = touchScreen" and nothing more. Can someone please open the file in system/use/idc an check the values for me?
Click to expand...
Click to collapse
Mine doesn't have values either, but my pen input works. Maybe reflash the ROM?
RealityFails said:
Mine doesn't have values either, but my pen input works. Maybe reflash the ROM?
Click to expand...
Click to collapse
Thanks for that,
Yes, it might be the case I guess. I upgraded to Lollipop and spend a week using only fingers, when I tried pen it didn't work anymore.