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?
Hey all...
So I have been in the Kaiser forums for about a week now and have played around with some of the ROMs out there. My previous device was a PPC-6700. On that device there was a ROM and an Extended ROM. To the best of my experience, I never played with the ROM, but I did unlock the extended ROM and remove many of the bloatware cabs. I also set up some file (I can't remember the name, but it was similar to the UC option) which would allow my own CABs placed in the extended ROM to be auto-installed. In this way we were able to distribute the phones to employees with only the software we wanted (for instance, with our company cert pre-loaded and TCPMP to play back cisco VMs).
While I understand the interest in "cooking" a ROM to get all the latest and greates components (WM version, Radio, etc.) from the various ROMs into one uber-ROM, I'm not sure I see the advantage of adding in all the additional pieces of software.
From my viewpoint, I would think that a ROM should be as clean as possible, this would present a nice base for users to customize. Instead of "cooking" all the files for other components (plugins, menu replacements, voice command, SIPs, etc) into the ROM, why not just provide these as CABs either within the ROM or as a separate download alongside the ROM?
This would allow not only users to choose what to add, but also allow them to remove an installed CAB if they no longer want to use it or if a new one comes along.
I understand part of the allure of a cooked ROM is that the cook has ensured all the components work together... and in my scenario this would still be the case. The ROM would be qualified and shipped with a certain set of applications, but that doesn't mean they all need to be installed.
Another argument I hear for using a cooked ROM is that all the apps are already installed and it doesn't take time to reinstall all the apps. However, with UC, can you not just load all CABs onto an SD and have them all autoinstall? I am pretty sure you can write a file that will install a set of cabs even from local storage. While I understand that this might take a couple minutes more initially, I think the time saved in the long run would be equal or more. For instance, it might take me 10 minutes after I re-flash a base ROM to load another 15 CABs that I want. But, when a new version comes out of my application, or another application I want to install conflicts with something on there, I can easily uninstall the CAB. Small changes to the configurations can also be made without cooking a new ROM.
Now I fully appreciate all the work the cooks on this site have done. I think their work is great. What I am suggesting is an alternative methodology and one that is certainly not new. I am the type of person who likes a very clean build, but also enjoy the many features that are offered with some of the busier ROMs. I feel that having a base build and then simple a suite of approved or offered CABs make the whole process cleaner.
I am trying to understand how the mindset evolved here to make these feature rich ROMs instead of the alternative. The main argument I have heard is that it is quicker to just flash a ROM with all apps rather than load each one. As I have addressed that above, I don't think that the time savings are significant in comparison to the flexibility of modular CABs.
Perhaps there are additional advantages to the current approach that I have overlooked and I would be interested in hearing them.
tell me your thoughts?
wow......all that writing and all you are suggesting that cooks put out some clean roms? arent those already available?
lmfao flash your own clean rom, flash your own choice of radio, tweak on your own, etc...
Do you ever contribute anything worthwhile to threads or do you just prefer to be a sarcastic jerk?
I realize there are some clean ROMs out there...that wasn't the full scope of the post.
The "clean" ROMs are indeed what I would prefer, however that leaves the user going around hunting for all the applications and additions they desire. (And don't use the argument that the user is lazy if they don't spend the time to do this...after all that is what the "cooked" roms allow the user to be...lazy).
The alternative is the loaded ROM which has everything chosen by the cook. The user can't uninstall a component he may not want, or if it causes conflicts with something else.
The middle ground is what I am advocating...a clean ROM but offered with either "built-in" cabs or a separate repository. This would allow the user to install what they wanted (or install it all...then removing what they don't find useful). This would also allow easier updates in between major cooked releases.
I am not stating one way is definitively better, just that at some point someone decided to cook it all in rather then just offer the cab files, and I am looking for the advantage over my alternative.
What would even be nice (and if I knew how to code for PPC I would look to do it!) would be a little menu app that could manage installs from a repository either on your SD card or even online! So you could browse a list of available apps, versions, and descriptions and load it right up. These repositories would then be what the cooks spent time compiling, even offering "Suites" of applications that complement each other well.
As I stated in my original post I am very thankful for the work that others have contributed here and am not belittling their accomplishments in any way. I am just trying to understand how and why things have evolved to their current situation since, if I were to have the time and knowledge I see my framework as more workable (IMHO).
My personal opinion
That's one of the best presented arguments I've seen in a while Bengalih.
Completely agree with all your reasons for preferring a clean ROM over a loaded one - particularly the ability to update applications as and when a new cab is released. While this is the best answer for you (as you state) and in all probability every person with the willingness to go and look for the latest version of everything, I personally still prefer the loaded ROM. I simply prefer the least amount of time between a Hard Reset and being fully back up and running - in my case as long as it takes me to type in my Exchange server details. I try to cook in applications without any bugs that do what I want, so I won't need that newer version (just want it) and if a newer version does come out I can easily bake it into another ROM and be back up and running from start to finish within half an hour (mostly).
While you're completely correct in everything you say - I'm one of the fundamentally lazy people (seriously, check out my ROM's v1.3 intro - that's the word I use to describe why I built it) and so I tend to prefer loaded ROMs.
the way i see it, we cook a rom to have our ideal base. Things where we meet the minimum. The minimum for me must have HTC home, office, tomtom, the games that I always play, which is a whole variety, pim backup, and battery status. When I have my clean base, I just add my packages, which doesn't even take me long at all. If something screws up, we flash our cooked rom, and we don't have to worry about flashing a clean base and adding all our cabs. My roms include a lot of apps, but thats what I expect from my base. Having cabs doesn't seem as clean. I see your point, but cooking your own rom, you don't feel like trying anyone elses roms because the rom is exactly the way you want it.
Thanks for your reply Stu...a perfect example of how one can disagree with an opinion while being completely civil. It seems many other members of this forum can learn from your example.
I'm still not 100% sure I agree with the time you save by having everything cooked in. As you admit, if you want to upgrade an app you would basically cook a fresh ROM with the new package in it and take up to 30 mins. To be honest I would think that you could load ALL your cabs in well under 30 minutes (the first time) and then it takes about 1 minute to upgrade a cab if a new version comes out.
Of course it depends on how often you do each. If you really find yourself reloading your ROM alot...let's say once a week, you might have saved yourself 10-20 mins each time since you don't need to load CABs. However if you instead wanted to upgrade 4 apps, you have saved yourself 30 mins each time from having to recook the ROM.
I guess another thing I don't understand about the argument for the fully loaded ROM is how often are you really re-flashing your ROM? While I understand someone may do this frequently if they are testing ROMs, how often do you really need to re-flash your ROM once it is running with the apps you like (and/or cooked in)?
Also, I believe your opinion is slanted (and not in a bad way) because you obviously cook your own ROMs. Because of this you can customize it the way you want since you have total control. Some of the cooks on here seem to be people like you who then just turn over their ROM for others to use, while other cooks seem to be making ROMs to please the population. Not saying either is a bad thing...just what I notice.
I haven't cooked my own ROM yet (though I have read through the tutorials). I believe however that even after I have decided on everything I want that I won't cook a loaded ROM (if i cook one at all). I would prefer to just put all the CABs i use in a directory and if i ever rebuild just load them all back on, or possibly create a UC script to load them all off my storage card.
Although I still don't really see the advantage of the fully loaded ROM (unless of course you tend to A) reflash your ROM frequently (for what reason?) and B) Tend to not want to upgrade CABs frequently)... to each his own.
thanks!
thomassster said:
Having cabs doesn't seem as clean. I see your point, but cooking your own rom, you don't feel like trying anyone elses roms because the rom is exactly the way you want it.
Click to expand...
Click to collapse
It's funny you say that thomas... because i feel opposite. I feel that with the cooked ROMs it seems that many things just get dumped into the Windows directory instead of being put into individual Program folders. In addition, with no uninstall option it gives me a non-clean feeling
I see your point of course on just building the base the way you want and it makes sense if you don't feel you will want to upgrade an individual component.
I guess I am generally they type that like to go and get the newest version of an app if it is available and would find the process quicker if i could just upgrade the CAB.
Also, as stated above, once I find a config I like I don't know why I would reflash my ROM on any type of frequent basis.
There are additional reasons why certain applications cooked into ROMs aren't always your best alternative.
This is when certain applications (e.g., TomTom, MobiTV & XMRadio) require specific directories for installation. If cooked into the ROM, it will occupy twice the amount of space, since all files are placed in \Windows and through initflashfiles.dat get copied to other locations (e.g., \Program Files\MobiTV). Chefs that know about this avoid cooking these apps into their ROMs.
As for ROMs & which way is better, it's a matter of personal taste. Some folks prefer different levels of clean, and others prefer different levels of full. Some people won't flash unless a cube is included. It's pretty much why I release 8 different versions...
Thanks _Alex_,
Yes that speaks to my point to a degree.
It seems that most cooks don't use INITFLASHFILES.TXT to move applications to a specific directory (under \Program Files) and just let everything sit in \Windows. I was under the impression that INITFLASHFILES could MOVE the files and not just COPY, so thanks for clearing that up. Would it not be possible to execute some sort of script to delete the unnecessary files from Windows and add reg entries to allow programs to be listed in add/remove? Of course this would be additional work for the cook but would really provide the best of both worlds.
I realize you have alot of time and experience invested in your methods (which we all appreciate). But, it would seem to me that instead of cooking 8 ROMs you could cook a base and then offer CAB installation suites as I mention. With either a custom menu install app like I suggest, or UC scripts the process can be automated.
I am not necessarily suggesting that you change how you do things (since you do it so well D), but I just throw this idea out there in case any experienced cooks, or even newcomers agree with my method they are welcome to give it a try.
thanks for your input
bengalih said:
Thanks _Alex_,
Yes that speaks to my point to a degree.
It seems that most cooks don't use INITFLASHFILES.TXT to move applications to a specific directory (under \Program Files) and just let everything sit in \Windows. I was under the impression that INITFLASHFILES could MOVE the files and not just COPY, so thanks for clearing that up. Would it not be possible to execute some sort of script to delete the unnecessary files from Windows and add reg entries to allow programs to be listed in add/remove? Of course this would be additional work for the cook but would really provide the best of both worlds.
I realize you have alot of time and experience invested in your methods (which we all appreciate). But, it would seem to me that instead of cooking 8 ROMs you could cook a base and then offer CAB installation suites as I mention. With either a custom menu install app like I suggest, or UC scripts the process can be automated.
I am not necessarily suggesting that you change how you do things (since you do it so well D), but I just throw this idea out there in case any experienced cooks, or even newcomers agree with my method they are welcome to give it a try.
thanks for your input
Click to expand...
Click to collapse
The method you describe has been mentioned before in other threads and quite possibly in its own thread. (The topic was UC packs, CAB packs or something like that)
There are three cons with that method:
Which cabs to include are subjective, so it's much easier for an individual to gather his/her own cabs
Creating CABs can be a serious pain in the ass, especially if you have 50 OEM packages that need converting and/or fixing for the specific ROM you're building
Cross ROM / device support, which frequently occurs when CABs are released.
On the other hand, with a cooked ROM, you know it works because the chef ( andhis beta tester(s) ) spent the time to test it on the same/similar device and on a specific OS build. ROMs give a better experience overall because of this testing.
FWIW, I've thought about doing what you mention above waaay back with my first UltraClean ROM, but as stated, serious PITA
*SHRUG* Perhaps I'll re-consider it in the future too...
edit: Alltheway used to offer UC packs. Not sure if he still does on his 4shared folder...
I have, personally, always preferred a clean ROM. Yes, it takes some time to set it up the way you want it but, at least, that way, I am not stuck with applications I do not use. If I were to cook a ROM, I would cook it the way I want it and then distribute it. Most cooks here do just that. I would be happy if every cooks released a clean ROM but that is not possible. If cooking ROMs were a full-time job for these cooks, then, I would definitely demand one. So, the way I feel it, if I am lazy or not good enough to cook my own ROMs then I should stick with what has been released and not complain.
@ sherpa:
Perhaps you should go back and re-read my posts. Not once did I "demand" or "complain" about anything that any cook has put out. In fact more than once did I thank and compliment them on all their work. The fact that you state you would "demand" a ROM a certain way if this was the cook's full time job show that it is you more than I who feel that they are, or might be, owed something from these contributors. I fully realize that many cooks are just putting out their own personal ROMs to the masses, but there are plenty of them out there that are also looking to please the community and offer something different. It was to these people that I thought my message might resonate and someone might want to try something like it. As _Alex_ suggested others have thought similarly at somepoint (including himself), so I am not alone in my thoughts. So before you accuse me of complaining, you should re-examine my own words and yours.
@_Alex_
Thanks for the thoughts. I see all the points you are making. However I would argue that point #1 and #3 happen whichever method you choose. A cook is subjective when choosing which CABs to add to a loaded ROM as well. In addition, a single ROM is also device dependent whether it is fully loaded or not. I feel your pain on point #2 about creating CABs... you helped me out in another thread as I created a CAB of the latest Remote Desktop client (with drive mapping support) from the latest AT&T test ROM. I agree that for the cook that would be an extra effort although in many cases most of the CABs are already out there.
Again, I am making a recommendation as to a new (or old?) way to approach this. It sounds like it would be good for the user, but more work for the cook. Of course the current methods are well established, so even if my idea has merits it would most likely encounter some resistance (and as seen already by some, accusations and ignorance.) I still like the idea of an online (or off) repository with a little front-end on the device. The repository can be loaded with approved CABs which can be loaded and unloaded off the device.
In the long run, I don't think it will matter much for me individually, as I will most likely use an available clean build, an RTM ROM, or maybe cook my own. But in any case, I will stick with CABs, and just hope that the ones i need are available or I am able to create them myself (which is exactly what I did for Remote Desktop).
thx!
Dude, I never accused you of complaining. When I wrote "not complain", I meant it to the general population who complain about what's included and what's not included.
No offense meant, no offense taken then. Based on how this thread started out I guess I was just in a defensive mind-set.
We all good
ok bro bengalish
you are just quiet right , i understand your point and i also think that thought cookers make a great work to interduce a room that is useful for everyone but it still better to get a clean room and that's because a simple reason , you will never be able to make everyone happy because simply everyone of us has his owen taste
but i would like to describe what a clean room means ..
i belive it should contain main updates that everyone will need i mean updates like camera , sound and system etc..
i have to thank you for this rich argue and much greeting for you
and i hope really everyone in this forum can show little respect and kindness for the others
cheers
Yes haam,
I would prefer to see more frequent ROMs that have all the base stuff updated (latest BT, VC, etc). And not have the cooks spend as much time with the additional applications as many people will want to do customization here. To the main point, I think there are alot more people out there who can cook an application CAB then cook a ROM with all the latest drivers properly implemented. In my framework the cooks can focus on an up to date clean ROM and the assistant chefs (many in the community) could work on CABs.
Of course I fully acknowledge that there is a segment here (cooks included) that they want everything loaded from the get go and don't really care about additional customization. If that is the majority then things will stay status quo. If not, maybe we will see more people working on UC or CAB packs or something to that effect.
thanks for everyone's thoughts!
not sure if any body thought of this what if chefs let users to sign their names addresses and finger print scan in the rom
1st will be thief deterent
2nd good hearted will return it if found
3rda phone will be a personal thing,chefs can leave their name somewhere for the smell and taste fo thier cooking
I'd think Chefs should also put a file in the \windows directory called release_notes with their ROM name and a forum link to their ROM thread.
Can't say how many times I've forgotten who's I've got flashed at any given time.
First, most chef's already put their name in the rom in one or more places, second , if you are using one of Alex's rom's used the kitchen & you can put whatever you want in it. Third, if somebody decent finds the device, your name & etc. is already in device owner info or can be looked up by your carrier with the serial or esn. Finally, if anyone else finds your device , it will take them all of 10 minutes to use Google & figure out how to flash a new rom. You could change the device ID to something nonexistent to make it harder to flash, but that's something better worked out by you & no Chef is gonna want to do that for every single person, not to metion that if he did, the thief would google & figure it out.
There is always ways around things, just ask AT&T, HTC & everybody at XDA
GSLEON3 said:
First, most chef's already put their name in the rom in one or more places, second , if you are using one of Alex's rom's used the kitchen & you can put whatever you want in it. Third, if somebody decent finds the device, your name & etc. is already in device owner info or can be looked up by your carrier with the serial or esn. Finally, if anyone else finds your device , it will take them all of 10 minutes to use Google & figure out how to flash a new rom. You could change the device ID to something nonexistent to make it harder to flash, but that's something better worked out by you & no Chef is gonna want to do that for every single person, not to metion that if he did, the thief would google & figure it out.
There is always ways around things, just ask AT&T, HTC & everybody at XDA
Click to expand...
Click to collapse
1st the whole idea is not about the phone getting lost rather than personlizing it ,to google or change that is why i said chefs should make it possible to ingrave it in the roms thiefs if they know all that they are nottheifs they won't find time to steal they will be cooking for us
actually, for anti-theft, I was thinking of a kit...
1) modified SPL; requires non-standard password and a signed NBH using your own custom certificate
2) OS is locked down with a trusted certificate of your own in the store so SSPL won't run at all... unless you sign it with your certificate
3) program that checks the SIMcard IMSI; if it changes then it sends an SMS to another number.
now... there are a few practical issues with 2) because it makes installing new apps a pain in the arse since they all need to be signed, so maybe a way of buggering up SSPL would be better.
ras said:
1st the whole idea is not about the phone getting lost rather than personlizing it ,to google or change that is why i said chefs should make it possible to ingrave it in the roms thiefs if they know all that they are nottheifs they won't find time to steal they will be cooking for us
Click to expand...
Click to collapse
A Chef that makes ROMs used by thousands is not gonna want to customize or personalize each one for every user. That said, with a donation, there are many that might consider it for you. Of course, you can always use a base ROM & the Kitchen to do it yourself. I do this.
Also, you can use provisioning xml's to customize or personalize them on a basic level using UC. Read Sleuth's thread on UC (User Customization).
@ Olipro, I really like the idea's 1 & 3. I have played a bit with CID locking to an imagined CID & with false Model ID's but of course while you then can't flash a ROM that's not customized to match, you could bypass it with SSPL, making it pointless against anyone half competent.
Your solution 1 & 3 would almost have to go hand in hand, having the password & a way to keep SSPL from jumping the password measures. Something like this, in conjunction with WIMP & UC in ROM, would be a great tool for security. Very Interesting indeed.
This is my 3rd post ever here, so please be gentle.
Crogon said:
I can't seem to find it now, but didn't there used to be a list of pre-cooked ROMs here somewhere?
I think what I'm aiming at is a fully patched / hacked 6.1 HTC ROM with everything fixed and no bugs. Preferably minus any bloatware. If it has recommended utilities pre-installed great, if not, no big loss. Did they ever finish hacking a video driver together? I lost track of that thread, and can't seem to find any current info.
Click to expand...
Click to collapse
Update: I found a tidbit somewhere that says the newest video driver updates should be cooked into the newest ROMs.. but how do I figure out which ones have all the bug patches and hacks installed, and etc. like I mentioned above? I know there USED to be a list of pre-cooked ROMs, but I can't find it now.
Hmm.. Am I maybe thinking of a list of pre-cooked ROMs for the Wing, or some other HTC? If I am, I'm DEFINITELY going to need some ROM recommendations.
Here are my stats, if it helps any:
rom version 3.57.502.2 WWE
rom date 7/17/08
radio version: 1.65.21.18
protocol version: 25.88.40.05H
tri-color screen
KAIS1*0
SPL-3.56.Hard
CPLD-8
.
.
Serial
image version 3.57.502.2
R 1.65.21.18
G 25.88.40.05H
D 3.57.00.00
Thanks again for any help!
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
mazin13 said:
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
Click to expand...
Click to collapse
he DOESN'T WANT a cooked rom he is looking for a pre-cooked rom.
@op did you check the kaiser wiki or htc's website?? 'cuz that is where you will find all the latest roms for your device that aren't cooked by a chef.
Also, look around for mbavrian's Kitchen Elements.
The "Base ROMs" on which our Chefs makes their gourmet meals are difficult to locate. Some chefs refuse to share like little playground children.
Others, Like NotATreoFan, have released their base for other people to use to make ROMs. Great Contributors.
Woops!
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Click to expand...
Click to collapse
I've never seen one and I don't believe one exists. You'll just have to do your own research.
Crogon said:
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Click to expand...
Click to collapse
You have to spend some time and TRY each ROM and see which one is suited for you.
Again, READ and spend time.
Read WIKI especially.
There is no 100% perfect ROM even if it is official one.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
If you want a newest list, you are always welcome to Update the wiki
I'm heading for the aspirin bottle just now. I spent like 3 hours reformatting the info on the wiki page into a spreadsheet.. when I discovered that some of the authors are still releasing, but it's not on the list!
AAHHH!!
So basically, A full up to date list is needed. Let alone version comparisons or features and bug fix lists.
Good grief.
No wonder most people opt to install ROMs randomly till they happen across one they like.
.. I think I'll make a new wiki page eventually. Something along the lines of a Kaiser ROM Feature Comparison page.
Do I get a XDA-Dev decoder ring if I actually finish it? lol