The menu appears to have been hidden on the more recent Android releases — currently on Android 14 the only per-app toggle the users are given is 'allow background usage' (app info → app battery usage). On my Oneplus 8T device the OS is actively stopping some apps designed to be running on the background at all times, such as Shizuku . On AOSP-based ROMs three settings used to be available for each app, the most permissive being 'unrestricted'. SystemUI Tuner didn't expose the menu. --- Using ADB is an acceptable answer as well.

I normally keep my OnePlus 13 slider on the "Vibrate" setting as to not disturb others. Sometimes in the evening, I switch it to the "Ring" (loud) setting. I recently installed an app for a medical device, and I require the app to be loud at all times. I tried enabling "Allow in Do Not Disturb" but this only takes effect when using Do Not Disturb, which stops all other notifications. How can I set my medical app (or any app) to be loud AT ALL TIMES, while keeping all other apps on Silent, Vibrate, Ring (according to the slider)?

I have a OnePlus, OxygenOS 14, non-rooted. I'm using the multiple user feature. However, the second user keeps running in the background and increases battery usage and occupies RAM unnecessarily, even when switching the profile to the main user. How to log out of a user in the multiple user feature?

I have very cheap earphones that have a terrible microphone. My phone's built-in microphone is better. How can I make it so that WhatsApp calls (or regular calls) use my phone's mic, instead of my earphones mic? I tried looking around, and got pointed to apps such as soundabout, which do not exist anymore. I'm using OnePlus 7 Pro, Android 12, Oxygen OS 12.1

My com.android.nfc service keeps crashing, how can I pinpoint why/how it is crashing? Below is the adb logcat logs I have gathered, but nothing points me to what is causing the service to crash. This is repeated constantly and happens every 5 seconds.

3369  5620 D ActivityTaskManagerServiceExtImpl: preBindApplication record is null
15753 15753 E OplusCustomizePackageManager: mIOplusCustomizePackageManagerService is null
15753 15753 E OplusCustomizePackageManager: mIOplusCustomizePackageManagerService is null
15753 15753 E OplusCustomizePackageManager: isOplusCertificatePackage Errorjava.lang.NullPointerException: Attempt to invoke interface method 'boolean android.os.customize.IOplusCustomizePackageManagerService.isOplusCertificatePackage(java.lang.St ing)' on a null object reference
15753 15753 D ResourcesManagerExtImpl: applyConfigurationToAppResourcesLocked app.getDisplayId() return callback.displayId:-1
15753 15753 W ActivityThread: ClassLoader.loadClass: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
 3369  4367 I ActivityManager: Death received, pid = 15753, processName = com.android.nfc for thread android.os.BinderProxy@a60a167
 3369  4811 I ActivityManager: Process com.android.nfc (pid 15753) has died: pers PER
 3369  4811 W ActivityManager: Re-adding persistent process ProcessRecord{c8f2673 15753:com.android.nfc/1027}
 3369  3697 I ActivityManager: Start proc 15773:com.android.nfc/1027 for restart com.android.nfc

