Yes, but your last position keeps "cached".
So, app knows your last postion before to know your current position.
But, if Location is disabled, probably the system blocks it at kernel level, so there is nothing to do.
Certainly, it would be easier to keep Location enabled and let an app think the Location is turned off (or the device is located at another fake position).
Ok, now I know where you are coming from.
Yes, I agree with the caching. However, even when I enable Location on my device, it will still take 2-3 minutes before the app will "see" *any* GPS coordinates (even the fake one) because it seems the device first needs to lock into the satellites. So this is giving me the impression that the way apps get gps coordinates is via a system broadcast intent from android (after it locks into the satellites), and then XPLUA can intercept that broadcast and substitute the real coordinates with the fake ones so the app will only get the fake ones.
And yes, this delay wouldn't happen if I kept location on all the time because it would always be "locked in" after the initial lock. But for privacy/security reasons, I only turn on the location for this app, then turn it back off then I am done using it. So, I just looking for a solution so I don't have to wait the 2-3 minutes before the app fully works correctly.
So, my main goal is to get the app to see the "fake" coordinates immediately and not wait the 2-3 minutes for the device to lock into the satellites.
But, if my theory is correct (that apps receive gps coordinates via a broadcast intent only *after* the device locks in), then that means I must somehow generate my own broadcast intent, so that the app doesn't have to wait the 2-3 minutes for android to generate it.
But it doesn't seem that XPLUA can do a broadcast intent.