Database Info

Midget v0.1 Vanilla Crossbow Rom (Based on Helmi's Unreleased Rom)

Unknown to me, the 'clean' source i was given to make this ROM was actually heavily customized already to fix some major bugs and flaws by Helmi_C. He deserves the main credit for this ROM, but i will continue to keep it up to date - no hard feelings?
Hi, as you may know I've been here (xda-developers) for quite a while, In this time i have been learning the art form that is rom building, my teachers (at least i think of it like that include maimach (How can he be human?), Tuatara (God of all things WM5 on BA), Lt.Cmdr.Ivan, Helmi_c and many others (thanks everyone, sorry if i didnt mention you)
Finally in December 2006 i had a chance to use this knowledge i have gathered when i acquired a pre-release version of WM6 from a good friend (you know who you are ) Since then i've spent days tweaking and fixing bugs in this rom, i wanted to wait until it was perfect to release, but due to recent event s i think now would be the best time, so i present you with My first ROM for Universal and my First Crossbow rom...
Current State of things:
Bugs:
Video Calling doesn't work (im working on this - thanks bepe)
In REALvga mode (addon cab) if you have owner information or password set to display on boot then you will hang your device, hard reset needed. im stuck as to what is causing this, anyone got any ideas?
Occasionally after flashing the phone will reset into bootloader - not load OS. a quick "set 14 0" in mtty fixes this (again anyone got any ideas?)
Features:
Version 5.2.318 (Build 15341.0.0.0)
Most Stable Crossbow rom for universal (verified by two beta testers who have tried them all)
Free Storage 40mb
Free RAM 30mb
Cache Tweaks for Performance
New Comm Manager hacked for speed and look (WM6 Background)
No Bloat
Coming soon:
Video Call Drivers
AKU 0.1
Well i've rambled on too long here ill give you the links
Rapidshare.com:
http://rapidshare.com/files/12143324/midget_1990_v0_1_vanilla_wm6.rar.html
Addons:
REALvga mode (Read the bug above first!):
ftp://xda:[email protected]/Uploads/Universal/midget_1990/midget_1990_realvga_wm6.cab
Tweaks and hacks:
Includes: Oxios Close apps (great tool) and map to backlight button. (ability to change backlight button also)
A collection of IE tweaks for faster and more stable surfing
Enable b/g wifi mode
Set keyboard and audio priority to better values
Enable cleartype for both modes
Change cache sizes for faster device
ftp://xda:[email protected]/Uploads/Universal/midget_1990/midget_1990_tweaks_and_hacks.cab

BRAVO mate BRAVO
my 1st universal Rom upgrade and I am really happy with this one
Mainly because of the
MASSIVE 30 mb RAm
Cheers

anyone tried tomtom with it?
i wana try this tonight but cant find my god damn usb lead!

Tom Tom works great (both vga modes)

hello there midget... I thought u said that u hv 40mb ram?? U make me busy with ur statement there my friend...lol...
so basicly its a modify to vanila version and added vga functionality? well, if u dont mine send me ur default.hv let me see what difference that u make my friend...

I found one more problem. I tried to use oZVGA mode in this release and most of the icons disappeared. The taskbar became blank.. i couldnt see the start button. oZVGA doesnt work with this release of crossbow it seems.
Please try to fix that Midget.
Thanks Awesome release.

Thanx Midget

helmi_c said:
hello there midget... I thought u said that u have 40mb ram?? U make me busy with your statement there my friend...lol...
so basically its a modify to vanila version and added vga functionality? well, if u don't mine send me your default.hv let me see what difference that u make my friend...
Click to expand...
Click to collapse
I said 40?! that would be nice lol, must have been a typo
bear in mind that some of the tweaks are separate in the cab file i linked to.
try the comm manager too, its MUCH faster

nuclear said:
I found one more problem. I tried to use oZVGA mode in this release and most of the icons disappeared. The taskbar became blank.. i couldnt see the start button. oZVGA doesnt work with this release of crossbow it seems.
Please try to fix that Midget.
Thanks Awesome release.
Click to expand...
Click to collapse
did you read what i wrote?
you need to install my vga mode cab (i wanted to save space so i dnt include it) this install the icons etc and ozvga

Midget_1990 said:
I said 40?! that would be nice lol, must have been a typo
bear in mind that some of the tweaks are separate in the cab file i linked to.
try the comm manager too, its MUCH faster
Click to expand...
Click to collapse
yes u did!...lol... and I do everything... I means everything... the maximum size I get its 31-32mb something... lol... btw congrat mate...
hacked CommManager?? with what? upx it?

helmi_c said:
yes u did!...lol... and I do everything... I means everything... the maximum size I get its 31-32mb something... lol... btw congrat mate...
hacked CommManager?? with what? upx it?
Click to expand...
Click to collapse
reshacker to change the interface (new background, the buttons are still in the making - each button has 5 part so it takes time) to make it fit in with wm6 and upx

Why do I only get 26 of free mem?

Extended Rom is seen as a drive and Outlook use it to store mail attachment (impossible to change the storage used) For other office program you can use SD CARD.
And it's impossible to hide Extended Rom
So I use an empty extended Rom

I'm having issues to flash this rom.
When I click "Upgrade" button, my uni reboot, and i can't upgrade it.

symbol no more works

poussin69: if im not mistaken i set extrom to install from /storage card/extrom (sorry i forgot to mention that) i've only recently got my uni so i though /storage for attachments was normal, ill look into changing it for you
Also what is symbol?
ZeD:
1) are you connected via a hub? this is bad.
2) try putting in bootloader mode first
3) did you included RUU.conf?
4) no idea sorry

