New here, dont think this has been brought up. Has anyone else had the problem where music played in android sounds like its been sped up? It has a high pitch and the song seems to be a couple seconds shorter than it should. Any ideas?
The same thing happens to me. Weither it is from my sd card or through pandora.
same thing here. it sounds like alvin and the chipmunks!
I'm not entirely sure but I think this is because of the same reason which makes the clock go faster than it should be.
This is because android is set to turbo mode, so that it runs faster and smoother for you guys, but i'm sure the devs will have something sorted out soon so that its at normal speed.
sorry if i'm wrong, but i think that's what the problem is
Raary101 said:
I'm not entirely sure but I think this is because of the same reason which makes the clock go faster than it should be.
This is because android is set to turbo mode, so that it runs faster and smoother for you guys, but i'm sure the devs will have something sorted out soon so that its at normal speed.
sorry if i'm wrong, but i think that's what the problem is
Click to expand...
Click to collapse
WHEN this is the problem than guys who have this should read the right posts. You have to try the different Zimages,or in best way the latest. There are no problems anymore with pichtin tracks or turbo mode.
no problems with dan's v1 2.2 froyo build with music. I've always started up android manually via explorer instead of using one of those dual-boot solutions... maybe that'll help you guys?
aussiebum said:
no problems with dan's v1 2.2 froyo build with music. I've always started up android manually via explorer instead of using one of those dual-boot solutions... maybe that'll help you guys?
Click to expand...
Click to collapse
Which ROM and Radio are you using?
I am running the newest version of wm6.5 and radio version 2.10.50.26. im just too nervous to brick my phone by putting a new rom on it, should that help?
This is related to the robot noise in calls issue.
It is fixed by using a tmous 2.10 base winmo rom.
Search could have told you this....
GavTheStoner said:
This is related to the robot noise in calls issue.
It is fixed by using a tmous 2.10 base winmo rom.
Search could have told you this....
Click to expand...
Click to collapse
I had this issue (Chipmunk-esque music playback and robo-voice). Flashing to my current rom fixed both problems.
My radio version is 2.10.50.26 on the stock tmo rom (2.13.531.1) and still get the sped up music and robot voice also running the latest zimage from cotulla.
same here, zimage seem not to solve the problem its also not the turbo mode cuz mi clock is working correct but the tracks still sound to fast. Would really like a fix flashed about 5 roms now but nothing seems to work.
I also appear to get this problem, could this be due to a change in hardware in recent models (i got a replacement HD2 in June).
dragonhuntur said:
My radio version is 2.10.50.26 on the stock tmo rom (2.13.531.1) and still get the sped up music and robot voice also running the latest zimage from cotulla.
Click to expand...
Click to collapse
same here. i just stopped listening to music while on android. the songs sound 10x better on winmo right now.
OK, an update seems i managed to fix it by flashing Dutty's latest test ROM
Related
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
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
hey guys. ok ive searched and searched and gone through thread after thread to try and find a working android build for an AUSTRALIAN TELSTRA HD2.
im still using the phone on the telstra network and have yet to find a rom/radio/android combination that works.
so far most ones ive tried have the problems where i cant answer half of my calls since the screen was so moody or other ones the battery would drain in just a few hours.
i keep hearing that mdj's latest desire hd build is fantastic so if anyone has a good combination of a rom + radio + android build that would work for my hd2 then i will love you forever!!!
Hi,
I have a t9193 as well but first thing I did was flash a custom rom.
I am using Dutty's v9 on the windows mobile side and Mdeejay's 4.3 desire hd on the android side. It works fine but it needs a little time to get going. Also, you will need to set your apn info manually in Android so take note of it in windows. I am using the latest radio 2.15.50.14 without problems. T9193 is able to support most roms out there contrary to the t-mobile version.
Miri's v25 on htcpedia.com also works great.
Good luck.
darrengladysz said:
Hi,
I have a t9193 as well but first thing I did was flash a custom rom.
I am using Dutty's v9 on the windows mobile side and Mdeejay's 4.3 desire hd on the android side. It works fine but it needs a little time to get going. Also, you will need to set your apn info manually in Android so take note of it in windows. I am using the latest radio 2.15.50.14 without problems. T9193 is able to support most roms out there contrary to the t-mobile version.
Miri's v25 on htcpedia.com also works great.
Good luck.
Click to expand...
Click to collapse
alright ive put on that combination exactly and it still has a problem where sometimes it DOESNT come back from the black screen when locked. is there any fix for this as its been my main android problem since the beginning T-T
You need to change the radio rom to something that ends in .50. Telstra radio roms seem to end in .51. I use 2.15.50.14 and it seems to work ok.
I'm using MDJ_FroYo_HD_v._4.3_MDJ_S7.5HD with my wm being Cheetah Rom 3.14 base. I've been running this for a few days now and its pretty stable.
Good luck with your Android, gingerbread (Android 2.3), will probably be available soon too, waiting for that...
Cheers....
ultramag69 said:
You need to change the radio rom to something that ends in .50. Telstra radio roms seem to end in .51. I use 2.15.50.14 and it seems to work ok.
I'm using MDJ_FroYo_HD_v._4.3_MDJ_S7.5HD with my wm being Cheetah Rom 3.14 base. I've been running this for a few days now and its pretty stable.
Good luck with your Android, gingerbread (Android 2.3), will probably be available soon too, waiting for that...
Cheers....
Click to expand...
Click to collapse
yeh im using a .50. type radio and STILL having problems its like my phone doesnt want to do android at all and its really starting to frustrate me. almost to the point of wanting another phone. do i need to be doing anything else or doing a few more restarts???
karasu666 said:
alright ive put on that combination exactly and it still has a problem where sometimes it DOESNT come back from the black screen when locked. is there any fix for this as its been my main android problem since the beginning T-T
Click to expand...
Click to collapse
Hi,
I had this issue initially on 1st and 2nd boot or so. Don't forget that Android is run from sd card. You have to give 1-2 seconds to get going and load up the info from the sd.
When this happens, hit the end call button until the keypads light up and wait a few seconds. Make sure your keypad is lit up as it sometimes closes again. You can hit the call button and middle button as well.
Also, make sure that you uncheck auto intensity for display in windows mobile and I set the display time out to 10 minutes in Android.
Here is a trick and use and it seems to work. I let android sit for about 15-30 minutes on first boot to allow it to be stabilized and allow all the syncs to take place (the hd rom actually will download and re-install all marketplace apps - have a look in marketplace under downloads to see this). I then restart it a few times after that and even let it sit a bit to finalize everything. Don't ask me why but this helps a lot. Android seems to get faster each time. You also may want to postpone sync with exchange/outlook and also htc sense until your 4-5 boot.
Lastly, when you first start an application (each time you boot up) there is a slight lag so exercise some patience. After that it is very fast.
Hope this helps. If you want a faster build that is non desire hd based you can try mdeejay evo sense revolution build. It is not as fancy as the hd build but is lightning fast.
karasu666 said:
hey guys. ok ive searched and searched and gone through thread after thread to try and find a working android build for an AUSTRALIAN TELSTRA HD2.
im still using the phone on the telstra network and have yet to find a rom/radio/android combination that works.
so far most ones ive tried have the problems where i cant answer half of my calls since the screen was so moody or other ones the battery would drain in just a few hours.
i keep hearing that mdj's latest desire hd build is fantastic so if anyone has a good combination of a rom + radio + android build that would work for my hd2 then i will love you forever!!!
Click to expand...
Click to collapse
I also happen 2 own an Australian HD2 off Telstra and use both Telstra and Vodafone sims. Check my sig for the Win Rom/ Android combination. It works well for me, I've tried most of Mdj's Android roms as well but have found Sergio's Core Droid to be the most stable. Any of NRGZ28's Windows Roms will work well with Android, give it a go. I also downgraded my radio from 2.15 to 2.12 and that seems 2 work better for me. Hope that helps
My Telstra HD2 is running Android perfectly.
However, I want to watch Foxtel on it but says it doesn't recognise my HD2 as a Telstra device.
It is a T9193 from Telstra, but there must be a setting somewhere that's not right.
Any help would be awesome.
Cheers,
Dev
Hello,
My friends complain about my call quality. They tell me that my voice repetitively gets extremely silent, so inaudible they often ask back so I need to repeat myself multiple times which is weird and aggravating at some point.
I have an EU HD2 with radio 2.15.50.14 and Rafdroid HD 4.0.2 NAND + data2sd. I had this problem back while I was still using wm65 Energy ROMs or my own custom built wm65 ROM, so I'm 99% sure it's unrelated to the operating system.
BTW I'm on T-Mobile Hungary. Gonna try my phone with Vodafone too, just to narrow things down.
Oh, and no, I'm NOT covering the microphone with my hand. I always hold my phone in my right hand when calling.
Anyone else had a problem like this?
Thanks,
Jay
Bumpity bump?
If you had the issue with the Energy ROM and your current ROM plus you have the most current radio version installed it my just be a issue of bad service in your area. You could try down grading your radio starting with the radio under the one you have and systematicly work your way down from there with the radio versions to see if you can find one that works better in your area. Go to the HTC HD2 Master Radio Thread to get the radios.
T-Macgnolia said:
If you had the issue with the Energy ROM and your current ROM plus you have the most current radio version installed it my just be a issue of bad service in your area. You could try down grading your radio starting with the radio under the one you have and systematicly work your way down from there with the radio versions to see if you can find one that works better in your area. Go to the HTC HD2 Master Radio Thread to get the radios.
Click to expand...
Click to collapse
Thanks for the tip! Will try that.
I have exactly the same issue on my HD2.
Radio 2.07.50.27_2
Energy ROM: Energy.Leo.29007.Sense2.5.Cookie.2.0.Dec.27
I think for me this is a hardware problem, but it occurs very randomly and usually sound is ok again after some seconds.
JayMore, did you find a solution?
I have had this problem for quite a while also on older Energy ROM (same radio), but I never called very much. Now it is getting worse or I make too much long calls and I'm ready to RMA.
Try using a different microSD card, since I've switched, nobody mentioned this problem. Sounds stupid enough to actually do the trick...
Help!!!
My HTC HD2 is giving me problems....everytime I receive a call the caller gets a echo of his/her voice.....is there anything I can do to fix that????
Same problem here.
Usually when people phone me. If I phone back it seems OK.
Gonna try and rollback to an earlier radio to see if that works.
hi all
i have been using nand android builds since day one , and in most of the builds i am having this same issue
sometimes when i receive a phone call the system just hangsout and then gives me a force close msg for the phone application !!
either way , if i force close or not , no further phone calls can be answered and the phone will freeze for about 30 seconds with every call
also when this happens the volume buttons wont modify the volume for the media anymore and the phone wont give any sounds
so is there something i can do to get rid of this ?
i tried android builds based on 2.3.3 and 2.3.4 , miui , sense , no sense , and i have this issue with all of them
again , it happens like 10% of the times
hope i get an answer to this
I want to ask what exactly rom are you using (does it use newest tytung r10 kernel?) and tell you that I have not been experiencing these issues with NexusHD2 2.8 rom (2.3.4).
fpu
i tried typhoon , rafdroid , ndt miui , and plenty more and i think typhoon and ndt miui has the latest kernel
have you ever tried receiving a phone call while the camera application is running
this seems to trigger the issue many times , not always tho
if you have the call recorder running turn it off. it was causing me lot's of problems.
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
domenukk said:
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
Click to expand...
Click to collapse
+1 Same ****...
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
I just recieved a phonecall without problems.
Flashed the .12 radio from http://forum.xda-developers.com/showthread.php?t=611787&highlight=radio
however... My rom feels a bit slower now.
I am playing with it now.
Maybe clearing Dalvik cache will help. Or the issue comes back... Will see.
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Synthezys said:
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Click to expand...
Click to collapse
Switching Radio to something.12 did the trick for me.
No problems for two days now.
domenukk said:
Switching Radio to something.12 did the trick for me.
No problems for two days now.
Click to expand...
Click to collapse
Leo_RADIO_2.12.50.02_2 - is this good?
Synthezys said:
Leo_RADIO_2.12.50.02_2 - is this good?
Click to expand...
Click to collapse
Yes that's it. Works fine for me
Mea culpa just today I had the same issue, for first time.
It's nothing major and reboot made it work fine again, but breaks my belief in HD2 as perfect, native-like Android device.
[email protected] said:
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
Click to expand...
Click to collapse
Beside changing of radio, THIS seems to be interesting.
I'm on MAG but considering switching to cLK (for many reasons - fastboot support being one, second that I don't need 99% of MAGLDR features).
Let's see how it all pans out ;-)
fpu
It just happened again! On the new rom... :/
There is a thread, however, stating that it's due to skype.
This can very well be true.
http://forum.xda-developers.com/showthread.php?t=1164058
but I need skype to stay on contact with my girlfriend... why can't android support skype natively instead of sipthings? -.-
Well still... anyone tried clk (instead of magldr) and skype?
Disable "Audible touch tones". It's under Sound in Settings, it did the trick for me.
I thought this was against robot voice?
well what ever. let's give it a try. Thx
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
An0n1mUs said:
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
Click to expand...
Click to collapse
For me recieving a call does nothing but a very bad noise. hd2 nearly freezes after that. I cannot hang up most of the times. If I somehow manage to, phone app forcecloses and connection cannot be reestablished until I pull out the battery...
Good old Robotvoice. I wish that was my problem.
i have switched to cLK about 3 days ago and till now i have got no problems at all