Database Users

anyone found a hero thats fast?

every hero i have tried is slow.. or gets painfully slow after a day of use..
anyone found any hero that works and is fast?
and im on a class 6 card.

im with you on that one.
i actually want to know if its something i am doing wrong.
i mean im installing the HERO ROMS and partitioning the SD cards as directed but 3 HERO ROMS i ahve tried have been so slow that they dont even respond to my finger touches to move over even if i try really slow and hard not a quick flick.
i installed the Evil Hero Rom 1.3x last night and this mornign after i took it off the charger at 10am by 1pm i was down to 23% batter life WTF and NO blue tooth, NO wifi and NO GPS at all and i wasnt even usign the phone it was just sitting on my desk while i took care of work.
i removed that ROM and installed the JACHeroSki-v1.4-sapphire that just came out today and its just as slow so i removed that one and tried
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B CC v1.3b and same thing just as slow.
all 3 HERO roms i have tried are so slow on my Mytouch that they just get HTC splash screen reboots and do not respond to my finger touches for anything.
so at this time i really do not think its teh ROMS per say but something I am doing wrong because i havent seen anyone else complaining like me, a few people saying quirks and some saying they lag a BIT but not as slow as i experience.

are you guys on 32A?? I just installed the MyHero rom and its the fastest one ive tried so far. time stamp issue still prevalent though

im on 32B and i have always made sure i do a complete wipe using the recovery image first before flashing the new roms
i mean i dont even know much regarding COMPCACHE and SWAP ROMS
some say COMPCACHE and some say SWAP
both ROMS alwyas have details included that state you MUST have 3 partitions setup fat32/ext2,3/Linux-swap
i have made sure in the recovery image that i format the SD card to 3 partition first and then once that is done i copy the HERO rom i want and renameit to update.zip and then i perform a WIPE DATA and then APPLY UPDATE.ZIP
and i have tried ROMS with COMPCACHE (the Evil Hero ROM) and then i also tried the one with SWAP
which ones should i be using? what is the difference between compcache and swap anyways?

NO! Do they even exist for the 32B Magic?
I've tried the original Fatal1ty Hero rom, the Qteknology and the evil one (both this week). For me, they are not responsive enough to use on a day to day basis. If I have to wait more than 5 seconds for my phone to do something it quickly gets annoying, I always end up going back to CyanogenMod ...

ya im on 32B.. and had no problem with installs .. just dog slow.
and i have 32MB of swap on a class 6 card.

st0kes said:
NO! Do they even exist for the 32B Magic?
I've tried the original Fatal1ty Hero rom, the Qteknology and the evil one (both this week). For me, they are not responsive enough to use on a day to day basis. If I have to wait more than 5 seconds for my phone to do something it quickly gets annoying, I always end up going back to CyanogenMod ...
Click to expand...
Click to collapse
i also go back to cyanogen

only thing i can suggest to possibly speed some things up on a class 6 sd card is to swich your swap size to 40mb... that seems to be the sweet spot for me, although its still unusable... i'm currently testing hero roms without apps2sd (or trying to at least)... from my experience any ROM runs faster on the mytouch with apps2sd disabled...

bump
to
the
top

Actuaully an update i am using this Hero ROm
(V1.3b) Qteknology HTC HERO PORT from WWE [1.76.405.6] 32b
in this thread http://forum.xda-developers.com/showthread.php?t=540745
and it was slow at first but after everything cached it seems to be doing fine.
its not too terribly slow and i also increased the Processor speed to Max 527 to help as well and i noticed a difference.
i can actually use it now and i dont really get many HTC Black screens except when i attempt to edit the weather widget.
Only draw back is the blue tooth doesnt pair with my cars bluetooth hands free system in my BMW

"Only draw back is the blue tooth doesnt pair with my cars bluetooth hands free system in my BMW"
I'm jealous. Wish I had a Beamer.
I too am running Qtek's ROM and it's incredibly fast for me. It seems that each Hero ROM has a slightly different reaction to each phone. My Mom's Mytouch could not run the Hero ROM from QTek cuz the screen went pixelized. I however, had no problems. Strange.

