I've been having this problem for a while (Android 7.1.2 and now 8.0). I will try to video call my wife using either Google Duo (Pixel to iPhone) or Facebook Messenger. We used to have the problem that calls could be initiated, but as soon as the other answered, it would hang up. We still have this problem except now the app doesn't even wait for us to answer, it just hangs up after a single ring or so. It's almost immediate.
I tried asking Google for help using the support option on the phone but they were less than helpful. The situation and the lack of support have made me mad enough to want to ditch the phone and get an iPhone (which I typically curse - I hate everything Apple but at least I could finally be compatible with the rest of my family).
Anyone had this problem before? How can I troubleshoot to resolve?
street9009 said:
I've been having this problem for a while (Android 7.1.2 and now 8.0). I will try to video call my wife using either Google Duo (Pixel to iPhone) or Facebook Messenger. We used to have the problem that calls could be initiated, but as soon as the other answered, it would hang up. We still have this problem except now the app doesn't even wait for us to answer, it just hangs up after a single ring or so. It's almost immediate.
I tried asking Google for help using the support option on the phone but they were less than helpful. The situation and the lack of support have made me mad enough to want to ditch the phone and get an iPhone (which I typically curse - I hate everything Apple but at least I could finally be compatible with the rest of my family).
Anyone had this problem before? How can I troubleshoot to resolve?
Click to expand...
Click to collapse
Are you using a smartwatch? It's a known problem with them, if you disable the phone audio profile for them, it should work.....I had the same issue too
Related
Hello al! I was wondering if any of you have this problem....
Friends show offline after some time using Gtalk or when switching from Wi-Fi to Mobile Data
I have to sign out and sign in again...
Anyone else has this issue?
I have the same issue, and it's pretty annoying. Don't know how to fix it
It's funny how there is no fix. Most probably its because many people use other chat clients.
Sent from my Desire HD using XDA App
I would think GTalk is quite popular. Anyway I have been having this same issue, and it's really annoying!
It seems the problem is present on multiple devices, so it's likely to be related to Google Talk itself. In order to maximize the efforts to find a solution it's better if we focus on one topic only. The following one seems to have the greater number of replies so far:
Google Talk issue - after a few minutes Contacts are all offline when not
Sorry to necro, but it's either that or starting a new thread on this.
I have this issue myself on my Galaxy Nexus GSM.
It happens very regularly, and regardless of ROM/kernel. I've had various configurations and this issue has never ceased. I hoped Jelly Bean would finally fix it, but it hasn't.
I have tried everything under the sun. Clearing data, cache, etc. - I can't work it out. It seems like a server issue, yet I never had this problem on my previous Android (2.1, Galaxy Spica) and my friend (Desire Z) never has this problem, nor does my girlfriend on her Galaxy Note (with the same Gtalk version)
It boggles the mind.
Every so often, everyone just shows as offline, when they're not.
This happens on 3G and WiFi and doesn't seem to be an issue with handoff either. Sometimes I can rectify it by signing out/in, or simply by sending a message... but other times, that doesn't make a difference either.
Why does this happen??
On top of all this, Google Talk seems to have a lot of issues recently with delivering messages on time - to the point that my friend won't get the message (or I won't get theirs), and messages often appear out of order.
Has Gtalk just gone down the pan? It's weird, because we never seem to have any issues when both parties use it in Gmail on the PC.
Hey fellow wp7 lovers.
Lately ive been using a lot of messaging on whatsapp. I can chat fine on 3G but whenever i switched over to wifi... the message either gets stuck on delivering (1 line) ... or simply just shows the clock (not delivered)
Solution was always to switch 3G back on or turn on/off the wifi...
Its becoming quite tedious really...
Is anyone else experiencing this issue?? Or anyone know of a better solution?
(dont really want to use my 3G lately as its closely approaching my limit)
Got exactly the same issue. Don't know where i'm talking about really, but recently the thought hit me that maybe it is because when you come out of stand-by mode and send a message seconds later, your phone wants to send it over WI-FI, which might not be possible yet since it's still trying to connect, which then maybe results in a message not able to be sent and ends up being stuck on your phone, even though your phone connects to WI-FI succesfully after a while.
I usually turn off 3g, open the app, en most of the times it helps, which doesn't make sense at all. I am not sure, anyway. Haven't paid too much attention to it. Sometimes I just know its the WhatssAppserver, but I can't tell every time, and that makes it difficult to research the exact cause.
I really hope whatsapp releases an update and irons out its issues. Whatsapp on WP7 sucks.
It isn't that bad! It works, and thats more then we had. However, I don't understand why they can't manage to get simple things right...
hm i wonder if this is design flaw.. or purely just to save battery...
Coz on the android whatsapp, the internet is always connected even when on locked screen but on wp7 its not! The only solution is to use 3G!
This makes whatsapp useless if you only have wifi available... >< so much for instant messaging
Later on i found out ur wifi STAYS connected (even when in lock screen) when you plug it in to charge.... so thats the only workaround
so can we petition microsoft to add wifi on all the time in the next update??
OR does anyone know of an app that always require wifi connection?
(as described in this thread - http://forums.wpcentral.com/windows-phone-7-os-discussion/179861.htm)
Hm another quick note.....
how come whatsapp on ANDROID is so frickin fast!!!!! On iphone it takes about 5s to load into it. WP7 about 7s....and ANDROID is INSTANT!!!!
Lol is WP7 and APPLE so closed off that we cannot integrate whatsapp more into the OS? bah
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
Hey I have searched the forum and so far I have yet to find a solution to my problem. I have the Droid RAZR Maxx HD running on Jellybean. I am not sure if the problem was present before I upgraded to Jellybean.
I don't use video chat very often, but sometimes it comes in handy. Especially handy when you're troubleshooting something remotely. Ok I have tried Tango, Skype, Fring, ooVoo, Google Talk video, and Facebook video. Each one of them seem to do something different. Tango will dial the other person up and start my camera, but it will never let us connect. When I attempt to hang up a Tango call all it does is turn the green light off under the video camera icon, and the video camera stays on. I have to press the home button and force close the app. Skype will just force close if I attempt a video call as will Google+. The ooVoo app allows the video to work fine on both ends but we have zero audio and I've been unsuccessful finding anything in settings to change that. The Fring app let's the other person see me (they were on a Samsung Galaxy Note II), and we can hear each other. I can only see my own camera on my screen, though. So far ooVoo and Fring seem to be the closest to being working apps for me, but they still are not functional enough to be of any use. I contacted Verizon about this on the phone twice and visited the store once. The guy on the phone this morning said that it was likely something with the jellybean upgrade. The guy at the store last night said his works fine with the same kind of phone, but I'm not sure about that personally because I never saw him get it to work. The only phone he tried to initiate a video call with was mine. I'd really appreciate it if someone could help me figure out how to get around this. By the way, I also tried clearing the cache and the data for Tango and uninstalling, installed an older version of Tango from Google, but that only force closed. Please let me know if you need more information to help solve this issue, and thanks in advance.
Anyone ? ? ?
Sent from my DROID RAZR HD
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders