Re: How does incoming caller ID work - and more specifically - can caller ID source data be controlled?

On Sat, 6 Jun 2020 22:30:21 +1000, Gary R. Schmidt wrote:

>> But if you have a _better_ working solution to the problem, I'm all ears.
>> 
> Sure, you have to write a "call application" that does all that you want 
> securely, it cannot be done using the existing components of an Android 
> handset.

Hi Gary,

Thank you for clarifying the situation, where I don't disagree with you.
o Both you & I are well meaning, intelligent, purposefully helpful adults.

As such, you hit the nail on the head.
o If you're an expert, you can write your own apps that do have privacy;
o But if you're a general user, you need to rely on privacy-based apps.

The only workable solution is to either write your own app, or simply use 
apps that don't rely on the inherently poorly designed default sqlite 
contacts database use model (designed, of course, by Google).

To have _anything_ in the default contacts sqlite db, is to NOT be private!
o I didn't design it that way... Google did.

To my knowledge, nobody has suggested a better solution (e.g., your 
solution is fine to write your own app, but it's not workable for the 
general user).

For the general user... 
o If you value privacy, then you *must* have an _empty_ contacts sqlite db!

Yet, for someone like you, who likely _can_ write your own apps (dialer, 
contacts, & sms apps), then, to people like you, the statement that the 
default sqlite contacts database is inherently not private doesn't ring 
true (but only to people who write their own apps).

But, the fact remains, for the general user, this is a VERY TRUE statement:
o *The default sqlite contacts database is inherently _not_ private!*

Worse, for the general user, this is also, sadly, a very true statement:
o *It is constantly uploaded to the Internet _without_ your permission*

Luckily, for the general user, these two workarounds appear to work well:
1. A workable solution is to wipe out that default contacts sqlite db, 
2. And then, use non-Google apps that employ a private contacts database.

I've already explained the apps that _do_ respect your privacy
o That is, you need apps that do _not_ use the default sqlite contacts db!

The only app I have left to define is a privacy-aware caller-ID app.
o All it needs to do is read its own private contacts database.

Or, as you correctly stated, you can write your own app that respects your 
privacy better than the Google apps do (contacts, dialers, sms, etc.).
-- 
The key problem with privacy is that Google doesn't want you to have any.