Database Users

Phone won't properly switch from vibrate to sound

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.

Loosing all sound?

Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S

sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.

sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.

Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S

just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5

+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.

me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does

+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.

yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap

Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.

Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!

Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse

DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it

When will the Audio Problem be fixed completely

I want to know when will the sound problem be fixed completely? im currently using fresh 1.5 because all of the 2.1 have problems with the sound.. when someone calls i cant hear them and they cant hear me! i cant be resetting my phone everytime this happens. the fix that they have dont work also it might prevent it from happening so often but all my calls are important... does any one know when this will be fixed fully or why is this happening? how to prevent it ? mayb its the cdma settings? Thanks alot

The audio problem for the effected phones will be fixed when official 2.1 comes out.

i found whats causing it.... so who has a nice rom with the older kernel before .29 .. wats the kernel ? lol
The issue is caused by audio drivers in the kernel not resetting. we do not have the source for .29 kernel so there is no fix. we dont know why this effects some people and not others. Since the audio drivers do not reset it does not allow anything to read them. so it continues resetting and resetting and this causes the cpu to be pegged by the constant retry and retry.

Any 1.5 or overclocked 2.1 Rom

The audiofix posted by avalaunch worked briliantly for me. I have not had the issue once since he posted his fix about two weeks ago.
Also just so you know, zens my touch Rom did not have the audio issues for me. Just be sure to reboot after the first boot to completely get everything working.

which fix the audiofx or audiorc?? or u on the newest one for testers? i hate the my touch roms omg lol whats the older kernel version

wait another thing could it be because we didnt update the radio ?? or u guys doubt that 1?

I have had the audio issue with every ROM i had used until i flashed the Dachdroid 2. Ever since i have not had any kind of issues with phone freezing or caller not hearing me when i answer. Its very strange, but i wanted to post to see if any of the Devs can find out the differences between whats in this ROM and all the othersthat would make it work. Again i have had audio issues with all except this one.

What is this Audio problem?
I've run ROMs with both the .29 and hacked up .27 kernels.
Is this a bluetooth audio problem? Or handset audio?

The problem occurs randomly, for me at least. It's an issue I've had as others have that no audio at all comes through after an unknown time. I notice mine is triggered when I get off the phone with someone, I get 'call lost' and then all my audio is gone and have to reboot to get audio back. It affects BT and handset for me.

Iv never had the problem and iv changed my radio quite a few times. I think im on my 4th radio.
Maybe later at night you could flash a 2.1 rom, change to a newer radio and give it a few test to see if it works.
Flipz has alot of radios and I think the stock one on his site.
(IF anyone trys flashing a radio this is really the only way you can brick your phone. DO not flash any radio unless it says CDMA htc hero. All of them are on flipzmode website. You cant go wrong if you get them from him.)

the issue will hopefully be fixed when they release 2.1 officially. and im still looking into the issue a little at a time. 99% of people reported that one of the two updates put together fix it.
the only other cause could be a hawrdware issue. like the moved one resistor on the board and this causes something in the kernel to restart drivers. idk that is a very very very simple thought. but anyways like i said hopefully it get fixed!

Dont know if this is related but its absolutely killing me
Just today the headset icon popped on and wont go away. I cant hear anything when using the phone because its stuck in this mode. I plug in headphones and the voice dialer starts. I can hear through the headphones, but taking them out does nothing.
Anyone have any info on this or if there is anything I can do?

yea thats y im on fresh 1.5 i hate the 2.1 simply because of the audio problem coming from the headset !!! andn darch droid2? does everything work correctly like camera ect ... i hope its not that dam mytouch theme that 1 sucks ill try tonight

killacammiami said:
yea thats y im on fresh 1.5 i hate the 2.1 simply because of the audio problem coming from the headset !!! andn darch droid2? does everything work correctly like camera ect ... i hope its not that dam mytouch theme that 1 sucks ill try tonight
Click to expand...
Click to collapse
yeah...Ive come to the conclusion that 2.1 is just not going to work for me...went back to fresh 1.1 and everything is good. Its funny though, Ive been on 2.1 since all of the work was done and never had a problem until now. Ive been on damn near every 2.1 rom and didnt have an issue. Now all of the sudden the handset icon shows up and I cant hear anything unless I put in headphones. Tried all of the audio fixes and searched the entire net looking for a resolution. Hopefully the official comes soon. I am definitely going to miss 2.1.

No1Lives said:
Just today the headset icon popped on and wont go away. I cant hear anything when using the phone because its stuck in this mode. I plug in headphones and the voice dialer starts. I can hear through the headphones, but taking them out does nothing.
Click to expand...
Click to collapse
That's more than likely a mechanical problem. Take it in to Sprint.

posguy99 said:
That's more than likely a mechanical problem. Take it in to Sprint.
Click to expand...
Click to collapse
I would think so too, but I went back to fresh 1.1 and its fine...

I'd go back, but then I'm stuck with not being able to receive picture messages. So far I get the audio problem every other day, and it's a simple reboot.

DexSade said:
I'd go back, but then I'm stuck with not being able to receive picture messages. So far I get the audio problem every other day, and it's a simple reboot.
Click to expand...
Click to collapse
a simple reboot ? a simple headache lol idk about u guys i dont want to have to restart my phone when i just got a call that i couldnt answer !! ..... is there any newer roms with the older kernel?? because i dont understand the whole kernel thing...

This audio loss issue is reason number one why all of the people who say "Who cares when HTC and Sprint release 2.1? We already have it!" are just total idiots.

Answering a Call

Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)

yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.

Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.

Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).

Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.

What carrier are you on?

this happens to me too.its so annoying. im on att

Can't find the thread but it was pretty long.

nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.

This sounds like an att problem not a nrsux one problem

I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.

I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One

Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.

I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.

I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?

khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.

Sounds more like a network issue than a hardware issue, IMO

This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.

[BUG] Other person can't her me mid-call, mic gets muted

Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.

Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300

Have you tried to DISable the noise canceling feature?

No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app

I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?

BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app

just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?

Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).

the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?

Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.

Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:

the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course

change modem

Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?

avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas

I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...

I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.

I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app

Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium

I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.