Develop Bugs

Rom version change

Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i

tomme45i said:
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
Click to expand...
Click to collapse
You can do that from the kitchen. I know ervius kitchen has two dialog boxes on the left, sort of middle of the screen, where you can set ROM date and version. It will patch the nk.exe accordingly.
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
P.S.: Sorry tomme, don't really read the Trinity threads anymore. But I will take a look every now and then, promise!

Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.

tomme45i said:
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
Click to expand...
Click to collapse
That's because of the nk.exe that has already been patched. Try another nk.exe or an older buildOS.

tnyynt said:
Try another nk.exe or an older buildOS.
Click to expand...
Click to collapse
I try on PkgToolsBuildos 4.2b3 and on 4.3b1. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.

tomme45i said:
I try on PkgToolsBuildos 4.3b1 and on 4.3b3. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
Click to expand...
Click to collapse
Try with this one.

tnyynt said:
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
Click to expand...
Click to collapse
it can be changed, it's just a hardcoded MOV instruction in assembly

tnyynt said:
Try with this one.
Click to expand...
Click to collapse
tnyynt thank you for you answer, but even on older version situation is the same. Program always overwrite 1st digit. Here is screenshot from older version buildos+package_tools-4.1b1:

You can't change the first digit in ROM version, no matter which nk.exe you try to change.
On the old nk.exe (the one used to fix the losing password bug for some users) you'll always have 0. before whatever you want your ROM version to be.
On the newer nk.exe you'll always have 3. before whatever you want your ROM version to be.
That's something you just can't change, because it's an hardcoded value and this was the reason why my ROMs for trinity were 3.something (because when I started cooking I was using the newer nk.exe) and even after changing to the old nk.exe (to solve the losing password bug for some users - a problem I never had in my device), I had to start numbering my ROM as 0.3.something.
My advice:
If you don't have the password bug with your device, and are not planning on releasing the ROM, use the newer nk.exe and number your ROM 3.1.0, and forget about the 3..
The ROM version in Device Info is a completely different thing. That value is not hardcoded anywhere, and since it's a registry value, you can put whatever you wish and it will display properly.
In conclusion, if you're using the PkgToolsBuildos (doesn't really matter which version you're using) to change the ROM version (and this is responsible only for the value that appears on the boot screen), leave the left field as it is, and change only the right field to what you want and save changes.
I hope this will clear your doubts about this. Happy cooking!!

I don't know the difference between this two version of NK.exe so FInixNOver thank you for explanation!
I release my roms on polish forum. First nine was based on old NK.exe, so the last was 0.9. Now when I try new NK.exe I was surprised that my rom version in boot is starting from 3.
BTW. I think only first digit is hardcoded, cause I can change dot symbol by hex editing S000 file.
One more time FInixNOver thank you for your reply!

FInixNOver said:
That's something you just can't change, because it's an hardcoded value
Click to expand...
Click to collapse
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above

cmonex said:
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
Click to expand...
Click to collapse
I stand corrected. I just said that because I was never able to change that value. So if you say it's possible, even better!!

[BETA] Platformrebuilder.exe - Next generation ROM Kitchen

I have been working on this new ROM Kitchen project over the last months.
Public beta can be found here:
http://www.darkforcesteam.com/showthread.php?p=3560

Downloading this minute. Is it also for old devices? (Blue Angel?)

Sounds great, thanks for this kitchen

motisu said:
Downloading this minute. Is it also for old devices? (Blue Angel?)
Click to expand...
Click to collapse
Should theoretically work for all HTC devices.
Only have an HTC Diamond to try it myself, but others tested it on Universal, HD, Raphael, ...

Nice to see you back Bepe!, Happy New Year

OMFG
bepe, you've completely outdone yourself this time!!! Checked out the videos, looks amazing!! Congratulations.

Downloaded, will check it out and post results. Thanks!!!

Hmm.it will work on all htc devices.
maybe some older dev cant use,need to test by yourself
really nice Rom Kitchen.
Great jod!!!
Cheers
Monkeybape

i second the post with the video tutorial !! great work and even me is able to build a rom now *lol*

Is removal of unneeded files from XIP supported, bepe??

this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again