I've been running Fatal1ty's Hero rom and is fast enough for daily useage
setup:
bypassed his swap setting (always deny upon flash) and ran the new swapper app
I do have a swap partition to work with the new version swapper app
delete stock, mail, peep, footprints (and a few more I can't remember)
did the priority mods found here
I'm still trying to figure out why wifi-tether won't start up on Evil's Hero rom.
Both my myTouch'es have had no luck with Qtek (pixelation).
And ported version of Drizzy's still gets pixelated.

ROM problems on MT 1.2...Very slow.

Hey, everyone, just want to say that thanks to this site, and all the hard-working devs, I've learned alot about my phone, how to root, how to flash ROM's, what to flash, etc.
But I've hit one VERY annoying snag...
Every single ROM i have flashed (save for the stock Fender ROM) has been EXTREMELY slow. For example:
First ROM i ever flashed, was CM 5.0.8-DS...worked GREAT...for a few days, then it started lagging horribly. My setup has always been as follows: SetCPU @ 576MHz max, 245MHz min, "on demand" setting, Compcache enabled, NO swap (although i DO have a SWAP partition), graphics setting are quite low (no window animations, no "fancy" input animations, etc.), and i have 12 widgets spread across 3 home screens.
ATM, i have CM 6-RC1 with the exact same setup, but its STILL acting horribly slow, "acore" has been crashing, ADW has been crashing, (seperately, i might add, i thought CM replace acore with ADW?), there is menu lag, typing with stock android keyboard is slow, stuff like that.
Has anyone experienced such atrocities (lol)?
Info:
HBOOT-1.33.0013
CPLD-13
Radio-2.22.23.02
MoBo- 32A (U.S. Black MyTouch with 3.5mm jack)
Thanks.
EDIT: Crap! I posted in the wrong forum, didn't i D:? Sorry everyone!

I noticed the same thing. I did find a little bit of in the cm wiki about swap/compcache/etc, and found that compcache was slowing things down over time. I run without it, and tbe problem sent away. I can't post the link right now...

Yeah, i just read that page, but now I'm running the MyTouch Slide ROM (CR_Slide) and after awhile, the same thing happens, it slows down tremendously, to where the screen just goes black (but the bottom keys are still lit up) and i have to pull the battery out, but it turns back on fine.

Moving to General.

jdyates said:
Hey, everyone, just want to say that thanks to this site, and all the hard-working devs, I've learned alot about my phone, how to root, how to flash ROM's, what to flash, etc.
But I've hit one VERY annoying snag...
Every single ROM i have flashed (save for the stock Fender ROM) has been EXTREMELY slow. For example:
First ROM i ever flashed, was CM 5.0.8-DS...worked GREAT...for a few days, then it started lagging horribly. My setup has always been as follows: SetCPU @ 576MHz max, 245MHz min, "on demand" setting, Compcache enabled, NO swap (although i DO have a SWAP partition), graphics setting are quite low (no window animations, no "fancy" input animations, etc.), and i have 12 widgets spread across 3 home screens.
ATM, i have CM 6-RC1 with the exact same setup, but its STILL acting horribly slow, "acore" has been crashing, ADW has been crashing, (seperately, i might add, i thought CM replace acore with ADW?), there is menu lag, typing with stock android keyboard is slow, stuff like that.
Has anyone experienced such atrocities (lol)?
Info:
HBOOT-1.33.0013
CPLD-13
Radio-2.22.23.02
MoBo- 32A (U.S. Black MyTouch with 3.5mm jack)
Thanks.
EDIT: Crap! I posted in the wrong forum, didn't i D:? Sorry everyone!
Click to expand...
Click to collapse
If you want to run CM5 or CM6 do NOT use swap. Not sure about not running Compcache. I don't run either and I've had my phone running for up to 4 days without a hiccup before. Everything is installed to internal memory and I still have about 130mb free with about 100 apps installed. Seven screens all filled with over a dozen widgets. If anyone's phone should be running like crap, it would be mine. You're definitely doing something wrong.

I've got the myTouch 1.2 and have been running Cyanogen 5.0.8-DS for a few days now with no problems. Did you do a system wipe when you installed the ROM?

Sorry, guys, havn't checked this thread in awhile.
@Binary100100: Thanks for the move , and at the moment I'm running CM6-RC2-08092010-NIGHTLY, W/O ComCache or SWAP, WITH a 512mb ext3, and i hit the same problem. It ran great for half a day, then went to complete sh*t. Have any idea what i could be "doing wrong"?
@DonJuan692006: Yes, i ALWAYS full wipe
EDIT: 8/10 12:20am:
OK, think i found my problem: Did a clean install of CM 5.0.8, and realized that when i added the SetCPU widget to my 3rd home screen, the phone slowed down, so i removed the widget (not the app, just the widget) and my damn phone is running SO much better! It's been running great for hours now with very snappy app drawer opening, apps open fast, and my home screens don't freeze! Gonna test this theory for the next few days, but i seriously believe i found the solution!

[Q] HD2 with Android randomly freezes in standby

I've tried 3 different roms and while in standby my phone freezes. The screen goes black and won't come back on, and eventually the buttons won't even light up. Is this a known issue or could I be doing something wrong? I am running all stock windows mobile.
Thanks in advanced.

should post this in the Android thread.
However, I'll give you my $0.02. I've noticed there is a lag in my build as well. Sometimes it won't seem to wake up. Often I just need to wait a bit and it wakes. I've read that two things can be causing this: 1) autorotate in android (you can turn off in settings, but I kinda like it) and wrong ROM. Peruse the 'droid threads for good ones, everyone likes Miri's.

