Database Info

Oreo Update, speaker weirdness?

Hello all,
There is a consistent issue that i have been dealing with ever sense the Oreo update rolled out that I have not been able to find a solution for. At times ( watching a Youtube video/ listening to music from Spotify) media audio would begin playing from the phone as if it was ring/ notification audio. All sounds coming from the phone would get cut back in volume by a significant amount and the bottom speaker stops firing completely.
This only seems to happen once I interact with the app after starting to play the video/song (i.e i go to pause a video/ advance 10 seconds). From that point I would need to leave the app and come back for the audio to go back to normal.
As well I have been having audio video sync issues with the Youtube app that I have never dealt with before, related?
I have the US duel sim variant
I am on build number 47.1.A.5.51 , November security patch
I have tested with all audio settings on/off ( EQ, S-Force,ClearAudio+,normalizer)
I have checked the service test menu and everything is shown as calibrated.
Restarted the phone, cleared various caches for apps
I really am at a loss here, anyone else having these issues? Any possible causes/ solutions?

I had that issue on the first version of oreo... I found the latest oreo update fixed it. Maybe uninstall youtube app and reinstall again?

Were you able to fix this issue?
I have the same problem but for me it happens on all applications.
Mate 20 Pro on EMUI 10, although the issue was also there on EMUI 9

Hi all,
I have what seems to be the same issue but in Android 9 PIE, & latest build 47.2.A.10.107.
I didn´t had this issue in my Xperia XZ Premium G8141 (single SIM) , now it happens after switching to a Xperia XZ Premium G8142 (same phone, but dual SIM, same as you have).
In my case I get around opening volume controls and moving the ring and notification volume (with its slider) for some amount back and forth.
Y don´t use youtube so much (in the phone screen) then I cannot tell if it happens with youtube, but does happen in Spotify and it is very annoying to have to correct every now and then.
Then, same phone, completely different Android version, hardware problem?
Will appreciate any hints or troubleshooting tips from you guys.
When I have some time I will take a look to the kernel messages cable-connecting the phone for USB-debug.
Thanks in advance,
Take care,
Alvaro

Android 11 Beta 2 Released

Just downloaded the Beta 2 OTA from google's site: https://developer.android.com/preview/download-ota#
Go get it!! Already downloaded and installed on my P4XL. Checking it out now.

Yup just downloaded and flashed and have root still??

Currently on it! Improvement in animation in some places, better landscape to portrait transition.
Missing clock option from themes
Music player now looks better, I think no more an experimental feature.
Final api released good for developers.
Recently screen tweaked a bit no share option anymore.
Yet to find other changes
---------- Post added 09-07-2020 at 12:25 AM ---------- Previous post was 08-07-2020 at 11:47 PM ----------
Restart button vanished from power menu! Great

Updating my Taimen now. About to be in a meeting so I need my Coral working, do will update later.
From Coral, with Tapatalk

Problems I have noticed are
The screen flickers a lot especially when using dark theme and a dark themed app.
I'm also missing new media controls.
Anyone got these problems?

does the navigation bar still remain on the home screen even on beta 2?

Flickering here too

Rotten Ross said:
Problems I have noticed are
The screen flickers a lot especially when using dark theme and a dark themed app.
I'm also missing new media controls.
Anyone got these problems?
Click to expand...
Click to collapse
I have the flicker issue too, media controls are there though.
I've noticed there's no longer the option to force 90hz now either in developer settings which I presume would resolve the flicker issue.

CodeFox said:
I have the flicker issue too, media controls are there though.
I've noticed there's no longer the option to force 90hz now either in developer settings which I presume would resolve the flicker issue.
Click to expand...
Click to collapse
Just done a quick test and turned brightness up above 70%ish the flickering stops or just isn't noticeable.

Flicking is so annoying.. is there any fix?
Maybe custom kernel? I can't watch on this stroboscope

Anyone got Magisk working on the new beta? The canary build that was reported working on beta 1 isn't booting for me. (I never tried beta 1 myself.)

Here is my experience...
1) The flickering screen is annoying
2) I had no problems rooting via Magisk
2a) After rooting my Messages app stopped receiving messages but I was able to send them without issue
2b) I could not update apps from the Google Play store. It would just say "Downloading" but nothing would happen
2c) The Google weather widget on the home screen would not show the weather nor would it take me to Google weather when I clicked it. It seemed disabled.
I have since re-flashed the latest Beta but didn't root. All of the above issues, aside from the screen flickering, have been resolved,

Lots of flickering

Terrible flickering...
The flickering exists also at Beta 1 but only at very low brightness (environment and system brightness). Now screen flickering regardless of environment and system brightness (except at extreme high system brightness...) as long as background is not totally black.

Flickering sucks! OMG! No media controls here but do have force 90hz option still

Hopefully the flickering issues can be fixed with a 2.5 patch or maybe play services/kernel update ??

tardis_42 said:
Anyone got Magisk working on the new beta? The canary build that was reported working on beta 1 isn't booting for me. (I never tried beta 1 myself.)
Click to expand...
Click to collapse
I have tried a few ways no luck yet.
As for other people the flicking screen I have it in this beta . I had it before Beta too, It's the 60hz - 90hz refresh rate. Sucks to say but if you disable it fixes the problem.

