Hi all
Had my watch nearly a year and every now and then the mute phone alerts and call feature stops working. I usually have to factory reset watch and delete android wear app on phone to fix the problem. However this time even thats not working?
I am running nexus 5 on marshmallow and had marshmallow a week and today its only just decided half way through day to stop working and all of a sudden my phone is sounding alerts.
anyone know a way to fix this?
Hi,
Recently I've started to experience call issues. During the call (not always) after some time (sometimes half miunte, sometimes 4 minutes, pretty random) audio is gone, we can't hear each other. After ending the call and calling other side again, there is some issue, call cannot be set up, i have to wait like 30sec/1 minute, and even after that audio is missing sometimes. My Note 5 is N920K, yesterday I've flashed latest official firmware (but there was DRK missing error), and flash Dr Ketan ROM after, and it didn't fix the problem.
Does anyone have any idea what could cause it? Is it hardware problem? If so, what i should change or how i can diagnose it?
So problem was with S8 port ROM
Hi all,
since i updated to android Pie i frequently noticed that y calls end abruptly. Sadly i did not notice any pattern so that i could narrow down the cause.
It does not matter if i initiate the call or if i am called. Also it seems that the carrier does not matter. Sometimes it required 5 attempts until i could finis a phone call. Other times it works normally.
I have no idea what to do, other than maybe a factory reset, again.
Thanks!
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.
Anyone else have delayed notification? Basically if I receive a text, it will be 15-30 minutes before my phone alerts me. When it does, it will correctly say received 15-30 minutes ago.
If I manually wake the phone after receiving a text (sent it to myself), the notification sound will play as soon as the device is woken.
The phone has to enter deep sleep, ie longer then ~5 minutes after putting the phone to sleep(screen off). It does it on wifi(w wifi calling) and mobile data.
I've been trying to google for answers and it seems some other people also have the problem.
moto forum
I personally am running LineageOS 16, with the FI version. I just updated to the latest firmware only for the FI, no change. (XT1900-1_PAYTON_FI_9.0_PPW29.69-39-2__A-B_FIRMWARE_ONLY)
I had this problem as well as other text related issues with various ROMs in the past.
Only solution I found was using stock and taking advantage of Magisk and root to modify my phone.
I thought it was problems with Project FI at first.