Quote:
Originally Posted by rstoyguy
There for a while I tried that approach because when you cook a rom everything goes into \windows. I thought that UC would save me a couple seconds everytime I went into \windows with TotalCommander. Ended up that I did save a couple seconds, but at the expense of my UC's running on for 30-45 minutes. Now I do a happy mix of both. But the clean rom base is not the way, I use OMJ's. Strip out what I don't need, add a couple things I do and install the rest with UC.
|
OMJ does great work, as do the other chef's, but everything that meets my requirements (that I can see, anyway) is a mix of WM6 & WM6.1 and every one of the ROMs seems to have a level of instability, perhaps due to the WM6.1 equation.
The instability is actually the primary catalyst for this. Gimme a stripped down stock Sprint OEM base, which will presumably be stable (at the expense of the WM6 memory leaks) and I'll add whatever else I need via User Customization.
I am curious, though - what, or rather how many things are, or were you adding via User Customization, which caused the process to run for 30 minutes?