[Q] How does WinMo build affect performance, battery life of Android? - HD2 Android Q&A, Help & Troubleshooting and Genera

Just trying to understand how the choice of Windows Mobile ROM affects the performance and battery life of the Android if the haret.exe file shuts down the Windows Mobile portion of the phone. If this is the case, wouldn't the Windows Mobile ROM portion not matter unless it is running in the background?
Just trying to understand what is going on with this WinMo-Android compatibility issue.

There are a few registry tweaks that can be made in WM. These pertain mostly to the SD card. They must affect the way android picks up the system once it is handed off by windows.

Your choice of rom has a pretty significant effect on how well Android will run. Running Android off the SD card is essentially running 2 OSes at the same time, Android-over-Windows, so therefore the efficiency of your WM rom has a direct effect on your android rom.
I've been running Shubcraft 1.4d for the past week over 3 different WM roms with different results on each one. Running over the stock T-Mo rom was some serious butt-hurt. It was slow, buggy, the battery life sucked, the volume was too low, and nobody could understand me cause of the robot voice thing. On VBN rom it ran much better but the battery life was still kinda crappy. On ChuckyDroid(my current rom), it runs FANTASTIC & battery life is great(for Android anyway, it's still not as good as WM but I can easily make it through the day with moderate use). I get about 1% an hour battery loss with my current combo.
Your radio can have a big effect too. The wrong radio can give you the robot voice problem and cause compatibility issues.
You should also fully format your SD card before attempting to run Android. There's an sd format program listed in one of the threads on here & it is awesome. I used it last night & while it took about 4 hours to completely erase & format, I have noticed a HUGE difference in the way my phone runs now. I'm topping out the charts in benchmark tests now.

kabuk1 said:
Your choice of rom has a pretty significant effect on how well Android will run. Running Android off the SD card is essentially running 2 OSes at the same time, Android-over-Windows, so therefore the efficiency of your WM rom has a direct effect on your android rom.
Click to expand...
Click to collapse
Sorry to disagree, but I think you're only partly right. It is correct that your WinMo hoice affects or can affect android performance in some ways. What is not correct is that Android runs over WinMo. From my understanding, Windows Mobile only initializes drivers for the hardware (this is why different ROMs may indeed result in different android performance). Booting the Linux kernel then completely shuts down Windows Mobile. Android is not an "App" running in WinMo, but a completely independent OS once the Linux kernel has been booted. BTW, I'm not trying to be a smartass here, just trying to clear this up

another thread with the same old question...

I agree with tsrzealot. It is not android-over-windows. It is not windows running emulation software running android. That is 100% incorrect. Android cannot boot directly from the phone's hardware, it requires windows to start the boot process and nothing more. There is some difference in how each winmo hands off the hardware to android.

Related

