If you own an OPPO Find X9 running ColorOS 16, you've probably noticed that swiping left from the home screen opens Google Discover. You've probably also noticed there's no setting anywhere to turn it off.
The classic trap: every solution online tells you to disable the Google package, which kills "Hey Google", Gemini, and voice search along with Discover. Not great.
Here's the clean method. It disables Discover only, and leaves everything else intact.
What you need
- An OPPO Find X9 (this should also work on other recent OPPO phones running ColorOS)
- ADB installed on your computer (Mac, Windows, or Linux)
- A USB cable
- USB debugging enabled on the phone
If you've never used ADB before, it's a small command-line tool that lets you talk to your Android device from your computer. On Mac with Homebrew:
brew install android-platform-tools
To enable USB debugging: Settings, About phone, tap "Build number" 7 times, then go back to Settings, Developer options, and turn on "USB debugging".
The fix
Plug in your phone, accept the ADB authorization prompt that pops up, then run these commands:
adb shell settings put secure assistant_screen_type 0
adb shell settings put secure asistant_screen_type 0
adb shell am force-stop com.android.launcher
adb shell am force-stop com.google.android.googlequicksearchbox
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
That's it. Swipe left from your home screen, nothing happens. Discover is gone, but "Ok Google" and Gemini still work.
Why this works
ColorOS uses an internal key called assistant_screen_type to decide what shows up to the left of the home screen. The possible values:
| Value | Behavior |
|---|---|
0 |
Nothing (Discover disabled) |
1 |
OPPO Assistant (Breeno) |
2 |
Google Discover |
Default on the Find X9 is 2. We set it to 0.
The force-stop on the launcher and the Google app forces them to reload their config. Without it, the change only takes effect after a reboot. The am start cleanly restarts the home screen.
The weird part: the duplicate key
You probably noticed we run the same command twice with different spelling:
adb shell settings put secure assistant_screen_type 0
adb shell settings put secure asistant_screen_type 0
Yes, there's a typo in ColorOS. Somewhere in OPPO's code, someone wrote asistant (one "s") instead of assistant. Both keys exist in parallel, and depending on the system version or context, one or the other gets read. Setting both to 0 covers all cases.
What I tried first and what didn't work
In case you run into these elsewhere, here's why they fail:
| Method | Why it breaks |
|---|---|
assistant_screen_type_left_enable=0 |
This key only toggles the UI option, but assistant_screen_type=2 still forces Discover |
Disabling the Google package with pm disable
|
Kills Discover, but also kills Assistant, search, Gemini, basically everything |
Disabling MinusOneActivity or DrawerOverlayService
|
SecurityException: Android protects system app components, you don't have permission |
launcher_slid_slip_enable_state=0 |
Controls a different gesture, not Discover |
swipe_right_display_content=0 |
This key isn't used by the OPPO launcher |
overlay_launcher_scene=0 |
Same, controls something else |
Verifying it stuck
adb shell settings get secure assistant_screen_type
adb shell settings get secure asistant_screen_type
Both should return 0.
If you want Discover back later
adb shell settings put secure assistant_screen_type 2
adb shell settings put secure asistant_screen_type 2
adb shell am force-stop com.android.launcher
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
Notes
Tested on OPPO Find X9 running ColorOS 16, no root required. The method should work on most recent OPPO and OnePlus phones since they share the same ColorOS base, but I haven't verified it on other models.
If a system update ever wipes the config, just rerun the commands.