Hello,
i'm quiet new to use Android Build on HD2. So far i used SD Builds and NAND Builds.
Can anybody help me understand the Pros And Cons of each configuration ?
I mean i would like to understand :
1. What is the less battery consuming configuration (SD Builds, APP2SD, with 2 partitions ? with 3 partitions ? RAM Builds)
2. What is the configuration that provides the best performances ?
PS: for information i have a Leo 512 with an micro SD 16GB class 10
Ok,
SDcard builds use more battery as it's constantly accessing the card.
Apps2sd moves some of your applications to a partition on the sdcard (You have to create this partition yourself) to save room on the phone's memory, as if you use a lot of apps you can fill up the memory on the phone. It uses some extra battery power, but not constant
number of partitions doesn't matter.
RAM builds is the only decent option in terms of battery usage, also it has the best developers working on NAND roms (in my opinion, sorry if that upsets anyone)
You'll have to try different builds yourself to find out which works best, I've seen NAND builds that empty your battery in less than a day and some that seem to last days, with the same 'configuration'
As with everything on this forum, you need to TRY things for yourself. Just make sure you have HSPL installed
Good luck
Many thanks for your info it helps a lot !
Related
Hey everyone, I am glad NAND is finally released (for those that have been waiting for it), but I'm wondering if theres anyone (yes I know the pros of having NAND Android) that prefers being able to dual boot? I'm starting to feel that work will halt on the SD/RAM builds. Any reassurance? Thanks guys.
I'd like to keep SD builds as well.
Sent from my HTC HD2 using XDA App
Naw I think a lot of us non-TMOUS HD2 owners will still use SD builds. Reason being, we just don't have a lot of storage space, which many of us need. Unless Devs perform the ext4 partition thingie onto or sd card, for us to expand storage, storage will still be small for non-TMOUS HD2 NAND users i guess.
Yes, RAM builds are the biggest source of competition for NAND - however, I haven't filled up my storage yet with my apps and still have about 90/100MB left of phone storage.
What about installing apps to SD card???
Signal strength is much better on NAND though for me.
Can you report how many %of the.time without signal with sd and %with nand? I believe you but I didnt test nand roughly because of the memory limitation. But I guess thats gone now
I hope the response will be "No". I use the PSX Emulator (FPSece) on WinMo so I prefer switch on Andoid or on WinMo.
Nand is obviously the next stage of evolution in rom development towards running Android natively on our hd2's.
sd card builds have the great advantage of being swapped easily, especially with multiple sd cards (I have two, one stable daily use which is fully configured and one experimental)
Moreover the risk of bricking your previous device is rather low from sd..
I am not very clear about the difficulty of transferring a build from an sd build to nand and vice versa, but if there could be a migration tutorial, as a sticky we could have both, latest builds in nand and the choice of running them from sd..
Is this technically possible? Which factors could inhibit easy migration?
Sent from my HTC HD2 using XDA App
I thought originally MAGLDR was supposed to be able to multiboot Android and WinMo (probably a non-sense version of each due to space)?
I hope MADLR can do the following soon:
- Load SD\RAM\NAND Android from custom folders on the fly
- Allow backup\restore of the data store
- Load WMP 6.5 and maybe even 7
I think this will keep the flexibility of multiple build loads alive which will benefit the user and the devs. I know some of this should be coming but it would be nice to get all of our belated Christmas wishes.
not sure but,,
im not sure but the aMAGLDR menu does also have the option to boot from SD-card, i havent tried it yet though..
also one thing i still want is the ability to boot my ubuntu-sd-card build, now i cant use haret.exe im not sure how to go about the dual booting thing ??
much stuff to try out
***edit***
ok, just put the contents of an old sd card build directly onto the root of an sd card (ie, without the 'android' folder) booted phone holing power key until magldr menu shows, then select boot AD from SD and it boots just like the old sd card with haret method, -
so far i see it finds zimage and initrd.gz, then i get the boot screen, .... looks like dual booting is still an option even if it may need a bit of tweaking.. i guess its just the startup.txt that needs to be read for it to boot properly ,
*********
I think in the original NAND release thread, Cotulla explains that a SD build (haret.exe) and a NAND build are very different, to use the SD boot option in MAGLDR, you need to put the content of a NAND build on the SD card, somehow...
edit: forum.xda-developers.com/showthread.php?p=10202441#post10202441
I would like it if they could implement a better DFT installer, which had options such as
• Install to NAND
• Install to SD
• Customise partitions
• Multiboot
Instead of just being able to install to NAND. This way, we can have a single installer / release for both methods (and this would make it easier for chefs )
HectiQ said:
Can you report how many %of the.time without signal with sd and %with nand? I believe you but I didnt test nand roughly because of the memory limitation. But I guess thats gone now
Click to expand...
Click to collapse
I think it's impossible to say for how long - but on Darkstone 1.5 RAM, and MDJ's HD4.6 I would find the signal to have disappeared at least once a day up to three times - requiring a reboot of the phone - airplane mode did not seem to work.
After reboot signal would return to full strength in the same exact spot.
Problem is the signal would be lost in a pocket or on my desk and you simply would not notice it until you went to use the device - in fact the first time I realised it was happening was because I was getting far fewer emails/smses and calls and the phone was utterly quiet - very peculiar for the holiday season and party planning.
I haven't as yet downloaded a NAND build although i may well do that this evening, however having downloading many different builds for Android over the last few months i can safely say Dark Stone's SUPERAM blows everything out of the water in terms of speed it really is very fast which IMO is very important.
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).
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.
Hello.. I have a question.. What is best rom Android: Nand or SD ?
What and because of ?
if you did some search you'd have seen a lot of similar posts..
but here's your answers:
it actually depends on what you want
SD:
- No actual change on your device memory so Windows will be intact and it will load after every boot
- WinMo has to load first = longer boot time for Android
- sligtly higher battery consumption than NAND
- newer builds (builds for SD/MAGLDR, ROMs for NAND) are quite fast almost like ROMs (I emphasize the almost)
- you can try several Android build at the same time, and changing from a build to another is easy, and installing new builds is a simple copy/paste operation.
MAGLDR:
same as SD but you don't have to load WinMo first.
NAND:
- it will remove WinMo from your device completely so device will boot straight to Android
- sligtly lower battery consumption than SD (like 1-2% to be honest)
- it's like having a native android device, lags are less than in SD builds and some apps will run better.
- Changing ROMs is a bit more complicated, and needs flashing everytime. you can still run MAGLDR builds, but haven't tried it myself.
you need to figure out what you want of your device, and how you want to use it. for example, I still have some programs on WinMo that I can't do without and there's no equivalent on Android, and I don't like going through MAGLDR, I don't mind extra 50 seconds to boot so SD is the best for me.
if you're going for android for the first time, I recommend trying SD first. it's simple, and you'll learn a lot without risking to brick your phone, then after a week or so of reading about NAND android and how to flash it you will have some experience to flash and run NAND android safely. My advice, look for the threads where people had problems flashing NAND ROMs, the more you read about errors, the less you'll have them
use Android, NAND, and flash as key words.
Hi ,
Can you please tell me which SD ROM is less battery consuming . I tried every thing but not able to stop Hugh battery loss while using SD ROM .
Dr.Move said:
if you did some search you'd have seen a lot of similar posts..
but here's your answers:
it actually depends on what you want
SD:
- No actual change on your device memory so Windows will be intact and it will load after every boot
- WinMo has to load first = longer boot time for Android
- sligtly higher battery consumption than NAND
- newer builds (builds for SD/MAGLDR, ROMs for NAND) are quite fast almost like ROMs (I emphasize the almost)
- you can try several Android build at the same time, and changing from a build to another is easy, and installing new builds is a simple copy/paste operation.
MAGLDR:
same as SD but you don't have to load WinMo first.
NAND:
- it will remove WinMo from your device completely so device will boot straight to Android
- sligtly lower battery consumption than SD (like 1-2% to be honest)
- it's like having a native android device, lags are less than in SD builds and some apps will run better.
- Changing ROMs is a bit more complicated, and needs flashing everytime. you can still run MAGLDR builds, but haven't tried it myself.
you need to figure out what you want of your device, and how you want to use it. for example, I still have some programs on WinMo that I can't do without and there's no equivalent on Android, and I don't like going through MAGLDR, I don't mind extra 50 seconds to boot so SD is the best for me.
if you're going for android for the first time, I recommend trying SD first. it's simple, and you'll learn a lot without risking to brick your phone, then after a week or so of reading about NAND android and how to flash it you will have some experience to flash and run NAND android safely. My advice, look for the threads where people had problems flashing NAND ROMs, the more you read about errors, the less you'll have them
use Android, NAND, and flash as key words.
Click to expand...
Click to collapse
if you're getting a 60mA/h standby it's because you've let WinMo run for a while. Install any Android loader, I recommend Exceller's because it can load multiple builds on your SD. And make the loader run at startup (or just choose auto 15 seconds from the menu) then restart and let Android load.
It is recommended when using SD Android that you restart your phone before running android because of that issue.
As for the builds I'm using the ones in my signature and both have very little battery consumption, also MCCM GS10 has little battery consumption and is stable enough to use if you're into sense 3.0 as for senseless builds you can try Isayah's builds, or the popular American Android. they all have little battery consumption, but will have ~ 60mA/h consumption when I run them after a while of using WinMo.
Hi
Tried to search for quite a while now.
Unsuccessfully.
so I'll ask; is it possible to dual boot the HTC hd2...
.......with two versions of android BOTH on the sdcard.
not different cards. The same on (assuming there's enough space)
Sorry if there's a previous thread: couldn't find it.
Many thanks
Yes. One method is to use two NativeSD ROMs. Higher the class sdcard the better it works.
All you need to do is install the NativeSD ROMs in the ext4 partition and then when you want to change from rom1 to rom2 you just launch the application, choose rom2 and reboot.
http://forum.xda-developers.com/showthread.php?t=1869673
thanks very much to that/
you can even triple boot
try the links below, it might help
thanks for that! i had no clue but triple boot would be great!
one for daily use, one for performance, and one for testing! :laugh::highfive:
Some guys have around 12 android native sd roms running from same sd card and wp7 running from nand
Sent from my HTC HD2 using Tapatalk 2
i've currently managed five android roms on an 8gb sdcard, with extremely high performance on all but one.
however, from what i've heard, and read you need a lot larger sdcards, often just for one or two roms. could u please explain whats going on? and what does the card class have to do with it? cosidering you have 3 hd2s in the family, all with high level mods, i'm sure you know
You will need atleast 1 gb per rom to install more apps...so partition according to your needs...remaining fat 32 portion is common to share between the rom s installed..so if you want lot of music or movies, naturally you will need more...also if you have wp7 on nand, you will need another partition for that..so you probably will need larger card...
I have 16 gb cards with wp7, 2 native sd android rom
Class 4 atleast will ensure better speed..use sandisk...
Sent from my HTC HD2 using Tapatalk 2