chavonbravo said:
Is removal of unneeded files from XIP supported, bepe??
Click to expand...
Click to collapse
yes, it possible to add/remove all files/modules you want. It works the same way as in IMGFS... just delete the file/module from the XIP package or add a new one to an existing or new package.
the Kitchen will not include files that are not needed like boot.rgu, *.rgu, *.dsm to the XIP section, so there is no need to remove them after the XIP partition is build.

mbarvian said:
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
Click to expand...
Click to collapse
1. replacing WINCE_NLS is not really a problem, but the size of the .nls file might be.
example:
- you are using a WWE Kitchen with a WWE nls size: 267 KB
- you want to change lang to CHT, the nls size would be 1500 KB
--> this means the size of the xip section would grow very much
--> ROM\os.nb.payload is WWE and would not have enough space for the bigger CHT XIP
--> ImplantXIP.exe should give you an error I think... never tried it...
solution: use the CHT os.nb.payload (just replace the WWE .\ROM\os.nb.payload by the CHS one)
The CHS roms would have more space for XIP, so all would be working fine
2. Using another resolution is not a good idea... most SYS packages are compatible, but there are packages like this:
- Base_DPI_192 - this is for 192 DPI like Diamond, Raphael, HD
- Base_DPI_96 - only for QVGA devices
- base_dpi_192_resh_480_resv_640 - this package tells you the exact resolution it was made for
You could mix two builds, like using only new packages without *_DPI_192 or *_dpi_192_resh_480_resv_640 in the name...
... but not really a good idea, even that many ppl are making that. Consider that there might be resources that might be changed

Would take a look at it, but the forum requires compulsory registration to view.
Please fix your forum.

It tells me I'm missing msvcr71.dll when I try and dump. I noticed that file is other kitchens so I tried to copy it over and it starts the dump but then RecMod.exe stops responding and it asks to close.

I keep getting this error when it comes to running platformbuilder
Code:
This aplication has requested the runtime to terminate it in an unusal way

boo, I wanted to watch the tutorial on your forum again, getting an initflashfiles .dat not where it's supposed to be error. but your forum seems to be down, or under too high traphic right now, is there any way you would think of putting together a short text based info set on everything we need to know to dump and rebuild? if not, no biggie, I am sure I will figure it out, like any great new tool, there is always a learning curve Thanks much for sharing your work with all of us though

Good to see you back bepe!!! I will give this a shot later on today...

outstanding bepe!! I thought your tutorials were excellent too!

thanks bepe
tested your kitchen on my Elfin and it worked well except for implantxip, because i've reduced the size of my XIP partition in template payload, so implantxip gave me error like "no xip section found". i replaced implantxip with msflshtool and it worked fine. no other issues faced in ROM building and porting newer build for my Elfin . although i had to make some adjustments to Dump_200.bat for dumping the ROM.
also, we used buildxip for xip porting before and it had some specific switches like -g, -k and -f useful for enabling different kernel modes, changing fsrampercent etc. i was wondering if same is possible while xip porting with new kitchen or is the best setting chosen automatically?
and, do check your paypal for Transaction ID: 45A49499TS934251W

IMGFSFromDump-TURBO v2.4.0 with file prefetching and multicore compression (19/09/10)

Yes, it's actually just as awesome as it sounds: multicore-multithreaded compression allows it to compress up to 2x faster on dualcores and 4x faster on quadcores but it's not just that, it also does realtime file prefetching while compressing, allowing imgfs to be built much faster even on singlecore machines and without causing any additional hard-drive overhead. The v2.2.2 version also allows selecting the compression (LZX/XPR/None) trough a command switch, overriding the compression setting dictated by the source imgfs file and finally removing the need of having to hexedit the original imgfs file to change compression type.
Remember to fasten your seat belts and turn off any electronic gadget, it's so fast your PC chassis could actually take off!
And remember, *use this at your own risk* I don't take responsibilities, especially if your computer chassis really takes off .
Command line syntax
ImgfsFromDump.exe [-compression <LZX/XPR/None>] [-freespace <NumberOfMegaBytes>] [-empty] [-verbose] <imgfs-in.bin> <imgfs-out.bin>
All parameters but the input and output file are optional so you can use the tool in ervius' and other kitchens without having any issue just by replacing the imgfsfromdump.exe file.
NOTE: Oskitchen already comes with customized versions of this tool so please do not replace the one oskitchen comes with.
Changelog
Version 2.1: faster and uses less ram
Version 2.2.2 version: allows selection of compression (also allows building ROMs with no compression and removes the 256mb IMGFS file size limit)
Version 2.2.3 version: compiled statically so it doesn't need any c++ runtime to work
Version 2.3.0 version: now more stable, no more hanging with None compression (I had it running in batch mode for days and it never gave an issue with it or other compressions), allows setting the free space (if you manage to use imageupdate) and allows creating empty imgfs.bin without requiring a dump folder (useful for reducing payloads)
(NEW!) Version 2.4.0TEST: implemented native support for unicode file names (used in stock Oboe ROMs).

