Related
at&t 8525 owner, here.
So, I've had this issue for a little while now after I flashed Shadow TE ROM. But it's continued since then... so here's the issue:
I go into work and turn the phone onto vibrate. After I leave work, I switch back to sound on (ring & vibrate). Even though the icon shows the sound is back on, it's not. It only vibrates. It acts as if the speaker is still asleep.
So for awhile I'd have to reset my phone every day to get it working again until I realized I can go into sound settings / notifications and I find that the phone's jumped back to the default ringtone and more than that, I have to literally push PLAY to test the sound in order for the speaker to "wake up" if you will. Then the phone's fine until the next day.
Ok so back to present:
I got fed up and thought it was Shadow TE. So I flashed CRC's v9.2 ROM. Still had the same speaker issue! I was advised to flash a shipped rom.... which I did.... and flashed CRC's v11. Issue still remains.
I've searched the board and could only find one other person make mention of this a couple years ago and no one ever addressed it. Does anyone have any suggestions? I'd appreciate it greatly.
Same problem here with a custom Titan ROM. Installed the same software as every other ROM that I've used so the problem must be in the ROM somewhere.
nonegiven said:
Same problem here with a custom Titan ROM. Installed the same software as every other ROM that I've used so the problem must be in the ROM somewhere.
Click to expand...
Click to collapse
Could be... but why does no one else seem to have this issue? Wouldn't there be tons of people replying here?
I did find that instead of switching it to vibe when I arrive at work, I switch it to silent... and SOMETIMES when I go back to Sound it works ok for a few hours but then it goes back to silent without warning so I miss calls and texts a lot. Might as well force the sound back on through Notifications Menu anyway. I'm SO getting away from Windows Mobile ASAP.
As soon as the Blackberry Bold is released here in the US, I'm buying it.... unless something about it disappoints me, in which case I'll settle for the iPhone 3G. The Bold can't come soon enough.
Who would like to claim this Hermes when I'm through with it? What are you willing to pay?
Try making sure that your ringers are in the windows\rings folder. Saw it somewhere else and it seems to be working.
nonegiven said:
Try making sure that your ringers are in the windows\rings folder. Saw it somewhere else and it seems to be working.
Click to expand...
Click to collapse
Hmm... I tried putting them in, like, 4 places... but none of them seemed to be that location. I'm doing it now and I'll test tomorrow. Thanks for the tip.... i hope it works.
cozbaldwin said:
Hmm... I tried putting them in, like, 4 places... but none of them seemed to be that location. I'm doing it now and I'll test tomorrow. Thanks for the tip.... i hope it works.
Click to expand...
Click to collapse
Sorry to report that this didn't help.
C'mon AT&T... release the Bold.... let's get this thing released already...
cozbaldwin said:
Sorry to report that this didn't help.
C'mon AT&T... release the Bold.... let's get this thing released already...
Click to expand...
Click to collapse
Don't know what to tell you then. Make sure you're not running any 3rd party software.
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
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 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
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705
Thanks, I will try that out tonight and report!
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.
Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!
Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...
need help also
Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?
xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time