Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.cellular    |    Devices for productivity & masturbation    |    20,339 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 20,069 of 20,339    |
|    Alan Baker to Arlen Holder    |
|    Re: How does incoming caller ID work - a    |
|    01 Jun 20 11:44:45    |
      XPost: comp.mobile.android, alt.comp.freeware       From: notonyourlife@no.no.no.no              On 2020-06-01 10:55 a.m., Arlen Holder wrote:       > On Mon, 1 Jun 2020 19:00:00 +0700, JJ wrote:       >       >> Telephone caller ID source data came from the telephone service (the       >> telephone company's machine), not Android OS or the recipient's phone       >> device. So, whether it can be controlled or not, depends on whether the       >> telephone service provide a way to do that.       >       > Hi JJ,       >       > Thanks for taking a risk at helping answer the technical question, where       > you and Gary accurately pointed out that the caller ID information comes       > from a _variety_ of cascaded sources.       > 1. Carrier "Calling Number Identification" packet information       > 2. Default "Phone app" lookup into the system sqlite contacts database       >       > My goal is to control the _final_ caller ID display, based on a contacts       > database of my choosing, on the local device (since I do not have a default       > sqlite contacts database, simply for privacy reasons alone).              Because sqlite databases on your phone aren't private, Arlen?              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca