Unified ROM Project, Phase II: The Kitchen Application

[sonnemad]

If you want the ability to build everything locally, yet still don't want the user to have to download every oem available. Why not just have the "application" which the user picks the OEM's they want have an option or section listing downloadable OEM's in addition to selecting any local OEM's they may already have. Then when the application builds the rom, it will download any additional OEM's the user has requested but does not yet have.

In doing this, you still have the user building the rom locally saving the server from doing all the work. Then all you need to maintain is an OEM Repository. This would probably be a bit more complicated than a standard local application, but I believe it would be simpler than a full web/server based solution.

Like I said, Just a thought.

Great work everyone!

[dannzeman]

I think colonel's post is right on. The web based method sounds good but what if some apps that I want aren't included? Is it feasible, or even possible to have every app out there accessible? No. Also, like colonel said, I like the idea of being able to change any little minute detail in my rom. I think we should go with an app based solution.

[angel12]

i havent cooked my own rom yet (havent really had time to do so lately), but i like the idea of an application, not a web based kitchen. As colonel said, it would make for one huge download, but i think i have a way around that. Maybe have just the builder and the vanilla rom be downloaded first, then once the user picks the oems they want, the app will download them for the user. I know this is a lot of work, but ive seen it work greatly too. Im thinking Debian Linux or Gentoo linux style, where you download the barebones setup then build your own with an internet connection.

Thanks for everyone's help on the Rom team, cant wait to try it out!

(now off to go study some more for cooking)

[luv2chill]

How about a nice web page with links to the kitchen, patches, OEMs and a nice readme? The existing method is really not that difficult. If someone can't follow a simple list of steps then I fear they really shouldn't be trying to use a custom rom in the first place.

My 2 cents.

[pixelwix]

Originally Posted by luv2chill

How about a nice web page with links to the kitchen, patches, OEMs and a nice readme? The existing method is really not that difficult. If someone can't follow a simple list of steps then I fear they really shouldn't be trying to use a custom rom in the first place.

My 2 cents.

i second that idea. i started cooking my own rom and its not that hard, i have everything automated for me when i flash, about the only thing that needs my input is the welcome screen, everything is all in the rom, and if i can do that, anyone should be able to cook their one roms.

[Glossman]

Originally Posted by luv2chill

How about a nice web page with links to the kitchen, patches, OEMs and a nice readme? The existing method is really not that difficult. If someone can't follow a simple list of steps then I fear they really shouldn't be trying to use a custom rom in the first place.

My 2 cents.

That may be the most elegant solution, however, I'm not sure it meets our original goal of bringing an easily-customizable ROM to the masses.

While I and many others have no trouble following kitchen instructions, there is a much larger group of people here who are savvy enough to flash, but may be afraid or not have the time to attempt a ROM from kitchen.

That's where our proposed tool comes in.

Just my .02!

[angel12]

Originally Posted by luv2chill

How about a nice web page with links to the kitchen, patches, OEMs and a nice readme? The existing method is really not that difficult. If someone can't follow a simple list of steps then I fear they really shouldn't be trying to use a custom rom in the first place.

My 2 cents.

that seems like a good idea. Just do that for the mean time, while the uni rom is being baked

[nuguy]

Why not K.I.S.S. (keep it simple stupid) an ap would be the simplest to implement which would include the base kitchen and then it could search for whatever OEMs are in the local OEM folder and include them in the build. There could be a couple of other folders such as EXTENDED_ROM and perhaps CABS posibly even TWEAKS and REGISTRATIONS for further customizations.

One strong vote for an ap (in my opinion) is that it is a standlone entity. If it were only a web based page/ap it could easily disapear if something happened to the host, or if MS didn't like it being available.

As well it would take a huge hit on the servers: let's say I build a rom today and tomorrow I decide I wish I had included something else - or wish I hadn't included something, with an ap I would only dl the new OEM, or just remove the one I don't like from the OEM folder... Not re-download the whole package every time I want to tweak a little something.

As well if I wanted an assortment of options I would only need to keep extra OEMs not try to name the resulting file something that would let me know everything that I chose oem-wise to make it.

If we were a OEM provider, or manufacturer ourselves the web version would be best, but since we're not, and ms did what they did to xda...

I really feel it should be an ap.

[nuguy]

I would also like to be a QC tester again. I would hope to be a bit more helpful this time as I may actually be in town (High Point Furniture Market was last week).

[boe]

This sounds GREAT!!

You guys are pretty dang sophisticated - I'd be happy to be a humble tester.

I'm sure you've got it figured out but I'm hoping you make it easy for us to add copyrighted cabs from our PC such as Voice Command and SPB Pocket Plus since those two seem pretty common.