Database Users

[Q] Android Folder onto HD2 Phone How come?

Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?

AngelDeath said:
Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
Click to expand...
Click to collapse
hi
Haret cannot currently read from NAND, its code reads and searches for Data IMG and Rootfs and kernal in SD ONLY .....
hence NAND is so very different from HARET.
well Magldr is what would do the trick

I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.

AngelDeath said:
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
Click to expand...
Click to collapse
hi
Well firstly NAND does not necessarly mean booting from start, NAND= Internal memory, in fact cotulla's MAGLDR can boot android of the SD straight from power up whilst having WIN MO on NAND.
So to answer your question again,
HARET CANNOT READ NAND (INTERNAL MEMORY), it always looks for SD for everything , in some cases RAM, as in the new RAM builds that are popping up by devs.
the code for HARET cannot handle NAND at the moment and i dont thing it will ever be implemented.
I'm neither a dev or a hacker, this is just what i ahve understood from reading, i'm open to corrections,
best regds

I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..

greg17477 said:
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
Click to expand...
Click to collapse
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?

mally2 said:
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
Click to expand...
Click to collapse
never say never and expect the unexpected, thats what life teached me
phone wouldnt get bricked if you just read nand, but writing into it could do damage, i agree on this.

OK, so when I first read the OP, I thought he meant booting Haret from the phone's internal storage memory, not NAND.
Though the NAND Haret idea is really not bad, I couldn't see it corrupting the bootloader as long as it behaves the same way as it does from the sd. I mean, the phone is already booted WinMo, so HaRet and Android have no need to touch the bootloader, just as when running from sd. It would be more or less a startup.txt change/ rel_path = NAND/Android (not exact, but general idea). Seems alot different to me from MAGLDR, maybe there is just confusion about this
But if the NAND idea is not workable, wouldn't it be possible to run HaRet Android from the phone's internal storage memory, yielding a performance speed increase and less wear on the sd?
Clearly we couldn't do like I have now, a ton of builds with exceller, all running from internal storage, obviously we don't have 16gb internal. But what about just loading our daily driver from internal, and testing/less commonly builds from sd?
I like the idea because it could mean less wear on the sd, and possibly performance increase
BTW 300th post

Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.

AngelDeath said:
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
Click to expand...
Click to collapse
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02

huggs said:
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
Click to expand...
Click to collapse
Very possible,
Haret needs to be modified for that,
not sure who can do it.

Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers

greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
spot on
NAND = Internal memory

greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
Well true except the TMOUS, which is 1024 mb, so it should be plenty then to run Android this way right?
Even with just 300 left after WM ROM, Android could still be done conservatively, without much apps installed, or with some kind of a2sd functionality, Froyo has inbuilt app to sd functionality, albeit not as good as a2sd ext2 or ext3 setup.

Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.

Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.

dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD

dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
Its not about putting the whole Android folder into nand, but for example only the system partition, just like in the RAM builds. All data and user stuff goes to sd.
Btw what do you mean by "...*could* be possible to put Android on internal storage(NOT NAND)." ? nand is the internal storage (memory). Or you guys are using different terms do you mean by "nand" the reseverd space where roms are stored and by "internal storage" the free space left (still in nand)?

