Hi all,
I have T-Mobile version connected to Samsung Galaxy Note 3 (Sprint version). It seems like everyday I have to fight in order to receive notifications on my watch even though I did nothing but place it in airplane mode over nite or disconnect it via BT over nite....depends on my mood. When I awake in the morning, I turn everything back on and once again, no messages. I have tried turning on/off BT, turning on/off notifications thru gear manager, turning off/on my phone and even uninstalling gear manager and reinstalling it. Have even reset the watch.
Sometimes they start coming after rebooting phone but today nothing I have done will work. Hate that I paid a good penny for this and my Pebble works better.
Anyone else having this issue and if so, what the heck do you do to get it working? Oh my phone is not rooted.
Thanks in advance for any help!
Related
Hi!
I have a few very annoying problems I want to get rid of.
The first is that all sorts of push notifications are often (if not always) very delayed. For example, when someone's played Wordfeud and it's my turn it can take up to 20 minutes before the phone alerts me. Same thing with Whatsapp and other apps. I did a factory reset recently and the problem seemed solved but after just a few hours the delays began to appear again. Both with 3G and Wi Fi.
It is the same thing with the built in FB-chat. Sometimes messages are also delayed for up to an hour. Occationally when I enter the Message hub and swipes to Online tab the messages arrives but it's rare. It could at first appear as work when two or maximum three messages arrives but then the conversation just dies and I must go to the Facebook app to view and continue the chat. Also after the factory reset it worked somewhat fine but just like with Push notifications it didn't work long enough... Same here, both over 3G and Wi Fi.
Does anyone have a single clue of what the issue is here?
Is the phone checking for new notifications in a certain pattern, like every 30 minutes?
I'm not completely sure if this is the right forum for this but I'm beginning to be kind of desperate. Notifications on iOS and Android works like a charm and I don't think the Lumia with WP should be behind in this matter.
Extremly thankful for answers.
Regards
Mikael Ivarsson
Nokia Lumia 800
OS version: 7.10.8773.98
Zune: Latest available
its not a problem of software, its a wanted feature of microsoft, wp7 doesnt have any multitastking, so if you turn of wifi and whatsapp is running, wifi is turned off for some minutes and if you turn on screen, wifi connects and whatsapp gets your messages, thats what i realized..
next phone wont be wp. :/ nice OS but the little things like this are annoying
facekill1337 said:
its not a problem of software, its a wanted feature of microsoft, wp7 doesnt have any multitastking, so if you turn of wifi and whatsapp is running, wifi is turned off for some minutes and if you turn on screen, wifi connects and whatsapp gets your messages, thats what i realized..
next phone wont be wp. :/ nice OS but the little things like this are annoying
Click to expand...
Click to collapse
Thanks for the reply!
But that's the strange thing, even if i don't turn off the screen and keep the phone "awake" there are no toast. The push notifications were instant for a few hours after the factory reset so there must be something that is "blocking" push messages. Same thing with the fb-chat. The chat should also work without problems even when the screen is turned off.
Me too are also considering walking out of Microsoft on this one. The OS is very beautiful and everything is so thought through but they still have som work to do.
Yes, background agents run every 30 minutes
thats why i wont buy a wp phone anymore. its really annoying and not SMARTphone like!
But shouldn't push messages be pushed through nearly instant?
it should be popup in the second it arrives
Exactly. Even if the screen is unlocked and wifi 3G is connected and all that it still is a delay.
The problem seem to have solved itself! I don't know what I've done but one morning I woke up and everything worked smoothly. Let's hope the issue doesn't return!
Data connection should be enabled for Push notifications to work. Maybe you went above your data cap or sometimes the 3G reception got lost.
Also, are you sure that app uses Push notifications and not regular Toasts sent by a background agent ?
Ok, this is a good one. I'm a long time root/custom ROM person all the way back to a G2 and I've not heard of something like this happening.
I got an S5. Rooted it successfully with Chainfire's auto root as described here: https://www.youtube.com/watch?v=qaZvtGwwziQ
All was well, but after a few days, I began to notice that I was not getting notifications regularly. After quite a bit of testing, and here is where it gets really weird, I was able to determine that:
-When the phone is connected to wifi and
-When the screen is off
I get NO notifications. Gmail, Facebook, Life360, nothing comes through. I've waited 5+ minutes to get one, and nothing. Then, when I turn the screen on, they all come flooding in at once. If I disable wifi, notifications come through fine. This makes no sense to me. SMS and MMS however, work fine regardless of root and/or wifi connection.
I spent quite a bit of time with a TMO rep who did all she could do to no avail. She said I should return the device for another one, which I did today.
On an unrooted, brand new device (no apps installed either), I could now get these notifications when connected to the wifi. Strange, but ok. So I rooted it, and the SAME problem began again. No notifications when on wifi.
I must have sent 30+ emails to myself trying various things to get it to work on wifi, but no dice.
I checked to make sure wifi stays on when the phone is alseep, and it was.
I checked the Samsung push service was active, and it was.
I am on the ANCH update.
I am seriously stumped here. I suppose my next step is to unroot it and see if the problem goes away. I am really surprised that no one else has reported this!
Thanks so much for your time and input. This one is killing me...
Chris
Well, I just took the NE6 software update via Kies, and nothing has changed.
I should also have said in the first post that when on wifi, and the screen is ON, all notifications are instantly delivered.
/sigh
Again, thanks for any input.
Chris
Have you tried different wifi access points? You could have background data disabled under power saving mode. I remember seeing an option to block notifications while the screen is off. I can't remember exactly where the option is located tho.
savoritz said:
Have you tried different wifi access points? You could have background data disabled under power saving mode. I remember seeing an option to block notifications while the screen is off. I can't remember exactly where the option is located tho.
Click to expand...
Click to collapse
Thanks for the thoughts. Really appreciate the input.
I have not had a chance to try other wifi access points yet, but will do that today I hope.
I did check all the power saving modes, and all were disabled.
I'll look for an option to block notifications when the screen is off, but it seems like if that was turned on, then I wouldn't get notifications regardless of being on wifi or not.
Interesting note though: Last night, on wifi, I did get notifications for some emails. So it does "work", but they are very, very delayed. I'll try and determine how delayed today as well, but for now, I will just leave wifi disabled
Again, thanks very much for any input.
Chris
Did this ever get fixed? I've been experiencing the same issue it's driving me nuts. I have my phone set to not sync, I'll manually sync but it will take several minutes, if ever to sync. My phone is getting good wifi speeds between 60-90mbits down, and I can browse the Web without delay but stuff that syncs... Facebook, Gmail, etc. All have an excessive delay.
Sent from my SM-G900T using XDA Free mobile app
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
diehardbattery said:
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
Click to expand...
Click to collapse
With my S5 initially, Remote Connection would kick in after a few minutes out of Bluetooth range. But, when I was back in Bluetooth range, I would have to do what you are doing to drop RC. I had a Gear 2 Neo prior to Gear S, don't know if that was any issue. .I did a factory rest on S5 ( to get rid of root and some other things) , and now watch connects and disconnects to RC by itself and rather quickly. BTW, when in RC, all texts and calls to S5 do come to Gear S. If I were in your shoes, I might try to reinstall Gear on phone before wiping phone. IF you do wipe phone, Gear S will be reset during the pairing process, so you may want to back up your Gear S data prior.
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
jerrycycle said:
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
Click to expand...
Click to collapse
Yeah, all that was set, but I ended up wiping both the phone and the watch and everything seems fine now... Still loving the watch... wondering how they'll make the next one better..
Just bought the second gen moto 360. Whenever i turn off bluetooth from my phone it doesnt immediately show on my watch that phome has been disconnected. I have also installed the find your phone app which tells you that phone is out of range when it loses bluetooth connectivity. The notification or vibration for disconnect usually come to the watch after a minute or two. Is there any problem with the watch?
nklrwt said:
Just bought the second gen moto 360. Whenever i turn off bluetooth from my phone it doesnt immediately show on my watch that phome has been disconnected. I have also installed the find your phone app which tells you that phone is out of range when it loses bluetooth connectivity. The notification or vibration for disconnect usually come to the watch after a minute or two. Is there any problem with the watch?
Click to expand...
Click to collapse
Nah, no problem with the watch, it dose the same on mine.
There is due to this some kind of "power saving" feature either on the watch itself or in Android Wear app, that's why it doesn't show the disconnected sign on the watch immediatly nor the vibration alert sent by whatever apps similar to "Find your phone" app (I've tested quite a few)
What I found is that, if you turn on your watch's screen from either ambiant mode or non-ambiant mode (black screen) to normal mode, the disconnected sign would show up as well as the disconnected vibration alert within seconds, otherwise, it could take minutes...
It is kinda annoying if we wanna use those apps to alert us whenever we've left our phone behind or it's being stolen since it does not make any vibrations UNLESS we manually wake the watch face up
This kind of alert should really have been built into the Android Wear app's settings in the first place along with the vibration strength/duration settings (few 3rd party apps can do that pretty well), because a lot of us often find the watch's vibration is weak (well, actually, not that weak but too short), we know the purpose is to preserve the battery's life, but I bet a lot of us would prefer to not miss notifications rather than having a few extra hours of battery life...
Hello,
Have any of you had a problem of auto disconnection with the application? I have already restored the factory settings several times and the problem still occurs maybe one of you had such a problem and could advise me how to deal with it, I don't get any notifications, which starts to irritate me
Regards
what device (model and ROM version) and what phone? Without any info about your setup it's very hard to try to help...
Anyway, the most common causes to connection issues are other app that may conflict with Amazfit app or kill it while in the background (check your phone settings) and Bluetooth/WiFi conflict. To test the later, disable all WiFi, put phone in Airplane mode then turn only Bluetooth on and see if connection gets better.
I have Stratos A1619 with PolishROM my phone is Huawei Mate 10 lite, but on any kind of ROM that problem occurs
Put your phone in Airplane mode and turn on only Bluetooth, make sure Amazfit app is open and running, confirm that watch is connected then move watch away from the phone. How far can you go without disconnecting? If it disconnects after just 30-50cm then most probably it's a hardware issue. But I'd recommend that you go entirely stock to test these things, it's hard to pinpoint anything using modified ROM.
Heey, you have options in that place where you can uninstall app, battery saving mode or optimization - sth like that. I have stratos and note9 and i have the same problem. Watch seems like have connection (top options at top left symbol phone with tick that means - connected to phone). But phone is saying disconnected. What helps - turn in airplane mode in watch, wait few seconds and turn airplane mode off.
But as i was saying - check battery optimization options and turn that function off in phone. If you are from Poland then write to me PM - i try to explain this in out native language