Before *Android OS 16*'s last update (to build # BP3A.250905.014), it was possible to use programs such as *Google Messages* to send or receive **SMS** messages. But as of BP3A.250905.014, **SMS** messages sent to you (which are required to login to your government accounts, or to use social services, or bank apps such as *Well's Fargo*, or to login to your *Google* account if you are stuck with 2-factor-authentication) are not shown, and you can not send **SMS** messages:  . If you click "More ways to veridy", Google's 2-factor-authentication has an option to enter a code for account access, but [build BP3A.250905.014 breaks the input box (the text input which you enter the code into)](https://android.stackexchange.com/questions/262261/after-system-update-to-bp3a-250905-014-you-cannot-use-bluetooth-keyboard-to) . If you can disable 2-factor-authentication, that is a possible solution, but do not know how to. How to restore **SMS**? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card (so *Google* can not force those), or [switch to a new **OS** (such as *Ubuntu Phone*) which allows you to use your phone](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ?

Before *Android OS 16*'s last update (to build # BP3A.250905.014), Home settings had Allow home screen rotation (if enabled, this uses the accelerometer so that home is vertical if the phone is vertical, or horizontal if the phone is horizontal. - This was the sole option that allowed you to hide the *Google* search bar; if you disabled the *Google* app and enabled this option, then when your phone is horizontal, the *Google* search bar does not show.  But BP3A.250905.014 replaces this option with Landscape mode (which is a permanent on/off switch). - It is now not possible to hide the *Google* search bar unless you replace the stock launcher (such as with *Nova Launcher*, which is not recommended). With the new Landscape mode, even with the *Google* app disabled and the phone horizontal, the *Google* search bar shows.  How to restore the old home view? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card (so *Google* can not force those), or [switch to a new **OS** (such as *Ubuntu Phone*) which allows you to use your phone](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ?