TheATHEiST said:
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Click to expand...
Click to collapse
Actually your part right, it was tested and released in the initial phases of the Rapheal (aka Fuze) and ran smoothly from what I read, yes there were hiccups, but that was due to the build being still in the alpha stages.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
This is where your part wrong as well. if you use a pre-set data.img file, yes for the most part you cant use anything larger then possibly 512mb on a TMous, 256 on others, definitely could not use the 1gb img file thats for sure, but the other part of this your missing is that if you dont put a pre-set data.img file, during the initial loading of android, android will create the file itself, and IF I am right the file will be sort of dynamic, dynamic in the sense it will expand as needed, I seriously doubt it shrinks. And on top of this you would then use the function a2sd, which in then would install your apk's to sd card. As of right now how much bigger is your 1gb data.img file that everyone added to their SDCards? Bet still the same size.
mally2 said:
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
Click to expand...
Click to collapse
Actually after doing some reading, neither the kernel (if I read correctly) nor is haret.exe the cause of pointing the boot location. I did some searching (Mind you I am NOT a LINUX person), but reading some of the files, I am guessing that the key file which controls the loading of Android, is located in the "init" file in the rootfs.img file. I mounted this file in windows to look thru it and view files, and that file seems to have a major role in it, how it works I dont know yet.
To All, please I am not trying to cause a stir here, I am merely looking at possibilities, and unfortunately I cant test them out since I dont have a spare SDCard as of yet (Will ina couple of days, 32GB SDCard for $40, woohoo), and then I have nothing to loose to try, cant brick the phone, since winmo is the default loading OS anyway. One of the reason it might not have been put on the phone as I said, could be speed, I dont know how much faster internal phone storage would be opposed to sd, but another reason why could be cause then the installation would put folders on the root file system of the stroage card and make it messy. Also alot of people constantly flash new builds, this would also hamper your android install being on the phones storage. And remember our normal HD2 roms are between 225 and 250mb stock or custom, where lite versions or stripped down version would be considered better for taking up less space.
One thing to keep note, during all this, I have an HTC Aria (Liberty) as well that I just recently got as an upgrade to one of my ATT lines, and I checked the internal storage of that phone, its stock with ATT's build of Android, and it has ONLY 168mb of storage available, and it came with a 2gb sd card. Now think about that when saying that the files would get to big, obviously the HTC Aria doesnt have anywhere near the capacity of the HD2.
And again to anyone else, let's be clear, yes the phones storage is a NAND, but just to make clear, we aren't talking about doing a cold boot of android, I know how sometimes that can get confusing.

Sorry guys, yes internal storage is NAND memory, the reason I drew a distinction was to make a distinction between loading from internal storage and ROM space. I only meant to illustrate the difference between the two and demonstrate my opinion that both are possible. I think with further investigation and testing, advantages of booting this way will begin to emerge. For example we will be able to remove the sd card while Android runs, not a great benifit, but you get the idea. But yeah, I should have used the term 'ROM Space' instead of NAND, I only meant to show difference between the 2 places to boot from.
Sorry if i caused any confusion.
Sent from my... whatever

NAND DFT - Sense and free space issues

Firstly, amazing day, finally been able to get rid of winmo and get android into my NAND.
Sadly, i keep running into free space issues which is a bit frustrating. Im sure it might be something i am doing (or not doing), but was wondering if i am alone. As far as details, im running UK HD2, with DFT - SENSE rom flashed into my NAND and radio 2.15. I had no problems with the flash process and the phone generally works well.
I have apps2sd running and it says there are no apps that can be moved to the SD so i have everything where it should be. My SD is listed as 6.1gb free but internal memory is 115in use and about 38mb free. I cant even get copilot to install as it just says there is no space left (although i was running the .apk from the sd to install on the sd).
Could this be because i was previously using the sd card for android? Anyone else having these issues?
Thanks.

geekyhawkes said:
Firstly, amazing day, finally been able to get rid of winmo and get android into my NAND.
Sadly, i keep running into free space issues which is a bit frustrating. Im sure it might be something i am doing (or not doing), but was wondering if i am alone. As far as details, im running UK HD2, with DFT - SENSE rom flashed into my NAND and radio 2.15. I had no problems with the flash process and the phone generally works well.
I have apps2sd running and it says there are no apps that can be moved to the SD so i have everything where it should be. My SD is listed as 6.1gb free but internal memory is 115in use and about 38mb free. I cant even get copilot to install as it just says there is no space left (although i was running the .apk from the sd to install on the sd).
Could this be because i was previously using the sd card for android? Anyone else having these issues?
Thanks.
Click to expand...
Click to collapse
Same problem with me I only have 35 mb free internal memory ,own using cotulla nand desire Rom
Sent from my HTC HD2 using XDA App

try the desire hd version, it has a bit more space ..
the owner of a hd2 (us) with 1024mb have no problems with that ..

Hi
Did you try titanium backup to move apps from nand to SD, it should be better to give it a try...

Using nexushd2 I have 216 MB free space.
Sent from my Nexus One using XDA App

Tmo US W/Desire HD 538mb Free!

frankinstine said:
Tmo US W/Desire HD 538mb Free!
Click to expand...
Click to collapse
TMOUS HD2 Rocks

I just get free space only 99 mb on my hd2, i want to know why each device don't be got free space as same as ones.
My hd2 runs in Colluta's desire nand rom.
Sent from my HTC HD2 using XDA App

This is not a problem with you guys, it's just with the 512 limit of our devices.
Be patient and someone /Cotulla/ will fix it so that we can install to SD card.
BTW
I just downloaded move2sd and it works just fine. Now my apps go to the sd and i've moved all possible apps to sd.
I am left with 82 mb which should be enough for txt and logs...

