My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
try the replacement handset. I've had my G3 since it came out with no problems whatsoever.
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
Wow, my G3 just started doing this too. I've had it for 6 months and it's just been the past week that I've been having issues. It's hit or miss, but about 90% of the time I get complaints that the other person can't hear me or that I sound very faint. It's been driving me crazy. I've figured out that I can toggle speaker mode and it fixes it. Can you try that out see if it's the same for you?
I noticed this about a week ago, interesting. Wonder if it's something on tmobile's network.
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
---------- Post added at 09:48 AM ---------- Previous post was at 09:04 AM ----------
madmanjsm said:
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
Click to expand...
Click to collapse
I'm now running in safe mode and a couple test calls to my Google Hangout sound fine. Don't think it's a hardware issue.
I've started to experience this too. It's really annoying. I hope it gets fixed soon. Though, I am glad to know it's not just me. I really didn't want to dig around in my apps to find the offender.
Question: Do any of you guys have the Nova Launcher Beta running? I think I started having issues around then.
Sent from my LG-D851 using Tapatalk
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
bryanwny said:
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
Click to expand...
Click to collapse
Thanks! I downgraded and installed Google App 4.1.29 here http://www.apkmirror.com/apk/google-inc/google-search/google-app-4-1-29-1706998-arm-android-apk-download/. Also disabled auto-update for Google Apps so it doesn't update to 4.2.16.87075793. I'll test it out and see what happens.
I also have had the same problem lately, just twice. A reboot fixed it
This is affecting me as well. I'm also in Los Angeles and the phone was fine until some time last week. I'm trying to the google apps downgrade now...
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Lookatthemonkeys said:
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Click to expand...
Click to collapse
Try downgrading the Google app. Worked fine for me.
Downgraded, seems better. Are people also recommending not to use voice activated Google now?
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
tippingvan said:
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
Click to expand...
Click to collapse
In the play store for the Google search app click the uninstall button. That will return the app to it's factory version. Then just install the version that's linked earlier in this thread. Make sure you have automatic updates turned off for the app or it will keep updating.
Sent from my LG-D851 using Tapatalk
Same thing happens to me. I had my phone for about 2 months now and sometimes people cant hear me or i sound like a transformer. i restart my phone and it fixes the problem but still does it after a couple days. I'm not rooted or anything like that. I also have a problem when I'm on a call. my volume bare goes up and down if i wanna lower and or raise it and the volume sounds the same even on speaker phone it does it too..
I had the problem turn off ok google from any screen and reboot and problem with voice calls fixed
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
JohnnyDanger said:
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
Click to expand...
Click to collapse
I was gonna do a factory reset and if that didn't work i was gonna get a replacement . Hopefully this fixed the problem. The only issue I seem to be having is. when I'm on speaker phone or have it to my ear. and when i go to adjust the volume it doesn't change it. like i see the meter go up and down but the volume stays the same. its weird
I can confirm that after enabling voice activation for google now from any screen was the culprit of Mt audio issues. I was told I sounded far away or like a robot far away. Reset my device numerous times and reinstalled all apps and made calls. Once I enabled OK google from google now the issue came back. Disabled it and BOOM it worked fine. Haven't had an issue since.
Related
Since moving to Jellybean (when it first got released) and attempting to use Google Now, I noticed that the it wasn't doing or understanding what I was saying. It appeared that there was a lot of static noise before it would recognise what I was trying to say.
I loaded some recording software to make sure it wasn't just Google Now, but it turns out that it just hisses for that first 5 seconds before it comes good. It does not happen in phone calls, just when recording/talking to Google Now. Changing ROMs, kernels and radios has not changed the problem. Even moving up to the new 4.1.1 hasn't rectified the problem.
Has anyone else had this problem? Has it ever been fixed?
Any help would be fantastic!
Bumping.
Still can't seem to find an answer anywhere for this.
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
galapogos01 said:
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
Click to expand...
Click to collapse
I've tried different basebands, ROMs etc. Still suffers from the 2 seconds of hissing/not working microphone before it comes good and is usable.
Interesting. I too am on Telstra, tried few 4.1 and 4.1.1, CM10 and the same issue. Not to mention, even after the hiss is over, the volume is very low and rubbish in general.
Interesting that it affects a lot of Telstra phone owners.
Anyone reverted to the stock Telstra rom/baseband to test? Does it affect voice search in 4.0.x as well?
Same problem!
I have this exact problem!! I've had difficulty finding any others with this problem until I found this thread.
Grr, mine shows static for about 4 seconds and it struggles to understand anything at all! After those 4 seconds, it dies down, then I can speak and it is better but far from perfect with recognising my speech!
FYI mine is a yakjudv Telstra phone from Australia which I flashed to yakju 4.0.4 and then did a JB update OTA......
It was on the stock DVKK6 but am now on the XXLF1 radio that came with JB....
Argh, whats going on, i was so pumped for google now voice actions!!! Now its basically useless!!
Mines almost spot on 4 seconds every single time.....
Any solution to this would be greatly appreciated!
+1 again on my gnex
factory installed yakjudv i think, from vodafone.
I have had it since ICS, tried to record lectures in class, and the first few seconds is always static.
Now that you mention it, when I activate voice search in google now, i see the grey circle voice indicator spazzes out for a few seconds before it goes back to normal. Maybe that's why I have to speak loud for it to recognise my voice to make it distinct from the initial static, so it usually doesn't work that well.
Kinda weird that it appears to be Telstra gnex's. Still no luck in finding fixes yet.
Sent from my Galaxy Nexus
Any workaround or fix for this?
It seems like Santaria has already tried a variety of different radios with no luck.
Is this a case of sit and hope that Google fixes this?
So what exactly is the problem? There's 2 mics in the phone, but its picking up the wrong one?
Since when were there 2 mics? one for phone call and one for speakerphone? I didn't even know this. How could this happen and why is it only on Aussie phones? The hardware should be the same across the board?
I'm so confused
One is for noise reduction.
Cheers,
Jason
I wonder if there's a way to enable/disable the noise reduction mic?
Sent from my Galaxy Nexus
galapogos01 said:
One is for noise reduction.
Cheers,
Jason
Click to expand...
Click to collapse
One is for calls the other one is for recording videos and video calls...The Galaxy Nexus do not have a noise reduction software on board neither the required hardware so no noise canceling feature!
Sent from my Nexus 7
Err...
http://www.slashgear.com/galaxy-nexus-review-21196912/
http://en.wikipedia.org/wiki/Galaxy_Nexus
There seems to be some debate about its effectiveness - probably related to the above bug disabling it in some cases.
For the record, same problem on my telstra Gnex, google now only works if I hold the mic right to my mouth.
I'm having the exact same issue. I just bought a new gn that was locked to Vodafone Australia. I unlocked it and went to yakju then got the OTA and then started having the exact same problem that everyone else has described. I get massive static and so far nothing I've said has been recognised. It just times out with the message "recognising...".
I've recorded my voice using an app but everything sounded fine and I didn't get any static. I have the same problem if I use a hands free kit too.
Seems this happened with ICS also
http://forum.xda-developers.com/showthread.php?t=1602840
Star this issue
Hey guys, a few of us seem to be having this problem, please star this issue so that Google will be aware of it.
http://code.google.com/p/android/issues/detail?id=29092
SIMPLY CLICK HERE AND STAR THE ISSUE.
Starred
Starred a long time ago...
No luck, even with 4.2.2
I take it they're never going to fix this problem
For whatever reason callers can't hear me.
I think I have narrowed it down to Bluetooth, doesn't matter which device. A reboot seems to resolve the issue.
What can I do besides the infamous hard reset? I know it isn't a microphone issue because I used Voice recorder and it was crystal clear when callers could not hear me.
mikemikemikexxx said:
For whatever reason callers can't hear me.
I think I have narrowed it down to Bluetooth, doesn't matter which device. A reboot seems to resolve the issue.
What can I do besides the infamous hard reset? I know it isn't a microphone issue because I used Voice recorder and it was crystal clear when callers could not hear me.
Click to expand...
Click to collapse
I am coming here to solve THIS EXACT problem.
If you go to google card settings -> Voice -> "Ok Google" detection
Turn off "From Any Screen"
I have Verizon LG G3 unrooted and just had my phone swapped out from Verizon on Saturday because of this issue. Got my new phone after it was mailed to me, bought a new glass screen protector for $50 set all my settings back up and then today it started again. I have been searching for HOURS online and found a reddit article suggesting this solution. Tried it, and like magic my phone was working fine again. It is entirely software related.
First thing I did was come to this forum to make sure it was recorded here for others suffering.
AHpatriots37 said:
I am coming here to solve THIS EXACT problem.
If you go to google card settings -> Voice -> "Ok Google" detection
Turn off "From Any Screen"
I have Verizon LG G3 unrooted and just had my phone swapped out from Verizon on Saturday because of this issue. Got my new phone after it was mailed to me, bought a new glass screen protector for $50 set all my settings back up and then today it started again. I have been searching for HOURS online and found a reddit article suggesting this solution. Tried it, and like magic my phone was working fine again. It is entirely software related.
First thing I did was come to this forum to make sure it was recorded here for others suffering.
Click to expand...
Click to collapse
Do you by any chance have bluetooth in Google Settings enabled?
I do have it enabled
AHpatriots37 said:
I do have it enabled
Click to expand...
Click to collapse
Sorry missed this post. Just as an FYI, your suggestion works but also keeping everything checked except Bluetooth
Hey all,
Just wondering if anybody is having a similar issue. Before I get started I did a quick search and havent found any recent threads stating the same issue.
What happens is often I will place a call and immediately switch to speakerphone so I can put the phone down and be handsfree, however for some reason I cannot hear ANYTHING the other line is saying, but they can hear me just fine. Switching back to earpiece does nothing either. This problem has been happening for about a week or so.
The only remedy I have found is to either call back, or reboot my phone but both of these options are unacceptable IMO.
Has anybody else experienced this? If so, what was your solution? I have gone through all the call settings and nothing seems to be out of the ordinary. I don't mute or hold calls and my call volume is almost at max.
Any help or input is appreciated.
Same problem since I went to lollipop. Met a lgcrep who had never seen this
Thanks for the response. It must be a pretty bad software bug then
The problem is with the 3/19 update of the Google search app. Either roll back the build on your phone or disable OK Google from any screen. Same problem exists on KitKat.
OMG thank you so much!
I was starting to think I would never be able to use speakerphone again
Yaminashi said:
OMG thank you so much!
I was starting to think I would never be able to use speakerphone again
Click to expand...
Click to collapse
You are welcome. I almost RMA'ed my phone. Apparently, lots of people have already only to have the same problem as soon as they apply updates.
Here's the apk for the older version. Make sure that you roll back updates to the installed version of Google (and turn off auto-updates) before installation:
http://www.apkmirror.com/apk/google...-app-4-1-29-1706998-arm-android-apk-download/
Same issue
datawrhsdoc said:
You are welcome. I almost RMA'ed my phone. Apparently, lots of people have already only to have the same problem as soon as they apply updates.
Here's the apk for the older version. Make sure that you roll back updates to the installed version of Google (and turn off auto-updates) before installation:
http://www.apkmirror.com/apk/google...-app-4-1-29-1706998-arm-android-apk-download/
Click to expand...
Click to collapse
I had this same issue and disabling the from any screen feature fixed it. I do like that feature however and would like to continue to use it. Do you know if the version in your link supports that function? If not do you know if there's a version that does that does not interfere with speakerphone function?
Thanks.
I have been having trouble with my microphone shutting off while I am on a phone call. This issue seems to happen after 5 to 10 minutes randomly. I have tried toggling the mute button and the speakerphone button, this does not seem to work. The only solution I have found is to end the call and redial. Has anyone else been experiencing this issue and does anyone have any input on solving this problem?
Thanks.
crygon said:
I have been having trouble with my microphone shutting off while I am on a phone call. This issue seems to happen after 5 to 10 minutes randomly. I have tried toggling the mute button and the speakerphone button, this does not seem to work. The only solution I have found is to end the call and redial. Has anyone else been experiencing this issue and does anyone have any input on solving this problem?
Thanks.
Click to expand...
Click to collapse
Yes actually this just happened to me twice today. Once after about 20 minutes into a call and then again 40 minutes into a call. I can hear them just fine but they can't hear me.
Are u on Project Fi?
I'm on Verizon and this has happened twice
Interesting....
This has been reported on Project Fi since April on Nexus 6, 6p, and now on Pixel
I contacted Verizon they said that it is a software issue and to expect an update. I am not sold on the waiting it out for an update, might just get a replacement.
crygon said:
I contacted Verizon they said that it is a software issue and to expect an update. I am not sold on the waiting it out for an update, might just get a replacement.
Click to expand...
Click to collapse
Not sure replacement will fix anything. Ive had this issue (and many others) on Fi for a long time. It's the first time I hear Verizon people have this as well.
I am not sure about update either, there is no fix for this since April as I said before.
I don't think it's on all calls...maybe landline only? Also not on international calls. I tend to notice this while making long 800 calls mostly, and it always cuts out at around 30 minutes
I'm having this problem randomly as well. A couple things to note:
I had to replace my Pixel 5" already due to a stuck volume down button and the muted call problem happens on the new phone as well.
Nothing solves this once the caller stops hearing you. You have to end the call and call them back and then things work just fine.
It's not related to Project Fi as I'm on a Verizon sim card and have experienced this with landline and cell calls.
I read somewhere that someone tried not optimizing all phone related apps/frameworks. I've tried this and thought it fixed it but it didn't as I just had it happen 20 minutes ago.
I'm at a loss as to why the mic cuts out in the middle of longer calls. It's never happened during quick 5-10 minute calls for me.
I have the same issue with my Pixel XL. Verizon has already replaced the phone once. The replacement phone does the same thing. It seems to happen with those who I am talking with on an iPhone. I have tried all of the above fixes and nothing works. Other than this, this is a great phone. Hopefully Google figures it out fast, I don't want to go back to a different phone.
I don't believe it has anything to do with calling or receiving calls from iPhone users. The person it most frequently cuts off with me is calling from a Samsung G7 or landline. It's gotta be a software issue. I still think it has something to do with the length of the call and the phone somehow going into doze or something. I'm not trying to remember to pull the phone away from my face every 10 minutes or so to wake up the screen if I'm on a long call to see if that "solves" it.
Just started happening to me after two weeks...
Happened 3 times (after 3 minutes on the call).... All were incoming calls from a landline...
Verizon Users
Not saying this may be a solution but I changed to Franco Kernel r5 and I have not seen this issue occur since that time. Could be coincidence or ??
Could be placebo effect but I feel I'm getting better battery life which I didn't think would be possible :good:
Update Nov 24 - it's got to be the kernel that's causing this issue. Since I went to FK r5 I've not had a single dropped call (or more precisely a muted microphone). I haven't tried flashing back to stock to make the problem reoccur but I'm pretty confident a kernel change (Franco or perhaps ElementalX) would solve this issue.
Same issue for me. On Verizon. Does seems I do have the most problems with iPhone users on AT & T service, although that is not conclusive. A replacement from Verizon did not solve the problem.
Sounds like mine. Mic started cutting out first, then the earpiece speaker next. Eventually neither would work at all. VZW shipped a replacement.
Can anyone else confirm that a kernel change fixes the microphone issues? I'm unlocked on Verizon(completely stock at the moment) and don't wanna have to exchange my phone.
Update: fk r6 kernel did not fix my microphone issue.
jguy said:
Can anyone else confirm that a kernel change fixes the microphone issues? I'm unlocked on Verizon(completely stock at the moment) and don't wanna have to exchange my phone.
Update: fk r6 kernel did not fix my microphone issue.
Click to expand...
Click to collapse
Did u try r5?
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
fyyzer said:
Not saying this may be a solution but I changed to Franco Kernel r5 and I have not seen this issue occur since that time. Could be coincidence or ??
Could be placebo effect but I feel I'm getting better battery life which I didn't think would be possible :good:
Update Nov 24 - it's got to be the kernel that's causing this issue. Since I went to FK r5 I've not had a single dropped call (or more precisely a muted microphone). I haven't tried flashing back to stock to make the problem reoccur but I'm pretty confident a kernel change (Franco or perhaps ElementalX) would solve this issue.
Click to expand...
Click to collapse
Any update on changing the kernel
junweigu said:
Did u try r5?
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
Any update on changing the kernel
Click to expand...
Click to collapse
I can't say for certain the kernel affects it one way or the other. I can say that since I've been on Franco's kernels I've had this issue pop up no more than once every 3 weeks rather than sometimes multiple times per day. Kernel swap doesn't appear to be a solution but I believe it's helped me.
I have not tried r5, but my issue has gone away. I don't think it is kernel related. I suspect it might have been inserting a wired headset into the jack may have done it for me. Whether it was hardware of software I think it made something switch. Good luck.
junweigu said:
Did u try r5?
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
Any update on changing the kernel
Click to expand...
Click to collapse
Verizon user here with same issue. It happened to me within one week of the pixel release.
The problem first occurred when stock, and has continued throughout multiple updates, mods, kernels, etc.
I'm also having this exact same issue on Verizon. Here's some observations I've made, maybe some of you can confirm or deny these?
-Seems to happen almost exclusively on non-HD calls, like to landlines, almost never happens on HD calls to other Verizon users.
-Happens with or without using bluetooth, so isn't an issue with the Pixel's microphone.
-Is getting worse, I got my pixel in November and I don't remember it happening during the first month or so. Now it's happening almost every day.
-I noticed it more after I enabled wifi calling, but it still happens when I turn wifi calling back off.
-I called google support and they want to know if it happens in safe mode. I don't really want to stay in safe mode all day waiting to see if it happens, has anyone else done this?
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
I didn't notice this on the unit that I sent back!
Thanks.
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
fury683 said:
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
Click to expand...
Click to collapse
Thanks for the suggestions.
No screen protector fitted or anything obscuring the sensor.
Next time it happens, I'll check to see if it might need cleaning.
One theory I have, is that this phone has been upgraded with the November patch and maybe there's something in there that has caused this issue.
Has anyone else noticed this after the Nov update?
Thanks.
jscsltd said:
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
Click to expand...
Click to collapse
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
I know there is a bug when using the pixel buds and unplugging them either before a call or during it would stop the proximity sensor from working.
a reboot was the only thing that would fix this issue for me
xweb10 said:
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
Click to expand...
Click to collapse
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
How do I test my proximity sensor?
jscsltd said:
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
Click to expand...
Click to collapse
I am trying to get to the bottom of this. Do you happen to have a Samsung Gear watch? I have the S3 and removed the "phone calls" option from the Pixel Bluetooth menu and so far this issue has not occured, but I am still testing.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
swieder711 said:
How do I test my proximity sensor?
Click to expand...
Click to collapse
There are apps on the play store.
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
jscsltd said:
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
Click to expand...
Click to collapse
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
xweb10 said:
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
Click to expand...
Click to collapse
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
jscsltd said:
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
Click to expand...
Click to collapse
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
xweb10 said:
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
Click to expand...
Click to collapse
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
jscsltd said:
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
Click to expand...
Click to collapse
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
baginz10 said:
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
Click to expand...
Click to collapse
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
xweb10 said:
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
Click to expand...
Click to collapse
I've switched off the ability to take calls on the S3 and can now switch to phone speaker with ease.
I'm hoping I can re-enable the S3 capability when an update by either Google or Samsung fixes the issue.
jscsltd said:
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
Click to expand...
Click to collapse
Sorry I wasn't clear I've done an RMA with google so just wanted to see if anyone else had done the same even though they didn't purchase direct from them. Last year with the 2XL they would send the new one out once the faulty device was sent at the post office, they must have known from the tracking. This time it's via UPS and is going straight to Poland! Not due to arrive until the 4th. If a replacement doesn't get sent out tomorrow or Monday looks like I'll be waiting a while. I even noticed screen burn in when resetting it. Changed to Samsung displays and still burn in from the nav bar just like last year. I wish I'd gone back to carphonewarehouse now to get a replacement!
Wow, I never would have thought of the Samsung gear watch interfering. I have the newest one (the one after the s3) and had the same issue with the screen staying awake while on a call. It was the one thing I really didn't like about the phone. Seems like the symptoms are the same Pixel 3xl, verizon, Samsung Galaxy watch and a restart fixes the issue for a while. I just tried what you suggested. Thank you very much for posting your idea.
I've been dealing with a similar issue, but not exactly,
My screen turns off when I hold the phone against my ear, but the display still seems "active".
My cheek is still bringing the notification area down, toggling my quick settings or even going into the settings app (if my phone was unlocked while I answered a call).
It's been super constant and annoying because one time my flashlight was toggled in an elevator, which was a bit awkward.
Another time my clock app opened and changed my alarm time and then turned it off entirely.
Luckily I could feel the vibration so I knew something was going on but this is a really strange issue.
I have already setup a RMA since the phone has a speaker distortion problem as well, so we'll see what happens once the new device arrives.