Related
Looking to stick an android rom on my hd2, wondering if you guys can help me out looking for one. which is this smoothest running and has the least issues. whether its 2.1, froyo with or without sense. thanks yall
thatg said:
Looking to stick an android rom on my hd2, wondering if you guys can help me out looking for one. which is this smoothest running and has the least issues. whether its 2.1, froyo with or without sense. thanks yall
Click to expand...
Click to collapse
Any build that I have used from Darkstone has been smooth and fast. You can download the latest "clean" froyo build or the "sense" themed froyo build here:
http://gamesquare.co.uk/froyostone.htm
Imho, the clean froyo build is a bit faster.
i used the max energy co0kie energy ROM for win mo, used hardspl 3, the latest radio, and used the latest froyostone sense build, and the jmz dual boot .cab, everything is working pretty good... when i turn the phone on, i can boot co0kie energy win mo, or android 2.2. now im pretty happy with my device
pbleonidus said:
i used the max energy co0kie energy ROM for win mo, used hardspl 3, the latest radio, and used the latest froyostone sense build, and the jmz dual boot .cab, everything is working pretty good... when i turn the phone on, i can boot co0kie energy win mo, or android 2.2. now im pretty happy with my device
Click to expand...
Click to collapse
awesome. your voice calling and speakerphone are working? i almost have the same setup as you except i'm using chucky's rom. voicecalling works perfectly. no echoes no robotic voices. i may try energy rom some time this week although i like chucky's + gtx white theme.
ryan562 said:
awesome. your voice calling and speakerphone are working? i almost have the same setup as you except i'm using chucky's rom. voicecalling works perfectly. no echoes no robotic voices. i may try energy rom some time this week although i like chucky's + gtx white theme.
Click to expand...
Click to collapse
i havent been able to try any sort of calling on the android os yet, but everything works great on co0kie energy win mo os...
pbleonidus said:
i havent been able to try any sort of calling on the android os yet, but everything works great on co0kie energy win mo os...
Click to expand...
Click to collapse
cool, let me know if the voice calling works.
btw, here's a thread over on the android hd2 development section consisting of a growing a list of the fastest and most stable build+ rom combinations including a running list of what does/doesn't work on some builds
http://forum.xda-developers.com/showthread.php?t=749110
this should help the OP of this thread as well.
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
pbleonidus said:
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
Click to expand...
Click to collapse
i'm experiencing the same exact thing but the froyostone dev has stated that this is a known issue and it will be fixed upon the next build
would the next build the fix is in be the agust one, or the next one as of todays date? because yesterday the agust build came out, and i beleive that is the one i have installed, is there a way for me to check which release date i have?
Shubcraft cm6 v1.2 is very fast and stable and 98% off the things work on it...and i think the theme is pretty neat...
Sent from my HTC HD2 using XDA App
pbleonidus said:
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
Click to expand...
Click to collapse
I would suspect that whatever the CAB is you have installed probably changes a register (not registry) in the micro controller that controls the keypad and its lighting. As long as this microcontroller doesnt get a reset signal or power loss it is going to keep that register set even when booted into android.
As far as i know when using HARET WinMO is no longer running, but please correct me if im wrong, ive tried to find some detailed info on how HARET works, but haven't found much to date. I always wondered if android was truly running all on its own, or if HARET was something like a vmware translating android calls to winmo api calls with winmo still running the show under it all
Before you boot into Android make sure the bottom keys aren't lit. That's keep your keys from turning on at all in Android.
Sent from my HTC Desire using XDA App
d0ug said:
I would suspect that whatever the CAB is you have installed probably changes a register (not registry) in the micro controller that controls the keypad and its lighting. As long as this microcontroller doesnt get a reset signal or power loss it is going to keep that register set even when booted into android.
As far as i know when using HARET WinMO is no longer running, but please correct me if im wrong, ive tried to find some detailed info on how HARET works, but haven't found much to date. I always wondered if android was truly running all on its own, or if HARET was something like a vmware translating android calls to winmo api calls with winmo still running the show under it all
Click to expand...
Click to collapse
Yes, haret completely shuts down winmo and boots linux. There is nothing else running when you're using android.
Dual Boot
Can someone help me? I am trying to dual boot but it is not working. I read somewhere that you need to change HKLM/init launch 52 to Launch 62 but there is no Launch 52 on my phone.
Hey folks! I'm one of the many who regretting giving WM another chance... So I decided to try to get Froyo 2.2 running on my HD2. All works VERY well (I used Darkstone's ROM).
In all honesty I should have said MOST works well. Everything works wonderfully except for:
1. The phone application because:
If the call does go through, I get the infamous robot sound and;
2. Sounds:
I have none. No ringtones, no alert tones, nothing. Another known issue.
Here is my dilema...I read about workarounds for the issues above (mainly folks are saying to try different radios (like 2.10.50.26) and to use a proven ROM over WM like Miri's). The big problem is that Sense is locked up on my phone. It stays at the "Launching HTC Sense" forever. As it is it is tricky to get to the file explorer to launch these Android ROMs without the screen constantly turning off.
So there I am. I am stuck with a WM phone that doesn't launch Sense and is crippled and locks up as a result but got Android ROMs to work but with no sound or phone capabilities. Kinda blows, really.
Any help will be greatly appreciated.
If it helps, I have Cookies ROM running on the WM side of the phone. I cannot uninstall it since clicking on "Settings" in menu does absolutely nothing except for highlighting the icon.
P.S. I downloaded a radio that is supposed to help out my problem but don't know how to install that. Any help on this would be great as well.
P.S.S. I do run the CLRCAD.exe before running HARET.exe when trying these ROMS. But still no sound.
Thanks in advance folks!
Read this. To get you familiar with flashing things.
Have you tried a hard reset to deal with the Sense problem? With the phone off, hold the Volume up AND down buttons, press the power button for a second and release it. You will get a confirmation and instructions how to proceed.
Hi new to hd2 android. I have tried multiple roms and and droid builds ,but the problem I am having is after I format my sd card with the sd formatter that I was recommended I transfer the android build to it let it boot up. After that I reboot it and set everything up ,and 99% of the time I will set the phone down and when I go to pick it back up I hit the power/end button to turn on the screen and I get no screen I just get buttons lighting up. Is there anything that I am not doing or doing that is causing this. Please help. I am no stranger to electronics as I modify about everyone of them that I own ,but I can't crack this one. I've been working at it for over a week keep getting the same result. If anyone can help me I would greatly appreciate it. Thanks in advance
vdubbri said:
Hi new to hd2 android. I have tried multiple roms and and droid builds ,but the problem I am having is after I format my sd card with the sd formatter that I was recommended I transfer the android build to it let it boot up. After that I reboot it and set everything up ,and 99% of the time I will set the phone down and when I go to pick it back up I hit the power/end button to turn on the screen and I get no screen I just get buttons lighting up. Is there anything that I am not doing or doing that is causing this. Please help. I am no stranger to electronics as I modify about everyone of them that I own ,but I can't crack this one. I've been working at it for over a week keep getting the same result. If anyone can help me I would greatly appreciate it. Thanks in advance
Click to expand...
Click to collapse
It would help if you added your WinMo ROM/Radio and the Android build this is happening with?
Sorry I am running the elegancia gtx right now with the froyostone sense 3.1.7 and the 2.10.50 radio ,but it has done it with numorous builds
Me too
I have the same problem and i have tried several different builds and am running chuckyRom
I have tried the chucky rom and the ozdroid rom as well with almost every single android build that is half way decent. This sucks I would love this phone to be up and running good. Now I did have the combo of chucky rom with the same radio I have now with the hyperdroid 1.6 and it ran for a few days with no problems ,but the darn battery died quick. I haven't been able to get it to work properly since.
Hit the phone button it will wake up faster
Sent from my HTC HD2 using Tapatalk
The problem is its not turning the screen on at all. No matter what button I hit.
vdubbri said:
The problem is its not turning the screen on at all. No matter what button I hit.
Click to expand...
Click to collapse
U have advanced task killer installed?
Sent from my HTC HD2 using Tapatalk
I'm having the same issue, and yep, Advanced Task Killer is installed and running.
same here
i am having all those same problems and i have tried it with and without ATK
I do not have task killer installed not any version of any of the task killers. If a android build has it in it I go in and uninstall it.
Try changing your sd card. I saw some cards (such as team branded) exhibit that behaviour.
Same problem here tried changing the SD card and same thing happens.
Might have found a fix for this for now. All I did is turn auto rotatescreen in android display settings hope it works for you guys.
I have just started using the newest Energy rom with tmobile usa radio and I was getting the black screen of death. After a bunch of messing around I set it to the compact start menu and turned off sense in windows mobile home options and now the problem went away. YMMV
In the middle of reading all the posts here yestarday I glanced at motoman234's sig and I decided to try his setup and so far twelve hours later still no black screen of death. I don't know if it was my winmo rom that was causing it for me or the radio I was using ,but so far so good. The touch screen seems a little laggy which I wish wasn't there ,but again happy to have a setup that is stable.
Hello all. Im using Chuckdroid rom with the new radio 2.15 (although the problem still existed with 2.14) and Mdeejay Froyo revolution android.
I had this issue spring up unexpectedly. I had been using Mdeejay's previous version for a day or two with no issues. Then all of a sudden the audio stopped working. I tried updating the radio first to 2.15 from 2.14. Then I tried rebooting after initial launch because it was Froyo. Then I tried updating the Android version to the newer one Mdeejay had. Still nothing.
When it first boots there is sound if I press volume up. Then nothing.
Any thoughts? Is this because of Froyo? Am I missing something?
I jsut changed out the Android version again to: CMYLXGOs.Droid.RedTopia.v1.0.1. It is still not working. I have no idea where I messed up here. Im still searching! Anybody?
Bump. Still having issues guys.
First things first.... Do you have working sound in WM?
adamsweeting said:
First things first.... Do you have working sound in WM?
Click to expand...
Click to collapse
Yes, the sound is working in WM.
worldishis said:
Hello all. Im using Chuckdroid rom with the new radio 2.15 (although the problem still existed with 2.14) and Mdeejay Froyo revolution android.
I had this issue spring up unexpectedly. I had been using Mdeejay's previous version for a day or two with no issues. Then all of a sudden the audio stopped working. I tried updating the radio first to 2.15 from 2.14. Then I tried rebooting after initial launch because it was Froyo. Then I tried updating the Android version to the newer one Mdeejay had. Still nothing.
When it first boots there is sound if I press volume up. Then nothing.
Any thoughts? Is this because of Froyo? Am I missing something?
Click to expand...
Click to collapse
Same here, after boot Sound is working, leave it for sometime then NO Sound at all, even media players, youtube, phone calls, Sound Just stops working, cant even call or hear anyone when I use the dialer, as if there is something that Kills Sound.
Desire HD 3,7
Any Fix or workaround? How can I get the Sound to work again?
Willy318is said:
Same here, after boot Sound is working, leave it for sometime then NO Sound at all, even media players, youtube, phone calls, Sound Just stops working, cant even call or hear anyone when I use the dialer, as if there is something that Kills Sound.
Desire HD 3,7
Any Fix or workaround? How can I get the Sound to work again?
Click to expand...
Click to collapse
Im at a loss. Ive never had an issue I couldnt figure out until now. Next thing Im going to do when I get home is change the kernel. If that doesnt work then a different rom. If that doesnt work, I guess change the radio to 2.12 or before. Other than that I dont know what to do. Maybe format and start over.
I wish somebody would weigh in with this.
blah blah blah
Hi All
I saw that someone else had a similar problem, but did not get any definite answer - So Im asking too.
In the last few days I started playing with installing Android on my HD2.
(European HD2 with latest Official WM6.5 ROM).
My problem is as follows:
I boot to Android system (clscad then haret),
Android boots,
everything seems to work ok for the first few seconds.
After these few seconds, the sound stops working.
I tried several NativeSD and SD android versions.
All showed the same behavior.
If I boot to Android again, I get these few seconds of sound again.
Did anyone had this problem and knows how to resolve it ?
Many Thanks in advance.
Som30ne said:
Hi All
I saw that someone else had a similar problem, but did not get any definite answer - So Im asking too.
In the last few days I started playing with installing Android on my HD2.
(European HD2 with latest Official WM6.5 ROM).
My problem is as follows:
I boot to Android system (clscad then haret),
Android boots,
everything seems to work ok for the first few seconds.
After these few seconds, the sound stops working.
I tried several NativeSD and SD android versions.
All showed the same behavior.
If I boot to Android again, I get these few seconds of sound again.
Did anyone had this problem and knows how to resolve it ?
Many Thanks in advance.
Click to expand...
Click to collapse
Ah, clrcad and haret, so much memories.
I'm not giving you a definite answer, I'm just guessing. clrcad is what makes the phone have sound, try a different file (from a different source). I remember the very old versions of sd android have flawless sound, you might want to dig them up and try using their clrcad. Also, try turning on airplane mode on windows mobile before booting into android, see what happens.
Marvlesz said:
Ah, clrcad and haret, so much memories.
I'm not giving you a definite answer, I'm just guessing. clrcad is what makes the phone have sound, try a different file (from a different source). I remember the very old versions of sd android have flawless sound, you might want to dig them up and try using their clrcad. Also, try turning on airplane mode on windows mobile before booting into android, see what happens.
Click to expand...
Click to collapse
Thanks for the reply.
I tried your advice, sadly, it did not help.
Some more investigating revealed the following:
If before doing anything used the Volume up-down buttons, and as long as I had the volume slider on screen,
the device was audiable, and played the volume tone up and down.
The moment I let it disappear - I lost the audio completely.
If I did anything else I only had the first tap sound, and then silence.
So I think that only a single app can take over the sound device, and even that - only once.
Again - anyone have any idea how to resolve this ?
So - some findings -
Since pretty much everybody says it works perfectly for them,
I tried playing with this a little (I believe 3 hours is a little).
I tried isolating the cause for this phenomenon.
Tried removing/installing apps (on the WM),
Tried hard reset, and eventually I found that when I turn screen tap sound on in WM
(Setting->Menu->All Settings->Sound and Notifications->Check all check-boxes)
Android audio is stopped after a few moments/after the first Android App, accessed the sound device and closed it.
I would be thankful if someone can verify this finding.
(Set his/her device to sound screen taps sound,
Reboot the device with Screen Taps On,
run Android, and see if/when sound is lost)
If this is verified, perhaps some one who develops Android ROMs for HD2 could investigate.
(I like my screen tap sounds in WM,
It would sadden me to lose them)
Som30ne said:
Since pretty much everybody says it works perfectly for them,
I tried playing with this a little (I believe 3 hours is a little).
I tried isolating the cause for this phenomenon.
Tried removing/installing apps (on the WM),
Tried hard reset, and eventually I found that when I turn screen tap sound on in WM
(Setting->Menu->All Settings->Sound and Notifications->Check all check-boxes)
Android audio is stopped after a few moments/after the first Android App, accessed the sound device and closed it.
I would be thankful if someone can verify this finding.
(Set his/her device to sound screen taps sound,
Reboot the device with Screen Taps On,
run Android, and see if/when sound is lost)
If this is verified, perhaps some one who develops Android ROMs for HD2 could investigate.
(I like my screen tap sounds in WM,
It would sadden me to lose them)
Click to expand...
Click to collapse
So - Can anyone try this and say if this phenomenon happens to him/her as well ?