Database Info

[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.

Really confused! Audio drops during calls

Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!

are you running any special ROM or anything because its happening to me as well

I have been having the same problem for almost a month now. I was rooted when this started happening. I went back stock still happened. New 4g card still happened. Another phone still happened. I have been getting the runaround from verizon the whole time they have no clue what is going on.
On a side note asked a friend that works at a little vzw store if they have seen this problem and sure enough she had. She told me that they had a customer go through 4 phones and she started making calls and was told by Customer Support that it was a known thing and there was a software update coming out for that.
After hearing this I called good ole *611 yet again and they were clueless and said they knew nothing about it. *sigh*
¿GotJazz? said:
Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!
Click to expand...
Click to collapse

What rom ???

Yorto said:
What rom ???
Click to expand...
Click to collapse
Umm can't even remember now was a month ago LOL. But my 2nd phone I didn't put one app on or anything left it bone stock and still had the same problem. Same as the customer my friend had they would mess up right out of the box.

probably weak antenna

no you don't lose signal call keeps running you lose Audio.

chiahead52 said:
are you running any special ROM or anything because its happening to me as well
Click to expand...
Click to collapse
Yorto said:
What rom ???
Click to expand...
Click to collapse
Yes, I am running a custom ROM, but it's basically a stock rooted & voodoo'd EE4 ROM (by danalo1979, I think). It's got all the yucky poo-brown colors and all the bloatware.

Same issue here. I'm running completely stock right now, non-rooted. Sometimes the audio will drop at the onset of placing a call (I won't even hear ringing) and sometimes it will happen a few minutes into a call. Other parties do say they can hear me though.
Personally, I've noticed that this problem only happens when I am also connected to a Wireless Network. If I'm running 4G/3G, sometimes I hear echos of my voice, but the audio won't drop out.
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
What should we do? Personally, I'd like to wait for the SG2 to arrive before I start complaining. My plan would be to basically flip out explaining that I need my phone to work like a phone, etc. Then flip out that I paid for 4G and my decision was battery based (so I don't get stuck with a Thunderbolt). I bet I could talk my way into a new SG2 over this... Just saying.

KarateExplosion6 said:
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
Click to expand...
Click to collapse
Well they do not tell me they know what is wrong they tell me they have no clue. I even explained to them somebody there does know as they have explained the issue to someone else that has had the problem but I still get they you just need another phone speel.

I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1

kvswim said:
I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
same, don't have this problem but i probably just jinxed it.

I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?

Edvard_Greig said:
I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?
Click to expand...
Click to collapse
I've experienced that. But I'm not so sure I'm not just covering the mic with my finger.

I was on nluetooth, with the phone in the cupholder... Don't think my finger was involved.
Sent from my SCH-I510 using XDA App

Well 2nd Fru and as I told them it would. It does the same thing. Bone stock. *sigh*

One thing that seems odd to me is that I seem to see this problem more when calling another mobile phone vs. a landline.
Maybe it's just my imagination, but I always see problems when calling my wife's mobile phone. Last night, I called a landline for over an hour without any problem.

same here I can talk to customer service for 1hr+ but mobile to mobile most Ican get is maybe 15 min.

I drive around as part of my job and today I tested a call out to my wife who has a charge as well and we were able to talk for over 20 minutes with no issues. That same area I drove through a few days ago caused 3-4 drops in audio before. So in my opinion its a network related issue and hopefully its get fixed 100% cause most of us need our phones to work solidly

To the people losing audio during their calls, can you post your location?
The reason why I ask this is because on the Verizon forums there is an eight page post about this issue. Seems like a lot of people in Arizona are experiencing this. I'm in Chandler, Az and have this issue, especially when calling other VZW people in AZ.
Can't post links yet but check the VZW community forum for the Charge.

[Q] Problem with Samsung phone performance

Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.

What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info

ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.

I will give you $20.00 a piece for them!!!!

ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7

Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app

Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Android Law #1: Costum ROMs are ALWAYS 10x better than stock.

Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium

Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium

qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).

are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?

ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl

[Q] Rebooting and roaming

****************UPDATE AGAIN
My phone number only seems to switch when I'm under "NV" for my CDMA subscription. It appears to be randomly switching back to NV periodically. If I put it in airplane and switch it back, it will correct my phone number and allow some messages to be sent. Any info on what settings should be there how to keep that from switching or any other info regarding this?
My phone number is currently showing up as 000-000-3720
My MIN is currently showing up as 0000003720
I do have a IMEI and MEID
Hello,
I have had two issues with the galaxy s3 since I got it. I never had any problems with my gnex but gs3 is killing me.
1. When I download AOSP roms like liquid smooth and mrom, the phone randomly will not send text messages and will frequently go into roaming. Even if it says I have 4g, it will still not always send text messages. Then it will randomly be fine for about 45 minutes and then go back into crap mode.
2. When I download touchwiz roms, everything appears to look normal and I have no problems with my phone calls or messages not sending, BUT my phone likes to randomly reboot when opening apps and especially with sending messages. I can reproduce the problem several times over by sending a text message.
Both seem to be sms related. But in many ways seem completely unrelated. Any ideas on what is going on?
Thanks
Bryan