Im glad im not by myself with this. I guess the solution will come when the devs get chance to get ext4 up and running on our sd cards as data.img, that way the problem goes away. apps2sd/titanium etc are all fine, but if you have a lot of apps then you will always be in the situation i am of bouncing off the warning of low space.

The only problem is now the low space...
Hope the devs can add a partition from the SD that functions as the internal memory.
And people with 1024leo's should stfu. It's like saying to a blind person.. hah that's weird I can see perfectly fine.

pr0x2 said:
The only problem is now the low space...
Hope the devs can add a partition from the SD that functions as the internal memory.
And people with 1024leo's should stfu. It's like saying to a blind person.. hah that's weird I can see perfectly fine.
Click to expand...
Click to collapse
Totally agree with the ignorant TMOUS owners saying they have no problems. I used to put a 4gb data.img in with my builds to make sure I had plenty of space. Still early days so lets wait for TMOUS users to come forward saying they have used up all their memory.
Putting that aside, the same problem happens with most other devices. I suppose using Android from SD card we had the luxury of choosing how big data.img to have. Now we are in the same boat as other Android handsets with the exception we cant go into recovery mode. If we could go into recovery mode then we could partition the SD card into two partitions. One for sd card usage like music, pictures etc and the other partition as ext3 to expand the phone memory onto the sd card.
If Cotulla or the DFT enables us to use our device in recovery mode, maybe they should only make it for HD2 Europe devices, seeing as TMOUS owners are all saying they have plenty of memory.

Google Earth and Flash Player are killing me.
They still hold much space after moving to sd.
Looking forward to app2ext.

nokn956120 said:
Totally agree with the ignorant TMOUS owners saying they have no problems. I used to put a 4gb data.img in with my builds to make sure I had plenty of space. Still early days so lets wait for TMOUS users to come forward saying they have used up all their memory.
Putting that aside, the same problem happens with most other devices. I suppose using Android from SD card we had the luxury of choosing how big data.img to have. Now we are in the same boat as other Android handsets with the exception we cant go into recovery mode. If we could go into recovery mode then we could partition the SD card into two partitions. One for sd card usage like music, pictures etc and the other partition as ext3 to expand the phone memory onto the sd card.
If Cotulla or the DFT enables us to use our device in recovery mode, maybe they should only make it for HD2 Europe devices, seeing as TMOUS owners are all saying they have plenty of memory.
Click to expand...
Click to collapse
Sorry man, not tring to be ignorant, I do love my TMo HD2. Ido agree with you on the ext3. I have my N1 w/a2sd and its awesome, no need to worry about space.I had about 95+ apps at one time and still had 150mb free of internal. Im guessing once we get a recovery img. we can then get the ext3 and a2sd working as it should. I have clockworks recovery on my N1 and works awsome. You can Backup any part of your rom even your ext3. Also Amon_RA's recovery is good too cause it has PSfreedom implemented, for those looking at PSFreedom Modds

Idea/thought

Hi guys Android development is evoluvating to new diamention.I have tried from Build from SD cards and RAM version and NAND ROM.The NAND ROM is better of all but the biggest disadvantage is internal storage.when many apps are installed 'memory is low' appearing.even after moving all movable apps to sd card using move2sd.some programmes use internal/phone memory like evernotes,copilot.
so my idea is can't you guys create vitual storage in sd for the NAND like the one we had in SD card based build.which is easy for portablity of data when we update.GUYS YOU ARE BEST DEVELOPPERS IN THE WORLD HERE

This might be useful for those with 512 version of HD2, or maybe even for 1024, and it should be pretty easy to mount file from SD same as data.img from SD builds.
But! The question I had is, do you really need to create thread with "Idea/thought" subject? Can't you call it "Increase data space for NAND builds" or "Mount data.img with NAND build" or something like that? It's cool of course to create "Idea", "Question", "Help", "Please" etc threads...

Hi dude,
the reason I created this is - it gives an idea to developpers to develop in their next nand to focus on more storage as you know new native phones have more than 1Gb internal space it goes up to 16GB. As I have mentioned some apps can not be moved to SD card. You may have different idea on how to open thread which is not nessesarily same to others. Give something which is useful to development of andriod on hd2.cheers buddy

[Q] HELP!! I was going good until these came along!!!

