yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anagarika:
I'd suggest for our chefs releasing new ROM, to indicate usage of new 6.5 NK.exe on the subject/thread title ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Mars.C:
I am trying to cook a WWE ROM，but my english is not very good :D

So Sorry ！I have been cooking CHS ROM:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nicke85:
I tried to cook 6.1 rom with native kernel but won't boot..:mad:

Who tried too!?!?:cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Mars.C:
I tried,I have not found any problems！:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pdaimatejam:
camera no problem

HTCCamera1.dll delete

camera ok no problem :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nicke85:
Great :D..I'm stupid maybe hehehe :confused:..which build you use!??!?Which kitchen!?!?

I tried 21054,21056 and old 21109..every time like in posts before memory map is diferent..

I found that old build 21109 work with full D3D support,101 ram and old kernel..

but combination is only netCF3.5+D3D on old build..very speedy..

Now want to try that build with new kernel..:p

And tell me do you use new 6.5 drivers on 6.1 build!?!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] neilverma:
Sorry could you please be more clear. Are you saying that it is safe to delete HTCCamera1.dll without any problems?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nicke85:
Get 6.1 worked!!!!:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jjblaster3:
yup, just done uploading 6.5.x rom, u can get it here

http://xdaforums.com/showthread.php?t=567850

yes it is safe, i delete it coz it interferes with the camera launching, causing errors...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Quetzecotyl:
This is probably the coolest upload on this subforum. Thank you to Mars for the info, and nick/joojoobee for your respective uploads, this is just great and completely unexpected :D.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Mars.C:
aha ！ congratulation
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ZGGZHH:
Thank you.

:d谢谢mc。。。你是最棒的。
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nicke85:
Some new stuff Kaisers..

Native Kernel 6.5 modded to 107mb ram by me (Work Perfect!!) :rolleyes:

And!

Drivers for WM6.1 sorted to work with Native Kernel 6.5 :eek:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] twisted:
thanks for sharing this stuff.

regards,

twisted :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Mars.C:
you hex PagePool 6M ？I do not think that good :D

I proposed to maintain the dynamic:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nicke85:
If you don't use Manila2D than 6MB pagepool is perfect for WM6.5..

I just use it and don't have speed problem with my Kaiser..

I made it personaly for me but shared if somebody wan't also :cool:

You can use dynamic ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] obaz:
give me try
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] af974:
Thanks for sharing nicke :D

Btw i have some problems with new Kernel and Manila,youtube wont start and opera has some glitch on open,..........with new kernel opera and youtube wont work, but with old kernel all seems to works fine.

Any advice?

Thanks.

PS: i use old drivers with only new touch.dll couse when platformrebuilder starts it give me some errors with some dll.....uhmmm.. i guess mycpl and api if im not wrong...sorry i dont remember :D

ED: what about os.nb.payload? i have a version of 06/2009 2,75 mb, can it make the problems?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Twistedme:
silly question

How exactly can you tell that a rom is using the new kernal from the flashed device? I mean is it listed on the bootloader,under info or device, I tried using total comander to look at the actual nk.exe. Im just curiouse if its possbile to detect which kernal a rom is using without haveing to break it open in a kitchen app.

Thanks in adavnced to anyone who is willing to help educate me on this.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gajodafeira:
Screenshots of the rom working please?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] purasx:
How install this drivers for Kaiser? Is this really boost pda? Call of duty 2 works better?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
You can't install those, they must be COOKED in!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] l2tp:
guys, can anybody share romhdr.bin for this 6.5 nk? i have slow connection right now and cannot download entire rom made with this nk by somebody in order to extract romhdr only from it!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] af974:
There is a metod to see if the rom is a Real Native kernel:

StartMenu/setting/memory----->

Native kernel has RAM 100.xx or 106.xx

Old Kernel has RAM 101.28

