I was wondering if there is a easy way to make themes that work on the Wizard running WM6. I've looked around and found a couple of tools that talk about Windows Mobile 5 for the Pocket PC. However, a PPC doesn't always have the phone features and I'm not one to assume that WM5 themes work with WM6.
I got the Matt kitchen to work and made the perfect image for my needs. (Thank you 100 times over Matt!)
So now I just want to dress it up the way I like it.
Also, is there an easy way to change the splash screens prior to creating the ROM? When it's still in "dump" mode? I'm guessing there is as a few ROMs here have their own splash screens (i.e. Crossbow Reloaded and XM6). The thing I found on here looks more like an after-the-fact highly complicated way to do it.
Any help from the experts here would be appreciated. I promise...I won't try to sell anything I learn here on eBay! LOL
the-equinoXe wrote a thread over in the Wizard Upgrading forum on how to modify the 3 splash screens. Then the Core Kitchen has this scripted out nicely to make it even easier (IMO). So I use the Core Kitchen for most all of what I do (I use the Ingenetics rom and oem packages by mattk_r in the Core Kitchen, as I just like the feel of that kitchen and how its laid out).
I wish I could just get a zip of your cooking directory. LOL
I downloaded the Core kitchen but I couldn't figure out crap with that. It just installed shortcuts to files or something and to me they are completely random.
The equinox stuff was the complex thing I referred to in my post. I tried following it and I can't even get the screen creation to work. I made a 240x320 24-bit BMP and run the little tool to make the .nb file and his instructions say "It should be exactly 65xxx in size and mine is like 202xxx in size.
ExploreMN said:
I wish I could just get a zip of your cooking directory. LOL
I downloaded the Core kitchen but I couldn't figure out crap with that. It just installed shortcuts to files or something and to me they are completely random.
The equinox stuff was the complex thing I referred to in my post. I tried following it and I can't even get the screen creation to work. I made a 240x320 24-bit BMP and run the little tool to make the .nb file and his instructions say "It should be exactly 65xxx in size and mine is like 202xxx in size.
Click to expand...
Click to collapse
That means your graphic is too complex. Try this:
Pull your .bmp into your graphic program, then save it as .gif
Close the window that had your .bmp that your converted to .gif (this is important)
Open the .gif you just created. Now save it back as .bmp
Now try running the tool to make the .nb and see if it is 63536 in size. If not, then you may have to save it as a .jpg and crank down on the compression (put it to like 50%). Then close that window and reopen the .jpg and save it as .bmp and try again
The HTC Splash screen is the hardest (IMO) splash to make work due to the size restrictions.
OKay, I got it working. For that initial splash screen (the size limited one) I had to drop it down to 16 colors, but it still looks pretty cool.
Now, one of the last steps in making this a truly personalized ROM...I just need to know how to create a new theme.
Also, Mr Frazz, since I know you've done this with your ROMs...is there a way to integrate these splash screens into the building of the ROM instead of installing them after installing the ROM?
If you could help me with these last two steps I will be very grateful!!!
All that is left are a few little tweaks (one I wrote to you about in a different thread) but it is otherwise perfect...for me!
ExploreMN said:
Now, one of the last steps in making this a truly personalized ROM...I just need to know how to create a new theme.
Click to expand...
Click to collapse
First step is grab an existing .tsk that is similar to what you want. Then use a program to pull it apart (a .tsk is just a .cab so any program that can work with cabs will work on tsks. The Core Kitchen has a free tool that does this). At a minimum there should be a stwater.bmp and then registry entries. Possibly there will be a tdywater.bmp also. Those BMPs are the backgrounds.
For building this into the rom, you need to find the directory that has default_stwater*.bmp in it (sorry, not at my computer with my kitchen). Just replace those with what you created (there are multiple versions for screen sizes. I get rid of the 240x240, and just use 320x240 and 240x320 ones).
Also, Mr Frazz, since I know you've done this with your ROMs...is there a way to integrate these splash screens into the building of the ROM instead of installing them after installing the ROM?
Click to expand...
Click to collapse
Yes, the output of the steps will create the .nb files. You just suck those into the nb2nbf program when you build the rom (so you will use 2 more lines).
mfrazzz said:
Yes, the output of the steps will create the .nb files. You just suck those into the nb2nbf program when you build the rom (so you will use 2 more lines).
Click to expand...
Click to collapse
I'm assuming you mean the screen below. I saw that but I was very nervous to attempt it since it didn't offer the same "selection" as the nb2nbf program that came with the equinox stuff. It only seems to understand the one splash screen and not the htc-logo screen. Since it picked the same memory location and everything, I was scared to brick my MDA so I didn't do it. Should I have no fear?
Please see the link to the attached photo to see what I'm talking about.
http://practicalservices.org/build.jpg
I'll give the theme thing a try. Thanks!
ExploreMN said:
I'm assuming you mean the screen below. I saw that but I was very nervous to attempt it since it didn't offer the same "selection" as the nb2nbf program that came with the equinox stuff. It only seems to understand the one splash screen and not the htc-logo screen. Since it picked the same memory location and everything, I was scared to brick my MDA so I didn't do it. Should I have no fear?
Please see the link to the attached photo to see what I'm talking about.
http://practicalservices.org/build.jpg
I'll give the theme thing a try. Thanks!
Click to expand...
Click to collapse
The drop down for the "HTC Logo" gets left blank. nb2nbf tool will know what it is by the number you enter...
3.1 Start Addresses for nb2nbf tool:
1. OS without splashscreens: just set Image name to OS
2. With Splash Screens you add:
SPLASH --> mfrazzz-Splash.nb --> Start Address: 92000000
HTCLOGO --> mfrazzz logo.nb --> Start Address: 9D000000
3. The other start adresses:
Extension Rom: 9B000000
GSM: 96000000
OS: 80040000
Splash: 92000000
HTC Logo: 9D000000
SPL: 91000000
IPL: 90000000
(taken from edHaas tutorial)
here's a link to the wiki entry I started on cooking (using the Faria Kitchen but it applies to them all with just slight differences):
http://wiki.xda-developers.com/index.php?pagename=FPRK_Cooking_Instructions
I detail the steps for filling in the lines, so maybe this will make it more clear. I want to go back and update these pages (or make a whole new one) that is more generic, and one for Core Kitchen (since that is what I use now and really like).
badbert said:
The drop down for the "HTC Logo" gets left blank. nb2nbf tool will know what it is by the number you enter...
3.1 Start Addresses for nb2nbf tool:
1. OS without splashscreens: just set Image name to OS
2. With Splash Screens you add:
SPLASH --> mfrazzz-Splash.nb --> Start Address: 92000000
HTCLOGO --> mfrazzz logo.nb --> Start Address: 9D000000
3. The other start adresses:
Extension Rom: 9B000000
GSM: 96000000
OS: 80040000
Splash: 92000000
HTC Logo: 9D000000
SPL: 91000000
IPL: 90000000
(taken from edHaas tutorial)
Click to expand...
Click to collapse
Sorry to hijack your thread. Move this post if necessary!
Does anyone have the start address for the user area of a rom. I want to try and convert a user area nb file (created by WST) to nk.nbf using nb2nbf.exe then flash to my fone.
It would make a handy backup if it worked!
Related
Just a clarification question...
I found the following files, packaged in a .cab, but don't think I need all of them and don't know where to put the files I do need.
Here's what I have:
4orangeh.dll
HomePage.xml
HomeScreen.dll
HomeScreen_menuF.bmh
HomeScreen_MenuS.bmh
orange.scheme.xml
OrangeHomescreen.home.xml
I'm thinking that the 4orangeh.dll is the only file I need and that it goes in the application data/home directory, and that the other files are associate with a homescreen this particular individual authored. Is that correct or no?
Thanks for the help!
ahhhh
NO.....nononono....thats wrong.
You got the units for ABAXIA (all the files above exept the 4Orangeh.dll)and 4OrangeH.
You may copy the files to /Application Data/Home and register the .dll manually with wm5regsvce.exe.
May not work stable, but you got this: (Link to another Thread by me about the 2 DIFFERENT OrangePlugins called Abaxia and 4OrangeH (4Orangeh includes 10 different Plugins)
ClickMeHard
The Top Image is Abaxia, the second Images are 4Orangeh.Abaxia is poooooor, 4OrangeH really Impressive
Nice arpy!
You wouldn't know where I can find some (English) documentation on how to use this plugin?
erm,no...sorry.Ive created a German Doc with all needed attributes for this Plugin, it was a hard trip and needs a lot of try-and-error-sessions to get nearly all informations about it.
Here is a Howto in German, it includes nearly all Attributes and Parameters needed for 4OrangeH.Not finished yet...there are some more undocumented Features, like FreeMemory,Messages,Ringtone...it is like an OWN HOMESCREEN-PROCESS, so it can Host more than one Plugin in one Line...an REALLY DAMN ****IN **** MISSING FEATURE in my lovely SmartPhone.
the file maybe helpful, if you always create Homescreens...
Thank you. I'll try and see how this comes through a translater.
Kitchen Based on HyperCore and Bepe's new Compact ELF/IN DevPack.
SuperProCore Is On Hold
Ported XIP Caused SD reading Issues and Bluetooth Radio Issues.
(Syrop how's this working on your version?)
This is an OpenKitchen anyone can contribute, this is for the community and those pesky users that come download and never report issues or say thanks.
SuperProCore, is a kitchen based on a new small simple kitchen made by Bepe (as usual).
Of which you will find the original thread here.
What Makes it SuperPro, is hopefully the amount of Packages/Selectable Apps and options that will show up when you start building the ROM.
What Makes it Core is that hopefully i'll learn how to get some of the great tools in the HyperCore Kitchen...
Everythings discusable.
It's because Microsoft doesn't like to listen that most of us hang out at XDA.
Buttttt.... I have to make one Dictotariol Discision.
Help Files Are A No No.
I have never opened one.
And anyone that needs them on their phone should notbe flashing their Phone.
I onlyleave .htm files in that are doubtfull or needed.
6 Years ago when i first flashed my firt HTC/02 Device XDA allready was about downloading a RomCustomizer, choosing your options then flashing it.
Now since HTC got a bit more stuck up and build a lot more security into their Devices other tools are needed and used. And getting your own custom Rom needs a lot of reading and testing.
The thing is the tools are available, and everyone should be able to do cook their own personal Rom.
Now knowing myself i could work 24/7 on this project (I'm a ****ing Chaotic,Paranoid, Compulsive Cooker), but sadly, i also have a life and need to keep myself healthy.
So i'm hoping Some people will jump on this project, even if it means putting "Cooks" out of busines. But hey it will propably also get some people more nights of decent sleep
For now i'm just curious of the opinions and discusions that will pop up.
The Beta v3 ELF/IN Devpack should be enough for some old and new "cooks" (40 downloads) to play with.
So here's an easy deadline, Small update coming next week Wednesday.
Now let's get this thread Sticky.
Extended Elf/Elfin Kitchen for WM6.1
Version 0.6
Download
Nothing New Here.
Requires the Microsoft Visual C++ 2008 Redistributable Package
Bepe's Original Kitchen for ELF/IN.
Just the files to cook with.
So it can be seperatly be updated with New Batch files, Tools and flashing methods.
Why seperate?
Because there are people that know a lot more about writing batch files and apps then me (I know jack ****).
This way if anyone can contribute just to the small kitchen others don't need to download all the seperate packages for the update.
Changelog
XIP ELF/IN Core
Version 1.2
Download
This OEM Package can be used only ihttp://rapidshare.com/files/95392724/ROM.zipn the ELFIN Kitchens.
Why Seperate XIP Package?
Well maybe some people want to get it working in other kitchens
ChangeLog
XIP ELF Only Core
Yeah this one has 4MB PP
XIP taken from hdubli's WM6.1 CE OS5.2.1238 (Build 19521.1.1.0)
Hopefully SOMEONE gets this working.
I have Put the XIP in the Above XIP package SYRXIP (It's Extracted from Syrup's Rom Which Worked, but extracted Bluetooth is dead SD is dead and Wifi IS Dead)(But maybe i remember it incorrect)
OEM Package Update
Version 1.2
Download
This OEM Package can be both Kitchens (If i ever get the SuperProCore Working)
Why Seperate OEM Package.
Well the OEM will become smaller and smaller as parts move into the SYS package and as files get merged or deleted from OEM Package.
ChangeLog
SYS Package Update
Version 1.2
Download
This SYS Package can be both Kitchens (If i ever get the SuperProCore Working)
Why Seperate SYS Package.
Well the SYS will become BIGGER and BIGGER as parts from OEM move into the SYS package as selectable options and new Packages get added to it.
ChangeLog
Rules
What Rules?
Oh Yeah..!
This is not a "I'm Having Trouble FlashingThread"
Packages must have a Byte Count in the <Tip> Field.
Explanation Here.
Add Blank Safety Files To Prevent Overlapping Packages.
Explanation Here.
IMportant Links Thread
Important Reading Material
Cooking Class
Bepe's Beta Kitchen
Suggestions?
Roms Created By Contributors (for the really lazy people out there)
My Personal Rom Cooked With This Kitchen
You?
Explanation Of Byte Field In option.xml file
Well as some people might want to hit a specific target for their end RUU_Signed.nbh file.
It might be handy to have some bytes to give them an indication of how much space a package might takein the file .NBH file.
And maybe if we are very nice and Bepe's very happy, he might consider to Change/Patch BUILDOS to read a new option.xml field with these Bytes to Calculate the end result build, while still in BUILD OS so it wont run when under 50MB?
Methinks that wouldbe a nice feature.
And it would propably need to read a settings.xml file that contains The Core bytes count and wwehter this Security feature is on or of.
What do you think Bepe Nice Idea?
Explanation Of Blank Safety Files
Let's Say there are 5 different Commanagers and you select two?
Well Buildos will tell you which folder itlast processed butit could even be moreacurate orexplanatory.
What if it's a package only containing an registry setting that will kill another registry setting in a similar or different package?
Well if it's known and both packages would have a blankfile with name that will give you the crucial hint where to look for the wrong selected option.
The GlyphCache Packages are a small and explanatory example of what mean.
They all Contain a blank text file without extension name
"You Have Selected Mutliple Options In The GlyphCache Section"
So when you select two by accident you get the regular BUILD OS error but becauseit shows you the file name, it's easier to find.
Again it would be nice if this could be done by BUILDOS by reading another option.xml file.
Oh, nice work! Thanks!
Checking the size in the batch files before we call BuildOS could work!? Well using VBS might be easier... I couls write the target size check if i know how you want to impliment the byte size stuff.
For instance how big is the base? Then each package...
Is it possible to calculate the byte size simply by how big the folders are?
Ouch brain hurts!!
bytespider said:
Checking the size in the batch files before we call BuildOS could work!? Well using VBS might be easier... I couls write the target size check if i know how you want to impliment the byte size stuff.
For instance how big is the base? Then each package...
Is it possible to calculate the byte size simply by how big the folders are?
Ouch brain hurts!!
Click to expand...
Click to collapse
Nah the size of the folder or even just the files that get cooked do not match the eventual size they take in the eventual os.nb or RUU_Sigtned.nbh.
Besides you make the selection of batch/packages inside BUILDOS so depending on that selection you get different outcomes.
At the moment in between living a normal live I run the proces with and then without certain packages and add it to the tip field. So when you mouse over the Option/package in buildos you get the indication.
The eventual base OS i haven't calculated yet as it's not as Base as i want it yet
Good thing there's someone that knows more about some stuff then me.
Tnx
Noonski said:
Stilldon't know what the prefered place is formost cooks to put theirpackages on ELF cooking?
Yes the OEM folders need updates to.
As i'll be merging PROVXML files and taking out parts of the registry to some Seperate SYS Packages to avoid Cooking Conflicts.
All in Time.
Click to expand...
Click to collapse
here is one i like to add to my roms...
Ok, tried it, added some things I usually add, flashed it.
You're saying (or Bepe is) that 19199 is the latest version, yet after flashing it, I'm getting the "old" phone app, not the new one like in Shadow 2.0. Weird? On startup it says Windows mobile 6.09 too... I'm a bit suspicious here
Also, it seems the 8 buttons com manager isn't able to start the wifi properly. PhoneAlarm (accessing the WLAN driver directly) works though.
The esmertec Java package is outdated too, it's back from April.
Otherwise, I'm ending up with much less RAM than Shadow 2.0. Around 3 MB with the same apps installed. I don't understand how that can be ! (8MB PP each)
Positive side is that my touch is much more responsive. I'll keep track of the memory leaks. seems 6.1 handles memory much better, which was really needed with the ELF !
zeflash said:
Ok, tried it, added some things I usually add, flashed it.
You're saying (or Bepe is) that 19199 is the latest version, yet after flashing it, I'm getting the "old" phone app, not the new one like in Shadow 2.0. Weird? On startup it says Windows mobile 6.09 too... I'm a bit suspicious here
Also, it seems the 8 buttons com manager isn't able to start the wifi properly. PhoneAlarm (accessing the WLAN driver directly) works though.
The esmertec Java package is outdated too, it's back from April.
Otherwise, I'm ending up with much less RAM than Shadow 2.0. Around 3 MB with the same apps installed. I don't understand how that can be ! (8MB PP each)
Positive side is that my touch is much more responsive. I'll keep track of the memory leaks. seems 6.1 handles memory much better, which was really needed with the ELF !
Click to expand...
Click to collapse
The Phone skinn is not New to WM 6.1
It's just a ported Phone pad from somewhere....
The emsertec Package might indeed not be new i just grabbed what could get because Shadow Rom was not extractable for Java rgu files.
Nothing has been tweaked memory wise, but if anyone has any ideas.
zeflash said:
Ok, tried it, added some things I usually add, flashed it.
You're saying (or Bepe is) that 19199 is the latest version, yet after flashing it, I'm getting the "old" phone app, not the new one like in Shadow 2.0. Weird? On startup it says Windows mobile 6.09 too... I'm a bit suspicious here
Also, it seems the 8 buttons com manager isn't able to start the wifi properly. PhoneAlarm (accessing the WLAN driver directly) works though.
The esmertec Java package is outdated too, it's back from April.
Otherwise, I'm ending up with much less RAM than Shadow 2.0. Around 3 MB with the same apps installed. I don't understand how that can be ! (8MB PP each)
Positive side is that my touch is much more responsive. I'll keep track of the memory leaks. seems 6.1 handles memory much better, which was really needed with the ELF !
Click to expand...
Click to collapse
Had the same with the comm manager. The one attached works fine.
Added Random Acces and seperate Default Contacts/Addressbbook packages with Security files so they cant be installed together.
(No worries the default is just rgu file.
Added LargeTitleBar to packages thanks Pkoper.
Renamed it to 000_LargeTitleBar tho.
Did Byte Count for Auto Udate. (131072 Bytes)
Now checking what's different with the Commanager you just posted as i allready had an 8 button original one in there.
(i first took out the link.exe but i put it back)
Hmmmmm yours has a different lay out....
Well looks like an extra option package ten don't need all the Graphics and exe's for that in the kitchen.
I'll post what i mean.
A **** it... added Your CommManager anyway. 7-Zip will not take up any more packeging space when files are identical anyway.
Did change UID to be safe.
And added security file will maybe do a byte count sometime.
Keep em Coming.
Maybe tomorow maybe in the weekend, next assignement is make package for new taskmanager and remove it correctly.
And remove SQM (M$ Phone Home) correctly.
probably doesn't belong here, but check this one out http://www.ultimatelaunch.de/
i got the com manager of swiftblade... had similar issues back when i was playing with GTouch....
There is like 4 of us working on a german version of the kitchen at the moment..... headaches!
this one could really grow out of proportion...
There is so much **** one could include.... the size would be just huge
maybe set up a rapidshare thingy for the packages?????
I could probably spare some webspace and traffic...
Where to from here?
Bare WM 6.5 23028 Cooked ROM with unnecessary items removed.
UPDATED on Sept 4, 2009 - 6:05 pm US Central Time
Starting with with September 10, 2009 I have decided to consolidate Bare WM 6.5 builds into only one (1) thread. I suggest you subscribe to the following thread to be kept abreast of future updates:
http://forum.xda-developers.com/showpost.php?p=4469872&postcount=1
http://forum.xda-developers.com/showpost.php?p=4469872&postcount=1
This ROM was cooked with the osKitchen (by OndraSter) which can be found here:
http://forum.xda-developers.com/showthread.php?t=540704
The ROM follows the principle of getting rid of unnecessary items in the Windows Mobile 6.5 source files in order to make as much RAM available on my Kaiser as possible after the installation of WM 6.5. However I didn't want to 'cripple' features that I needed/wanted to have installed.
The result is a vROM that uses about 32 MB of RAM while the Kaiser is idle (and before you install your own applications). That means that you will have close to 70MB of free RAM with this cooked ROM. The size of the cooked ROM flash image (the NBH file) is: 51 MB, leaving 154 MB of storage space available on the Kaiser.
What I may consider 'unnecessary files' may not be considered the same by others. Therefore I am listing the WM 6.5 items that I removed so that you can determine if this cooked ROM fits your needs. I am also enclosing a folder titled "XXXX- Kitchen Removed Sources.zip" which will show you EXACTLY what was removed. If you miss one of the removed items, simply move it back (to the same directory) and cook a ROM.
** General overview of what was removed:
- All of the non-essential OEM and EXT applications which normally ship with "Os Kitchen". I left only the OEM and EXT items which I found to be necessary for the normal operation of the ROM on the Kaiser. If through your own testing you find that one or more are unnecessary please let me know (as I would want to get rid of it as well!)
- Ringtones and other sound files which are not necessary for the normal operation of the ROM (if you miss one or more of those files you can easily put them in an SD card and access them from there)
- All files (CPR, Images, etc.) that relate to a resolution that is not supported by the Kaiser.
- The 'Calculator' application because there is plenty of great calculators for WM PPC out there, and I don't like to have software duplication.
- All "Windows Live" related stuff, because I don't use it.
- All 'games' that come with WM 6.5 because I don't use them, and there is much better games in the marketplace.
- IPSEC related files because I don't use that type of 'virtual tunnel'.
- LiveSearch because I prefer Google.
- Unnecessary Mobile Office templates
- Remote Desktop (because I don't use that software. I prefer RDM+, which I install separately...not in the ROM)
- Task Manager (because I prefer to install Advanced Task Manager...separately, not in the ROM)
- Skybox (because I don't use Microsoft 'My Phone' and related services.)
- Skymarket (because I don't need a software store on my phone)
- All Themes except for 'Classic Blue' (because I prefer to install my own themes...separately, not in the ROM)
- VOIP (because no VOIP application comes with WM 6.5, and VOIP applications like Skype work without these files. So they seem to be a waste of space. If anybody disagrees and can explain the purpose of those files please let me know.)
- Welcome Center (Because I am experienced enough with WM 6.5 that I don't need somebody to guide me)
- All Windows Mobile Widgets (because I prefer to install my own ....separately not in the ROM).
*****
In addition to the file removals that I describe above, I made a few changes which apply to BOTH Chocolate and Vanilla Flavors of the ROM.
- I changed the boot screen back to the original HTC screen that says "smart mobility"
- I changed the animation screen back to the original HTC screen that has an animated HTC logo
- I changed the boot up sound to one that uses aprox 100K
- I changed the Windows start up screen to that of Windows Mobile 7
- I added software to fix the animation start up sound (which didn't work in the original build)
- I added software to fix the animation boot up screen (which was mixed with some other stuff that I removed)
- I added a registry entry that changes the default skin on Windows Media Player to Diamond Portrait.
- I added code to install 'Random Access' in the Contacts Screen. (allows quick access to people by clicking letter on the right margin)
- I added code to change the Start menu to a single column vertical list. I consider that MUCH more useful than the hexagon grid.
- I added a registry entry to remove the 'tap time' that is required when selecting items in WM 6.5 folders.
- I added a registry entry to allow two way phone conversations to be recorded with any 3rd party software.
- I added a registry entry to display 'Recording' in the phone menu (shows up in the menu only during a call)
- In addition the "Chocolate" flavor has these changes:
- Replaced the battery indicator for one that shows the percentage remaining (in increments of 10%), and changes color (White/Orange/Red) depending on the amount of battery remaining.
- Added Advanced Task Manager
- Replaced regular Comm Manager with a 6 item Comm Manager to replace the 3 item one that comes standard with WM 6.5
Screen shots of the "Chocolate" flavor are here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screen shots of the "Vanilla" flavor are here:
NOTE: For those who do not like the Chocolate or Vanilla flavors, I am making available the source files so that you can make any necessary changes to suit your taste. All my changes are in the EXT folder and are clearly labeled with "-PW" after the folder name. So you can choose to keep them or remove them based on your personal needs.
And here is an Spb Benchmark test on a fresh copy of this ROM. I don't know if this type of tests are trustworthy, and I have no benchmark to compare it with. All I can say is that the OS feels very fast and responsive. Don't base yourself on the benchmark. Try it and see if it works for you. It does for me.
Here are the files:
a)You can download the "Vanilla" flavored cooked ROM (which is ready to be flashed directly on your device) from here:
http://www.4shared.com/file/126466054/a9cb5e22/ROM_v23028_-_V_-_1.html
b) You can download the "Chocolate" flavored cooked ROM (which is ready to be flashed directly to your device) from here:
http://www.4shared.com/file/126449658/86532d8d/ROM_v23028_-_C_-_1.html
c) You can download the OEM, SYS, EXT, MSXIPKERNEL, and Bootup and Windows & "Bootup Start up Screens" folders (which have been purged of unnecessary items), and replace the respective folders that are in the "sources" directory of osKitchen from here:
http://www.4shared.com/file/126438245/ec6c73d8/WM_6523028_-_Kitchen_Sources.html
d) You can download the "Vanilla" flavor osKitchen configuration file (which you MUST use in combination with the OEM, SYS, EXT folders shown in item "c" to cook your ROM in osKitchen) here:
http://www.4shared.com/file/126466054/a9cb5e22/ROM_v23028_-_V_-_1.html
e) You can download the "Chocolate" flavor osKitchen configuration file (which you MUST use in combination with the OEM, SYS, EXT folders shown in item "c" to cook your ROM in osKitchen) here:
http://www.4shared.com/file/126442055/2b6eaa83/osKitchen_Configuration_File_v23028_-_C_-_1.html
f) You can download the 'removed' OEM, SYS, and EXT folders (which you can use to verify what I removed....or to move back something that I removed but that you want) here:
http://www.4shared.com/file/126442044/4572ab54/WM_6523028_-_Kitchen_Removed_Sources.html
Enjoy!
IMPORTANT: The only thing that I ask in return for my contribution is that if you find more space savings you share them with me. I left several items in the OEM and EXT folders because I know for a fact that some of those items ARE needed for the correct functioning of critical features such as movie file playback. However some of those items may not be necessary. If you find out that they are not necessary, or you find other files in the SYS folder that could be removed without affecting performance, please let me know by posting a message on this thread.
Tips:
- After the ROM loads, go to phone settings (Start-Settings-Personal-Phone) and in the "Phone" tab select the Ring Type that you want to use. You can put Ringtones in any folder of your Kaiser and they will appear in the "Ring Type" pull down menu. I put them on external storage (SD Card) under a directory called "My Ringtones".
- Missing MMS Options. Standard Builds of WM 6.5 DO NOT come with MMS. To get MMS read other threads such as http://forum.xda-developers.com/showthread.php?t=500869.
- HTC Task Manager missing. The source files do not have the HTC task manager and I don't like it anyway; so I am keeping that away on purpose. If you want the HTC task manager please install it on your own, or cook your own version of my ROM.
- OEM/EXT folders - If you cook your own ROM using my files, you will be able to identify what OEM/EXT packages were added by me, because I follow each package with "-PW". Packages that do not have "-PW" came with the osKitchen, and they appear to be necessary for the proper functioning of the ROM, but I am unable to provide an explanation since I didn't put them together. Contact OndraSter (the maker of osKitchen) in case you have a question about an OEM/EXT package that do not have "-PW" after it.
- Aligning Screen - After you install the new ROM, remember to align the screen. You can do that here: Start - Settings - System - Screen and align your screen from there.
- Move your Kaiser configuration from an old ROM to a new one - Unfortunately the upgrade ROM feature of spb Backup doesn't seem to work properly for this new build of WM 6.5; I successfully upgraded from WM 6.5 build 23009 to 23028 using spb Backup's upgrade ROM feature, but when I tried to upgrade from 23028 to 23034 I got many errors.
- SIM Manager - Left out on purpose. Read solution here: http://forum.xda-developers.com/showpost.php?p=4372512&postcount=79
Known Issues:
Small Fonts get blurry on Titanium / Today Screen, and sometimes images on Today Screen plug-ins (such as Artesea Twmr 6.5r) get distorted. - This issue has been confirmed by other people cooking WM 6.5 23028 regardless of the cook or kitchen used. It seems to be an issue related to the Microsoft code, and I am unable to fix it.
Reserved for future use by the owner of the thread. This is the last space I need.
good job ..thanks
Great Work
Downloading Vanilla
Thanks for providing this. This is exactly what I've been looking for. The base OS so I can install just the apps I want loaded and not have all the stuff I don't care about but have no way to remove.
One thing that would be nice to leave in would be the align screen process that starts up after loading the new ROM. I understand that if you're making your own ROM you can enter the alignment points into the build but when providing it for others it's kind of pain to try and get into the alignment setting when your screen isn't aligned in the first place. It's a minor thing process to go through after loading and you only have to do it once so leaving it in wouldn't be that big of a deal.
wau the available free storage is so massive compare to other 6.5 rom
i will try it over the weekend , install with m2d which is my prefer interface
TomH123 said:
Thanks for providing this. This is exactly what I've been looking for. The base OS so I can install just the apps I want loaded and not have all the stuff I don't care about but have no way to remove.
One thing that would be nice to leave in would be the align screen process that starts up after loading the new ROM. I understand that if you're making your own ROM you can enter the alignment points into the build but when providing it for others it's kind of pain to try and get into the alignment setting when your screen isn't aligned in the first place. It's a minor thing process to go through after loading and you only have to do it once so leaving it in wouldn't be that big of a deal.
Click to expand...
Click to collapse
I purposely didn't include the screen align screen at the start and I don't plan to do it in the future either. But that doesn't mean that you align your to fit your screen. After you load the ROM go to Start - Settings - System - Screen and align your screen from there.
chteh0721 said:
wau the available free storage is so massive compare to other 6.5 rom
i will try it over the weekend , install with m2d which is my prefer interface
Click to expand...
Click to collapse
Good to see somebody from KL in here! I have very good memories of the time I have spent in KL. I was there about 2 years ago leading a project at the Petronas Towers. Really like your country.
witschey said:
I purposely didn't include the screen align screen at the start and I don't plan to do it in the future either. But that doesn't mean that you align your to fit your screen. After you load the ROM go to Start - Settings - System - Screen and align your screen from there.
Click to expand...
Click to collapse
I understand you left it out on purpose and I understand how to fix it. I'm just pointing out that the settings only work for yor device and it's a pain to get to get to without having your screen aligned. Since everyone that downloads this ROM will have to run it why not have run automatically the first time it boots up?
Just a suggestion to make it a bit friendlier. It's your ROM so it's up to uou.
Thanks again for providing it.
TomH123 said:
I understand you left it out on purpose and I understand how to fix it. I'm just pointing out that the settings only work for yor device and it's a pain to get to get to without having your screen aligned. Since everyone that downloads this ROM will have to run it why not have run automatically the first time it boots up?
Just a suggestion to make it a bit friendlier. It's your ROM so it's up to uou.
Thanks again for providing it.
Click to expand...
Click to collapse
A pain to navigate a few menus in order to align screen? I think that's a gross exaggeration. This version of WM 6.5 is finger friendly so you can navigate menus without super precision. So even if the settings are off a bit relative to your device, they will be close enough that you can navigate fairly easily.
I won't incorporate the welcome menu because they use up space and only work ONCE (during installation); so I think that between 'avoiding the pain of navigating a few menus) and having something stuck in memory that only gets used once, I favor the later.
I understand your point, but I will politely disagree.
I just want to say great Roms. I found your 23009 build a couple of days ago and thought it was great..it's just what I've been looking for! Today I upgraded to the 23028 build.
Theres 1 issue that I'm noticing in the 23028 build that I'm not sure is something with your ROM or with the build of WinMo OS itself. The issue is that I cannot setup a sync with Google to have my contacts and calendar synced to my phone. This worked fine on the 23009 build just fine. I have double and triple checked my settings with no luck. It tries to sync..but nothing is actually imported.
Just wanted to give you the heads up!
Keep up the great work!
deafening.quiet said:
Theres 1 issue that I'm noticing in the 23028 build that I'm not sure is something with your ROM or with the build of WinMo OS itself. The issue is that I cannot setup a sync with Google to have my contacts and calendar synced to my phone. This worked fine on the 23009 build just fine. I have double and triple checked my settings with no luck. It tries to sync..but nothing is actually imported.
Click to expand...
Click to collapse
I am afraid that I don't sync with Google. I use Microsoft Exchange and it works perfectly. What do you use to sync with Google. A third party application or an application that is built into my ROM? If it's a third party application you need to report the bug there. Otherwise perhaps somebody else reading this forum uses Google Sync and can help you.
Unable to set ringtones or "auto set" time
yet both work on 23009; so not sure why.
drbowden said:
yet both work on 23009; so not sure why.
Click to expand...
Click to collapse
I set a ring tone by placing it on my SD card, tap and hold the file and it will ask if you want to set it as the ringtone. once you do this you will be able to use the "auto set" time.
Thanks for helping!
betrayed said:
I set a ring tone by placing it on my SD card, tap and hold the file and it will ask if you want to set it as the ringtone. once you do this you will be able to use the "auto set" time.
Click to expand...
Click to collapse
Thanks, I'll try it!
Would this be something I should get if I wanted a bare bones ROM and wanted Manilla 2D? Is that even possible or do Today screens like cHome, M2D, Moto, etc. have to be cooked in to the ROMS? If its possible, will a simple CAB do the trick to install M2D?
Thanks! Much appreciated.
pndragon said:
Would this be something I should get if I wanted a bare bones ROM and wanted Manilla 2D? Is that even possible or do Today screens like cHome, M2D, Moto, etc. have to be cooked in to the ROMS? If its possible, will a simple CAB do the trick to install M2D?
Thanks! Much appreciated.
Click to expand...
Click to collapse
I have no idea. I have never used Manilla as I don't see the need for it.
While working on a ROM (for the hero), I have recently tried to do some theming by small changes (i.e. color changes) to the drawables in the framework-res.apk.
It appears the both for me, and the fellow that is helping me (floomat), these 9-patch files are giving a headache. We prefer editing them in some normal app (i.e. photoshop) but this seems to mess up the 9-patch "code".
I have written a very small program to apply the changes to a 9-patch image without disturbing the 9-patch itself. Note that this program is mainly meant as a "proof of concept" and hopefully one of the apk managing tools will pick up the ball and integrate it. In the meantime it might be useful even as it is (with some scripting around it most likely). Or it might be just a way to prove I am fool and there is simpler way to get around this I am not familiar with
"Program" and source: http://www.sendspace.com/file/sw4atc
(its really too small and simple to be called a program)
Usage:
Code:
java copy9patch original.9.png changed.png
Will copy the changes made to the changed.png over to the original.9.png but keep the 9-patch data of the original.9.png.
Its code (also included) and the way it works is very simple: It takes the size of the original image (i.e. 19x27), without the 1 pixel border with the 9-patch codes - so in our example it will be 17x25. Now it just copied the center 17x25 pixels from the changed.png over the original's center pixels. It has some very basic boundary conditions if the image sizes do not match but this could probably be handled better, possibly just by issuing an error in these cases.
If you want to use my code, change it, do whatever you like with it please do so and I'll be glad to checkout your result!
NOTE: I feel a bit uncomfortable posting this in the "G1 development" section but I see both apktool and apk manager are here....
erasmux said:
While working on a ROM (for the hero), I have recently tried to do some theming by small changes (i.e. color changes) to the drawables in the framework-res.apk.
It appears the both for me, and the fellow that is helping me (floomat), these 9-patch files are giving a headache. We prefer editing them in some normal app (i.e. photoshop) but this seems to mess up the 9-patch "code".
I have written a very small program to apply the changes to a 9-patch image without disturbing the 9-patch itself. Note that this program is mainly meant as a "proof of concept" and hopefully one of the apk managing tools will pick up the ball and integrate it. In the meantime it might be useful even as it is (with some scripting around it most likely). Or it might be just a way to prove I am fool and there is simpler way to get around this I am not familiar with
"Program" and source: http://www.sendspace.com/file/sw4atc
(its really too small and simple to be called a program)
Usage:
Code:
java copy9patch original.9.png changed.png
Will copy the changes made to the changed.png over to the original.9.png but keep the 9-patch data of the original.9.png.
Its code (also included) and the way it works is very simple: It takes the size of the original image (i.e. 19x27), without the 1 pixel border with the 9-patch codes - so in our example it will be 17x25. Now it just copied the center 17x25 pixels from the changed.png over the original's center pixels. It has some very basic boundary conditions if the image sizes do not match but this could probably be handled better, possibly just by issuing an error in these cases.
NOTE: I feel a bit uncomfortable posting this in the "G1 development" section but I see both apktool and apk manager are here....
Click to expand...
Click to collapse
Huh. I've been wondering if this was possible. I haven't tried this yet but if it works, nicely done! I think that this would be a huge improvement and addition to the themeporter programs that are out there. There is a high demand for this in that area and in the area of HDPI>MDPI/MDPI>HDPI conversion. I'm certainly bookmarking this!
Awesome, just checked out ur source, so simple but effective
Anyway wanted to ask if ur ok with me incorporating it into theme-porter ? Link
Wht im thinking is perhaps when "Hdpi to mdpi" is on, it would resize the .9.pngs by 66%, after which it would transfer the .9 data using this program so (9-patch) code is preserved.
Let me know. Thnx
FYI : Just gave it a whirl, works perfectly.
Daneshm90 said:
Awesome, just checked out ur source, so simple but effective
Anyway wanted to ask if ur ok with me incorporating it into theme-porter ? Link
Wht im thinking is perhaps when "Hdpi to mdpi" is on, it would resize the .9.pngs by 66%, after which it would transfer the .9 data using this program so (9-patch) code is preserved.
Let me know. Thnx
FYI : Just gave it a whirl, works perfectly.
Click to expand...
Click to collapse
Maybe my original post wasn't blunt enough, my code is just "proof of concept" because I am bit lazy in this department (themeing tools) - I'd rather spend my time compiling kernels (go figure ).
So my main goal for this post is for developers of apk managing tools and etc. to pick up the ball and go forward with this
And to be even clearer:
If you want to use my code, change it, do whatever you like with it please do so and I'll be glad to checkout your result!
(am also adding this to the main post)
Regarding your actual resizing idea, you might want to resize it with the 9-patch "codes" (in the 1-pixel border) because you want the codes from your original HDMI files just resized. This should work, just be careful with resizing algorithms which average pixels and such. If I understand correctly the edge pixels should be either white or black (defining stretchable and context areas). Need to play around with this until it works well.
Let me know if I can be of any further assistance.
erasmux said:
Maybe my original post wasn't blunt enough, my code is just "proof of concept" because I am bit lazy in this department (themeing tools) - I'd rather spend my time compiling kernels (go figure ).
So my main goal for this post is for developers of apk managing tools and etc. to pick up the ball and go forward with this
And to be even clearer:
If you want to use my code, change it, do whatever you like with it please do so and I'll be glad to checkout your result!
(am also adding this to the main post)
Regarding your actual resizing idea, you might want to resize it with the 9-patch "codes" (in the 1-pixel border) because you want the codes from your original HDMI files just resized. This should work, just be careful with resizing algorithms which average pixels and such. If I understand correctly the edge pixels should be either white or black (defining stretchable and context areas). Need to play around with this until it works well.
Let me know if I can be of any further assistance.
Click to expand...
Click to collapse
Hmm k i'll spend more time with it, perhaps the resizing program im using causes mishaps. Currently when i resize it completely messes stuff up even though the resolution corresponds to a mdpi device.
I'll do the good ol' trial/error n let u know. Thanks for the (proof of concept)
Edit :
Ok so upon using ur code for transferring images of diff sizes u can obviously tell whts up
So one improvement im thinking off, is if the images differ in size, it could draw the border and eliminate anything outside it. Ugh gotta brush up on my java though :S
bump
10 del al char har
bump
I tested it out and it works great! Thanks!
I really hope someone takes this idea and runs with it! If I knew how to code, I would certainly look into this. Maybe I can get one of the Vibrant Devs to look at this....
erasmux said:
While working on a ROM (for the hero), I have recently tried to do some theming by small changes (i.e. color changes) to the drawables in the framework-res.apk.
It appears the both for me, and the fellow that is helping me (floomat), these 9-patch files are giving a headache. We prefer editing them in some normal app (i.e. photoshop) but this seems to mess up the 9-patch "code".
I have written a very small program to apply the changes to a 9-patch image without disturbing the 9-patch itself. Note that this program is mainly meant as a "proof of concept" and hopefully one of the apk managing tools will pick up the ball and integrate it. In the meantime it might be useful even as it is (with some scripting around it most likely). Or it might be just a way to prove I am fool and there is simpler way to get around this I am not familiar with
"Program" and source: http://www.sendspace.com/file/sw4atc
(its really too small and simple to be called a program)
Usage:
Code:
java copy9patch original.9.png changed.png
Will copy the changes made to the changed.png over to the original.9.png but keep the 9-patch data of the original.9.png.
Its code (also included) and the way it works is very simple: It takes the size of the original image (i.e. 19x27), without the 1 pixel border with the 9-patch codes - so in our example it will be 17x25. Now it just copied the center 17x25 pixels from the changed.png over the original's center pixels. It has some very basic boundary conditions if the image sizes do not match but this could probably be handled better, possibly just by issuing an error in these cases.
If you want to use my code, change it, do whatever you like with it please do so and I'll be glad to checkout your result!
NOTE: I feel a bit uncomfortable posting this in the "G1 development" section but I see both apktool and apk manager are here....
Click to expand...
Click to collapse
Can U just tell how to use this code for bulk images?????
pratyush.creed said:
Can U just tell how to use this code for bulk images?????
Click to expand...
Click to collapse
Hmm, haven't used this for a very long time and don't really remember whats going on here.
Still attached is the version which I have on my HD, and it does support bulk images if all the images are in a folder.
If I remember correctly (mostly going by the help that is displayed by running the program without argument):
Code:
fixResPngs drawable-mdpi drawable-mdpi.org
Will go over all drawable-mdpi/*.png files (possibly also sub dirs?! I really have no idea, sorry), and "fix" each such file. If I am not mistaken it needs a "reference" file only for 9 patch files which are identified by their ".9.png" suffix (regular pngs I think are just rewritten without any change which I found improves compatibility). In case of a 9 patch file, the original file with exactly the same name should be found under the directory given in the second argument. For example: If drawable-mdpi/aaa.9.png is processed the 9-patch data will be copied from drawable-mdpi.org/aaa.9.png.
Obviously it also still works on single files. It does *not* work on lists of files or lists of directories.
If anyone is interested in the code, I am sure I have it somewhere (I hope)....
erasmux said:
Hmm, haven't used this for a very long time and don't really remember whats going on here.
Still attached is the version which I have on my HD, and it does support bulk images if all the images are in a folder.
If I remember correctly (mostly going by the help that is displayed by running the program without argument):
Code:
fixResPngs drawable-mdpi drawable-mdpi.org
Will go over all drawable-mdpi/*.png files (possibly also sub dirs?! I really have no idea, sorry), and "fix" each such file. If I am not mistaken it needs a "reference" file only for 9 patch files which are identified by their ".9.png" suffix (regular pngs I think are just rewritten without any change which I found improves compatibility). In case of a 9 patch file, the original file with exactly the same name should be found under the directory given in the second argument. For example: If drawable-mdpi/aaa.9.png is processed the 9-patch data will be copied from drawable-mdpi.org/aaa.9.png.
Obviously it also still works on single files. It does *not* work on lists of files or lists of directories.
If anyone is interested in the code, I am sure I have it somewhere (I hope)....
Click to expand...
Click to collapse
Gr8 work...u made themin a kid's job
Sent from my GT-S5670 using XDA Premium App
???
does the original still work cause im on windows 7 64 bit and i was able to copy the changes to original but not it makes no changes at all, so the original file doesnt get the changes...
please help!!
So first off, the release:
I've created a program (technically a script) written in Python that does all of the tedious work of making a boot logo and getting it on your Droid X or Droid2 phone. Specifically, it does all of the following for you:
1) Takes a 24-bit BMP of size 480px X 182px and flips the canvas horizontally
2) Makes the image the right size by removing the first 54 bytes (after the canvas flip all images are the same size so we don't need to remove the last 2)
3) Reverses all the bytes and writes the image out to a logo file (logo.bin)
4) Puts your created logo into the TBH Logo Replacer flashable zip file
5) Pushes the zip to your SD card
This tool should give anyone who has Clockwork recovery and is slightly familiar with it and knows how to copy, paste, and crop in an image editor the ability to make their own boot logo.
code.google.com/p/android-customization-autotool/downloads/detail?name=AutoBootLogoCreatorV1.1.zip
The project in development:
As you can probably tell from the link above, I'm also working on a tool that I have dubbed the Android Customization Autotool. When completed, it will have all the same functionality as ApkManager, and more. For the most part, I've been using ApkManager and it works fairly well.
However, there are some things that I feel are missing and have added in my tool. Similar to ApkManager, my tool isn't some new method of doing something or some type of breakthrough. It merely takes existing tools that are out there (and some that are not) and packages them up into an "all-in-one" type tool that is easy and efficient to use for beginners and experts alike.
What I'm aiming to do with the tool is quite simple. I'd just taking the significant amount of scattered knowledge on various forums regarding hacks and customizations and automating the whole thing so that people who don't have the know how, or aren't confident in their know-how can have all of the same customization opportunities that the rest of us who know what we're doing have. And for those who do know what they're doing, the tool will save a lot of time and effort.
The project is located at:
code.google.com/p/android-customization-autotool/
If anyone is interested in helping out (note it's in Python) just let me know. I'm also extremely open to any suggestions that people have about what should be supported. There are still a ton of customizations out there that I haven't seen any tools for and it would be nice to cover everything.
For those of you who would like to continue using ApkManager (since right now it's the better choice), I've been designing my tool in a modular way where any functionality that is provided can be forked off into it's own stand-alone application. And since the project is open-source, you can add or strip away as much or as little as you want. If you do make something cool though, please let me know because I'd love to add it to the tool (credit is always due of course).
thank you for sharing
Thank You...
If you guys run into any problems with the code, please let me know via the Issues page at code.google.com/p/android-customization-autotool/issues/list and I'll do my best to fix them. Still working on the all-in-one, but I've made an Update Zip auto creator that generates the META-INF folder, creates a .zip and signs it. More on that later today, sleep time =D
Thank you!!