Help "Device only" location not working on Moto G

[Android Question]

I have a Moto G first generation with Android 5.1.
I have installed a GPS spoofer as a system app, and now when I set the Location Mode to "Device only" (Use GPS to determine your location) the phone is unable to detect any location. I've tried to download GPS Status & Toolbox, and the GPS does not seem to be answering.
What can I do? Thanks

 

[eshieldsvx4]

I have a Moto G first generation with Android 5.1.
I have installed a GPS spoofer as a system app, and now when I set the Location Mode to "Device only" (Use GPS to determine your location) the phone is unable to detect any location. I've tried to download GPS Status & Toolbox, and the GPS does not seem to be answering.
What can I do? Thanks

You sabotaged your hardware's ability to naturally detect your location by installing that spoofer. You need to disable it or have it spoof network location instead.

Since Android 4.4.x, Location has three tiers:

Battery Saving - uses network based location, accurate to 75 - 750 feet.

Device Only - uses device's internal hardware to pinpoint your position. Accurate to 15 - 150 feet.

High Accuracy - uses both methods stated above simultaneously. Accurate to 5 - 50 feet.

Android 5.x and above allows you to deny location queries from apps that abuse location services without root access. Go to Settings > App manager, and select "Modify" to approve or deny individual permissions.

Please note that disabling some permissions may break the functionality of apps. System apps cannot be modified. Google apps are technically overlaid, so their permissions will be visible even if they're installed to /system/app.

 

[Hadron]

I think you mean 6.x rather than 5.x. That definitely isn't a default feature of Lollipop.

 

[eshieldsvx4]

I think you mean 6.x rather than 5.x. That definitely isn't a default feature of Lollipop.

I'm running 5.1.1 and I can modify permissions in the native app manager. Those screenshots are from my one m8 running 5.1.1.

Although it could be different as I'm using a CM12 release build from last November...