you have a sym.txt file in windows directory so, when you type
a and use the "sym key" you will switch to à
e to é è ê .....
it was working with WM5
(I change the keyboard country to french as usual (azerty keyboard))

Midget_1990 said:
ZeD:
1) are you connected via a hub? this is bad.
2) try putting in bootloader mode first
3) did you included RUU.conf?
4) no idea sorry
Click to expand...
Click to collapse
I have tried to put into bootloader first, but I cant upgrade. I included the RUU.conf.
I'm not using a usb hub also.
Maybie a old bootloader version?

Ok, I got it.
Flashing the rom now.
After i get the version of the rom on the upgrader I put the device on bootloader and press "Upgrade".

poussin69 said:
you have a sym.txt file in windows directory so, when you type
a and use the "sym key" you will switch to à
e to é è ê .....
it was working with WM5
(I change the keyboard country to french as usual (azerty keyboard))
Click to expand...
Click to collapse
hmm, i didnt even knew that existed ill try to add it for the next release

Yikes!!!

Okay,
I have had my wizard for about a year now and in that time have flashed countless ROMs without any major problems, but yesterday I came as close as I ever have to bricking my device, and the crazy thing is that I have no idea why. I am hoping that the "real men of genius" here can help me figure out what the freak happened, or specifically what I probably did wrong
Before anyone asks, yes my phone is SIM and CID unlocked and it is a G3.
I recently moved from Core 2.0n to mfrazzz XDA Mobile 6. I really liked it but with mattr_k's easy kitchen and stripped down base I figured I could play with it a little to get some more of the apps and settings I like in it from the get go, and save the space without the ones I don't. I had been playing around with the core kitchen and the first kitchen mattk_r upped so I had a pretty good idea of what to do.
here is what happened as best as I can remember ( I should have taken notes as it was happening but I was too freaked out!)
I created the OEM directory and copied the reg tweaks and packages that I wanted from Pandora's Box (v2). I ran Build OS and selected all and it completed without problem. I ran createROM.bat and no problems there. I went into flashing, built the nbf and flashed. The flash went fine with no hang ups.
When the device restarted after flashing it went to the first splash screen and then stayed white. I left it this way for 10 minutes and then it was still like this I tried a soft reset. It reset fine but stayed white. I then tried flashing back to the original mfrazzz ROM but when it got to 95% the flash tool errored out and closed. The phone was stuck with the progress bar at 95%.
I freaked out a little and then rembered that I still had a copy of wizard love on this computer so I put it in bootloader mode and then flashed that. That got the phone back up. I then tried reflashing my "cooked" ROM. It loaded this time, but the today screen was a white background and some of the today plugins were extremely distorted and it just wasn't right.
I reflashed wizard love, and then reflashed the mfrazzz's original XDA Mobile. My phone is now fine.
Any ideas on what the heck happened.

