I have Android Beta 15 (AP41.240925.009). Is it possible to leave the beta program without wiping? I tried opting out from the beta program, but then received an update that said it will wipe the device. When I opt back in, I get an update for Android 15 QPR2 Beta 1. That update clearly says > If you are currently running a Beta version of Android 15 QPR1 (build starting with AP41) and want to exit the beta program without wiping your device, you can opt out of the Beta program **before applying this update** But that doesn't seem to be the case:

I'm using Nothing phone 3a pro, Android 15, it has USB 2.0. PC System: Windows 10 home edition with last update. Tried to connect it to usb 3.1, 3.0, 2.0, I see the storage of my phone, but when I go into it,and it is empty I rebooted my PC, rebooted Phone. Reconnected it. I gave all the recommendations from “Nothing support.” (change cables, developer settings usb, reset and etc.) Only I didnt do is to reset my phone to factory settings. My old phone Samsung A80 which has USB 2.0 too, still have good connection to the PC. Nothing phone haven't got own drivers. What I did: - Enable usb debugging mode. - Enable the transfer file on phone. - Have screen ON. - I download program which automatically load new drivers, also I update windows, but nothing happened again. - I changed drivers in device manager, delete my device, reinstall drivers. - Also I tried VirtualBox with cleared Windows 10 on same hardware. Got same problem, folders didn’t load. - Also Installed new clear Windows 10 to another SSD on same hardware. Same problem. Any possible solutions? If you need more information, please write your reply.

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 just switched from an older Samsung phone to a Pixel 9 running Android 15. I noticed that the timestamp on each notification shows a relative time ("43m") rather than the wall-clock time ("07:22”). Is there a setting (or 3rd party app) to change this behavior? In particular, I'd like to be able to see exact time of events more than an hour ago, which now just show up as e.g. "2h" - the loss of precision is really annoying.

When I'm texting (SMS) someone and want to call them, I click the phone icon in the app. But that launches Google Voice. How can I set it to launch the regular voice app (to make a standard phone call)? I'm on Google Pixel 6, Android 15. Edit: Apps>Default apps>phone> is Phone app

Installed crDroid-based Android 15 and noticed single tap on recents button (on a 3-button navbar) has ~0.4 second delay before it opens the recent apps view. Note the delay is gone if double-tap action on the button is removed, which for me switches to last/previous app. But I've always had this functionality on double-tap. There was no noticeable delay on Android 14 or earlier. Also gave [custom launcher](https://github.com/LawnchairLauncher/lawnchair/releases) a go, but that has the same delay, so it appears to be an OS-level issue. Is this something introduced by Android 15, or is it likely related to specific ROM I'm using? Is it possible to remove this delay?

My Pixel 6 just upgraded to Android 15, where the Do Not Disturb mode moved into a new Modes area. I don't like how more taps are required now to enable or disable that mode. How can I reduce the number of taps required? Nowadays it seems this is what I need to do: 1. Swipe down from the top of your screen to open Quick Settings. 2. Tap "Modes" 3. Tap "Do Not Disturb" 4. Tap "Turn On" 5. Tap "Done" I think this is TWO more steps than used to be required, and it's annoying me throughout every day. Also, I do not want to use the 'Flip to Shhh' Gesture. And I do not want to schedule DND mode or set rules for when it should automatically enable. How can I change the steps back to how they were?

I need to trade in my old phone soon. The file did not transfer to my new phone (or I cant locate it). I have had the same wallpaper since 2012 and would like to keep it if possible. I am on Android 15

I have a OnePlus 6, running LineageOS 22.1 (Android 15). In December when I still was on LOS 21 (Android 14), out of nowhere my phone's camera & torch have stopped working. It just shows "Camera in use" message under the Torch button in the notification area, the LOS camera app just closes itself, or other apps display "can't open camera". I've revoked camera permissions to see if anything is using it, but no change. Initially after a few reboots the torch was working, but later on even that stopped working & after many reboots & upgrades I can't get that back to work either. LOS support said to flash back the original OxygenOS, but I don't want to do that, as it will log me out of loads of apps which don't survive TWRP/OrangeFox restore. So what I'm looking for is a way of confirming that the camera is physically broken, so to see I'd need to try to replace it (if possible, didn't look at it), or there's some software issue only (I don't want to open the phone if not necessary). Does anyone know a way to do that, eg. from a recovery/fastboot boot/ADB or anything else? Or is there a possibility to boot to OxygenOS without flashing it in? Thank you

I bought a used Android 15 Samsung phone from Amazon's WHD, the phone has the previous' users Google account connected. Can I factory reset the phone and use it? This related question does not seem to work for A15. I have ADB available if that could help.

After setting up a private space, when I unlock the private space, I see the option to add a few (system) apps, such as camera, and google. Is there any way to move existing apps (such as banking apps, Switch Parental Controls, etc.) into the private space? Is reinstalling the only option?

I ended up with my Android device (Google Pixel 7a, on AOSP 15) having accumulated about **~14k** videos/photos files in /sdcard/DCIM/Camera. As a consequence I have noticed some very *unexpected* delay when listing this directory in this particular folder, *but also* in general. I do run the following tests

[user@archlinux-box ~] $ ## having the Pixle 7a connected via USB-3 port USB-debugging
[user@archlinux-box ~] $ adb shell
lynx:/ $ ## time the listing of /sdcard/DCIM/Camera
lynx:/ $ (cd /sdcard/DCIM/Camera; time ls | wc)
  13980   13980  398700
    0m04.55s real     0m00.07s user     0m00.31s system
lynx:/ $ ## exclude that it is a fault ot ls binary I check via find too
lynx:/ $ (cd /sdcard/DCIM/Camera; time find | wc)
  13981   13981  426662
    0m05.25s real     0m00.07s user     0m00.41s system

Being suspicious that listing ~14k files may very well take some time, yet not ~5seconds (and less so upon 2nd time directory listing reads, given I would assume some caching to occur) I tested if this is related to the specific folder /sdcard/DCIM/Camera doing this

lynx:/ $ ## create and enter a test directory to hold 14k files
lynx:/ $ mkdir /sdcard/14k-files-dir
lynx:/ $ cd  /sdcard/14k-files-dir
lynx:/sdcard/14k-files-dir $ ## create 14k files somewhat efficiently
lynx:/sdcard/14k-files-dir $ ## have filenams be comparable length as photo files
lynx:/sdcard/14k-files-dir $ PREFIX='filename-similar-to-photo-files-file-no-'
lynx:/sdcard/14k-files-dir $ seq 1 14000 | sed 's/^/'"$PREFIX"'/' | xargs sh -c 'touch "$@"' _
lynx:/sdcard/14k-files-dir $ ## rerun tests
130|lynx:/sdcard/14k-files-dir $ time ls | wc
  14000   14000  618894
    0m01.92s real     0m00.10s user     0m00.28s system
lynx:/sdcard/14k-files-dir $ time find | wc
  14001   14001  646896
    0m00.72s real     0m00.03s user     0m00.13s system
lynx:/sdcard/14k-files-dir $ time ls | wc
  14000   14000  618894
    0m00.80s real     0m00.10s user     0m00.13s system

as can be seen this time, the directory listing is far faster (particularly once it appears to be in cache). Lastly I wanted to test - given Android being based on linux kernel - how well my 10+ year laptop would compare.

[user@archlinux-box ~] $ ## running test on a 10 year old laptop
[user@archlinux-box ~] $ mkdir 14k-files-dir
[user@archlinux-box ~] $ cd 14k-files-dir
[user@archlinux-box 14k-files-dir ] $ ## create 14k files somewhat efficiently
[user@archlinux-box 14k-files-dir ] $ ## have filenams be comparable length as photo files
[user@archlinux-box 14k-files-dir ] $ PREFIX='filename-similar-to-photo-files-file-no-'
[user@archlinux-box 14k-files-dir ] $ seq 1 14000 | sed 's/^/'"$PREFIX"'/' | xargs sh -c 'touch "$@"' _
[user@archlinux-box 14k-files-dir ] $ ## run tests on laptop
[user@archlinux-box 14k-files-dir]$ time ls | wc
  14000   14000  632894

real    0m0.025s
user    0m0.015s
sys     0m0.014s
[user@archlinux-box 14k-files-dir]$ time find | wc
  14001   14001  660896

real    0m0.030s
user    0m0.019s
sys     0m0.020s
[user@archlinux-box 14k-files-dir]$ time ls | wc
  14000   14000  632894

real    0m0.021s
user    0m0.009s
sys     0m0.015s

As can be seen the speed listing directories differ vastly. I am puzzled to determine the reasons. 1. It is mostly unclear why the direct "on Android device" comparison of directories listing times is so huge (1-0.7seconds vs 4-5seconds for /sdcard/DCIM/Camera) 2. It is puzzling as I would expect both folders residing on the same block-device and filesystem being both below /sdcard ? 3. In a bigger picture however I cannot wrap my haed around (and seek with this question the causes that a 10 year old linux laptop can list 14k files at 0.02seconds while a rather recent Google Pixel 7a needs 0.7 to 5+ seconds, so plainly 250 times as long? #Update# I have found this info on redit which mentions > As mentioned below, it seems on Android 11 ALL file access to external storage goes through SAF, even when targeting API 29 and using standard file access functions. This is a change from Android 10. This explains the difference in speed. I hence wonder (with regarding to the causes I seek in this question here) if this this still the reason? Also with this new information I cannot still see why the two folders still have 5-10 times different directory lookup speeds.