Ladies & gentlemen;
Good day!
Well, I am one of those who admire the XDA BIG TIIIMMEE!! However I have an HD2 and managed to have it as a NAND Android after the help of the XDA (as usual of course!) Anyway when I started looking for new ROMs I have noticed that there is new method or way which I do not grasp, comprehend and assimilate AT ALL....ZIP that is, such as [A2SD+], NAND SD and ClockworkMod.Recovery!!!
What is the difference between running Android on NAND & SD with ClockworkMod?!
I am sorry people because truly I must have missed threads or the way of understanding, so hopefully you'll going to be the teacher of mine for now and always!
Could anyone help me as if I am 7 years old?!!!
THANK YOU XDA & Members!!!!

Android nand is running off internal memory. Sd option is what it says, a build running off your sd card opposed to running it with nand.

Thank you for your explanation, but does that mean if the Android runs off internal memory would make the running proccess faster or it would hepl smoothen applications response?! What is the use if I already have the internal memory, wouldn't be even better off?!

Hello
SD Builds start to boot from SD card while being on WM6.5. The hardware shutsdown WinMo and runs Android on it.
NAND Builds run from the internal memory of the phone(just like where WinMo was before)
RAM Builds load all the OS from the SD Card inside the RAM.
[A2SD+] means that you can use a small ext2,ext3 or ext4 partition in your SD Card for increasing your internal storage memory for installing more apps... so this means more internal space.
ClockworkMod is a small linux-based booting utility allowing users to install Android Builds on-the-go which are stored as zip packages on the SD Card. It allows you to install new kernels as update.zip packages as well without having to re-format your entire phone again, or just to erase all personal data on the sd-ext partition.
So, in fact a lot of things have changed in the last 3 months... these are just a few features i can tell you about every method, but at least I hope this will help you to understand quickly a bit about all that.

You know!!?? I Thank you all guys!!!!

NAND runs off the internal memory and even though you get much lower Quadrant scores, NAND is much more responsive and smooth.
The only reason SD based builds get more Quadrant is because of I/O speeds thanks to the SD card.
SD builds are fast, but NAND builds are much SMOOTHER and reliable and if you can do something on SD, you can do it just as well on NAND (gaming for example).

NAND or SD?

Yes I've searched and have not found a definite answer.
Sorry I'm new to the HD2 coming from a Vibrant but was wondering what is faster and more efficient?
NAND or SD?

Alanrocks15 said:
Yes I've searched and have not found a definite answer.
Sorry I'm new to the HD2 coming from a Vibrant but was wondering what is faster and more efficient?
NAND or SD?
Click to expand...
Click to collapse
NAND has more ROMs and seems better on battery life, but both are good.
If you are going to be Android only (no WP7 Dual-Boot) I'd probably go NAND. However, here are the things I like more about sd:
1) This ROM IMO is better than any NAND I've seen: http://forum.xda-developers.com/showthread.php?t=957652
2) You get more "phone storage" because you can basically choose how much space you have. This eliminates the need for an ext partition on your SD or any fear of running out of app space.
3) multiple ROMs. You can have like 5 roms on SD and all you do is tell the bootloader which to load or change the folder name and it boots!
For those reasons I prefer SD, but NAND offers more choices.

From what I've found, speed wise...just depends on the rom but typically NAND is faster. Stability wise NAND is from what I've used and tried. But it mainly depends on which OS you have on NAND Windows wise from what I've gathered but I don't have any interest in WM6.5 so I've ran all NAND builds lately without any issues.
I have setup a dual boot of WP7 and SD Android and it worked ok but found I typically didn't boot into WP7 as much so I wiped and went NAND Android

orangekid said:
2) You get more "phone storage" because you can basically choose how much space you have. This eliminates the need for an ext partition on your SD or any fear of running out of app space.
Click to expand...
Click to collapse
With the built in Apps 2 SD in Gingerbread it's a easy transfer to memory card without having to install a ext partition. It's all built in on the Applications menu to move them to the SD card to free up app space in the memory

with nand you can also have multi roms on your sd and flash at random. i have about 3 i like best and then flash when i feel the need for a change. i personally prefer nand over sd but if you ask someone else they're likely to disagree. the big reason i like nand over sd is because i see a huge difference in battery life with nand and i also prefer android over winmo. if you like winmo and would use it then go the sd route but if you dont like it & dont plan to use it then go the nand route.