NexusHD2 Android Forum

Hi,

I think it would be great if there was an SRAM/DataOnEXT or NativeSD hybrid. I used to try Barebone CM7 V2b SRAM and it's super fast. And I guess it will be even faster if it keeps data in the SD card structurally instead in a data.ext4 file. What do you think about this?

soren wrote:Hi,

I think it would be great if there was an SRAM/DataOnEXT or NativeSD hybrid. I used to try Barebone CM7 V2b SRAM and it's super fast. And I guess it will be even faster if it keeps data in the SD card structurally instead in a data.ext4 file. What do you think about this?

Is data.ext4 in fat partition faster than ext4 based data partition?

symbuzzer wrote:Is data.ext4 in fat partition faster than ext4 based data partition?

I believe ext4 based data partition is faster because the system can access the files directly. But SRAM is very fast because the system is on the RAM.

soren wrote:I believe ext4 based data partition is faster because the system can access the files directly. But SRAM is very fast because the system is on the RAM.

So,Is System on RAM, Data on Ext4 best combination, right?
On System on RAM method, is battery draining faster than our known ins. methods?

symbuzzer wrote:So,Is System on RAM, Data on Ext4 best combination, right?
On System on RAM method, is battery draining faster than our known ins. methods?

Yes, I think so. Regarding the battery, I'm not sure. Barebone CM7 is very nice but I didn't use it for long because I wanted to use the latest version of Android and Barebone CM7 supports only en_GB/US locales. But when I used it, I didn't feel that the battery drained fast at all.

soren wrote:Yes, I think so. Regarding the battery, I'm not sure. Barebone CM7 is very nice but I didn't use it for long because I wanted to use the latest version of Android and Barebone CM7 supports only en_GB/US locales. But when I used it, I didn't feel that the battery drained fast at all.

I liked this method in theory, I will try this rom at weekend. Thanks for informing me about this method. I hope, devs will write their opinions and critics in here.

symbuzzer wrote:
So,Is System on RAM, Data on Ext4 best combination, right?
On System on RAM method, is battery draining faster than our known ins. methods?

I thinked again. Maybe System on RAM + Data on Nand or System on Ram + Data on Ext4 + Dalvik on Nand methods are faster.

symbuzzer wrote:
Is data.ext4 in fat partition faster than ext4 based data partition?

It should be faster with data on ext4 partition as soren says. Else NativeSD would be the same speed as sd builds with data and system in image files on fat32.
I think it is a good idea to have some system folders permanently in ram.
Battery drain should be less too as there is less sdcard access.

I'm new to these forums, but have more than a decade of experience running Gentoo Linux. I'm concerned that these phones are too resource limited to use this technique. With only 1/2 a gig of ram and no swap, running most of the system in memory wouldn't leave much for anything else and could quickly lead to a situation where apps are starved and crash especially when multiple apps are opened simultaneously. This of course would defeat the intended purpose.

This seams like it would be a more viable solution for a newer phone with more resources available, but I'd love to see the results of such an experiment on the HD2 though I wouldn't want to try myself.

Odysseus wrote:I'm new to these forums, but have more than a decade of experience running Gentoo Linux. I'm concerned that these phones are too resource limited to use this technique. With only 1/2 a gig of ram and no swap, running most of the system in memory wouldn't leave much for anything else and could quickly lead to a situation where apps are starved and crash especially when multiple apps are opened simultaneously. This of course would defeat the intended purpose.

This seams like it would be a more viable solution for a newer phone with more resources available, but I'd love to see the results of such an experiment on the HD2 though I wouldn't want to try myself.

Very true, the barebone CM7 SRAM build mentioned in OP has a system of around 100Mb, leaving around 400Mb (less some for graphics I think) for android to use. Anything much larger would make the build unuseable and very laggy. boonbing did make an initrd.gz in the Portadroid thread (http://forum.xda-developers.com/showthr ... ?t=1094372) which only put 100Mb of a larger system image into RAM, although I am not sure whether it was the first 100Mb or whether system folders were cherry picked. I have uploaded it here http://d-h.st/xz6
I did notice in init that it checks whether an sd-ext image exists, perhaps this could be modified for NativeSD
I am a bit of a linux noob still