No it wouldn't, and it'd be nigh impossible for the handset to make that judgement call. That's not a computable problem except by the User reading the code, understanding it, and toggling the fake data switch on.
Besides which, I don't care if you feed me garbo GPS GLONASS if I've war driven and reverse indexed local wireless nodes to GIS coords. There's more than one way to get at coordinates, and enough hands in the jar in terms of being honest with location data by default that it'd be an uphill battle to fight teach users just how many ways a mobile handset can potentially leak location data.
The problem is that the data is retained at all. Until that data is considered toxic/a liability, there will be no respite from it.
Besides which, I don't care if you feed me garbo GPS GLONASS if I've war driven and reverse indexed local wireless nodes to GIS coords. There's more than one way to get at coordinates, and enough hands in the jar in terms of being honest with location data by default that it'd be an uphill battle to fight teach users just how many ways a mobile handset can potentially leak location data.
The problem is that the data is retained at all. Until that data is considered toxic/a liability, there will be no respite from it.