After the "update" (to build # BP3A.250905.014), + still shows the apps list, but does not switch to next (nor to previous) apps upon release&re-press of `` (which is what *Android OS* used to do, and all other *OS*s still do.) Before BP3A.250905.014, could use + (through *Bluetooth*) to show the apps list, then release ` and re-press ` to switch through all of the current apps. How to restore this? Do you have to undo the update (roll back to the old version) to restore + switches? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/)) ; is it possible to go back to the old version, or do you have to return such defective devices and purchase new? Can not include photos of the current apps list since (as of BP3A.250905.014) the + combo is broken in the apps list (the combo just shows the volume tooltip unless you release ` (but releasing closes the current apps list)). A previous "update" broke the physical screenshot buttons on Bluetooth keyboards, which (as of BP3A.250905.014`) are still broken (still can not use).

So, for instance one of apps renamed itself to "Content on this profile might be inappropriate for those under a certain age" and displays that message (and "Stopped.") in a MessageBox when started. Its icon also changed (to a grey heart; another changed to a grey edit-pencil). It works again after reinstalling it though. And my VLC player app is now called "_". Do you think my phone fell victim to a virus? I got the Kaspersky virus scanner installed and when doing a full scan it finds nothing. I guess it's probably just some bug. Maybe someone else had the same problem? Edit: it appears that moving apps from my phone to the SD card was causing the icon-problem. The icon of Firefox changed to some grey icon after doing so. It changed back to the proper icon after I restarted the device. Not sure if that was also causing the app-names problem and I think it's unlikely to have caused that soundcloud-app-problem.

I often receive the following error message when attempting to perform Android security updates: > There was a network error while downloading the update. Please try again later or connect to a different network. In researching this error message, it is apparent that many other people have been reporting the same issue for years: - Update cannot be downloaded on specific networks : GooglePixel https://old.reddit.com/r/GooglePixel/comments/10whijh/update_cannot_be_downloaded_on_specific_networks/ - Not able to update to android 15. Shows error in network while downloading although connected to WiFi - Google Pixel Community https://support.google.com/pixelphone/thread/322921191/not-able-to-update-to-android-15-shows-error-in-network-while-downloading-although-connected-towifi - Pixel 7 System Update Fails : GooglePixel https://old.reddit.com/r/GooglePixel/comments/ycejcz/pixel_7_system_update_fails/ - There was a network error while downloading the update. Please try again later or connect to a diffe - Google Pixel Community https://support.google.com/pixelphone/thread/205161477/there-was-a-network-error-while-downloading-the-update-please-try-again-later-or-connect-to-a-diffe Over the years, people have offered "magical" solutions, such as toggling WiFi on and off, which likely has nothing to do with the real issue. Yet some do claim that such actions have temporarily fixed the issue (not myself, though). What's even more odd is that those reporters have not indicated they made any additional changes. In Google's latest Android version, Android 16, this issue is still present. Ironically, the issue seems to be most prevalent on Google's own Pixel devices. Does anyone know what is causing this bug and how to actually fix it? Update --- A couple of our community members asked some good questions... here are the answers: - The issue occurs regardless of whether WiFi or carrier data is used. - I've seen the issue occur on many Google Pixel devices, starting with the Pixel 4. Online reports indicate it was present going back to at least the Pixel 2. I've seen this issue on several Samsung devices as well, although online reports of this issue tend to mention the Pixel devices more often than Samsung devices. - Regarding proxies, VPNs, or blocked ports/servers, I need to investigate further. It definitely happens on a wide range of devices and on a wide range of networks, but perhaps there is a common element that I can discover.

This is a very poorly-defined question, because I can't figure out what causes this issue (and cannot easily reproduce it). But on occasion (and not rarely), when I pull my Google Pixel 6 phone out of my pocket, the flashlight is on, Bluetooth has been turned off, and when I unlock the phone I am looking at the emergency call screen. I believe that the DND and bedroom settings get modified sometimes as well. I haven't been able to find anything like this on the web. Any ideas? (Android 13)

My Google Pixel 4 cellphone (Android 13 build TP1A.221005.002.B2, up to date) stopped pairing with headphones (Shokz Open Air Pro) after working fine for a few years. This happened after I paired the headphones with a new phone, then later tried connected my usual phone with the headphones and it wouldn't work as they usual did, so I had my usual phone forget the headphones and try to re-pair. That's when the problem arose, not pairing or responding to clicks on the pairing list. To try and fix this, I had already had my phone forget the BT connection, so I tried to reset the headphones and tried what I could with limited settings there. Starting fresh should work since it worked before, I figured. One of the only other options for headphones other than factory resetting was to enable multipoint pairing , I tried enabling that too and I don't think it had any effect, I've again reset the headphones. The furthest I've got is the headphones show up on my phone when trying to pair with new devices, but when I click the headphones, the phone doesn't respond. I tested my phone and the headphones independently. My phone connects with other BT devices no problem. They show up on list available for pairing, I click them, it says connecting and does its thing on both ends, data and sound transfers fine. I tested the headphones with two other phones and a computer, and they all work fine, connecting as expected. Something between my phone and the headphones appears stuck, such that my phone is unresponsive to the request to pair with the headphones, despite recognizing them as available for pairing. The headphones are in pairing mode and can connect with other devices from there, so as far as I can tell, nothing is wrong on that end. So far on my phone, I tried: - toggling Bluetooth on and off, - forgetting the headphones in the first place (they haven't paired to let me try to 'forget' again) - I turned on developer mode and toggled "Disable Bluetooth A2DP hardware offload" to turn it on. I saw this resolved some BT issues for other users, but no effect for me. I turned it back off. - I've restarted the phone many times throughout all this, tried over a couple of weeks now. **What other settings can I adjust on my phone to try to reset/remedy pairing with these headphones?** Is there a way to reset my phone's BT completely? I have a few other paired devices I'd rather not forget if unnecessary but I can reset and reconnect to all those if that might fix these headphones. I just don't want to factory reset the phone if I can avoid it.

I noticed that either USB key or the Razer Kishi gamepad where undetected by my device although it did work some time ago. It may be related to an update or a material problem, I don't know. I tried the devices on both my computer and other android devices and they are perfectly detected. I have no setting to toggle on Settings > Additional Settings, while I saw on the internet that OTG devices have a setting to toggle on for OTG. See attached picture for the specs of my phone. Is there any way to confirm whether it's a software issue or a physical issue ? And would anyone know which steps to take in either case ? EDIT: Extra information provided:

After the Android Youtube app updated a few days ago on November 7th 2024, I have been having these two problems: - Pressing back arrow from video view, the mini player disappears outside the screen but audio keeps playing. - After pausing the video, it refuses to continue. I see from Google Play reviews that some other users are also having these problems, but not all. In case it matters, I'm using Oneplus Nord CE 5G and running OxygenOS/Android 13.

So this is happening for the last 2 weeks. Whenever I (short) press the home button on my Galaxy S7 (on Android 8.0.0) specifically in the (facebook) messenger app it registers as a long click (opening the google assistant until i disabled it). I'm not sure if it is a messenger problem since Im sure I had this happen in the playstore app as well but cant replicate it right now (so right now its only happening in messenger app). I played around with the Tasker and Automate apps around the time this started happening, but I have also uninstalled them around that time. Might just be a coincidence. I have tried reinstalling the messenger app but that didnt help. Does anyone have any idea what could cause this or at least give me some pointers on how I might troubleshoot it? Edit: definitely happens in other apps as well but still mostly in messenger

OnePlus 7T smartphone randomly freezes and rebooting. Bootloader unlocked and rooted. Smartphone runs on Android 11, but the same behavior occurred on a purely installed Android 12. Often the error appears in moments related to graphics, such as rotating the screen, changing the screen in games (the appearance of a video screensaver, for example). This can happen from once a day to several times. From the logs it is clear that this is somehow related to video drivers:

[20240305_12:19:40.512637]@0 platform 2c6a000.qcom,gmu: OOB_set(0x40000000) timed out
[20240305_12:19:40.622730]@0 platform 2c6a000.qcom,gmu: ----------------------[ GMU error ]----------------------
[20240305_12:19:40.622782]@0 platform 2c6a000.qcom,gmu: Timeout waiting for lowest idle level 3
[20240305_12:19:40.622804]@0 platform 2c6a000.qcom,gmu: Timestamps: 272b38cc6 272d3aee0 272d3af12
[20240305_12:19:40.622825]@0 platform 2c6a000.qcom,gmu: RPMH_POWER_STATE=0 SPTPRAC_PWR_CLK_STATUS=0
[20240305_12:19:40.622846]@0 platform 2c6a000.qcom,gmu: CX_BUSY_STATUS=71000000 CP_STATUS_1=1000000
[20240305_12:19:40.622868]@0 platform 2c6a000.qcom,gmu: RBBM_INT_UNMASKED_STATUS=1 PWR_COL_KEEPALIVE=0
[20240305_12:19:40.622889]@0 platform 2c6a000.qcom,gmu: CP2GMU_STATUS=0 CONTEXT_SWITCH_CNTL=0 AO_SPARE_CNTL=0
[20240305_12:19:40.622961]@0 ------------[ cut here ]------------
[20240305_12:19:40.623004]@0 WARNING: CPU: 0 PID: 272 at drivers/gpu/msm/adreno_a6xx_gmu.c:973 a6xx_gmu_wait_for_lowest_idle+0x450/0x490
[20240305_12:19:40.623024]@0 Modules linked in: wlan(O) rmnet_perf(O) machine_dlkm(O) wcd934x_dlkm(O) mbhc_dlkm(O) wcd9360_dlkm(O) swr_ctrl_dlkm(O) wcd9xxx_dlkm(O) tfa9894_dlkm(O) wsa881x_dlkm(O) wcd_core_dlkm(O) stub_dlkm(O) wcd_spi_dlkm(O) hdmi_dlkm(O) swr_dlkm(O) pinctrl_wcd_dlkm(O) usf_dlkm(O) native_dlkm(O) platform_dlkm(O) q6_dlkm(O) adsp_loader_dlkm(O) apr_dlkm(O) q6_notifier_dlkm(O) q6_pdr_dlkm(O) wglink_dlkm(O) msm_11ad_proxy [last unloaded: rmnet_perf]
[20240305_12:19:40.623200]@0 CPU: 0 PID: 272 Comm: kgsl_worker_thr Tainted: G S      W  O    4.14.190-perf+ #1
[20240305_12:19:40.623220]@0 Hardware name: Qualcomm Technologies, Inc. SM8150 V2 PM8150 MTP 18865 19863 14 15 (DT)
[20240305_12:19:40.623243]@0 task: 00000000ead67ef5 task.stack: 000000007e72c1e2
[20240305_12:19:40.623263]@0 pc : a6xx_gmu_wait_for_lowest_idle+0x450/0x490
[20240305_12:19:40.623282]@0 lr : a6xx_gmu_wait_for_lowest_idle+0x44c/0x490
[20240305_12:19:40.623300]@0 sp : ffffff8014783980 pstate : 60c00145
[20240305_12:19:40.623316]@0 x29: ffffff80147839b0 x28: 0000000000000004 
[20240305_12:19:40.623348]@0 x27: 0000000000000002 x26: 0000000000000002 
[20240305_12:19:40.623379]@0 x25: ffffffe2b336e000 x24: 0000000000023b0c 
[20240305_12:19:40.623409]@0 x23: 0000000272d3af12 x22: 0000000272d3aee0 
[20240305_12:19:40.623440]@0 x21: 000000000001f888 x20: 0000000272b38cc6 
[20240305_12:19:40.623471]@0 x19: ffffff8b4a2fac00 x18: ffffff8b4a238000 
[20240305_12:19:40.623502]@0 x17: 0000000000000000 x16: ffffff8b4a45d000 
[20240305_12:19:40.623533]@0 x15: 4c544e435f455241 x14: 0000000000000060 
[20240305_12:19:40.623563]@0 x13: 0000000000000444 x12: 0000000810947aa9 
[20240305_12:19:40.623593]@0 x11: 0000000000000015 x10: 00000000000f4240 
[20240305_12:19:40.623624]@0 x9 : 610bdee29b856c00 x8 : 610bdee29b856c00 
[20240305_12:19:40.623655]@0 x7 : 0000000000000000 x6 : ffffff8b4a45cdaa 
[20240305_12:19:40.623686]@0 x5 : 0000000000000034 x4 : 0000000000000008 
[20240305_12:19:40.623715]@0 x3 : 0000000000000000 x2 : 000000000000006e 
[20240305_12:19:40.623746]@0 x1 : ffffff8b47f48d3c x0 : 00000000ffffff92 
[20240305_12:19:40.623780]@0 
PC: 0xffffff8b48696360:
[20240305_12:19:40.623797]@0 6360  9400632e f9400728 b0009a81 b85ec3a2 91238821 b94013e3 91004100 94006327
[20240305_12:19:40.623885]@0 6380  f9400728 b0009a81 29410be3 91245021 b94007e4 91004100 94006320 12800da0
[20240305_12:19:40.623965]@0 63a0  d4210000 9000dbc9 f85f83a8 f9404529 eb08013f 54000121 a9484ff4 f94023fb
[20240305_12:19:40.624046]@0 63c0  a94757f6 a9465ff8 a94567fa a9437bfd 910243ff d65f03c0 97e0a1aa d503201f
[20240305_12:19:40.624127]@0 
LR: 0xffffff8b4869635c:
[20240305_12:19:40.624142]@0 635c  91004100 9400632e f9400728 b0009a81 b85ec3a2 91238821 b94013e3 91004100
[20240305_12:19:40.624223]@0 637c  94006327 f9400728 b0009a81 29410be3 91245021 b94007e4 91004100 94006320
[20240305_12:19:40.624303]@0 639c  12800da0 d4210000 9000dbc9 f85f83a8 f9404529 eb08013f 54000121 a9484ff4
[20240305_12:19:40.624383]@0 63bc  f94023fb a94757f6 a9465ff8 a94567fa a9437bfd 910243ff d65f03c0 97e0a1aa
[20240305_12:19:40.624464]@0 
SP: 0xffffff8014783940:
[20240305_12:19:40.624480]@0 3940  486963a0 ffffff8b 60c00145 00000000 ffffffd0 ffffff80 499e7914 ffffff8b
[20240305_12:19:40.624560]@0 3960  ffffffff ffffffff 9b856c00 610bdee2 147839b0 ffffff80 486963a0 ffffff8b
[20240305_12:19:40.624638]@0 3980  147839b0 00000000 00000000 00000000 00000000 00000000 00000000 00000001
[20240305_12:19:40.624718]@0 39a0  01000000 71000000 9b856c00 610bdee2 14783a10 ffffff80 4865924c ffffff8b
[20240305_12:19:40.624797]@0 
[20240305_12:19:40.624815]@0 Call trace:
[20240305_12:19:40.624834]@0  a6xx_gmu_wait_for_lowest_idle+0x450/0x490
[20240305_12:19:40.624857]@0  gmu_stop+0x34/0xf0
[20240305_12:19:40.624877]@0  gmu_core_stop+0x1c/0x28
[20240305_12:19:40.624901]@0  kgsl_pwrctrl_disable+0x70/0xb8
[20240305_12:19:40.624921]@0  _slumber+0x208/0x2e0
[20240305_12:19:40.624939]@0  kgsl_pwrctrl_change_state+0x234/0x510
[20240305_12:19:40.624962]@0  _adreno_start+0x2b8/0x958
[20240305_12:19:40.624981]@0  adreno_start+0x44/0x78
[20240305_12:19:40.624998]@0  _wake+0xc4/0x3f8
[20240305_12:19:40.625017]@0  kgsl_active_count_get+0x148/0x1e0
[20240305_12:19:40.625039]@0  sendcmd+0xe4/0x508
[20240305_12:19:40.625058]@0  _adreno_dispatcher_issuecmds+0x2a8/0x5b8
[20240305_12:19:40.625076]@0  adreno_dispatcher_work+0x450/0x9d0
[20240305_12:19:40.625101]@0  kthread_worker_fn+0x80/0x168
[20240305_12:19:40.625119]@0  kthread+0x11c/0x130
[20240305_12:19:40.625141]@0  ret_from_fork+0x10/0x1c
[20240305_12:19:40.625158]@0 ---[ end trace 137859bf8ec69b6e ]---
[20240305_12:19:40.625228]@0 platform 2c6a000.qcom,gmu: Failed to stop GMU
[20240305_12:19:40.625690]@0 kgsl kgsl-3d0: |_wake| start failed -110
[20240305_12:19:40.625985]@1 kgsl kgsl-3d0: RB[-1]: gmu fault status 00000001 rb 0000/0000 ib1 0000000000000000/0000 ib2 0000000000000000/0000
[20240305_12:19:40.626077]@0 kgsl kgsl-3d0: |kgsl_iommu_fault_handler| GPU PAGE FAULT: addr = 0 pid= 0 name=unknown
[20240305_12:19:40.626104]@0 kgsl kgsl-3d0: |kgsl_iommu_fault_handler| context=gfx3d_user TTBR0=0x3000273352000 CIDR=0x0 (read translation fault)
[20240305_12:19:40.626129]@0 kgsl kgsl-3d0: |kgsl_iommu_fault_handler| FAULTING BLOCK: CP
[20240305_12:19:40.626178]@0 kgsl kgsl-3d0: ---- nearby memory ----
[20240305_12:19:40.626200]@0 kgsl kgsl-3d0: *EMPTY*
[20240305_12:19:40.626219]@0 kgsl kgsl-3d0:  <- fault @ 00000000
[20240305_12:19:40.626236]@0 kgsl kgsl-3d0: *EMPTY*
[20240305_12:19:40.627643]@1 platform 2c6a000.qcom,gmu: Suspended GMU
[20240305_12:19:40.633654]@0 platform 2c6a000.qcom,gmu: GMU CM3 fault interrupt received
[20240305_12:19:40.742778]@0 platform 2c6a000.qcom,gmu: OOB_set(0x40000000) timed out
[20240305_12:19:40.774568]@0 platform 2c6a000.qcom,gmu: Suspended GMU
[20240305_12:19:40.780103]@0 platform 2c6a000.qcom,gmu: GMU CM3 fault interrupt received
[20240305_12:19:40.882739]@0 platform 2c6a000.qcom,gmu: OOB_set(0x40000000) timed out
[20240305_12:19:40.914491]@0 platform 2c6a000.qcom,gmu: Suspended GMU
[20240305_12:19:40.920147]@0 platform 2c6a000.qcom,gmu: GMU CM3 fault interrupt received
[20240305_12:19:41.022673]@0 platform 2c6a000.qcom,gmu: OOB_set(0x40000000) timed out
[20240305_12:19:41.054826]@1 platform 2c6a000.qcom,gmu: Suspended GMU
[20240305_12:19:41.060742]@0 platform 2c6a000.qcom,gmu: GMU CM3 fault interrupt received
[20240305_12:19:41.162731]@3 platform 2c6a000.qcom,gmu: OOB_set(0x40000000) timed out
[20240305_12:19:41.192733]@3 ------------[ cut here ]------------
[20240305_12:19:41.192774]@3 kernel BUG at drivers/gpu/msm/adreno_dispatch.c:2270!
[20240305_12:19:41.192799]@3 Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[20240305_12:19:41.192816]@3 Modules linked in: wlan(O) rmnet_perf(O) machine_dlkm(O) wcd934x_dlkm(O) mbhc_dlkm(O) wcd9360_dlkm(O) swr_ctrl_dlkm(O) wcd9xxx_dlkm(O) tfa9894_dlkm(O) wsa881x_dlkm(O) wcd_core_dlkm(O) stub_dlkm(O) wcd_spi_dlkm(O) hdmi_dlkm(O) swr_dlkm(O) pinctrl_wcd_dlkm(O) usf_dlkm(O) native_dlkm(O) platform_dlkm(O) q6_dlkm(O) adsp_loader_dlkm(O) apr_dlkm(O) q6_notifier_dlkm(O) q6_pdr_dlkm(O) wglink_dlkm(O) msm_11ad_proxy [last unloaded: rmnet_perf]
[20240305_12:19:41.192984]@3 Process kgsl_worker_thr (pid: 272, stack limit = 0x000000007e72c1e2)
[20240305_12:19:41.193004]@3 CPU: 3 PID: 272 Comm: kgsl_worker_thr Tainted: G S      W  O    4.14.190-perf+ #1
[20240305_12:19:41.193018]@3 Hardware name: Qualcomm Technologies, Inc. SM8150 V2 PM8150 MTP 18865 19863 14 15 (DT)
[20240305_12:19:41.193033]@3 task: 00000000ead67ef5 task.stack: 000000007e72c1e2

Any suggestions on how to fix this error? Or why might this be happening?

I think I have spotted a major bug in the Wireguard app for Android but I can't see any reliable way to report it (and the IRC channel is probably not the best place to report bugs). Does anyone know a reliable channel to report possible WG bugs?

From time to time I get a notification on my phone which says: Bug report #1 captured Tap to share your bug report When I tap, it warns me about the possibility of sensitive information being in the report. I tap on "Ok" to continue. But now, instead of the report being submitted somewhere automatically, like it would under something like Windows or Mac OS X, it pops up a "Share with" prompt, asking me how I want to share it. I have no idea, I don't even know what caused the bug report! The choices I see are Gmail (who am I supposed to send it to, especially given that I don't know what the report is even about?), Add to Dropbox (what good would that be?), Android Beam (never used this, but it sounds like maybe I would need to be in the same room as Android developer for this to be useful), and Save to Drive (again, seems about as useless as adding to my Dropbox). I'm not even sure why I'm being prompted to do this, given the complete lack of instruction on what I should be doing. Update: I tried e-mailing the report to myself. The bug report contained an empty (black) image, and a zip file containing a 16.4MB log file (which appeared to just be a dump of various process info - I didn't look at the whole thing due to length, but I couldn't find any obvious indication of what the problem was) and a FS directory containing a path FS/data/tombstones containing 10 separate files ranging between one month and one year old (nothing from today!). The newest of these files appear to be system related (/system/bin/rild, com.android.nfc, system/bin/netmgrd, ...)

Just bought a new phone with Android 12 and found this app switch failure: I press "square" button, see recent apps list, tap on one of them. So that app came to top for a moment and then hides away. I tried Nova, Pixel, Microsoft and Niagara launchers, all with the same effect. The problem don't appear only with stock launcher. I've found that it can be fixed by disabling "Animator Duration scale" in developer options. The problem is that I literally can't disable that option - I tap on it, select "Animation off", but value still shows "Animation scale .5x". Oukitel WP18Pro, Android 12, stock launcher is Quickstep, no root, no custom things. Factory reset also does not help.

On Motorola Edge 30, the system setting for this is not working. Interestingly, I found a GitHub issue that suggests this might be a bug in Android 13. Is there a workaround or a reliable way to detect specifically when an outgoing call is answered in Android 13?

My Asus Zenfone 5 is beginning to have some malfunctions : No more sound, which means : - I can't make calls (the phone freezes to black and I can only start it up again by holding the power button) - I can't receive calls (callers go directly to voicemail) - I can't open the camera to take pictures or videos - Alarms don't ring, they just vibrate - I can't listen to music - I can't watch videos (videos taken with my phone, on youtube, on any social media app...) : video just won't start. I got this bug report from NewPipe, a youtube client : ## Exception * __User Action:__ play stream * __Request:__ Player error[type=ERROR_CODE_AUDIO_TRACK_INIT_FAILED] occurred while playing https://www.youtube.com/watch?v=RH2v_m5dBdg * __Content Country:__ GB * __Content Language:__ en- * __App Language:__ fr_FR * __Service:__ YouTube * __Version:__ 0.25.0 * __OS:__ Linux Android 9 - 28 Crash log

com.google.android.exoplayer2.ExoPlaybackException: MediaCodecAudioRenderer error, index=1, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100]), format_supported=YES
 at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:566)
 at android.os.Handler.dispatchMessage(Handler.java:102)
 at android.os.Looper.loop(Looper.java:198)
 at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)
 at com.google.android.exoplayer2.audio.DefaultAudioSink$Configuration.buildAudioTrack(DefaultAudioSink.java:2110)
 at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrack(DefaultAudioSink.java:1070)
 at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrackWithRetry(DefaultAudioSink.java:1049)
 at com.google.android.exoplayer2.audio.DefaultAudioSink.initializeAudioTrack(DefaultAudioSink.java:846)
 at com.google.android.exoplayer2.audio.DefaultAudioSink.handleBuffer(DefaultAudioSink.java:929)
 at com.google.android.exoplayer2.audio.MediaCodecAudioRenderer.processOutputBuffer(MediaCodecAudioRenderer.java:703)
 at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1894)
 at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:792)
 at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:989)
 at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:490)
 ... 3 more
 Suppressed: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)
  ... 13 more

