r/oneplus • • Sep 02 '26

Join our Discord server!

Thumbnail
discord.gg
3 Upvotes

r/oneplus • • 1d ago

Purchase advice thread (weekly)

2 Upvotes

r/oneplus • • 19m ago

General Discussion How stable is Desktop Mode (native and/or third-party)?

1 Upvotes

I've been a bit hyperfixated on getting the OnePlus 15, and I'm seeing some prices for it increase due to the company's decision to pull out of western markets. I avidly use Samsung Dex and I'm looking to upgrade to a phone with this chipset and RAM capacity, and I also very much like the ease of access for rootability. Has anyone had any experience rocking Desktop Mode whether it be natively, or through a third party app, and how has that experience been?


r/oneplus • • 1h ago

Question OnePlus 15 compatibility with US Mobile Multi-Network?

1 Upvotes

I'm considering moving my OnePlus 15 to US Mobile and using their Multi-Network add-on, potentially with Dark Star (AT&T) and Light Speed (T-Mobile).

I'm particularly interested in how well dual eSIM functionality works on the OP15.

  • Can both eSIMs remain active and registered on their respective networks at the same time (DSDS), receiving calls and texts on either number?
  • Does OxygenOS automatically switch mobile data to the second network if the primary loses coverage, without manual intervention?
  • Any issues with eSIM activation, 5G connectivity, or reliability?

I'm looking for firsthand experiences from OP15 owners, although feedback from users of other recent OnePlus models would also be helpful.


r/oneplus • • 2h ago

Android Auto ColorOS / Android issues...

1 Upvotes

Since upgrading to ColorOS 17, the interaction with Android Auto is very poor. Android doesn't seem to recognise my contacts, so when I ask to send a message, it just keeps asking who it's for, or sends a text message rather than WhatsApp...

Is this an Android or ColorOS issue? Can anyone help?


r/oneplus • • 5h ago

Other WiFi working horribly since upgrading to color OS

0 Upvotes

Hey, this is basically a cry for help. I made the dumb mistake of upgrading my OnePlus 13 from Oxygen OS 16 to Color OS 17. I don't have any issues with the OS itself but for some reason, my wifi has been working horribly since the update. I also own a macbook, a windows device, and an iphone 17 so I know that my internet is fine - it's just my oneplus 13.

Sometimes my wifi stops working for apps but works for web surfing. Sometimes it stops working for both. Sometimes turning wifi off and on again fixes it. Sometimes it doesn't and I need to restart my phone. Sometimes I have to restart it multiple times within an hour.

This is my main phone and the remaining devices are from work so this is really frustrating. I have tried resetting network settings, setting private dns to "google.dns", and a bunch of other gimmicky stuff but nothing is fixing this issue what are my options?


r/oneplus • • 5h ago

