Develop Bugs

[Q] android most annoying bugs

hi,
well i'm against that policy, not able to post at developer threads under 10 posts, else I would have question that directly,...
I've tried several roms and ended at slim beam, first to 4.2.1 which states at stable but also tested the new one 4.2.2 build 2.5
actually i'm fine with the roms, also slim bean but I do have a 3 major issues with all of them which may be related to S3 and asop/cm:
1.) problem using my apple iphone earbuds (yes I'm a iphone user too)
sometimes after mute the microphone, it won't work after de-mute, keep on muted !
microphone not working after re-connecting earbud on a running call, sometimes no audio on earbuds too, sometimes audio even do not work for the whole device -> reboot etc,...
I've found several possible solutions, non of them has worked.
why android doesn't work with that kind of TRRS earbuds, are they incompatible from hardware point of view, do I need special ones which will work on S3.
2.) problem with direct dialing from calendar, not respecting RFC2806
i really need this very often to join conference calls, sometimes the host creates an conf call and including a number with pin as the location.
well almost every mobile os recognizes this and i'm able to direct dial in on selecting the string: iphone, win, even blackberry, but not android.
i know there might be additional apps which can handle this, but it should be implemented into core apps as this is a well known standard and specified in a RFC.
3.) not recognize AP with highest signal strengh within same SSID
it seems that android devices are not able to seamless switch over to different AP within a wifi network with same SSID.
if moving out of range of AP1 and into range of AP2, android devices for some reason are not able to switch to AP2 (with higher signal strengh), therefore it states at AP1 without beeing able to establish any connectivity (because AP1 out of range). as workaround users needs to disable/enable wifi ;-(
this is also something where I have to find a workaround in my current project (creating huge wifi network over europe), because market share of androids is that high and it still have this serious annoying bug.
thanks,
nean

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
10 post rule is there to protect developers from spam and users not knowing what belongs in a development thread and what belongs in Q&A

1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing

CNexus said:
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
Click to expand...
Click to collapse
thanks for the reply.
ad 1,2,3.) hmmm, is this working on googles stock os and eg on nexus?
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....

nean24 said:
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
Click to expand...
Click to collapse
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.

tazfanatic said:
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
Click to expand...
Click to collapse
thats correct, but it doesn't work on galaxy stock os either, that's why I've tried custom roms just to find out if its related to samsung stock rom or if its a general android behavior. well the outcome was that it works on aosp/cm a bit "better" (shorter timeout) but not seamless.
my intention is not about to blame anyone, just like to find out where I can adress this issue, or do I need to get in contact with google?
rgrds

Note II Bluetooth issue

Trying to find a kitkat ROM that supports Voice dialling via Bluetooth on my note II sgh-i317m. If I role back to 4.3 it works fine (like DN3). I am currently testing CM11 and it does not work (unless somebody has a work around)
Most bluetooth functions work fine except voice dial. I hit voice commands on my Jabra and it does hear my commands. I also tried a Motorla bluetooth device and experienced the same.

Moved to Q&A.

Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.

FYI, over the last few days, I installed both Official AT&T / Samsung KitKat 4.4.2 and Ditto Note 3 v5.2 (based on 4.4.2) and they both properly support Bluetooth audio and microphone for voice command after a button press.
AT&T / Samsung Official:
Unfortunately comes with a version of Google Search (v.3.6) that provides the terrible Google Voice Dialer in response to a bluetooth button press, so if you were planning on using that, be prepared to root, move it from /system/ to /user/, uninstall, and then go find and install Google Search v.3.4.
S-Voice works fine, but you may need to switch your APN from "phone" to "nxtgenphone," if you haven't done so already. Else, S-voice may only work on wi-fi, not mobile data. Check out the thread on doing so here:
http://forum.xda-developers.com/note-3-att/general/psa-s-voice-stops-volte-markets-using-t2848929
Ditto Note 3 v5.2:
Comes with Google Search 3.4 which gives correct "Listening.." when bluetooth button pressed. Be sure to uncheck auto update in google play store until Google gets their crap figured out. Phone will flash as N7105, so download and use the build.prop for i317 from their extra files and turn on the telephony.lteOnCdmaDevice=1 setting. Set also ro.product.locale.language=en_US and ro.product.locale.region=US since you're an AT&T customer. You'll also need to add the nxtgenphone APN as above, I'm afraid. It's not rooted as it comes - use your recovery to flash the SuperSU binary of choice from your SD card after installation if you want root. It all works, though, and is my OS now.
rmzalbar said:
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
Click to expand...
Click to collapse

