Been looking at the various available partition sizes offered on Alpharev.nl, and it got me thinking a little...
Data++: spacious, but cache (5MB) is too small for flashing radio images from recovery. Not good. Also there is much space leftover in system after ROM is flashed.
CM7: same cache as Data++, but even more space for data. More suitable size of system, less waste of space.
I'm not too keen on aplying these two as I would have to plug into the laptop to flash a new radio. Not that much of a nuisance, but nevertheless....
Bravo-Sense: Tempting, but quite a waste of space as system is 180MB and a good part of it would be unused after flashing the Data++ version of LeeDroid. Only real difference from Data++ layout is 35MB moved from Data to Cache.
N1-table: I presume this would waste space too as cache is a staggering 95MB!? It also have the least space for data apart from the stock table.
Oxygen is tempting too. I can't find it's written anywhere that 10MB cache is too small for flashing radio, but it still might be a little small for large downloads? Rom don't fit either, so it would take some stripping down on my own part to make it fit on the 90MB system.
Would be great to be able to make my own partition table with suitable layout, something like CM7 with a 20-30MB cache, but I guess that is just too time-consuming to learn for a semi-average nerd like myself with family and work to take care of
Just a little brainstorming here. Guess I will end up with either the Oxygen or the Bravo-Sense in the end....
Like you not sure about data++ don't know too much about it if I'm honest need to do some research, must be cons as well as pros..
For now stuck with A2SD+ and all is peachy, good work as ever Lee..
Thanks for the reply. I decided to flash the ext3 patch again to check if it works. I found that:
1) CWMrecovery could mount the sd-ext again (w00t)
2) my phone doesn't boot into Android anymore.. stuck at HTC-splash. ()
I wonder what the problem is.. I've got hboot 0,80, S-ON. I want to S-OFF, but not before a good nandroid with ext3 backup included.
suggestions?
edit:
had to pull the battery, and upon entering recovery again CWM couldn't mount the sd-ext anymore?? WTH
edit-2:
OK, nevermind: after applying the patch for the 2nd time the phone booted in Android again
That's what I meant, 2nd time. For some reason, it has to be patched again. Then the rom will flash.
-I recommend to use a data++ Rom only if you know what you do. Be prepared to use Google :)
- You need s-off and usually the Oxygen hboot http://www.alpharev.nl/ you get over 330 MB internal memory... ;)
- Radio updates have to be installed with fastboot, see http://www.alpharev.nl/ for more info. (cache partition is to little to hold the update... )
- I recommend a 1GB ext3 partition on the SD card, more should not be needed, less may be to short, cause a part of the system is on ext and A2SD+ is active too.
- Parts of /system are on the sd-ext: /system/framework, /system/media, /system/fonts and /system/app
- Themes cant be directly flashed. The best way should be, to put the theme-files into the ROM.zip prior the flash. Another possibility is to update the paths in the script of the themes, or via "adb push" in recovery.
One thing I could not say (not at home on my pc) is, if the /cache ramdisk is implemented. If not, there could be problems with big market downloads.
Been looking at the various available partition sizes offered on Alpharev.nl, and it got me thinking a little...
Data++: spacious, but cache (5MB) is too small for flashing radio images from recovery. Not good. Also there is much space leftover in system after ROM is flashed.
CM7: same cache as Data++, but even more space for data. More suitable size of system, less waste of space.
I'm not too keen on aplying these two as I would have to plug into the laptop to flash a new radio. Not that much of a nuisance, but nevertheless....
Bravo-Sense: Tempting, but quite a waste of space as system is 180MB and a good part of it would be unused after flashing the Data++ version of LeeDroid. Only real difference from Data++ layout is 35MB moved from Data to Cache.
N1-table: I presume this would waste space too as cache is a staggering 95MB!? It also have the least space for data apart from the stock table.
Oxygen is tempting too. I can't find it's written anywhere that 10MB cache is too small for flashing radio, but it still might be a little small for large downloads? Rom don't fit either, so it would take some stripping down on my own part to make it fit on the 90MB system.
Would be great to be able to make my own partition table with suitable layout, something like CM7 with a 20-30MB cache, but I guess that is just too time-consuming to learn for a semi-average nerd like myself with family and work to take care of
Just a little brainstorming here. Guess I will end up with either the Oxygen or the Bravo-Sense in the end....
I found this on xda
Quote:
Data++ is a technique that was first implemented and tested by ClassicalDude. Using a re-laid out nand MTD, only the davlik-cache is retained in the internal memory. All .apk's are moved to the SD-EXT partition, where they are rarely accessed. This means a HD RoM can be fit in 180MB, leaving a lot of room for userdata which will remain in the internal memory. This results in a lightning fast ROM which stays fast through with no lag whatsoever during market downloads etc. Add to this the cool fix from coolexe and baadnewz that creates a dynamically resizable ram-disk for market downloads: and you have a great RoM that doesn't need to waste space for cache and will never have a market download fail!
I tried but failed to install 3.0.7 on the oxygen hboot. The System rom is about 5meg to big to fit... From the quote above it seems as though the cache partition size doesnt matter so it can be kept at 5meg.
Given the amount of coverage that Android receives around here, you could almost be … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?