Database Develop

Lookout Mobile Security on CM6(.1)

I'm having some trouble with Lookout Mobile Security. I don't know if it's related to my provider (WIND Mobile Canada) or my ROM (currently on CM6.1 RC1).
Here is my experience today:
- At about 1:40 PM Pacific Time, I initiated a locate request from the mobile web interface. I did not receive a location.
- For the next 9-10 hours, my phone had a working network and data connection. I did not receive a location e-mail.
- At about 11:10 PM Pacific Time, I opened the Lookout application on my phone. The GPS fired up and within a minute I received a location e-mail.
The expected behaviour, which has worked for me before when Fido was my provider and I was not using custom ROMs, is that within a few minutes of initiating the request, Lookout should fire up in the background and send the phone's location to the Lookout servers.
So it seems that, for some reason, Lookout is failing to act in the background in response to a location request. Only once the application is brought to the foreground (which is not something I'd expect a thief to do for me as a favour) does the locate function kick into gear. Do you have any thoughts on why this may be happening?

For me it would be logical that GPS has to be turned on allways... how else should the phone know where it is? But it's just a guess.

grimsrud said:
For me it would be logical that GPS has to be turned on allways... how else should the phone know where it is? But it's just a guess.
Click to expand...
Click to collapse
GPS is enabled, that's not the problem.
The issue is that Lookout's servers are supposed to be able to push a signal to the phone (by SMS or data or otherwise) that triggers Lookout to wake up and initiate a phone locate. This used to work for me on other combinations of ROM and service provider.
What's happening now is, Lookout doesn't trigger in the background. I can wait 4 hours, 8 hours, a day after initiating the locate request and nothing happens. So far the only way to make it trigger is to open the Lookout app itself, and then it kicks in. This makes it relatively useless as a "find my phone" app!

Make Tasker restart GPS when fix is lost

Hey there,
I am having some problems with GPS of my phone. Sometimes I lose my GPS fix, typically when driving in an unknown area and relying on satnav.
What helps is to disable high precision location in quick settings and re-enable it.
So I thought this could be automated. If fix is lost, disable and enable GPS again.
Secure settings can do that, but I have problems getting a Tasker profile reacting properly to that state.
I tried querying the %LOCACC variable, (LOCACC < 5) but that didn't do it.
Any ideas?
Cheers, toskala

Any way to quick restart GPS?
I use Android Auto and at first signal didn't work, then I should enter the settings, turn GPS on and of on his high accuracý mode, then all works OK

A reliable way to manipulate location mode on 6.0 (marshmallow) and up is by using the tasker AutoTools plugin.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Hi everyone, does anyone can give a clue on how to track down GPS FIX =YES/NO from tasker?
I have the same q as topic starter.
Location accuracy variable is no help here as it is not reset once fix is lost but gps remains on (last known accuracy is stored)

solution found!
Tasker: read GPS FIX status (TRUE/FALSE) or #of Sats. in the fix
groups.google.com

Hi everyone,
I've read the above mentioned solution however I'm new to tasker and have therefore difficulties interpreting it.
My aim with tasker is, if gps fix is lost, to issue some task like dimm the screen of my android headunit when a tunnel is entered and restore brightness when tunnel is left.
First of all I would create a new profile with an event (gpx fix lost) and start then a task (lower brightness). outgoing task is e.g. restore brightness.
What is then the condition in the profile section of tasker and how can I use the solution above, respectively.
thanks in advance!

Nougat on S6 Active Wifi goes to sleep after 5 minutes... Grrr.

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.

IF statemnent in tasks

I have dificulty understanding the "IF" logic.
I tried to turn off WiFi when the screen turns dark only if I am NOT connected to a WiFi hotspot
I know I can do it by creating two profiles and querying their state, but I thought IF should also work, turns out it does not and I'd like to know why it doesn't
So I thought I'd just trythe IF condition in the task and configure a task that tells me the value of the variable %WIFII by popping up the info, but as you can see in the attached screenshots, WiFi is turned off even allthough the variable has a content matching *CONNECTION*
my phone is a rooted Xperia Z3c running 23.5.A.1.291 stock sony firmware
Any thoughts welcome

_Agility_ said:
I have dificulty understanding the "IF" logic.
I tried to turn off WiFi when the screen turns dark only if I am NOT connected to a WiFi hotspot
I know I can do it by creating two profiles and querying their state, but I thought IF should also work, turns out it does not and I'd like to know why it doesn't
So I thought I'd just trythe IF condition in the task and configure a task that tells me the value of the variable %WIFII by popping up the info, but as you can see in the attached screenshots, WiFi is turned off even allthough the variable has a content matching *CONNECTION*
my phone is a rooted Xperia Z3c running 23.5.A.1.291 stock sony firmware
Any thoughts welcome
Click to expand...
Click to collapse
2 things:
- maybe 10s is not long enough? have you tried 20?
- on screen off, Android does not seem to always be able to create a Wi-Fi connection successfully.
I have this problem myself, trying to auto turn on Wi-Fi and connect when I get home.
You can try having this run on screen on (even while locked) to test this.
Maybe someone with better knowledge of how Android system works would have a solution for this?

Thank you for your reply
Screenshots show that the WiFi connection is established successfully, I am trying to find out why some variables can bei used in the if query and others cannot
Regarding your Problem, you could try adding a wake up command at the beginning of your task. I use display dim for this purpouse (needs the secure settings or equivalent plugin)

How to get Tasker to *actually* connect/disconnect VPN?

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.