General Automatic Play Store app updates delay - individual apps were set to not receive automatic updates

Back a couple of weeks ago or so at least two people mentioned they weren't receiving automatic updates to their apps. I can't find the thread now when I search for it - was probably posts buried in one of the existing threads.
I was having a problem with one particular app yesterday, and I was wondering if it needed an update. It didn't, the problem was probably the particular company's, but I noticed there were over 40 apps that needed updates, and just now I received a notification that 24 apps had updates available.
I chose to update them all, and then after they updated I started checking each of them one by one on the Play Store, and they were all set to not Auto update. I've had this before but only work select apps, not a bunch.
I don't know if it's related to me using Swift Backup to restore only some apps' data or what could do this. Even Swift Backup was set not to auto-update.
It's frustrating that after all this time there's no way to just get a list of those set but to auto-update and not, and be able to toggle a bunch all from one screen instead of each individually.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I keep getting 'unable to update' or whatever. Some apps only update by manual update

Hmm, that's an oddity. I'll start with some simple guesses for what could potentially be causing such an issue.
This hasn't happened to me yet, however, I don't use any backup apps after a full wipe or a phone swap; so that could potentially be affecting your device's apps. But also - and this probably isn't related to the problem - but do you disable verity and verification each time that you flash an update? So many people have been saying that it is no longer necessary, however, I have been doing it every single time just in case. Lastly, you are definitely using the correct factory image from Google's site, right? If you purchased the phone directly from Google, you're not supposed to use the image labeled as "For US Carriers" (although I'm not sure that using that image anyway would cause this issue)... These are all things that I've learned/started doing just to play it safe.
*Edit* - Oh, and which Google Play system update are you rocking?

fil3s said:
I keep getting 'unable to update' or whatever. Some apps only update by manual update
Click to expand...
Click to collapse
Interesting! Have you looked at any of those apps' individual checkboxes to see if they're set to auto-update?
NippleSauce said:
Hmm, that's an oddity. I'll start with some simple guesses for what could potentially be causing such an issue.
Click to expand...
Click to collapse
Hi, thanks for your suggestions on the subject.
Update of sorts: I scrolled through all 256 apps (not all of them user apps, and now uninstalled two) and didn't detect any particular pattern to the ones which had the checkbox set and which didn't. I believe among stock (in the firmware) installed apps that they were usually checked but I didn't pay close attention if any of those were not. I believe there were a few that were not.
At least 75% of the apps, but definitely not all - even not all of the user-installed apps, had auto-updates disabled.
As a side note, besides the usual pain of having to check that setting for each individual app, it's especially a pain to try to hit the 3-dot menu button right beside the curved edge of the screen, 250+ times. There was more than one app that it took several trials and errors to click the menu button.
NippleSauce said:
This hasn't happened to me yet, however, I don't use any backup apps after a full wipe or a phone swap; so that could potentially be affecting your device's apps.
Click to expand...
Click to collapse
The most recent time I factory reset, I only restored backups through Swift backup for particular apps that don't implement Google's cloud backup for the app data. I didn't restore the actual apps, just the data. Previous to that, I had actually had Google's cloud backup restore everything. I always do and have never had any obvious problems for several years now.
NippleSauce said:
But also - and this probably isn't related to the problem - but do you disable verity and verification each time that you flash an update? So many people have been saying that it is no longer necessary, however, I have been doing it every single time just in case.
Click to expand...
Click to collapse
I did disable them the last time that I flashed because I knew I was going to be flashing the updated CleanSlate kernel and I wasn't sure if it was still going to be necessary. At this point, I don't remember if I later flashed verity and verification without disabling them (to enable them).
When the January update arrives, I plan on not disabling verity and verification. I know that the CleanSlate kernel has been updated to not require those being disabled.
NippleSauce said:
Lastly, you are definitely using the correct factory image from Google's site, right? If you purchased the phone directly from Google, you're not supposed to use the image labeled as "For US Carriers" (although I'm not sure that using that image anyway would cause this issue)... These are all things that I've learned/started doing just to play it safe.
Click to expand...
Click to collapse
I am on raven-sq1d.211205.017-factory-bf3da4b2 - for all U.S. Carriers.
You are the second or third person who has said in this section that the US Carrier image isn't the correct one if using the factory unlocked variant. I'd like to know what the source is of this information, as no one has pointed to an article or official Google source saying one way or the other.
At this point, over two months since my wife and I received our P6Ps, I don't remember the exact firmware that was on it, nor the exact OTA version that was available immediately - either one of the following two:
SD1A.210817.019.B1, Oct 2021, AT&T
or
SD1A.210817.019.C2, Oct 2021, T-Mobile (US), USCC, Google Fi, CA, & TW carriers.
I tend to keep things simple when possible and my interpretation and advice to everyone who has asked what update they should flash is simply, whichever one matches your carrier. After all, they contain radio optimizations geared towards the carrier(s) available in those areas. Certainly, all of the firmware versions work on any bootloader unlocked Pixel, but without evidence to the contrary, I have no reason to think I shouldn't be flashing the one for U.S. Carriers, and the December one that didn't specify a particular place would be for "everywhere else" other than the three others which did specify.
If you can lead me to the solid information that says I shouldn't, I'd greatly appreciate it. I'm not trying to be contrary or argumentative - I'm just genuinely curious what the source is for this information. It would have to be a very solid source for me to change my thought on the matter.
NippleSauce said:
*Edit* - Oh, and which Google Play system update are you rocking?
Click to expand...
Click to collapse
I am on the November Play System update, with no update available.
Before I accidentally factory reset my phone three weeks ago, I had gotten the December Play System update. I remember reporting at the time in a thread here which someone made about the Play System update that the phone reported the update to December was ~650 MB, which was tons larger than what most were reporting as ~50 MB or so. As others have speculated, there are probably multiple updates available in the same month sometimes, so perhaps I was on an older October update before that, and most others were already on November - just speculation, though.
I didn't root right away because I was waiting on all the positive reports on success and methods, and then I had to wait for a time I felt comfortable taking the time necessary to set everything up on the freshly factory reset phone. I believe I had unlocked the bootloader immediately, as I knew that would factory reset and would be necessary for rooting, but of course then there was the disabling verity and verification which I didn't know about when I unlocked the bootloader, anyway, so I did that later, and then I had to factory reset yet again.
For the record, I haven't had any other problems, like others have.

Interesting! Have you looked at any of those apps' individual checkboxes to see if they're set to auto-update?
Click to expand...
Click to collapse
Yeah it's setup to automatically update as I have unlimited wifi. I just get one or two apps fail to update about once a day.

fil3s said:
Yeah it's setup to automatically update as I have unlimited wifi. I just get one or two apps fail to update about once a day.
Click to expand...
Click to collapse
You took a look at my screenshots in the OP? I just want to make sure you and I are talking about the same thing. My Play Store settings, in general, have always (or at least for many, many years) been set to auto-update over both Wi-Fi and mobile data connections (I used to do Wi-Fi only a long time ago as well), however, each app's page in the Play Store has its own individual checkbox for auto-update located in the upper right corner's 3-dot menu, which is independent of the overall Play Store settings for auto-update, and takes overrides it, at least when the general setting for the Play Store is to auto-update.
I haven't had the issue you're having with 'unable to update' or anything similar, for what it's worth.

roirraW edor ehT said:
You took a look at my screenshots in the OP? I just want to make sure you and I are talking about the same thing. My Play Store settings, in general, have always (or at least for many, many years) been set to auto-update over both Wi-Fi and mobile data connections (I used to do Wi-Fi only a long time ago as well), however, each app's page in the Play Store has its own individual checkbox for auto-update located in the upper right corner's 3-dot menu, which is independent of the overall Play Store settings for auto-update, and takes overrides it, at least when the general setting for the Play Store is to auto-update.
I haven't had the issue you're having with 'unable to update' or anything similar, for what it's worth.
Click to expand...
Click to collapse
I use swift backup Pro also, but haven't used it on my p6pro yet.
Yeah sorry about that I didn't read your post properly. Blame the psyche meds I'm on, or my frontal lobe damage

fil3s said:
I use swift backup Pro also, but haven't used it on my p6pro yet.
Yeah sorry about that I didn't read your post properly. Blame the psyche meds I'm on, or my frontal lobe damage
Click to expand...
Click to collapse
LOL!!! No sweat.

I've been noticing the same. However I also saw this issue on my OP8T running LOS18.1. I do manually disable auto-update on YouTube (since I use Vanced) all other apps are set to auto-update. I wonder if it has to do with having even one app not set to not auto-update or if it is Swift (since Google doesn't restore my 2FA Authenticator data and until recently you couldn't export).
As for the question about Verity, mine is off from when I rooted right after Dec update when it was required.

Based on your response, I'm going to guess that this could either be due to the incorrect factory image use or due to the use of SwiftBackup. We're both on the Play System update from November - so that seems like an unlikely cause.
I, personally, never backup anything before wiping my phone. Does that make it a real pain in the arse to setup again? It definitely does =(.
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Also for the disable verity and verification stuff - I still don't think it could be causing the issue, however, I've been sure to disable it with every single factory image update. So perhaps this has more of an impact on stability than was previously thought .
Regardless, my apologies for my crummy formatting in this response and also for possibly missing some details. I'm on mobile right now and have had a severe traumatic brain injury about a year and a half ago. After reading the short message from @fil3s , it seems that XDA is the safe ground for us brain injury nerds, haha =)

NippleSauce said:
Based on your response, I'm going to guess that this could either be due to the incorrect factory image use or due to the use of SwiftBackup. We're both on the Play System update from November - so that seems like an unlikely cause.
Click to expand...
Click to collapse
Of those two choices, I would lean towards Swift Backup, however, I doubt if it's that either since I definitely didn't restore anything using Swift for so many of my apps - I only restored very select apps' data after I had restored from Google Backup. Hell, it could be a Google Backup/Restore bug for all I know. I've had nothing (else) but good experience with restores from Google over the last five years or so.
NippleSauce said:
I, personally, never backup anything before wiping my phone. Does that make it a real pain in the arse to setup again? It definitely does =(.
Click to expand...
Click to collapse
I prefer to manually over-backup and restore only what I need to as I need it - any app data that Google's Cloud Backup didn't restore for apps that are slightly more painful to remember how I had them set up. It's better for me to not need the data but have it backed up, then need it and not have it backed up.
NippleSauce said:
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Click to expand...
Click to collapse
I'll definitely need more than that before I switch my thinking on that subject, but thank you for sharing what you do know or remember. The easy way to find out, of course, is for someone who's completely on stock unrooted, preferably even bootloader still locked, running on AT&T like me to share with us which December OTA they received - for those relatively few who actually received it.
I may go ahead and make a question thread/XDA poll on the subject: Poll only for non-rooted factory unlocked P6P owners running on any US carrier who received the December over the air update, not manually flashed
NippleSauce said:
Also for the disable verity and verification stuff - I still don't think it could be causing the issue, however, I've been sure to disable it with every single factory image update. So perhaps this has more of an impact on stability than was previously thought .
Click to expand...
Click to collapse
I doubt if it is a factor for stability, or at least only indirectly through the increased security they provide. See the section on that subject with information that other more knowledgeable folks in the first four posts in my P6P thread that I have in my signature below if it's information you're not already aware of.
NippleSauce said:
Regardless, my apologies for my crummy formatting in this response and also for possibly missing some details. I'm on mobile right now and have had a severe traumatic brain injury about a year and a half ago. After reading the short message from @fil3s , it seems that XDA is the safe ground for us brain injury nerds, haha =)
Click to expand...
Click to collapse
I'm very sorry to hear about your brain injury. I hope you cope as well as possible. Don't worry about formatting - even if it's not easy to read/digest XDA's newer software makes it easier to break up into chunks and respond to individual portions, from what I remember over the old software. My brain issues are more psychological (so far), however, the Army did feed us beef that was potentially from mad cows in Britain in the mid-1980s, but the only way anyone will ever know if I was exposed to it is if I die from it - at least that was the information that was given to me when I found out about that almost 20 years ago when I went to give blood.

roirraW edor ehT said:
Back a couple of weeks ago or so at least two people mentioned they weren't receiving automatic updates to their apps. I can't find the thread now when I search for it - was probably posts buried in one of the existing threads.
I was having a problem with one particular app yesterday, and I was wondering if it needed an update. It didn't, the problem was probably the particular company's, but I noticed there were over 40 apps that needed updates, and just now I received a notification that 24 apps had updates available.
I chose to update them all, and then after they updated I started checking each of them one by one on the Play Store, and they were all set to not Auto update. I've had this before but only work select apps, not a bunch.
I don't know if it's related to me using Swift Backup to restore only some apps' data or what could do this. Even Swift Backup was set not to auto-update.
It's frustrating that after all this time there's no way to just get a list of those set but to auto-update and not, and be able to toggle a bunch all from one screen instead of each individually.
View attachment 5503665
View attachment 5503667
Click to expand...
Click to collapse
I've been noticing the same with my Pixel 3 and 6 Pro. When I upgraded my 3 to Android 12, I had trouble updating apps and checked the setting. It was turned off, for almost every app (I never did turn any of these boxes off manually). I guess it's an Android 12 thing-y / bug. Since my P6 Pro also had several of these settings turned off, it has probably nothing to do with upgrading to Android 12, but Android 12 in general just being a buggy mess.

Morgrain said:
I've been noticing the same with my Pixel 3 and 6 Pro. When I upgraded my 3 to Android 12, I had trouble updating apps and checked the setting. It was turned off, for almost every app (I never did turn any of these boxes off manually). I guess it's an Android 12 thing-y / bug. Since my P6 Pro also had several of these settings turned off, it has probably nothing to do with upgrading to Android 12, but Android 12 in general just being a buggy mess.
Click to expand...
Click to collapse
Thanks! That does sound more likely. I guess I can officially list myself as having one problem.

Question S21FE 5G bluetooth not working for calls ever since update to andorid 13, media is fine

Please help me with crazy problem. I just spent a lot of $$ for bluetooth hands free Plantronics Voyager 5200. When connected to S21 FE, media is fine but I can't hear anything and other side can't hear me. Headset works with other phones. After this, I came to realisation that my bluetooth for calls stopped working ever since my phone update to android 13, i could not use it in the car anymore, but I just thought "meh, i will fix it next time" and never really bothered anymore.
I would not come here and ask for help if I didn't try for like 24 hours already all kinds of things. The only thing I didn't do is the factory reset becasue i have so many authentication and figital signature apps that i will need another 6 hours to set them up.
On samsung forums i did see a lot of similar feedback but with crap replies from samsung support.
I can't wipe bluetoooth app cache as it is greyed out, same like many other users. If anyone has some good idea about this, any input is appreciated. Thanks!

I have the same problem and Factory Reset doesnt Fixed it.
I didnt manage to fix this without using an GSI.

So you want to go back to Android 12, right ?

This shouldn't be possible due my Binary Value is higher than Android 12.
And I cannot say If it is an Issue from Android 12 or General because It randomly happened (in my case).

Do you think it is because you upgraded to Android 13

This might be the original firmware error...

Back up with smart switch and do a factory reset

Or install an Android 12 ROM via Odin

The original one

General Whomp - A Tale of Swift Return (lol)

Kind of bummed, ahh well.
Now that that is unrooting and relocking is out of the way... have to say I am sad about this one. I was excited for it, spent HOURS getting it all setup. You all know the deal, lol.
Ran into two issues that I found that apparently showed up with OnePlus' implementation of Android 12 and persist even still... all this time later.
1. The Display Timeout option is not properly (normally) exposed to things like Tasker
2. Call redirection (for things like Google Voice) is broken
I recognize that these are probably issues that 90% of people don't notice/care about, but they're also extremely well documented and reported in all of the normal OnePlus places. I find it bonkers that after all this time, those issues still exist. I use Google Voice to make calls as needed for business when I am on the move without exposing my personal number (and to avoid carrying two devices). I made a number of calls before realizing that it was not working properly (since it's not obvious).
Coupled with some of the little Pixel things I was fine giving up... eh. Just feel sour about long time bugs like that.
Maybe I will try the OnePlus 12 next year. For now, the OnePlus 11 goes back to Amazon.
Just a little rant into the void.

I can't believe they still haven't fixed call redirection. That's been an issue since Android 12 on the OP9. It was so annoying I just switched Google Voice to prefer wifi/mobile data and used the dialer in the app to work around it.

EtherealRemnant said:
I can't believe they still haven't fixed call redirection. That's been an issue since Android 12 on the OP9. It was so annoying I just switched Google Voice to prefer wifi/mobile data and used the dialer in the app to work around it.
Click to expand...
Click to collapse
Yeah... I could work around that... yes, it would be annoying when I am getting in the car to remember to have to get out of the parking lot (off wifi) before making the call... but it would end up ok. Then sometimes (hit or miss in my experience) the call would get messed up when I arrive somewhere and connect to wifi again during the call).
And I could work around the Display Timeout issue using different apps and such.
And workaround this and that, etc. But it's just BS to me. Like... fix these old bugs that you create in your build that don't exist in Android/every other build. Admittedly, I was really annoyed at the several calls I made where I had no idea the wrong number was being shown on the receivers ID. Soured the whole thing for me.

dmarden said:
Yeah... I could work around that... yes, it would be annoying when I am getting in the car to remember to have to get out of the parking lot (off wifi) before making the call... but it would end up ok. Then sometimes (hit or miss in my experience) the call would get messed up when I arrive somewhere and connect to wifi again during the call).
And I could work around the Display Timeout issue using different apps and such.
And workaround this and that, etc. But it's just BS to me. Like... fix these old bugs that you create in your build that don't exist in Android/every other build. Admittedly, I was really annoyed at the several calls I made where I had no idea the wrong number was being shown on the receivers ID. Soured the whole thing for me.
Click to expand...
Click to collapse
Totally agreed. I dumped my OnePlus 9 for the Pixel 7 Pro and chose the S23 Ultra over the much cheaper OnePlus 11 because of my software experience with the 9.

EtherealRemnant said:
Totally agreed. I dumped my OnePlus 9 for the Pixel 7 Pro and chose the S23 Ultra over the much cheaper OnePlus 11 because of my software experience with the 9.
Click to expand...
Click to collapse
I would love to try the S23 Ultra, but from what I've read... the hoops to unlock and root are just a pain. Getting an import model, etc etc.
I root for many fewer reasons than I once did... but I still have reasons to do it. Someday.

dmarden said:
I would love to try the S23 Ultra, but from what I've read... the hoops to unlock and root are just a pain. Getting an import model, etc etc.
I root for many fewer reasons than I once did... but I still have reasons to do it. Someday.
Click to expand...
Click to collapse
Yeah I kept my Pixel for my rooting needs (really just for Network Signal Guru) and haven't missed it at all on the S23U. There's no way I'll ever import a phone with all the compatibility issues AT&T and Verizon have with them plus they never have n71 for T-Mobile either.

EtherealRemnant said:
Yeah I kept my Pixel for my rooting needs (really just for Network Signal Guru) and haven't missed it at all on the S23U. There's no way I'll ever import a phone with all the compatibility issues AT&T and Verizon have with them plus they never have n71 for T-Mobile either.
Click to expand...
Click to collapse
Every year I think more and more about it. At this point I am using root for 4 apps and only 2 of them matter.
1. Adguard - So I can nicely adblock without using VPN style blocking.
2. Swift Backup because I actually find myself regularly wanting to roll back or recover.
The other two are Tasker, but that's mostly just for self granting permissions, and my file explorer that I can easily live without.

dmarden said:
Every year I think more and more about it. At this point I am using root for 4 apps and only 2 of them matter.
1. Adguard - So I can nicely adblock without using VPN style blocking.
2. Swift Backup because I actually find myself regularly wanting to roll back or recover.
The other two are Tasker, but that's mostly just for self granting permissions, and my file explorer that I can easily live without.
Click to expand...
Click to collapse
I switched to Brave so I don't need an ad blocker (ads in apps don't bother me, just the nonsense that happens in the browser, and in fact I get free service from Boost for watching ads anyway) and I started noticing problems with backups that included app data so I just switched to Google Backup. I will say though, Shizuku is supported by Swift Backup. You can back up and restore everything except the app data without root using Shizuku.

EtherealRemnant said:
I switched to Brave so I don't need an ad blocker (ads in apps don't bother me, just the nonsense that happens in the browser, and in fact I get free service from Boost for watching ads anyway) and I started noticing problems with backups that included app data so I just switched to Google Backup. I will say though, Shizuku is supported by Swift Backup. You can back up and restore everything except the app data without root using Shizuku.
Click to expand...
Click to collapse
Yeah, I have needed that app data a number of times... for better or worse, I guess.

I'm selling my OnePlus 11. The software is beyond frustrating and the simple tweaks one can do with Developer Options and ADB are either locked out on this phone or revert to defaults upon reboot. Clearly, OnePlus doesn't listen to their fan base outside of China. The development potential was what drove me to buy this, but it has been a complete disappointment. The lack of wireless charging has also proven to be an inconvenience and I don't trust the longevity of the charging port.
It looks like if you want a Snapdragon 8 Gen 2 running clean versions of Android, Motorola and Sony are the way to go.