Can't hear - Verizon Samsung Galaxy S III

Ok so this is the problem. I was on CleanRom 7 when I first noticed this. For the first few weeks every thing worked fine then suddenly when I received a Skype call my btooth kicked me out and had to switch to speaker, first I thought it was a Skype bug. A week later I switched to Bonestock ROM again everything was fine for 3-4 weeks then the phone rebooted itself and I lost btooth again when on a Skype call, but now I also lost voice or I should say can't hear when I'm making a regular call unless I switch to speaker or on btooth. Ppl can hear me fine just no sound on my end unless I switch to speaker or btooth. I tried switching back to CR 7 but problem persists. Anyways if someone could give some thought about it it would be greatly appreciated.
When ever I switch ROM's I always do a clean install wipe data, cache and dalvic two or three times.
Thanks for any help you could provide.
Sent from my SCH-I535 using xda app-developers app

Related

[Q] Anyone else having this problem?

I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.

[Q] can't hear other side in conversation.

hey,
I bought the nexus s (9023) about two months ago, stock rom, not rooted, and for the last week or two, it started making problems.
about 1-5 times a day, i can't here the other side at all. as if it's on mute. not even the ringing tone, before I'm answered. the only thing that solves it, is to restart the phone.
in other forums i've read that it's a mess, and that i should use my warranty. the problem is i bought the phone abroad, and shipping it should take about 3 weeks.
is it a common issue?
can i solve it alone, mabye by switching to a non-stock rom?
i'll be very happy to read some good news here, but bad news is better than non.
thanks a lot,
tal
p.s, iv'e downloaded system info to monitor the temp, and it doesn't happen necessarily when the phone is hot.
I don't know... I am rooted, I have used 5 different roms since purchasing my phone.
Stock
CM 7
Savaged Zen
Oxygen
Soju
I have also used several kernels
CM Stock
Netarchy
Matrix
James Bond
Trinity
So far, on all roms and kernels I have experienced the same problem. You make a call and it connects, looking at the screen the time counter is going but there is no sound; it will sit there and hold the call for 30-55 seconds then ends call. A quick redial and bam it works. Some people have reported that they answered and there was nothing. I don't know, it's really obnoxious.
The other, more annoying problem is that randomly on calls throughout the day the phone will just reboot itself. Right in the middle of a call. AHHHH like 3-5 times daily!
help, anyone?
i'm stuck with this, and a bit clueless.
Well, somehow I discovered that the problem is related to the bluetooth. as long as it's turned of, nothing will happen, on the other hand, when I use my earphone (most of my conversations happen while driving) i need to restart my phone every 1-2 calls
any ideas?
just u can't hear other one while calling u?
thanks.
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
tal89 said:
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
Click to expand...
Click to collapse
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
it's quite obvious, unfortunately it doesn't work.
cutiyar said:
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i can't hear, and he can't hear as well.
tal89 said:
i can't hear, and he can't hear as well.
Click to expand...
Click to collapse
hehee its problem ,
am really disappointing with nexus s , but i dont have enough money to buy HTC product again.
any solution?
Hi, did anybody have any solution to this problem?
I live this problem on almost half calls of specific numbers.
I am desparate...
Try setting discoverable timeout to never? Have you tried a different Bluetooth device?
Sent from my Nexus S 4G using xda premium
I have this problem too. This seem to happen on some Kangs and nightly, but not all of them. I can't hear when someone calls me. But when I call someone, I can hear them. I always have Bluetooth off (do not use them).
I live the same problem. No problem for outgoing calls. For incoming calls, I cannot hear caller's voice but they can hear me. It is not for all numbers.
I am on t-mobile and nexus s (cynagenmod nightlies). For all incoming calls from tmobile numbers no problem. But for almost all other carriers, it is just random.
I feel like I started having this problem after updating from CM 7.0.2 to 7.1 RC and thereafter(but not very sure on this).
If anybody still following this topic, I would suggest you to contact samsung if you still have warranty. On the second attempt they sent me a brand new phone with box and accessories.
Sent from my SGH-T989 using XDA
Or, you might give it a try with a different radio for your model:
http://forum.xda-developers.com/showthread.php?t=1116884
If you go this road, make sure you backup your EFS folder.
What i would do is if it is still in warranty just give it back to them and they'll probably give you a new phone. Since you said it takes 3 weeks to ship, just wait for it and use another phone if possible. Its not like your life is going to end. I think the problem is, not every phone is the same so there will be problems especielly when flashing a rom. For example unstable roms might not allow you to use this app or have serious effects on your phone.
Best to give it back to samsung and get a replacement.

[Q]NO Call Audio