I don't see the flickering on my device. Yes to using dark mode, force dark mode, enabling 90 Hzv display (no more force), and playing a couple games at well as watching videos, reading news...
It never shows. Or else I am not recognizing it - and I'm pretty sure I know what flickering means, so....
I do use figure mode to automatically pause most of my games and SoS I don't normally use at work during work hours, so maybe that is why?
Or else something else I might have done?
From Coral, with Tapatalk

I thought mine wasn't doing it to until just now. In dark room and looking at chrome settings while using dark mode. The grey background flickers like crazy... On a positive note at least it's safe to to back to Android 10 July without face unlock breaking

Anyone who is missing the new media controls, found any way to get them to work yet?

Android Auto issues on ColourOS11

Ever since updating to ColourOS11, android auto has been freezing on me when the screen is off however activating the screen will unfreeze it.
Is anyone else experiencing this or if anyone knows a fix besides 30m screen timeout.

The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...

Craphead said:
The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...
Click to expand...
Click to collapse
Yea I had a look through some other threads. Turning off AOD and Fingerprint while screen off seems to somewhat work abiet still glitchly. Been in contact with Oppo who seems to only want me to send the phone into the service centre but I am waiting for Christmas break to be over and send it then otherwise hopefully a update by then but doubts.

I just had the issue, but by leaving it plugged in and letting the connection time out, it reset and connected. Took about a minute.

I finally got the ColorOS 11 update and now Android Auto is having this issue. Really rather annoying as I've only just got a new car and had Android Auto so was enjoying it!
Basically same issue where the car screen just locks up until you unlock the phone screen (i still get audio prompts for directions in google maps etc so Android Auto is still running). Seems to be a standoff between the OEM's and Google. Looking at other forums some OnePlus phones have the same issue (BBK group thing perhaps!)

Google answer...
[FAQ] Can't connect to Android Auto on Android 11 - Android Auto Community
support.google.com

I solved this issue going into developer options and activating the "keep screen on while charging" mode. The display will remain on, but with a very low brightness level.

Screen dimming after 4-5 seconds

Hey all! I recently updated from Android 10 to Android 11 OOS 11.0.2.2 and I have a strange issue I didn't have before. On grey/blue backgrounds, the screen dims and changes color a little bit after not touching it for 4-5 seconds. I already submitted a bug report but I just wanted to see if others are having this issue. I do have a T Mobile device that's been converted to global, but again this issue wasn't present before. I can't report as to whether the issue happened on OOS updates previous because I just updated and got 11.0.2.2. I've also linked a short video here showing the issue. If you guys have any input at all, it's appreciated!

I may be having a similar issue. I am trying to view your video to see if it is the same problem. I have noticed that my color turns warm, as if the blue light filter was activated. It normally happens when I am trying to type in a field. In most situations, it happens when there is a lot of white being displayed.
I did not pay attention to the browser that I was using. It may be a Chrome issue, but that is only if we are experiencing the same thing.

Ok, so we are talking about two different things. But, your dim is very subtle, at lease as far as the camera is concerned. Does mine do the same thing? No idea. I probably never noticed.
However, are you using Adaptive Brightness or manual brightness? In my experience, OOS 11 came with a LOT of bugs. I've been getting screen orientation problems as of late, and it would lock my screen sideways depending on what I am doing. I do not use auto rotate, and I am certain that I didn't press the rotation button in the bottom right corner. Even if it showed up, it shouldn't have, as I was using my phone in portrait mode every time that bug showed up.
TL;DR: OOS 11 - YMMV.

AarSyl said:
Ok, so we are talking about two different things. But, your dim is very subtle, at lease as far as the camera is concerned. Does mine do the same thing? No idea. I probably never noticed.
However, are you using Adaptive Brightness or manual brightness? In my experience, OOS 11 came with a LOT of bugs. I've been getting screen orientation problems as of late, and it would lock my screen sideways depending on what I am doing. I do not use auto rotate, and I am certain that I didn't press the rotation button in the bottom right corner. Even if it showed up, it shouldn't have, as I was using my phone in portrait mode every time that bug showed up.
TL;DR: OOS 11 - YMMV.
Click to expand...
Click to collapse
So I have the same thing with the screen going super warm on white backgrounds too, primarily on web browsers. With the other issue it only happens with the brightness between 30-70% or so and the screen gets darker and the gamut seems to get a tad cooler but I've chalked these up to separate issues. No phone is without faults but it seems like Oneplus releases software without testing it at all.
Edit: I noticed the yellowing on Chrome, and nowhere else on the phone. Samsung internet does have the same issue

Yes, I have a slew of issues with Android 11. My problem is the fact that I like it a lot more than A10 w/OOS, sooo....I have no option but to tolerate them for the moment.

Question USB-C to headphone adapter music stops with locked screen...and can cause an OS crash?