101.28 its the old kernel with memory patch.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] twopumpchump:
so are all chefs having the problem with some multimedia apps not working using this kernel? i havent cooked it yet, just curious. also is there a difference in the amount of total ram with this kernel and the old 101 ram kernel?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] af974:
Well, actually i have 90% of apps working , i have only an user that has problem with Ndrive(navigation software) that is inbcompatible with new kernel and drivers IMO.

As what ive test yet there are difference in total amount of Ram (as i write before)

Native total amount Ram: 100.xx (106.xx with Nicke85 nk.exe)

Old Kernel amount Ram : 101.28 with Memory map

Also i did some test with native kernel and memory map but it wont work,Ram is always 100.xx

I have right now an old kernel rom up so i dont remember exactly the total ram in ne kernel,,thats why i wrote 100.xx, could be 100.28 if im not wrong.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UltimoJedi:
tnx

@Mars.C Thank you for reporting.

good test for all ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ASCIIker:
i'm not a chef but just a bit curious and somewhat confused...

i am currently using JJ's first ROM that was built with the native kernel. it shows 101.34MB total. the latest ROM from JJ (released today) also uses the native kernel and shows 101.34MB total.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] af974:
Yes i know....i was testing all new roms with native kernel and not today and the only rom with native and over 101 mb is JJ's rom.

Ive send him a PM and he saied me that he was using native,dont know what happened ....maybe a bug.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] twopumpchump:
its probably the difference in pagepool ;) so are you guys using memfix with the new kernel, or is it built in the new oemdrivers? reason i am asking is that since the nk.exe is 101mb ram, it must have been hacked by someone. i have spoken with da_g and he said that the extra ram we got in kaiser with 101 ram is taken from reserved memory for multimedia applications...hence the reason we have issues with youtube and d3d stuff. i really dont think that htc made that nk.exe with 101 ram, but i could be wrong.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] af974:
I just made 2 Roms with your Kitchen...one with memory fix ,and one without.

The result its always the same :total amount of RAM 100.96 mb.

From New OEM drivers what you need for sure is only touch.dll.

In my rom ,now, Youtube and Opera does work, ive only an user with some issue with Ndrive but i found the issue in some EXT packages nor in drivers.

EDIT :what pagepool size have you by default in your kitchen?

I used to set mine to zero in Ondra Kitchen.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
Yep, that mem up to the full 128MB is used by Camera, D3D etc so any using this memory will cause troubles with some stuff probably.

Also, that different memory (100.34, 103.69 etc) is based on size of XIP since platformrebuilder resizes value of ulRAMFree by size of XIP plus align. So if you have smaller XIP, the more RAM you actually can get. But since XIP is about 3.5MB large (you can make it to 2.8MB on Rhodium, not sure about Kaiser), it doesn't matter that much.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] af974:
ok Ondra , what we they do for have a smaller XIP?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
Delete unneeded stuff :)

If you google a bit, you'll find some files that can be removed :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jjblaster3:
the OEMdrivers that come together with the nk do contain the proper ddi.dll + wce_pmem.dll (lets call this new memfix :p) to work with the 101 ram...

I however used my old OEMdrivers and just tried out the new memfix files but they seem to reduce performance abit compared to previous memfix files that i used to use. So both my roms (6.5 and 6.5.x) use only new nk.exe together with the touch.dll but everythin else is previous stuff
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anagarika:
I have a question: during 6.1, flashing doesn't require stock ROM prior to custom. 6.5 with 6.1 kernel needs that. How about now 6.5 with native 6.5 kernel? Any chef has insight?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Dukenukemx:
So what do these native kernal and oemdrivers do?

Increased stability? Performance? More ram? Do they allow for OpenGL with 101MB of ram?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
They mostly allow map modules to all four slots => faster loading => faster device :).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sgoo:
... ... ... and not stable OpenGL with 101MB of ram ,

I think it's impossible with more of 85MB :( .

An example under WinXP ( observe the division into User and Kernel Space ) :
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ahmedfikry:
so how about if you upload your "tweaked" and working 6.5 drivers & nk