Hi!
Let's get straight to the point.
I just got a Skyrocket (Canadian Version) last week on Craigslist and I am having a blast with it-- wonderful phone. There is only one problem, though... my in-call audio would not work. When I put a call on speakers, I can hear the other side, but when I am using the actual call speakers located at the top of the front screen, I cannot hear anything. If I reboot the phone, it will work for about say 4 times... and then it will be borked again. Also, I noticed one time that when the background of the other phone is loud, that is when the problem would arise.
Should I go back to complete stock and see if that fixes it? Or is it a hardware issue?
Do a complete odin wipe back to stock, and use it for a couple days. If that doesnt work i suspect the seller knew of the issue, and sold u a borked phone.
I've experienced the exact issue as well. I upgraded a few weeks ago and on day 3 of having the phone, bam, in mid call the default call audio speaker went out. I was on Sky-ICS at the time. I flashed different radios despite knowing that couldn't have been it, went all the way back to stock and nothing worked.
I concluded that it was a hardware issue, or a software issue that was beyond anything a flash, battery pull, or tweak could fix. For whatever reason, the call audio muted the default speaker, yet rerouted to the loud speaker with no problem. So I took it back to the store, explained it to the sales rep and got a new Skyrocket.
Sent from my SGH-I727 using xda premium
I guess this is just the main problem with getting things second hand.
Sent from my SGH-I727R using xda premium
Also check your noise suppression settings in the dialer app....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Telstra HOXL only works on speakerphone

Hi all,
Apologies if this has been posted but I could not find any using the search although I came close.
I bought a 2nd hand Telstra HOXL using an Optus sim on fleabay and it is basically brand new. I've had it for almost a week and everything has been working fine except that I dont actually use it for calls that often. So last night I get a call and the person on the other end couldn't hear me so I figured they were in a bad reception area. Similar thing happened today and it felt strange so I called myself and all i could hear was a loud buzzing sound every time I spoke into the mic. When i turn on speaker phone, it actually works properly. Obviously it's a bit pointless if I can make a call without being on speakerphone. The strange thing is, I definitely had a successful call when i first got the phone but it required a few attempts before we could hear each other and I was told by the caller that all they could hear was the buzzing noise. Why it would suddenly work after a few attempts and then never again is beyond me.
Things I've tried:
- Performing the Audio Test. It failed because I could not record anything. I confirmed this by trying the voice recorder and it didn't work - just buzzing.
- I tried factory reset without success
- Finally I jumped onto the online support and they told me there is only 1 mic so it sounds like a software problem.
Has anyone experienced the same thing? I can't exactly take it for repairs cos the Ebayer has gone MIA even though they promised to provide proof of purchase. Hopefully they aren't dodgy cos they even refunded the postage difference. So now i'm stuck with a potential lemon and a few hundred bucks poorer.
Thanks.
I probably can't help you, but I suggest making more tests and post here, hopefully somebody had a similar problem and can help:
- try over headphones
- try over Bluetooth headsetor in car handsfree
- try a call over Skype or yahoo messenger (on wifi) to make sure isn't the network
Post results here. You'll probably end up with a custom rom, but not sure.
Sent from my HTC One X using xda app-developers app
Thanks. It's definitely not the network because I put my sim back into my old trusty Desire and it works fine. I'll give the headphones / bluetooth a crack later and I have a feeling they will work.
UPDATE - Tried it with headphones on and it works. I read on another forum that some people believed it had something to do with removing the headphones from the jack which caused the propblem. I happen to use my headphones a fair bit and I'm thinking maybe it's "confused" itself somehow. Some people have tried clearing the cache but I'm not sure how to do that on the XL.
slimslim said:
I probably can't help you, but I suggest making more tests and post here, hopefully somebody had a similar problem and can help:
- try over headphones
- try over Bluetooth headsetor in car handsfree
- try a call over Skype or yahoo messenger (on wifi) to make sure isn't the network
Post results here. You'll probably end up with a custom rom, but not sure.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

[Q] HELP! - No Call Audio on Incoming Calls

Has anyone else had this happen or heard of it happening?
Out of the blue today all incoming calls have no audio. I cannot hear the other end and they cannot hear me. If I call out it works fine.
I am running a stock rooted NCB ROM and have been for a few weeks with no issues. I have already tried rebooting, restoring a backup, and I tried installing the R.O.T.D. ROM but this issue persists.
Any ideas?
My wifes s5 had the same issue. I could hear her but she could not hear me. She also lost speakerphone. She had to take it back and get it replaced. Luckily it was within 3 days of purchasing it so it was no hassle.
Sent from my SM-G900P using Tapatalk
I was afraid of that because after all I did root it so my understanding is that the warranty is void...
Just to clarify... when I make an outgoing call everything works fine. The problem only happens on incoming calls. I would think this is a software issue since the hardware clearly works.
Tou can try a factory reset. Thats what they made her do at the sprint store before they would replace it. I think her issue was slightly different but the same. Does your speaker phone work? Try a data reset and see if that fixes it. If not odin it back to stock and hope they dont look at it too hard. Be quick, I think you only have a few days before you have too use the warranty.
Sent from my SM-G900P using Tapatalk

Categories

Resources