@ / to rom devs
 

Hey,

I was just wondering what the point of adding things like googlemaps, .net 3.5 etc (3rd party software) into a rom is. Doesn't that just make it impossible to remove some software? I can see adding things like Java/QuickGPS (things the phone should have come with) but it seems all this other stuff is just taking up space in system memory. Shouldn't a rom be a stripped down version of the os software w/tweaks and fixes applied vs a software package which would be a package of my favorite software? Thanks for cluing me in.

Regards,
Will

Re: @ / to rom devs
 

Some like to have a rom ready to go. And that's what makes all the rom's different. Each chefs personal touch or programs installed. Everyone pretty much has the same ingredients available to them, it's what they include in their app list that makes people download and install their rom. And by apps, I mean skins or themes as well. Some offer a clean version you can customize as well. Before I learned how to cook, I would go with a "full" rom, then I went through a period of wanting a "clean" rom with uc that I could customize with .cabs, then I found nexvisions hulk rom and decided to cook them myself.

It's all a personal preference I suppose

Re: @ / to rom devs
 

This is the great dilemma affecting all chefs. I personally started with a 6700, so I had to keep my ROM lean and mean just so it would fit. On my 6800 I was afforded more room, and thus I included a bit more stuff. On my current 6900 I am actually back to the debate of all in or all out. Current thought was to leave the ROM lean and mean, and then CAB everything else. Doing it this way gives you the most flexibility when new releases of things you use come out. You dont have to continually flash a new ROM. Just uninstall the existing CAB, soft rest, and then install the updated CAB.

I am sure the pendulum will swing the other way soon enough for me. In fact I am starting down that route with the 20755 kitchen.

Re: @ / to rom devs
 

a lot of the chefs around here are also always on a new rom, If I stick with a rom more then a week, the reason for that is I am to busy to flash it. So I can make a basic ROM, with updated apps, and the exact programs that I will use, Then I never have to install anything else. No cab files to worry about and no matter what everything is going to work, for the next few days, until I change one small setting and start all over again.

Re: @ / to rom devs
 

What most chefs do now is add what they think will attract an audience, if you notice if you started out with the titan the goal was to make it look like a touch if you have a touch the goal was to make it look like a diamond ..... some add what they may use on a daily basis .... then some just was the credit and acceptance from making a rom .... to put my spin on your question - what is the purpose of the custom rom ?

Re: @ / to rom devs
 

Like Rstoy said it's all personal preference. I cook my own rom that's bare minimums, it has a couple programs that I know aren't being updated any time soon built in, everything else is installed later because I want to be able to upgrade it without having two copies of the program.

Re: @ / to rom devs
 

for me it's all about saving time....I'd rather have my apps cooked in the rom instead of adding via cab...I'm not too concerned about program updates, unless it's something major.

Re: @ / to rom devs
 

When creating OEMS do you use the Personal OEMizer from Tiermann? Or is it some other tool?

Steve

Re: @ / to rom devs
 

oemizer is good to use. it's easy too.