please share the final files you use after deleting & adjusting to get best size & speed

thanks in advance
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
This has one small flaw... WinMo's memory management is totally something different and this issue has different roots.

It comes from that the 128MB RAM is shared between all CPUs and GPUs etc. Which means that even camera and OpenGL and audio etc must have its own reserved memory. Guess what happens, if you move your ulRAMEnd to eg offset from (just examples, not real story) 10000h to 11000h if the OpenGL driver uses memory from 10100h? It won't work:rolleyes:.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UltimoJedi:
Nk: Ram 84mb & 89mb

NK: RAM 84MB & 89MB

A thanks to udK for the change :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Teijak:
Many thanks to both of you, do you have more info regarding OndraSters post.

edit: Tested 89MB version works very good, video and camera working great. Even D3D driver from HTCClassAction.org is working.

Teijak
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ahmedfikry:
can you please explain a little bit whats the difference in RAM size effect, which one is better to use & are you using these nk with 6.5 drivers without modifying the drivers?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UltimoJedi:
I will have made hundred test in this week with the possible whole NKs (101, 89, 84 MB) and the possible Drivers (3.57 HTC, 3.57AT&T, 3.55, 3.53, 3.34, 3.29, 3.14...) but with my kitchen I always find me an a instable ROM if they go him to activate the OpenGLs. :(

it is alone from about ten days that I am studying this new Native Kernel (I had remained to the OLD 6.1) I have wanted to share even with you alternative Kernel someone he succeeds in finding an optimal solution :)

I apologize me if I speak a little here on XDA, but my English is very bad :D

Good test to everybody ;)

C!A@ UJ
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nicke85:
Diferent ram size with NK for 6.5 is pagepool sets..it is edited with HEX editor..

Less ram size has bigger pagepool..:p
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ahmedfikry:
well

i have been facing the same problem

i tried different combos of nk & drivers.... i can get a booting rom, but the video playback does not work with any of them

if some chief who was successful in cooking with native 6.5 for kaiser can upload his working native nk+drivers (with working video playback) it would be appriciated

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
I don't think so, pagepool is something different, this sets where the system should map from classic memory to other processes (ulRAMFree).

(It's set in nk.exe when OEMInit runs.)

Or this is all is done?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] twopumpchump:
you are right, its reserved memory being used by remapping memory in nk.exe.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ahmedfikry:
so the more memory (the higher) the better

then nk 107 or 101 would be better than 85 & 89?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] twopumpchump:
its according to what you call "better". if we had the original nk.exe with normal ram, then you would be able to stop using memfix and d3d would work ;) not sure if the ones made by udk will work with d3d drivers or not i havent tested but the should i think. basically when you gain the ram, you are giving up the reserved memory for multimedia applications and you will see some lag in video and like i said d3d doesnt work.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sunsetdk:
Which DDI did you use with the dirvers (as I understand the DDI is the one the drivers access)

Does anyone know how you can see the driver version? (cooking a danish rom, using the danish latest drivers I could find, but no idea what version they are)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anagarika:
Shane,

Being in this discussion here, do we have hope to see V12 (and the counterpart Stock Like) for your Kaiser ROM in Native Kernel?

(hopeful mode, not pushy mode ;) )
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sgoo:
I can confirm that restoring the end address of main memory to 85MB in this Native Kernel

D3DM and OpenGL_ES run decently smooth and fast . It is sufficient to replace 4 system graphics DLL ;) .

A little example :

A new rom asap :D .
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jeanpiere:
hey would you mind sharing your 85mb kernel, or at least what steps you used to create it??
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UltimoJedi:
GOOD WORK my Friend ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sunsetdk:
Which 4 dll's do you replace and from where do you get the replacements?

What did you do to restore the end address to 85 MB?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Dukenukemx:
I love whatever interface or application you're using. You wouldn't happen to have a link to that rom would ya? :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sgoo:
... òps !!! :D the kernel ... here ... you are :
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UltimoJedi:
This Native Kernel works very well ! :eek:

Good work my friend :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ahmedfikry:
can you please share the wm6.5 native OEM drivers folder that works with that NK ram folder?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sunsetdk:
I now got the 85 MB NK.

But what drivers have you used to get the openGL to run? And how to you get the carusel on SPB to work? I have been crawling the forum for more than 10 hours to find any usefull info.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jeanpiere:
Hey what kitchen, and oem packages are u using?

I cant seem to get opengl support even with this kernel. i'm using ondraster's kitchen with new ui. And oem packages from jjblaster. Please your help would be really appreciated.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sgoo:
Hi, I have post an answer in the other 3D :) .
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UltimoJedi:
I am using one "experimental kitchen" [Engine] given me from one great friend (MaJa) of mine and to the moment it is not still definitive to be able to publish it. We are in phase of test :D

But I don't believe that has depended on the used kitchen the use of a ROM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] burtcom:
hardware keyboard woes

My native Kernel ROM based on 28205 is fast and stable, but one problem I can't seem to solve is with the slide-out keyboard -- the mapping is wrong.

This is on a non-branded stock Kaiser, but its acting like a Tilt, I think. Fn-Q presents the @ character instead of !

As suggested earlier in this thread, the only "native" driver I'm using is touch.dll

I've tried setting registry, but nothing has worked (yes I did a soft reset after each change)

... tried specifically setting CWSLayout to 0 (it did not exist in HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD)

... also added CurLang"=dword:00000409 in the same location

... made sure HKLU/Mui CurLang was set to 0409

Any of you also seeing this with your english 409 ROM?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] burtcom:
Well, curious -- I just applied the Tilt keyboard fix, and now the hardware keyboard is fine :)

Huh -- this is definitely a stock HTC, and I thought Tilt fix was for Tilt devices with non-tilt ROMs...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Mars.C:
:D:D:D:D:D:D:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] evanchan3313:
Here strongly support the idol:D:D:D:D:D:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ADB100:
Apologies in advance...