I don't know if it's related, but I've also noticed that in the play store, when I check the the compatibility of any app with my device, it is identified as Asus UNKNOWN_PRJ_ID, instead of X00QD. I don't know how to proceed from there, is my phone fixable ? The last time it happened, I was able to *fix* the issue by shutting down and restarting the phone a dozen times, but this time it's not working.

Recently I've stumbled upon a very weird and cumbersome bug. Android mistakes one of my contacts for another. As far as I know it happens to exactly one pair of contacts on my phone (let's call them A and B). When trying to message A, it shows the proper message history, but the messages are sent to B >< This causes a lot of confusion for the recipients, and for me as well. I've tried using a different messaging app (instead of the default one), but the end result is just the same. Here's the bug captured on video: https://vimeo.com/261324755 And in screenshot form: 1. I enter the name of contact A (starting with "Lucyna") 2. I select the proper suggestion and I can see the message history with A: 3. I tap the message field, and the moment it gains focus the name of the contact in the top bar changes to contact B! Sending the message now causes it to go to the wrong person. The two contacts aren't related in any way, and I have no idea why did those two in particular get mixed. I'm on Android 7.1.2

I am trying to edit the value of a Secure Settings key over ADB with the command: settings put secure camera_double_twist_to_flip_enabled 1 For some unknown reason, the value of this key is 0 and cannot be changed. Because of this, the shake gesture in the Google Camera app does not work. I've tried a number of fixes, all with no success: - settings put --user 0 secure camera_double_twist_to_flip_enabled 1 : Fails to set value. - settings put --user 10 secure camera_double_twist_to_flip_enabled 1 : Successfully sets value for the Work Profile (aka user 10), but doesn't affect the Personal Profile (user 0) where Gcam is installed). There are no other profiles set up. - settings put secure camera_double_twist_to_flip_enabled default : Value remains at 0. - **Settings > System > Languages & input > Advanced > Flip camera** : No such toggle exists in the Settings app. - **Settings > System > Gestures > Flip camera for selfie** : No such toggle exists in the Settings app. - Boot into **Safe Mode**, then settings put secure camera_double_twist_to_flip_enabled 1 : Successfully sets value, but only temporarily. When phone is rebooted into Regular Mode, the key value is RESET TO 0. The device is an unrooted Google Pixel 7 running GrapheneOS 13 (a ROM very similar to stock AOSP). This issue is being discussed on the [GrapheneOS development forum](https://discuss.grapheneos.org/d/3214-twist-to-flip-frontback-camera-feature-missing) , where a different user running GrapheneOS 13 on a Google Pixel 6 did *not* encounter the same issue and was able to set the key value via ADB as expected.

Every since my Nokia 5.3 was upgraded to Andoid 12 recently, the battery suffers from processes com.android.phone and qcrild using the CPU a fair amount. It is not completely reproducible, but it happens especially when the the phone is locked, or at least the screen is off. I observe that increased CPU usage via adb shell top -u radio. At that same time adb shell dumpsys phone shows a lot of the following:

❯ adb shell dumpsys phone
------- PhoneGlobals -------
  mPrevRoamingNotification=0
  mDefaultDataSubId=1
  mDataRoamingNotifLog:
  isSmsCapable=true
    2022-11-23T13:56:23.510818 - dataAllowed=true, reasons=Data allowed reason: NORMAL
    2022-11-23T13:56:23.512116 - dataAllowed=true, reasons=Data allowed reason: NORMAL
[snip rest of the output]

And that seems to always immediately follow these adb shell logcat -d phone warnings about ...without a qualified user and Permission Denial to read the phone state:

11-23 13:56:23.460  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1206 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2880 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 android.os.Binder.execTransactInternal:1184
11-23 13:56:23.461  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2884 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 
11-23 13:56:23.462  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2891 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 
11-23 13:56:23.463  1681  2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)
11-23 13:56:23.463  1681  2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid 1001)
11-23 13:56:23.464  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2895 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 
11-23 13:56:23.465  1681  2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)