03-21 20:57:23.604  6499  6499 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.oplus.wirelesssettings/com.android.settings.SettingsActivity}: java.lang.NullPointerException: Attempt to invoke interface method 'int android.nfc.INfcAdapter.getState()' on a null object reference
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4372)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4569)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:126)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeNonLifecycleItem(TransactionExecutor.java:179)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:114)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:86)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2902)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:107)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:282)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:387)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:9494)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1005)
03-21 20:57:23.604  6499  6499 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'int android.nfc.INfcAdapter.getState()' on a null object reference
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.nfc.NfcAdapter.getAdapterState(NfcAdapter.java:1112)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.nfc.NfcManager.getDefaultAdapter(NfcManager.java:121)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.nfc.NfcAdapter.getDefaultAdapter(NfcAdapter.java:889)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.NfcPreferenceController.(Unknown Source:12)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.c.buildPreferenceControllers(Unknown Source:7)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.c.createPreferenceControllers(Unknown Source:14)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.settings.dashboard.DashboardFragment.onAttach(Unknown Source:29)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.c.onAttach(Unknown Source:5)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.Fragment.performAttach(Unknown Source:49)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.s.c(Unknown Source:199)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.s.m(Unknown Source:124)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.d0(Unknown Source:277)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.i1(Unknown Source:84)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.a0(Unknown Source:21)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.e0(Unknown Source:1)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.a.switchToFragmentExt(Unknown Source:55)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.a.onCreate(Unknown Source:88)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.settings.SettingsActivity.onCreate(Unknown Source:0)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:9192)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:9164)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1544)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4346)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        ... 13 more
03-21 20:57:23.934 21462 21484 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 21484 (android.hardwar), pid 21462 (android.hardwar)
03-21 20:57:23.961 21571 21571 F DEBUG   : Process name is /odm/bin/hw/android.hardware.nfc-service.nxp, uid is 1027, not key_process
03-21 20:57:23.961 21571 21571 F DEBUG   : keyProcess: 0
03-21 20:57:23.961 21571 21571 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-21 20:57:23.961 21571 21571 F DEBUG   : Build fingerprint: 'OnePlus/CPH2655/OP5D55L1:15/AP3A.240617.008/V.R4T3.1c79fbd_1e174_440e:user/release-keys'
03-21 20:57:23.961 21571 21571 F DEBUG   : Revision: '0'
03-21 20:57:23.961 21571 21571 F DEBUG   : ABI: 'arm64'
03-21 20:57:23.961 21571 21571 F DEBUG   : Timestamp: 2025-03-21 20:57:23.948224098-0700
03-21 20:57:23.961 21571 21571 F DEBUG   : Process uptime: 3s
03-21 20:57:23.961 21571 21571 F DEBUG   : Cmdline: /odm/bin/hw/android.hardware.nfc-service.nxp
03-21 20:57:23.961 21571 21571 F DEBUG   : pid: 21462, tid: 21484, name: android.hardwar  >>> /odm/bin/hw/android.hardware.nfc-service.nxp >> /odm/bin/hw/android.hardware.nfc-service.nxp >> /odm/bin/hw/android.hardware.nfc-service.nxp <<<
03-21 20:57:33.977 23360 23360 F DEBUG   : uid: 1027
03-21 20:57:33.977 23360 23360 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
03-21 20:57:33.977 23360 23360 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
03-21 20:57:33.977 23360 23360 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
03-21 20:57:33.977 23360 23360 F DEBUG   :     x0  0000000000000000  x1  0000000000005b1b  x2  0000000000000006  x3  00000076449e8990
03-21 20:57:33.977 23360 23360 F DEBUG   :     x4  2f3d485441500000  x5  2f3d485441500000  x6  2f3d485441500000  x7  0080d0c1d4c8bdaf
03-21 20:57:33.977 23360 23360 F DEBUG   :     x8  00000000000000f0  x9  00000076c9c8b378  x10 ffffff80ffffffdf  x11 fffffffffffffffd
03-21 20:57:33.977 23360 23360 F DEBUG   :     x12 00000076449e8480  x13 0000000000000008  x14 00000076449e85e8  x15 000000004a40580d
03-21 20:57:33.977 23360 23360 F DEBUG   :     x16 00000076c9d74e60  x17 00000076c9d5fac0  x18 0000007642fa8000  x19 0000000000005afc
03-21 20:57:33.977 23360 23360 F DEBUG   :     x20 0000000000005b1b  x21 00000000ffffffff  x22 0000000000000001  x23 00000076449e8f80
03-21 20:57:33.977 23360 23360 F DEBUG   :     x24 00000076cdaa28f8  x25 00000076cdaa1268  x26 00000076449e8a60  x27 00000076cda9d1b0
03-21 20:57:33.977 23360 23360 F DEBUG   :     x28 00000076cdaa2238  x29 00000076449e8a10
03-21 20:57:33.977 23360 23360 F DEBUG   :     lr  00000076c9cfaa68  sp  00000076449e8970  pc  00000076c9cfaa98  pst 0000000000001000
03-21 20:57:33.977 23360 23360 F DEBUG   : 7 total frames
03-21 20:57:33.977 23360 23360 F DEBUG   : backtrace:
03-21 20:57:33.977 23360 23360 F DEBUG   :       #00 pc 0000000000095a98  /apex/com.android.runtime/lib64/bionic/libc.so (abort+172) (BuildId: f4501bd873d8a85bd2dd833a169dec5f)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #01 pc 0000000000044e34  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_emergency_recovery(unsigned char) (.cfi)+252) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #02 pc 0000000000038238  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_process_ext_rsp(unsigned char*, unsigned short*) (.cfi)+4876) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #03 pc 000000000002cc98  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_read_complete(void*, phTmlNfc_TransactInfo*) (.cfi)+304) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #04 pc 000000000002bccc  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_client_thread(void*) (.cfi)+560) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #05 pc 00000000000a7488  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+196) (BuildId: f4501bd873d8a85bd2dd833a169dec5f)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #06 pc 0000000000099584  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: f4501bd873d8a85bd2dd833a169dec5f)
03-21 20:58:28.891 24176 24207 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 24207 (android.hardwar), pid 24176 (android.hardwar)
03-21 20:58:28.924 25096 25096 F DEBUG   : Process name is /odm/bin/hw/android.hardware.nfc-service.nxp, uid is 1027, not key_process
03-21 20:58:28.924 25096 25096 F DEBUG   : keyProcess: 0
03-21 20:58:28.924 25096 25096 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-21 20:58:28.924 25096 25096 F DEBUG   : Build fingerprint: 'OnePlus/CPH2655/OP5D55L1:15/AP3A.240617.008/V.R4T3.1c79fbd_1e174_440e:user/release-keys'
03-21 20:58:28.924 25096 25096 F DEBUG   : Revision: '0'
03-21 20:58:28.924 25096 25096 F DEBUG   : ABI: 'arm64'
03-21 20:58:28.924 25096 25096 F DEBUG   : Timestamp: 2025-03-21 20:58:28.912536513-0700
03-21 20:58:28.924 25096 25096 F DEBUG   : Process uptime: 53s

