The very first Android phone I purchased was in 2010, and it was an HTC Desire. I have been a huge fan of Android ever since, owning literally hundreds of phones and tablets from various manufacturers such as Samsung, Huawei, Motorola, Xiaomi, LG, Sony....the list goes on and on. I've tried iOS a few times, but I simply just didn't like iOS. In recent years my loyalty to Android was severely tested because of an issue that many may think is inconsequential and even petty, but to me it was ultimately a deal-breaker - delayed push notifications (predominantly when the screen is locked and off)
So picture this - I'm sat at home with three other members of my family who also own Android phones, and we have a group chat (FB Messenger) going with other members of the family. Every time someone posts a comment *PING*...but wait, four android phones, and only two went *PING*...then a few seconds later another goes *PING*, then a few seconds later the fourth goes *PING*.
I'm not exactly sure when this issue first arose, but I only really started to notice around the time Oreo was mainstream, and I've been obsessed with trying to figure out a cure ever since. Of course I've tried literally everything that's been suggested, hard resets, turning off battery optimisations, locking the affected app in the recents, disabling Doze with ADB, clearing the cache, custom roms, different routers, different networks, heartbeat fixing apps for GCM/FCM, bla bla bla...none of it works. Now I have finally accepted there is a flaw in the way the Android OS handles push notifications, a flaw that affects every single Android device, at least since Oreo, and maybe even before. It's a strange one because the issue doesn't seem to occur when the screen is awake, only when it is locked and off. At one stage I was hopeful features like AOD on AMOLED devices might be a solution, but alas, even with AOD active, the problem persists.
Now before you say "I've never had a problem with push notifications on my Android device", are you sure. Have you ever really been in a situation where you would notice? Try it for yourself, perform a test using a similar scenario to the one I mentioned in the second paragraph. Create a group chat in any messaging app you like, and have several of the group members with Android devices sit in the same room with their screens locked and off, then have one person send a message in the group chat, then watch as some get the messages immediately, some with a slight delay, and some not at all until they wake the screen. Do it a few times and you will soon notice there is no pattern at all, sometimes you will get the notifications immediately while others are delayed, then sometimes others will get the notifications immediately and yours will be delayed.
My most recent (and very last) Android purchase was the Samsung Galaxy S21 Ultra 5G (outright, not on contract, so you know roughly how much I paid). When I'm paying that amount of money for a mobile phone, I expect timely push notifications as a given, but no, the same issue occurs even with one of the very latest and greatest. I contacted Samsung Tech Support and the guy admitted it's the most common complaint he deals with every single day. I was previously given a similar story by Motorola and Huawei support too, and a little digging around online shows that thousands of Android users are complaining about the very same issue. Needless to say they now have that phone back.
I know I know, something this trivial shouldn't really bother me this much, but it does, it's just who I am. I can accept there is no such thing as a perfect mobile phone, I can live with an average camera, a budget processor, a dull screen, lifeless aesthetics etc. but there are some compromises I just won't make. Apart from the obvious (the ability to make and receive calls and texts), my requirements are quite simple - I require a phone with stable WiFi, Bluetooth and NFC, a decent battery life and of course timely push notifications. With no Android device currently able to fulfil my very simple requirements, it really did only leave me with one option - joining the dark side....so I bought an iPhone.
I have owned an iPhone for just over a month (that's two weeks longer than my last three Android devices), and thus far my delayed push notification woes have vanished. Now when someone in the family posts in our group, *PING* immediately every single time. The battery life is acceptable for someone like me who isn't the most demanding user, WiFi, Bluetooth and NFC have presented no issues, and it makes and receives calls and texts without a problem. I can honestly say the only thing I miss so far is my Android App Drawer. I know iOS introduced their App Library in iOS 14, and it's a start, but it's just not the same. There is probably an app in Cydia that would give me an app drawer, but I'm not quite ready to get into the world of jailbreaking just yet (I'm not that brave).
So after my big rant, here's a summary - Android push notifications are broken, they've been broken for some time and Google don't seem interested in fixing the problem. If someone told me tomorrow that Google had finally fixed push notifications, I would drop iOS like a hot potato and rekindle my love for Android. Please Google, help bring me back from the dark side, it's really cold out here!
Des
energy6uk said:
The very first Android phone I purchased was in 2010, and it was an HTC Desire. I have been a huge fan of Android ever since, owning literally hundreds of phones and tablets from various manufacturers such as Samsung, Huawei, Motorola, Xiaomi, LG, Sony....the list goes on and on. I've tried iOS a few times, but I simply just didn't like iOS. In recent years my loyalty to Android was severely tested because of an issue that many may think is inconsequential and even petty, but to me it was ultimately a deal-breaker - delayed push notifications (predominantly when the screen is locked and off)
So picture this - I'm sat at home with three other members of my family who also own Android phones, and we have a group chat (FB Messenger) going with other members of the family. Every time someone posts a comment *PING*...but wait, four android phones, and only two went *PING*...then a few seconds later another goes *PING*, then a few seconds later the fourth goes *PING*.
I'm not exactly sure when this issue first arose, but I only really started to notice around the time Oreo was mainstream, and I've been obsessed with trying to figure out a cure ever since. Of course I've tried literally everything that's been suggested, hard resets, turning off battery optimisations, locking the affected app in the recents, disabling Doze with ADB, clearing the cache, custom roms, different routers, different networks, heartbeat fixing apps for GCM/FCM, bla bla bla...none of it works. Now I have finally accepted there is a flaw in the way the Android OS handles push notifications, a flaw that affects every single Android device, at least since Oreo, and maybe even before. It's a strange one because the issue doesn't seem to occur when the screen is awake, only when it is locked and off. At one stage I was hopeful features like AOD on AMOLED devices might be a solution, but alas, even with AOD active, the problem persists.
Now before you say "I've never had a problem with push notifications on my Android device", are you sure. Have you ever really been in a situation where you would notice? Try it for yourself, perform a test using a similar scenario to the one I mentioned in the second paragraph. Create a group chat in any messaging app you like, and have several of the group members with Android devices sit in the same room with their screens locked and off, then have one person send a message in the group chat, then watch as some get the messages immediately, some with a slight delay, and some not at all until they wake the screen. Do it a few times and you will soon notice there is no pattern at all, sometimes you will get the notifications immediately while others are delayed, then sometimes others will get the notifications immediately and yours will be delayed.
My most recent (and very last) Android purchase was the Samsung Galaxy S21 Ultra 5G (outright, not on contract, so you know roughly how much I paid). When I'm paying that amount of money for a mobile phone, I expect timely push notifications as a given, but no, the same issue occurs even with one of the very latest and greatest. I contacted Samsung Tech Support and the guy admitted it's the most common complaint he deals with every single day. I was previously given a similar story by Motorola and Huawei support too, and a little digging around online shows that thousands of Android users are complaining about the very same issue. Needless to say they now have that phone back.
I know I know, something this trivial shouldn't really bother me this much, but it does, it's just who I am. I can accept there is no such thing as a perfect mobile phone, I can live with an average camera, a budget processor, a dull screen, lifeless aesthetics etc. but there are some compromises I just won't make. Apart from the obvious (the ability to make and receive calls and texts), my requirements are quite simple - I require a phone with stable WiFi, Bluetooth and NFC, a decent battery life and of course timely push notifications. With no Android device currently able to fulfil my very simple requirements, it really did only leave me with one option - joining the dark side....so I bought an iPhone.
I have owned an iPhone for just over a month (that's two weeks longer than my last three Android devices), and thus far my delayed push notification woes have vanished. Now when someone in the family posts in our group, *PING* immediately every single time. The battery life is acceptable for someone like me who isn't the most demanding user, WiFi, Bluetooth and NFC have presented no issues, and it makes and receives calls and texts without a problem. I can honestly say the only thing I miss so far is my Android App Drawer. I know iOS introduced their App Library in iOS 14, and it's a start, but it's just not the same. There is probably an app in Cydia that would give me an app drawer, but I'm not quite ready to get into the world of jailbreaking just yet (I'm not that brave).
So after my big rant, here's a summary - Android push notifications are broken, they've been broken for some time and Google don't seem interested in fixing the problem. If someone told me tomorrow that Google had finally fixed push notifications, I would drop iOS like a hot potato and rekindle my love for Android. Please Google, help bring me back from the dark side, it's really cold out here!
Des
Click to expand...
Click to collapse
Now that's what I call a structured rant!
But what type of phone did you owned ?
I know this problem from samsung phones, and other phones I've tested. usually it's because of the OEM's aggressive take on battery management. They freeze apps in the background, and run them periodically to check notifications.
I know that's frustrating, but with your story I could feel the social isolation you've felt. And even with all the perks in the world, I wouldn't want a phone that makes me the third wheel.
But I'm much more radical than you, I don't want to change my phone, so I changed my friends. Way better now you should try it, those Apple "cool kids" pigeons weren't good friends anyway.
Obviously I'm just kidding, but I think the issue can be solved by using a ROM to espace your OEM's restrictions, or try another brand. If you ever want to come back to the light (which I'm sure you will because I couldn't bare iPhones after using an android all this time, seriously wtf if that file manager of them, and wtf is the "Other" memory partitions that increases without me having any control over it!), ask in various xda sections if users experience notifications latency, and if they don't know suggest them your little experiment you described in this post.
Hope you'll come back from your journey in the shadow,
Have a great day
Interesting rant.
Were all the phones that your friends had on the same networks? It could easily be a network latency issue
affecting how fast each message was distributed. Given that the passage of a message, say a Whatsapp message is at least: :
from phone screen
to
Whatapp encryption software
to
wi-fi-switch
to
domestic router
to
domestic ISP
to
internet backbone
to
commercial ISP
to
Whatsapp run cloud server
to
Whatsapp redirection processes
to
commercial ISP
to
internet backbone
to
domestic ISP
to
domestic router
to
wifi-switch software
to
friend phone
to
Whatsapp decryption software
to
phone notification sub-routine
to
phone screen
I'd say a small discrepancy in arrival times would be expected.....
I only mention this because it seems that you've tested massive of phones - but did you take into account different networks?
Related
My push notifications from thirdparty apps and live tiles stop working very regularyly which is a shame since the platform heavily depends on this.
It fails to open a channel etc.
Is microsoft fixing this bug in the os? Since now they say yeah just do a factory rest and it should be fine. But i dont wat to lose my settings.
And a restart temporarely fixes it but after an hour or so its terrible again.
or are the ms servers just over crowded already? I dont like apple but my dads iphone just kept working while mine stopped receiving the toasts
...
Marvin_S said:
My push notifications from thirdparty apps and live tiles stop working very regularyly which is a shame since the platform heavily depends on this.
It fails to open a channel etc.
Is microsoft fixing this bug in the os? Since now they say yeah just do a factory rest and it should be fine. But i dont wat to lose my settings.
And a restart temporarely fixes it but after an hour or so its terrible again.
or are the ms servers just over crowded already? I dont like apple but my dads iphone just kept working while mine stopped receiving the toasts
...
Click to expand...
Click to collapse
Toasts and tile updates come from the app developers servers, so depending on the platform they use there may be some down time. The Beezz twitter client occasionally stops working, but it's a free app and not ad supported so we should be lucky it has toasts and tile notifications at all.
sulphuricaciduk said:
Toasts and tile updates come from the app developers servers, so depending on the platform they use there may be some down time. The Beezz twitter client occasionally stops working, but it's a free app and not ad supported so we should be lucky it has toasts and tile notifications at all.
Click to expand...
Click to collapse
not really since tested with the same apps at the same time. Its probably because it goes to the ms servers and fails to deliver timely. Also the unable to open a channel is not related to their servers i believe? Its related to a channel not able to open on the ms servers. Downtime should probably be equal when using the same apps on ios and wp7 sending out to each other, the messages do get delivered in app just no or really really delayed notifications. Like 20 minutes and then it just works normal for a while.. Then stops again. Other than this i really like the platform.
So i wonder does anybody else experience trouble? And which is the program you use which seems to be stable all times?
I'm experiencing the same troubles on my omnia 7.
Following programs do have some problems:
-Fim: Unable to open the channel - push notifications don't work anymore.
-TextMe: Push Notifications sometimes work - but with a delay of approx. 20 minutes
Following programs don't have any problems:
-Hotmail
-Messenger by Miyo
----------------------------------------
This is really annoying - since a "usual" restart of the device doesn't help, i think i will have to do a hard reset (i wonder if this will help at all). But i don't want to lose all my settings, installed applications, short messages etc. So this really is a PITA.
stylopath said:
I'm experiencing the same troubles on my omnia 7.
Following programs do have some problems:
-Fim: Unable to open the channel - push notifications don't work anymore.
-TextMe: Push Notifications sometimes work - but with a delay of approx. 20 minutes
Following programs don't have any problems:
-Hotmail
-Messenger by Miyo
----------------------------------------
This is really annoying - since a "usual" restart of the device doesn't help, i think i will have to do a hard reset (i wonder if this will help at all). But i don't want to lose all my settings, installed applications, short messages etc. So this really is a PITA.
Click to expand...
Click to collapse
hardreset, would that really help? I think it wont really help. I have the same phone same apps and same problems also with tigertext send to wp7 and notes to tile.
i dont have the time and or want to hardreset. It might be a driver thing with the 3g etc. If nobody with other phones is experiencing this. I think hardreset changes nothig and will return to same behaviour. I will hardreset when the update comes or see if this will fix it.
20 Minutes is just strange conpared to instant on iphone and happens a lot
Pff
Did a hardreset. Tested the push again, ait a damn thing changed besides that I lost all my settings and stuff. Its just not working right. And probably a samsung driver or a ms server/os issue....
Does nobody else experience push notification downtime? Or delays? It's just not the way it should work. IM apps and Text replacement apps can never work properly in the background with these delays...
@Marvin_S which apps, specifically are you having trouble with? It could very well be that the developers servers have been down or slow.
I haven't had any Live Tile problems that couldn't directly be traced back to either the app dev's server or the way they've implemented notifications. Not on my Omnia 7 nor the HD2. Afaik, and I'm pretty sure I'd have heard about it - the wife's Omnia7 is doing just fine also. Have you tried flashing the new updated ROM? That seemed to fix a bunch of data issues.
Oh, as for the 20 minute thing, I've never seen this. Beezz for example notifies me (via toasts) in about a second or so.
Beezz has never worked for me. I always get an error whenever I try to enable push. The same happens for GReadie. I get a fail to open channel error. The weatherbug app also stopped working.
Right now my HTC hub live tile works. Its the only 3rd party live tile app I use.
emigrating said:
@Marvin_S which apps, specifically are you having trouble with? It could very well be that the developers servers have been down or slow.
I haven't had any Live Tile problems that couldn't directly be traced back to either the app dev's server or the way they've implemented notifications. Not on my Omnia 7 nor the HD2. Afaik, and I'm pretty sure I'd have heard about it - the wife's Omnia7 is doing just fine also. Have you tried flashing the new updated ROM? That seemed to fix a bunch of data issues.
Oh, as for the 20 minute thing, I've never seen this. Beezz for example notifies me (via toasts) in about a second or so.
Click to expand...
Click to collapse
Well I seem to be running the latest version pre-installed by samsung... i asked in the omnia7 forum what kind of rom I was running.
Well the thing is, it builds up all the notifications and than releases them all after each other 20 minutes later.
Basically these apps: Textme and tigertext (which I tried later to see if it could replace textme, very kind and responsive developers btw)
Also send to wp7, which often than comes up with the failed to open channel stuff.
If this rom should rely fix it, then I will just reflash it eve though its exactly the same rom... I think it has something to do with losing 3g+ signal, or wifi drops.
I'm testing the reliablility heavily since I such problems by sending constant test messages to myself (or to the echo server) the messages are received fine, but the toast is so unreliable.
Can you maybe type the versions of your firmware so I can compare it with mine? Because its for sure not an app problem since the messages all come later from diffrent apps. My test flow is like this: Open app, send message, close, send message with the second app, close and than wait. If it takes to long, open app again, resend. Sometimes it works quite right for a while, than teribly bad.
And note that I'm from a crowded area with lots of cellphone towers and have also good wifi coverage in the places I tested it. Same apps on the iphone work without problems, I compared side by side as well.
So it might just be my omnia, thats why I would like to hear which versions you are running. Since hardreset did not change a thing, I'm starting to believe its or a driver problem or ms-servers are overcrowded. I would like to try beez and see if its diffrent, however I dont havee twitter and i guess its required.
I don't think the newer ROM from Samsung fixes anything, because i installed it. Version 2424.10.11.1
but perhaps the region affects this problem, e.g. North-American Azure-Servers work fine while European Servers are struggling.
I personally have massive problems with push notifications since monday or so, and it's really starting to pi** me off!
Hard resetting idny going to fix anything permenitly because it is not the phone it is the apps just gotta wait for and update to fix
Sent from my EVO 4G using XDA App
Weird. I'm using Beezz, SendToWP7, uController, eBay, Weatherbug and probably a few others using toast and/or live tile notification. Beezz server seems to go down every so often, but both uController and SendToWP7 notifies me real quick.
I'm running the latest Omnia 7 ROM as people said it was slightly faster and had a better data connection - that said, I was entirely happy with the phone even before updating.
I did a hard reset/reinstall of my apps and such, I'm still having intermittent push problems with some apps, and with others the push won't work at all. I will say that it seems to be the same apps having the same problems, and the ones that always have worked (weather bug) still work.
I'm thinking (hoping, praying!) this is a problem simply because of the infancy of the OS...I remember the first iphone, which I bought on day one, had all sorts of problems and "gaps" in technology
emigrating said:
Weird. I'm using Beezz, SendToWP7, uController, eBay, Weatherbug and probably a few others using toast and/or live tile notification. Beezz server seems to go down every so often, but both uController and SendToWP7 notifies me real quick.
I'm running the latest Omnia 7 ROM as people said it was slightly faster and had a better data connection - that said, I was entirely happy with the phone even before updating.
Click to expand...
Click to collapse
oKe im running the latest rom since the beginning. Created fake twitter account sended a ton of messages. Crap as hell, very unreliable and today i was not able to load fb app data on 3g full bars. So it can be a phone problem on drivers with data over 3g, while 3g+ works fine. Probably euopean servers are overloaded than. Does changing my location from USA based (im dutch) To germany change the servers as well? Bc germany is much closer thus more reliable?
jmerrey said:
I did a hard reset/reinstall of my apps and such, I'm still having intermittent push problems with some apps, and with others the push won't work at all. I will say that it seems to be the same apps having the same problems, and the ones that always have worked (weather bug) still work.
I'm thinking (hoping, praying!) this is a problem simply because of the infancy of the OS...I remember the first iphone, which I bought on day one, had all sorts of problems and "gaps" in technology
Click to expand...
Click to collapse
Its the apps not the phone the apps need to be updated inorder to work on the os not the other way around
Sent from my EVO 4G using XDA App
v hubris v said:
Its the apps not the phone the apps need to be updated inorder to work on the os not the other way around
Sent from my EVO 4G using XDA App
Click to expand...
Click to collapse
this is not the case, read my post. Has nothing to do with the apps since ALL apps behave like this, it has nothing to do with the apps itself but probably slow ms servers. So no this is really an os or server or device firmware problem and not an app. Since all notifications come at the same time all after eachother highly delayed.
Apps have own servers they Sony go threw ms os is not mad for apparently apparently are made for os if apparently no work on os they need update
Sent from my EVO 4G using XDA App
v hubris v said:
Apps have own servers they Sony go threw ms os is not mad for apparently apparently are made for os if apparently no work on os they need update
Sent from my EVO 4G using XDA App
Click to expand...
Click to collapse
its not the problem of the apps! Since all apps fail at the same time to update. This is no coincidence, only a restart or waiting will solve this and than all notifications not yet delivered by multiple apps come at once! Now tell me how this is an app poblem,its the phone who is not able to receive the push even on wifi. The apps do deliver, but there is a huge delay even with beez which i checked with fake twiter account.
Every once in a while the phone just fails to receive any data based push notifications! All of them. While i do have wifi and or 3g. On 3g+ it seems to be more stable.
This could be europe related or omnia related. And narrowing this down will help dtermine the issue, since the apps are not the problem. These work fine for the others...
Marvin_S said:
This could be europe related or omnia related. And narrowing this down will help dtermine the issue, since the apps are not the problem. These work fine for the others...
Click to expand...
Click to collapse
It is neither Europe or Omnia related as I'm using the 16GB Omnia7 in Europe (slightly north of you) at the moment without fail.
If it really is all apps, I would suggest there is a problem with your data connection - are you able to browse the web properly and without pages having to reload or taking a long time to open? If not, make sure you are indeed within range of, either, 3G/HSDPA or WiFi - if you are, and it works fine on another phone/laptop I would say you have a hardware fault and need to take the device back for a replacement.
Several things to be aware of with live tiles and notifications.
I am a developer of a few apps and offer push notification and live tile updates i have done alot of testing and know the ins and outs of this..
1st there is a such thing of the phone not being able to "open a notification channel" and Hard Reset is the only way to correct this.
2nd it is possable that the app developer side to also be the problem not sending because of their service going down server problems etc.
3rd when your batt. get to be less than 1/4 percent the notification service shuts down on the phone and you will not recieve updates. once the batt is above the 1/4 percent the service will then start working again.
4th sometimes the push service is delayed due to MS.
Hope this helps to better understand.
My Apps
World Weather (Live Tile)
TV Show Alert (uses Push Notification)
To Doos (Comming soon Push, Live Tile)
Hello All,
With the new 7.5 release, does anyone think it'll be possible to eventually have an app similar to phoneAlarm Pro or even get the simple setting of peak times? I know that the newer 7.x phones are a lot more restrictive than previous WM phones when it comes to what a dev is allowed to do.
Here's the thing, because there isn't (to my knowledge) a way to quiet the phone at night for all notifications except a real phone call, I leave my phone in another room. Bottom line I'd hate to have an emergency call come in at night and miss it because I don't want to keep the phone on the nightstand.
Thank you,
Well oddly enough I was searching for a possible answer today (as my search in XDA forums yesterday didn't show any results), and found this older post concerning notifications. http://forum.xda-developers.com/showthread.php?p=11432995#post11432995
So it appears the only way to keep the phone active for emergencies and turn off notification on email, sms, etc. is to just turn off cellular and wi-fi. Sorry MS, but this is stupid as hell...
Even with 7.5 windows phone still has the smoothest UI but is behind in important features. Unfortunately seprate notifications must not be a issue with ms
Hello, Hopefully I can help with some frustrations regarding the various levels of SYNC systems and their apparent compatibility issues with Galaxy S phones. I will help anyone with this system to the best of my ability, and being a technician for Ford, i have a pretty good handle on these systems.
First off, I would encourage anyone with a question about this system to reference the Device Compatibility Matrix that is available at syncmyride.com, as is some basic troubleshooting information.
Always make sure that your CIP is up to the most current software level. Version numbers are different for each vehicle line(Fiesta, Focus, Fusion, Flex, Edge, MKx, MKt, MKs, MKz, F series, E series, Mustang etc).
There is a known compatibility issue with Samsung Galaxy S family phones that is fairly consistent, however not 100% of the time.
The common symptoms both from my engineering department, and from my own experience is a complete lockup/disconnect when updating the phone book(sync) or a blackscreen and complete system lockup(mytouch variants).
In some instances, mainly with the AT&T flavor, the phones will not connect via bluetooth for media/text messaging or sync services, however they will usually work as a phone. None of the Galaxy S series will accept phone book downloads, and that has been known to completely lock out the system, requiring a hard reset and occasionally a full reflash of the APIM(Accesory Protocol Interface Module, SYNC's brain box) to unlock.
I have found a dead consistent workaround for this that I dont imagine ford would be willing to back, but it is rock solid reliable and relatively simple, it involves flashing a rom that does NOT include touchwiz. I am not familiar enough with these phones to say exactly what, however every phone I have attempted to pair/use with touchwiz has failed, with touchwiz, or stock touchwiz gone, and again, I am not familiar enough to say for sure, the problem disappears.
I have first hand used Bonsai(epic 4g) and Beautiful SGS4G(Galaxy S 4g) as well as CM7(Vibrant) and had zero problems pairing or using any functions with the vehicle. Phone calls, streaming audio, Pandora, Text messaging, navigation etc all work smoothly with no hangups or hitches since romming the phones.
Again I hope this is helpful and if i can help you directly, feel free to contact me via pm or in this thread, however pm is going to be the best way to get in touch with me.
A few quick things that I have consistenly observed...Blackberrys are trouble. SYNC does NOT like BB's. Sync is also very sporadic with non smart-phones. Regular ol dial only phones do not seem to be very compatible, even though there are some listed on the compatibility matrix. Mytouch systems(8" touchscreen navigation with a black background and 4 way grid homescreen with top left-phone, top right-nav/services, bottom left-audio, bottom right climate control) are VERY tempermental. SYNC systems(smaller MFD that is non touch screen, or newer mustangs/raptors etc) are much more forgiving and much hardier from my experience.
Take care!
Great information, thanks.
Hmm -- app possible to remote control a late model ford, like driving the thing around with nobody in it?
lol its not quite that integrated. So far our capabilities in the shop are not that far above what you can do as an end user. I would imagine they will tie remote start, unlock/lock, windows etc in probably by end of the 2013 m/y.
We have managed to run diagnostics through sync as its tied into the HS/MS can networks, but beyond basic code pulling and system network integrity tests we haven't been able to pull reliable data out. Nowhere near solid enough to do realtime diagnostics or fault tracking.
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
I'm an experienced programmer, but a complete novice when it comes to android development. I also hope I'm posting this in the right place...
I have recently bought a OnePlus Nord (AC2003) which I'm *fairly* happy with, and a Samsung Galaxy Watch3. I'm having an issue with it in that the watch and phone will fairly randomly disconnect from each other, even when they're in close proximity to each other. I have read extensively about the possible issue*, and reset both the watch and the phone, and cleared the bluetooth cache, which appears to have made a difference, at least in the long term. The disconnection now only happens about once a day, rather than the every half an hour that was happening originally.
* One school of thought is that the watch is absolutely at fault, as the users have no problems with other bluetooth devices. Another school say it's definitely the phone, as they have no issues when they use the watch with a different handset. Go figure.
My programmer's hunch (which I've learned to trust over the years) is that a service or app in the phone is stopping and starting, and I'd like to get a log of when the phone is stopping and starting apps and services. I've enabled developer mode, and I can see the option for 'Basic Log' and 'Power Consumption Exception' log in the OnePlus logKit.
My question is - Has anyone looked at the logs for this sort of data before, and is there anything in particular I should be looking out for, with particular attention to when the battery management on the phone decides that a process can be stopped or hibernated.
(Obviously, if anyone has anything to share about any Eureka moments regarding smart watch disconnects with this phone, I'd love to hear those too )