Database Users

Getting androiod to work on different roms!

I have done a lot of testing receintly and have found a few things that may help people who are having issues getting android to work, eg not booting or robot voice. This is what I have come up with so far.
Getting android working properly seems to depend on two things. Both windows rom and radio.
I have found the following in testing.
Having the wrong radio will stop haret from booting. I installed the standard htc hd2 o2 stock rom which is ver 1.72. I then tried to boot using the default radio which was 2.7.51.22
When I booted android it got to the stage just before linux loads and hung at that point.
I then simply installed the radio 2.12 and it booted perfectly also there was no robot voice and worked very well.
I also tried a couple of tmous roms and it did not seem to be compatable. It would boot up and run ok but I got robot voice. I built a standard rom using standard hd2 stock rom 1.66 and cured the robot issue.
I then built a tmous rom to get the 576mb hack with the same settings as the 1.66 using the same radio and got the robot voice again.
If anybody knows how to fix this that would be great. I know there are 576mb enabled roms out there that are android compatable I would be interested to know how they work. Eg thinking of energy roms!
Hope this helps when you are trying to get android working. I am currently using 1.4 which is awsme and the work that has been carried out so far in such a short amount of time is staggering. Keep up the good work folkes!!!

I don't personally see how the Windows Rom would effect anything with the Android side of things. I used a stock T-Mobile US rom until a few days ago and nothing has changed since I flashed a different WinMo rom. The only logical thing that COULD effect Android performance is the radio.

Breakthecycle2 said:
I don't personally see how the Windows Rom would effect anything with the Android side of things. I used a stock T-Mobile US rom until a few days ago and nothing has changed since I flashed a different WinMo rom. The only logical thing that COULD effect Android performance is the radio.
Click to expand...
Click to collapse
I was wondering about this as well. I have got Robot Voice from day one on every single build. I updated my Radio from 2.10 to 2.12 and still RbV. (I do get better battery life now though - go figure)
Anyway. I'm really confused as to what the ROM would have to do with it. As far as I know, the ROM is just some software windows uses to get everything non-radio working on your phone. Sense Haret completely shuts down Windows when it launches Android, how can the ROM have anything to do with it?
Someone please explain this!
I have seen pretty much every combination on both sides say it works, and then others that say it doesn't.
Something is amiss, and I wish I knew what it was.

YEah. I would like some more info on this as well.

I am just reporting what I heave lernt over the last couple of weeks, some not all tmous roms do seem to cause robot voice. As I said I built both a tomus rom and and 1.66 release rom with exactly the same settings and radio yet I got robot voice when using tmous and didn't when I used the 1.66 rom!
It is a very odd issue
Both were built using the same windows os 2189

phone call = unresponsive phone

okay so i've used the phiremod skinnyEVO1.5 and Mdeejay eVo Sense Stock and i've had the same problem with both. Whenever i make a phonecall/receive a phonecall, as soon as the person and i end the call my phone goes completely unresponsive. the screen goes completely black, and none of the hardware keys light up
the only thing ive found that can get the phone to come back 'to life' so the speak is to call the phone again and end the call on my phone with the end button.this doesnt always work though.
im running the Chunkydroidrom in WM and have radio 2_12_50_02
i even updated the kernel on the Mdeejay build and it still happens
is there anything that can be done to fix this?
please help me guys

different build, but same issue, nexus one by ummmmmmmmm matc forget which version. radio 2.15, wm chunky gtx sense with that CHT 2.0 i think..................

so far our windows mobile rom is the same cook, could be where to start im about to change my winmo rom

i just changed my windows mobile rom to ozdroid and im still having the same problem, and when i use the included bootloader i get robotic/froggy sounds in phone calls. maybe its not running clrcad correctly so ill try it the old fashioned way and see what happens

please
bump
can someone pleasee help?

good luck in finding help. Ive had some of the same issues i believe. My phone will completely freeze during a call for now apparent reason. it'll working fine in the call in the just freeze during my call. I tried different winmo roms that are suggested for droid builds. i believe i tried every radio available for tmo and about every build of driod and the problem is still there. It may run fine for a day then it starts freezing. I've posted a question about this yesterday and 97 people have viewed it and one person suggested i return the phone. I don't believe that its a hardware issue, more like a software issue. I guess i better learn how to pull the logs and then i may get a reply. i just haven't found a place that it explains it well enough for me to do it myself. My persistence will prevail though, cause I'm addicted.

Well please if you ever figure it out please let me know as this can get quite annoying
Sent from my HTC HD2 using XDA App

Disable Auto-Rotate in the Settings>Display.
See if that helps.

I had the same problem. I have Advanced Task Killer installed and it was set to kill apps on screen off. I turned off the option to kill apps on screen off and so far it solved my phone call = unresponsive phone.

I have theese issues only if i have certain call recorder softwares installed .. try uninstalling them , and if nothing helps delete ur data.img and do a fresh start(u can back it up tho if it prooves unusefull)

@souljaboy
what exactly do you mean by certain call recorder softwares installed? such as which ones?
@JonSolo
i disabled auto rotate and i still experienced the problem during phonee calls
@mike91t
i changed my auto kill to every 4 hours, so i'll let you know what happens with that over the course of the week