Would some of you smarter people please help figure out what's going on? I/you can then file a bug report which won't result in it being closed due to their misunderstanding.
The primary issue is that music stops playback when a USB-C adapter is used, once the screen locks. I've used three different ones, which I can't identify the differences between with my skillset of linux, but they all produce the issues and one does treat the microphone differently.
It's not related to screen off timeout, only lock screen timeout. If I lock the screen, music stops. If I set the lock timeout 30 seconds after the screen off timeout, music stops 30 seconds after the screen is off.
The secondary and deeper issue is that if fingerprint or face unlock are enabled, it causes a 7+ second delay in unlocking, or it "breaks" screen unlocking entirely (until the adapter is removed), or can even result in a hard crash or "soft" (yeah?) crash of the OS. However, this is only if a certain type of audio session is running with Android (which I don't understand anything about), until the headphone adapter is removed. If left in, it can cause the phone not to unlock or even crash and reboot.
The broken lock screen does not occur if using an app such as Simple Music Player, although the music does still stop when the screen locks. It doesn't do the same type of audio session with the operating system that Amazon Music, Audible, or Podcast Addict do. I know this only because Wavelet doesn't detect the audio session, so it's very likely not an app issue but an OS issue with how the audio session type causes this problem.
The broken or delayed lock screen does not occur if I turn off face and fingerprint unlocking. It works normally with entering a PIN and there's no delay.
The fingerprint scanner is broken, no matter what, if face unlock is also enabled.
If I delete the stored face scan, the fingerprint scanner works but with the big delay.
After playing music and locking the screen, if I turn on the screen and wait about 7 seconds, it will unlock the screen using my face. If I try to use the fingerprint reader, it'll often, but not always, break unlocking entirely until it crashes or I remove the adapter.
If I successfully unlock it, the music is shown to be "still playing", although it's silent. If I lock it again, it's definitely broken and cannot be unlocked via fingerprint or face, and will not fallback to PIN.
If I let it sit a while (not more than 90 seconds) after that, it becomes unresponsive and the screen will not turn on again. It doesn't hard crash all the way to the bootloader, but when I unplug the adapter, the "G" loading logo is shown and then the lock screen asks me for my PIN.
I can't say how I managed to get it to hard crash to the bootloader twice, but I think those times I was quickly using the fingerprint scanner numerous times, turning the screen on and off, and I don't THINK I had a successful unlock first, during the hard crashes to bootloader.
EDIT:
Enabling "allow wired headset requests with device locked" in the Google App doesn't resolve the issue. The headset doesn't work then, either, and gets disconnected. I guess I could file a bug report on that alone and maybe the fix would trickle down to everything else...but I'd rather not.
Sorry for the wall of text, but it's not a simple scenario since I don't know what's actually going on and what's important. Hopefully one of you can help figure out the stuck process and reduce it down to two sentences for a bug report. I don't recall having this issue with my Pixel 6 Pro, but the times I used a USB-C headphone adapter with it was probably only in the first few months it was released, if at all, so a specific Android update may be to blame, but I don't know which/when.

Solved.
Yikes. So if I change my "default USB configuration" in developer options to "no data transfer", then it works normally, music doesn't stop, lock screen works normally.
Well, that solves that part, but I've loved just plugging my phone into my computer and it being ready to go without intervention. Maybe Tasker can be my savior and change the usb configuration type.
EDIT:
Tasker: Set USB for file transfer automatically - NotEnoughTech
One of the most annoying things in new Android is the inability to trust USB devices permamently
notenoughtech.com

That's odd... Did you have a bad adapter or something?
For me most of them works fine. I've tested multiple Chipsets on these (I make custom cables), like:
ES9280C
ALC5686
CS43131
All works fine on March Update....

yurishouse said:
That's odd... Did you have a bad adapter or something?
For me most of them works fine. I've tested multiple Chipsets on these (I make custom cables), like:
ES9280C
ALC5686
CS43131
All works fine on March Update....
Click to expand...
Click to collapse
I've seen multiple reports of this through several forums. Google is aware of it and working on a fix.

xunholyx said:
I've seen multiple reports of this through several forums. Google is aware of it and working on a fix.
Click to expand...
Click to collapse
Interesting guess we'll see. It's weird that it only happens to some and not others

yurishouse said:
Interesting guess we'll see. It's weird that it only happens to some and not others
Click to expand...
Click to collapse
I think it depends on what you have set up for USB in developer options

Having recently purchased a Pixel 7 Pro, I immediately set the developer option for USB to file transfer (it's even more of a chore in A13 to use the popup than it was in previous versions).
I also picked up a Jsaux USB-C DAC for use with the P7P as, unlike my P20 Pro, it doesn't support USB analogue audio (making my old adapters useless, sadly). As soon as the screen is locked, if the default setting is USB File Transfer, the music stops. If the phone is then unlocked, the app playing will hang.
I was going to return the adapter (thinking it was incompatible or faulty) but decided to check if others had a similar issue. As I only need to use wired audio occasionally, I will just have to manually switch the default setting when needed (far more common that I need the USB file transfer - I usually listen to music with my M&D MW07 earbuds).