My last post on this subject was a little bit of a whinge, this one will not be.
I’ve had a teeny, tiny epiphany on this subject, but it puts me firmly in the naughty camp. See, it goes a little something like this…
Mobile device AGPS is shit. No ifs, buts or maybes, it’s straight up useless. Some devices do a far better job than others; Samsung have burned their bridges in my book after the Galaxy Nexus and the damp string they used for the GPS, but I know a lot of my Croydon ENL brethren (and sisteren) swear by current gen Samsung, and the Sony I’m currently rocking for my main device is pretty good once it gets a lock, and it’s pretty good at getting a lock, but the fact remains that for accurate GPS you really can’t rely on AGPS.
So what to do? For car-based navigation I’ve used CoPilot Live since my first Android device, and when I was cursed with owning the Galaxy Nexus I picked up a no-name Chinese Bluetooth GPS unit from eBay. It wasn’t expensive (even back then), and it’s SiRFSTAR III based (so it’s dead quick to pick up a lock, even when moving), and I get sub-10M accuracy off it almost all the time…
…and it would be nice to be able to use it for Ingressing. Only problem being you can’t use mock location when Ingressing, and the (many) Bluetooth GPS softwares for Android rely on having mock location enabled.
In my investigations of the “black hat” Ingress environment, I came across a great forum post that explained how to get mock locations without using Android’s Mock Location feature (not difficult, as it turns out, but you have to have a rooted device to do it). The post actually demonstrated this in reference to using fake GPS positioning (for Ingress ghosting), but the technique works equally well with Bluetooth GPS provisioning software, so I can have a second device running with accurate location thanks to black hatting. And in doing that, I’m flat-out breaking the Ingress ToS (twice, in actual fact).
Ingress “cheating” – a grey area at the very least…by