I have a Verizon branded model XT1922-6. A little over a week ago I was attempting to set up Google Family Link on my phone, and the Google rep who called couldn't hear me. No one can hear me, not even with speakerphone on. Even the number presses during a call don't give sound on the other end, only light static.
I have dabbled in removing unwanted apps through ADB, but a factory reset hasn't resolved the issue. I CAN, however, dictate through Gboard and record voice memos just fine. Using an external earbud and mic work just fine as well. I highly doubt there is a hardware issue. Any insight to this would be greatly appreciated.
Dmbruley said:
I have a Verizon branded model XT1922-6. A little over a week ago I was attempting to set up Google Family Link on my phone, and the Google rep who called couldn't hear me. No one can hear me, not even with speakerphone on. Even the number presses during a call don't give sound on the other end, only light static.
I have dabbled in removing unwanted apps through ADB, but a factory reset hasn't resolved the issue. I CAN, however, dictate through Gboard and record voice memos just fine. Using an external earbud and mic work just fine as well. I highly doubt there is a hardware issue. Any insight to this would be greatly appreciated.
Click to expand...
Click to collapse
The permissions for Google apps are incorrect. Motorola screwed up is the problem. The Sprint variant has a problem with the keyboard sound not working after a reboot for the same reason. You have to manually toggle the preference to make it work again every time. You'll have to wait for an OTA.
Which Google app permissions, exactly? Do I need to allow them through system settings, or the Google app itself?
Dmbruley said:
Which Google app permissions, exactly? Do I need to allow them through system settings, or the Google app itself?
Click to expand...
Click to collapse
I'm referring to the permissions found in /system/etc/permissions not the ones found in settings.
Related
Had some issues with the touch tones not working correctly with the speakerphone enabled. Didn't find any threads here on XDA but found a few over on a couple other android forums.
Basically it seems that when using the touch tones with speakerphone enabled, the mic picks up the speaker phone and the receiving end hears each touch tone twice.
I had the issue when trying to call verizon wireless to enter my passcode, as well as trying to setup my voice mail. I have 3 separate Galaxy Nexus phones in my family, and the issue can be replicated on all 3 phones.
Also noticed lowering the volume on the speakerphone can alleviate the issue too, but it's just kind of annoying as I don't want to hold the phone up next to my ear when I'm trying to enter things on the dial pad.
I've also tried switching the DTMF setting between long and normal, the problem still exists
Hoping with a firmware update they can filter out the touch tone, or just not make the touch tones audible to ourselves. (I'm assuming
this is because the speaker is so close to the mic on the GN)
Anyway, I don't think there's a fix for it yet, but I'm just posting here to see if anyone else is experiencing the same issue, and to make people aware of it.
Also found the issue on google support here:
http://code.google.com/p/android/issues/detail?id=24467
Bump,
Anyone else run into the same issue? Or have some secret fix I don't know about? (Other than turning off the speaker lol)
Sent from my Galaxy Nexus using XDA App
This explains the problems I was having the other day trying to join a Go-To-Meeting - would not accept my pin.
I was on speaker phone too - ty for this !
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
_Gir_ said:
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
Click to expand...
Click to collapse
Just realized this before I came to post, thanks for pointing it out too! Mute FTW!!!
i too noticed this as well when i first got it and think that it ridiculous that it wasnt thought out better.
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
ConanOBrien said:
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
Click to expand...
Click to collapse
This is the workaround I've been using for about a month now with no issues. I had the same issue where the conference call service wasn't getting my pass code entered correctly.
Only issue now is the headset echo heard by connected parties, which has been reported and hope to be fixed soon. I've tried several workarounds here but none have been bulletproof.
Looking to see who else out there is using Groove IP and what settings you have found to work the best. I can't seem to pin down the right combo so I am going to try crowdsourcing.
http://snrblabs.com/snrb/grooveIp.aspx
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
Are you having issues w/ sound distortion over WiFi?
The default settings work fine on most devices, and the changes I've made are minor.
Using version 1.2.21:
-Allow 3G/4G calling
-Accept calls on answer
-turned off DTMF feedback under Audio/Echo settings
-turned on Keep Screen On and Sync Voice under Troubleshooting
What are your Speaker and Mic gain settings? I am only calling over WiFi
Phillip Fry said:
What are your Speaker and Mic gain settings? I am only calling over WiFi
Click to expand...
Click to collapse
Speaker vol: 10
Mic gain (bluetooth as well): 0
Echo Cancellation: On, with Auto Detect
I haven't noticed any issues on my end by tweaking these settings, but can also say things worked fairly well on default.
Phillip Fry said:
What are your Speaker and Mic gain settings? I am only calling over WiFi
Click to expand...
Click to collapse
What kind of issues are you running into? Defaults should be good for the Galaxy Nexus. One thing to watch out for is by default the Galaxy Nexus puts the wifi into a power saving state when the screen turns off. You can change that from the android settings->wifi settings->advanced wifi settings, or enable Keep Screen Alive in GrooVe IP.
I get noticeable lags using Groove IP on my Galaxy Nexus. The extent varies - it's sometimes less than half a second, but often close to two seconds. Happens both incoming and outgoing. I am using the default settings except for the volume. If this matters, the lag is there both on Wi-Fi and 3G.
Phone: Galaxy Nexus (GSM Unlocked)
Carrier: T-Mobile
Region: Seattle
Any advice would be appreciated.
daihard said:
I get noticeable lags using Groove IP on my Galaxy Nexus. The extent varies - it's sometimes less than half a second, but often close to two seconds. Happens both incoming and outgoing. I am using the default settings except for the volume. If this matters, the lag is there both on Wi-Fi and 3G.
Phone: Galaxy Nexus (GSM Unlocked)
Carrier: T-Mobile
Region: Seattle
Any advice would be appreciated.
Click to expand...
Click to collapse
Few things can cause lag. First would be latency on the data connection. Apps running on the device that use cpu or data...or battery manager or task killer apps could also cause problems with calls. We are also working on a new update that should improve the in-app delay for audio. On our Galaxy Nexus it seems to work pretty good so far. I think we'll have a beta for it ready sometime this weekend. We'll likely be posting it on our facebook page when it's ready. Oh, something on the device going into a power saving state would also cause delay. Keep Screen Alive can help with that.
snrb Labs said:
Few things can cause lag. First would be latency on the data connection. Apps running on the device that use cpu or data...or battery manager or task killer apps could also cause problems with calls. We are also working on a new update that should improve the in-app delay for audio. On our Galaxy Nexus it seems to work pretty good so far. I think we'll have a beta for it ready sometime this weekend. We'll likely be posting it on our facebook page when it's ready. Oh, something on the device going into a power saving state would also cause delay. Keep Screen Alive can help with that.
Click to expand...
Click to collapse
Thanks for the update! I will await the new beta version. I'll keep an eye out on your FB page.
Besides the Keep Screen Alive option, are there other options that may help reduce the lag? I see things like Synchronize Voice and Mic Buffer. For instance, will it reduce delay if I change the Mic Buffer size from medium (default) to small?
Thanks again!
daihard said:
Thanks for the update! I will await the new beta version. I'll keep an eye out on your FB page.
Besides the Keep Screen Alive option, are there other options that may help reduce the lag? I see things like Synchronize Voice and Mic Buffer. For instance, will it reduce delay if I change the Mic Buffer size from medium (default) to small?
Thanks again!
Click to expand...
Click to collapse
Synchronize Voice can help, I don't really use it on the Nexus. Changing the mic buffer to small should also help, that's one of the things we're changing. Small seems still too large. So we're going to be adjusting small to be smaller and make it the default.
snrb Labs said:
Synchronize Voice can help, I don't really use it on the Nexus. Changing the mic buffer to small should also help, that's one of the things we're changing. Small seems still too large. So we're going to be adjusting small to be smaller and make it the default.
Click to expand...
Click to collapse
Thanks! I will make adjustments to those settings to see how it goes.
I wonder if there is plan to support more than one google voice login in Grooveip soon? Something that we can switch from one to another quickly?
testrider said:
I wonder if there is plan to support more than one google voice login in Grooveip soon? Something that we can switch from one to another quickly?
Click to expand...
Click to collapse
Might not be soon but it is something we're working on. Right now you can switch users pretty quickly by going into the menu and pressing change user. But that's not the same as supporting multiple accounts. Battery life is also an issue with multiple sign ins, still working on it.
Hey is this beta or new version addressing the latency available yet? I have an Epic Touch 4G & have tried everything (spoken to support repeatedly over email - thanks!) & still get 1-2 second delay. Difficult to have a normal conversation as we keep cutting each other off as we think we're done speaking.
snrb Labs said:
Might not be soon but it is something we're working on. Right now you can switch users pretty quickly by going into the menu and pressing change user. But that's not the same as supporting multiple accounts. Battery life is also an issue with multiple sign ins, still working on it.
Click to expand...
Click to collapse
elcidroyale said:
Hey is this beta or new version addressing the latency available yet? I have an Epic Touch 4G & have tried everything (spoken to support repeatedly over email - thanks!) & still get 1-2 second delay. Difficult to have a normal conversation as we keep cutting each other off as we think we're done speaking.
Click to expand...
Click to collapse
The latest version on the market has all our improvements for latency. There will still be latency from your network or from the device. Stopping apps running in the background can improve the device latency.
Well I downloaded that version and most of that lag seems to be gone. Yippee!
elcidroyale said:
Well I downloaded that version and most of that lag seems to be gone. Yippee!
Click to expand...
Click to collapse
Glad that improved things. Thanks for the update.
I just purchased this after months of debate. Are there any settings to reduce the static on the other caller's end? I did some test calls with a friend's phone, except I was holding both devices in each hand. It doesn't matter who initiates the call, but they'll hear a static noise that doesn't happen if the call is made via mobile network. Could very well be Google Voice itself because people have mentioned it to me before before I purchased Groove IP, but I just want to be sure.
Also, sending and receiving bluetooth calls do work through my car stereo. But if I'm receiving a call, something is missing to tell the radio to pause/mute the music and start the ringer. The phone itself still rings and vibrates, but it's easy to miss a call if the music is loud enough. Is there an additional setting I'm missing? The function works properly if I'm using the regular phone app.
binglejellsx2 said:
I just purchased this after months of debate. Are there any settings to reduce the static on the other caller's end? I did some test calls with a friend's phone, except I was holding both devices in each hand. It doesn't matter who initiates the call, but they'll hear a static noise that doesn't happen if the call is made via mobile network. Could very well be Google Voice itself because people have mentioned it to me before before I purchased Groove IP, but I just want to be sure.
Also, sending and receiving bluetooth calls do work through my car stereo. But if I'm receiving a call, something is missing to tell the radio to pause/mute the music and start the ringer. The phone itself still rings and vibrates, but it's easy to miss a call if the music is loud enough. Is there an additional setting I'm missing? The function works properly if I'm using the regular phone app.
Click to expand...
Click to collapse
The static could be because both phones were in close proximity to each other. Have you tried it with normal calls?
For incoming calls were you using the native music app or another app like pandora? We broadcast that a call is being made or received, the native music app should detect that, but an app like pandora may not since the app isn't the same as the native phone system.
snrb Labs said:
The static could be because both phones were in close proximity to each other. Have you tried it with normal calls?
For incoming calls were you using the native music app or another app like pandora? We broadcast that a call is being made or received, the native music app should detect that, but an app like pandora may not since the app isn't the same as the native phone system.
Click to expand...
Click to collapse
You mean to a landline? I haven't. I did try with another person a few hundred feet away with the same results. I also talked to someone else for a few seconds, but the only thing they asked was if I was whispering. After I had posted on here, I changed my settings to the ones recommended from the "other" forum: http://rootzwiki.com/topic/32464-voip-apps/page__st__10#entry902020. My voice was probably just low due to the low mic gain setting, but I'll leave things the way they are until I get more comments from people's calls.
As for the bluetooth issue, I'm not using my phone to play music. The music is through the radio, which utilizes bluetooth to make phone calls. Normal operation of incoming calls cuts the audio and rings through the car speakers until I pick up. With Groove IP calls enabled, only the phone is ringing and the music/car audio is still playing (which is usually louder than the phone's ringer). Hope that clears things up a little.
Happy Holidays!
If I make or recieve a call with the stock sony call app, the other party can not hear me unless I switch to speaker. I tried with different people, it's always the same.
However, if I use google hangouts for calls the both the microphone and the spaker work just fine.
If I record a voice message in Whatsapp, the microphone works but is really low.
If I use Trackid for a song the microphone doesn't work again.
This has only started a few weeks ago and I can't find any solution on my own. Anyone has an idea what the problem could be?
I already tried safe boot and factory reset, it stays the same. I am really confused as it only happens in a few apps while working fine in others.
Thanks in advance!
Just blow some air into the microphone. I also have this problem
Puneet247 said:
Just blow some air into the microphone. I also have this problem
Click to expand...
Click to collapse
That didn't work :/
But thank you for your answer
I submitted my zl in service centre for 25 days and they do nothing , always keep saying that parts are coming. Finally I ask them to give it to me without replacing the microphone as i have to go somewhere, Finally I factory reset my phone use a pin,cotton and and some water in the microphone then blown some air And it WORKED. So most probably its the dirt. For your hangouts working it might be your phantasm.
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.
Hello All,
My apologies if this has been already asked and have been overlooked by me.
Anyone experience the output audio randomly switching between speakers when on a speaker call?
When I put a call on speaker, the speaker switches randomly.
Is this a known issue? If so, any fixes?
using the stock phone app? or other 3rd party apps?
Stock phone app
How long until that happens?
Does it happen in safe mode?
Try clearing system cache.
Clear associated apk caches then data if the former doesn't get it.
Do not reload as the problem if solved will only probably pop up again.
Tried the above suggestions. Nothing works. A bit frustrating paying a grand for a phone and this doesn't work among other things (google assistant doesn't respond and activates randomly, random home launcher switches.)
Do you have microsoft teams installed by any chance?
https://answers.microsoft.com/en-us...s-models/d4d25d15-b22d-4721-a07f-b2069eb8ecbf
Negative. Teams is not installed. Bit surprised that not many are having this issue.