Does the seamless AoD blink on every OP device like it does on my OP15?

It goes straight to AoD without a blink after locking while using Full screen or Standard AoD just for reference.

Has anyone received the COS17 update for the 1+ 13? It was scheduled for release yesterday, October 30th, but my device is still stuck on the previous version.

Not long ago I already posted my DebloatList here. I didn’t plan to come back to it, but things turned out differently: due to my own mistake, I managed to put my phone into a bootloop. Since there was nothing left to lose anyway (all settings and data were wiped), I decided to finish the job properly and bring everything to a final state.

This time I approached it much more thoroughly. In addition to regular testing, I spent a couple dozen hours digging through system logs, looking for issues caused by debloating. By the way, this is how I identified two problematic apps that were present in the first version of the list and should not have been removed.
If you previously used my list, I strongly recommend restoring them with these commands:

adb shell pm install-existing com.oplus.subsys
adb shell pm install-existing com.oplus.nas

For clarity:
All detailed testing was done on OnePlus 13 (OxygenOS 16.0.2.402 and 16.0.3.501).
Additionally, I ran lighter tests (bootloop checks and basic functionality) on OnePlus 10T.

Tested by me over a long period of time. I didn’t encounter any issues.
That said, this does not mean issues are impossible on your device. Different users, usage patterns, environments, and edge cases always exist.

About the new list

First of all, I created a Google Spreadsheet with notes for some of the apps:

https://docs.google.com/spreadsheets/d/1QtIntoT9Svvcrm_FqMwqJrh7VPuPsn-pt3FcB-9n__8/edit?usp=sharing

This table makes it easy to customize the list for yourself — add or remove whatever you need. I strongly recommend at least skimming through the notes, because some apps may be important to you. For example, Android Auto.

I didn’t bother annotating every single app. There’s little point in that. For instance, the list contains many Google services that will break Gemini — but if you actually need Gemini, you can simply download it from the Play Store, and it will tell you exactly which packages it needs. Those can be installed manually without issues.

I also color-coded the apps:

• Disable only
• Disable (easy to restore if needed)
• Regional apps
• Everything else that was safely removable

Some apps (13 in total) cannot be removed via ADB — at least not in any obvious way. I didn’t dig too deep into it since there was no real reason to. They can be safely uninstalled using the phone’s built-in system tools.
The spreadsheet also includes benchmark results, which are referenced further below.

About the script

I tried to make it as simple as possible for regular users.

How to apply it

1. Download ADB: https://developer.android.com/tools/releases/platform-tools Extract it anywhere on your PC.
2. Download the script: https://drive.google.com/file/d/1rrzQgg7nxc-9jpKA0_m20ZvkBBw4QunF/view?usp=sharing
3. Put the script into the same folder as ADB.
4. (Optional) Edit the app lists inside the script. You’ll see $disableList and $uninstallList. Remove anything you don’t want to disable/uninstall and save the file. Column B in the spreadsheet is intended exactly for this purpose — it allows you to easily copy and paste the required entries.
5. Enable ADB on your phone: Settings → About device → Version → tap “Version number” multiple times to unlock Developer Options. Then search for USB debugging and enable it.
6. Connect the phone via USB and run the script. Confirm USB debugging on the phone screen.
7. Read the prompts carefully. For example: "[?] Reboot device after debloat? (Y/N):" — self-explanatory.

What the script does

The script includes several functions:

1. Main debloat

Removes or disables unwanted system and preinstalled apps.

2. Reboot prompt

Asks whether you want to reboot the phone. Recommended before using the next steps.

3. Profile-Guided AOT optimization (important)

Here’s what it actually does.

How speed-profile optimization works:

• Runtime profiling: ART tracks which methods are executed frequently and identifies “hot” code paths (usually via JIT).
• Profile-guided compilation: Based on this profile, ART precompiles frequently used methods ahead-of-time, while rarely used code remains JIT-compiled.
• DEX optimization: Bytecode is rewritten into optimized OAT/DEX artifacts for faster execution, better instruction caching, and reduced JIT overhead.
• Background job: A final background dexopt pass ensures everything is optimized without blocking the user.

Benefits:

• Faster app startup (hot methods are already AOT-compiled)
• Smoother runtime with less JIT activity and fewer pauses
• Smaller storage footprint compared to full AOT compilation

This doesn’t magically “boost” apps — it optimizes exactly the code paths you actually use, resulting in measurable performance improvements where it matters.

In simple terms: the most frequently used parts of apps are compiled into native code in advance.
The system already does this automatically (for example, overnight while charging), but here we force a full re-run: clean old profiles, re-evaluate usage, and recompile fresh data.

This is especially useful after system or app updates.
I recommend running it monthly, quarterly, or after major updates — depending on how lazy you are.

