Hey ya's.
I've just discovered a problem I was having and was wondering if there's a way around it. Since going to GB I'd offhand noticed that when I opened my navigation apps, or golfshot my tasker profile to turn on GPS wasn't turning it on.
I deleted the profile the other day and started a new one, but when I was setting the task to turn on the GPS when these apps are started I got a message from Tasker that Google has disabled the ability for the gps to be turned on with the apps and that they require the user to in fact turn on the gps themselves.
I find this annoying as I've never had to think about the gps myself, it just went on and off with the apps thanks to good old Tasker.
Don't suppose anyone knows a fix for this or maybe with the heads up someone will go looking? Won't be me 'cause I can't do ****.......
But I can hope someone will find a way.
Android 2.3+ doesn't let apps toggle GPS. This restriction can only be removed by flashing a custom ROM
Related
I've had this question for a while, and it's really bugging me. It is not a specific Android question, but maybe there is an Android solution.
Is it common for Vogues to only poll/activate the GPS when a "non-service" app is requesting it? In other words, I want the GPS active in the background no matter what else I'm doing on my phone. With my wife's blackberry, the GPS is active all of the time and updating Latitude the entire time the phone is on. Can this be done with Vogue? Right now, my GPS is only active when I run an app that wants to use it explicitly, such as Maps or GPSTest. Is there not an Android service that would run in the background to do this?
There's nothing I'm aware of that does this (though I'm wrong.. lots.. lol) GPS is a huge battery hog, so that's why it only runs 'on demand'.
Thank you for the reply. I just wanted to make sure it was expected behavior.
I would be OK with the battery drain. I'm kinda surprised there are no android apps/services to do this.....
hmm...
I've always wondered this with regards to Google Search locally oriented searches - how would it determine what's local? It seems to quick for it to be able to get a fix
To be honest with you.....the GPS functionality on the Vogue doesn't make much sense, and it's pretty much useless unless you plan on running maps (or your favorite gps app) in the foreground. As soon as you get a call and app changes to background, you risk losing your GPS lock.
szman22 said:
To be honest with you.....the GPS functionality on the Vogue doesn't make much sense, and it's pretty much useless unless you plan on running maps (or your favorite gps app) in the foreground. As soon as you get a call and app changes to background, you risk losing your GPS lock.
Click to expand...
Click to collapse
The GPS lock comes back. I've turned off the screen, taken calls, changed apps, and GPS has always worked for me.
I hear all this stuff that GPS doesn't work, and I'd fix it, but I have no debug info! It works for me...
Ever since the most recent Motorola Assist update I get a constant Notification Nag that I need to turn GPS on for driving assist to work. I am fully aware of that and use taker to turn on GPS when my car bluetooth attaches. Can anyone give any insight into how to make this notification stop? Is there an Xposed module that addresses this or any other way to use assist and driving but not be nagged?
TCommander said:
Ever since the most recent Motorola Assist update I get a constant Notification Nag that I need to turn GPS on for driving assist to work. I am fully aware of that and use taker to turn on GPS when my car bluetooth attaches. Can anyone give any insight into how to make this notification stop? Is there an Xposed module that addresses this or any other way to use assist and driving but not be nagged?
Click to expand...
Click to collapse
Just leave GPS on. It's only in use when an app calls for it so it does not affect battery life...unless you have a bunch of apps that constantly update based on location. You don't have to worry about turning it on and off when you need it.....enabling it on your device only provides access to it from your apps (driving assist, maps, etc..), it doesn't turn it on and it just runs non-stop.
I've just unchecked the "notifications" box in the Assist app info, that solves it for me. If you don't care about it displaying the current profile in the status bar it'll fix ya fine
I'm having some problems with NFC. Prior to Friday evening, my NFC was working great with Android Beam, Google Wallet, etc.
Friday afternoon I was playing around with Tasker and the NFC Locale plugin to create some tasks when a specific NFC tag was read. I made just a simple "turn on flashlight" task and was wowing myself with the magic of the tag. I also installed the Xposed module that lets you use NFC with the screen off. After playing with it for awhile I put my phone in airplane mode (I was in a poor service area). A few hours later (still in airplane mode but with NFC turned on) I resumed play with NFC and Tasker to make some more interesting tasks but noticed my phone wasn't responding to my previously used tag or any other (unused) tags. I thought maybe since I didn't cell signal that is why it wasn't working (stupid thought, I know) and decided to wait till I had service to resume the tinkering.
Fast forward to tonight, I still can't get my phone to respond to any NFC tags or any tap to pay terminals (for use with Google Wallet) or Android Beam with my SO's Moto X and I can't think of what else to try before I do a factory reset.
So far I have:
1) frozen/hibernated every NFC using app individually to test each one to see if any of them would work on their own
2) uninstalled every app and Xposed module that uses NFC except Google Wallet
3) rebooted my phone multiple times ensuring NFC is on
4) ran a logcat to make sure NFC is actually turning on/off and from what I can tell it is (I can post the logcat if need be)
Factory resets are such a PIA and I'd like to avoid it at all costs but I am thinking that is the way I need to go unless anyone has any other ideas for me. Googling around it seems like a lot of NFC issues tend to be hardware related...I am definitely hoping that is not the case.
Thanks in advance for any advice or input!
Hey dudes, recently I've been having a problem with my note 5 where google maps/gps just doesn't work unless I reboot my phone. I'll put in the address and my location will be detected, but once I start driving the location doesn't move, it's as if the app is frozen, but it isn't. Rebooting and reopening the app makes it work which makes me think it must be software rather than hardware? I have factory reset the phone, but the problem persists. Any ideas for a solution?
GPS Toolbox app, use it, if it doesn't work try a different navigate app, like waze.
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
I'm having the same problem. GPS seems to know generally where I am, but not enough to guide me through the navigation. If I ask Maps to tell me where I am right now (stationary, at home), it locates me two blocks away. If I ask Maps to navigate me while I'm on the road, it finds me a route from where it thinks I am, but is unable to update my location once I start moving. My location seems to jump around a lot during navigation and it shows me driving in the middle of the block two blocks away.
I've been trying to find an answer to this online but can't find anything helpful - my location services are on, power saving mode is off, locating method is GPS, Wi-Fi, and mobile networks. I've tried turning location off and back on, I've tried restarting the phone. Nothing works. The problems started when I woke up (e.g. didn't change the settings and suddenly it went wrong) and the phone didn't drop or anything.
GPS toolbox did nothing for me. Waze is having the same problem. I even downloaded Mapquest, thinking that Waze was using Google tech and that was the issue, and Mapquest is having the same problem. This is so frustrating - any ideas?
I have the same issue with my Note 5. I have even had my handset replaced to fix this issue. But I'm stuck with the same problem. There is something seriously wrong with these devices and Samsung needs to own up to it. Considering how much these devices cost, you'd expect everything to work.
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!