Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Marion <marion@facts.com>
Newsgroups: comp.mobile.android
Subject: How to delete Google Discover from both your user & work profile
Date: Fri, 21 Mar 2025 04:06:54 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <vrioku$1632$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 21 Mar 2025 04:06:54 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="39010"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
Cancel-Lock: sha1:ok1vEWgwcR9usIJcIsaVSK+exdw= sha256:hvDvI/uhwTw7T5a/QxSfj5L2kUPmo/v6XZOljNFDuV0=
	sha1:Zdvlq8YYzVKJUg5LJOVbRKeyg1w= sha256:J/CfgsxcG7i2ojAoQqUONTMNSTm9aWzOd9Ld98DGR/I=
Bytes: 3223
Lines: 44

Following up on this post in a thread from Stan I don't want to hijack
 *Google nag to turn Discover on*
 <https://www.novabbs.com/computers/article-flat.php?id=57854&group=comp.mobile.android#57854>

In that thread, I looked up what "Google Discover" was, since I had never
experienced it in all my years of using non-rooted Android phones. It
turned out I had disabled it long ago for "user 0" but not for "user 11".

I didn't even know I had a "user 0" and a "user 11" on my phone.
Did you know that?

Anyway, this post is written so that anyone can cut & paste the commands
below to determine if you (or the other users on your phone), have it.

If you have it, you can wipe it out.
It's what I do to all the google packages (that don't break the system).

It's important to note that 'Google Discover' is inside this package.
 <com.google.android.googlequicksearchbox>

I have that package on my Android 13 Galaxy so why don't I see "Discover"?
 C:\> adb shell pm list packages com.google.android.googlequicksearchbox
      (this lists it)

Luckily for me, it's been long ago "disabled" by me (probably en masse):
 C:\> adb shell pm list packages -d com.google.android.googlequicksearchbox
      (this lists it)

I looked to see if it was "stopped" also (in addition to disabled).
 C:\> adb shell "dumpsys package com.google.android.googlequicksearchbox | grep stopped="

The output indicated that the package wasn't installed for "user 0" but it
was installed (& working) for "user 11", so I needed to figure who is who.

 C:\> adb shell am get-current-user
      This reported that I'm user 0 when running adb

Digging deeper, since I have no accounts set up on my phone, apparently I'm
user 0 & apparently my "work profile" is "user 11" (which I didn't know).

So for the work profile, the Discover functionality exists, but not for the
main profile of mine. (I don't have any "accounts" set up on my phone.)

I'll post a followup that starts with all that in mind, but that's a
summary that I brought over from the aforementioned thread, for starters.