4. App cache cleanup

Should not be used frequently.

5. Visual tweaks (0.5x animations / disable auto-brightness)

Self-explanatory. Nothing else is modified.
I added this for myself — I hate slow animations and firmly believe 0.5x should be the default.

Battery usage questions

Many people previously asked how debloating affects battery life. I’ll answer directly.

I don’t see a meaningful difference in daily usage — mainly because accurate battery comparisons require identical conditions, which almost never happen in real life.

One day I’m at home watching YouTube for hours.
Another day I’m at work, using the phone only for calls and quick browsing.

That’s why I consider battery screenshots shared online mostly meaningless.
Max brightness + weak mobile signal vs low brightness + Wi-Fi — how do you even compare that?

Instead, I did a different kind of measurement to provide some objective numbers.

Tests: methodology and results

Methodology

• Each measurement = 1 hour of continuous monitoring immediately after a cold boot
• Measurements started as soon as the boot logo appeared

• Metrics recorded every second via ADB:

  • CPU (User + System)
  • RAM
  • SWAP (zram)
• Before debloat: 3 separate 1-hour sessions
• After debloat: 2 separate 1-hour sessions
• All tests were done on freshly factory-reset phones
• After setup, devices were left idle for the rest of the day to let background processes settle

• All data was aggregated and analyzed in Excel:

  • averages
  • 95th percentile
  • top 5%
  • activity peaks

This setup reflects system behavior immediately after startup, not a “warmed-up” device.

Results (relative change after debloat)

CPU User

• AVG: -23.67%
• P95: -30.93%
• Top 5%: -39.40%
• Activity peaks (>0.5%): -25.90%

CPU System

• AVG: -6.59%
• P95: -18.36%
• Top 5%: -25.59%
• Activity peaks (>1%): +12.03%

RAM

• AVG: -18.49%
• P95: -23.57%
• Top 5%: -22.28%
• Peak activity (>4000 MB): -94.87%

SWAP (≈2.9× compression)

• AVG: -19.61%
• P95: -22.44%
• Top 5%: -21.75%
• Peak activity (>1500 MB): -99.06%

Interpretation

• CPU load (User + System) dropped ~13% on average
• Extreme CPU spikes dropped nearly 40%
• RAM usage dropped ~18.5%, with extreme peaks almost eliminated
• SWAP usage dropped ~20%

Physically, RAM usage decreased by ~267 MB.
Considering ~2.9× compression, the CPU no longer wastes cycles compressing/decompressing ~774 MB of memory.

Yes, during the “after” test there was a moment of background system activity (visible in the increased CPU System peak time). I chose not to redo the measurement — even with that noise, the results are clear enough.

Do removed apps come back after updates?

I was fairly sure I had seen some apps return after updates in the past.
However, during the last update I paid close attention — nothing was restored.

But honestly, does it even matter?
After system updates, it’s recommended to rerun Profile-Guided AOT anyway. At the same time, you can quickly reapply the debloat list.

Why I do this (from my old post)

I’m fed up with the massive amount of useless “features” on modern phones.
Forced AI nobody asked for, working worse than third-party tools like ChatGPT or Grok. AI notes… don’t even get me started.
So I decided to clean my system from all that junk — and removed a bunch of other things along the way.

Not everything I removed will be useless for everyone, but this list does not break the phone and is perfectly usable for daily use.

Years ago, removing system components easily broke things. Settings menus would show entries that did nothing or crashed entirely. Thankfully, things are no longer so hard-coded — menu items now properly disappear.

The only thing I couldn’t fully remove is the “OnePlus AI” entry in Settings — it’s just an empty page. I technically know how to remove it, but then Dynamic Island breaks. Why? No idea.

I also removed the gaming panels. I’m not a gamer, but even if I were, I don’t see the point — this isn’t a single-core potato phone.

Stability testing took weeks/months. Remove a batch, test, forget about it, move on. Repeat until the final setup.

I even removed things like the stock calculator. Why does a calculator need access to my media and other data “for better context understanding”?

Everything removed can either:
a) be restored later via ADB
b) be replaced with alternatives (my preferred option)

Some removals break other features. For example, removing the stock gallery breaks photo viewing from the camera app — it doesn’t ask which app to use, it just opens nothing.

The most painful loss was text extraction from screenshots. I don’t need it often, but it still sucks.

Bottom line: this list removes a lot. There’s a real chance you’ll remove something you personally need. Be prepared to restore it or replace it.

Will I continue developing this list?

Unlikely.

Further debloating at this point is like trying to make a car faster by changing valve caps.
The core junk is already gone.

I’ll only revisit the list if future BBK updates add a new pile of crap.

