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

On Tue, 9 Jun 2020 13:35:53 +1000, Gary R. Schmidt wrote:

> Ah, I didn't mean that 'you' qua 'you' would have to write the 
> application, but that a secure application would have to be written.

Hi Gary,

I appreciate that you clarified, as Usenet is inherently an easily confused
media, as we converse, days apart, and only via the textual medium.

Unfortunately, I suspect, something like 99.9% of all contacts on people's
Android phones, are _already_ uploaded to the Internet, whether they know
that or not.

Even _my_ contacts, years ago at least, were uploaded to Google servers!
o But this was before I realized what Google was doing with that sqlite db!

All I'm trying to do is what I've always strived to do, which is:
a. Provide a general purpose (usually free) solution that anyone can use
b. Which gives them two things that I feel everyone on Android deserves
   (1) Functionality (e.g., contact lookup & caller ID)
   (2) With privacy (i.e., contact information should never be on the net!)

I'm close with a solution... 
o Oh so close... as I've solved the contacts, dialer, and SMS app issues.

Privacy-based tools that do _not_ use the default contacts sqlite db:
o Dialer === SimpleMobileTools Dialer (a dialer is actually optional today)
o Contacts === SimpleMobileTools Contacts (this is still essential today)
o SMS === PulseSMS (this can be tricked into displaying the caller ID)

Each of those works just fine with an empty default contacts sqlite db.
o *The only thing left is caller ID* (with an empty contacts sqlite db)*

I need to test caller ID apps, but I've been working other issues, e.g., 
o Microsoft installer error: 1326 Failed to install update. 
<https://groups.google.com/forum/#!topic/misc.taxes/43gVJ_MxTn4>

Since I'm a good Usenet citizen (e.g., I search first, I ask, I test, and I
report back), I won't have any useful information for you until I test out
the caller-id apps to see if _they_ will solve the caller ID problem that
remains when you wipe out the default contacts sqlite database for privacy.

> Possibly one or more already exists, if I wanted secure[1] 
> communications I would be looking for such a replacement application, as 
>   I said, it cannot be bolted-on to the existing one.

I agree, there are multiple possible solutions to the problem set of the
default contacts sqlite database being uploaded to the net without your
permission.

What are those possible solutions? 
o I don't know them all, but these are two that I will strive to find!
1. Find only apps that use their own private personal contacts database!
2. Figure out how to stop Google uploading the default contacts sqlite db.
-- 
It's a worthwhile endeavor to maintain functionality & privacy together.