Just guessing here....did you messed with the splash screens ?

anichillus said:
Just guessing here....did you messed with the splash screens ?
Click to expand...
Click to collapse
Not on purpose, followed the steps above as far as I can recall.

You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
If you only did the OS, what is the size of your nk.nbf? If its too big it wouldn't have flashed.
BTW: Welcome to the world of rom cooking... I've scared myself a few times

ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
mattk_r said:
ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!
Click to expand...
Click to collapse
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!

boto said:
You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking
Click to expand...
Click to collapse
well it would definitely be a tragicomedy!! or perhaps a nail biting thriller! I wanted to give as much detail as possible since I hate it when someone posts, "I bricked my device, what happened?!?!?! PLEASE HELP!!!!"

dcdivenut said:
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!
Click to expand...
Click to collapse
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.

mattk_r said:
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.
Click to expand...
Click to collapse
I don't think I entered WWE for language, but I did everything else, and didn't do anything extra. That is something to try...

UPDATE!!
I am not sure that something as simple as typing WWE in the language field is what made the difference but I did and it worked. On my home computer I redownloaded the kitchen, base and OEM packages.
I first flashed it with nothing added to the OEM folder and it worked
Then I added to the OEM folder and that worked.
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Any help from the pros in getting this up woudl be awesome! Hopefully others will be able to use them as well.

dcdivenut said:
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Click to expand...
Click to collapse
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .

mfrazzz said:
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .
Click to expand...
Click to collapse
SWEET!
Soft key - Check
Time Sync - Check
I found this in the .rgu file in the x-mfrazzz apps. is this for the softkey app or something else?
[HKEY_LOCAL_MACHINE\Services\Stk_service]
"Dll"="\\windows\\STK_Service.dll"
"Description"="STK Service"
"DisplayName"="STK Service"
"Context"=dword:00000001
"Keep"=dword:00000001
"Order"=dword:00000005
"Index"=dword:00000005
Windows Live search - In your OEM folder there are two folders, WindowsLive and WindowsLive_DPI_96. These are both currently also in the SYS folder of mattr_k's base so wouldn't this throw an error? I know I am missing something stupid here.
Ring tones - Is there anyway I can build mp3's into the ROM? I tried placing them in the x-mfrazzz settings folder in my SYS but that didn't work, even though they get built into the windows directory. I looked in the .rgu and there doesn;t seem to be anything about where to place these
PHMReg Edit - I thought I remembered you saying something about being able to export reg settings in the correct format. I was playing around with this and the closest thing I could find was backup. That created a .rbk file but I get gibberish in notepad when I try to open it. My thought process here was to use get all the reg setting the way I want, export them, get them into a .rgu file and then build them in. Any ideas?
How do I get it so that ini_tray.lnk is not automatically in startup?.

Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?

dcdivenut said:
Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?
Click to expand...
Click to collapse
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)

mfrazzz said:
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)
Click to expand...
Click to collapse
Cool, will check when I get home, any thought on post above?

Hmmmmmm...
Seems to me your mind was on your woman and not your Wizard... just a thought,ehehe!
Congrats bro!

My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...

Madcap180 said:
My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...
Click to expand...
Click to collapse
dc just got engaged.....

Congrats DC ... if you ever need someone to pick the lock on that ball and chain, let me know...j/k

v2.0 Integrating Touch Files into 318 Kitchen [kitchen updated 7/9/07 @ 21:37 PST]

I need some help debugging the kitchen with the touchflo files.
For those who are sent the new kitchen; as you test and find solutions, please post what you did.
I wanted a sperate thread for just these specific objecives.
Here is the objectives:
To retain the ability to build a ROM with or without TouchFlo
To have only ONE seperate camera package that will work in any configuration
To allow portions of the touch software to work seperately should TouchFlo not be installed
I know there are other threads dedicated to debugging the touch software, however this is targeted at just the kitchen integration.
Current issues (v2):
Streaming Media isn't showing up in Programs, won't open.
Speed Dial hasn't been confirmed working or not.
No images for Beam - still need pictures!!!
Windows Live won't connect. Cab fixes issue. Need to find missing entries
Black Keyboard doesn't show numbers across top row. Need to find setting.
The power button will put phone into "standby" mode (basically screen and Wifi off), but won't power down.

318
I'll be glad to test. I was working on a 318 Kitchen but didn't get very far.

Too many Duplicate files.
Going back to work on my own kitchen I was much further along than what you have here.
My suggestions:
1) You should at start by deleting duplicate files. I can build a rom and flash it with my kitchen, I can't build with yours w/o getting one dup file error after another.
Please update, I will try to devote some time to your kitchen.
Thanks

NP. I'll update shortly.

My Files
I deleted dup files in my kitchen but I think I deleted one to many, now I can build, and I can flash using shelltool but it gets stuck at splash screen. Damm where did I go wrong??? I feel like a dumbass!

Hopefully this one will work a bit better. another 30 mintues till it's up.
The boot issue is probably related to the files in the OEMAPPS folder. There are some dll's in there that I found are super sensitive to this build - too bad I wasn't more careful in documenting what they were.

Documenting.
Started documenting now! Too much going on now not to, especially after my last mistake.

Test
So have you actualy built and started testing a rom with your kitchen?

I've been doing that for days... but I've tried a number of different combinations and this one seems most promising - though by no means is it ready. 1413 has by far been the easiest, but I still believe the 318 is the best choice.
I'm gonna be out until Monday night, so this is my last attempt for a few days

I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.

Whiterat said:
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Click to expand...
Click to collapse
If you could, it would be much appreciated. Anything to help get closer to a fully functioning setup

Ok, so i tested the oem folder from the reTouched Beta thing. I included everything in there but my problem is that TouchFLO does not function the way it is supposed to. With what you guys are doing, have you verified that TouchFLO even operates correctly?

I thnk the touch flo isn't all its cracked up to be..I ran the reTouch wasn't a fan..its not as fast as any rom..only thing I like is the dialer and the cube

I actually have a good feeling about it. I ran the french rom for a couple days - and other than not knowing most of what it said (glad I know the OS and took 2 years of french in high school) I was very pleased with the performance. Specifically the speed at which the screen "rotated", responsiveness, and how quickly the contacts scrolled on the screen was impressive. Enough to keep me interested well into the night

so matt, think you can make a cab from it? the cube that is lol.

Here you go:
http://rapidshare.com/files/40068930/OEM.rar
Click to expand...
Click to collapse
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)

Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
So if what you are saying is true I should be able to create cabs from the correct?

AFAIK It wont be possible due to the touch driver not being replacable, you might be able to rename touch.dll and then update the registry entry.

cleaning up
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!

hanzieman said:
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
Click to expand...
Click to collapse
For what I see whiterat folder are some reg tweaks that you'll probably use anyways, and as far as folders to remove it might be less of a hassle to simply add the packages that you use that are not there.

3.53.DK.02, UC 2.0 Compliant, Supa-Clean [5/23/2008]

