How to Disable Google Discover on OPPO Find X9 (ColorOS 16) Without Losing Google Assistant

Florian — Mon, 27 Apr 2026 14:35:44 +0000

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.

Openinary: The Self-Hosted Cloudinary Alternative Nobody Built Before

Florian — Sun, 21 Dec 2025 13:06:10 +0000

I spent the last 6 months building Openinary, and I believe it fills a real gap in the self-hosted ecosystem.

The Problem

You know what’s wild?

There’s Nextcloud for file storage
There’s Immich for photos
But there was nothing for image processing and delivery at scale, fully self-hosted

Most SaaS image platforms follow the same pattern:

A great API
Strong lock-in
A bill that keeps growing

Cloudinary gates your media.
Uploadcare does the same.

I was paying $90/month for Cloudinary.

For what?

Resizing images
Processing a demo video
Adding watermarks
Optimizing formats

The Solution

Openinary is what I built.

A self-hosted, open-source alternative to Cloudinary, focused on simplicity and control.

What it does

Self-hosted, runs on your own infrastructure via Docker
Simple URL-based API
- Example: /w_1500,h_500,f_avif/sample.jpg
Smart caching with invalidation
S3-compatible storage
Works with AWS S3, Cloudflare R2, MinIO
Automatic format optimization
- WebP, AVIF, best format per browser
Open source, AGPL-3.0 license

Why It Matters

The self-hosted movement is real.

People are moving away from SaaS lock-in, especially for core infrastructure.

Until now, one piece was missing:

You couldn’t process and deliver media at scale on your own infrastructure.

Openinary aims to fill that gap.

Current Status

⭐ 83 GitHub stars
🔥 Featured on GitHub Trending (Dec 9)
🎥 8,000+ views on the feature video
🎯 Goal: 100 stars by Dec 31 (yes, I’m chasing this 😅)

Tech Stack

Runtime: Node.js
Deployment: Docker, one command
Storage: S3-compatible (AWS, Cloudflare R2, MinIO)
License: AGPL-3.0

Try It

GitHub:
https://github.com/openinary/openinary
Deploy guides:
- Deploy on Coolify
- Deploy on Dokploy

Looking For

Early feedback, especially from Cloudinary users
Ideas on what to build next
Help spreading the word before the end of the year

If you’ve hit the wall with expensive image services, or wanted to self-host but couldn’t find a solid solution, I’d love to hear from you.

Questions?

Drop them in the comments.
Happy to discuss the architecture, use cases, or why I built this instead of using existing solutions.

DEV Community: Florian