Related
XDA Mobile 6 Release 4 Cooking Pack
Build your own flavor of XM6r4
By popular demand, I'm releasing the XDA Mobile 6 Release 4 (XM6r4) Cooking Pack. Basically, this is just a the ROM / SYS / OEM folders that I used to build XM6r4. Those so inclined, can download this and build their own flavor of XM6r4 and customize it to their heart's content.
NOTE: This is NOT a Kitchen, but is "guts" of the kitchen. I personally used anichillus' HyperCore Kitchen to build XM6r4, and recommend this kitchen. But since most all of the Wizard kitchens I've seen are almost all alike, these folders will probably work in the majority with only minor changes.
How to Use the Cooking Pack
First you need to download a kitchen and install it per the instructions for that kitchen. NOTE: This thread is NOT for supporting kitchens, and is NOT for general questions on cooking. It will be for the usage of this Kitchen pack. I'll reserve the next post or two and will add specifics that are posted about how to make this work with other kitchens if there are changes needed.
After you get your kitchen setup, then download the XM6r4 Cooking Pack. Unzip the file and place the ROM, SYS, and OEM folders under the kitchen directory where it belongs (for HyperCore, these folders will go under the Build folder).
At this point you are basically ready to cook.
Where are the options.xml files???
My style of cooking may be a little different than what some are used to. For me, rather than having a BuildOS that is loaded with lots of options, I personally prefer to have an OEM directory which (in most cases) is what is going into the rom, and another directory for things that won't go into the rom (OEM-Hold or somesuch. Call it what you want). Then all I do is take OEM packages I don't want in the ROM from the OEM folder and move them to the OEM-Hold folder. By doing this, they won't be part of the rom (and you don't have to deal with checking and unchecking things in BuildOS). If you don't like this style, then feel free to create options.xml files for each of the OEM packages and you can then check and uncheck to your heart's content. Some of the packages do have options.xml, so you can use those as examples on how to set that if (if thats what you want).
If you want to add things to the rom, you'll need to create the OEM packages and drop those in the OEM folder.
Final Notes
This is an exact copy of the folders I used in building XM6r4. I have not upgraded or changed anything (so the same bugs and features in the built version will be in this cooking pack). A lot of the pieces originated from mattk_r and theloon's kitchen work for the 318 ROM. Then I've made changes to those bases to create the XM6 series. Most OEM folders found in theloon's kitchen work will probably work with this cooking pack (but no guarantees).
Official Download Sites for XM6r4 Cooking Pack
HTTP Download
Happy Cooking!
.
Extras
Splash Screens
Attached are the BMP and PNG files used for the splash screens on XM6r4. While the graphics are not mine originally (I've found them here in the forums but asked permission for their use) some modifications are by me. If you are using HyperCore, there are tools for building splash screens in that kitchen.
NOTE: For me, the first splash screen (the so called HTC Logo, which I used the Cylon image for) tends to be the trickiest one. If the file size and complexity of the graphic isn't just right, the screen will not show up properly. If you are trying to build your own htc logo splash screen and having problems, use a graphic editor to convert it from BMP to GIF. Then close the image completely (important) and then reopen it, and then convert the GIF back to BMP. This will sometimes work. If not, then convert the image to a jpg and increase the compression level to be below 50% (the image will start to get grainy and not look as good so you'll have to play around with this). Then close the image and then reopen the jpg then convert it back to a BMP and try again.
Corrected Arcsoft MMS Folder
You can download the Corrected Arcsoft MMS Folder from HERE. Then just extract the contents of this zip file to your OEM folder and it will replace the existing Arcsoft MMS folder. This will fix the bug that was in the original XM6r4 rom. Note that due to filesizes in this patch, you will NOT be able to rebuild a full XM6r4 with this patch. You will have to remove something else as the patch makes the entire rom too big.
Basically this patch is an example of the dangers of compressing things. I had compressed some of the larger MMS files, and it turns out that this broke parts of the MMS application.
This space is intentionally left blank
Thanks...
downloading the cooking pack right now...
love your work...
and thanks for sharing the pack and the roms...
Do these folders have the mms folder fix that was an addon cab in the R4 thread?
thx mfrazzz,
this is the best "Sinterklaas kado" (it's typical dutch) I could get. I've alway great fan of your rom and customized to my own settings.
one question, your three start up screens, are they included? because there are nice.
I just hope this doesn't mean you're not going to develop for the HTC Wizard anymore ...
I am convinced that this is a great base ... so ...this means you're Santa and you came early this year
Take Care !
anichillus said:
I just hope this doesn't mean you're not going to develop for the HTC Wizard anymore ...
I am convinced that this is a great base ... so ...this means you're Santa and you came early this year
Click to expand...
Click to collapse
Lets just say that "Santa" hasn't come yet (its only 8-Dec after all!!!)
I meant to do this after XM6r3 but just never got around to doing it. Wanted to release this now before I started doing anything else.
famewolf said:
Do these folders have the mms folder fix that was an addon cab in the R4 thread?
Click to expand...
Click to collapse
Nope, they don't. I'll update the second post with the replacement files for the MMS folder. Thanks for reminding me. Watch for this later today / tonight (US Mountain Time).
daheufster said:
this is the best "Sinterklaas kado" (it's typical dutch) I could get. I've alway great fan of your rom and customized to my own settings.
one question, your three start up screens, are they included? because there are nice.
Click to expand...
Click to collapse
Thanks for that! And thanks for the reminders of the splash screens. I'll upload those later too.
The second post has been updated with a file containing the splash screen graphic files, and a download link for the XM6r4 patch (which is just a replacement of the Arcsoft MMS folder in the OEM packages).
Are the splash screens just BMPs with the extensions changed?
I've tried several times to make a flash that JUST changes the splash, and what I get simply won't load - it goes to 90% and freezes....... 320x240, BMP, 24 bit color depth - which should be right.....
Genesis3 said:
Are the splash screens just BMPs with the extensions changed?
I've tried several times to make a flash that JUST changes the splash, and what I get simply won't load - it goes to 90% and freezes....... 320x240, BMP, 24 bit color depth - which should be right.....
Click to expand...
Click to collapse
No, you have to "cook" the splash screens. In HyperCore there is a script to help you do this. Or the old tried and true way that I've used in the past is from this post: http://forum.xda-developers.com/showthread.php?t=284006&highlight=splash
But its not just changing the extensions... You have to build the .nb files that then get built into an .nbf file.
Aha! Grabbed the other package... thanks.
BTW, the Hypercore Kitchen is flagged as having a nasty Trojan embedded in it by my antivirus software..... your R4 kit doesn't work with the 1933 kitchen..... it appears to, but doesn't build the image - it looks like there are some missing pieces......
Oh, it also doesn't work with Faria's kitchen..... hmmm.... are there things missing in general?
Genesis3 said:
Aha! Grabbed the other package... thanks.
BTW, the Hypercore Kitchen is flagged as having a nasty Trojan embedded in it by my antivirus software..... your R4 kit doesn't work with the 1933 kitchen..... it appears to, but doesn't build the image - it looks like there are some missing pieces......
Oh, it also doesn't work with Faria's kitchen..... hmmm.... are there things missing in general?
Click to expand...
Click to collapse
Try the following:
Grab the r4 rom...extract the rom to the kitchen of your choice then replace the folders using the r4 kit provided...then replace the mms folder (fix) then tweak.
Uh, what tool do I use to extract the rom?
That one's a new one for me
your roms is very nice and thanks for sharing the pack !!!
Genesis3 said:
BTW, the Hypercore Kitchen is flagged as having a nasty Trojan embedded in it by my antivirus software..... your R4 kit doesn't work with the 1933 kitchen..... it appears to, but doesn't build the image - it looks like there are some missing pieces......
Oh, it also doesn't work with Faria's kitchen..... hmmm.... are there things missing in general?
Click to expand...
Click to collapse
I haven't downloaded the HyperCore Kitchen lately, but there was no Trojan or Virus in it previously (a few months ago). What antivirus software are you running? I know in the past some kitchens (I believe Faria's did this too) were flagged with virus and stuff when they really didn't have them.
As for the 1933 kitchen, why does it now work? Can you give more specifics? Sometimes some of the kitchens just require the os.nb file to be named differently in the ROM folder.
BuildOS appears to run normally but the CreateROM program fails with an error.
I will see if I can figure out what's up with it....
If its just a naming problem that's easy enough to fix.
Genesis3 said:
BuildOS appears to run normally but the CreateROM program fails with an error.
I will see if I can figure out what's up with it....
If its just a naming problem that's easy enough to fix.
Click to expand...
Click to collapse
Is the error near the end of task? When CreateROM fails with an error normally this is caused because the amount of extra OEM packages exceed the maxium ROM size. When this occures CreateROM gives an error.
No, it was right up front, but it appears that I found the problem - it was a rename on the original OS file that was required.
It builds now..... I need to sort out the size issues (they're still there) and then play with this .vs. my 1933 custom hack job to see what I prefer.
The only "gotcha" I have open on my 1933 build right now (a mix of V1 and V2 which appears to work very well in general) is that the camera won't record video - there are obviously some DLL problems somewhere, and just stuffing the Camera 3 package in there from some of the other kitchens does not fix it - so its in the base OS somewhere.
dang I been trying to figure this out all day.
I copied the oem and sys folders into the hypercore build directory, put in files that I did not want into the package folder, but I dunno how to build the os from there
is there any hope that we can upgrade the ultimate 9502 to wm6.1 soon ????????
There is another thread on this a little further down, but so far i-Mate support is telling some people yes, and some people no - so I'm not sure.
so y cant some1 cook wm6.1 for imate 9502?
6.1 soon?
Signs of activity, or just wishful thinking?
http://preview.tinyurl.com/57sshv
Well we are trying to develop rom for imate 9502 but we are not getting enough support from the community. Check out the link in my signature and help the community in whatever way possible, so that we can build a working rom for the device.
This turned up in the Imate forums today. If anyone can translate from Polish it'd be great.
UniCom (Polish i-mate distributor) informed that i-mate confirmed OS update to WM 6.1 for 9502 and 8502.
The exact date will be announced soon.
Source:
http://www.gsmonline.pl/portal/news...M,Professional,6.1,w,smartfonach,marki,i-mate
Edit: Same link as above. Sorry.
samy.3660 said:
Well we are trying to develop rom for imate 9502 but we are not getting enough support from the community. Check out the link in my signature and help the community in whatever way possible, so that we can build a working rom for the device.
Click to expand...
Click to collapse
Hmmm. Perhaps that's because you've set up shop outside of the community? 9502 users are thin on the ground as it is, so why fragment that user base further by trying to divert them off to a lightly used forum? There's a wide audience of ROM experts here at xda-dev, so wouldn't it be more productive to share your ideas here? I have enough forums to check everyday as it is, so I don't really need another one with limited content and only a handful of users.
OK, the 9502 hasn't got its own section on xda-dev (and isn't likely to). But neither has the i780, and that hasn't stopped very successful collaboration and development for that device right here at the home of ROM cooking.
Ineedtoys said:
Signs of activity, or just wishful thinking?
http://preview.tinyurl.com/57sshv
Click to expand...
Click to collapse
Are we there yet?
Answer -NO STILL
So I personally doubt Imate will do it, I think its more likely they won't be around for long given the reports I read.
eg.
HTML:
http://msmobiles.com/news.php/7733.html
I think this is interesting!
"Sales for the six-month ended of September are estimated at $20.6 Million compared to $46.2 Million for the same time last year. This resulted in an estimated operating loss of $10.8 Million loss compared to $29.4 Million loss for the same time last year. Our cash position is at $11.2 Million and stock at $9.1 Million with debtors of $3.9 Million and creditors of $2.6 Million."
If I am reading this right it sounds like a good thing sales are about half because now the losses are only about 1/3. To me it's obvious why they are delisting and the customer support is legendary for all the wrong reasons.
Looks like we need to make our own ROM if my 9502 will work like its supposed to.
calibration code !
Originally Posted by corollatercel View Post
So i've been having problems with the screen alignment on mine since i had one spot on my MDA screen that was dead and my screen was cracked so the alignment wizard basically got stuck in limbo when I tried to calibrate it. SO basically what I had to do was download PHM Registry Editor and change the registry key touch referenced in here.
Afterwards I used the remote alignment tool (attached) to retrieve the correct settings from the correctly aligned mda(after changing the registry key then rebooting the device) then made sure the file was saved on my pc....normally it's saved by default in the C:\Program Files\Code Factory\Remote Screen Alignment directory. The file was called WIZA200.dat. I did a soft reset then when the alignment screen came up I did the skip function in the remote screen alignment application and it automatically read the proper calibration from the wiza200.dat file and then properly calibrated my mda now my screen is properly calibrated even though i never ran the alignment wizard.
So here are the Instructions folks:
1. Download the latest activesync and connect your mda to your computer and verify your device is connected(not as guest)
2. Perform a soft/hard reset on your MDA then tap your screen to start the screen alignment wizard
3. Download the remote screen alignment tool attached and install it on your machine.
4. Download the wiza200.txt file attached and rename it to WIZA200.dat then put it in the C:\Program Files\Code Factory\Remote Screen Alignment directory on your computer
5. Ensure your MDA is connected to your pc(A green activesync Icon usually indicates a connection )
6. Open the remote screen alignment tool on your pc meanwhile your phone be displaying the alignment screen wizard.
7. Click SKIP in the screen alignment tool.
Assuming everything went fine a message box displaying "The operation has been completed successfully. Your device will be restarted." should pop up on your computer and your device should restart. Afterwards your phone will run the files it always does when you do a soft/hard reset then you touch screen should be properly calibrated and work fine.
thanks in adv !
Downloads Available on 2nd Post
Hello Everyone! This will be my FIRST attempt at cooking a Kaiser ROM, so please bear with me. I know this needs some work, so let me know what you find, and I'll do my best to keep up.
Fair Warning: I'm dealing with an illness that keeps me down a lot, so I may not always be available to answer questions. So, if you know an answer to a question, please feel free to answer if I'm not here. I'll try to fix things as quickly as I physically can. Thanks for your understanding.
This is WM6.5 23405 - I've spent MANY hours making an Ervius Visual Kitchen for the Kaiser. I started with my Trinity Kitchen, then modified it for the Kaiser. I then cleaned up the OEM for the Kaiser a bit (it was a mess, still is somewhat).
Notice the new Task Manager accessible from the Start Button (Tap & Hold). It also "CLOSES" programs when the X is tapped. Or, you can choose to Tap & Hold the X to minimize. Thanks to amarullz! Find more information over here.
Each Different Version will be listed on Page 2 (Might Spill onto Page 3) with the Download Link for each. In each Download Link I will post the Self Extracting Kitchen, an RUU_Signed.nbh, and an AutoFlash file.
What is AutoFlash you ask? I've taken the RUU file, added the Flashing Program, and Packaged it all up into an AutoExecuting AutoFlashing Program, and, it's a smaller download than the RUU alone. Pretty cool huh? Yes, others have already done this, but I'm going to make it a standard practice from now on.
"AutoFlash (tm), Making Flashing Socially Acceptable, One Package at a Time!"
My recommendation for Flashing is:
Make sure you have Hard SPL on your Phone.
Be sure your battery is at least 50% full.
Start your phone in Tri Color Screen mode. Steps below
--Unplug your phone from USB
--Hold down the Power & Camera Buttons
--While still holding them down, press the Reset Button using the Stylus
--Release the Reset Button, but continue to hold the Power/Camera buttons until you see the Tri Color Screen
--Plug in the USB cable (if asked about installing a driver, do this), You should see USB in the White Box)
Now you can Flash.
Run the AutoFlash file for the ROM you've selected, or Flash using the Standard Flashing Program included in the Kitchen.
After flashing, please be patient as it takes a LONG time to start up.
Enjoy!
I recommend using the SkyFire Browser as your default.
Thank you to EVERYONE on XDA. Chefs, Programmers, Da_G, Cookers, Users, Noobs, everyone! You've ALL helped me to be able to do these. I'm sure I'll learn a LOT more as the days go by.
NEW!!! Color Themes!!! In Attachments!!! Also, Enable or Disable Startup Sound
Use these to Change the colors of the Today Screen, Menu Screen, and Dialer. Portrait & Landscape!
I'll fill this in when I get back from Dr's...
DOWNLOAD NOW It's currently uploading, but I have to go to bed. It's 2:38am and I have a full day of Dr Appts today. Let me know what still needs help. PS, I did notice the name when connected to ActiveSync, I'll fix that later. As I mentioned in the first post, I've used my Trinity Kitchen and modified it for this.
Immediately After Flashing, Please Setup the Keyboard following My Short Video Tutorial. Best viewed HD and Full Screen
You will find that I like to share what I get accomplished. Anytime I get a Kitchen, Cab File, Package, or anything else working, I'll be posting it for you to use.
I prefer the Ervius Visual Kitchen, and did not find one, so I created my own. Thanks for trying it out!
Also mine...
Wellcome new cook !
Appreciate your work!
I was getting ready to flash JJblaster's new ROM, and had yours on file, so thought I'd try. I barely use Manila anymore. I like the over all set up, nice and lean with MS Voice Command and Office, and plenty of room to put in other things I like. (JMLtoday, iContact) I'm not a "power" user. . not much internet stuff except wi-fi when its convenient, but seems plenty feature-rich for my daily use. . . phone, calendar, and Excel. It moves pretty fast.
Two criticisms:
1. The response to the stylus is laggy from time to time. (could it be the SPL I'm using? 3.34 - - - works great with jjblaster's ROMs)
2. There is a little flutter as the screen roles. This is most noticable in the start menu section. . I suppose it is a graphics thing with the colorful icons.
I don't know how things will be during daily wear and tear. . just thought I'd post some preliminary observations. Thank you for making your ROM available. Hope you will cook many more.
PS - I like the wallpaper
touch response
With regard to the laggy stylus response, I found this tip at Sakajati's site:
[HKEY_LOCAL_MACHINE\SYSTEM\GWE\Touch\Filter]
"MinimumTapTime"=dword:28 . . . change the tap time Decimal value from 40 to "0"
Now the response is very good.
Hi SuperSport
Congretulation!
I would like to cook a kaiser wm6.5 Rom for a friend and i see HTC Kaiser 6.5 Native Kernels, is your kitchen include this?
Regards
chanvi93 said:
Hi SuperSport
Congretulation!
I would like to cook a kaiser wm6.5 Rom for a friend and i see HTC Kaiser 6.5 Native Kernels, is your kitchen include this?
Regards
Click to expand...
Click to collapse
Unfortunately, no, it does not. I am trying to research for you what needs to be changed to make 6.5 NK work.
Then, hopefully, you will be able to do the Magic you are famous for.
Ok,
Here is a working Kitchen with the 101M Native 6.5 NK and the needed OEMDriver Folder.
Good Luck, and let me know if you need anything else.
http://www.mediafire.com/?2zygdjjyyyt
Thanks Supersport
It work but pb with backlight after wakeup, i search....
ok i use my own ervius kitchen 1.8.2 all work fine now, kaiser is a fantastic phone, will uploade for you SuperSport with com5 21551 and com2 21897 as soon as i have HS Internet.
Hi SuperSport
This's my first basic Kaiser_Kitchen_WM6.5 in 2 languages, wwe and fra, with 2 builds, COM2 21897 + COM5 23551.
I have tried all 4 versions and its 100% working.
I begin to seperate drivers and soft from OEMAPPS, for change to other newest in futur like mega or iolite with manila etc..., but have not time to finish may br next wk.
Regards
EDIT: I have added AMeBa_v0.7.1b'soft to close app in 23551 so don't need TaskManager.
hey folks. i'm new to this rom cooking thing. i'm using the Kaiser Kitchen. I've loaded a base rom into the folder and run the Begin command prompt. now i'm stuck. i have no idea what OEM/SYS items i can get rid of and what i need to keep. i'm just trying to build an extremely lite rom that has manila 2d with the weather under the clock on the home screen. but i don't want to go and delete something that i need, so i'm not comfortable doing any editing just yet. can anyone give me a breakdown of what this stuff is? or even point me in the right direction if it's already posted (which it probably is, i'm just not sure what to search for)? i'd greatly appreciate it. i'm enjoying this rom cooking quite a bit, but, like i said, i'm pretty new to this. i've never taken any classes or anything, so i don't understand some of the terms/procedures used on this site, so please use layman's terms if you reply to me. again, i appreciate your taking the time to help me out, even if it's just a finger pointing me in the right direction.
Hope it doesn't take you too long to read.
first off what's your base ROM (the ROM that you downloaded and put inside the BaseROM folder) and then I could tell you what to get rid of. By the kaiser kitchen you mean the one from the wiki correct?
I'm going to need more info on how you are putting the weather on the home screen (e.g. CAB, Package. etc.) and your BaseROM to tell you accurately what to do.
as for adding in that weather package, first make sure the manila version you are using is 2.x or more. I would say don't make a package out of the CAB (if that's what you are using to put the weather display on the home page). Instead go into the OEM folder and look for the OperatorPKG folder. Enter the OperatorPKG folder and look for a file named "config_operator.txt" (without the quotes).
Mine looks like this:
LOCK:Enabled
TSK: \WINDOWS\Htc.tsk
CAB: \WINDOWS\AMfix.cab
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\fixyoutube.cab
CFG: \WINDOWS\config_PT.txt
I'm positive yours will look different. Pay attention to the "CAB: \WINDOWS\"insert CAB file name here"
What you are going to do is take that weather CAB for manila and put it in the OperatorPKG folder. Now go in the "config_operator.txt" and add this string:
CAB: \WINDOWS\"name of the cab file you just put in the OperatorPKG folder, INCLUDING the .cab extension (ex: M2Dhomeweather.cab)"
After cooking and flashing the ROM and setting up your device it will auto install that CAB and you should be set to go.
Now once you tell me the baseROM you are using I can tell you what is mostly junk in the OEM folders you have.
Also in case you are curious.
In the "config_operator.txt"
A "TSK" represents a theme and will make the device load a certain theme.
A "CAB" (obviously) represents a CAB file and will auto-install the CAB file.
A "CFG" represents the next config.txt file and tells the device to look at that config file next.. There are 4 total in all used for different purposes but they all do the same thing more or less. In the "config_operator.txt" ALWAYS make sure the
CFG: \WINDOWS\config_PT.txt
string goes last. It will skip anything else after itself if you do not have it as the last string.
P.S. - Always get an opinion from more than one person
Using the above process you will be using 2x the amount of space .cab & install
Also when things are cooked in they are faster accessible than via .cab install.
Regards removal of OEM/SYS a very good guide
Universal Tutorials for Customizing any Device and Cooking
Holds alot more valuable info than just what your after
clsifford said:
hey folks. i'm new to this rom cooking thing. i'm using the Kaiser Kitchen. I've loaded a base rom into the folder and run the Begin command prompt. now i'm stuck. i have no idea what OEM/SYS items i can get rid of and what i need to keep. i'm just trying to build an extremely lite rom that has manila 2d with the weather under the clock on the home screen. but i don't want to go and delete something that i need, so i'm not comfortable doing any editing just yet. can anyone give me a breakdown of what this stuff is? or even point me in the right direction if it's already posted (which it probably is, i'm just not sure what to search for)? i'd greatly appreciate it. i'm enjoying this rom cooking quite a bit, but, like i said, i'm pretty new to this. i've never taken any classes or anything, so i don't understand some of the terms/procedures used on this site, so please use layman's terms if you reply to me. again, i appreciate your taking the time to help me out, even if it's just a finger pointing me in the right direction.
Click to expand...
Click to collapse
BTW, you are better off using visual kitchen.in that way you tick what u need and untick what you don't. If you find out that you needed it you simply tick it again...LOL!
kaiser:
well, first off, i'm using the HyperDragon IV as my base ROM. it's the only one i can find that actually has the weather on the home screen. i love the ROM, don't get me wrong, but it just has a lot of extra stuff in it that i don't need, and i'd like to have that storage space. this ROM actually has the home weather already built in. updates automatically according to the GPS (i'm assuming since it always displays the weather for the city i'm currently in). very handy for taking a quick look rather than having to press any buttons (i'm one of those "no phone while driving" people). however, when i add the Blue Galaxy theme to it, it changes the clock and takes away the home screen weather. i'm very new to this rom cooking business, ie: all i know is what i've either taught myself or looked up on XDA, so i have no idea how to make packages from cabs or anything like that. but reading above about where to put the cabs to auto install with the new rom doesn't seem too difficult. i can visualize it in my head (i spent QUITE A WHILE looking at those files yesterday! haha!). the HyperDragon IV rom is about 110 MB, and it moves a bit slow, but that is my ONLY complaint about it. i'd like to get to the point of being able to build a rom from scratch, but i think breaking one down and rebuilding it to my liking is a better starting point. i'm checking into taking some classes on it. i really enjoy working on my phone and i think if i had some formal training on it, it could be something that i LOVE to do. i just have no grasp of the technical jargin used, so sometimes i'll find a post pertaining to the topic i'm looking for, but i get lost in trying to understand some of them, you know? same thing with cars: i can work on them all day, but i have no idea what most of the parts are even called, much less what they do. i actually have 2 Tilts (my wife thought it was too complicated and got a different one), so i use one to practice on and check out new roms, and the other for everyday use. last night i installed the Hyperdragon IV rom on the extra and printed out the HTCHomeSettings file (with home screen weather) and printed the HTCHomeSettings file from my regular use phone (Blue Galaxy theme installed so no more home screen weather) and was getting ready to print them out and compare the differences between the two. just out of curiosity, would that have done me any good?
Off-hand question: NRH, is that North Richland Hills? if so, nice to see a fellow Texan! i live in Arlington, born and raised.
Stylez:
yeah, that's what i understand. phone operation is much quicker when software is built into the rom. thanks for the link. i was looking for something along those lines yesterday, just couldn't find it. i appreciate it. i've actually looked up A LOT of usefull info that you've posted on here, so thanks for the knowledge as well!
Staxx:
thank you, thank you, thank you sir! i actually posted a request last week for suggestions on a more beginner level user friendly kitchen, but got not a single response (last i checked). that's exactly what i was looking for: something where i can just check what i do and don't want. i was using PPCKitchen at first, but after cooking 3 roms that were just as big as HyperDragon IV (110+ MB) the program started giving me error messages. the frustrating part was that it wouldn't give me errors until it was almost done building the rom. that's quite a while to wait and quite a bit of time (by my standards) wasted to find out that the program isn't going to produce anything! so thanks for the suggestion. i'm going to go search for and download it right now.
To All:
thanks again for the help and advice. you guys are life savers! i can usually figure things out on my own. i like to think i'm smarter than the average bear. but sometimes i just need to be pointed in the right direction, or have things translated from technical jargin to layman's terms. i appreciate yall taking the time to help me and answer my questions. it's nice to see that there are still people in the world willing to help complete strangers. so thanks again guys! i'm sure i'll probably have more questions arise, so i'll probably be posting those as well. i try not to post anything that has already been answered, but sometimes i can seem to find exactly what i'm looking for, even if it is posted already. there is A LOT of info on XDA, but that's a good thing, or a GREAT thing i should say.
Kaiser:
by the way. i'm looking to cook a WM 6.1 ROM with:
blue galaxy theme, but with weather on the home screen, of course
bluetooth function
data connection auto config
manila 2d (dont need the customizer)
quick menu
quick gps
google maps
kaiser tweak
S2U2
BT enabled voice command
BTAudio Toggle (not the btaudio on/off but the toggler button that has the little headphones on the icon)
smartphone tracker
activesync
camera
opera 9.5
***prefer but don't have to have:
volume control, the one that is all black with the white volume bars running up and the vibrate and silent buttons directly underneath
there is also a contacts list that matches the above volume controls, black background with scrolling
wow! that actually looks like a lot now that i've written it out! i actually have all the cabs for the above mentioned items (except camer,activsync, volume controls and contacts list). i also have the cab for manila 2d with the weather on the home screen, but i haven't been successful in installing it WITH the home screen weather working, or even on the screen. i believe it's actually an add on. it's not the full manila 2d, just suppoesed to replace the clock with the flipping clock and add the weather under the clock (which it doesn't seem to do), so i think it may be about useless.
that's really about all i want in the rom. i'll most likely be using the HyperDragon IV rom as my base rom, since it already has the home weather. after that (and some more practice) i may try to learn how to take another lite or naked rom and add the home weather clock to it with manila. that's my goal anyway, to learn how to add it to a rom that doesn't already have it or manila. well, i'm off to download and check out that other kitchen. thanks again for the willingness to help me!
You should probably ask the chef of this ROM for help I'm sure they would be more than happy to help you. They would know about everything in the ROM and would be able to help you the most. If not then I'll download Hyperdragon and look at it in the kitchen.
@off-hand question - yup.
kaiser:
well, i think i'm going to download a stock WM 6.1 rom to practice on first. i'll see if i can't get in contact with the chef in the mean time. i got it off of the Sakajati website. not sure if that's going to make any difference in contacting the chef, but i'll see how it pans out. thanks again for your help.
Hello!
I’ve searched around this board and Google, over the last 30min and have not found an answer yet.
I installed a rom by Kumar, which I happen to be very, very happy with. However, I have come across a problem that I hope can be fixed. When you set up your stock US T-Mobile HD2 to ask for a 4-digit password after an amount of time has passed with no activity, it does so with a nice looking HTC skinned/themed screen.
Is there a cab floating around out there that can give back to me, that nice looking screen rather than the ugly Windows Mobile default screen I now have?