Hello XDA! Let's start off with a few thanks. Pof, Jscepi, Kyphur, Bepe, XDA for all the tools and knowledge. Cuboosh, Sirooga, Packetmangler, Tdusen, Drbowden, IDJ and everyone from my 3.02 thread for helping me work out the bugs. Without further ado:
3.53.DK.02 Based on CE OS 5.2.19213 (provided by incognitho)
Storage: 164.66MB Total, about 3MB In Use, about 162MB Free
Program: 85.32MB Total, about 31MB In Use (after soft reset), about 54MB Free
3.53.DK.01 Based on CE OS 5.2.19213 (provided by incognitho)
Storage: 165.79MB Total, about 3MB In Use, about 162MB Free
Program: 85.32MB Total, about 31MB In Use (after soft reset), about 54MB Free
3.51.DK.01 Based on CE OS 5.2.19209 (provided by incognitho)
Storage: 165.29MB Total, about 3MB In Use, about 162MB Free
Program: 85.32MB Total, about 31MB In Use (after soft reset), about 54MB Free
This rom starts where my older roms left off as far as "stripped down-ness" . My roms have AT&T connnection settings by default so no need to install and run HTC Connection Setup if you are an AT&T customer. Keyboard is Tilt layout so install KaiserKeyboard.cab attached below to change to Kaiser layout. Now onto the deets:
3.53.DK.02
- All Tweaks removed (cab included in rar)
- Removed Comm Manager (cab included in rar)
- Put back SIM Manager
- Clear Storage runs after flashing (no need to hard reset, but I still recommend you do)
- Overall more refined (I started from scratch on this one to work out some bugs)
3.53.DK.01
- starts where 3.51.DK.01 left off, nearly identical
- custsat.dll replace with no2chem's dummy file
- AUTD in CommManager replaced with 3G Toggle, cab also available below
3.51.DK.01 (4/24, radio not included)
- starts where 3.02.DK.05 left off
- removed help files from OEM_Lang_0409
- removed bmp's associated with help files
- removed DRM from OEM_Lang_0409 and SYS
- removed several dll's that are a part of Audio Manager and Streaming Player
- replaced NetCF 3.5 and SqlCe 3.5 with NetCF 2.0 and SqlCe 3.0 (for compatibility)
Stuff I noticed in 3.51:
- Addition of disptools.dll in OEMDrivers with new registry settings to go with it! I have no idea what this does and I'd love it if someone could enlighten me.
- AutoShortcut.exe and a shortcut to it that gets place in StartUp. Don't know what this does either.
- HTCCpl.cpl changed to MyCpl.cpl and mxip_HtcApps_translation.provxml reflects those changes. These cpl's control some items under "Settings".
- New bluetooth registry settings! not sure if this is related, but the blue light no longer turns on when you reset.
- What happened to the Program memory? 85.32 down from the usual 101.32.
Issues:
- Microsoft Voice Command versions older than 1.6.19209 will cause lockups.
- Typing area does not show with IM+.
- No video when using CorePlayer in QTv mode.
- I don't use TCPMP, but I'm guessing this still does not work either.
- Using cleartype in landscape mode causes text to disappear.
3.53.DK.02 Download Linkage:
http://rapidshare.com/files/117111999/3.53.DK.02___CABS.rar.html
see here for ringtone size limit fix http://forum.xda-developers.com/showpost.php?p=2227911&postcount=58
3.53.DK.01 Download Linkage:
http://rapidshare.com/files/114733628/3.53.DK.01.rar.html
http://www.4shared.com/file/47558388/89ca384e/KAISIMG_353DK01.html - mirror provided by sirooga
3.53 ROM Base (for cooking, download both parts):
http://rapidshare.com/files/115118417/3.53.DK.01-OEM-ROM.rar.html
http://rapidshare.com/files/115115367/3.53.DK.01-SYS.rar.html
3.51.DK.01 Download Linkage:
http://www.filesend.net/download.php?f=f7a49564aea29389db9d30afa52f22ee
http://www.megaupload.com/?d=5UH62WA2
http://rapidshare.com/files/110092950/3.51.DK.01.rar.html
3.51 ROM Base (for cooking, download both parts):
http://rapidshare.com/files/112782518/3.51.DK.01-OEM-ROM.rar.html
http://rapidshare.com/files/112779560/3.51.DK.01-SYS.rar.html
Radio Thread (1.65.20.29, Thanks to P1Tater):
http://forum.xda-developers.com/showthread.php?t=391714
Radio Linkage (1.65.14.06):
http://www.filesend.net/download.php?f=3ddce0d0b38d500a2108715d20a01677
http://www.megaupload.com/?d=SM6CWVNB
http://rapidshare.com/files/110097140/KAIS_Radio_Only_1.65.14.06_CustomRUU.rar.html
DO NOT INSTALL RADIO 1.65.17.10 IF YOU WANT TO DOWNGRADE IT LATER, I'M NOT EVEN GOING TO PROVIDE A LINK FOR IT, Thanks ATW !
I've started to mod my cabs to install to their own folders under \Program Files instead of \Windows whenever possible to keep the directory as clean as possible. 3.51 has 814 objects in \Windows after flash and opens wicked fast through File Explorer. Voice Command still seems to be in the grey area for posting so PM me for the my new 19209 version that installs to \Program Files\Voice Command. Help files are removed from my new cabs. Cabs attached below with more to come.
Update: There were some issues with 3 of my cabs and I just removed them from my first post. I will re-up them to my second post once I fix. I need to apologize to the 23 members that downloaded HTCQuickGPS 1_00_220821_00, the 17 members that downloaded MSInternetSharing 6.0 and the 15 members that downloaded MSRemoteDesktopMobile 6.1.
click me if you wanna give a me a little somethin'