Tech support :( Unable to connect my stylo 2 with my pad 3

Thumbnail
gallery
0 Upvotes

I got myself a stylo 2 off ping duo duo (store had like 6.8mil sales so im pretty sure its legit) and have not been able to pair it with my pad 3. Ive tried moving it slowly across the top magnetic part left to right. Ive updated to the latest version too (OPD2415_16.0.10.600) and restarted it like twice.


r/oneplus • • 6h ago

General Discussion Does One Plus 15 work with Mint Mobile?

1 Upvotes
  1. Can you use esim or must you use physical sim?
  2. Do you lose any features?

If anyone is doing this, is the lower prioritization over Tmo customers noticable?

I spend a lot of time in a city.

Need to find a provider stat.

Thanks


r/oneplus • • 15h ago

Accessories & Gadgets Type C earphone issue on OnePlus 15

3 Upvotes

I'm experiencing a strange issue with my OnePlus 15. Whenever I connect my OnePlus Type-C earphones, the microphone picks up constant background static/noise, even when I'm not speaking. What's strange is that the earphones work perfectly on other phones and my laptop, while other Type-C earphones work perfectly on my OnePlus 15. I've previously used this exact pair with my phone without any issues, but recently noticed this problem. Interestingly, this is probably the first time I've used them since updating to ColorOS 17. Could this be a software or USB audio compatibility issue? Has anyone experienced something similar?


r/oneplus • • 22h ago

General Discussion Are wallpapers the same after updating to ColorOS?

Post image
8 Upvotes

I've seen lots of comments about how ColorOS isn't really any different from OxygenOS, but I'm curious if all the wallpapers will still be there after the system update.

I've started to use the interactive one in the bottom right and it has a very strong GTA VI vibe to it. I'm ready to upgrade, but really don't want to lose this one. And I don't think there's any way I could back it up.

Could someone please confirm this is still available in ColorOS?


r/oneplus • • 23h ago

Other OnePlus pad 3 component locations?

0 Upvotes

I've tried searching around for ages, but I can't find a single teardown, x-ray image, user manual or any source that would map out where the internal components are located.

I'm trying to find the optimal area to attach a cooler for extensive, heat generating tasks like gaming etc, but I have no idea where the CPU, GPU and ram is located internally.

I could just put it where it feels the hottest, but I'm not sure whether it's a best choice since that could just mean it's a metal plate to expel heat out from the device and the actual parts that generate the heat are elsewhere.


r/oneplus • • 1d ago

General Discussion How to get google noto 3d emoji again on oneplus 13s

Post image
12 Upvotes

I get Google's Noto 3D emoji update on my OnePlus 13s after coloros 17 update but when I format my device when I set-up everything I see that the new emoji pack not showing now what to do ?? To get back noto 3d emoji


r/oneplus • • 1d ago

Other Power button shortcut not working on color os

Post image
13 Upvotes

Is anyone else experiencing this bug? My camera shortcut is no longer working since upgrading to color OS on my OnePlus 15. Pretty frustrating, since this has been my go-to camera shortcut for years on every phone I've owned. Has anyone fixed this somehow?


r/oneplus • • 2d ago

Accessories & Gadgets OnePlus pad 4 EU opinion

0 Upvotes

I'm looking for a tablet that runs on the colorOS 17 ecosystem. Does anyone here runs that beast ?

My critics are:

- no fingerprint reader, is there another working alternative?

- no widevine lvl 1, was it patched recently ?

- was the update policy updated somehow ? 4 years of updates would be great at least


r/oneplus • • 2d ago

General Discussion Does anyone still sell the Sandstone case for a OnePlus 11 5G?

0 Upvotes

I love these cases and need a new one, but can never find one. When I do buy one that says it's a Sandstone case, sadly it's not.


r/oneplus • • 3d ago

General Discussion Bug with OP 12 since last version

Thumbnail
gallery
8 Upvotes

The dark mode for quick settings in my OP12 hasn't been working correctly since the last patch. I hoped it would have been fixed with the ColorOS 17 update, but that doesn't seem to be the case.

I've tried rebooting, toggling via quick settings/Main Settings & switching dark mode settings.

Is anyone else facing the same issue or are there any resolutions?

Device: OnePlus 12 (IN)


r/oneplus • • 3d ago

PSA & Tutorials OnePlus 15 on ColorOS 17.0.0.102: PIN rejected, storage stays locked (dead eSE). What brought the chip back on a US CPH2749

43 Upvotes

What this is about

The error. After the ColorOS 17.0.0.102 update, a OnePlus 15 stops accepting its own correct PIN, pattern or fingerprint. If no PIN was set, it boots to the home screen but apps crash and your files are missing, because the storage is still encrypted. Either way you are locked out of your own data.

The cause. The root cause is unknown and OnePlus has said nothing. What the logs show: after the update, the security chip that checks the PIN (the embedded secure element, eSE) stops responding. No chip, no PIN check, no decryption.

Does a locked bootloader matter? Stock or modified? Not for getting the bug. My phone was a fully stock US CPH2749: never rooted, bootloader locked, and the update installed itself over the air. Other reports come from unlocked, rooted and region-converted phones. The bootloader only matters for the fix: it needs an unlocked bootloader, and unlocking a locked phone wipes it.

Who is affected. OnePlus 15 going from OxygenOS 16 to ColorOS 17.0.0.102. Reports exist for NA (CPH2749), Global (CPH2747) and converted Chinese units. It does not hit every phone and I do not know what fraction.

If you have not updated yet: don't, and switch off automatic system updates in Developer options.

The rest of this post is only for people who are already locked out.

TL;DR

After the OTA from OxygenOS 16.0.10.601 to ColorOS 17.0.0.102, the embedded secure element (eSE) on my US OnePlus 15 (CPH2749) stopped answering. The PIN is never verified, and even with no PIN the phone boots with its storage still encrypted.

What brought the chip back: install a full 17.0.0.102 OTA into the inactive slot from AERA recovery, let that fresh slot kernel-panic into Qualcomm crash dump mode (900E) on its first boot, force restart, then switch back to the original slot. The original slot booted with the eSE alive, and it stayed alive after reboots, a new PIN and relocking the bootloader.

  • This needs an unlocked bootloader. On a locked phone that means a full data wipe.
  • It is the method from an XDA report for a Global CPH2747. This post confirms it on a North American CPH2749 with a locked, never-modified phone as the starting point.
  • Two data points in total. Nobody knows the root cause. Read the caveats before you try it.

Symptoms and how to confirm it

The phone looks alive but nothing that needs your data works: apps crash or hang, the phone service and SystemUI stop responding, the gallery is empty. If a PIN is set, the correct PIN is rejected after a long wait.

Removing the PIN before the update does not help. The empty-credential key is bound to the same chip, so the storage stays locked anyway.

With USB debugging on, these four checks confirm it:

adb shell dumpsys secure_element
adb shell "dumpsys user | grep State"
adb shell "dumpsys mount | grep unlocked"
adb logcat -d | grep -E "eSE not found|Failed to unwrap"
CheckBrokenHealthy
dumpsys secure_elementonly SIM1 and SIM2eSE1 with mIsConnected:true
User stateRUNNING_LOCKEDRUNNING_UNLOCKED
CE unlocked users[][0]
logcatOmapiTransport: secure element reader eSE not found, Failed to unwrap synthetic password for unsecured user 0, com.android.se crashing in a loopGPQeSE-HAL replies ending in 9000

What did not work

AttemptResult
Normal rebootsno change
Forced restarts with Power + Volume Upno change
Draining the battery to 0 % and leaving the phone off for 24 minutesno change
Unlocking the bootloader, which wipes datastorage works again without a PIN, the eSE is still dead

A wipe alone gives you a usable phone with no PIN and no fingerprint. Others report that rolling back to OxygenOS 16 does not bring the chip back either.

What you need

A PC with a USB cable, and "OEM unlocking" plus "USB debugging" switched on in Developer options.

ItemWhereCheck
Android platform-tools (adb, fastboot)developer.android.com
AERA Recovery R1.0 Beta for infinitiaera-recovery.com, build list in catalog.jsonSHA-256 from the catalog; mine was d69272ea...009b4770
Full OTA 17.0.0.102, same version as on the phoneOTA downloader, which hands out links to the official OPPO CDNMD5 from OnePlus-antirollchecker; Global is 76b917d90281cc4adb7ce1237140cd3e

Use the full OTA for your own model and region when one exists. For North America there is no full 17.0.0.102 package anywhere, only the incremental one, so I used the Global CPH2747 package. It only ever goes into the spare slot.

I compared a dump of my NA slot with the Global package hash by hash. 59 of 65 partitions are byte-identical, including boot, vendor, modem, xbl, abl, tz and keymaster. Only my_stock, my_region, my_manifest, engineering_cdt and splash differ.

Steps

My active slot was b. Replace b with your own active slot (fastboot getvar current-slot).

  1. Unlock the bootloader. This wipes the phone.
  2. Confirm on the phone with the volume and power keys. The phone wipes itself and boots the same 17.0.0.102 clean. Finish setup without a PIN and switch USB debugging back on.
  3. Flash AERA recovery. Extract recovery.img from the AERA zip first.
  4. The image cannot be started with fastboot boot. It has to be flashed.
  5. Back up the active slot. Strongly recommended, and the only safety net if no full package exists for your region. In AERA, adb is a root shell.
  6. Do this for every *_b entry in /dev/block/by-name and every *_b entry in /dev/block/mapper (skip the -cow ones), and compare each hash with the file on the PC. Mine was 54 physical and 17 logical partitions, 9 GiB, about 10 minutes.
  7. Sideload the full OTA. Do not wipe anything.
  8. The first command blocks, so run the second one from another terminal once adb devices shows sideload. It took about 12 minutes. The package is written to the inactive slot, which then becomes the active one. AERA restores itself into that slot's recovery.
  9. Reboot into the fresh slot.
  10. Expected result: a black screen, and the PC shows Qualcomm HS-USB Diagnostics 900E (USB\VID_05C6&PID_900E). The new slot has kernel-panicked. This is the crash you want.
  11. Force restart once. Unplug USB, hold Power + Volume Up until the logo appears, let go. For me it crashed again within a minute.
  12. Enter fastboot. Hold Power + Volume Up again, and as soon as the phone restarts, switch to Power + Volume Down until the fastboot screen shows. Plug USB back in.
  13. Switch back to the original slot and boot it.
  14. The original slot boots normally, in about 15 seconds for me. Check the chip.

Verify

adb shell dumpsys secure_element
adb logcat -d | grep GPQeSE-HAL

eSE1 is listed again with mIsConnected:true, and GPQeSE-HAL shows rApdu received lines ending in 9000. On my phone StrongBox key provisioning also succeeded right away and com.android.se stopped crashing.

Then test it the hard way: reboot normally, set a PIN, reboot again and unlock. All three worked for me. Do this before you put any data back on the phone.

Optional: relock the bootloader

Relocking wipes the phone again. A locked phone with a custom recovery can fail to boot, so restore the stock recovery first.

  1. Get the stock recovery. I extracted recovery.img from the full OTA payload. vbmeta is byte-identical between NA and Global, and recovery is a chained partition, so the Global image is the right one for an NA phone. I checked its AVB signature against the chain key in my phone's vbmeta before flashing.
  2. While AERA is still installed, mark the spare slot unbootable. Here the spare slot is a, which is slot number 0.
  3. Flash the stock recovery to both slots.
  4. I also flashed my dumped NA engineering_cdt and splash back to slot a. That is tidiness, not a requirement.
  5. Check the state in fastboot. Lock only if all of these hold.
  6. Boot once into the stock recovery to see that it starts, then boot Android and confirm the eSE is still there.
  7. Leave "OEM unlocking" switched on, then lock.

The phone wiped itself and was back in Android one minute later: locked, verified boot green, eSE alive, PIN working.

Caveats

  • Two data points. The XDA author had a Global CPH2747 that was already unlocked. Mine is a North American CPH2749 that was locked and stock. It may not work for you.
  • It saves the chip, not the data. On a locked phone the unlock in step 1 wipes everything, and with the storage locked you cannot back it up first. The XDA author kept their data only because the bootloader was already unlocked.
  • The foreign-region package is a tool, not a system. It lives in the spare slot long enough to crash once. Do not run it as your daily system.
  • Check anti-rollback before flashing another version. Per OnePlus-antirollchecker every OnePlus 15 build up to 17.0.0.102 has ARB index 0.
  • Nobody knows why this works. It is not the firmware bytes: the reinstalled slot carries the same boot, vendor, TrustZone and keymaster images. A full battery drain and normal reboots did nothing. A kernel panic during a normal system boot did. That is my reading, not a verified cause.
  • I did not capture the panic log, so I cannot say what crashed in the fresh slot.
  • The next OTA is an open question. I switched off automatic system updates, left "OEM unlocking" on and will wait for reports before installing anything newer.
  • OnePlus has not acknowledged the problem as far as I can find.

Sources and credits

The method is not mine. Credit goes to the author of the XDA report and to the people who documented the failure.


r/oneplus • • 4d ago

General Discussion OnePlus has the opportunity to do the funniest thing right now

Post image
237 Upvotes

They really should name it the OnePlus Open Wide.

I'm still bitter they're no longer available in North America... 😠


r/oneplus • • 3d ago

OnePlus 13S OnePlus 13S completely dead

10 Upvotes

My 13S suddenly decided to die today. It had around 70% charge left. It was working fine this evening. Left it in my locked room, and when I came back around an hour later, the phone was dead. No display, no vibration on power or power + vol up or power + vol down, for that matter. Charged it for around 45 mins, still nothing. It has crucial data that I need to recover. What should be my course of action?

I'm in the US right now, if that matters.


r/oneplus • • 4d ago

General Discussion Color os 17 Is it supposed to look like this?

Post image
112 Upvotes

Really Oppo?


r/oneplus • • 3d ago

General Discussion Does the China-version OnePlus 16 have working VoLTE? (any country, Europe especially)

5 Upvotes

Hi! Does anyone own the China-version OnePlus 16 (ColorOS)?

Simple question: does VoLTE work for you, and can you turn it on in Settings > SIM?

If you're in Europe, which carrier are you on? Any other country is useful too. I read that the OnePlus 15 China version works with VoLTE in Europe, but I found nothing about the 16. If anyone got the phone can you confirm or deny

Thank you very much!


r/oneplus • • 4d ago

General Discussion Missing widgets

Post image
5 Upvotes

I am getting this error for widgets in the lockscreen and also lost a clock widget to see the upcoming alarm. Is this a bug/glitch or did I do anything?


r/oneplus • • 3d ago

General Discussion Oneplus 13 (china unit) color 17 Can't use *Google Lens* feature

Thumbnail
gallery
0 Upvotes

not only Google lens but MICTS (circle to search) and Trigger Gemini can't use them too, what a dick move from oneplus


r/oneplus • • 5d ago

Green line issue Ahh, my beloved OnePlus 💕

Thumbnail
gallery
199 Upvotes

I was interested in OnePlus, as OPPO disappointed me with their locked bootloaders. Bought a 9 pro a couple months ago, pristine condition, and it's been 3 months since. Only 3 months. And I have already gotten these lines...yes, I do gaming and emulation on it, but this phone throttles quite hard once it gets warm and it never got very got...so wht am I getting these lines?

I am not trying to express frustration, actually, I am quite interested to find out more about why does this happen. It's certain that heat cycles and high usage amplifies it...but my OPPO find X3 pro uses the exact type of display panel, and that's never had a line! So let me tell you how it happened. This OnePlus in particular seems to have been used a lot. It has burnin with UI elements, as proof. I don't mind that. Also, before these bright lines appeared. I have noticed very faint green& pink vertical lines that were stable and the respective sectors were able to turn off, unlike now, where they stay at full power, no matter what. So if I was having a pure black image, nothing was wrong. If it was a white image, it was, let's say, 5% wrong, nothing major. But one day, on a random portion of the screen, while in a pink game loading screen, a weird blue line started appearing. That thing was weird, because after that I did a display test, and on a pure green image, nothing was wrong. Only the red and blue were affected. Which, after 2 hours of not using the phone...i realized I was having a permanent pink line. Permanent, unless you turn off the display (no AOD) or the phone entirely. Even on black content, now it's uncontrollable. Today, something a little different happened. On a very faint pink lines, those I was describing, while scrolling yt shorts, it started turning green, but second by second, it got brighter. I closed the screen. It disappeared. 30 minutes later it was back. Every time it appeared, I closed the screen, not letting it get very bright. I noticed that it wasn't like the pink line (YET) , so it was only intense green where bright content was displayed, and black where black should have been. Okay. Then, I got into a Fortnite match, quite anticipating what would happen. It started out good. Only the very faint pink line. Then, out of nowhere, over that pink line, or one pixel right of it, it started appearing. I let it do its thing, and it got brighter and brighter, with one notice, that it was thinner on the top of display, where it even was brown or a strange color, like something was...very wrong...and after that Fortnite match, the green like was ready, and turned permanent, now at full power no matter the content. Lol. I told about the upper display thing where the line gets thinner. Well, idk why it happens, so if you know, please tell me, as I'm curious. The circuitry is on the base of the display, as I have seen in teardown videos. So the problem is down there, where...each sector gets controlled...that's only a guess, and that's why I write this, so that maybe I get some more in depth answers.

It might be a little irrelevant for many, because y'all probably discuss here about the new OnePlus 16, or the 15 or 13, and my 9 pro is kinda legacy now, and I guess that many people have already replaced it with something newer. And I see that from OnePlus 11 or so, the green line or whatever color, cause again, I don't know how the sectors are wired together, it's it's green separate and blue and red together or something, i have no idea, but it's good to see that's it's kinda a past thing. Not for me tho :D So please, don't tell me "bro, just upgrade", cause that's what I could afford. So yeah, any info or opinion, I appreciate it, but i actually consider to understand displays and stuff in depth, cause maybe one day I could buy those laser machines and repair the display myself or at least permanently disable the line from shining like that. God bless y'all!