boconnor341 said:
Hello,
I have had two issues with the galaxy s3 since I got it. I never had any problems with my gnex but gs3 is killing me.
1. When I download AOSP roms like liquid smooth and mrom, the phone randomly will not send text messages and will frequently go into roaming. Even if it says I have 4g, it will still not always send text messages. Then it will randomly be fine for about 45 minutes and then go back into crap mode.
2. When I download touchwiz roms, everything appears to look normal and I have no problems with my phone calls or messages not sending, BUT my phone likes to randomly reboot when opening apps and especially with sending messages. I can reproduce the problem several times over by sending a text message.
Both seem to be sms related. But in many ways seem completely unrelated. Any ideas on what is going on?
Thanks
Bryan
Click to expand...
Click to collapse
Try turning off vibrate for notifications - it works in one older JB build.

jefmoody1 said:
Try turning off vibrate for notifications - it works in one older JB build.
Click to expand...
Click to collapse
Ill try that when the issue starts back up again. Right now I'm asymptomatic.
Anyone have this issue or possible solutions to either of the above or a reason why this might be occurring?
Thanks

jefmoody1 said:
Try turning off vibrate for notifications - it works in one older JB build.
Click to expand...
Click to collapse
I tried to do it when it started up again. Its going into roaming again.
****************UPDATE
My phone number is currently showing up as 000-000-3720
My MIN is currently showing up as 0000003720
I do have a IMEI and MEID

boconnor341 said:
Hello,
I have had two issues with the galaxy s3 since I got it. I never had any problems with my gnex but gs3 is killing me.
1. When I download AOSP roms like liquid smooth and mrom, the phone randomly will not send text messages and will frequently go into roaming. Even if it says I have 4g, it will still not always send text messages. Then it will randomly be fine for about 45 minutes and then go back into crap mode.
2. When I download touchwiz roms, everything appears to look normal and I have no problems with my phone calls or messages not sending, BUT my phone likes to randomly reboot when opening apps and especially with sending messages. I can reproduce the problem several times over by sending a text message.
Both seem to be sms related. But in many ways seem completely unrelated. Any ideas on what is going on?
Thanks
Bryan
Click to expand...
Click to collapse
I feel for you. I ruined my first S3 by downloading CM10.1. Never had issues with Galaxy Nexus. S3 is wonky when it comes to AOSP based roms (i.e, speakerphone echo, may lose MEI when flashing, AOKP ms 1 has occasional issues with sudden failed bluetooth connection issues in car, all Jellybean 4.2.1 AOSP based roms seems to have issues with cutting off streaming when traveling in your car via using iHeartRadio). I never had any of these issues with my Galaxy Nexus. When a better phone comes out, I will ditch this S3 fast for a phone that works better with custom AOSP roms. I sometimes long for my old Galaxy Nexus.

sghrush said:
I feel for you. I ruined my first S3 by downloading CM10.1. Never had issues with Galaxy Nexus. S3 is wonky when it comes to AOSP based roms (i.e, speakerphone echo, may lose MEI when flashing, AOKP ms 1 has occasional issues with sudden failed bluetooth connection issues in car, all Jellybean 4.2.1 AOSP based roms seems to have issues with cutting off streaming when traveling in your car via using iHeartRadio). I never had any of these issues with my Galaxy Nexus. When a better phone comes out, I will ditch this S3 fast for a phone that works better with custom AOSP roms. I sometimes long for my old Galaxy Nexus.
Click to expand...
Click to collapse
There are certainly positives and negatives, but at this point the phone is unusable at times and I almost feel like it was a waste "upgrading". .
The issue exists with Touchwiz roms as well in that it reboots rather than go into roaming or fail to exchange data/txts.. Nobody has had this issue? I find it hard to believe I'm the only known case of this. Anyone have something similar or any options?
Could I benefit from starting completely over from stock? Anyone with knowledge pertaining to this would be greatly helpful.
Thanks

boconnor341 said:
There are certainly positives and negatives, but at this point the phone is unusable at times and I almost feel like it was a waste "upgrading". .
The issue exists with Touchwiz roms as well in that it reboots rather than go into roaming or fail to exchange data/txts.. Nobody has had this issue? I find it hard to believe I'm the only known case of this. Anyone have something similar or any options?
Could I benefit from starting completely over from stock? Anyone with knowledge pertaining to this would be greatly helpful.
Thanks
Click to expand...
Click to collapse
updated again

Pixel 3 Speakerphone issues?

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!