XPost: comp.mobile.android, sci.electronics.repair   
   From: harry@is.invalid   
      
   He who is nospam said on Tue, 21 Nov 2017 17:55:51 -0500:   
      
   > you were *so* sure you had blocked google's ability to track you, going   
   > to such extreme lengths as changing your google id every few weeks.   
   >   
   > many people told you that you were still being tracked, but you blindly   
   > dismissed it.   
   >   
   > now you know.   
      
   You would love that to be the case, but, you're jumping to conclusions out   
   of confirmation bias (i.e., you *wish* it were true).   
      
   I looked and I don't think it's the case for me since I don't see (yet)   
   anything called "Firebase Cloud Messaging" on my Android 4.3 phone.   
      
   Time will tell which phones were affected, but this is a good one for   
   Google to get sued on, as it certainly will take some 'splaining why they   
   captured unique cell tower IDs when Location Services were disabled.   
      
   All we know, so far, is that it started in January of this year, and that   
   it used "Firebase Cloud Messaging" services - whatever that is. I googled   
   it, and I don't think it's even on my phone - but it's too early to tell   
   just yet what's going on.   
      
   Google apparently immediately said they'd terminate the practice of   
   capturing cell tower unique IDs - so, it doesn't appear to be something   
   they sanctioned (because they wouldn't likely have agreed to terminate the   
   practice so quickly if they had their legal ducks already lined up).   
      
   Time will tell which devices are affected - but I don't even see the app on   
   my phone - which is rooted - so I can delete it - if I can find it - but it   
   doesn't seem to exist.   
      
   To other android users:   
    Q: Do you see a process for "Firebase Cloud Messaging" services?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)