Google Chrome Problematics

These problematics below aren't verified by other peoples, but I've found by myself!

* Feel free to say, shout out and/or share this document if you've experienced the same.

1. No matter that how long you've disabled Chrome app, if you've open Play store app, it will update itself and re-enable back! regardless of you've set to turn off automatic updates!!

   As I can reproduce, it's happen often when I've change system language.

   • Also, these apps are auto update itself without user consents and cannot be prevented! if you didn't disable Google Play Store before it does!!
     • YouTube (can do same things like Chrome does, by re-enable and update app if you've disable it before!)
     • Google Play Store
     • Google Play Services

2. When I've complete reset Chrome app either via App settings or ADB commands (use am kill, am force-stop, and pm clear together), I've re-check app info and found Chrome app have Location permission toggled on after successfully clear everything!

   • Personally, I think in case if everything has been reset, it should have none of any permissions can be granted automatically at all!!
   • That's why some tech news said and found Google Chrome itself phone home user locations too often!!!

   • None of any forks doing the same things as Google Chrome itself does for this (intentionally?) problem, maybe because the marketing agreement of Android ™️ and/or Chrome itself are pre-installed as system level, which have enough priviledge for doing that thing!?
   • Same things also happen to Android Auto and Google search app itself, but both are worst than Chrome, it's will grant every permissions that those apps have except Location if you didn't turn on device location yet. (either GPS or just network-based or both)

3. Because Chrome itself use internal Manage storage function, so...

   • The Clear storage button will launch app itself (via activity shortcut?) and have 3 buttons inside, to clear unimportant site storage, clear all site storage or clear every data. (the last choice is mean include your configuratoion in the app!)
     • You will wake up an app itself, sadly to say if you've decided to stop using and keep ignoring it!
     • Default clear data button will only show confirmation dialog before performing completely delete everything within app and start everyting over from the beginning...
       • And yes, only just 2 taps to clear everything for default Clear storage button, while Chrome itself built-in clear storage button have extra steps than that!

   • From the problem number 1, I prefer to clear those data through ADB for avoid unintentionally waking it's app.
   • It seems like all of forks are also follow this line, include Bromite, (Marmaduke's Chromium fork](https://github.com/macchrome/droidchrome), etc.

4. They're lots of strange NXDOMAIN requests (captured, monitored and logged via personalDNSFilter) everytime I've start using and keep using it, no matter about hardening within application settings and browser flags!

   • This probably related to DNS Interception checks that I've recently see in the Group Policy Config of Desktop environment, include Edge Chromium, and it's enabled by default!
   • Although, they can do no harm because those random domain requests are (hope to) surely not connect to any real servers, it's only check is ISP trying to abusive the DNS resolvers or not.
   • Unfortunately, they are none of any browsers can turn off this, it's also make the pain point to network manager and/or advanced users who want to determine which domains are users and/or devices was connected.

     • This problems can be found in any other forks that follow the Google Chrome / Chromium update pipeline and doesn't patch or hardening enough before build, especially every chromium forks that appear in Play store, also include Brave and Vanilla chromium , maybe I need to include routine built from the Chromium team*, too!? *(See The Chromium Authors)
     • That's why I won't using Chrome and any chromium forks that not patched this! unless they've something to let users turn that thing off, also, they might need to make this feature off by default in the future, too!