Develop Bugs

[Mod][NOR] Lang characters for hardware keyboard v0.3

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)

Screen calibration config

I'd like to know where are stored the parameters of the screen calibration.
I ask this because at every reboot they reset to factory default so I want to mod it directly.
Kisses to all

seems to be stored in
Code:
/data/data/org.isageek.dasbrennen.CalibrateScreen/databases/calvalues
which is a sqlite database (which I know nothing about!)
You could try making a copy of it before and after rebooting and see if it changes (binary diff). If it does, maybe you could replace it on every boot in your userinit .sh
If not, maybe the CalibrateScreen app just needs to be started to load the custom values, but you could probably do that on startup too.

mmec2 said:
seems to be stored in
Code:
/data/data/org.isageek.dasbrennen.CalibrateScreen/databases/calvalues
which is a sqlite database (which I know nothing about!)
You could try making a copy of it before and after rebooting and see if it changes (binary diff). If it does, maybe you could replace it on every boot in your userinit .sh
If not, maybe the CalibrateScreen app just needs to be started to load the custom values, but you could probably do that on startup too.
Click to expand...
Click to collapse
Thank you very much for your reply, however I was trying to figure out the place where these values are stored into android system and not into the app... because I think that the app it's only a bridge for the real calibration of the system... or maybe I'm wrong?

TuoNonno said:
Thank you very much for your reply, however I was trying to figure out the place where these values are stored into android system and not into the app... because I think that the app it's only a bridge for the real calibration of the system... or maybe I'm wrong?
Click to expand...
Click to collapse
For some reason, I assumed it was a built in part of the system, but it's not!
Anyway, your question has got me interested now, so I took CalibrateScreen.apk from Scoot's CM6.1 build, decompiled the apk with apktool and searched the source for "write"
I believe the values you are looking for are
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
(found in CalibrateScreen/smali/org/isageek/dasbrennen/CalibrateScreen/Calibrator.smali)
so you could just add
Code:
echo NUMBER > /sys/class/vogue_ts/xmin
etc. etc.... to your userinit.sh

mmec2 said:
For some reason, I assumed it was a built in part of the system, but it's not!
Anyway, your question has got me interested now, so I took CalibrateScreen.apk from Scoot's CM6.1 build, decompiled the apk with apktool and searched the source for "write"
I believe the values you are looking for are
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
(found in CalibrateScreen/smali/org/isageek/dasbrennen/CalibrateScreen/Calibrator.smali)
so you could just add
Code:
echo NUMBER > /sys/class/vogue_ts/xmin
etc. etc.... to your userinit.sh
Click to expand...
Click to collapse
you are the man! You solved a issue that was drilling me since months!
Many many thanks!

It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
3) edited userinit.sh with notepad++ like that:
Code:
#!/system/bin/sh
#
# Fix su so that we use the one supplied with the build. This allows the Superuser Permissions app to do it's stuff
#
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 708 > /sys/class/vogue_ts/xmin
echo 3660 > /sys/class/vogue_ts/xmax
echo 257 > /sys/class/vogue_ts/ymin
echo 3551 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
4) created a androidupdate.tar file with 7zip containing system/bin/userinit.sh
5) dpad during startup, installed androidupdate and fixed permissions
Happy ^^

could you upload the standard calibrate file to me ?
I dont understand why my kaiser seem to be crazy because touch screen seem to be rotate 90 degrees. it mean .... the app button ( in the center of the bottom screen ) will become middle of the left screen. I mean if I want to touch app button, I must touch the middle left of the screen
I cant do anything with this !!!
Fuk my kaiser >.< sorry for my bad emotion !!!

dai_thang said:
could you upload the standard calibrate file to me ?
I dont understand why my kaiser seem to be crazy because touch screen seem to be rotate 90 degrees. it mean .... the app button ( in the center of the bottom screen ) will become middle of the left screen. I mean if I want to touch app button, I must touch the middle left of the screen
I cant do anything with this !!!
Fuk my kaiser >.< sorry for my bad emotion !!!
Click to expand...
Click to collapse
Sure, here it is, install it like a normal update from dpad menu on boot (remember to fix permission after the install)

thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !

dai_thang said:
thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !
Click to expand...
Click to collapse
LOL...
have you tried to follow the instruction that I posted above to extract the correct values for your touch? remember also to do the calibration with the sliding keyboard closed!

TuoNonno said:
It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
Happy ^^
Click to expand...
Click to collapse
How can I generate this information ???
What did U mean .... by saying "copied" ?

Those are the steps I did, so I wrote "copied".
Just follow those steps, nothing more to do
Basically, you need to run the calibration screen app, then you copy the 5 files in "/sys/class/vogue_ts" to your sd card root in order to be more handy and do those steps.

dai_thang said:
thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !
Click to expand...
Click to collapse
actually i cant speak english properly. but ill try to answer ur questions.
i have a stupid solution for the problem of calibrating the screen. i use Incubus26Jc's Super Froyo 2.2 [Deodexed] [RLS15] on my kaiser.
i do the screen calibration once a week. for the screen calibration on my android, will appear a black screen with two red dots on the screen to the left top, and bottom right. all i have to do is touch one red spot twice, until the recalibration text does not appear. (or other writings that tell you to re-calibration).
finished ...!!! what i have to do is press the "OK" to apply. i hope now ur screen is not mad anymore.

TuoNonno said:
It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
3) edited userinit.sh with notepad++ like that:
Code:
#!/system/bin/sh
#
# Fix su so that we use the one supplied with the build. This allows the Superuser Permissions app to do it's stuff
#
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 708 > /sys/class/vogue_ts/xmin
echo 3660 > /sys/class/vogue_ts/xmax
echo 257 > /sys/class/vogue_ts/ymin
echo 3551 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
4) created a androidupdate.tar file with 7zip containing system/bin/userinit.sh
5) dpad during startup, installed androidupdate and fixed permissions
Happy ^^
Click to expand...
Click to collapse
Awesome! my Kaiser 100 now holds screen calibration, even after a dead battery or a power cycle. Really enjoying Dark_Prince's Froyo 2.2.2 on this AT&T tilt. But the method of creating a androidupdate.tar did not work for me. The update reported it worked as a success, then a fix permission seemed to finish, but still no calibration save.
This is what worked on my device:
As TuoNonno said I copied the four files containing the needed values, and in the end I went to market and got a file manager that had root permissions and edited ' /system/bin/userinit.sh ' to reflect the values those four files held.
my userinit.sh on my device now looks like this:
Code:
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 1345 > /sys/class/vogue_ts/xmin
echo 3387 > /sys/class/vogue_ts/xmax
echo 334 > /sys/class/vogue_ts/ymin
echo 3615 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
Not sure if that is the 'proper' way to fix, but it surely seems to work - I no longer have to use the physical buttons to navigate to and open the screen calibrate app.
Thank you to all that had a part in developing this fix. The knowledge of the gurus on this forum is outstanding!

[Q] QWERTZ -> QWERTY on a Desire Z

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.

[N2E] Nook 2nd Edition Touch - Development

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).

[Q] Changing Desire Z hardware keyboard to swedish (with åäö)

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