Related
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.
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
I searched the forum for this, and even google, but without any replies. So I thought I have better luck creating a new thread.
Basically I'm my question is about the conference call beeping sound (when calling more then one person at the same time). I read it's a privacy thing. But in my opinion it would be enough to beep only, maybe, the first 10 minutes?
So my question is, is it a phone thing or a carrier thing?
And if it's a phone thing, I'm stunned that no one had made a solution to disable it, cause it doesn't seam to be included in a phone.
Can anyone shed some light on this?
I think its a phone thing and you may put it in silent mode then no one will disturb you
hit thanks if I helped you
sent from the wonderfull s3 mini GT-I8190 using xda app
I think you misunderstood me.
The percipients that I called to the conference all is hearing the sound. Not me.
And it sounds every minute, to all of them, so it's not an incoming call or anything.
M facing same problem like you, found no solution yet.
I've been using the phone for almost 7 months now, the problem never occurred until a couple of days ago. In both incoming and outgoing calls, the other party can't hear me, not at all. I cut it and call them again, then it's okay. This problem, however, vanishes if I'm using a headphone or loudspeaker, but whenever I switch from the headphone/loudspeaker to hands-on, the problem immediately starts again. I've tried restarting the phone, doesn't help. Has anyone faced this issue? I heard in one place that a factory reset might be helpful, I'm not quite sure whether I should go for it. Can anyone tell me whether it's a software or a hardware level problem? Because this problem does not occur when I'm using Viber or Skype, it only occurs when I'm calling from my carrier number. Any help will be much appreciated.
I am having a similar if not the same problem. Phone is basically unusable. Going to try the low mic fix in this forum. Only other bit of info I'd add is I'm on AT&T.
Can you give me a link to that low mic fix?
Sent from my A0001 using XDA Free mobile app
javed24 said:
Can you give me a link to that low mic fix?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Haven't tried it yet, but here it is.
http://forum.xda-developers.com/oneplus-one/help/qa-low-mic-call-t3056078
OK, So I have flashed the low mic volume fix successfully, and though the problem was intermittent before, I have yet to see the issue persisting past the "fix".
I'll keep my fingers crossed and update if the problem shows up again.
I got my Pixel 3 unlocked from Google a couple of days ago. I really love the phone, but oddly, every time that I call my wife and I'm on speaker, it always takes 8-10 seconds for her to be able to hear me. This happens with no one else, as I've called multiple people on speaker. Google offered to RMA the device, but I'm not convinced that it's a hardware issue. If it's a software issue that will likely be fixed in the future, I will just keep this one. I'm not entirely sure what to make of it, but I don't really want to go through the RMA process just for it to continue happening. Has anyone else had similar experiences? From what I can see on Reddit and elsewhere, it appears to be a rather commonplace issue. I just can't justify waiting for another device to solve a wide spread problem. If it was a fluke issue, then a factory replacement wouldn't make me nervous. I think that I am just going to return the device for a full refund and wait for something else to come out. Sucks though, because I otherwise loved this phone.
I have noticed this as well. I try to talk over the speaker and the person on the other end can't hear me for a little bit. I might try to RMA the phone. How'd you go about talked to Google Support about the issue? A phone call, chat or email?
norman1080 said:
I have noticed this as well. I try to talk over the speaker and the person on the other end can't hear me for a little bit. I might try to RMA the phone. How'd you go about talked to Google Support about the issue? A phone call, chat or email?
Click to expand...
Click to collapse
I was using the chat service, it worked fine. I haven't RMA'd the device. I went and got a new SIM card from AT&T and it seems better. I did tons of test calls to other people on different carriers and it only ever happened with my wife, who is in Verizon. For that reason, I don't think there is a hardware issue with my device, but I don't know what it might be.
norman1080 said:
I have noticed this as well. I try to talk over the speaker and the person on the other end can't hear me for a little bit. I might try to RMA the phone. How'd you go about talked to Google Support about the issue? A phone call, chat or email?
Click to expand...
Click to collapse
I figured it out while I was messing with it yesterday. Turn off HD voice. "enhanced LTE" in the network settings menu and that fixes it. I am on AT&T and had great connectivity with same carrier subscribers, Sprint, and others. I tried calling multiple friends with Verizon and had the issue every time. So I just turned it off.
Update: it looks like December update fix my issue. Will update again if something happen
---------------------------------------------------------------------------
This speakerphone issue is happening to me using TMobile and also using Whatsapp calls.
I noticed this issue because the phone is also not connecting to my Honda Civic 2016 Bluetooth and tried using the speakers.
I'll wait for December 2018 update and make lot of test before I contact Google.
I'm using the regular Pixel 3 white.
I have the same issue,,,when I first get a call and answer it with speakerphone no one can hear me for a few seconds then if I toggle speaker off then back on it works okay??
stl-fan said:
I figured it out while I was messing with it yesterday. Turn off HD voice. "enhanced LTE" in the network settings menu and that fixes it. I am on AT&T and had great connectivity with same carrier subscribers, Sprint, and others. I tried calling multiple friends with Verizon and had the issue every time. So I just turned it off.
Click to expand...
Click to collapse
Doesn't this remove the ability to use group chats?
I got my wife the Pixel 3 at launch and we're on the 3rd phone because of this issue and it's still happening. It only happens on speakerphone (not regular) and her speakers seem to be fine which makes me think it's software and not hardware.
deblas66 said:
Doesn't this remove the ability to use group chats?
I got my wife the Pixel 3 at launch and we're on the 3rd phone because of this issue and it's still happening. It only happens on speakerphone (not regular) and her speakers seem to be fine which makes me think it's software and not hardware.
Click to expand...
Click to collapse
I agree with you. I think I'm still having issues with it even without it on. My wife is still saying it sounds like I'm in a tunnel any time I'm on speaker. I hope they get this resolved, and ASAP.
stl-fan said:
I agree with you. I think I'm still having issues with it even without it on. My wife is still saying it sounds like I'm in a tunnel any time I'm on speaker. I hope they get this resolved, and ASAP.
Click to expand...
Click to collapse
Me too. I did some serious searching and it is a more major problem than I thought.
https://productforums.google.com/forum/#!topic/phone-by-google/YCbNdF9b1ts;context-place=forum/phone-by-google
I am wondering if anyone has tried turning off the wifi calling option? I havent tried that yet as it is the only thing I havent tried to see if my phone doesnt have problems when first answering a call with the phones speakerphone and people on the other end not being able to hear me for the first few seconds? I saw in a Google thread that there may be a problem with the handoff of wifi to actual LTE calling and it makes it difficult for the phones speaker to know where to apply the sound to? I dont have a sim in my phone currently so I am wondering anyone else tried this to see?
Archangel said:
I am wondering if anyone has tried turning off the wifi calling option? I havent tried that yet as it is the only thing I havent tried to see if my phone doesnt have problems when first answering a call with the phones speakerphone and people on the other end not being able to hear me for the first few seconds? I saw in a Google thread that there may be a problem with the handoff of wifi to actual LTE calling and it makes it difficult for the phones speaker to know where to apply the sound to? I dont have a sim in my phone currently so I am wondering anyone else tried this to see?
Click to expand...
Click to collapse
I've had WiFi Calling and VoLTE disabled for a while now - still garbage call quality on speakerphone.
Same here
I have WiFi calling off of mine.. still same issue
i have a new google pixel 3 after an ota update my speacker is not working anymore i tried to reboot the phone and even flashing it but nothing worke with me. can any one help please ?
hi,
i have same issue .. did you find how to solved this problem?
jon2jay said:
I may have found a fix for this. Need you guys to confirm.
Goto the permissions of Google play services, and disable MIC permission. During phone calls you will see a 'this app needs permissions to run blah blah' ignore it. Test speaker phone now. I stumbled upon someone who mentioned this (can't find the post now) and I have had 0 issues w/ straight speaker phone.
Click to expand...
Click to collapse
I can't even make calls with mic permission disabled
jon2jay said:
I may have found a fix for this. Need you guys to confirm.
Goto the permissions of Google play services, and disable MIC permission. During phone calls you will see a 'this app needs permissions to run blah blah' ignore it. Test speaker phone now. I stumbled upon someone who mentioned this (can't find the post now) and I have had 0 issues w/ straight speaker phone.
Click to expand...
Click to collapse
My wife has this issue with her new Pixel 3 - oddly not when calling me (I have an S8) but when calling 3 other confirmed people (who [co-incidentally] all have iphones?). Even talking to them over handset first which is obviously fine, when she switches to speaker mid-call they can't hear her.
We tried this but she still has the issue.
bwgooch said:
My wife has this issue with her new Pixel 3 - oddly not when calling me (I have an S8) but when calling 3 other confirmed people (who [co-incidentally] all have iphones?). Even talking to them over handset first which is obviously fine, when she switches to speaker mid-call they can't hear her.
We tried this but she still has the issue.
Click to expand...
Click to collapse
Newest update ending in C3 for my Pixel 3 has fixed my speakerphone problem, so far! Will keep you posted.
kperk said:
Newest update ending in C3 for my Pixel 3 has fixed my speakerphone problem, so far! Will keep you posted.
Click to expand...
Click to collapse
Yes, she just updated and tested speakerphone with one of the iPhone's she was having trouble with and no problem. Seems to be working for now!