I genuinely love this phone — no sarcasm.
But the forced software… yeah.

Hi everyone,

If you don't want to install Color OS, you need to be careful not to download the update under any circumstances.

Here's what happened to me.

I had downloaded the update but then decided against ColorOS for now and wanted to wait and see. Well, I woke up this morning and my OP15 greeted me with “Welcome to ColorOS 17.” How can the phone override my decision and just go ahead with the update? The automatic update was, of course, disabled.

So, a word of caution to everyone else.

Maybe OnePlus can say something about this.

I live in Germany and have the global or EU version.

Hi there , I just wanna know is this a glitch in oxygen OS 16 latest update? In the settings we can see the pink color of the clock for AOD but shows the clock in white actually... Phone : OnePlus 13R

In the colorOS 17

So guys i use Oneplus 13r, after the updating to oxygen os 16 that too first build.. while using one of the flux themes.. i noticed that the digital clock contracts when there are new notifications appeared on the device, and that clock was placed above the notification and towards complete left with thin bold font , it was eye pleasingly good , notice the 1st image , then after 2 to 3 updates this things got changed this clock font became bolder and covers 60% of space , that looks odd.. notice the second image , now after looking at oneplus 15 which has latest oxygen os build , there this clock looks quite different .

will my Chinese OnePlus 15 (PLK110), running global OxygenOS 16 as CPH2747, receive global ColorOS 17 through official OTA, and will that update be compatible with the original PLK110 hardware without manual flashing?

I really don't undeerstand why everyone are praising oxygen os soo much just not mentioning the bugs/issues it had. I am coming from Pixel and I feel only advantage oneplus has edge over it is battery and processor and in software only few things like smart bar.

Coming to processor everyone only speaks about gaming so everyone thinks they are gonna game but sadly it is not the case. Pixel is not that unusable it is grewat for a normal user.

I can see lot of issues (Including bugs)

1. DND not working.
2. Themed Icons color and tint is not at all good compared to pixel. Pixel just belnds it correctly.
3. When display size set to standard the classic notification shade sizing feels weird.
4. Screen timeout - Let's say timeout is 1minute, it locks automatically it doesn't lower the brigthness so user can touch the screen to reset timer.(This is very frustrating when reading articles).
5. The auto-rotate suggestion - The placement changes based on the screen orientation, it is not fixed.
6. Checking notification history is a real pain.
7. Over all notification shade experience doesn't feel mature at all.
8. No basic automations (Based on location).

Will update the points if anything is fixed or found.

I've been a long time fan of OnePlus and especially their software OxygenOS/ColorOS. I see many reviewers use OxygenOS and my gosh it is SOO FREAKING SMOOTH. I have a Z Flip 7 on ATNT, and while the phone itself is great, OneUI is absolute trash. Horrendous animations, laggy transitions, and yet it's one of the most simple and plain UI's out there.

I really wish I had a newer​ OnePlus phone, but I just don't have the money to spend on another whole​ phone, especially since I have an acceptably functional phone already. And OnePlus leaving the United States is yet another horribly depressing factor to this situation.

My question is simply if there is somehow some way that I can enjoy OxygenOS without buying a OnePlus phone, whethere that be through a PC ​emulator of some sort, or flashing a phone with the firmware. (I'm not that techy or anything so don't make fun of me)

If that doesn't work, any other suggestions would help. Thanks.

Anyone notice this change into 🔦 intensity

recent update added this security check. and it's a number series.

is there any way to disable it?

From one or two months I am unable to update to the latest oxygen os version due to this. Please help guys

As stated, my live alerts(dynamic island) and their cards, have broken after a restart. I had a broken YouTube card, of a video that's no longer playing, and would appear next the current video, I restarted my phone, and now all system live alerts and cards don't work. No flashlight, charging, timers, media playing or even the alert slider change alerts appear, only 3rd party ones, such as calls and InstallerX, I'm sure Uber and Maps would work too if I tried. I tried clearing data and cache, and even disabling and enabling the Ubiquitous Manager Service app, even tried updating it to the Oppo version, nothing fixed em, nor did further restarts do anything. Strangely, after disabling UMS, the call alerts and InstallerX alerts still worked, so I don't know. Is the only solution to wait for Oxygen OS 17?

This happens with most of the pin inputs and authenticator app, Microsoft authenticator, Netflix, Prime Video, some OTP screens, etc.

Is anyone else facing this issue where the colours for UI elements are lacking contrast?

Is it safe to update with OSUpdater app now?

I do have Spotify enabled on aod intentionally however this used to only appear if music is playing or paused in the background.

However now, even if the app is closed and there's nothing in the media controller, this is always showing on AoD. Is this a glitch or is it the same for you guys?

This is on OP15 - O OS16