Iam happy that iam replying first to this thread.
Hmm i have downloaded that and wanna see if that really that fast in my dual core pc.

Flashing with the new imgfsfromdump. I went from 1 minute and 3 seconds for a LZX compression to just 21.45 seconds. I did have to use a different cecompr_nt.dll then the one you supplied for lzx compression to work, but other than that, nice work!

Working like a charm on my kitchen, thanks mate.

cecompr_nt.dll in the zip file support both LZX and XPR compression or not?

texture said:
cecompr_nt.dll in the zip file support both LZX and XPR compression or not?
Click to expand...
Click to collapse
It shouldn't since it's an old version, just overwrite it with a more recent one.

seems to be working great so far for me, thanks for the share airxtreme!

just tried this and damn it builds a rom fast

Wow, amazing
Really improve the build process
Thanks for this

THx Share

airxtreme said:
Yes, it's actually just as awesome as it sounds: multicore-multithreaded compression allows it to compress up to 2x faster on dualcores and 4x faster on quadcores but it's not just that, it also does realtime file prefetching while compressing, allowing imgfs to be built much faster even on singlecore machines.
Remember to fasten your seat belts and turn off any electronic gadget, it's so fast your PC chassis could actually take off!
And remember, *use this at your own risk* I don't take responsibilities, especially if your computer chassis really takes off .
Click to expand...
Click to collapse
Thank you very much

great work!

So, I just need to replace the 2 files in my Ervius Visual Kitchen, I dont need to config anything?

A bug!
When i use LZX compression,the new imgfs.bin is larger than the imgfs.bin of XPR compression,but it is fast than before!Thx~

madsurfer1 said:
So, I just need to replace the 2 files in my Ervius Visual Kitchen, I dont need to config anything?
Click to expand...
Click to collapse
Can EVK 1.8.2 use this?

ted973 said:
A bug!
When i use LZX compression,the new imgfs.bin is larger than the imgfs.bin of XPR compression,but it is fast than before!Thx~
Click to expand...
Click to collapse
That shouldn't happen, the file size should be exactly the same. Did you use a recent cecompr_nt.dll to make LZH work?

Here's the cecompr_nt.dll that I use to get LZX compression.

eagle88_cn said:
Can EVK 1.8.2 use this?
Click to expand...
Click to collapse
same ask, I try it one time few days before, and old IMGFSFromDump make a booting rom, but your IMGFSFromDump cant make a booting rom, will try it later, thanks very much

kane159 said:
same ask, I try it one time few days before, and old IMGFSFromDump make a booting rom, but your IMGFSFromDump cant make a booting rom, will try it later, thanks very much
Click to expand...
Click to collapse
I tried this on osKitchen and it worked fine, it should work on any kitchen that uses imgfsfromdump, probably your issue was caused by the LZH compression that didn't work with the included cecompr_nt.dll. Just use the cecompr_nt.dll that came with the kitchen and everything should be all right.

eagle88_cn said:
Can EVK 1.8.2 use this?
Click to expand...
Click to collapse
kane159 said:
same ask, I try it one time few days before, and old IMGFSFromDump make a booting rom, but your IMGFSFromDump cant make a booting rom, will try it later, thanks very much
Click to expand...
Click to collapse
i've swapped out the original's in my 1.8.2 kitchen w/the one posted here, and it's working great

[Release] [Kitchen] - SuperJustKitchen v0.9 - Engage!

SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
​ SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
​
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!​

Well ... I have repaired my Hermes yesterday and now I'm trying ROMs here and none of them really suits me.
So your SJK came in the right time. I did few ROMs for myself last year, so I'm gonna try your SJK probably this evening.
And if it will work flawlessy, I'm considering donation.