And that results in a lot of logging that seems to be about refreshing the data about my mobile carrier (onRefreshCarrierInfo()), which may be where the CPU time is actually spent (following log capture is from a later occurrence):

11-23 14:18:08.592  2936  2936 D ServiceStateProvider: subId=1
11-23 14:18:08.592  2462  2640 I CustomizedNetworkIcon: getConfigValueByKey: oem_key_rat_name_of_4g_int=0
11-23 14:18:08.595  2462  2640 I CustomizedNetworkIcon: getConfigValueByKey: oem_display_lte_icon_int=1
11-23 14:18:08.597  2936  2936 I Telephony: TelecomAccountRegistry: onSubscriptionsChanged - reregister accounts
11-23 14:18:08.598  1676  2040 D CompatibilityInfo: mCompatibilityFlags - 0
11-23 14:18:08.598  2936  2936 D Telephony: isEmergencyPreferredAccount: subId=1, activeData=1
11-23 14:18:08.598  1676  2040 D CompatibilityInfo: applicationDensity - 280
11-23 14:18:08.598  2936  2936 D Telephony: isEmergencyPreferredAccount: Device does not require preference.
11-23 14:18:08.598  1676  2040 D CompatibilityInfo: applicationScale - 1.0
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: onReceive Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 cmp=com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver (has extras) }
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: onServiceStateChanged, ss: 0
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: networkOperator: 20416
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: update supported roaming operator as
11-23 14:18:08.601  2936  2936 I Telephony: isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
11-23 14:18:08.601  2936  2936 I Telephony:  isRttSupported: false
11-23 14:18:08.601  2936  2936 I Telephony:  isUserRttSettingOn: false
11-23 14:18:08.601  2936  2936 I Telephony:  alwaysAllowWhileRoaming: false
11-23 14:18:08.601  2936  2936 I Telephony:  isRoaming: false
11-23 14:18:08.601  2936  2936 I Telephony:  isOnWfc: false
11-23 14:18:08.607  2462  2640 E CustomizedImsIcon: customizedVoLTEandVoWiFiIcon:
11-23 14:18:08.608  2462  4440 I CustomizedImsIcon:  customizedImsIcon:++
11-23 14:18:08.608  2462  4440 D CustomizedImsIcon: isAirplaneModeOn: false
11-23 14:18:08.608  2462  4440 D CustomizedImsIcon: customizedImsIcon:clear all vowifi icon which is added with TAG when airplane is off
11-23 14:18:08.608  2462  4440 I CustomizedImsIcon:  isOperaterCustomized:mccmnc=20416
11-23 14:18:08.609  2462  4440 I CustomizedImsIcon:  isOperaterClaroCustomized:mccmnc=20416
11-23 14:18:08.609  2462  4440 I CustomizedImsIcon:  isCustomizedBySkuId:isCustomized=false
11-23 14:18:08.609  2462  4440 D CustomizedImsIcon: getSimCount: simCount=1
11-23 14:18:08.610  2462  4440 I CustomizedImsIcon:  isWifiCallingAvailable: isImsRegistered is false
11-23 14:18:08.610  2462  4440 I CustomizedImsIcon:  isShowVoWiFiIcon: isAllowed=false
11-23 14:18:08.612  2462  4440 I CustomizedImsIcon:  isAllowShowVoLteIcon:OEM_ALLOW_SHOW_VOLTE_ICON_BOOL=false  phoneId=0
11-23 14:18:08.612  2462  4440 I CustomizedImsIcon:  isShowVolteIcon: isAllowed=false
11-23 14:18:08.613  2462  4440 I CustomizedImsIcon:  customizedImsIcon:--
11-23 14:18:08.615  2936  2936 I Telephony: reRegisterPstnPhoneAccount: subId: 1 - no change
11-23 14:18:08.615  2936  2936 D CallNotifier: updatePhoneStateListeners: update CF notifications.
11-23 14:18:08.616  2936  2936 I NotificationMgr: updateCfi: subId= 1, visible=N
11-23 14:18:08.616  2936  2936 I NotificationMgr: updateMwi(): subId 1 update to false
11-23 14:18:08.618  2462  2462 D KeyguardUpdateMonitor: received broadcast android.intent.action.SERVICE_STATE
11-23 14:18:08.618  2462  2462 V KeyguardUpdateMonitor: action android.intent.action.SERVICE_STATE serviceState={mVoiceRegState=0(IN_SERVICE), mDataRegState=0(IN_SERVICE), mChannelNumber=1656, duplexMode()=1, mCellBandwidths=[], mOperatorAlphaLong=Simpel, mOperatorAlphaShort=Simpel, isManualNetworkSelection=false(automatic), getRilVoiceRadioTechnology=14(LTE), getRilDataRadioTechnology=14(LTE), mCssIndicator=unsupported, mNetworkId=-1, mSystemId=-1, mCdmaRoamingIndicator=-1, mCdmaDefaultRoamingIndicator=-1, mIsEmergencyOnly=false, isUsingCarrierAggregation=false, mArfcnRsrpBoost=0, mNetworkRegistrationInfos=[NetworkRegistrationInfo{ domain=CS transportType=WWAN registrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[VOICE,SMS,VIDEO] cellIdentity=CellIdentityLte:{ mCi=70817281 mPci=66 mTac=527 mEarfcn=1656 mBands=[] mBandwidth=2147483647 mMcc=204 mMnc=16 mAlphaLong=Simpel mAlphaShort=Simpel mAdditionalPlmns={} mCsgInfo=null} voiceSpecificInfo=VoiceSpecificRegistrationInfo { mCssSupported=false mRoamingIndicator=1 mSystemIsInPrl=-1 mDefaultRoamingIndicator=-1} dataSpecificInfo=null nrState=**** rRplmn=20416 isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=PS transportType=WWAN registrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=CellIdentityLte:{ mCi=70817281 mPci=66 mTac=527 mEarfcn=1656 mBands=[] mBandwidth=2147483647 mMcc=204 mMnc=16 mAlphaLong=Simpel mAlphaShort=Simpel mAdditionalPlmns={} mCsgInfo=null} voiceSpecificInfo=null dataSpecificInfo=android.telephony.DataSpecificRegistrationInfo :{ maxDataCalls = 20 isDcNrRestricted = false isNrAvailable = false isEnDcAvailable = false LteVopsSupportInfo :  mVopsSupport = 3 mEmcBearerSupport = 2 } nrState=**** rRplmn=20416 isUsingCarrierAggregation=false}], mNrFrequencyRange=0, mOperatorAlphaLongRaw=Simpel, mOperatorAlphaShortRaw=Simpel, mIsDataRoamingFromRegistration=false, mIsIwlanPreferred=false} subId=1
[...snipping a lot more similar logging...]

What could be wrong? Or at least, how can I further debug this?

So I have this bug, I already reported it to OnePlus but didn't get any feedback. I have a OnePlus 8T, which has a physical notification slider above the lock button on the side of the phone. This slider will put the phone in silent, vibrate, or sound-on mode. The bug is that whenever I do this when I'm in the google chrome app, it will start a search on page. Is this a bug that people know about? Is it a feature? Any ideas what it could be? I provided a screenshot below to show what I mean. Sorry for the dutch, but as you can see it started a "search on page" when on the right you see that it also switched to vibration mode