This happens to me too. I've tried a few of the recent builds and when I put it on standby and wait 5 minutes I get a black screen and nothing but backlight.
EDIT: Reformated storage card and so far so good. Give this a shot

Been months since i last was on xda, is there a ****tional android rom now? SWEET! Where do I finde it, wasnt able to find anything by searchin on the forum.

Had same problem. And got solved after reflash my radio to 2.11.50.26_** and ROM to ChuckyROM GTX + CHT 1.8.5. Also formatted SDCard(so i also used a fresh android build).
So i would also suggest formatting your SDCard to FAT32

I formatted the SD and the problem remain. I noticed that (in my case) if i start android from WM Explorer, i dont have the problem. If i start android from Android Windows Boot, the phone freeze in standby. Give it a try, dont have to modify anything. Good luck!

Impressions on running CM 6.0/5.0 on 32B Magic

Hello,
I've had a couple of problems:
1. Low memory on 32B makes it really hard to use with multiple apps, apps struggle to keep resident in memory. There is no 10 MB RAM hack for CM 6.0 or 5.0 AFAIK. Option for keeping the Home Screen resident in RAM helps, but still it will reload slowly occasionally when the device is under memory pressure.
2. Reception is flaky, the signal bar goes to 0 (usually after I bring it from standby), and call audio is being interrupted in this case. This problem is already mentioned here http://forum.cyanogenmod.com/topic/4179-reception-problems-with-cm6-rc1/ and upgrading the radio to the latest available for 32B doesn't help according to this guy.
I'll be trying CM 4.2.15.1 now and see if that improves the situation in any way.

The jury is still out for me. I was very happy with CM 5.08...performance was smooth and I rarely had force closes.
Since upgrading to CM6, performance is about the same or perhaps a bit worse...definitely not better. In addition, I'm getting lots of force closes...primarily with the new 3D gallery, but also some with Voice Search and even occasionally the HTC keyboard.
I have dither, JIT and compcache all turned off. I've tried different heap settings. I've also experimented with different memory settings using Minfreemanager. I can't seem to shake the force closes.
I've purchased a class 6 sd card and will try swapping next. If that doesn't help, I'll probably go back to 5.08.
Overall, I think the CM 6 build is solid and beautiful. Unfortunately, I think Froyo is a bit beyond the hardware capabilities of the MT3G 32B. I've read of some users who are very happy with it, but that's not been my experience thus far.