4/24 - Fixed QuickGPS and InternetSharing cabs attached.
5/13 - Added ArcsoftMMSComposer 5_0_31_19.cab

Great, time to flash again...

Hung on the Windows Mobile 6.1 screen right after the flash. Had to hard reset to get past that point.
Loading up my apps now to see how it works.

akadonny said:
- I don't use TCPMP, but I'm guessing this still does not work either.
Click to expand...
Click to collapse
People might check THIS link to get TCPMP working on your ROM.
Have to admit that I haven't tried it with your ROM. There are at least 3 new ROM's available from the last two days. So I have to check out a lot
Great work btw on your new release! Keep it up!

akadonny, Did you make the APN/RIL changes on this AT&T build for us BBC users?

GSLEON3 said:
akadonny, Did you make the APN/RIL changes on this AT&T build for us BBC users?
Click to expand...
Click to collapse
No. Didn't have any requests for this so never thought to include it. Give me a few minutes and I'll make one for ya.
Edit: I just took a look at your instructions for "Multiple Data Sessions". Was about to make a new rom when I checked my registry. If the only change that needs to be made is:
<parm name="AGPSNVSetting" datatype="integer" value="5" />
then my rom is good to go for BBC. Happy flashing!

I just reflashed to the 3.02 because this one kept locking up on me. I don't me SOD either, I mean total lockup with the backlight on full brightness for 5-6 minutes...
I might try the multi connection ROM shortly.

idj1975 said:
I just reflashed to the 3.02 because this one kept locking up on me. I don't me SOD either, I mean total lockup with the backlight on full brightness for 5-6 minutes...
I might try the multi connection ROM shortly.
Click to expand...
Click to collapse
Did you install Voice Command? Using any version other than 1.6.19209 will cause your phone to lockup. Took me a while to figure this out, but found it installing 1 proggy at a time. Also, radio 1.65.14.06 is required.

akadonny said:
Did you install Voice Command? Using any version other than 1.6.19209 will cause your phone to lockup. Took me a while to figure this out, but found it installing 1 proggy at a time. Also, radio 1.65.14.06 is required.
Click to expand...
Click to collapse
no voice command, had the radio from your first post installed too...
*however* i didn't flash the radio first... i just realized that. i'll flash the radio & then flash the rom to see if it gets any better.

