Is there a way to remove Gemini from my Android phone (safely)? This intrusive software app just appeared on my phone some months go, and
(1) I have no need for it and (2) it's just the kind of cr*p I don't
want. I just want to remove it, but I don't know if it's possible.
Is there a way to remove Gemini from my Android phone (safely)? This
intrusive software app just appeared on my phone some months go, and (1)
I have no need for it and (2) it's just the kind of cr*p I don't want.
I just want to remove it, but I don't know if it's possible. Please
advise. TIA
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it,
but I can disable it. I'm not interested in reenabling it to see how
the disables are configured.
We can always uninstall any app, even a system app, even if not rooted.
adb shell pm uninstall --user 0 com.google.android.apps.bard
Is there a way to remove Gemini from my Android phone (safely)? This
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it,
but I can disable it. I'm not interested in reenabling it to see how
the disables are configured.
We can always uninstall any app, even a system app, even if not rooted.
adb shell pm uninstall --user 0 com.google.android.apps.bard
In comp.mobile.android, on Sun, 4 Oct 2026 21:07:37 -0700, Mike Copeland <mrc2323@cox.net> wrote:
Is there a way to remove Gemini from my Android phone (safely)? This
YOu should ask Gemini!
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it, >>>> but I can disable it. I'm not interested in reenabling it to see how
the disables are configured.
We can always uninstall any app, even a system app, even if not rooted.
adb shell pm uninstall --user 0 com.google.android.apps.bard
I never recommend that procedure unless the user absolutely knows that
the absence of an app does not affect system function, or the operation
of other apps. Disable works just as well, and has the advantage that
if an unwanted side effect then reenable is easy. Mostly the only
advantage of uninstall is recovering storage space, like for the APK.
I know of people who are afraid of elevators. Even afraid of planes.
Some are afraid of left turns. Most are afraid of snakes & spiders.
If it does something "unstable" to the system, then you run this next:
adb shell cmd package install-existing --user 0 com.google.android.apps.bard
We've covered this about a thousand times on this very Android newsgroup.
micky wrote:
Is there a way to remove Gemini from my Android phone (safely)? This
YOu should ask Gemini!
Newsgroups: comp.mobile.android
Subject: Uninstalling any app, including any system app, with ADB. sans root
Date: Mon, 5 Oct 2026 12:13:59 -0300
Message-ID: <11a0erm$fv0$1@nnrp.usenet.blueworldhosting.com>
Note that I've run this command for, oh, I don't know, hundreds of apps, including scores of system packages, and it rarely fails, but it can fail.
For an unrooted user, pm uninstall --user 0 doesn't always guarantee that every system app can be removed for user 0 as apps may refuse based on...
1. It is marked as a protected system app.
Android/OEM software can designate packages as non-uninstallable.
2. It is a critical system component.
Some packages are protected because removing them could break
core Android functionality.
3. The package is required by another system component.
An OEM may impose restrictions on removing dependencies.
4. Device-owner / enterprise management restrictions.
A managed device can prevent package removal.
5. The OEM has special restrictions.
Samsung, Google, etc. can add their own package-management protections.
6. The app may be part of an APEX module or another specially managed
component which don't behave like ordinary APK-based system apps.
However, many ordinary preinstalled system APKs can be uninstalled for the user even though their APK remains in the read-only system partition.
Ask me how I know this.
I've debloated my USA-spec (hence unrootable) Galaxy so much that it works perfectly, in so much as it's even incapable of showing advertisements.
Fancy that.
I install an app that *says* it has ads.
But the ads have no way of showing.
Every once in a while, maybe one out of a score of deletions, something
"bad" happens, so the good news is you can restore these deleted apps.
The only time I couldn't easily restore was when I used Shizuku to wipe out Samsung TTS/SST engines, which could only be restored with a factory wipe (since I don't have a Samsung account so I couldn't get it from the store).
Arno Welzel wrote:
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it, >>>> but I can disable it. I'm not interested in reenabling it to see how
the disables are configured.
We can always uninstall any app, even a system app, even if not rooted.
adb shell pm uninstall --user 0 com.google.android.apps.bard
No, this just disables it. It will not be removed.
Actually *this* disables it:
adb shell pm disable-user --user 0 com.google.android.apps.bard
We've covered this about a thousand times on this very Android newsgroup.
I've debloated my USA-spec (hence unrootable) Galaxy so much that it works perfectly, in so much as it's even incapable of showing advertisements.
# Uninstall the app for user 0:
adb shell pm uninstall --user 0 com.google.android.apps.bard
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it,
but I can disable it. I'm not interested in reenabling it to see how
the disables are configured.
We can always uninstall any app, even a system app, even if not rooted.
adb shell pm uninstall --user 0 com.google.android.apps.bard
On 2026-10-05 09:48, Maria Sophia wrote:
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it,
but I can disable it. I'm not interested in reenabling it to see how
the disables are configured.
We can always uninstall any app, even a system app, even if not rooted.
adb shell pm uninstall --user 0 com.google.android.apps.bard
So, if there is a user 1, he still has the thing installed? Then the application is not truly erased, just somehow disabled.
Arno Welzel wrote:
On 2026-10-05 09:48, Maria Sophia wrote:
VanguardLH wrote:
There are a lot of disables in the Gemini app. I cannot uninstall it, >>>>> but I can disable it. I'm not interested in reenabling it to see how >>>>> the disables are configured.
We can always uninstall any app, even a system app, even if not rooted. >>>> adb shell pm uninstall --user 0 com.google.android.apps.bard
So, if there is a user 1, he still has the thing installed? Then the
application is not truly erased, just somehow disabled.
Exactly. This is why I explained, that this will not "uninstall" the app
but only disable it.
Hi Arno & Carlos,
Thanks Carlos, for asking how it works, because it's not obvious.
I've run ADB, oh, I don't know, thousands of times, and there are some nuanced details here because uninstalling just isn't the same as disabling.
Regarding what Arno Welzel wrote:
"This is why I explained, that this will not "uninstall"
the app but only disable it."
Arno, while close, is not quite technically accurate saying that.
Arno isn't allowing for the fact that Android's package manager has
several different operations for dealing with system apps.
Despite what Arno said, the command adb shell pm uninstall --user 0
does not disable a system app at all. It changes the package's
installation state for that particular user.
Always looking at this from the perspective of an unrooted Android device, for a system APK that is part of the read-only system image, Android maintains several different pieces of package state for each user.
So my point to Arno is that "disable", "uninstall" & "delete" are not interchangeable terms.
Most people on this newsgroup can't comprehend these details below,
but I invest the energy into you because I know you can (as can Andy).
For example:
1. adb shell pm disable-user --user 0 com.google.android.apps.bard
This changes the enabled/disabled state for user 0.
The APK remains in the system image, and the package remains
installed for that user.
2. adb shell pm uninstall --user 0 com.google.android.apps.bard
This marks the package as uninstalled for user 0 and removes
the package from that user's installed packages.
It does not delete the APK from the read-only system image.
The system APK is therefore still present on the device.
Therefore, it can be made installed for user 0 again with:
3. adb shell cmd package install-existing --user 0 com.google.android.apps.bard
This does not download or copy an APK.
It makes an existing system package installed for that user again.
A package can also be suspended (what various tools call "freezing"
an app), for example:
4. adb shell cmd package suspend --user 0 com.google.android.apps.bard
Suspension is yet another package state.
The package remains installed and its APK remains in the system image,
but Android prevents the user from normally using it while suspended.
Note if there is a user 1, that user 1 can have a completely different package state from user 0. User 0 can have the system package uninstalled while user 1 still has it installed and enabled.
The point is the APK itself is shared but per-user package state is not.
Then there is the concept of actually deleting the system APK.
Without root, an ordinary ADB shell/Package Manager operation cannot
delete an APK that is genuinely part of the read-only system image.
[Note: Some may be "marked" as system apps, but they're not really.]
[Note: Many system apps have user updates that can be uninstalled.]
While adb pm uninstall --user 0 changes the package state for that
user, it does not erase /system, /product, /system_ext, etc.
This is also why install-existing works: it isn't reinstalling the APK.
It is telling Package Manager to use the already-existing system APK for
that user again.
Carlos E. R. wrote:
Ok, so the package remains in the filesystem, it is not removed. To do
so needs being root. It is just marked as uninstalled or disabled for
user 0. Fine.
Then, what is the advantage of this system over the GUI method of
disabling an app? The effects are the same, AFAIK.
Is there a difference with updates? A system update can activate
disabled system apps. One has to remember to deactivate them once more.
Is this the same with adb?
Hi Carlos,
It's good that you're asking questions, as these questions I would ask too.
You are correct that using adb to (let's use loose terms) "get rid of" the effects of an app (which, in this case, is com.google.android.apps.bard) is not different, in effect, from simply doing the same thing in the GUI....
*if the GUI allows it*
To Carlos' point, adb shell allows bypassing GUI restrictions, where many system (bloatware) apps have the Disable/Uninstall" buttons grayed out.
Also we have to consider storage and cache reclaiming, which we can't
always control for system apps using just the GUI, as adb allows granular control that may not be available in the GUI.
An example we ran into long ago is that people "think" they know which apps are accessing their contacts, but if they use only the GUI, they do not.
Also, adb allows precise targeting of specific users (--user 0, --user 10, etc.) & multi-profile environments like Island or Shelter (Work Profiles).
However, Carlos is right that OTA and system updates can re-enable system apps that we thought were "gone" so I won't dismiss the possibility that it can likely happen, particularly after major OS updates perhaps (or, of course, after a complete factory reset).
In addition, adb allows if/then/else scripting, which isn't in a GUI.
a. disable -> changes enabled state
b. uninstall --user -> removes the package from that user's set
c. clear -> removes that user's app data
d. suspend -> prevents normal use while leaving it installed
e. install-existing -> restores an existing system package for that use r
In addition, adb is easily reproducible. For example, if I factory reset, I can re-run my saved adb commands which can re-establish a previous state.
But overall, my answer to Carlos' reasonable question is simply that ADB exposes operations that the Android GUI may not expose, and lets us perform them precisely, repeatedly, and on a specified user/profile.
Old McDonald wrote:
Fancy that.
Why do you waste time debloating and degoogling Android when you could
have GrapheneOS?
Why do GrapheneOS developers waste time on GrapheneOS when they should
be following your lead?
Since you're asking stupid questions, in an attempt to insult me, and yet, the fact your assumption is so asinine, allows me to respond rhetorically.
Q: What do you know about USA-dpec Samsung Galaxy booloader unlocking?
A: ?
HINT: Nothing.
On Mon, 05 Oct 2026 09:49:31 +0300, micky wrote:
In comp.mobile.android, on Sun, 4 Oct 2026 21:07:37 -0700, Mike Copeland
<mrc2323@cox.net> wrote:
Is there a way to remove Gemini from my Android phone (safely)? This
YOu should ask Gemini!
- How do I unstall Gemini on my Google Pixel 10 (Android 17)?
Because Gemini comes deeply integrated into Pixel devices running
Android 17, it cannot be fully deleted like a standard third-party app. However, you can completely **disable the app**, **remove it from your shortcuts**, and **switch back to Google Assistant or disable digital assistants entirely**.
### Optional: Advanced ADB Removal (For Tech-Savvy Users)
If you want to completely remove the package for your active user
account without rooting, you can use **Android Debug Bridge (ADB)** via
USB debugging:
```bash
adb shell pm uninstall -k --user 0 com.google.android.apps.bard
```
*(Note: System updates may reinstall or re-enable pre-installed system
stubs in future Android patches).*
On 2026-10-05, s|b wrote:
On Mon, 05 Oct 2026 09:49:31 +0300, micky wrote:
In comp.mobile.android, on Sun, 4 Oct 2026 21:07:37 -0700, Mike Copeland >>> <mrc2323@cox.net> wrote:
Is there a way to remove Gemini from my Android phone (safely)? This >>YOu should ask Gemini!
- How do I unstall Gemini on my Google Pixel 10 (Android 17)?
Because Gemini comes deeply integrated into Pixel devices running
Android 17, it cannot be fully deleted like a standard third-party app.
However, you can completely **disable the app**, **remove it from your
shortcuts**, and **switch back to Google Assistant or disable digital
assistants entirely**.
Aaaaaaaand that's got to be nonsense, if it's "deeply integrated" as a justification for "not able to be uninstalled", then how can it be
disabled? Unless "disable" does not disable...
[...]
### Optional: Advanced ADB Removal (For Tech-Savvy Users)
If you want to completely remove the package for your active user
account without rooting, you can use **Android Debug Bridge (ADB)** via
USB debugging:
```bash
adb shell pm uninstall -k --user 0 com.google.android.apps.bard
```
*(Note: System updates may reinstall or re-enable pre-installed system
stubs in future Android patches).*
It's "deeply integrated", so you can't uninstall it, but you can
optionally uninstall it.
I can sense a headache forming.
On 2026-10-05, s|b wrote:
On Mon, 05 Oct 2026 09:49:31 +0300, micky wrote:
In comp.mobile.android, on Sun, 4 Oct 2026 21:07:37 -0700, Mike Copeland >> <mrc2323@cox.net> wrote:
Is there a way to remove Gemini from my Android phone (safely)? This
YOu should ask Gemini!
- How do I unstall Gemini on my Google Pixel 10 (Android 17)?
Because Gemini comes deeply integrated into Pixel devices running
Android 17, it cannot be fully deleted like a standard third-party app. However, you can completely **disable the app**, **remove it from your shortcuts**, and **switch back to Google Assistant or disable digital assistants entirely**.
Aaaaaaaand that's got to be nonsense, if it's "deeply integrated" as a justification for "not able to be uninstalled", then how can it be
disabled? Unless "disable" does not disable...
[...]
### Optional: Advanced ADB Removal (For Tech-Savvy Users)
If you want to completely remove the package for your active user
account without rooting, you can use **Android Debug Bridge (ADB)** via
USB debugging:
```bash
adb shell pm uninstall -k --user 0 com.google.android.apps.bard
```
*(Note: System updates may reinstall or re-enable pre-installed system stubs in future Android patches).*
It's "deeply integrated", so you can't uninstall it, but you can
optionally uninstall it.
I can sense a headache forming.
If you want to completely remove the PACKAGE for your ACTIVE user
However, you can completely **disable the app**, **remove it from your shortcuts**, and **switch back to Google Assistant or disable digital assistants entirely**.
Arno Welzel wrote:
We've covered this about a thousand times on this very Android newsgroup. >>"a thousand times"? Really? So at multiple times a week for the last 10
years?
"pm uninstall" does *not* uninstall a *system* app if it is only done
for one user.
If you don't understand what a figure of speech is, then I pity you.
The goal here is, for all of us, to give the OP the "correct" answers.
Arno Welzel wrote:
I've debloated my USA-spec (hence unrootable) Galaxy so much that it works >>> perfectly, in so much as it's even incapable of showing advertisements.
And I *replaced* Android in Galaxy and many other devices with a version
which does not have even Google Services integrated. So what?
Hi Arno,
That comparison is absurd.
Allow me to help you understand what you don't seem to comprehend, yet.
Q1: Roughly, how many people "can" do what I do with my Galaxy A32-5G?
(if they had a galaxy A32-5G that is, where mine is USA-spec)
Q2: Roughly, how many people "can" do what YOU do with my Galaxy A32-5G?
(when you realize the answer, you'll realize what you said is absurd)
Note: You're likely on a Pixel.
Pixels are VERY different than USA Galaxy phones for this topic.
LineageOS supports many Samsung devices. Just because your specific
model is not supported, does not mean, Samsung in general can not use alternative Android versions:
<https://wiki.lineageos.org/devices/#samsung>
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498678:27:25 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 912 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,867 |