|
||||
Re: Several kitchen questions...
Quote:
2) IMHO, 6MB is the optimal setting for this device. Some say to up it more, but my opinion and my benchmarks have shown that this only significantly affects soft boot time, the difference bettwen 6MB+ pagepool is within margin of error. Lower than 6MB, you'll run into hurdles ESPECIALLY when GAC, i.e. .NET CF is involved. I used to build roms on 4MB, but really, 26mb fresh on boot is more than enough. 3) no clue, unless you add about 100 packages, you are unlikely to run out of space on the titan. 4)correct. this includes exchange passwords, etc. 5)You could either create you own oem packages - see TOOLS>OEMIZER, which makes it really simple, or you can rely on a tool such as SASHIMI, Tiermann autorun, or SDAutorun (UC). Since you're building a rom anyway, you might as well oemize.
__________________
|
This post has been thanked 1 times. |
|
||||
Re: Several kitchen questions...
1) various kitchens use various bases. As a general rule, we use the most current stock rom at the time the kitchen is first created as a porting base. It is unlikely you will see much difference regardless of which base is used.
3) It correctly accounts for the device you are on. It incorrectly accounts for the size of your OEMS (currently uses uncompressed size instead of compressed size). Can only be used as a guideline for now. The true test of rom to full currently is only available when you actually try to build your rom.
__________________
Grammar: The difference between knowing your shit and knowing you're shit.
Last edited by gguruusa; 08-08-2008 at 11:13 AM. |
|
|
|