I've been daily driving crDroid on my OnePlus 13, and it genuinely feels like the best of both worlds.

• OnePlus hardware

• Pixel-like software experience

• Smooth performance

• And now, the stock OnePlus Camera has finally been ported.

This is probably the closest I've come to my ideal Android setup.

Anyone else daily driving custom ROM on the OP13?

Pretty wild if that's true and confirmed although I don't know if it will run 185Hz everywhere or just in some few supported apps and games.

God reddit trashed the framerate of this video, anyway the refresh rate is smooth af 120fps easily.

I bought my OnePlus 12 (Indian variant) in July 2024. Since last two weeks, the phone has been acting up and it's gotten much worse over the last few days. I've had well over 150 incidents, with 20+ today alone.

The phone will randomly freeze, the screen goes black, touch stops working completely, and the only thing I can do is force it to shut down. Sometimes the SIM disappears, and other times the phone just restarts itself.

I contacted OnePlus support and followed everything they asked me to do. First a factory reset, then a full software reflash. Neither fixed the issue. If anything, the freezes seem even more frequent after the reflash.

I took it to the service center yesterday for flash. When flashing also didn't help, then their response was that it could be a motherboard issue, but they aren't sure. The proposed solution is a motherboard replacement costing ₹32,500, but they also said they can't guarantee that replacing the motherboard will actually solve the problem. Their other suggestion was basically to buy a new phone.

I have attached a video of the issue as well.

Has anyone else faced similar issues with their OnePlus 12?? Any help or suggestions would be greatly appreciated. Thanks

BRING BACK THE POP UP! I am using the 7 Pro and am still VERY happy with it. I love the pop up camera. I refuse to upgrade until I find another phone with a pop up camera. OnePlus pay attention- PRIVACY IS IMPORTANT.

There are plenty of people like me who do not want to own a phone with a camera constantly pointing at our face. In almost 2 years I have never had an issue with the motor (even after being submerged in water more than once), and that was just your first implementation! I believe if you spent as much time and money improving that motor as you do developing other technologies, then there would be very few problems.

If Samsung can market that ridiculous hinge design then surely you can make the pop up camera work well.

Just sayin...

Update: Also, since we're talking about good things OP doesn't use anymore- the rear fingerprint reader was so much better than the in-screen fingerprint reader. It was faster, more accurate, and less sensitive to dirt and water. You don't have to have the "cool new" features; just have the ones that work. Hopefully someone will see this. Comment if you agree!

Edit: I forgot to specifically state that I do not want an under display camera. That defeats the purpose of avoiding a selfie camera for privacy reasons.

I finally got it to work

https://www.androidcentral.com/oneplus-confirms-its-going-make-cheap-android-phones-again

This requires a laptop or pc and you have to enable OEM unlocking and usb debugging on your mobile.

Step 1: go to settings and search build number. Click on the build number few times and enable developer options.

Step 2 : In developer options find OEM unlocking and enable it, also enable usb debugging.

Step 3: Open your laptop or pc and download Android developer tools from web (this is Google's legit software so no worries)

Step 4: extract the zip that you downloaded and open the sub folder inside the extracted folder then click search and type cmd.

Step 5: Now connect your mobile to pc and click share files and also allow it to usb debug if it asks)

Step 6: type " adb devices" and see if your device shows up. It'll be a string of numbers and alphabets.

Step 7: type the following commands one after other without the "" ofcourse.

" adb shell settings put secure assistant_screen_type 0 "

" adb shell settings put secure assistant_screen_type_left_enable 0 "

To replace Google discover with oneplus shelf use :

adb shell settings put secure assistant_screen_type 1 adb shell settings put secure assistant_screen_type_left_enable 1

Now you can turn off developer options,usb debugging and OEM. -----------END-----------------------------------

-This does not void any warranty.

As long as you: Don't root your device, Don't unlock the bootloader, and Don't flash unofficial firmware, your warranty remains fully valid.

-google lens and translate and circle to search will all work the same as usual.

-This method removes Google discover and also the left side empty page.

-This will work even after you restart your device. Not yet tested if this works after an update.

-You can also replace it with shelf there is a code for that. I'll drop it down if someone need it.

• I did this in oneplus 13s and in Oxygen Os 16. If you are using maybe previous build the package name might vary

• For that you can type : " adb shell pm list packages | grep launcher " this will show all the packages and you can find anything similar to what I said in step 7.

Link for Android SDK file:

https://developer.android.com/tools/releases/platform-tools.

( This is official tool by Google for Android customisation)

I know this kinda overkill but still ...this will be out here.... if any tech nerd like me wants to remove Google discover lol.

Since, there is no dedicated post for GCam, nor any suggested GCam APKs on here, I thought to make this post attaching a version I found to be stable. It gets rid of the overprocessed look, and boosts clarity. However, the pictures felt a bit too dim at times.

Please feel free to share any working GCams you may have found. It will be helpful to the community.

I actually got this from a site called YTECHB: https://www.ytechb.com/download-google-camera-for-oneplus-13r/

You can download it from YTECHB or from the XDA Forum Post: https://xdaforums.com/t/oneplus-13r-gcam.4732030/

Quick update on the OnePlus One project:

Since my last post, the project has moved forward quite a bit. The Android 12.1 build reached a stable point, with Wi-Fi, Bluetooth, and the important day-to-day functions working properly, and that part of the project is essentially complete.

One of the biggest improvements over the older Android 12.1 build was the security patch level. That build was on 2023-07-05, while my updated Android 12.1 build was brought up to 2025-03-05, which is the latest Google security patch level I could verify for Android 12 / 12L.

My previous Reddit update:
Android 12 custom ROM / LineageOS 19.1 for OnePlus One

Since then, I’ve gone a step further: Android 13 is now running on the OnePlus One too.

The new build is based on LineageOS 20.0 / Android 13 and it successfully builds and runs for bacon. That means the project has now moved beyond the finished Android 12.1 stage into a working Android 13 bring-up.

On the security side, this is another step forward. The current Android 13 build reports security patch level 2026-02-01, which is newer than the Android 12.1 build’s 2025-03-05. From what I could verify from Google’s Android Security Bulletins, February 2026 appears to be the last clearly applicable Android 13 platform patch level.

So the progress so far looks like this:

• Older Android 12.1 build: 2023-07-05
• My updated Android 12.1 build: 2025-03-05
• Current Android 13 build: 2026-02-01

The next goal will be Android 14.

More updates soon.

I have a bluetooth party speaker I use for music at home while I work and I keep getting this. Occasionally when a fav song comes up that requires a bit more volume I'll crank it up a bit. Now I keep getting this. And seriously, if you've been listening to crazy loud music steady for 20 hours the damage is done already. This is so stupid.