Related
Hi everyone,
I have had the Moto G 2nd Gen for about 10 days now and I have noticed that notifications from several apps (Exchange email, Gmail, Whatspp, Facebook...) are either delayed by a few hours or don't come at all. This happens on both Wifi or my network. Has anyone else experienced this ?
I have tried the following with no success:
1- disable Wifi optimization
2- factory reset phone
3- Installed PNF No-Root and set hearbeat to 5min
4- Cleared data & cache of apps
My phone is not rooted running 4.4.4
Thanks
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
I have tried 1, 2 and 4 of your attempts to fix it to no avail.
Before I reset the phone all notifications showed the correct time that they should have come, for example if I slept the phone at 10:40 and a notification came at 10:44, I then woke the phone at 10:50 the phone would immediately buzz and sound but it would say the notification came at 10:44 in the notification draw.
However after the factory reset of the device in the same situation the notification draw would show 10:50 but I know that is wrong because WhatsApp for instance will say the correct 10:44 timestamp on the message in the app.
Notifications when the phone is awake come through perfectly every time.
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Mine is the same as yours XT1068 8GB Dual SIM Retail GB 21.11.14.titan_retgb.retbgall.en.GB retgb.
I also have the same problem with music, I also noticed this with chromecast, it seems to loose connection after playing one track.
I contacted Motorola assist and they said replace the phone. I'm not sure if replacing it will solve the problem, I'm guessing this is a software issue. I
I got it from Amazon UK, I'm thinking of returning this and going back to my Galaxy Nexus and wait for the new Nexus phone.
Because we have the same software version I more strongly suspect this is a software issue now, I'm not sure what to do, I don't really want to return the phone as I will be left phoneless and a replacement would just come with the same software.
Another option would be to re flash to a different software version (an international version) but that will invalidate the warranty.
Not really sure what to do, would be good hearing if any retGB people are not having any problems, if any are reading this thread? or if any non retGB are having this problem.
jay2the1 said:
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
[...]
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Click to expand...
Click to collapse
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
bhavin192 said:
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
Click to expand...
Click to collapse
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Been testing on 3G, after the phone is slept all notifications work perfectly for 10 minutes with the phone buzzing a second or 2 after my tablet, if you sleep the phone and send a message after 10 minutes the phone will only buzz after 30 minutes from being slept (ie the heartbeat).
I've reinstalled PNF app and will experiment more tomorrow, still not sure how I will fix WiFi but I think a little more experimentation is required (yet doesn't make sense why my tablet always works 100% and the phone doesn't when using the same router)
jay2the1 said:
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Click to expand...
Click to collapse
I agree with you that it has something to do with phone going to sleep. My WiFi router is Netgear. I have they same problem with every other WiFi network and also on 3G. I didnt have this problem on my previous phone Galaxy Nexus.
PNF doesnt seem to work at all.
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
anshumandash said:
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
Click to expand...
Click to collapse
I have posted this on the Motoral forums here https://forums.motorola.com/posts/dbb4806484
I have been experimenting again today, the problem is significantly worse on WiFi notifications are much slower than on 3G, the problem seems completely unreplicable, sometimes notifications come though aOK even after I have left the device sleeping for an hour (using WiFi) or sometimes the notification will be delayed for several minutes even if it has only just been slept (again using WiFi), 3G on the other hand there is a definite 10 minute cut off from sleeping the device.
I've had PNF installed since last night and it doesn't help WiFi at all, but 3G it might, I say might because sometimes after 10 minutes (even an hour later) if I send a notification I do receive it straight away (something that never happened before I installed PNF) but then sometimes it doesn't and it's delayed for several minutes again.
I will join the Moto forum and add my weight to that when I get back to my computer as you need to sign in with a Google account.
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
jay2the1 said:
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
Click to expand...
Click to collapse
I have also noticed that. It seems that many are having this issue, so far no reply from Motorola
Motorola might be investigating about it. Yesterday i went back to dalvik from art. I tested the notifications the while day. On Wi-Fi, i didn't see the delays any more. In 3g many tests were successful even after 1hr of deep sleep. Only at 4pm India time i found a delay of 22 mins for whatsapp notification. There i also realized that it had switched to 2g due to bad signal in that room. I was definitely having problem when i was on art. Last night i also got the ota for build 23. I see that the kernel is updated. I will monitor one more day and report here.
Motorola has at least seen the post even with no reply, I just hope they are busy behind the scenes working out what is wrong so they can fix it.
I've never used ART (I'm completely stock), and all the problems are still happening today, unfortunately Telegram is being DDoS'd today so haven't been able to test anything out.
It will be interesting to hear if the update you received helps in any way, esp with the updated kernel, since your retGB device received it hopefully ours may do soon too.
As far as I can tell it doesn't affect calls and SMS, but I simply don't use SMS or calls at all (WhatsApp ftw) so my testing has been the odd 'prank' phone call from my 2nd phone and it rings every time, but it's not enough to confirm if it's a fluke or if in fact it does not affect phone calls/SMS.
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
That's good news, hopefully the update has indeed fixed it, there's no indication when the update will hit the UK but if it does fix it then ASAP I hope.
anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
katkat911 said:
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
Click to expand...
Click to collapse
In a different thread Motorola amin had mentioned that they are investigating the notification delay issue. I don't see much delays after the update. There are few mins here and there, but mostly good. If you haven't received the update yet, check the ota thread and update manually. It's the same update. Then see if you find any improvement.
I got the OTA update yesterday and I'm still having the same issues
Just FYI, this seems to be a big bug in Verizon Visual Voicemail app for a long time now (even the same issue on my Sony Xperia Z3v just before this device).
Anytime I start playing the voicemail and soon as I bring it to my ear, it locks the device and stops playing the voicemail message I am listening to. I have checked every setting I can think of and I think this is a big bug in the app.
If anyone knows a fix or workaround for this issue please do let us know.
UPDATE: Workaround found - http://forum.xda-developers.com/showpost.php?p=60386275&postcount=3
open1your1eyes0 said:
Just FYI, this seems to be a big bug in Verizon Visual Voicemail app for a long time now (even the same issue on my Sony Xperia Z3v just before this device).
Anytime I start playing the voicemail and soon as I bring it to my ear, it locks the device and stops playing the voicemail message I am listening to. I have checked every setting I can think of and I think this is a big bug in the app.
If anyone knows a fix or workaround for this issue please do let us know
Click to expand...
Click to collapse
Works just fine on my phone just tried it, no locking and no stop playing when holding up to my ear same thing on my note 4.
dansto82 said:
Works just fine on my phone just tried it, no locking and no stop playing when holding up to my ear same thing on my note 4.
Click to expand...
Click to collapse
I figured out how the issue works but confirmed for sure it's a bug with the application.
If you go into your lock-screen security settings, I usually set mine to lock immediately on screen-off (I guess the default is some 30 seconds or so). If I change the screen-off lock timeout to 30 seconds or something then the screen goes off but the voicemail still plays since it's not locking the device. However if the voicemail ends up being longer than 30 seconds then of course at the 30-second mark it will lock and stop playing.
This seems to be the workaround but the issue is still there and can be considered a security issue if you need to have your lock timeout set longer just to be able to hear voicemails playing on the lockscreen once you already started them. Regular media still plays if you lock the device so there's no reason why the voicemail app shouldn't.
If anyone has any other details about this it would be much appreciated. This is for sure specific to Verizon's Visual Voice Mail app not allowing to stay running on the lockscreen.
I submitted a ticket with Verizon's IT team explaining all these details and and they said they will get back to me shortly.
Yeah i have my screen time out at 1 or 2 mins right now and trusted device unlock when i'm wearing my Moto360.
Changing my lock screen settings didn't work. Has anyone else found another resolution to this?
open1your1eyes0 said:
Just FYI, this seems to be a big bug in Verizon Visual Voicemail app for a long time now (even the same issue on my Sony Xperia Z3v just before this device).
Anytime I start playing the voicemail and soon as I bring it to my ear, it locks the device and stops playing the voicemail message I am listening to. I have checked every setting I can think of and I think this is a big bug in the app.
If anyone knows a fix or workaround for this issue please do let us know.
UPDATE: Workaround found - http://forum.xda-developers.com/showpost.php?p=60386275&postcount=3
Click to expand...
Click to collapse
I'm really stumped here. I haven't been able to find any solution to this issue through searching, so I figure I might as well post something about it.
For the past few months, I've been having an issue with my watch screen turning itself on then dimming after a few seconds. This seems to occur every few minutes or so even when theater mode is enabled and when always on screen and wrist gestures are disabled. This issue persists even after unpairing with my LG G4 and after a factory reset (on both the watch and phone). It should also be worth noting that I have recently rolled my phone back from the latest VZW Marshmallow OTA to a rooted 5.1 image in an attempt to resolve the aforementioned problem, but from what I can tell, it has only become worse.
From what I've been able to gather from battery/wakelock monitoring apps and bug reports is that the phone is regularly sending wake requests at semi-regular intervals. I have not installed any third-party wear apps and I've disabled pretty much every Google sync function but the problem persists.
I am at wits end here as to what I can do here. This coupled with my phone suddenly developing a severe wakelock problem has made me seriously consider switching to another manufacturer, and this time I may not exclude Apple as a choice.
Has anyone else experienced an issue like this that might have some insight as to what's going on?
Thanks!
PS: If needed, I can provide the full bug report along with a quick spreadsheet I made to organize the kernel wake source info found in the report.
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
I'm unsure which thread is the most appropriate to post this in, so I'll throw it here.
I don't believe the entire issue is tied to 7.1.1. I believe it originated in 7.1.0 or earlier, but got worse in 7.1.1. (Side note, I did on occasion get a "Bluetooth Share has stopped" notification, but only if I was actively using the phone).
My phone's bluetooth began "cycling" at the very latest in 7.1.0. I first noticed the issue when using an app called "wear aware," an app designed to let you know if you leave your phone behind (on your android wear watch). It was frequently giving me "false positives," so I ultimately uninstalled the app. I also began to have issues with android auto, where it would occasionally freeze and stop showing me data. Likewise, when I'd be on a phone call, my radio would randomly turn on and I'd assume the call got disconnected -- until I realized the other party was still on the line but now on speaker phone.
The reason I believe it got worse in 7.1.1 is because it used to cycle bluetooth. At least when it crashed, it restarted. Now it appears to require intervention to re-enable it. As a temporary work-around, I have Trigger set up to enable bluetooth if it gets disconnected from my watch. It doesn't work 100% of the time, but at least it re-enables bluetooth frequently for me (it claims to have run 10 times in the last 2 hours).
It's probably also worth noting that it's been reported on at least the Nexus 6 and the Pixel, from what I've seen.
My current setup:
PureNexus (1/21 release, rooted)
Franco Kernel
Huawei Watch
Prior to this, I was running Stock, unrooted, with the same issues.
Thanks for the workaround (Trigger) - like the speakerphone issue we are experiencing, it might not be an official fix but it works for now. It seems like the more updates we get, the more bugs we get. Seriously, 6.0.1 was about perfect, and I might flash back to that and add the additional Nougat features via xposed.
Post deleted
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Fvolfrine said:
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Click to expand...
Click to collapse
Anyone try to revert to an earlier dialer app or is it in the framework of the Feb patch?
I don't think it's the phone app. I get Bluetooth share disconnects with just a Pebble smartwatch.
As is stated in the second article, this issue is not related to the phone dialer app. I'll delete that post as it might cause some confusiom
Sent from my Nexus 6 using Tapatalk
I thought my phone was dying. I'm having this issue as well. I found that uninstalling Heart Trace, which records my heart rate every 15 minutes from my Huawei Watch, helped a lot with the Bluetooth issue.
It used to be that my Bluetooth would turn off in the middle of the night and I lose my sleep tracking data from my watch (Sleep as Android).
Don't google test their sofware?
This is a poor show by them.
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
But how often do you have to keep doing this?
Fvolfrine said:
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
Click to expand...
Click to collapse
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
danman7 said:
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
Click to expand...
Click to collapse
What is the 2/15 update?
@home said:
What is the 2/15 update?
Click to expand...
Click to collapse
PureNexus ROM. And I'm glad to hear that it resolved this issue, might be time to flashback over from stock.
On a side note, the one thing that I feel stock is missing, and this is minor, is a battery percentage that is not in the icon. Google has added just about everything I wanted to stock except for this one small detail, and yet I'm going to flash over because of it.
Sent from my Nexus 6 using Tapatalk
I'm on stock firmware and Project Fi on Nexus 6 and been having this problem lately yet I have had no updates since the Oct 5 2016 security update on Android v7.0. I wear a fitbit Charge 2 and occasionally use either a bluetooth headset or my car's bluetooth audio. I try real hard to keep my battery charge above 40% at all times. Normally I'm at 70% or higher when these problems occur. [edited to add] Forgot we also have a few Tiles and a LugLoc.
When not using bluetooth at all I frequently find bluetooth has disabled itself on my phone.
When using the bluetooth headset during a phone call bluetooth shuts off and my headset reports it has lost a connection to my phone.
In my car bluetooth is flawless and never shuts down even on long drives 2-4 hours.
I have also enabled trusted devices in Security when certain devices are connected via bluetooth.
Sometimes bluetooth settings loses a device. Sometimes they come back on their own but more often than not I have to repair the device to the phone.
Right now there are so many issues with this phone (including dust in the camera sensor) that makes it real frustrating as an owner.
@home said:
But how often do you have to keep doing this?
Click to expand...
Click to collapse
Only had to do it once
semsem_605 said:
Only had to do it once
Click to expand...
Click to collapse
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Fvolfrine said:
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
Click to expand...
Click to collapse
I tried this earlier today. Made it through two one hour conference calls with only one hiccup between the bluetooth headphones and the phone which did reconnect. No disabled bluetooth yet. I hope this is the fix!
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Are you on 7.0 or 7.1.1 & also which security patch?
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.