Its been a while since I cooked any ROMs for my Kaiser. PC has been wiped since then and I am almost back to square one :(

Anyway I have the latest osKitchen and have imported the latest official ROM (RUU_Kaiser_HTC_WWE_Brightpoint_US_3.29.422.1_radio_sign_25.83.40.02_1.70.18.02_Ship.exe). I have managed to rebuild this version (19212) without problems - I had lots of customisations that I need to recreate but I should be OK with that. However I want to build a 6.5 ROM and am struggling a bit.

I have downloaded the 3.57 OEMDrivers and the 6.5 NK (both the 101 RAM & 107 RAM) and replaced the items in the kitchesn (\Sources\Devices\HTC Kaiser\OEM Packages\HTC Kaiser Packages & Sources\Devices\HTC Kaiser\Profiles\default\OEMXIPKernel). I am using the latest 23680 build. When I rebuild the ROM it seems to build OK and flash to the device but it hangs at the 2nd splash screen. I don't see the 'Clearing storage' message on the 2nd splash screen but I can hear the beep when I would normally expect to align the screen.

If someone could point me in the right direction I'd appreciate it. I have searched....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] puppet008:
路过的.....:o
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dany547:
pls post a link with a WM 6.1 101mb Nk.exe
[General Questions and Answers] aprilhachem:
I upgraded my treo to wm 6.5, and it's giving me a lot of problems now. I have the official wm 6.0 version. Is there a way to downgrade from 6.5 to 6.1? thanks!
[General Questions and Answers] rakataka:
here is my problem guys. i was trying to flash my htc touch 2 sprint it with Raphaelhardspl(wrong flashing) and in the process the screen went blank. i was trying to do it one more time and my PC is asking for qualcomm cdmd technologies msn driver, every time i connect the phone to my PC. i have tried it soft reset. and hard reset wont work. any suggestion will be thanks full. thank you. the main problem is that my pc wont recognize ??

WHOEVER solve my problem will pay 50 buck via paypal
[General Questions and Answers] denco7:
The quickest way to brick your phone is to try to flash it with programs meant for other phones, which it appears you have done.( bricked )

Try putting it into bootloader and flashing stock rom , or try mtty.exe, but if your pc won't recognize it and your screen shows no life, it is probably toast. Does it at least have hardspl on it . ?
[General Questions and Answers] rakataka:
yes it does have hardspl. there have to be a way that my pc will recognized it. i think.
[General Questions and Answers] ElCondor:
As denco7 said, have you tried getting into the bootloader mode?

Hold volume down and press the red button with your stylus.

Connect your pro2 to your PC and if it connects the word 'serial' will change into 'USB'.

If it does, your device is not bricked.

I suggest you flash Hard-SPL again, and make sure to follow the instructions exactly! Don't think you can do it just in a minute, just take your time.

Then flash another ROM by using MTTY (see here) and there you'll get some instructions.

Good luck!
[General Questions and Answers] rakataka:
it wont go to boot loader mode, when i connect it to the pc it begin to charge and noting happen , then suddenly the light go off and the pc detect a driver is missing quaccom etc. does any one know about that this driver. :(
[General Questions and Answers] ElCondor:
I've had that before... that the MSM technology qualcomm **** is asking for a driver.

There's a driver replacement (used before mtty). You can try to install that; altough I don't think it will help.

If you can't get into bootloader your device is (probably) bricked.

What you can also try is getting your battery, sd-card and simcard out of your phone and leave it for an hour. Then put the battery only back, and try to boot.

Does your phone start when you press the start button? So do you feel a vibrate or somethin like that?
[General Questions and Answers] rakataka:
no it wont start but maybe by following that MTTY my pc read it, i will try it. . it doesn even bibrate it just that power light show when that phone its charging thats all.

thanks for you comment guys.
[General Questions and Answers] ElCondor:
That's strange.

There's one last thing you could try: the ultimate hard-reset

Some time ago I bricked my diamond. I tried all available sofkey combinations.

Then, suddenly, my device vibrated like 3 tiimes very loudly.

It didn't still boot nor go into bootloader.

But after about 4 hours it booted!

I only don't know what the combination was... something like VOl UP + VOL DWN + lOCK BUTTON + RESET.

Just try some combinations, maybe it works for you.maybe not, but you could try it.
[Touch CDMA General] szman22:
Does anyone else have to jump through hoops to get ADB to recognize the Vogue? It seems just like a collosal mess of drivers, which is even worse because different Android builds (2.01 vs 1.5 vs 1.6 vs 2.1) all behave differently.

I'm running Win7 and android via Haret and it is a complete cluster-xxxx of USB drivers. I have the android sdk usb drivers installed, but windows wants to install mass storage and/or usb composite. Then, there is a driver called HTC Dream Composite ADB interface. ADB works for me most of the time when this driver gets installed.

Earlier, I had adb working. Then I accidentally unplugged my usb cable. Plug it back up and I'm back in driver hell.

AARGH! Is this just my problem?
[Touch CDMA General] roberto188:
Similar problem

Nope...I've got a similar problem...windows recongnizes my Android ADB device...then when i try to use ADB or ADB explorer...it just won't connect and says their are no devices present. If i leave the hardware screen open...it will put an ! over my device when I try to access it via ADB. Still haven't gotten it to work...gonna try a differnt comp. I'm trying to push the new GPS libs.
[Touch CDMA General] mrkite38:
are either of you running x64?
[Touch CDMA General] roberto188:
No

Windows XP 32 bit.
[Touch CDMA General] gigermunit:
wasn't it said plenty of times that adb currently doesn't work in windows on nand?
[Touch CDMA General] mrkite38:
Who said nand? I count one haret and one no comment.
[Touch CDMA General] gigermunit:
im supposing if it doesn't work in nand, i doubt it would in haret.