idj1975 said:
no voice command, had the radio from your first post installed too...
*however* i didn't flash the radio first... i just realized that. i'll flash the radio & then flash the rom to see if it gets any better.
Click to expand...
Click to collapse
I didn't know the order of flashing mattered? I flash my phone so much while testing my rom before release that I lose track of these things. I do however always do a master reset after each flash.
Anyways, let me know how it goes. I've been using this rom since yesterday without any issues.

akadonny said:
I didn't know the order of flashing mattered? I flash my phone so much while testing my rom before release that I lose track of these things. I do however always do a master reset after each flash.
Anyways, let me know how it goes. I've been using this rom since yesterday without any issues.
Click to expand...
Click to collapse
i think it might since it hung during startup before i put the radio on.
reflashed the radio & then the rom a little while ago. loading up my apps to see if i get locks again

Right, well I found out what's killing it.
BB Connect seems to be making it die, which makes me wonder if it's the data connection or BB Connect...
EDIT: Loaded Alex's "clean" ROM & it doesn't seem to have the same issue.
EDIT2: Can't get BBC to connect on Alex's ROM, so 3.02 it is for a while longer...

landscape mode - issue with text
akadonny,
Loaded this new ROM on my AT&T Tilt and notice a weird issue (didn't have this with the previous version). In regular mode typing text via the onscreen keyboard is visible. When I switch to landscape mode all text that can be typed disappear or it doesn't appear until you go to a new line. I noticed this when I went to enter my Personal Information.
Otherwise it's working fine for what I use on the device so far.

akadonny said:
DO NOT INSTALL RADIO 1.65.17.10 IF YOU WANT TO DOWNGRADE IT LATER, I'M NOT EVEN GOING TO PROVIDE A LINK FOR IT, Thanks ATW !
Click to expand...
Click to collapse
Hopefully there will be a fix for this soon. If not I will have to revert to plan B.

Mirrors
3.51.DK.01 Mirror
1.65.14.06 Mirror

idj1975 said:
Right, well I found out what's killing it.
BB Connect seems to be making it die, which makes me wonder if it's the data connection or BB Connect...
Click to expand...
Click to collapse
Sorry about that idj. I don't use BBC so I can't really test this for ya.
ecltech said:
Loaded this new ROM on my AT&T Tilt and notice a weird issue (didn't have this with the previous version). In regular mode typing text via the onscreen keyboard is visible. When I switch to landscape mode all text that can be typed disappear or it doesn't appear until you go to a new line. I noticed this when I went to enter my Personal Information.
Click to expand...
Click to collapse
I didn't understand you at first, but I think this may be by design. Just to be clear you are saying that you type using the on screen keyboard entering your Owner Information and when you switch to landscape the on screen keyboard closes until you tap the screen again. Is this right? I tested this and the on screen keyoard seems close under any app where you can type when you switch to landscape. I think I do remember the on screen keyboard staying open in landscape before.
AllTheWay said:
Hopefully there will be a fix for this soon. If not I will have to revert to plan B.
Click to expand...
Click to collapse
ATW, there are a lot of Kaiser/Tilt users out there including myself that owes you many thanks for catching this early.
sirooga said:
3.51.DK.01 Mirror
1.65.14.06 Mirror
Click to expand...
Click to collapse
woohoo! more mirrors!
Thanks much, Sirooga

Ok. So I loaded up the straight bloatware ROM & don't have any of the issues with an immediate lockup when BBC is installed.
Maybe when something was taken out it broke something else in another way that wasn't visible?
At least the ROM is decently speedy for a full on vendor one.

thanks for another release akadonny!
Seems to be running well. Does this have a differently sized pagefile?
Thanks,
PM

idj1975 said:
Ok. So I loaded up the straight bloatware ROM & don't have any of the issues with an immediate lockup when BBC is installed.
Maybe when something was taken out it broke something else in another way that wasn't visible?
At least the ROM is decently speedy for a full on vendor one.
Click to expand...
Click to collapse
At what point does it lock up? Installed the software to my Tilt, ran through the initial setup, soft reset when it told me to and now I have a blackberry tray icon. I click on the tray icon and I have several tabs. I've attached a few screenshots. The cab I used to install it is to big to attach, but I downloaded it from here.
packetmangler said:
thanks for another release akadonny!
Seems to be running well. Does this have a differently sized pagefile?
Thanks,
PM
Click to expand...
Click to collapse
I didn't change the pagepool on this one, but it looks like the 3.51 default it 28MB as opposed to the usual 12MB.

This ROM problem is driving me mad!!!

Okay. I have exhausted all possibilities that I can think of for this problem. The last few ROM's I've ported have been fine, except for one thing. After flashing (or hard reset) the ROM displays the splash screen and then goes to the welcome screen (displays welcomehead.96). However, when the LogoMsg.bmp popups up (the text that says, "The device is clearing the storage. Please wait.) it only displays for a few seconds then leaves. A few seconds later the tone that accompanies the "Tap screen to begin setting up your device" sounds. The words, "Tap screen..." do not show. However, a second or two later the tone sounds again, this time followed by the text, "Tap screen to begin...". From here everything in the ROM works fine. I just cannot figure that part out.
The LogoMsg.bmp is located in OEMDrivers, so I thought I might have accidentally removed something from the OEM folder. However, I have not found anything seemingly related. Also, I thought it might have been related to welcome.exe. Though, I've tried replacing it with an older version; still no luck. Unfortunately, I have tried so many things that I cannot remember exactly what all I have tried. I've re-ported XIP's (using Ervius' kitchen and by hand) and SYS's, as well as taking a fresh copy of my base OEM.
Essentially, I am asking if anyone has come across anything like this in your cooking, and if you have any tips. I would be more than happy to upload a copy of my ROM for you to test or upload my kitchen folders. I appreciate any help that anyone can provide.
EDIT: I'll try and upload a video later to show exactly what is happening.

Hi KMFM$
I use an official rom iolite ita for porting the xip e Sys to my kaiser. After cooking i have the same problem that you describe.
After 2 mounth there is some solution... i'm crazy for this problem
Bye
Daniele

i have the same issue when flashing any of the wm 6.5 ROM's. not sure what kitchen the chefs use but it doesnt seem to effect anything.

Well, I have yet to find a "solution" to this. However, I have just simply learn to deal with it. It does not effect the ROM in any noticeable way, and from what I've heard from other chef's, this is common in all new ROMs. Not sure what is going on in the ROM during that time frame, but again, it does not effect the standard operation of the ROM.

well dont sweat it then. yeah, i think its normal for 6.5

yep been a normal thing for all my 6.5's

hi KMFM$
the ROM is 6.1 or 6.5?

When it comes to porting it depends on build ver. ect ect. Its a big try and fail operation for moust of us when thing doesnt work as planned. But to get a true port you have to use m'relloc and manual change values in the modules, there is alot of guides on how to.
On dump of nbh in kitchen it unpacks diffrently (provider to provider or if its a "pure" HTC nbh), anyway the cue is that some of the chef`s use xip files in the ROM folder while other make mxipkernel + mxipkernelLTK in SYS and oemxipkernel in OEM then os.nb+ a folder named XIP in ROM and THAT contains boot.rgu I use the last method which for some reason works best for me.

- shifu - said:
hi KMFM$
the ROM is 6.1 or 6.5?
Click to expand...
Click to collapse
Both, actually. WM6.1 builds from about CE OS 5.2.20757+, I believe, have all given the "extra" notifier. Again, I'm over it. I've just accepted the extra tone and moved on. No big deal.