I'm using Private Safe on my Oneplus device. I need to unlock my private safe as I have forgotten both the password and the privacy question that I had previously set. I have already tried out

adb shell
settings put secure privacy_password_is_open 0
settings put secure access_control_lock_enabled 0
reboot

These commands were the best bet I could find and they don't work. I don't know any other commands since I'm quite new to this. Any help is appreciated.

*This is a self-answer post written in response to a [question](https://android.stackexchange.com/q/236120/96277) where the user couldn't figure out why their well-functioning OTG device was not working on their OnePlus device*. So, I have a OnePlus device running stock OxygenOS. I decided to connect an accessory to my device through an OTG cable/adapter but I see that the device doesn't detect or shows any response when I insert it. My cable/adapter works in other devices, so I'm a bit clueless here. How do I get my OTG cable/adapter working in my OnePlus device?

I want to reinstall the OS on my OnePlus phone running Android 12. Before I do that I would like to backup some of my apps which don't store their data in the cloud. The phone is not rooted, so I have tried using Helium which is apparently dead, but I still tried it. While trying to enable it I found that my phone wasn't recognized by adb as a device, but this was fixed by adding the backup password , but the app just crashes when trying to backup briefly displaying this: As you can see it also clicks on the "set password" option which just opens desktop. The funny thing is: I don't think I can disable the password now, so... So after this didn't work I tried looking into backing up with ADB in PowerShell on my Windows 11 pc, but It seems to have issues with doing backups. To list the files I just do:

adb shell pm list packages -f -3

Let's say that out of those I would like to backup this one:

package:/data/app/~~yCw1hZQNzK2LConsvhuejg==/com.rovio.BadPiggiesHD-pMe0TFd1aaE5-WduzwZ1Zw==/base.apk=com.rovio.BadPiggiesHD

It pulls the .apk file no problem with this command:

adb pull "/data/app/~~yCw1hZQNzK2LConsvhuejg==/com.rovio.BadPiggiesHD-pMe0TFd1aaE5-WduzwZ1Zw==/base.apk" ".\BP.apk"

Although, a little suspicious that it is only 58MB when it should be more like 170. But trying to make a backup with this line:

adb backup "/data/app/~~yCw1hZQNzK2LConsvhuejg==/com.rovio.BadPiggiesHD-pMe0TFd1aaE5-WduzwZ1Zw==/base.apk=com.rovio.BadPiggiesHD"

generates an empty backup.ab file (literally 0B) even if I pass just com.rovio.BadPiggiesHD as an argument. I have also tried using the advice from this post and adding quotes around the arguments, so ideally it I want something like this since I need both an apk and data:

adb backup "-apk com.rovio.BadPiggiesHD -f C:\Users\name\Desktop\app_backups\

But this just spits out Now unlock your device and confirm the backup operation. and stops instantly without doing anything. I have even tried:

adb backup "-apk -shared -all -f C:\Users\name\Desktop\app_backups\full_backup.ab"

I don't need all apps, but this generates an empty file too. What is the cause of this issue? I am at a loss since there are no error messages.

My relative is currently using a OnePlus Nord CE 2 5G; he is visually handicapped and has enabled TalkBack on his phone to assist his daily use. Both System language and TalkBack language are set to Simplified Chinese, but after several minutes of use, the voice will speak in Chinese but with an American accent. It's quite hard to understand what the voice is saying due to the accent. I've tried looking around on various websites but am still unable to find any solution or explanation. Is there any fix or solution for this problem?

I am unable to use Find My Device app on my OnePlus 9 Pro. Even if I enable Find My Device under Settings > Google > Find My Device, the Find My app still asks me to turn on the service. I have tried rebooting the phone, but it doesn't help. I have checked for the latest OS updates as well as Play Store updates, but looks like I am up-to-date. Screenshot showing Find My Device is enabled: But it still asks me to enable the Find My Device: Any idea what can be done? Don't wish to format the phone though. Thanks

I'm using a OnePlus Nord CE3, and while the camera takes amazing high-quality photos, the file sizes are often quite large (usually exceeding 10 MB). I'm looking for a way to reduce the photo resolution or quality so that the file sizes are around 2-3 MB without compromising too much on image clarity. However, I couldn't find an option in the Camera app settings to lower the resolution or adjust the quality. Has anyone else faced this issue? Are there any built-in settings I'm missing?

I recently rooted my OnePlus Nord N30 5G using Magisk, but I still cannot edit the build.prop and hosts files (which was my reason for rooting in the first place). There is no TWRP in the directory for this phone. How can I grant myself read/write permission for these files without needing TWRP? This is my first time messing with the OS of an Android phone. I've tried following the instructions in this video: https://www.youtube.com/watch?v=5b_CMft4zlU , but I'm stuck on the very first step (after establishing the connection with adb), since I don't know where to find the systemrw file that he is talking about. Also, I don't trust the link in the description. I also tried to follow the instructions on https://droidwin.com/how-to-make-system-partition-read-write-on-android/ . On step 10, I do not know what this means, so I don't know how to decide what my "desired" partition size is. I just chose 1 and moved on. However, I am getting stuck around steps 14, as there is another prompt that the instructions don't warn about, creating another backup file. I selected "2" [Recovery/Row] and moved on anyway. From there, I was able to move on to step 19, but here I got stuck since I do not know what the "super.img" file that the article is talking about is, or where to find it.

Last night, I was setting up data transfer from my wife's OnePlus 7 to Pixel 8. After the usual process of Bluetooth enabling and scanning the QR code, the data transfer started. After a while, I noticed this warning on OnePlus 7: > This device may be disconnected from Wi-Fi temporarily. If you turn it back on, your transfer may stop or take longer. This is very confusing and counter-intuitive to me. From what I understand, Bluetooth is for enabling device identification (including QR), and subsequent data transfer is through Wi-Fi (both devices are on the same network). **Why should data transfer stop or take unduly long, if Wi-Fi is re-connected (and why should it be disconnected?)?** I have a fairly stable connection at home, if that matters.

I have a OnePlus Nord and recently updated to Android 12. After a few days, my phone screen suddenly became black and the phone was vibrating on its own. I tried restarting it, it turns on, but shows a black screen and is still vibrating. I do not wish to format it as it contains many important data, and I forgot to take a backup while updating. But due to luck and a software bug, it has ADB enabled, and it doesn't require confirmation even though I had never enabled developer options. So I tried copying files from storage/emulated/0/, but it was empty. So I switched to /data, and when I typed ls, it showed permission denied. Is there a way to access it without formatting the device and safely copying all the data to the PC?

I have the following hardware with software: - OnePlus 12 phone, model CPH2583: Android 14, OxygenOS CPH2583_14.0.0.802(EX01) - OnePlus Watch 2, model OPWWE231: Android 13, WearOS V6.0 I have NFC turned on my phone and watch, since I regularly use tap-to-pay and Google Wallet. However, when I place my phone near my watch (for example, holding the phone in landscape with the hand that has my watch on it, leading to the NFC reader in the phone getting close to the watch), a "New tag collected" screen pops up: I do not wish to turn off NFC on either device since I use both my phone and my watch for tap-to-pay. **Is there a way to turn off this pop-up?**

I have OnePlus Nord. I have installed: - the latest platform tools from Google - the universal ADB driver - the OnePlus USB driver USB debugging and OEM unlocking are on. With the phone turned on, everything runs fine. I can copy files onto the device and it shows up in adb and the device manager just fine. But when I go into the bootloader, fastboot does not list or recognize the device. Here is the fastboot mode shown on the device

FastBoot Mode
PRODUCT_NAME - lito
VARIANT - SM_ UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [redacted]
SECURE BOOT - yes
DEVICE STATE - locked

Below is how the phone shows up in Device Manager. Not sure if this is normal or not, but I am out of ideas. Any help would be much appreciated.

I tried fastboot delete-logical-partition product_a (remote: 'Failed to write partition table') and thats because i don't have a product_a partition.

Fastboot erase product_a
Erasing 'product_a'
FAILED (remote: 'Partition doesn't exist')

but then if i try creating a logical partition

fastboot create-logical-partition product_a 1
Creating 'product_a'
FAILED (remote: 'Partition already exists')

like i said its the same on all other partitions = system,odm,... what am i doing wrong? The phone i am trying to repair: **OnePlus Nord CE 3 Lite 5G CPH2467** (i got the system and all other images from the oxygen updater app)

I'm trying to recover data from my phone cache or anywhere else my phone hides data from me. I have the new OnePlus 12 as well as my previous OnePlus 8t. I'm not tech illiterate, and I'm not a tech genius. I'm looking for deleted data on both phones. I don't want to root the new OnePlus 12. I can root the OnePlus 8t, not that I know how to. I'm seeking an intelligent, patient, individual who can ensure accurate phone guidance, in layman's terms.

I'm trying to figure out whether or not, the One Plus 9 Pro's IR camera * Is exposed as any other camera? * Is a special device that is not exposed as a camera, but only a proprietary feature of the special One Plus Camera app? Was this IR camera ever exposed as a stand-alone camera?

> Most probably these question+answer will be deleted as duplicates, so please **do not vote here**. But if the answer is useful - add your upvote here: https://android.stackexchange.com/a/252613/251126 in order to bubble a good (my hehe) answer there For years I used my phone as a backup connection to the internet (and you know - airports...) Today I connected my phone to the laptop with my factory-default cable and tried to enable tethering - but the USB Tethering button in the menu was disabled. How to make it enabled? ---- I checked the cable (several), and I use one that does the trick with another phone. Recently I updated Android to v12