Same problem here, I've turned off screen autorotate, and I don't have any task killers installed. Everything works fine, and even a call or two, then it stops working and audio during calls doesn't work, and phone app becomes unresponsive.

have you tried a different radio rom?! maye 2.14 will help.

fruchtfliege said:
have you tried a different radio rom?! maye 2.14 will help.
Click to expand...
Click to collapse
well i waws thinking about changing to 2.14 but the android build im using recommends certain roms for best performance so i was going to keep using the radio rom and see if anything improved, so far i dont really think its working, so i might change to 2.14 because people seem to be having the less problems with it

[Q] **Random** Robot Voice (Leo Superram and Radio 2.15.50.14)

Ok, I have a HD2 (T9193) flashed to a LEO ROM (RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship) with radio 2.15.50.14 running the Superram version of android.
It works perfectly (calls are good and everything works) for quite a while. It was up for 4 days no reboot. Then randomly I got a call, I could hear them they could hear me, and then it dropped. I call them back and I have robot voice.
I KNOW THE "FIX" is to put it on loudspeaker then end the call immediately. Well this freezes the phone process and android force closes it. The whole phone crawls to a hault, and no matter what I try I cannot get it out of this robo-voice mode.
When this happened before, it took a good 2 or 3 hours of rebooting the phone and finally calls were ok and no robo voice. And it lasted 4 days.
I have run CLRCAD.exe and haret.exe manually and also used the bootloader (which does it for you) and same result once in android. I can make and receive calls just fine in windows mobile after this happens.
I am not sure what to do.
My radio is what people are suggesting, and it works most of the time
My ROM is a suggested ROM
It works most of the time then randomly does not
Loudspeaker then ending the call does not fix it but instead freezes the phone.
I have not seen anyone else post with these issues, so it does appear that a new thread is needed. Any help is appreciated.

i remember that i had this issue too... unfortuantely my solution was to just flash another android build

So you had this issue with the Froyo Superram version, but you switched to something else and now it is working?
Or did you have this issue with some other build before?
What version do you use now, and what is your hardware?

[Solution] Robot voice issues - NAND Builds

I believe I have found a fix for robot voice issues. I was playing arround with several builds and could not get it fixed. It did not seem to matter what type of build, sense / non sense / kernel was used, but randomly I would get robot voice.
I know this has happened to a lot of people but I think I have found the root cause and a temporary fix.
The problem seems to be stemming from the dial pad sounds. I noticed that before I heard the tone from the keypad there would be a weird click sound. Then the robot voice would appear. If you then tried to dial again it seemd to crash the phone.
To fix the issue simply go into Settings -> Sound and disable Audible touch tones. I disabled Haptic feedback as well but do not think this has anything to do with the sound. (May differ slightly on how to disable on certain builds)
After I have done this I have done multiple reboots and have not had any futher issues with sound.
Sorry if this has been posted before but I just wanted to let you guys know what I have found out

Cool!
so simple...
It worked for me. I falshed sevral radio version and was about to flush the whole android adventure down the toilet.
thanks dude, you made my day.
HD2 - CyanogenMod 6.1 - 2.15.50.14

my rom was perfect but except it had that robot voice now it works....this made my day!

fixed my issue
2.3.3
HyperDroid-CM7-v1.0.1 "Boisterous Bearcat"

Thx fix my robot voice to =

helped me also great job.....
im running hyper v12 nand.... and i flashed it twice rooted flashed all kinds of radios.... i was wiggen out. robot voices, i thought i needed to up my medication..... lol....
well THANK YOU and ill tell everyone about your little fix...

i was scared that i almost had to go back to win mobile. blahhhhh thank the baby jesus""

T-Mobile USA
I upgraded my radio on my T-Mobile HD2 USA with with ver. 2.15.20.14 and it solved my robot voice problem. See if that works for others.
Upgrade just the radio, and nothing else, did the trick for me.

Saved the day!

[Q] Calls get interrupted by LOUD noise, then end. Please help!

Hello there,
I've done a lot of reading and searching but can't find anyone having the similar problem.
First my specs:
HTC HD2, unbranded
Currently stock 6.5 Win, tried ChuckyDroid before
NexusHD2-FRG83D_V1.8__Froyo_2.2.1 build
2.08.HSPL
Now the problem, it's like this:
When I'm in a call, sometimes the call gets interrupted by a LOUD scratching noise, after that it's silence and the call ends shortly afterward. I can dial the number again and the call will be fine in the first moments.
Now the odd thing is, that this sometimes happens straight away, sometimes after a few minutes, and sometimes not at all. And it even happens in the WinMobile custom ROMs!
I have tried to use all different kinds of radio versions, stock ROM, custom ROMs, etc. I am using the NexusHD2-FRG83D_V1.8__Froyo_2.2.1 Android build.
Would be glad about help, this problem is driving me crazy, especially when making important calls!
Cheers,
Flo

If you have it using all builds, all roms and even on different platforms like Android and WinMo, then it's clearly something hardware related.
I suggest you flash back to a stock ROM and put your HD2 up for a repair.
That, or your phone is haunted ofcource. That stuff happens.