My experience is that 5.0.8 runs better on the 32b mytouch also. CM6 gave me the same issues, all related to not enough memory. I couldnt get get swype to install at all due to not enough memory.

I also do not find CM6.0 to run very well on my 32B. I've tried all the permutations of JIT, swap, setCPU, dither, etc... It keeps force closing a lot, the keyboard is flaky and unresponsive, and it just isn't as smooth as most other ROMs I tried.
It's too bad but I'm switching to another ROM altogether.

Just to update, I decided to purchase a class 6 sd card and try a swap file. I wiped, reinstalled CM6, then used swapper 2 to setup a 32mb swap file. So far, performance matches that of CM5.08. I've not had a single force close and performance is normal...or atleast as normal as is possible with the 32B.
I still believe Froyo is pushing the limits of the MT3G 32b, but so far so good with swap.

[TUT] Install Android On Your HD2

Background:
The devs have had some major breakthroughs in getting Android ported over to our HD2s lately. Just a bit ago, they finally got Bluetooth working and I decided it was time to give it a shot. I was pleasantly surprised at the stability of the version I ran and have actually been using it as my primary ROM for five days as of this writing.
My biggest problem was in wading through the myriad of techno-speak and complaints piled on top of vague references to a non-existent thread over on the Leo forums. However, once I got things figured out, I was good to go and haven't looked back!
Please see post 2 for some tips and tricks and "Don't do's" that I learned along the way.
You absolutely MUST HAVE data access to install Android. If you have WiFi, that might work, but if you may be able to talk a friend with a data account to lend you their SIM card for a few minutes
For the curious, I did initially install Android on my 16gb C2 microSD card that came with the phone. See post 2 for why I am no longer doing so
Read "Steps" for the fast and easy version, "Details" if you're a bit nervous or want to see how neurotic I can be with explanations.
And so, without further ado, here is the simple method for locating, download, installing and running Android on your HD2!
Steps:
I recommend finding a nice, stable ROM and flashing it fresh after a Task29 before moving forward. Be sure to hard reset (or use Clear Memory under Settings) and then soft reset your phone to ensure the ROM is stabilized.
If you are using a stock radio you may have issues, the radio I am using is: 2.10.50.26.
Once your phone is up and running, go to Settings Tab->Sound & Display: Single Volume On (100%), Pocket Mode On, then click Backlight: Ensure "Automatically adjust backlight" is NOT checked, adjust your screen brightness to optimal levels, then un-check the other four boxes.
Exit Settings and make a call using the Speaker Phone, then turn the Speaker Volume to 100%.
Visit GameSquare by clicking this link and scroll to the bottom of that page, look for the "Download" link at the bottom. Save the file (currently it is named "HD2Froyo_V2.1.7z") to your computer.
At this point, it would be a brilliant idea to backup the contents of your microSD card and reformat it.
Once your microSD card is ready, place the file you downloaded from GameSquare on the root of the card ("root" means don't put it in any folders you might have on the card) and extract the contents.
If you removed the card to reformat or unzip the file, put it back in the phone. It is a good idea to go ahead and soft reset the phone at this point, just in case some of the hardware has developed some issues while you were working.
Open File Explorer and navigate to Storage Card->Android, then click on CLRCAD.exe (it won't respond, but then it's not supposed to, click it anyway), then click haret.exe. Always run CLRCAD.exe before haret.exe to ensure you can actually hear phone calls
You phone should now show the HTC Penguin and a ton of text. The phone may hang a few times, but it's fine, just let it run.
Once Android has booted, follow the customization prompts. It may seem to take forever to boot, but let it go.
Once Android has completely booted and you can see the Home Screen, wait for the icon on the top left (sd card scan) to disappear and then soft reset and reboot Android. If you have run Android or used Google Backup in the past, wait for the sync icon to disappear before soft resetting the phone.
You should now be able to fully load Android and make calls, texts, data connections etc. Enjoy!
Details:
Myself, I chose to ignore the google location, facebook - twitter - youtube logins and weather; this is because I never intend to actually use the Windows Mobile ROM anyway
You may or may not have luck with a different radio, but I know people running stock are complaining and looking for replacements. I will not explain where to find or how to flash radios in this thread, use the search button above to find one that will.
My screen brightness is set to 50%, which is optimal for me. Un-checking the boxes will prevent your phone from darkening the screen while Android is running!
This seemed to help when I had issues with a very quiet speaker and ringtones running Android.
I will not link directly to the build because (1) it's not my site or work and (2) there are important messages on that page that DarkStone1337 wanted everyone to read. For your edification, the original thread: [BUILD] [18.08.2010] [darkstone HD2Froyo V2.1] [kernel: darkstone 2.6.32.9 #36]
I haven't used a stock ROM in forever, but all of the customs I have run had a "Format SD Card" app in the Start->Tools folder. If you use your PC to format it, be sure to use Fat with a 32 cluster (or allocation) size. Formatting your card will help to eliminate issues that some have been having (I had the same issues and reformatted later). I found that formatting the card via Windows allows for a less-buggy system.
This will create a new directory named Android and a small text file. You can read the "readme.txt" file if you want, but don't move anything around. Unlike the original builds, HaRET is located in the Android folder and should stay there.
If I get a call, text or email on my phone before I get Android booted, I go ahead and soft-reset again. It may be a pain in the butt, but it helps to narrow down any issues you might have to just the Android build.
Android may reboot your phone before you see any prompts, and if so just go back and run CLRCAD.exe and then haret.exe as before.
If you have any issues, reformat the card and start over. Here is where you need that initial data (internet) access. Android does not require you to always have internet, but if you reset or re-install it, you will always need it at this point.
You can turn off the phone by holding the "End Call" button (that's the red one ) and choosing "Power Off" from the popup menu.
Of course, you don't have to enjoy Android, that's just a suggestion
This tutorial is subject to updates and bug fixes in the future, but no promises
Be sure to read Post 2 for lessons I learned along the way!

Tips and Tricks
Format and Content of this post may change, depending on how I feel and what I learn along the way (respectively).
SD Card Care:
I would recommend you to always reformat your microSD card before installing or re-installing Android on it. This is the same as doing a Task 29 on your phone before installing a new ROM.
I don't know much about Android, but I've been using Linux on my personal computers at home for over 10 years. Android seems to continually read and write data to the SD card while the system is running. If it is in "write" mode and you change something on the card or reset the phone, it can damage your SD card. So far, I have managed to get through this by reformatting my card, but you can easily wipe the card by removing the battery or hitting the reset button instead of using "Power Off" via the Android menu.
Never attach your phone to the PC and activate "Turn on USB storage". When I say, "Never", I really mean, "If you ever, ever do this, your children will despise you." Writing to the card while Android is in "write" mode will cause data that is being written by Android to be misplaced and this is a very bad thing.
Do not use the "transfer to sd card" option that some of the apps may offer. For the same reason as the last tip, it will really screw your card up.
Android was not meant to run on external card like your microSD card. Some geniuses here on xda have managed to trick it into doing so, but it will never be safe. Some day the devs may actually manage to hack into the phone's NAND memory and then we can have real Android ROMs running without an SD card, but until then we have to use this system. You do risk ruining your card, but I feel that it is worth the risk
Stability:
Just after running HaRET, hit the back arrow key. This will cause your buttons to light up momentarily. I'm not sure exactly why, but this seems to help the battery drain issue a lot.
The current crop of Froyo (Android 2.2) builds all seem to cause issues with our phone's hardware. Specifically, the screen is often unresponsive, sometimes never waking up after being turned off and necessitating a hard reset or battery pull.
Bluetooth works, but you may have to cycle the service by hitting "Bluetooth" in a call twice, once to turn it off and then again to turn it back on. I have had to do this several times, particularly after a hard reset.
I find that a task killer is particularly helpful. I found a free one called "Advanced Task Killer Free" in the market and it works just fine for my needs. When I need to turn off the screen, I run the killer and wait a few seconds before hitting the End Call button. Using this method, I have reduced the non-responsive screen issues somewhat.
Another trick I have learned is to turn off the lock screen. Even the simple slider seemed to cause issues, so I found "No Lock", a free app in the market that, when activated, will turn off the lock screen. If you keep your phone in your pocket (bad idea, you're gonna scratch or break it!), this is not a solution you will be able to tolerate after a few butt-dials.
Some people over on the Leo forums report that turning off the Live Wallpaper helped with the non-responsive screen issues. I haven't really tried this because I really, really like the wallpaper interaction. Of course, since my issues haven't totally gone away, I gave that a shot, but it didn't seem to help.
I switched ROMs, trying to find a WinMo ROM that was lighter but still up-to-date and every call I made with the phone thereafter caused the "robot voice" (some call it the "android voice"). I am now flashing a new ROM that I found on the T-Mobile USA HTC HD2 ROM Development forum that said "Android" in the title. The chef claims it is "Android Safe" and so I've flashed it, but left the Android installation alone. The "robot voice" is definitely gone, so that's awesome. Not sure what else may have improved, but at least I can make phone calls
I've noticed a trend over on the Leo forums to shy away from "Best WinMo ROM for Hosting Android". Not sure why this is, but I will carry that trend on until I am better informed. That being said, I have flashed three different ROMs to my phone and only one has actually produced a stabilizing effect on my Android. You can find it in the T-Mobile USD HTC HD2 ROM Development forum, just search for "Android"
Apps:
Having trouble getting your apps to install? Try going into Settings - SD Card and "Unmount" your card and then try the install again. This worked for me when installing Angry Birds and Pocket Legends (two very awesome games).
"No Lock": This app disables the default sliding-lock screen. I had some issues early on with the screen locking up as I tried to turn it on. This has helped tremendously.
"Advanced Task Killer": Although cnet says this is rarely needed, they are not running Android from the SD card as we are You will need some sort of task killer because your phone can't handle the RAM drain every day activity brings.
"SlideIT Keyboard": Replacement for Swype. I've used Swype for so long that I consider this app a poor replacement, though you might disagree. It's better than nothing!
More to come!

Snarksneeze said:
Coming Soon!
This is just a placeholder while I get the real deal written. Please be patient, I have a 2yo to care for and my keyboard time is hard to justify these days.
Click to expand...
Click to collapse
Snarksneeze said:
Reserved.
Will put some lessons I learned in here later.
Click to expand...
Click to collapse
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?

Paten said:
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?
Click to expand...
Click to collapse
Sorry, I accidentally submitted my first post instead of previewing it. Had to work fast before I looked like a complete idiot. Guess I wasn't fast enough, eh?

Thank you for this post, Ive been wanting to do this for a while but the other threads were very confusing to me...

sound dll of 2.13.xxx.xx problem
hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.
is there any solution??

Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?

אםזגםנש said:
hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.
is there any solution??
Click to expand...
Click to collapse
I actually had a custom ROM installed on my HD2 that caused the "robot voice". This ROM: {ROM}13Sep Omega WM6.5.x24634 Base3.04 manila2018#XT+Dinik+GTX+MaxSense+Black#Android is the only one I've been able to get a decent run of Android on.
We really, really need more than one option when it comes to ROMs that give Android good support, so if anyone else knows of one, this is a good thread to link it to.

szfjcr said:
Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?
Click to expand...
Click to collapse
I tried two different stocks: The one my phone came with way back in June and the new one at tmobile.com/wm_update. I was able to make calls, but the other person couldn't hear me.
I would recommend the ROM I linked to in the post just before this one; it's working great for me so far!

gonna try it thanks

for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance

dementievafan said:
for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance
Click to expand...
Click to collapse
You might want to check this out: http://forum.xda-developers.com/showthread.php?t=723200

hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?
thanks again

I'm one of the lucky ones!
So far at least... I have been running Darkstone Froyo/Sense for approximately six hours with zero issues beyond it taking a bit to get used to Android again, which is not a complaint at all.
As I stated, I used Darkstone Froyo with Sense, latest release.
2.11 Radio
I did not have to revert my rom because I was able to use HSPL3 Successfully.
I have read several threads/posts but this was the most helpful, although I could not have completed this task without some other [TUT] threads.
Side note: I stated I have not had any issues, I wanted to mention that I had read some posts stating the 2.11 Radio had caused heat issues. With heavy downloading of apps, chatting, texting, and browsing constantly for the last six hours (as I was a passenger on a long drive right after I completed the install) I never noticed the phone getting hot, and I made a point to watch for this.
Again, thank you.

dementievafan said:
hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?
thanks again
Click to expand...
Click to collapse
Apologies to everyone for not responding to this thread while on vacation in Arkansas.
In order to install Android on the HD2 as a regular ROM we would need access to the NAND processor, which we do not have at this time. We may never be able to get Android to flash that way. In the meantime, we can run it via Linux by using HaRET (Hardware Reverse-Engineering Tool). As far as I can tell, this is the API version of Froyo, the one that can be run via an emulator and downloaded from Google. So it's not really the phone version of Android, but from a user's standpoint, there is no difference.

electshrimp said:
So far at least... I have been running Darkstone Froyo/Sense for approximately six hours with zero issues beyond it taking a bit to get used to Android again, which is not a complaint at all.
As I stated, I used Darkstone Froyo with Sense, latest release.
2.11 Radio
I did not have to revert my rom because I was able to use HSPL3 Successfully.
I have read several threads/posts but this was the most helpful, although I could not have completed this task without some other [TUT] threads.
Side note: I stated I have not had any issues, I wanted to mention that I had read some posts stating the 2.11 Radio had caused heat issues. With heavy downloading of apps, chatting, texting, and browsing constantly for the last six hours (as I was a passenger on a long drive right after I completed the install) I never noticed the phone getting hot, and I made a point to watch for this.
Again, thank you.
Click to expand...
Click to collapse
Thanks for your feedback
You mentioned that you could not have completed the install without other tutorials. Would you mind linking to them or telling me what I am missing?
To write this, I reformatted my SD card and installed a fresh ROM, then detailed each step I made along the way. I have looked back but can't see anything that I might have missed.
I see that you are running Froyo Sense. I linked to the regular Froyo, since it was the version that ran without any issues for me. Would this TUT be better if I were to link to the other builds as well?

Thanks for this [TUT]! I have this installed with Omega v13 and Radio 2.12.50.02_02. Works beautifully.
I also added Dual Boot option with Jmz Android Dual-Boot.cab as suggested by you in an earlier post. Very sweet.

wackywalt said:
Thanks for this [TUT]! I have this installed with Omega v13 and Radio 2.12.50.02_02. Works beautifully.
I also added Dual Boot option with Jmz Android Dual-Boot.cab as suggested by you in an earlier post. Very sweet.
Click to expand...
Click to collapse
Glad things worked out for you!
Keep us informed of any issues, tips or tricks you stumble upon as you enjoy your new Android

i have a few questions
im new to HD2, i want to run android on tmous unlocked hd2, i have stock rom no hspl, my spl version is 2.10.8 or something like that ... so how can i do it. Help appriciated

rukhi said:
i have a few questions
im new to HD2, i want to run android on tmous unlocked hd2, i have stock rom no hspl, my spl version is 2.10.8 or something like that ... so how can i do it. Help appriciated
Click to expand...
Click to collapse
Stock simply doesn't work for Android. You can boot up, but can't make calls or hear external sound.
In order to get Android running, you will have to (1)Flash HSPL and (2)Flash an Android-friendly ROM.
I am far from being an expert on Android or Windows Mobile, so there may be something that I don't know about. If you are dead set on keeping stock, you might contact one of the Android-friendly chefs and ask them what changes they made to their versions.
Don't forget: Flashing your T-Mobile HD2 is dangerous. Never flash a ROM unless you found it here: T-Mobile USA HD2 ROM Development.
The original (Leo) HD2 is incompatible with the T-Mobile version and it is easy to get confused. Some websites aren't even bothering to mention the incompatibility and lot of folks are bricking their phones as a result.