I recently obtain a Desire Z and immediately rooted and installed various ROMS. All is working great.
The problem is the hardware keyboard is a qwertz one (I bought the phone in Switzerland) and not a qwerty one. I want to the switch the keymap around such that z prints y and vice versa. I've set the keyboard setting to UK and US English but it has no effect on the h/w k/b.
I'm familiar with adb but don't know which files to hack on. Please can someone point me in the right direction?
Thanks!
the hardware keyboard layout is fixed.
the setting in menu is only changing the software keyboard.
Thanks for the reply.
But I don't buy it. This can be changed somehow and someone knows how. I'll keep hacking and post back with any useful results.
I have a sneaking feeling that it should be able to be cooked in. Even on Winmo, you can change your keyboard's layout, i don't see why android, a platform that is much more advanced, would not be able to do that.
This is just a hunch, but you probably just need to modify /system/usr/keylayout/vision-keypad.kl and possibly /system/usr/keylayout/qwerty.kl (they're both plain text files, but with unix line endings)
On a UK QWERTY Desire Z:
Key 21 is Y
Key 44 is Z
If your files have them round the other way, it should just be a simply case of swapping them and rebooting (nandroid first though!)
Great. I tried those files and no good so I went for the heavy handed approach after mounting system as rw and su'ing:
cd /system/usr/keylayout
sed -i s/Y/--/ *
sed -i s/Z/Y/ *
sed -i s/--/Z/ *
Job done! Thanks for your help
For the almost-beginners:
Connect your phone in sync-mode, run cmd, navigate do adb directory (search forum for adb if you didn't get it) and type:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/usr/keylayout
sed -i s/Y/--/ *
sed -i s/Z/Y/ *
sed -i s/--/Z/ *
Best regards to all
DRuMah said:
For the almost-beginners:
Connect your phone in sync-mode, run cmd, navigate do adb directory (search forum for adb if you didn't get it) and type:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/usr/keylayout
sed -i s/Y/--/ *
sed -i s/Z/Y/ *
sed -i s/--/Z/ *
Best regards to all
Click to expand...
Click to collapse
shall be rooted to run these?
am getting access denied!!!!!11111
Well obviously you need root to write to /system/ partition.
DRuMah said:
For the almost-beginners:
Connect your phone in sync-mode, run cmd, navigate do adb directory (search forum for adb if you didn't get it) and type:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/usr/keylayout
sed -i s/Y/--/ *
sed -i s/Z/Y/ *
sed -i s/--/Z/ *
Best regards to all
Click to expand...
Click to collapse
Hi, I've tried this on my Desire Z and it indeed switched the 'y' and 'z' character keys on the hardware keyboard.
The downside is that is also changes the corresponding FN symbols (i.e. number six character '6' and underscore character '_').
Do you know wether it is possible to switch the letters but not the symbols?
I don't know about the symbols. My guess is you have to live with it. I do. Yes, it's annoying but IMO about 10% as annoying as the original problem.
I would also add that on ICS, the above changes b0rked the keyboard (probably due to the sed script replacing stuff it ought not have). So I used this instead:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/usr/keylayout
sed -i s/'key 44 '/'key XX '/g *
sed -i s/'key 21 '/'key 44 '/g *
sed -i s/'key XX '/'key 21 '/g *
adb reboot
If I have to do this one more time, I'm going to make an app.....
In the end I managed to fix the symbols by editing some hex file I can't recall right now. I can check it out later and post what I did if anyone is interested.
Couldn't come up with a simple command like yours though, and edited it by hand by downloading to the PC and uploading after modification. It can probably be done using regular expressions, but they are not my biggest strength
Good job I'm certainly interested. If you could post specific details that would be great!
Cheers.
Sorry for the delay, but I've had quite a busy week...
The file that I modified was /system/usr/keychars/vision-keypad-ger.kcm.bin My phone was bought from Germany, so if you have a different region phone the specific file you need to edit might be a different one.
I edited it on Windows with xvi32 hex editor (GHex on Ubuntu works fine as well), and the nice thing about it is that you can see the hexadeciman values on the left and their ASCII counterparts on the right. It was quite easy to find the sections 'yY__' and 'zZ66'. You only need to change those to 'yY66' and 'zZ__' and voilá.
If you already have your 'y' and 'z' keys swapped (but the symbols out of place), you should changed change the '6's and '_'s. If you have the letters on their original positions you should then change the letters instead, and the symbols will stay where they are.
Hope that helps.
Great job
little help
migueluli said:
Sorry for the delay, but I've had quite a busy week...
The file that I modified was /system/usr/keychars/vision-keypad-ger.kcm.bin My phone was bought from Germany, so if you have a different region phone the specific file you need to edit might be a different one.
I edited it on Windows with xvi32 hex editor (GHex on Ubuntu works fine as well), and the nice thing about it is that you can see the hexadeciman values on the left and their ASCII counterparts on the right. It was quite easy to find the sections 'yY__' and 'zZ66'. You only need to change those to 'yY66' and 'zZ__' and voilá.
If you already have your 'y' and 'z' keys swapped (but the symbols out of place), you should changed change the '6's and '_'s. If you have the letters on their original positions you should then change the letters instead, and the symbols will stay where they are.
Hope that helps.
Click to expand...
Click to collapse
hi. how you manage to change permission of file vision-keypad-ger.kcm.bin ?
I tried with adb, it's not working.
needubad said:
hi. how you manage to change permission of file vision-keypad-ger.kcm.bin ?
I tried with adb, it's not working.
Click to expand...
Click to collapse
You need to mount the /system partition as rw to be able to modify that file. You can do that with
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
while logged as root in the adb shell.
If you already did that and are still unable to modify the file then I'm afraid I cannot be of much help
I'd like to do an oposite thing: QWERTY --> QWERTZ
for us, noobs, could someone please simillar commands for this operation?
thanks in advance
HoradricCZ said:
I'd like to do an oposite thing: QWERTY --> QWERTZ
for us, noobs, could someone please simillar commands for this operation?
thanks in advance
Click to expand...
Click to collapse
... for noobs you'd think you would just flip the placement of Z and Y.
Related
READ BEFORE TRYING
I am cdma hero user and it works very well for me. This should work on gsm hero. I pulled this from HERE, it was for the Milestone Android phone which is a GSM phone.
Before enabling
*Change home laucher
*Delete htc lock screen
see below if you dont no how
Jit does not work with htc sense, it will give you many problems. I suggest using Helix launcher from market (free and its what i use daily with no issues). You can also try GDE and nexus launcher, or really anything other then sense.
To change launchers go to setting>applications>manage apps>htc sense And clear defaults. Press home and choose a different launcher.
OR download "Home Switcher" from market.. Its a free app that lets you change between launchers.
JIT does not like any HTC apps.. So delete your HtcLockScreen by doing this.
Code:
adb remount
adb shell rm /system/app/HtcLockScreen.apk
Here is the htc lock screen if you want it back
HtcLockScreen
JIT is in no way perfect on our htc hero's so MAKE A BACKUP before trying.
And you could very well run into TONS of problems, its just something to test out.
Though if used right, you wont have any problems. I use this daily.
THIS IS FOR JIT
Download: *View attachment vmlibs.zip*
Then follow these steps:
•Create 2 folders on your sdcard: “jit” & “dalbk”
•Extract the vmlibs.zip to the “jit” folder on your sdcard
•Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad or similiar program.
•Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Save the changes and move it to the directory c:/
•Push it back to your “jit” folder on the sdcard
Code:
ADB push C:\build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit.
Code:
ADB shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
WIPE DALVIK CACHE AFTER ENABLING JIT.. This will cause your phone from sometimes going into a boot loop.
You dont have to wipe your whole phone.. Only dalvik cache. Your phone will take awhile to reboot since its rebuilding dalvik. Be patient. If it eventually freezes then reboot and it should go through fine after that.
TO DISABLE:
This should disable JIT and return phone back to defualt
Code:
adb remount
adb shell
su
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
Post For help if the disabling gives you any problems.. If it does you can always do back up of your rom that you should of made.
Original site http://sholes.id.au/how-to/
Awesome.. I really hope that some of the hero devs can optimize this for the hero.
madsborelli said:
Awesome.. I really hope that some of the hero devs can optimize this for the hero.
Click to expand...
Click to collapse
I am hoping this also. Most devs dont work on things like this, or know enough about it to fix it.
The only real problem I have had was using htc widgets, htc sense, and htc lockscreen. When I use other home screens, and delete the htc lockscreen, I can run error free with JIT enabled.
Jus10o said:
I am hoping this also. Most devs dont work on things like this, or know enough about it to fix it.
The only real problem I have had was using htc widgets, htc sense, and htc lockscreen. When I use other home screens, and delete the htc lockscreen, I can run error free with JIT enabled.
Click to expand...
Click to collapse
Can you feel the difference in speed?
madsborelli said:
Can you feel the difference in speed?
Click to expand...
Click to collapse
Everything is really instant. I clicked and then closed and clicked and closed multiple apps on my screen and it never hung up or lagged.
Before jit, it was pretty quick but every once in a while would slow up on opening or closing, or switching apps specialy when recieving a call or text at the same time.
One example is. Before jit I was using the yellowpages app with voice command and it would take forever loading voice and then entering what i said into the text box. I tested with jit and it was all pretty instant and never paused or lagged after multiple test.
I posted this on cdma hero and this hero, it gets alot of views but no one seems to actually been trying it and posting about it.
I would like to know what kind of improvements its makes from JIT disabled and JIT enabled for other people.
I understand you all have completely different roms so the numbers can't be directly compared. But the improvement between stock and JIT should show some resemblance from my rom and gsm roms.
Jus10o said:
I posted this on cdma hero and this hero, it gets alot of views but no one seems to actually been trying it and posting about it.
Click to expand...
Click to collapse
OK, I'm also one of the readers
The most important thing why I do not try it to use is, that I wanna held the "Sense UI".
Thats would be also the main reason for the other readers
regards
Dominic
derDominic said:
OK, I'm also one of the readers
The most important thing why I do not try it to use is, that I wanna held the "Sense UI".
Thats would be also the main reason for the other readers
regards
Dominic
Click to expand...
Click to collapse
Yeah I understand. I was one of those people. But I have come to like the helix launcher and beautiful widgets combination. I dont use any of the htc widgets other then the clock, which has a replacement for it.
Also over in cdma hero, many of the people use other launchers and dont use htc sense. Just for speed or personal favorites. I dont know how it is with here.
You can also disable jit very easily by changing the build.prop and having all htc widgets and sense usable agian.
when i do this "mount -o remount,ro /dev/mtd/mtdblock6 /system" it says
mount: device or resource busy
Also how does one get the $ sign whenever i type adb shell it automatically goes to the next line showing me #
Also after running these commands my hero boots but get stuck when i try to unlock the screen by dragging it down, is this not compatible with roise? im running Be hero 1.2.6 which is an ERIS port(2.1).
eldrid said:
when i do this "mount -o remount,ro /dev/mtd/mtdblock6 /system" it says
mount: device or resource busy
Click to expand...
Click to collapse
should be remounted when you reboot anyway.
eldrid said:
Also how does one get the $ sign whenever i type adb shell it automatically goes to the next line showing me #
Click to expand...
Click to collapse
then $ means you are logged in as an unprivileged user, the # indicates that you are root. so if you get # after opening adb shell that is fine, you can skip the 'su' command then.
eldrid said:
Also after running these commands my hero boots but get stuck when i try to unlock the screen by dragging it down, is this not compatible with roise? im running Be hero 1.2.6 which is an ERIS port(2.1).
Click to expand...
Click to collapse
second line of the first post should clarify that...
eldrid said:
when i do this "mount -o remount,ro /dev/mtd/mtdblock6 /system" it says
mount: device or resource busy
Also how does one get the $ sign whenever i type adb shell it automatically goes to the next line showing me #
Also after running these commands my hero boots but get stuck when i try to unlock the screen by dragging it down, is this not compatible with roise? im running Be hero 1.2.6 which is an ERIS port(2.1).
Click to expand...
Click to collapse
The error i received to, dont worry about it.
Yes mine goes to #, ill edit the instructions.
And after it reboots to the screen. Press menu to unlock your phone, DO NOT SLIDE.. It rarely works sliding.
And once you press menu, go to settings, applications, manage applications. Find htc sense, and CLEAR DEFAULT...
Then go to the market and download helix launcher.. You need to do all of this if you want NO force closes and no problems. Once its installed you can press home and select helix as default. Reverse the step to put htc sense back on.
If you really want to use sense ui, you must disable JIT.. Boot up your phone, let it load to the lockscreen. Dont touch anything. Do the steps to edit build.prop and do
TO DISABLE:
CHANGING THIS IN build.prop... This should disable JIT (I have not tested this yet, will post if this works later)
dalvik.vm.execution-mode=int:jit
To:
dalvik.vm.execution-mode=int:fast
push it back to your phone, and reboot
Thank you Kendong2 for replying, I was typing it out when you posted. I didnt know you had helped already.
If anyone does try this, feel free to post what home screen launcher and what errors you come across. Other then htc related things.
I just enabled JIT. Doing some tests now.
---
Alright, this are the results in a "real world" environment:
JIT DISABLED/JIT ENABLED:
NeoCore with sound: 24.4/24.4
NeoCore without sound: 28.8/28.8
Softweg GPU test: 117/116
Lag test: 41/40
Linpack: 2.312/3.663
The only noticeable result was with Linpack, let's say, RAW processing power. All the graphics benchmarks show same performance with JIT enabled. I guess it's a good thing then right?
Just enabled it as well... will test and report
now running alright and seems to be stable. can't tell too much of a difference at the moment but here is the result from linpack.
ahero v0.71 with 64MB swap
Configured with: debugger profiler hprof with_jit show_exception=1
BSK
Is an update.zip possible ? I'm at work, can't use adb right now
ok, im trying to disable it but cannot?
where do i have to change from jit to fast? in the build.prop from sd card right?
@Arkymedes
if you edit build.props in /sdcard/jit then whilst your in that directory do a :
cat build.prop >/system/build.prop
chmod 666 /system/build.prop
sync
reboot
once you have rebooted, it might be worthwhile going back into adb shell and typing this :
dalvikvm -h
i think you should not see "with_jit" in the last line.
BSK
bluescreenkid said:
@Arkymedes
if you edit build.props in /sdcard/jit then whilst your in that directory do a :
cat build.prop >/system/build.prop
chmod 666 /system/build.prop
sync
reboot
once you have rebooted, it might be worthwhile going back into adb shell and typing this :
dalvikvm -h
i think you should not see "with_jit" in the last line.
BSK
Click to expand...
Click to collapse
Followed every step that you mentioned...
After reboot that's what I get in the last line after "dalvikvm -h":
Configured with: debugger profiler hprof with_jit show_exception=1
PS: anyway, I think it's disabled since the scores in Linpack are the normal ones, around 2.250 or something.
Well well...
I just enabled this and after first reboot absolutely everything crashes and I can't get past the lockscreen. Rebooting again now.
EDIT: Same again next reboot. Am on Androbin 2.1 Vanilla ROM
@Arkymedes
if you followed the instructions you should have backups in the /sdcard/dalbk/ folder. just use the instructions again to put them all back.
but it looks like it's not now using the JIT you just copied across anyway.
BSK
Hi all!
After searching the wide web of the world I didn't find anyone who cared to program the special characters for nordic keyboards (æ,ø and å). The norwegian stock ROM has got these mapped to own keys, but I've never liked to use stock ROM, so I was stuck with the "long press method".
If you screw up your phone trying to adb push, cp -f these files I'm not responsible yada yada yada (nothing wrong should happend, really)
What I've done is taking the modified files from teferi, and added my own editing for the quick keys (as I had to make place for the chars I removed from jkl) and the special chars of course.
Confirmed on my G2 (running the CM and Sense ROMs)
Code:
*Norwegian*
version 0.3:
-Fixed issue with , and ; didn't work on hardware keyboard.
version 0.2:
Quick change to the "Z" button, since "`" is used in command substitutions.
-alt-z is still "^", alt-shift-z = "`"
version 0.1:
-alt+j,k,l = æ,ø,å (alt+shift gives capitol letter).
- make ".com" a TAB key, as it ought to be
- left softkey is now "\" "|" "/"
- right softkeys are now "[" "(" "<" and "]" ")" ">"
- alt-z is now "^"
INSRUCTIONS:
- download file
- unzip g2-nordic_01.zip
- adb push vision-keypad.kl /sdcard/
- adb push vision-keypad.kcm.bin /sdcard/
- adb shell
- su (if you don't have ro.secure turned off)
- mount -o remount,rw /dev/block/mmcblk0p25 /system
- cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
- cp -f /sdcard/vision-keypad.kcm.bin /system/usr/keychars/
- reboot
Btw... backup of original keymapping is included... just rename them without .orig, and follow the procedure above
Code:
Guide to make your own keys:
Download a hex editor (i prefer xvi32), open the "kcm.bin", and alter the symbols shown in the attached .jpg. If you wish to alter the "main" char of the key, you can change that in the .kl file with notepad. You can find the original untouched files in the nordic...zip
Thanks to teferi for the base files
adb shell
I keep getting this, im sure the files on are on the sdcard
Code:
# cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
cp: not found
#
Make sure you have busybox installed (to get the cp function)... easiest way
I'll also update that in the OP.
You can also just copy it over to the respective folders with root explorer etc.
Sent from my HTC Vision using XDA App
won't quite work on DZ - the keyboard device name is vision-keypad-wwe on that model. renaming them ought to work, but I don't have something to test it on.
teferi said:
won't quite work on DZ - the keyboard device name is vision-keypad-wwe on that model. renaming them ought to work, but I don't have something to test it on.
Click to expand...
Click to collapse
Renaming the bin/kl still don't "trick" the system into using the files. At least from my experience. I'm just trying to get the original g2 layout that includes www/.com, along with the 3 user keys to work on the z rom.
eViL D: said:
Renaming the bin/kl still don't "trick" the system into using the files. At least from my experience. I'm just trying to get the original g2 layout that includes www/.com, along with the 3 user keys to work on the z rom.
Click to expand...
Click to collapse
I've used the kl./.kcm files from G2 to make the G2-norwegian layout, and DZ files to make the esp-version... which is why I removed the esp from this thread...
I think it should be possible to port the keys if you use the base files from each device, and edit the .kl/.kcm files the way you want them. Then add them both to the ROM... G2 will use the vision-keypad.* files, DZ will use vision-keypad-wwe.* files (but I think you already know this)
There's occasional all-caps ÄÖÅ problem with hardware keyboard, but closing keyboard and opening software keyboard and back to hardware keyboard fixes that. Or you can try this.
Update: This seems to fix irssi connectbot and all caps scandinavian characters problem also. Fixed Norwegian AE and O with dash.
This is what I did:
First you have to get root, I used these instructions and they worked for me (Finland, Saunalahti):
http://forum.xda-developers.com/showthread.php?t=843014
Want to know more about modifying keymaps, see here:
http://forum.xda-developers.com/showthread.php?t=837002
And this old post is still valid for modifying keymaps-file with hexeditor:
http://forum.xda-developers.com/archive/index.php/t-504710.html
And that's basically what I did.
After you have root:
Download the attachment vision-keypad-nor.kcm.bin.zip and unzip it.
On PC run:
adb pull /system/usr/keychars/vision-keypad-nor.kcm.bin /tmp (for backup, store the file somewhere safe)
Copy modified version to /sdcard (the file you downloaded)
adb push vision-keypad-nor.kcm.bin /sdcard/
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp -f /sdcard/vision-keypad-nor.kcm.bin /system/usr/keychars/
sync
reboot
(few finnish words for finnish googlers: desire z ääkköset skandit)
when i try this part:
"adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp -f /sdcard/vision-keypad-nor.kcm.bin /system/usr/keychars/
sync
reboot"
i get "Permission Denied" when i write SU. my phone IS rooted and have S-off.. any clue on what can cause this problem?
what state should the phone be in? "disk drive" right?
Problem solved: i had to open my super user application on my phone to allow before i could continue
Did everything like in instructions, and now my touchscreen is mirrored!
If I push the left side of the screen it registers it on the right side and vice versa. And worst thing is that I don't have the original file anymore
edit: I found the original backed up file, thank god! Nice gag
Samusalo, are you serious? Shouldn't have anything to do with touchscreen calibration.
Exanimus, did it work for you after all?
Should not have anything to do with touchscreen calibration.
Also fixes wrong keyboard mapping or capacitive buttons not working in G2 based roms.
I posted a repaired file somewhere alrdy, and this is 5th thread after mine
thanks for getting this started
more than the scandinavian characters i was annoyed by the total LACK of certain keys on the keyboard
as a linux user <, > and | are essential!
so i cobbled this together (also fixes the capital char issue)
changes;
æ -> [
æ +shift -> {
æ +shift+fn -> æ
ø -> ]
ø +shift -> }
ø +shift+fn -> ø
ä +fn -> <
ö +fn -> >
å +fn -> \
å +shift+fn -> ^
. +shift+fn -> | (pipe)
these remain the same;
æ +fn = ?
ø +fn = !
it appears we can still add shift+fn keys for the whole keyboard if more are needed
any suggestions?
installation;
adb push vision-keypad-nor.kcm.bin /sdcard/
adb push vision-keypad-nor.kl /sdcard/
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp -f /sdcard/vision-keypad-nor.kl /system/usr/keylayout/
cp -f /sdcard/vision-keypad-nor.kcm.bin /system/usr/keychars/
sync
reboot
be sure to backup originals
Shole, great stuff! Thanks. Will try your keymaps.
shole, you're awesome! Thank you, Jusii too.
I would be more interested in changing Æ or Ø to a second fn.
Is that easy to fix?
Sent from my HTC Vision using Tapatalk
shole said:
it appears we can still add shift+fn keys for the whole keyboard if more are needed
any suggestions?
Click to expand...
Click to collapse
Shortcut for "~" would be awesome to have too. I've got no idea what shortcut to use tho, since your layout seems awesome already and it's taking pretty much all the spare combinations available.
~ is at [email protected] already in the stock phone, and these mods
a second fn would be trivial to add to replace, say, å, but you would lose that button entirely for fn role only
the keyboard is already short of keys and the fn and shift keys are sticky by default so i don't really see it as a need at all
the menu key on the physical keyboard is entirely redundant though(you need it rarely and the other one is only a short thumb move away on the screen half), but it's right next to the existing fn-key so that's not much use
right side shift key would be redundant if it wasn't used by connectbot as tab
tattevajoo said:
Shortcut for "~" would be awesome to have too. I've got no idea what shortcut to use tho, since your layout seems awesome already and it's taking pretty much all the spare combinations available.
Click to expand...
Click to collapse
I'd map it to [email protected] ...
EDIT: Oops, I was late.
Ahhh my bad, should of looked more carefully ~ thanksss (again).
Sent from my HTC Vision using XDA App
Any way to add back key to layout? Taking gloves off allways when need to use back button is annoying...
Fubaaarrr said:
Any way to add back key to layout? Taking gloves off allways when need to use back button is annoying...
Click to expand...
Click to collapse
That would be one helluva improvement to this phone. Adding left and right arrows and it would complete for my use.
this looks nice...
did anyone so far start working on a German version of this, and would mind sharing?
the stock Desire Z German version annoys me as hell.
I set the phone to English, but use the German keyboard layout.
first of all, I can't input capital Umlaute (ÄÖÜ), no combination of Fn+shift+j/k/l works. especially bad if i want to input a new word.
changing the keymap should fix my woes here, right?
also for general use, I'm lacking <, >, ~, | and some others - maybe someone modified the german keyboard for this already?
on the other hand - the phone specifically has a combination (Fn+search -> Symbols) - why does this only contain like 1/3 of the 2 pages available in the soft keyboard?
does anyone know a way to add the whole bunch from the soft keyboard to the selection screen that pops up when hitting fn+search?
kind regards,
sub
Irssi connectbot does not need rooting it has a fix for scandinavian characters of its own, just enable it in the settings. The fix also repairs ~
It also contains ^ < > | etc characters in its longpress-menu
Thanks for the fix! It works on Gingervillain 1.4.
I prefer using adb push:
Code:
adb remount
adb push /vision-keypad-nor.kcm.bin /system/usr/keychars
adb reboot
Thanks Jusii for the fix!
rollex said:
Thanks Jusii for the fix!
Click to expand...
Click to collapse
Jusii's fix worked me for a long time in Froyo (Virtuous 1.0.2), but then I updated to Gingerbread and Virtuous 2.0.0 and got problems shole described. Installed shole's keypad fixed all the problems.
I would thank you all participated but for some reason there is no THANKS -button below your messages. So once I again I thank here. Thank you!
Until we get a dedicated forum, at that time this thread can be moved, we can talk about development and progress aside from rooting. I'll start off with remapping the buttons on the front of the device.
In DOS you can pull the keyboard map file below
Code:
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
Once pulled you can edit it in a program like Notepad++ and edit the following lines
Code:
key 407 RIGHT_NEXTPAGE
key 412 LEFT_NEXTPAGE
key 139 LEFT_PREVPAGE
key 158 RIGHT_PREVPAGE
You can change LEFT_NEXTPAGE to MENU and LEFT_PREVPAGE to BACK and now you have hard mapped Menu and Back buttons. I have ordered my own nook I've just been messing with a co-workers so I haven't found the Power button or "n" button mappings if they are in fact in the file.
Finally you can push the file back to the nook
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push TWL4030_Keypad.kl /system/usr/keylayout/
adb shell chmod 644 /system/usr/keylayout/TWL4030_Keypad.kl
zonyl said:
I've locked it up before when trying to boot nookie. Called tech support and they told me that holding down power button more than 20 secs, does a hardware reboot. Works.
Click to expand...
Click to collapse
elmonica said:
I installed the Android app store, but I am receiving the following error message:
"For security your phone is set to block installation of applications not sourced in Android Market"
How do I turn that off?
Thanks.
Click to expand...
Click to collapse
This will allow non-market installs [unzip sqlite3.zip]
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
del settings.db
Also if you want to install SQLite3 to the N2E you can just push it to the device. [unzip sqlite3 (push to n2e).zip]
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push sqlite3 /system/bin
hey, i dont own nook touch, but this should work, just as on Nook color (from video I seen):
to go BACK, you dont need to remap key, just swipe with finger from right-to-left in clock area (on nook color it was at bottom, but on nook touch it should be at top position).
post results..
xmas_spirit said:
hey, i dont own nook touch, but this should work, just as on Nook color (from video I seen):
to go BACK, you dont need to remap key, just swipe with finger from right-to-left in clock area (on nook color it was at bottom, but on nook touch it should be at top position).
post results..
Click to expand...
Click to collapse
Yes, I've been doing this.
Nook 2nd Ed. Touch --from an SD card?
(First, sorry if this isn't the perfect place to post this...so feel free to move it if there's a better place.)
Ahem...uh, well...this question comes up because I happen to work at a business that is currently selling Nooks, and we've just received the new Touch version. However, for some brilliant (<<sarcasm) reason the demo units we've received are not really demo's, they only play a little presentation that shows how what the features are, and it loops over and over. So, we're very surprised that with this new touch sensitive Nook the user really doesn't have any chance to see how it actually works. No ability to test it, read, use the touch screen..nada! Wtf??
I'm curious whether someone might be able to make a bootable copy of the Touch software that will run off a SD card? If we could at least boot off the SD card so customers could at least see how the thing really functions, then it sure would make selling them easier...and no harm done afterward
-JTT
jttraverse said:
(First, sorry if this isn't the perfect place to post this...so feel free to move it if there's a better place.)
Ahem...uh, well...this question comes up because I happen to work at a business that is currently selling Nooks, and we've just received the new Touch version. However, for some brilliant (<<sarcasm) reason the demo units we've received are not really demo's, they only play a little presentation that shows how what the features are, and it loops over and over. So, we're very surprised that with this new touch sensitive Nook the user really doesn't have any chance to see how it actually works. No ability to test it, read, use the touch screen..nada! Wtf??
I'm curious whether someone might be able to make a bootable copy of the Touch software that will run off a SD card? If we could at least boot off the SD card so customers could at least see how the thing really functions, then it sure would make selling them easier...and no harm done afterward
-JTT
Click to expand...
Click to collapse
Of course this might be possible, but considering the limitations of this device (black and white, not meant to be a tablet) this would be very hard to achieve. The first step would be finding out if the thing can boot sd cards with a custom boot image.
ikingblack said:
Of course this might be possible, but considering the limitations of this device (black and white, not meant to be a tablet) this would be very hard to achieve. The first step would be finding out if the thing can boot sd cards with a custom boot image.
Click to expand...
Click to collapse
I do not see why it couldn't boot from SD since it boots from the SD to actually root it. I see ALOT of the original Nook color mod's and scripts working on this little device since it does not deviate from the Nook color design much.
Some more resources available here, including the installation for Kindle app
What does the partition shceme look like on the Nook Touch? Is it anyway similar to Nook Color? Don't have one yet, but plan on picking one up soon.
Thanks,
Racks
ikingblack said:
Of course this might be possible, but considering the limitations of this device (black and white, not meant to be a tablet) this would be very hard to achieve. The first step would be finding out if the thing can boot sd cards with a custom boot image.
Click to expand...
Click to collapse
10 char
Sent from my BAMF Thunderbolt powered by Sense 3.0
I was hoping that mapping HOME to one of the left buttons would bring up my launcher (ADW) but instead it it brings up the same menu as the N button. Any ideas how to map a button to a launcher?
I have found that Button Savior dies a lot, which means I can't get back to the launcher.
I remap the left keys as follows:
key 412 VOLUME_DOWN
key 139 VOLUME_UP
In Kindle, I set Kindle to use volume buttons for page turning. Then I can use the hard buttons for page turning in Kindle ! This also works in other reading programs for example Aldiko, NewsRob.
Does anyone know the key code of the Nook button and the action to launch the launcher ?
aruangra said:
I remap the left keys as follows:
Does anyone know the key code of the Nook button and the action to launch the launcher ?
Click to expand...
Click to collapse
Looks to be hard coded into the framework or something.
In trying to install the gapps on my NT, I've had to restore to factory twice. I started using the instructions for the NC here:
http://nookdevs.com/NookColor:Manua...gapps_google_applications_onto_your_NookColor
Code:
adb push nc_gapps.zip /media
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
cd /media
miniunz -x nc_gapps.zip -d /system/
echo "ro.config.nocheckin=no" >> /system/build.prop
exit
After installing the signed_youtube.apk I reboot.
Can someone who's done this post some details?
jocala said:
In trying to install the gapps on my NT, I've had to restore to factory twice. I started using the instructions for the NC here:
http://nookdevs.com/NookColor:Manua...gapps_google_applications_onto_your_NookColor
Code:
adb push nc_gapps.zip /media
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
cd /media
miniunz -x nc_gapps.zip -d /system/
echo "ro.config.nocheckin=no" >> /system/build.prop
exit
After installing the signed_youtube.apk I reboot.
Can someone who's done this post some details?
Click to expand...
Click to collapse
I know framework.jar does not like Nook Touch. BTW how did you factory reset?
To do a factory reset reboot x 8. Interrupt each boot with a powercycle prior to the "Nook..." screen.
It's really getting tough to find things, I'm following multiple nt threads, and I could swear someone wrote about installing gapps.
remount
Below is a handy script for mounting /system I keep in my /system/xbin directory. Originally from sdx for my epic, modified for the nook touch.
Code:
#!/system/bin/sh
case $1 in
rw)
echo "Remounting /system in read/write mode"
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system ;;
ro)
echo "Remounting /system in read-only mode"
mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system ;;
*)
echo "usage: remount rw -or- remount ro";;
esac
/system/xbin does not exist, it needs creation. I keep personal scripts there, and binaries such as busybox, bash, su, etc.
Extracting the root filesystem
These instructions assume using a linux console.
The root filesystem lives in a u-boot/PPCboot ramdisk. These instructions tell you how to extract it.
Boot your nt with the "rooted forever" sdcard while connected with usb.
Make a copy of the boot partition. After this you may reboot your nt normally.
$ tar -cf boot.tar boot/
$ tar xvf boot.tar
$ cd boot
Extract the uRamdisk file. first 64 bytes is the u-boot header, we need to skip it.
$ dd if=URamdisk bs=64 skip=1 of=ramdisk.gz
ramdisk.gz now contains the root file system.
Copy ramdisk.gz to a empty directory, then extract it:
gunzip -v ramdisk.gz
cpio -iv < ramdisk
Now the root file system has populated your work dir. Delete the file ramdisk. You can now make changes to the root file system, and using mkimage (in theory) reconstruct the uRamdisk.
That part I haven't done yet.
racks11479 said:
What does the partition shceme look like on the Nook Touch? Is it anyway similar to Nook Color? Don't have one yet, but plan on picking one up soon.
Thanks,
Racks
Click to expand...
Click to collapse
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 113.8M 0 113.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mmcblk0p2 15.7M 118.5K 15.6M 1% /rom
/dev/block/mmcblk0p5 278.9M 187.2M 88.8M 68% /system
/dev/block/mmcblk0p8 789.3M 80.2M 701.1M 10% /data
/dev/block/mmcblk0p7 232.4M 6.1M 223.9M 3% /cache
/dev/block//vold/179:6
236.3M 682.0K 235.6M 0% /media
/dev/block//vold/179:17
7.4G 3.1G 4.3G 42% /sdcard
dropbear & rsync
Dropbear and rsync are installed and working well on the nt. This setup allows me sync the libraries on most of my reading devices (exceptions PlayBook & iPad - walled gardens).
As we can provide new key mappings with custom roms, should it not be possible to do something like this instead? I'm fairly certain the keyboard has the equivalent buttons, but they're mapped to other useless stuff like shortcuts.
Would it be possible to include a swedish keymap in a rom and have it work "automatically"? I.e. are keymaps nothing more than a mapping turning a key (presumably an identifier) into a character?
Yes, it is. Take a look at Swedroid's forum.
Excellent, thanks!
I found some stuff there, and I've gotten to the point where I can modify my keymap. I know this, because I've managed to unmap a key. However, I'm unable to map the keys to the actual output I desire. I need the codes for å, ä and ö, respectively. According to that I found, they're FUNC_8, 7 and 5, but that simply doesn't work. I get nothing when I push the buttons when they are pointed to those mappings.
Any ideas?
Looking at vision-keymap-nor.kl, which contains the norweigian keymaps, the FUNC codes are the same. The question is, what do they point to?
So I looked at the files in /system/usr/keychars, and I found a human-readable file that looks like what I need. It looks like it's what defines the "aliases" being referenced in the keylayout file.
The only problem with that is that, when I uploaded my changed keychars file and rebooted, I reverted to some keymap with hardly anything but the basic keys in them. Only 4-5 keys produce anything while Fn is held...
I'm fairly certain I can edit the layout properly. I think, however, that it defaults back to Generic.kcm. I wonder why that is. Does anybody know how android selects which keymap to use?
I found the problem
I found the problem.
I had tried to use custom keycodes, A_RING, A_DOTS and O_RING in my vision-keypads-wwe.kcm, but it turns out that this is not allowed. You have to stick to ones that exist. I looked at vision-keypads-nor.kcm, and found that it used BUTTON_1, BUTTON_2 and BUTTON_3 for this. Once I switched from my custom keycodes to ones that exist, it immediately accepted the programming.
Result: I now have native åäö mapped to the bottom row of my keyboard in ICS.
As this maps SYM to 'å', you can get SYM bu doing Fn+Shift+SYM
If you want the same, I've attached my .kl and .kcm files. To put use them, do the following:
adb push vision-keypad-wwe.kl /sdcard/
adb push vision-keypad-wwe.kcm /sdcard/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp /system/usr/keylayout/vision-keypad-wwe.kl /sdcard/vision-keypad-wwe.kl.orginal
cp /system/usr/keychars/vision-keypad-wwe.kcm /sdcard/vision-keypad-wwe.kcm.orginal
cp -f /sdcard/vision-keypad-wwe.kl /system/usr/keylayout/vision-keypad-wwe.kl
cp -f /sdcard/vision-keypad-wwe.kcm /system/usr/keychars/vision-keypad-wwe.kcm
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
exit
adb reboot
Click to expand...
Click to collapse
If you need help, don't hesitate to ask.
Edit: Credit where credit is due. I had some help from this thread: http://www.swedroid.se/forum/showthread.php?t=26289&highlight=desire+svenskt+tangentbord&page=2