View Single Post
  #9  
Old September 24th 16, 03:23 AM posted to comp.mobile.android,alt.cellular,alt.internet.wireless
Horace Algiers
external usenet poster
 
Posts: 64
Default Do you turn off "location access" in all the apps that don't need it?

On Fri, 23 Sep 2016 18:03:05 -0700, Jeff Liebermann wrote:

I tested that on a fair collection of old Android
smartphones. The smartphone clock was set by cellular clock and not
by the GPS.


Thanks Jeff.
What I love about *your* responses is that you *back up* what you say.

So, you can be *believed* because you have credibility.

I believe you when you say that the Android clock gets its time zone and
time from the carrier signal.

And, the fact you *tested* that (on WiFi) is great proof of that.
And, that GPS doesn't help the clock drift (I can't see how it would since
the admittedly extremely accurate atomic clock *in* the satellite isn't
sending *that* signal to the phone, is it?).

Bottom line is that if you want an accurate clock,
you need to leave cellular turned on.


That confirms what I had thought.
So, in effect, the clock (and all those other apps) don't *need* location
access.

So why do they bother to force users (who don't know any better) to allow
location access when the clock (system) app is first installed by the
manufacturer?

What *advantage* is it to the clock app, or to the system manufacturer (who
installed the clock app in the first place) to *require* location access?

Makes no sense to me.
Does it make sense to you?

What do they gain?
What can they do with it in a clock app?