Impressive..
Downloading and will hopefully be trying this out soon.

Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)

ivanmmj said:
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
Click to expand...
Click to collapse
I am cooking a 23529 native build now and will know here soon

Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.

pajousek said:
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
Click to expand...
Click to collapse
You have to actually add them in the EXT packages. They are not built in so that you can choose your own. I stripped the OEM and created packages of all required programs and made them into EXT packages.

Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe

I must be doing something wrong then cause mine won't go past the boot screen using native. I used everything default. Will try again.

This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.

pajousek said:
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
Click to expand...
Click to collapse
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
Click to expand...
Click to collapse
I'm not sure what you mean. Can you please post a screenshot?

ivanmmj said:
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
I'm not sure what you mean. Can you please post a screenshot?
Click to expand...
Click to collapse
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|

pajousek said:
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
Click to expand...
Click to collapse
Fixed for next build. ^_^
For now, just remove the preconfig.txt file.
Please report any future bugs to the bug tracker. (There are way too many threads to keep track of all of them.)

I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?

pajousek said:
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
Click to expand...
Click to collapse
I activated you manually. I'm not sure why it's not sending out the emails. I'll look at the code of the site.

I take it this isn't bigstorage? If not do you plan to have one bigstorage? I'd like to be able to do bigstorage in 6.1 and 6.5 and this looks like my best option..
thanks

Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?

pajousek said:
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
Click to expand...
Click to collapse
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.

well, i'll try the not-native kernel (what disadvantages it has anyways?)
about bigstorage & clearstorage & dialer - i'll do some searching and testing and send you working links (since you don't have testing device).

ivanmmj said:
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
Click to expand...
Click to collapse
I have yet to get a ROM past the boot screen So I dunno..

Android :: How to change keyboard layout from QWERTY to AZERTY?

PLz do you know How to change keyboard hardeware layout from QWERTY to AZERTY,i'm using ?
i'm using Myn’s Warm Donut,every thing work fine for me !!

matriix said:
PLz do you know How to change keyboard hardeware layout from QWERTY to AZERTY,i'm using ?
i'm using Myn’s Warm Donut,every thing work fine for me !!
Click to expand...
Click to collapse
I think this is actually hardcoded into the kernel. I've had some looks at the kernel source code (which DZO maintains) as I want to add support for scandinavian keyboard. Shouldn't be that hard to modify once you manage to set up an enviroment that allows you to compile the kernel.

Could you take a photo of your azerty keyboard (detailed enough to also see the Fn alternative for each button) and if time allows I may have a go at it.
I've successfully managed to remap the kernel for my scandinavian keyboard (except for the special nordic characters).

How did you remapped it?
Henri från Finland

Hepe83 said:
How did you remapped it?
Henri från Finland
Click to expand...
Click to collapse
By changing the kernel source.
Edit: /arch/arm/mach-msm/board-kaiser-keypad.c
Then compile your own kernel. I'll send my changes to DZO once they are complete. Right now I have changed the "normal" layout but the correct way would be to add a new setting and make it selectable so it's needs to cleaning up. I also haven't managed to add ÅÄÖ (and the norwegian counterparts) yet. But everything else is mapped correctly so I no longer have to guess where the "slash" is and so on.
Actually my current mappings are posted in the kernel thread in the Vogue forums as I've asked for help for the remaining 5 buttons.
EDIT: Added my experimental kernel as an attachment. Unzip and place in x:\andboot\ (make a backup of your original kernel just in case)
This kernel should be the same as DZO's 29-03-10 kernel except it is partially remapped for nordic hardware keyboard and also have the BT changes that broke bluetooth on Eclair reverted.
EDIT2: Removed attachment, later version (and NAND) available here: http://forum.xda-developers.com/showthread.php?t=660158

Newer version of the Nordic keyboard kernel here: http://forum.xda-developers.com/showthread.php?t=655512
Edit: fixed the link

Try the attached kernel. Make sure to set board-kaiser-keypad.atttilt to 3 in default.txt/startup.txt.
Please let me know if it works OK asap. I've used a picture that I found on the net of the Kaiser azerty keyboard. Not use about the Fn->S. The picture was a bit blurry so I left the defult mapping for Fn-S which is a ".
EDIT: Removed attachment, later version (and NAND) available here: http://forum.xda-developers.com/showthread.php?t=660158