I use a special application (Blackberry Enterprise Server) on Android and I've had problems with disconnects.
The application opens a VPN back to the network to push email and notifications to the phone. The whole idea of this application is security (VPN) and always on for notifications, email, calendar etc.
So on Marshmallow the app disconnects after an hour or so (closes down the VPN) and won't receive anything until you wake the phone back up again. Totally broken as far as I'm concerned. Happens on my S6 Active and a Blackberry Priv. BB Support sheepishly admits that its a problem and says their workaround is to keep the phone plugged into a charger and the VPN won't disconnect. Total crap!!! They also told me the problem would be fixed on Nougat which would allow them to get to the app and disable the power saving feature for that app which is causing it to disconnect. OK, some hope.
In the meantime I find this app in the play store called "disable doze" and put it on my BB Priv. It stops doze from kicking in and shutting down the VPN. On the priv it actually works. Now my VPN stays connected all the time like it should. I'm ecstatic! I try it on my S6A and it doesn't work. Still getting the VPN disconnected. Bummed because I really like the S6A and want to use that as my DD.
So I come here to XDA and see the NOUGAT beta for S6A and get all excited. I flash it to my phone and set up BB Software. Now I find that the wifi shuts down after 5 minutes on Nougat. I read tons of threads about wifi turning off after 5 minutes disregarding the "always keep wifi on" setting in nougat. So far no way that I can see to get wifi to stay connected.
WTF!!! I totally understand all the power saving stuff to extend battery life, but they put provisions in there to allow those who need to be able to disable. WHY ISN'T IT WORKING? Is this related to the S6A or is it across all hardware? I don't have anything else on Nougat to test.
Any ideas on what else I could try. Love that S6A but if it's not going to stay connected I just can't use it.
Roveer
Nougats in beta right now for the S6A, this isn't official firmware.
I understand its beta, but flaw like this always seem to find their way into the final builds. I'm reading threads all over the place (not just S6A) about this issue so I don't think it's just a beta thing. I'm not sure I understand why if there is a setting in the wifi to keep it on _always_ including sleep / doze etc that it basically does NOT do that.
Related
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.
UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.
My WiFi has issues opening new connections, like checking my email can take anything from a normal 1 second to just sit there and spin for 30 seconds.
This gets worse if I ask the email client to check all three accounts at the same time.
Opening say facebook through a bookmark on the start screen, can either load instantly, or just show a white screen until I force close Chrome and retry.
I never get an actual timeout error, but it'll keep loading some items between 10 seconds, to just never connecting.
When I do a speed check, there's no issue, I get the same 12 Mbps as the wired computer, assuming it'll actually start downloading.
On the play store there's broken downloads though, it'll download at max speed instantly, but then hang in the middle until I force stop the play store (or reboot).
If I let it sit long enough, it might resume but often with corrupt downloads as a result.
I've had this problem for a while now, and I've tried connecting to various other networks with completely different configurations and it's pretty much consistent.
Disabling WiFi and using the LTE network instead, it doesn't display this behaviour at all, so it has to be something with the WiFi.
Has anyone else had this? I can't find anything useful through the search or google, they all suggest I do this and that on my router, but the other devices work fine.
Tested with the HTC M7, an old Motorola Razr, even the now ancient Moto XT720 has no issues.
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
eyeoncomputers said:
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
Click to expand...
Click to collapse
I checked your thread, and I had a bug like that on 4.4.4 actually.
Where it would work fine, go to sleep then not wake up again.
For me, it was a game from humble bundle that triggered this, "The Deer God"
There was another game on play that did the same, but I can't remember the name of that one.
After I emailed the devs of Deer God, they oddly found the bug immediately and their new version didn't have this problem.
I didn't even send them a log file or anything.. Which was weird.
So far this never happened after upgrading to Lollipop though.
My WiFi problems disappeared at work, but remained at home.
Thinking it was the router, I borrowed a WiFi repeater but the problem still occurred.
Even when I used the repeater as a hotspot with cable.
I was about to give up, and just use my 4G all the time..
But I installed DD-WRT, and lo and behold, WiFi works flawlessly?!
It's not like I'm using a cheap rubbish router, it's the Netgear Nighthawk for crying out loud..
You'd think the software for it would be well coded considering how long they've been doing these devices...
Hey Guys,
Today i upgraded from MM to Nougat and flashed the Moonlight ROM (nobody answered in the thread) ...so far everything works fine, but I have massive problems with push notifications...i receive push notifications just from whatsapp or email...from apps like flashscore (sports app) I dont get notifications
Can someone help me?
Could a new flash of this rom help?
Edit: everytime I turn off WIFI and turn it on again, it works for a few Moments...and I receive all the messages I missed at once
The same happens with mobile internet
I have exactly the same problem and can say it's definitely GCM related, as i first experienced it while trying to get the "Join" app (great pushbullet alternative) to work properly and ran the diagnostics that are included within it. The problem seems to pass for a while when the network status changes, then no pushes come through at all until it changes again, eg. connecting or disconnecting WiFi or turning airplane mode on and off. Im pretty sure it's not battery-saving related as it occurs regardless of if the app is active or working in the background, unless it's the Google play services part that gets killed after some time but i have no idea how to check it. I've tried some heartbeat interval changing apps but unfortunately none did the trick and I'm out of ideas and this is pretty frustrating
S6 Active on AT&T - DQE1 firmware giving me wifi problems. How do I stay on DQD1?
So I had been putting the nougat builds on My S6 Active from a post here on xda. On the DQD1 build everything seemed pretty good for me. Then one morning I awoke to see that the phone had automatically updated itself to the DQE1 build. Then the problems started. Every time the phone would go into lock screen and I'd re-open it, I'd get the wifi connection message. Also had all kinds of problems staying connected to wifi. I put DQD1 back on to do some testing. Problem is, it keeps updating to DQE1 overnight. I found 2 places in android to stop it from doing that but both don't seem to stop it. Again, it updated to DQE1.
Some have suggested that I freeze the update application with package updater pro. Before I go that route, what application or service am I trying to prevent? I got another app that is supposed to allow me to suspend applications/services but I can't seem to identify what app/svc I would actually want to suspend.
U open app ATT Smart WIFI -> to settings. and config app.
or disable thit app.
Now, check wifi again.
roveer said:
So I had been putting the nougat builds on My S6 Active from a post here on xda. On the DQD1 build everything seemed pretty good for me. Then one morning I awoke to see that the phone had automatically updated itself to the DQE1 build. Then the problems started. Every time the phone would go into lock screen and I'd re-open it, I'd get the wifi connection message. Also had all kinds of problems staying connected to wifi. I put DQD1 back on to do some testing. Problem is, it keeps updating to DQE1 overnight. I found 2 places in android to stop it from doing that but both don't seem to stop it. Again, it updated to DQE1.
Some have suggested that I freeze the update application with package updater pro. Before I go that route, what application or service am I trying to prevent? I got another app that is supposed to allow me to suspend applications/services but I can't seem to identify what app/svc I would actually want to suspend.
Click to expand...
Click to collapse
I've had the same problems. I'm hoping the suggestion from above me works.
I have a problem with my recently purchased Tasker app. I tried posting on the official Tasker forum (https://tasker.helprace.com/s1-general/problems/top) but after I would click submit, nothing would come up. If anyone knows how to get in contact with the developers other than leaving a negative review on the Play Store that would be much appreciated.
I have a Samsung Galaxy S9 (not rooted) running whatever the latest version OS (Pie I want to say?).
I have a simple Profile setup to Connect to VPN when Wifi is connected, and Disconnect from VPN when Wifi is disconnected (as an Exit task) using the OpenVPN Tasker Plugin.
On rare occasion, everything works as expected.
Unfortunately, the majority of the time, it will indeed recognize the correct state (Wifi Connected), however, it will not connect to the VPN. When I go into Tasker, I see the Profile is green text, and if I go to More>Run Log I can see that it says something to the extent of:
"Active 2 Wifi Connected" then "Start TaskService" then "Running 3 VPN Connect" then "OK 3.1 VPN Connect.com.ffrog8.openVpnTaskerPlugin\n***\n*!" then "ExitOK 3 VPN Connect" then "Stop TaskService" (this is all in reverse order, since I think the run log puts the newest events at the top, but this is how I read them from bottom up).
Tasker even says 1 Task running on the notification bar on my lock screen. However the VPN is not connected. If I go into Tasker, turn off that profile, then turn it on again (via the toggle switch on the right hand side), the VPN will connect as expected and the run log will say the same exact thing.
Likewise for the Exit Task - when I disconnect from the network Tasker seems to recognize the state just fine (evident in Run Log and notification icon in lock screen), however my VPN remains connected (well my guess is it must disconnect for a short period as I transition from Wifi to 4g).
I have tried waiting a while to see if it's just a time issue, but I could wait hours and it will never trigger one way or the other (VPN Connect or VPN Disconnect). I have tried different Wifi networks. The Wifi State Active = "Any". In Android Settings>Apps>Tasker>Battery the toggle for "Allow background activity" is set to on, Optimize Battery Usage is set to off. Likewise for OpenVpn Tasker Plugin.
*Joao or anyone have any ideas?
Many thanks.
Troubleshooting = Because a Piece of Code went
Sorry to say that it looks like I am the 1st reply, as I have no real training in coding or programming myself.
I too recently began to play with such though with the intent to install it on some family member's devices ? However, like you I have not been able to get my desired automation regular enough to share it. When I 1st downloaded Tasker (I think) it had something about a "community" to share & get help with as well as more.
Trying to be helpful I ran a quick search for the specific site & as usual, Google had to go overboard with the results. Still hoping this will help you sooner as they all focus on that particular program:
https://community.home-assistant.io/t/tutorial-using-the-new-auth-system-with-tasker/82423
Just wondering if all the changes to Android OS as a whole may also have an affect on something minor such as whatever we choose to do with "automation" programming? Have seen throughout various post's & news that sort of thing....
for any other poor soul with the same problem, I read a couple of obscure comments on the interweb that the OpenVPN plugin for Tasker is no longer functioning, and all must be run through the Open VPN Connect app (NOT Open VPN for Android app) using intents. I found a guide once, and am testing it now and will report back if it works more reliably. Thank you Lone wolf for your reply.
just to update the poor souls, using intents like I said seems to work more reliably in terms of connecting to VPN. The only problem is if you go out of wifi range, it disconnects, but then are back within wifi range quickly (like somewhere with bad wifi signal), it will not connect again for some reason.