I only have a couple days left, to return this phone.
Im having two huge bugs.
1. When I call people sometimes the phone calls them but the speakers never turn on, I cant hear them and they cant hear me... I cant even hear it ring...
2. Sometimes the proximity sensor goes ape bananas during a phone call and turns the screen off and on even when the sensor is next to my head.
Im using a custom rom but, Ive had both of these problems on the shipped rom as well. Is anyone else having these problems? If not Im assuming I have faulty hardware and will be returning my phone.
edit: Im pretty sure Ive gotten to the bottom of both of these issuses.
1. not being able to hear caller. This is a problem with all dk28 based roms. If you wait until you see the call is connected and the counter has started for a few seconds it should happen alot less often. If the problem still does happen usually turning on speaker phone and then back off again will remedy the situation.
2. proximity sensor freaking out. The proximity sensor works fine if you put your hand in front of it. The problem I was having is on occasion a small lock of my hair would be in between the proximity sensor and my head, this caused the sensor to bug out and turn the screen off and on. So if this happens to you just make sure the sensor located just to the right of the ear piece is point towards skin w/o hair in between it.
Most of the people on this forum, prolly have short hair and thats why they havent noticed it.
Go get it replaced before your time is up. Say that you are having issues that aren't being resolved through reloading di18
It is most likely hardware issue.
Sent from my SPH-D700 using XDA App
What android version are you on?
had the phone for a week and notice this problems, so i think i was on di18, which is 2.1 update
and currently im on 2.2.1 froyo
if no one else is having these problems, Im going to call them in an hour.
That isn't a common issue with the epic. Exchange it, remember to flash back to di18
Sent from my SPH-D700 using XDA App
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
AndrewZorn said:
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
Click to expand...
Click to collapse
hmm I guess Ill hold off another day before I return it, see if anyone else can confirm or deny these are software issues....
thx for the feedback so far.
AndrewZorn said:
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
Click to expand...
Click to collapse
This doesn't happen for me...what hardware version are you guys?
Sent from my SPH-D700 using XDA App
I have the issue with the phone calls not being able to hear them, or them hearing me.. Running 2.2.1. Did not have this problem before the upgrade to DK28.
I have not noticed any problems with the proximity switch, although every once in awhile my screen will not turn off like it is supposed too.
mrhocuspocus said:
had the phone for a week and notice this problems, so i think i was on di18, which is 2.1 update
and currently im on 2.2.1 froyo
if no one else is having these problems, Im going to call them in an hour.
Click to expand...
Click to collapse
I don't know if I am too late "chiming in" in here, but I can confirm that the call issue did not happen to me on the stock, out of the box, rom. However, every dk28 rom I have flashed has given me that issue. It is a "bug" in the leaked dk28.
The proximity sensor seems to be a hardware/software issue. That has never happened to me (the way you described it) For that - you should take the phone back before your time is up!
As someone posted earlier - flash/odin back to stock before you take it back!!
Got the same thing happening, using DK28 nebula rom, it happens like every other call.
I have experienced the call issue once after switching to 2.2 DK28, only once, and I have been running it since leaked.
as for the proximity sensor, I've heard of issues, but only seem to have an issue myself if I'm holding the phone at a odd angle.
If you have any concern at all, take it back and make them give you a new one, assuming your still in your buyers remorse period there shouldn't be any issues.
It's already been mentioned, but I'll repeat it again, flash back to DI18 before returning.
FWIW, I love this phone, very few glitches, very stable even running leaked DK28. There is not a better phone available through sprint at the moment.
Also wanted to add that the ROM I am currently using is Epic Experience 2.0.07
I think I have solutions to both of my problems, I have updated the op to reflect these events, and hopefully help other people.
Glad to hear you figured it out, I guess I just haven't noticed the first issue all that much.
I wish more people would update their posts like you did.
Sent from my SPH-D700 using XDA App
Related
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
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
What is the fix for? I know on my phone sometimes I can't hear anything when making a call.
I run my own Rom and kernel on my phone so can you just supply the fixed files or tell what they are and I will pull from the zip
-------------------------------------
Sent via the XDA Tapatalk App
what audio loss?, I've tried every rom and havn't had this problem yet.. are you talking about the dreaded audio bug? I am famililar with that as im on a refurb now from that. pre root tho.
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
I had that problem big time with Ivan's Official but with JCase's Plain Jane I havent had the problem at all.
I have that issue with the cyanogen roms and ic3rom. But as far as I've noticed the zenEXP and damageR roms do not have this issue. At least for me anyway.
I'd really like to run cyanogenELB, but the loss of audio is a deal breaker.
Renocat said:
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
Click to expand...
Click to collapse
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
LiverpoolsNo9 said:
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
Click to expand...
Click to collapse
When i have had the issue before, going into to settings and resetting the rigntone worked. It would be set on default ringtone, not what I had assigned. I put it back to what i wanted and it would ring again. same thing with notifications
Can't Wait
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Using the rooted version of leak3 and also have the same problem with loss of audio. Reboot only way to resolve it.
-------------------------------------
Sent via the XDA Tapatalk App
Having the audio loss (go to make a call every once in a while and the phone is silent and I have to reboot) on Evil Eris 2.0.1. Also, the alarm sometimes does not go off.
Avalaunchmods said:
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
Click to expand...
Click to collapse
I know you say DO NOT CAUSE AUDIO LOSS, but it seems like a lot of people are letting you know about their audio loss.
Sorry, but I figure I will add to this since others are speaking about Evil Eris.
For me, I get the silent bug (meaning all audio stops working: email notification, text, volume, music, ringtone selector, alarm tone--<when SB happens and I am trying to select a ringtone or alarm tone I get a FC for HTC sound something another>>--)
I have had this with EE 2.0, 2.0.1, and 3.0. My wife however is still on 2.0.1 and has never had the silent bug issue.
Also, for me, I do not get the shutter sound in camera, meaning when you take a picture it makes that camera sound noise. This happens without the silent bug, just don't get sound.
On AF http://androidforums.com/htc-droid-eris/99973-found-what-causes-silence-lag.html this may or may not help you.
This seems to happen to me about every 24-26 hours.
And most importantly, THANK YOU for looking into this and trying to fix it!!!!!!!
edit: I wanted to clear up, I love Evil Eris! I mean no disrespect to this fantastic ROM or to Frame!!!
cabbie12 said:
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Click to expand...
Click to collapse
I'm have the same problem using Ivans official. Not sure but i think the problem starts when I'm using data and then receive a call. When I answer I hear nothing and when I try to call back I hear nothing. I just reboot to fix.
Just wanted to give an update.
I flashed Sushi last night http://forum.xda-developers.com/showthread.php?t=701544 and am still having the silent bug making me a strong believer that I have a hardware issue.
Somewhere I read someone is thinking it has to do with the proxy sensor. Today I had silence twice, that's 2 times in just a few hours, this has never happened before. Also, each time today happened within an hour of using the camera (and I still have no shutter sound with this ROM).
I failed to mention last night that I am on an old Radio 2.40.00.01.22
I am sorry if I sound like a post whore but I just want to give accurate observations.
Camera
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
cabbie12 said:
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
Click to expand...
Click to collapse
Yes, I am now thinking it has something to do with the camera. I just got the silent bug again, 3rd time today, this was after I used the camera this evening to test and see if the silent bug would happen. This time it took 90 minutes when before it seemed to happen within an hour.
I had identified the bug a while back, but no one took any interest.
http://forum.xda-developers.com/showthread.php?t=668693
I'm glad to see that more people are becoming aware of it. Hope someone finds a fix soon. The only ROM that I'm aware of that isn't having this issue is the original 1.5.
just asking
im not sure what this trouble everyone is having but im not having any problems besides mms needing the fix but other wize no other issues sound included
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
cabbie12 said:
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
Click to expand...
Click to collapse
im not sayin it aint happening just didnt know it was a wide spread thing thats all
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.
I rooted and installed the leaked "official" 4.0.4 on my phone last week but have noticed an issue with the proximity sensor. It works like it should when making a call and putting the phone to my ear it turns the screen off. The issue I'm having is when needing to hang up the screen will not turn back on until I hit the power button, and after using the dial pad in a call the screen will not turn back off when I put the phone back to my ear and I can hear buttons being pressed. Other than that I haven't had any other issues with 4.0.4 and like the ICS OS a lot.
i have the exact same problem with 4.0.4
pgjensen said:
i have the exact same problem with 4.0.4
Click to expand...
Click to collapse
Well at least we know someone else with the same issue. I've gone through all the setting menus and couldn't find any setting for the proximity sensor. Its not a huge issue but its annoying when trying to hang up. I doubt it but maybe this is an issue they are trying to fix before an official OTA is released which is causing some delay.
Known bug of sorts with the leaked OTA. VHGomez's 4.0.4 apparently doesn't have it.
jonnythan said:
Known bug of sorts with the leaked OTA. VHGomez's 4.0.4 apparently doesn't have it.
Click to expand...
Click to collapse
Ok. I did a search for 4.0.4 proximity sensor on here and it didn't come up with any threads. For some reason it seamed to work ok last night but it was plugged into the wall charging while I made the call. I don't know why that would make a difference but it worked like it should while charging.
That's because the thread about the 4.0.4 leaked ROM was deleted.
I moved to vhgomez from the leak and have been happy.
Make sure you guys aren't using a wired headset.
Sent using Tapatalk, you know, the free version.
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.