[Discussion] NAND boot Android on HD2 (No it doesn't exist, just development)

So, I figured with Android getting ported quite nicely and is fairly well along, we should start working on getting it flashed directly to NAND. Eliminate Windows Mobile all together. So here are my notes. All this stuff combined in some order and sense will make it able to flash NAND with Android. But for some reason I just can't piece it all together and make the puzzle fit. I am posting this in hopes that someone with enough skill can take the information and build what is needed.
Working Tinboot - This is what the core of NAND android flashing is.
NBH for installation (Examples) - Needed to install android. Flash nbh, install android, reboot
To test all of this we need the RESUMEADDR of the HD2. Then we can pass RESUMEINTOBOOT to haret. Then we can check if there is enough low-level hardware support to even boot Android yet. This can be gotten by using haretconsole. But I have yet been able to get the RESUMEADDR because of issues with my computer.
Thanks goes to dzo for pointing me in the right direction for all of this.
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
i agree but...
zarathustrax said:
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
Click to expand...
Click to collapse
i agree with you, but this guy is asking for help do do a certain task.
I second you on your idea but there are people that would prefer to have a win mo. phone running android even if it runs slower or worst because some people just dont like wm. software.
By the way i cant help you jmztaylor because i just dont know...
zarathustrax said:
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
Click to expand...
Click to collapse
well running android from sd card creates higher battery consumption. Am I right? this is a good argument.
jojo_angelov said:
well running android from sd card creates higher battery consumption. Am I right? this is a good argument.
Click to expand...
Click to collapse
Yeah, that is true. Reading about the nand ports for other winmo devices show that battery is improved, but it still isn't no where near as good as winmo is with batteries. Power management is one of the issues that almost all android ports have.
At this point, i don't believe nand flashing is possible for the hd2... like i said, they need winmo to initialize many things. Also, once it is possible to flash nand, it probably won't have as much working hardware as the haret version until they get drivers that initialize all that hardware. If you look at some of the other nand flashable ports on other phones, things like wifi, bluetooth, camera, gps, etc don't work while they work when you use the haret bootable version. We're still a long way away from booting from nand... at least a version functional enough to want to get rid of winmo.
I'm really curious as to what peoples reason is to want a nand flashable version so bad.... I've heard people say that winmo is still running in the background with haret, but thats just not true. You generally have a much more functional android when run of storage card than the nand flashable ports are. There may be a small increase in battery life and small increase in speed when flashed to nand, but you will lose a lot of functions until they find ways to initialize the hardware without winmo. And from what i've seen with the hd2 ports so far, I don't think we will have any issues with speed like they did with other devices, so I don't see nand being needed to increase speed.
cmon people, lets support the motion.. remember we are dealing with one of the best htc-winmo devices here, the one of a kind htc-hd2..
for me the point is not "what is the need of doing this", the point is "it can be done "
maybe one shouldnt rush to start flashing android on hd2, thats why alpha and beta versions are made, where one understands the risks but does it anyways for the fun experience.. n remember this is just the beginning of android on hd2, i think there is room for a whole lot of improvement
zarathustrax said:
Yeah, that is true. Reading about the nand ports for other winmo devices show that battery is improved, but it still isn't no where near as good as winmo is with batteries. Power management is one of the issues that almost all android ports have.
At this point, i don't believe nand flashing is possible for the hd2... like i said, they need winmo to initialize many things. Also, once it is possible to flash nand, it probably won't have as much working hardware as the haret version until they get drivers that initialize all that hardware. If you look at some of the other nand flashable ports on other phones, things like wifi, bluetooth, camera, gps, etc don't work while they work when you use the haret bootable version. We're still a long way away from booting from nand... at least a version functional enough to want to get rid of winmo.
I'm really curious as to what peoples reason is to want a nand flashable version so bad.... I've heard people say that winmo is still running in the background with haret, but thats just not true. You generally have a much more functional android when run of storage card than the nand flashable ports are. There may be a small increase in battery life and small increase in speed when flashed to nand, but you will lose a lot of functions until they find ways to initialize the hardware without winmo. And from what i've seen with the hd2 ports so far, I don't think we will have any issues with speed like they did with other devices, so I don't see nand being needed to increase speed.
Click to expand...
Click to collapse
why dont we just have it running from internal memory without flashing? it would solve the speed and battery problems and we would still get to keep winmo . or is there a reason this cannot happen?
Well, knowing that android builds (system and user data) take about 530MB, it would be a tad hard to stuff in the HD2's 512MB, of which about 300 are used by Winmo...
Maybe on the 1GB TMOUS though....
kilrah said:
Well, knowing that android builds (system and user data) take about 530MB, it would be a tad hard to stuff in the HD2's 512MB, of which about 300 are used by Winmo...
Maybe on the 1GB TMOUS though....
Click to expand...
Click to collapse
but most of us have the 512 mb version
i would be interested in getting android stored on the device memory (Not a ROM flash). NRGZ28 released a winmo version that is very small (50 or 60MB) leaving me with 800Mb+ of internal storage. what must be changed to get HaRET to look in internal storage for the files and store information there?
This should be a very good discussion..btw ive been running off of sd card for a while now and battery consumption isn't that bad at all
As far as I see it, a major problem is for any non TMOUS HD2 owners an SD card will always be mandatory. Even if you are able to fit the whole system into the half sized NAND, there wouldn't be much room left for anything else.
And even on the TMOUS, it would be good to put Android and the Apps on internal memory, and have everything else on the storage card, like pics and such.
Main reasons I see for doing this, is once it's working a version that doesn't need to use WinMo can boot faster, and might be able to solve some issues eventually, like not needing a specific file in WinMo or specific ROM just to get calls working correctly.
As well, It gets annoying when even with bootloader it takes longer to boot back up, and I still sometimes get a voicemail or text message while HaRET is loading, and I have to reset, boot windows mobile, remove CLRCAD, reboot, and check the voicemail and texts. If I don't clear it in WinMo, sometimes I get a voicemail message notification every time I boot android even if I don't have any voicemail.
cavemaneca said:
as far as i see it, a major problem is for any non tmous hd2 owners an sd card will always be mandatory. Even if you are able to fit the whole system into the half sized nand, there wouldn't be much room left for anything else.
And even on the tmous, it would be good to put android and the apps on internal memory, and have everything else on the storage card, like pics and such.
Main reasons i see for doing this, is once it's working a version that doesn't need to use winmo can boot faster, and might be able to solve some issues eventually, like not needing a specific file in winmo or specific rom just to get calls working correctly.
As well, it gets annoying when even with bootloader it takes longer to boot back up, and i still sometimes get a voicemail or text message while haret is loading, and i have to reset, boot windows mobile, remove clrcad, reboot, and check the voicemail and texts. If i don't clear it in winmo, sometimes i get a voicemail message notification every time i boot android even if i don't have any voicemail.
Click to expand...
Click to collapse
agreed..then maybe after studying the 1gig version they can find a solution for the 512 version
Battery life isnt great on current builds but it is usable. Much of the issue is due to it being an a sd card. Once they put it on nand, battery life will be even better. As good as winmo? You never know until you try.
I dont get why people are all too ready to rain on someones parade. I say, if there is a possibility of making android boot on this thing, why not try it? WinMo is dying, some of want to jump ship and take our hd2s with us.
It seems that getting nand to run is a priority to devs. Check out the first 7/23 post at http://robsbay.co.uk/
These guys have been making a port much faster than others have anticipated. According to doom-sayers, we shouldnt have been at this point for another few months at least. Im willing to bet this thing will be booting on its own and running efficiently well before the doom-sayers would have expected us to even have this thing running on a sd card.
zarathustrax said:
What's the big deal about flashing it to nand anyways?
Click to expand...
Click to collapse
- Reliability
- Speed
- Battery life.
- Access to memory card as a removable device while Android booted.
Even a class 10 card can't compare to the speed of the internal nand.
Pagnell said:
- Reliability
- Speed
- Battery life.
- Access to memory card as a removable device while Android booted.
Even a class 10 card can't compare to the speed of the internal nand.
Click to expand...
Click to collapse
I completely agree. As others have noted, the main issue is initializing hardware. As an interim step to 100% Android, why not build an extremely slim WinMo with Android cooked into the NAND ROM.
I'm using desire v5 with latest Cotulla zImage it's pretty fast even off of a class 2 microSD. I really think my HD2 would be just as fast as my wife's EVO if the same thing were on the NAND.
nand boot tmous
any tmous user actually copy all of the files over to their phone's memory and try and boot haret? Or would this be detrimental to the life your WM phone?
I am a T-Mobile HD2 user and I think flashing from NAND would have many benefits. Lets do it up.
I am a T-Mobile HD2 use and this is great because we can boot both winmo and android from the nand, which is insane. All the non US users want to shut this down, because they are left out.
Leader2light said:
I am a T-Mobile HD2 use and this is great because we can boot both winmo and android from the nand, which is insane. All the non US users want to shut this down, because they are left out.
Click to expand...
Click to collapse
so have you booted it from the nand with your hd2?

[Q] Continued support for dual booting?

ok, Ive been using both android and WM 6.5.3 and frankly i couldnt think of a better combo, Ive spent months try to decide which one to move too and in all cases neither one wins out overall, then it hit me, why do i need to have one OS!
Android does everything i need socially, and WM covers everything i need for work and roaming the mountains so Id love to keep both
I guess what im asking you developers given that progress getting android and NAND working is this, will there be continued support for having android running from SD
so over to you guys!
interesting point, but i think android running from SD is sufficiently well progressed that if there were no more releases it would not be a major problem.
There current builds a very good for day to day use.
I would like to see WM ruinning from SD on android devices, because like many here I have inversted alot of time with winmo and have many apps that can not be easy replaced on android.
And because there is very slim chance of there being annother winmo 6.5 device ionly see a future with my next phone being android, so it would be great to have the option to roll back to WM every once ina while to use that app that you cant get anywhere else.
that is a good point, i hadnt considered that option but makes perfect sence as well, like yourself i have many much needed WM apps whichwill never exist on android so that option would equally be valid, my only issue would be i couldnt test this out for any length of time as i do need WM apps almost daily, after hours and out of work its always android running
is there anyway to dualboot android from nand? people dualboot windows and linux on a pc without needing to use a live cd every time. i don't know the specifics, but personally, i'd love to dualboot windows and android both from nand. while i just about always use android, there are times when i need winmo (few, but they do exist). that said, i'm still keen toward the benefits of having android running from nand (better battery life, no need to boot into winmo to transfer files, etc.)
I think NAND installation should be more important when an actual build will behave like it does on an Android native phone. HD2 with Android still can't record video at 720p and it still have occasional problems with camera flash. Sometimes 3G connection disconnects. When we will have a 110% working Android build for HD2 we should seriously think about flashing Android to HD2 NAND.

[Q] best WM build for android

ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
matthewharmon102 said:
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
Click to expand...
Click to collapse
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
eenbox said:
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
Click to expand...
Click to collapse
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
matthewharmon102 said:
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
Click to expand...
Click to collapse
What I did was reformatting under multimedia card reader - I do not think it matters but that's what I did.
I did find some registry tweaks that manages sd card power a while ago and tried them under stock rom and radio - it did not work but I never bothered to go back since my battery is not really getting drained - lasts enough for me.
I only installed BSB Tweaks and disabled EVERYTHING and left only power-saving ON. I have no clue whether this helps at all or not but just did it as a preventive measure ... also, make sure auto-lock is DISABLED under Windows. That was one of the old issues to get un-wake-able screens ... however, so far I have not really had any problems.
Keep in mind: if you want to install many apps that you would like to test - do not do it in massive installations one after another. Some apps are known to screw up battery life and stand-by mAs. Therefore, install couple at the time - after reboot if you get low mA - then app is not draining the battery.
So far I have experienced Extended power widget to drain the battery a lot and also any type of news browsers like e-buzz, pulse, etc - they seem to constantly pull data and remain active. However, they may work for you if you have data disabled for the most part (which is probably not the case) - forgot to mention mine is on 3/3.5G at all times.
- Background Data is checked (ON);
- Auto Sync is unchecked (OFF);
- Brightness disabled under very strong light (110 lumens of my flashlight hihihi) and set on 35-40% I think - somewhere around there.
- I have three home-screens and do not feel I need more
- Weather widget, current widget and google search widget - I do not have any clocks for simple reason - when the phone is locked I can easily see the time by clicking the hardware buttons - so what's the point of the background one ...
If I remember any other tips and tricks I'll let you know.

How well does your HD2 run?

Well, I got my HD2 to run Android okay, I guess. It does run better then the Vibrant. . .
But, my battery life sucks and I have no file transfer while running Android due the damn OS being on the SD card.
The WMO has all kinds off little glitches. . . . The battery life is half decent. But, there are no apps and it feels like Windows.
Anyone out there with a HD2 running at 100%? And if there is, it is hard to believe.
Uh...yeah? Mine runs pretty damn great with a custom WinMo ROM applied(Energy)...haven't soft reset in weeks. And there are applications for Windows...you just have to think outside the market
Well, the Wmo runs way smoother over time. . .
I am also running a Energy ROM. . . It's still has some glitchiness to it though.
samson_420 said:
Well, I got my HD2 to run Android okay, I guess. It does run better then the Vibrant. . .
But, my battery life sucks and I have no file transfer while running Android due the damn OS being on the SD card.
The WMO has all kinds off little glitches. . . . The battery life is half decent. But, there are no apps and it feels like Windows.
Anyone out there with a HD2 running at 100%? And if there is, it is hard to believe.
Click to expand...
Click to collapse
Mine runs awesome on the stock 3.14 ROM. It also runs awesome with a stripped 3.14 ROM and the Bluetopia 1.0.4 Android Build. I am getting about 12 hours of heavy use and more than a day if I turn off my data when I'm not using it. These phones are what you make them. You just have to try a lot of things out.
Out of the box with the stock rom they weren't awesome. Touch response was great, but it froze a lot. Then they updated the rom and it had ****ty touch response but didn't freeze. So people cooked ROMs with 2.10 touch drivers. Then they came out with 3.14 and everything worked.
On top of this, there are a ton of stable Winmo cooked ROMS to choose from.
And as of recent, there are flawless Android builds out there that run perfect with 3.14 stock ROM and lot of cooked ROM's as well. I prefer a stripped down 3.14 ROM for Android only use.
If Tmobile ever comes out with an Android native phone that is as nice as my HD2, I'll pick it up. Mostly because I know that WinMO 6.5 is dying and because the Android market is WAY bigger with better programs and utilities. I would end up keeping my HD2 and running WinMO only on it. I would also continue to play with it. I love to get my nerd on and the HD2 is the perfect phone for tinkering. But, I don't know when that will be. Not losing my screen size or the build quality/hardware awesomeness and I haven't seen anything comparable yet.
I don't mind rebooting into Windows to transfer to my SD card, but I'm also fine with shutting it down and pulling the card out and using an adapter. I guess it would be easier if you could just do it through Android but this isn't an Android native phone and it seems acceptable to me.
In the beginning my leo was a worthless pos, somehow over time it has begun to operate much smoother. A few downloads from this and a few other sites have straightened out some flaws
Be careful posting "issues" with your leo, you'll find that some loose cannon members on forums become extremely unstable and will begin kung fu flaming you until you never want to see another smartphone ever again.
then tear into your mom.
kick your dog/cat
etc.
Lol. . . . Flaming I can take. . .
Well, a few ROM's later I seem to have my HD2 running even better.
The file transfer is weak but like stated above, it is what it is.
A stripped down ROM really seems to best way to go for running Android.
I was also having major battery issues and today I finally found out why. I was using HandCent SMS. What it did was, it would wake up the phone and stay stuck at a 60 mA draw.
Removed the app and installed GO SMS, which has less then 1/3rd of the features of HandCent, but it does not hang up my phone.
So, it is getting better with time.
As far as hardware the HD2 is only second to the HD7(which just looks amazing).
But, the software is what makes the HD7 a 4.3" display having paperweight.
What are you guys talking about ? You can transfer files while booted in Android even if it is in the SD card.. Pull out your SD card while Android is on and it will still work.. I can transfer files fine.. Just change the mode from charge to disk mode..
MarlinFF said:
What are you guys talking about ? You can transfer files while booted in Android even if it is in the SD card.. Pull out your SD card while Android is on and it will still work.. I can transfer files fine.. Just change the mode from charge to disk mode..
Click to expand...
Click to collapse
I feel like a dumb ass. I didn't even notice the disk drive option. Thanks.
Is it safe to do since everything is installed on the card to copy to it while the OS is running? I assumed it didn't work and would not be a good idea. I didn't try to transfer anything, but it does work. I guess since the OS is actually running off the internal memory after you run Haret that it's cool. I just never really thought that much about it.
crisisinthecity said:
I feel like a dumb ass. I didn't even notice the disk drive option. Thanks.
Is it safe to do since everything is installed on the card to copy to it while the OS is running? I assumed it didn't work and would not be a good idea. I didn't try to transfer anything, but it does work. I guess since the OS is actually running off the internal memory after you run Haret that it's cool. I just never really thought that much about it.
Click to expand...
Click to collapse
My HD2 runs great. I use Core Cell Evo v4.1 on the WinMo side and use Darkstone Froyo Sense v3.2 on the Android side...works great for me.
I transfer files quite a lot and no problems.
If you eject your sd card it will continue to work but, when you install sd card again most things won't work and, then will lock up (I tried that and I have to pull battery, then reboot).
I did notice if you leave it hooked to your PC (disk drive) and don't use the default ringtones, they will default to them in Disk Drive mode.
My HD2 runs so well using BlueTopia that it has replaced my G2 as my primary.device I carry two phones, 1 for work and 1 for personal use.
-------------------------------------
Sent via the XDA Tapatalk App

[Q] Android on NAND or SD - is it worth it?

Hello guys....and girls if any
i'm a bit of a noob, managed to get Android working from SD but thinking of putting it on NAND. My question(s) to you guys:
IS IT WORTH IT?
is the battery life - any better or at least equal to winmo?, functionality wise, is it 100% working?
Is having 2 OSs more versatile, is it worth getting rid of winmo and its apps?
Awaiting replies from members that have Android NAND for a while and can give a full view
I apologize if this question has been asked before...i looked...couldn't see a thread like this.
Thanks
Only recently did I switch to android on my HD2. I used WinMo Stock Rom before, but I had a lot of problems with Windows, I wasn't happy about the general UI and the lack of "modern" applications.
So 2 or 3 weeks ago I decided to switch to Android NAND. Here are some of the points witch made me use NAND instead of SD.
1st: Space. I only have a 2 GB SD, so a SD Rom would've taken 'all' or most of my SD Card Space.
Installing it on the ROM saved me a lot of Bytes. ^^
2nd: No trouble with 2 OSs. As I thought that WinMo was useless anyway, I thought it to be stupid to still have it and let it consume space. I thought, NAND can't run worse as WinMo did for me, so why keeping it as fallback ROM. Also, I have an old phone (Sony C905) to fall back when flashing ROMs or if any problem would occur. (Just to mention it, I did not have any problems at all really)
These where my main points to use a NAND ROM (I am using this one here by gpc: http://forum.xda-developers.com/showthread.php?t=909096 )
After having used a NAND Rom for a couple of weeks now, I made the experience that these ROMs run very smoothly. Everything works for me, the sync between Google and Android is awesome. I followed the instructions of the cooks and did not have any problems with GPS, Bluetooth, Wifi, ... everything is working fine (exept stock tethering - but that can be easily achieved by 3rd-party apps). My Problem is, that I flash relatively often and I do not use any kind of backup so I have to reinstall all my apps. But the 200+ MB which the ROM leaves free from internal memory enable me to install a lot of apps and the market helps me to easily reinstall all of them after a flash.
Overall, Android Gingerbread is more stable (as to your question: I'd say it is working to 95%, and the 5% missing being non-essential, or can be achieved by 3rd-party-apps), has more functions, and drains less battery than WinMo6.5 - in my own personal oppinion... and it only took me half an hour to get my device from Win to Android. So I still do not see the point in leaving WinMo on the device and use up space of your SD Card.
But you should ask yourself, what do you need from WinMo, what do you need from WinMo what it can not do, and what can an Android-ROM do for you. And if you find for yourself that a NAND Android can do everything you need from your OS (or even more), than where is the point in still using an outdated OS?
I hope I could help.
PS: There are a lot of votings here on XDA and as far as my memory goes most of them voted for NAND-based roms... so I don't think that I am alone with my oppinion.
EDIT: BIG WARNING Thou': I should read all posts (especially sticky-ones) carefully to see, if you have the right Radio, and so on! a NAND-Rom _does_ have some kind of risk installing, and I don't want to be held responcible for bricking your phone. I am just telling you my personal experience as a User (I am neighter a developer nor have I ever flashed a phone in my life before), but I know, that there are some Users which did encounter problems. It's your decision in the end, I guess.
-felt like adding a disclaimer-
It depends if you still want winmo or not. Battery life is about the same as SD for me, overall performance is about the same as SD builds, but there are some bonuses with nand, like you can change sd cards, use recovery, couple other small things. If you don't use winmo anymore and don't want it, might as well put android to nand. You have to decide if losing winmo is worth it. Personally I use SD android because I have WP7 on NAND. I used NAND android for a while, and when I went back to SD android, I didn't really notice any difference. SD android is good enough for me and I think being able to have 2 OS's on my phone is much more important and is what makes the HD2 unique and special. If I just wanted android, I would have gotten a native android phone. When you put android on nand, it makes it just like any other android phone and there's nothing it can do that many other phones can't, but when dualbooting you're phone can do things that no other phone can do. And I use WP7 just as much as I use android now, so it's great having both OS's on the same phone.
I was pretty happy with WM+Sense on Stock T-Mobile HD2. And I'm expert-user of WM. But with so many apps for Android and so few NEW apps for WM - it is hard to resist. So I moved to Android SD-mode.
At that point I liked everything except battery life. And GPS Fix was slow. I tries few SD ROMs ... liked them all, not much difference for me. To fight battery drain I moved to NAND.
Speed-wise I do not see any difference between NAND and SD. My battery life is better with NAND. But then again ... may be ROMs get improved, may be I got more experience with how to manage things battery-wise. Got my slow GPS Fix resolved, but I'm sure it would work on SD-mode too.
I would almost all equivalent apps for Android to replace my favorite WM apps.
Bottom line is (for me).
1. Battery is still BETTER with WM. I have to charge every day with Android, with WM I could go 1.5 days, sometimes even 2. But then again ... Android is more into "cloud".
2. Booting into NAND directly is not much faster than WM+Android SD.
3. There is NO navigation with TTS+reliable map/poi source on Android which can be compared to properly skinned Primo 1.1 and that is my ONLY big complain.
4. Overall user experience with Android is better. For me at least. And it crashes much-much-much less than WM. Surprise !
Overall I'm happy with my WM->Android move and I'm not going back. But hey, I was happy on WM too

Categories

Resources