Related
OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.
I have a Tmobile G2 that I just got a week ago. I played around with it for a couple days before deciding to root it, but finally pulled the trigger. Two days after rooting it a very strange thing happened. In the middle of the evening some of my Google applications stopped syncing. Gmail, Voice, and Contacts stopped. Drive still worked. Hangouts still worked... It was just weird. I clicked around for awhile and hit the interwebs to find the solution or to see if there was some widespread google outage again, but nothing.
I did everything I could think of, and then I finally clicked the option to take the phone back to stock. I know it wasn't going to take away my root, but at this point I wasn't thinking root was the problem. I just thought maybe I installed something that messed up the phone or something. Anyway, I took it back to normal and now the problem was weirder. It wouldn't even let me connect my Google account (or any google account) to the phone. It kept saying there was some sort of server error. I called TMO support and they couldn't figure it out either. They gave me a number to call Google support to let them fix it. They said that this was a 'known issue' and google support would be the one to fix it.
I kind of got nervous that they were going to creep into my phone or something and void my warranty. If my phone was broken and wouldn't connect to Google anymore then I at least wanted to be able to return it to the store and get a new one. I kinda like this device. So I un-rooted it and took it way back to stock. That fixed the problem. I don't know why, but it did. It left SU on the phone, so I'll have to get that off if it has issues again, but for now it is working fine.
Any idea why it would have just suddenly stopped connecting to Google? It connected to Drive just fine and several other apps, but the important ones wouldn't work. Unrooting it did the trick, but that would suck if you have a really great setup built. Oh well... The price you pay for being a hacker I guess.
ocdetails said:
I have a Tmobile G2 that I just got a week ago. I played around with it for a couple days before deciding to root it, but finally pulled the trigger. Two days after rooting it a very strange thing happened. In the middle of the evening some of my Google applications stopped syncing. Gmail, Voice, and Contacts stopped. Drive still worked. Hangouts still worked... It was just weird. I clicked around for awhile and hit the interwebs to find the solution or to see if there was some widespread google outage again, but nothing.
I did everything I could think of, and then I finally clicked the option to take the phone back to stock. I know it wasn't going to take away my root, but at this point I wasn't thinking root was the problem. I just thought maybe I installed something that messed up the phone or something. Anyway, I took it back to normal and now the problem was weirder. It wouldn't even let me connect my Google account (or any google account) to the phone. It kept saying there was some sort of server error. I called TMO support and they couldn't figure it out either. They gave me a number to call Google support to let them fix it. They said that this was a 'known issue' and google support would be the one to fix it.
I kind of got nervous that they were going to creep into my phone or something and void my warranty. If my phone was broken and wouldn't connect to Google anymore then I at least wanted to be able to return it to the store and get a new one. I kinda like this device. So I un-rooted it and took it way back to stock. That fixed the problem. I don't know why, but it did. It left SU on the phone, so I'll have to get that off if it has issues again, but for now it is working fine.
Any idea why it would have just suddenly stopped connecting to Google? It connected to Drive just fine and several other apps, but the important ones wouldn't work. Unrooting it did the trick, but that would suck if you have a really great setup built. Oh well... The price you pay for being a hacker I guess.
Click to expand...
Click to collapse
Google had problems with their servers, many services were unavailable... had most probably nothing to do with you rooting...
You just picked the right time to do that.
Google from time to time have some problems. But not related to rooting.
PAGOT said:
Google had problems with their servers, many services were unavailable... had most probably nothing to do with you rooting...
You just picked the right time to do that.
Google from time to time have some problems. But not related to rooting.
Click to expand...
Click to collapse
That's kind of what I thought, but it was miraculously healed when I unrooted it. It could have just been strange timing, but there was nothing on the web about anybody else having this issue. I'll root it again and see what happens. There are some definite advantages to root access that I don't want to lose, but getting my email and texts are pretty important too, so....
ocdetails said:
That's kind of what I thought, but it was miraculously healed when I unrooted it. It could have just been strange timing, but there was nothing on the web about anybody else having this issue. I'll root it again and see what happens. There are some definite advantages to root access that I don't want to lose, but getting my email and texts are pretty important too, so....
Click to expand...
Click to collapse
Seriously??? The web was full of it ...
read here for example http://techcrunch.com/2014/01/24/gm...mails-to-be-sent-to-one-mans-hotmail-account/
http://techcrunch.com/2014/01/24/gmail-goes-down-across-the-world/
PAGOT said:
Seriously??? The web was full of it ...
read here for example http://techcrunch.com/2014/01/24/gm...mails-to-be-sent-to-one-mans-hotmail-account/
http://techcrunch.com/2014/01/24/gmail-goes-down-across-the-world/
Click to expand...
Click to collapse
I'm talking about this past Saturday morning, though. February 1st. I know about the google issue a week or two ago, but this was only affecting my mobile apps and wasn't the same thing. I was able to access gmail on the computer just fine. I could even access it from the phone's browser fine, but connecting the Google account to the phone was not possible. All I kept getting was 'cannot make a reliable connection to the server' error, so that is why I took the phone back to stock and then all the way back to unrooted. Unrooting it solved it, so I don't think it was just a google server issue which only affected me between the hours of 7:30 on Friday night till Saturday afternoon when I finally gave up and unrooted. It could have been connected, but I doubt it.
Which rooting guide did you follow?
Sent from my LG-D802 using Tapatalk
ocdetails said:
I'm talking about this past Saturday morning, though. February 1st. I know about the google issue a week or two ago, but this was only affecting my mobile apps and wasn't the same thing. I was able to access gmail on the computer just fine. I could even access it from the phone's browser fine, but connecting the Google account to the phone was not possible. All I kept getting was 'cannot make a reliable connection to the server' error, so that is why I took the phone back to stock and then all the way back to unrooted. Unrooting it solved it, so I don't think it was just a google server issue which only affected me between the hours of 7:30 on Friday night till Saturday afternoon when I finally gave up and unrooted. It could have been connected, but I doubt it.
Click to expand...
Click to collapse
I'm having the same problem. I deleted my account and recreated it. But auto-sync does not work. This has nothing to do with syncing. That works - but I have to sync manually. If I manually sync it from either the app or from the accounts option in settings it works fine. But it won't sync again. I deleted the account, restarted the phone and added the account again. Still doesn't work. If you root it and run into the same problem, please post again. I'll unroot too then.
I know this used to work at some point. I don't know when it stopped working. But it's not been working for days now.
mrm43 said:
Which rooting guide did you follow?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I don't recall. The root part worked fine. I was able to use several of my apps which require root access and they all worked fine for a couple days. It just seems really random that this would all stop working one day.
So here is the timeline.....
Monday 1/27/14 - phone arrives
Wednesday - Rooted
Friday evening - Strange sync issues
Saturday morning - restored to stock while keeping root (did not solve problem and now I cannot connect any google account)
Saturday afternoon - unrooted and restored device (solved problem and google account synced fine after)
That was all in the same week. I've only had the phone since last Monday. It is worth saying that my HTC G2 and my wife's HTC G2 didn't have any issues with google syncing during this time. Totally different products, but I really tried to find anything to link the problem to something systemic and not just a device issue.
I haven't rooted it again just yet. I need to do it before I go too nuts re-installing the apks on my machine anyway. I'll definitely post again if I have problems again, but I really want to believe it was just something left over from whatever bug plagued Google a couple weeks ago.
I have the following issue with OK Google.
Originally it was fine, but now it is not working at all.
After trying two different clean installs (Pure Nexus, and then Chroma) with only Gapps, the phone will not even recognise the first of "Say 'OK Google' three times" when training the Voice command.
Yet if the microphone is activated in the Google search bar, it is perfect.
I've tried turning off noise cancellation, but to no avail.
I suspect that it's hardware related as this is not a common problem. Thank you
tpsnjs said:
I have the following issue with OK Google.
Originally it was fine, but now it is not working at all.
After trying two different clean installs (Pure Nexus, and then Chroma) with only Gapps, the phone will not even recognise the first of "Say 'OK Google' three times" when training the Voice command.
Yet if the microphone is activated in the Google search bar, it is perfect.
I've tried turning off noise cancellation, but to no avail.
I suspect that it's hardware related as this is not a common problem. Thank you
Click to expand...
Click to collapse
I had the same problem when I 1st set up the phone. Refused to recognise OK Googke command even in the setup screen. Fixed by switching search language from UK English to USA English. After successfully setting up I switched it back to UK and has worked fine ever since. I can see you live in New Zealand so same fix may work for you (obviously replacing UK with New Zealand).
levellerbob said:
I had the same problem when I 1st set up the phone. Refused to recognise OK Googke command even in the setup screen. Fixed by switching search language from UK English to USA English. After successfully setting up I switched it back to UK and has worked fine ever since. I can see you live in New Zealand so same fix may work for you (obviously replacing UK with New Zealand).
Click to expand...
Click to collapse
The language setting is on US English. On these latest ROMs you can get to the set-up screen only if the you're on US English.
Thanks for the try though!
As of today, I noticed that when I say "OK Google" or touch the microphone, I don't get the audible "beep" that tells me it's ok to start speaking?
Has anyone else noticed this?
I uninstalled the latest version and tried it and the beep work, but when I updated again to the latest version, Sept 14th release, it doesn't beep for me.
[UPDATE] As posted in reply #6, my sons S6 no longer beeps either.
I haven't had any issues with Google Now. Got my phone Monday and installed B27 update as soon I turned it on.
gumbyx84 said:
I haven't had any issues with Google Now. Got my phone Monday and installed B27 update as soon I turned it on.
Click to expand...
Click to collapse
Mine works, just doesn't beep?
tele_jas said:
Mine works, just doesn't beep?
Click to expand...
Click to collapse
Works for me. Odd
Mine no longer beeps either. I don't use Google Now often, but I sure do miss the "beep"! Anyone know of a fix?
My son's S6 no longer beeps either, so it's not just an Axon 7 thing... Also, Google search found several people with this issue and the latest update. I even installed the latest "beta" and there is no beep, but uninstall it and roll back to the previous version, the beep is there.
It's a Google thing.....But it doesn't seem to affect every phone?
I got a google update today 9/23, it still beeps, I am using action launcher and the google pill widget....but still hooks to the google app.
Is anyone else having an issue with Bixby voice to text? Where I completely disabled Bixby voice to text, but still leaving Google Voice to Text on. Then a few minutes later Bixby voice to text is turned on again, by itself, automatically. it overrides the Google voice to text, which I realized it when trying to use Google Voice to Text from the keyboard. It will end up opening Bixby voice to text, instead of Google voice to text.
I contacted Samsung about this twice. The first time, they never heard about this issue. Then the second time I called, they told me there is an issue with Bixby, but they don't know what to do to fix this and they don't know if and when a fix for Bixby is comming out.
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
mrb6208 said:
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
Click to expand...
Click to collapse
That's exactly what I'm doing. But every few minutes continuously it turns Bixby voice to text back on in the same OS settings. When I try to use Google voice to text every few minutes or so, Bixby voice to text comes up instead of Google voice to text. Then when I go to the same settings again Bixby voice to text magically is turned on by itself. This is a repetitive cycle every few minutes.
bigj0110 said:
That's exactly what I'm doing. But every few minutes continuously it turns Bixby voice to text back on in the same OS settings. When I try to use Google voice to text every few minutes or so, Bixby voice to text comes up instead of Google voice to text. Then when I go to the same settings again Bixby voice to text magically is turned on by itself. This is a repetitive cycle every few minutes.
Click to expand...
Click to collapse
When I changed the settings in language & inputs it kept doing what your describing but if your disabling Samsung voice to text there's no way it should be enabling itself. I have an s8 plus on T-Mobile and it works for me. I'd try to swap out your phone before it's been 14 days cuz Bixby sucks. Good luck!
9
mrb6208 said:
When I changed the settings in language & inputs it kept doing what your describing but if your disabling Samsung voice to text there's no way it should be enabling itself. I have an s8 plus on T-Mobile and it works for me. I'd try to swap out your phone before it's been 14 days cuz Bixby sucks. Good luck!
Click to expand...
Click to collapse
I'm on my 3rd device because of multiple bugs. I fixed every bug except the Bixby Voice to Text issue, and a Wi-Fi issue. Till the point, I'm unable to use my Wi-Fi. I made another post on this site about it.
At least for the Wi-Fi and, they want me to send them the phone and remain without the phone for at least 2 weeks minimum. They keep saying they never heard of this issue, except the one representative who got multiple calls about it personally. Samsung has done absolutely nothing for me. I've called Samsung the last 4 consecutive days. Every time I called them about those issues they don't tell me yes, no, maybe, I don't know. They simply just want me to send them the phone. Today though I was able to get somebody show me the wanted to use my phone to figure out the problem because they claim they never heard about this. Even though all over the internet people are talking about this comma and even one Samsung representative confirmed she personally dealt with it on the phone last week.
What's going on with my Wi-Fi is that it connect to any network, the transparent box shows up and everything letting me know that is connected. 10 seconds later the transparent box comes again and tells me that network has been disconnected. And it repeats that non stop. This also happened across the 3 devices I've had. I'm not the only one to have the Wi-Fi issue, a simple Google search of this would indicate that. Even customer of other carriers such as AT&T, Verizon and my carrier T-Mobile are complaining about this as well. Like when I talk to Samsung I'm talking to a brick wall. I'm honestly about to return the phone and ask for a complete refund if I don't get an answer other than sending my phone in!
Thank you soooo much!!!!
mrb6208 said:
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
Click to expand...
Click to collapse
This issue is still an ongoing issue for me. Every so often randomly, I would have to go into the settings like it's described here and turn off Bixby voice to text in the OS setting. For some reason Google Voice to Text can't seem to stay on without Bixby voice to text turning itself back on in the settings. Which then, even though Google voice to text is still on, Bixby voice to text overrides that, once it's turned on.
I reported this to Samsung like a month or 2 ago. All they want me to do is send in my phone, and remain without a phone for 2 weeks minimum(which I'm refusing to do). They claim there's nothing else they can do to help me, other than that.
I mean I'm getting upset, because I spend a lot of money on the device and I'm still having issues with this, and the Wi-Fi issue I stated above. Even after 3 exchange devices the same exact issues are occurring.
To bigj0110 - I can't thank you enough! I just got my S8 a couple days ago, and I hate the Samsung voice input. I couldn't figure out how to make it go away, and I thought I was stuck with it. Your suggestion worked! I'm so happy to have Google voice input back! You made me a very happy woman! Thanks! Jo Ann
Use Twiter
If you tweet using #Samsung or support they are quick to get back to you because they don't like the bad publicity on social media. I am having the same issues and think its time for everyone with a note 8 that is having issues demand a fix by blowing up twitter with bad publicity. What else can we do at this point?
I'm on my 3rd device because of multiple bugs. I fixed every bug except the Bixby Voice to Text issue, and a Wi-Fi issue. Till the point, I'm unable to use my Wi-Fi. I made another post on this site about it.
At least for the Wi-Fi and, they want me to send them the phone and remain without the phone for at least 2 weeks minimum. They keep saying they never heard of this issue, except the one representative who got multiple calls about it personally. Samsung has done absolutely nothing for me. I've called Samsung the last 4 consecutive days. Every time I called them about those issues they don't tell me yes, no, maybe, I don't know. They simply just want me to send them the phone. Today though I was able to get somebody show me the wanted to use my phone to figure out the problem because they claim they never heard about this. Even though all over the internet people are talking about this comma and even one Samsung representative confirmed she personally dealt with it on the phone last week.
What's going on with my Wi-Fi is that it connect to any network, the transparent box shows up and everything letting me know that is connected. 10 seconds later the transparent box comes again and tells me that network has been disconnected. And it repeats that non stop. This also happened across the 3 devices I've had. I'm not the only one to have the Wi-Fi issue, a simple Google search of this would indicate that. Even customer of other carriers such as AT&T, Verizon and my carrier T-Mobile are complaining about this as well. Like when I talk to Samsung I'm talking to a brick wall. I'm honestly about to return the phone and ask for a complete refund if I don't get an answer other than sending my phone in![/QUOTE]
mrb6208 said:
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
Click to expand...
Click to collapse
Thanks MrB. this saved me lots of aggravation. voice to text works much better now.
Can't disable Samsung voice, the disable button is grayed out.
on my note 8 for turning bixby off, this what i did and not sure if this is what you want....
settings
general management
language input
on screen key board
+ manage keyboards
then on "Samsung voice input" toggle off
>>>>>>>>>>>>>>>>>>>>>>>>>>
hit back arrow twice
>>>>>>>>>>>>>>>>>>>>>>>>>
text to speech
then touch the radio button on "Google Text_to_speech Engine"
>>>>>>>>>>>>>>>>>>>>>>>>
hit arrow back as much as you can then go to main screen, then try texting using voice.... for me, no more Bixby!!! YAY!!!!
I tried training Bixby but there was always a freeking probelm. I have patience, but this thing got to me.... bye Bixby.