Hello, I have a Gear S3 Classic BT with a Oneplus 3 (LineageOs, last nightly).
Everything works except for making/receiving calls, it just says something like "check device" when I rotate the bezel to accept a call and does nothing when I try to start a new one.
Is there a way to fix it?
For OP3 users on OOS: does it all work with stock rom?
I had exact same problem.I was using Lg g2 with custom cm 14 rom, when i tried to call someone or answering incoming calls gear just says "check device" and nothing happens.I tried many things but none of them have worked.Solution for me is going back to stock based rom.
Gone back to OOS, calls work. Not fine (bluetooth connection issues, it disconnects randomly), but at least it works.
Related
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
I know it is only an alpha build ICS but this thing rocks. The smoothest ROM I have installed on my g2x. Except for wi-fi calling issues. W-fi calling initiates, can make/receive call but the moment you answer call, other end can't hear and you can't hear the other end and then it crashes. I tried everything already I know under the sun. Re-installed ROM, installed and re-installed different versions of ICS gapps, dalvik wipe, and everything. Just need it at work. I work in a place where every carrier has no signal, so wi-fi calling is awesome. Anybody has same problem with me and found a solution?
I've noticed a reboot or plane mode on/off will randomly fix it. It seems kind of hit-or-miss at this point.
I have the same issue except I haven't been able to make/receive a single call successfully. Admittedly I haven't tried airplane mode or rebooting after the first fail.
I've tried debugging it a bit and there's some strange messages in GANRIL -- there's a bunch of modem commands then suddenly NO CARRIER after some unsolicited command, then the whole thing seems to fail.
There's also some error that happens in the audio lib possibly pointing to a failed hand-off, but maybe that's a red herring.
I've tried a bunch of different versions I've found searching for a solution including one I packaged myself with some experimental build props and the .so and APK files from CM7.2. No success so far.
I kind of want to start a bounty for this -- Wifi Calling is very important for me. TMO signal sucks in my apartment that it's practically unusable even with a zBoost Wi-Ex running in here. In some places like Las Vegas the signal was so bad that I ended up using a Verizon MiFi card + Wifi calling =P
ICS is so cool though that even given all that, not having it is not a total deal breaker for me, just an annoyance.
I also have problems with wifi calling on HFS v1.2. It will connect and I can answer it. However, once I answer I can't hear the other side and they can't hear me and then it appears as if the other side calls again and all I can do is ignore the call.
Yeah, I managed to get this far now -- can sometimes make calls, can receive all calls but audio does not route on received calls. Then it goes into a bad state and requires a reboot for it to work again.
It seems ICS + Wifi Calling works, there's just bugs to iron out ...
Hephzibah said:
I also have problems with wifi calling on HFS v1.2. It will connect and I can answer it. However, once I answer I can't hear the other side and they can't hear me and then it appears as if the other side calls again and all I can do is ignore the call.
Click to expand...
Click to collapse
This happens only on outgoing calls on bluetooth (car audio): I can hear the person on other side talking, but that person cannot hear me. I switchover to handset or speakerphone and switch back to bluetooth, and the problem goes away. Both parties can hear each other and call proceeds without a problem.
This problem does not occur on incoming calls at all. I pick up using the button on car audio and the conversation happens without an issue.
The exact same issue occurs on all the builds I have tried: CM10.1 (both stable and nightly), Slimrom 4.2, Slimrom 4.3 nightly, Aditya's CM11 (tried at least 3 builds, currently running his build 12).
I did not see any mention of this by anybody else. Am I alone in facing this issue?
I have used both an android phone and a windows phone earlier on this car audio and this issue did not show up on those.
Thanks, folks. I would really love to fix this and continue to use this wonderful phone for a few more years!
It gets crazier
I just got my hands on a Sprint Galaxy Nexus (toroplus):
Weird: This exact issue (bluetooth outgoing call does not grab my side of the conversation until I switch the call to speaker/handset and back to bluetooth) happens on all the builds of CM10.2, CM11 and Slimkat.
Weirder: This DOES NOT happen on 4.3 stock rom (JWR67B) version of the software. I am unable to try and load stock rom to NS4G, so haven't tried this trick with that.
Weirdest: Now that I have isolated the problem to the CM (or its derivates in slim version), how is it even POSSIBLE that I am the only one experiencing this? I cannot find any mention of this issue anywhere in the net. Unfortunately, both my bluetooth receivers are the exact same model: pioneer DEH-4500BT. However, the fact that Galaxy nexus stock rom (and earlier phones, like Samsung Prevail or Lumia 521) work flawlessly deflects any suspicition on the DEH-4500BT's part.
hi,
i recently got a gear s3 classic, wifi and bt edition.
whenever i want to make a call from the watch its just erasing the numbers and doing nothing. also when im trying to call a contact, it's freezin for a few seconds and after its doing nothing. when i receive a call i can just decline it but not accept it. my bluetooth seems proberly connected, im getting notifications and similiar thing, also the gear app says im connected. using it with a oneplus2 on RR, android 7.1.2.
i hope someone got fix for this.
iLucas said:
hi,
i recently got a gear s3 classic, wifi and bt edition.
whenever i want to make a call from the watch its just erasing the numbers and doing nothing. also when im trying to call a contact, it's freezin for a few seconds and after its doing nothing. when i receive a call i can just decline it but not accept it. my bluetooth seems proberly connected, im getting notifications and similiar thing, also the gear app says im connected. using it with a oneplus2 on RR, android 7.1.2.
i hope someone got fix for this.
Click to expand...
Click to collapse
Do you have other devices paired to your phone? If so, you might experiment by UNpairing other devices (headphones, bt speakers, whatever) and then try again.
I've seen my go both ways. But I prefer it paired with my car so have tried to limit the bt pairing between my phone and the watch to notices and some data updates but NOT voice.
fred2546 said:
Do you have other devices paired to your phone? If so, you might experiment by UNpairing other devices (headphones, bt speakers, whatever) and then try again.
I've seen my go both ways. But I prefer it paired with my car so have tried to limit the bt pairing between my phone and the watch to notices and some data updates but NOT voice.
Click to expand...
Click to collapse
thanks for your answer. i've tried this, doesn't work. i've also reseted my watch already and reinstall all the samsung stuff. not working at all.
ive fixed the problem so far. its caused by the rom, if i use the oxygenos it's working
I can confirm that there are a few custom roms (7.1.2) which supports the calling functionality in OP2.
You don't really have to move back to the stock Oxygen OS. :good:
PureNexus
HalogenOS
AICP etc..
Hey guys!
I'm having troubles with not receiving incoming calls from certain people. No ringing, no notification, nothing in call history on my side. The other side can initiate the call, and it rings too, but nothing on my side. I can still call them and receive sms from them. I have no idea why or what causes the problem, nor if this phone/software or service provider issue. I tried the obvious reboot several times and switching the sim to the other slot, didn't work. Remaining options are wiping everything and do a full software update from scratch and talk to the service provider if the previous won't work.
I was wondering if anyone ever had an issue like this? Maybe on another phone? All people who can't call me now, could reach me before this started.
I have 64 GB op6 with Android 10 stock.
Same problem here
There are no signs of a call from certain numbers, even though the other side gets a ringing tone.
I am on OP6 latest stable oxygen os 10.3.2
Did you fix it? Anyone else having this issue?
I have the exact same problem on my OnePlus 6T on Oxygen OS 10.3.2 ? Please help
hey, did you guys manage to solve this issue? i have tried my sim in another phone and it works flawlessly, perform a full wipe (clean flash from RR Android 10 to EvoX Android 11), so wiping data does not help, neither wiping all the phone cache... please help!!