Related
Hello all... Hoping to get some help for my unlocked AU Oppo R7plus f handset with ColorOS 2.1.1. I have a new car with Android Auto, and my phone doesn't seem to function correctly.
I've enabled developer mode to enable USB debugging which allowed my handset to be detected by my car but the audio quality is distorted using Android Auto. It isn't streaming audio quality I am referring too - all google and navigation commands and music stored on my phone have the same issue.
Its not the car or the USB cable as I've tested my Samsung and Apple handsets and they work with my car.
What else can I try?
Can you safely uninstall ColorOS and install Android Marshmallow instead? I'd need guidance
Any idea on when ColorOS 3.X will be released?
Thanks in advance!
Lukey G said:
Hello all... Hoping to get some help for my unlocked AU Oppo R7plus f handset with ColorOS 2.1.1. I have a new car with Android Auto, and my phone doesn't seem to function correctly.
I've enabled developer mode to enable USB debugging which allowed my handset to be detected by my car but the audio quality is distorted using Android Auto. It isn't streaming audio quality I am referring too - all google and navigation commands and music stored on my phone have the same issue.
Its not the car or the USB cable as I've tested my Samsung and Apple handsets and they work with my car.
What else can I try?
Can you safely uninstall ColorOS and install Android Marshmallow instead? I'd need guidance
Any idea on when ColorOS 3.X will be released?
Thanks in advance!
Click to expand...
Click to collapse
I have exactly the same issue.
I have come across this issue on updating my car radio to one that is Android Auto compatible (Hyundai i30 GD-03 radio). My phone is an Oppo R7sf ColorOS 2.1.0i, Android 5.1.1.
'All' music, voice directions, Google assistant, youtube audio come through with a horrible distortion with the original signal barely audible beneath. The distortion is a short transient produced every 43ms (approx 23Hz).
I initially thought it could be some sort of electrical interference issue (but surely the USB audio is digital?). In experimenting with audio played through Android Auto via Black Player, I came across some songs on my phone that would play perfectly!
Looking at the 'good' and 'bad' song files in detail, it became obvious that all of the distorted (bad) songs were 44.1kHz sample rate. Other files with sample rates of 96kHz and 48 kHz played perfectly.
Which now makes me think this is a software issue with my phone. I tested with my wife's Samsung Galaxy S5 and it worked perfectly.
thommo101 said:
I have come across this issue on updating my car radio to one that is Android Auto compatible (Hyundai i30 GD-03 radio). My phone is an Oppo R7sf ColorOS 2.1.0i, Android 5.1.1.
'All' music, voice directions, Google assistant, youtube audio come through with a horrible distortion with the original signal barely audible beneath. The distortion is a short transient produced every 43ms (approx 23Hz).
I initially thought it could be some sort of electrical interference issue (but surely the USB audio is digital?). In experimenting with audio played through Android Auto via Black Player, I came across some songs on my phone that would play perfectly!
Looking at the 'good' and 'bad' song files in detail, it became obvious that all of the distorted (bad) songs were 44.1kHz sample rate. Other files with sample rates of 96kHz and 48 kHz played perfectly.
Which now makes me think this is a software issue with my phone. I tested with my wife's Samsung Galaxy S5 and it worked perfectly.
Click to expand...
Click to collapse
just curious. is this issue present on Official LineageOS 14.1 for the R7S?
celoxocis said:
just curious. is this issue present on Official LineageOS 14.1 for the R7S?
Click to expand...
Click to collapse
Hi celoxocis, I am unsure. My R7S is currently stock (it is my day-today phone). I COULD try and install Lineage, although currently don't want to risk bricking anything (small chance I know). So I'm PROBABLY going to get a new phone at some stage. So then I'd be able to test out LineageOS
I've paired my pixel 2 with my uconnect system in my Jeep. Two issues, 1 the metadata (song titles and track info) doesn't show on the screen in my car. This worked fine on my last several phones. I've tried deleting and pairing again but it doesn't help. 2, the navigation directions from Google maps do not come through my car's speakers despite having that option checked in gmaps settings. Anyone having similar problems and figured out a fix? I'm on 8.1 Dev preview, and this also did not work on 8.0. I can't imagine that the phone isn't capable.
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
pabarker said:
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Terrible, hope they fix it soon. Thought maybe 8.1 would help but no luck.
I feel sorry for you guys. OG Pixel had bluetooth issues on some cars and some of those issues are still not fixed 1 year later.
Bluetooth is great for me on my cars. Both newer GM vehicles. One with Android Auto, one without.
I have an SRT Hellcat with UConnect. It completely does the same type of stuff. Sometimes it fails to transfer calls. It also shows "Pixel 2" often rather than song titles, etc. If I disconnect BLE and reconnect it usually works better the second time. It is annoying.
How do they screw this up every year. Using play music now completely locks up my uconnect RHR radio. I really wish Google would test things before rolling out. I wish they would just release there new phones on the previous Android version and have a beta of the current since they always screw something major up.
---------- Post added at 04:53 AM ---------- Previous post was at 04:17 AM ----------
I upgraded my uconnect from 2.600 to 2.700 and deleted the device pairing a couple of times and now I can at least play media again although I no longer have song data displaying which was there before at least before my radio would lock up.
I also tried changing the Bluetooth codec via developer settings to ACC. However, after changing, it reverts on its own. I read that the November security patch supposedly contains some BT fixes, fingers crossed!
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
fishsupreme said:
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
Click to expand...
Click to collapse
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
fishsupreme said:
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Click to expand...
Click to collapse
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Not just with vehicles
760hacker said:
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Click to expand...
Click to collapse
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
phonefreedom said:
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
Click to expand...
Click to collapse
This is similar to what I see, both with my new Pixel2 and also my previous OnePlus3 on my Mazda 3. Phone will pair, but after a few seconds (or sometimes minutes) disconnect. Usually it will try to reconnect, and then be fine until the next time I use my car. Both phones behave identically, so it seems to be more a problem with vehicle systems that some phones (none I've owned unfortunately!) are more forgiving of.
Anyone know of a fix for this? I'm using uconnect and same issue, however my maps navigation does play over Bluetooth. Sometimes it seems to disconnect or mute after songs change, and the metadata issue is there. Super annoying that we go backwards in technology. My HTC M9 does this stuff flawlessly.
So I did the developer preview thing and set it back to 1.3 which helps the metadata issue. However, the music still pauses every once in a while, mostly between songs. I have to click to my AM/FM radio and back to bluetooth to fix that.
Well, it's always the same circle. There's a new device with a brand new Android version. Of course buggy a.f. They fix it over the time. The device works perfect. And then... a new major upgrade, which is buggy again.
7.1.2 worked perfect on my Pixel. Then came 8.0.
Bluetooth was messed up again. Now i use the Pixel 2, which is a great phone. But still has the complete bandwidth of bugs that were present in 8.0 on the Pixel 1.
Nice to have monthly patches. But instead of fixing so called security issues, they should focus on functionality bug fixes instead. Who has had a major security issue with hs phone at all, yet??
Google is like: "Fix: Someone could attack your phone using a backdoor in your bluetooth driver."
WTF?!
I can't even use my bluetooth to listen to audio correctly! Fix that first!
Long story short:
Yes, I have the same issue with meta-data in my car audio (Pioneer AVH-X2800BT). Sometimes it works. Sometimes it doesn't.
Just got November security patch which is supposed to include Bluetooth fixes but hasn't changed anything.
Sent from my Pixel 2 using Tapatalk
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
scoliosis said:
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
Click to expand...
Click to collapse
AVRCP 1.3 wasn't available in stock 8.0 either -- I had to put the 8.1 Developer Preview on to unlock it.
What is your Uconnect firmware version?
> the metadata (song titles and track info) doesn't show on the screen in my car
Mine does unless I'm running Android Auto
If your car has an older head unit with Bluetooth compatibility, you may have seen that with Android O, some of the metadata won't show up when playing audio from the phone. I found a tweak in the Android developer options that fixes it:
http://www.androidpolice.com/2017/0...ight-developer-preview-2-adds-avrcp-selector/
On my Honda Accord 2014, I set it to AVRCP 1.4 or 1.5, and Bluetooth shows the artist/track/etc again. Pandora runs more reliably as well.
There's no way I can get the audio system in my 2017 Subaru Forester to show remaining time on individual playing audio tracks. I have tried the various different developer options settings and it doesn't seem to make any difference.
I can confirm that setting version to 1.4, do fix this issue for pioneer radios. (Tested on DEH-X8500DAB).
After changing this, I can now switch tracks over bluetooth in my Honda Fit. Thanks!
In my case, after upgrading to Android 8.1 (Xiaomi Mi 5 @ AOSPExtended.mod by DennySPB) track infos won't work.
It doesn't matter if I choose AVRCP 1.3, 1.4, 1.5 or 1.6. It's just "no time, no title" etc.
Any other suggestions to fix that - apart from downgrading to 7.0?
(post removed by author, as it was not directly applicable to thread)
In my case, this solution worked, but I only post it "as is", without any warranty, that it will work for you.
1. Unpair audio device.
2. Go to Applications > show systems apps
3. Find "Bluetooth" and "Bluetooth MIDI", clear data for both of them
4. Go to developer settings, change AVRCP to 1.5 or 1.6
5. Restart phone.
6. Pair audio again.
Hi, thanks for the information, just reporting that this didn't work for me.
Android V9
Peugeot 508 JBL 2013
Hi, last week I installed the OTA Android 8.0 update on my HTC U11.
Since this update the audio quality when streaming to my car's audio system or to my pioneer hi-fi system at home is a lot worse than on Android Nougat. Especially on tracks with a lot of high tunes. There's always a slight 'clink' noise. I don't know how to explain this in English..
Have you noticed this issue as well? Is there something I can do about it? Thanks
question are you using any sound mods?
6th_Hokage said:
question are you using any sound mods?
Click to expand...
Click to collapse
No, I don't use any sound mods.
joscht said:
No, I don't use any sound mods.
Click to expand...
Click to collapse
Same for me. Since this update, the quality of phone call when connected to Bluetooth to my car is really bad. No problem with music stream connected to the same car.
I tried managing the new bluetooth options in developper mode menu but it doesn't solve the problem.
The codec used is all the time SBC even is I change it to AAC or aptX or AptxHD.
Fredz said:
Same for me. Since this update, the quality of phone call when connected to Bluetooth to my car is really bad. No problem with music stream connected to the same car.
I tried managing the new bluetooth options in developper mode menu but it doesn't solve the problem.
The codec used is all the time SBC even is I change it to AAC or aptX or AptxHD.
Click to expand...
Click to collapse
I have the same issue, it seems it was fixed in 42 version for US market(at least for LDAC)
I have 2 issues with Bluetooth connections with the car. The first is that it picks up interference from the noise of the wheels and engine while driving, and the sound quality suffers and it sounds unclear, unless I mute the vehicle.
The second is that it has a lot of trouble connecting to the car at times. Or, more often, it would not connect the media through the car. Don't know what's up with that.
I know how you feel
I've got exact same problem like yours. Although I'm using HTC u11 plus. My new pair of Bluetooth headphones have the same not OK audio quality. You're right especially the high tunes. I'm desperate, trying to reset everything, but doesn't help. If you find the solution, please let me know. Thank you.
joscht said:
Hi, last week I installed the OTA Android 8.0 update on my HTC U11.
Since this update the audio quality when streaming to my car's audio system or to my pioneer hi-fi system at home is a lot worse than on Android Nougat. Especially on tracks with a lot of high tunes. There's always a slight 'clink' noise. I don't know how to explain this in English..
Have you noticed this issue as well? Is there something I can do about it? Thanks
Click to expand...
Click to collapse
Same issue here. I have the U11 as well and just updated to Oreo and I have the same issue as well. Music over BT was ok on Nougat but after the update, music sounds as if there is digital clipping. And it's there with both my headset and car audio system.
Got the same issue, hope they fix it soon. The only solution seems to do a RUU right now.
Btw. I am on a custom rom (LeeDroid), gonna go full stock and try again.
I would suggest looking in developer options and trying some of the different options for bluetooth in there!
Settings > about > software information > more > then tap the build number till it says you are a developer.
Then
Go to developer options and check under networking, there are some settings to toggle in there.
You may find something you are looking for! I personally haven't tried bt since the update so I don't know if it is a common issue. Good luck!
Thank you!
Thank you very much.
Playing around with the bluetooth options in the developer's menu solved this issue.
The audio quality through bluetooth is now pretty much the same as it was with the previous android os
joscht said:
Thank you very much.
Playing around with the bluetooth options in the developer's menu solved this issue.
The audio quality through bluetooth is now pretty much the same as it was with the previous android os
Click to expand...
Click to collapse
Share what settings you stuck with so it may help the other people with the same problem
Hey there!
Same problem for me since updating my U11 to Oreo - very poor bluetooth audio quality...
I tried using different bluetooth settings under the developer options but the thing is: no matter what I choose, it keeps switching back to the default values not affecting anything at all.
If it switch back to default SBC it means your headset/BT device doesn't support other codec.
Alpert3 said:
If it switch back to default SBC it means your headset/BT device doesn't support other codec.
Click to expand...
Click to collapse
That's not necessarily true. On 7.1 both Bluetooth devices which I use can support either AAC, SBC and aptX. My understanding is this issue occured because of the removal of AVRCP 1.3. I think Google added 1.3 back to Android 8.q because of this.
yournamehere484 said:
That's not necessarily true. On 7.1 both Bluetooth devices which I use can support either AAC, SBC and aptX. My understanding is this issue occured because of the removal of AVRCP 1.3. I think Google added 1.3 back to Android 8.q because of this.
Click to expand...
Click to collapse
Yours is not necessarily true either. I'm on 8.0 and I can still use aptX if I want but only if my BT device supports aptX.
Alpert3 said:
Yours is not necessarily true either. I'm on 8.0 and I can still use aptX if I want but only if my BT device supports aptX.
Click to expand...
Click to collapse
I'm not arguing that aptX and other codecs aren't working on 8.0. What I'm saying is that with certain devices, we are no longer seem to be able to use certain codecs that we could use prior. It's obviously device dependent, but to say their isn't a problem and blame it on the Bluetooth device is incorrect. Infact the same problem has occurred on non HTC devices when they've upgraded to 8.0 such as the OnePlus.
yournamehere484 said:
I'm not arguing that aptX and other codecs aren't working on 8.0. What I'm saying is that with certain devices, we are no longer seem to be able to use certain codecs that we could use prior. It's obviously device dependent, but to say their isn't a problem and blame it on the Bluetooth device is incorrect. Infact the same problem has occurred on non HTC devices when they've upgraded to 8.0 such as the OnePlus.
Click to expand...
Click to collapse
Fair enough, I didn't understand.
Does anyone know how to make the bluetooth options under developer options stick? I'm on stock unlocked Oreo, and they go back to defaults as soon as I change them. I've tried changing them whilst connected in the car, but no change. The only thing that could make a difference is that I'm running Pitch Black Substratum theme. Anyone else got them to stick?
In my Audi a3 2015 before oreo i can able to skip the track with entertainment commad and in the display i saw name of the track. After update i have lost all funtionality and the car see my device only like esternal suorce . Can i do something?
What kind of internal DAc the 7 PRO has?
In case of usage of an external USB DAC + USB Audio PRO, what should I use for BIT PERFECT option?
thegios said:
What kind of internal DAc the 7 PRO has?
In case of usage of an external USB DAC + USB Audio PRO, what should I use for BIT PERFECT option?
Click to expand...
Click to collapse
There's a menu option specifically for bit Perfect. Just toggle it on. On another note, from my understanding, the pixel 7 or actually any tensor device is limited with USB output to 96. There's a a module that removes that limit in case you're using audio files that are higher than 96
Go to the menu, settings, USB audio and you'll see this
GitHub - Magisk-Modules-Alt-Repo/usb-samplerate-unlocker: USB (HAL) Audio Class drivers on Android have a limiter of sample rates at 96kHz. This magisk module unlocks the limiter.
USB (HAL) Audio Class drivers on Android have a limiter of sample rates at 96kHz. This magisk module unlocks the limiter. - GitHub - Magisk-Modules-Alt-Repo/usb-samplerate-unlocker: USB (HAL) Audi...
github.com
Yeedatoy said:
There's a menu option specifically for bit Perfect. Just toggle it on. On another note, from my understanding, the pixel 7 or actually any tensor device is limited with USB output to 96. There's a a module that removes that limit in case you're using audio files that are higher than 96
Click to expand...
Click to collapse
Yes but UAPP bypasses the Android limitations when using an external DAC.
thegios said:
Yes but UAPP bypasses the Android limitations when using an external DAC.
Click to expand...
Click to collapse
I thought that was what you asked about? I know you initially asked what kind of DAC the pixel has, but didn't you ask about an external as well? The DAC in the pixel 7 is nothing special. It's just similar to the other ones that are capable of pro audio output. Because it doesn't have its own amplifier like LG devices or some of the ROG Devices you'll be better off with an external. I have noticed on my pixel, however, that even when not using headphones, it outputs at 44.1 the majority of the time. If you click on the internal high res audio menu, there's also a bit perfect setting in there as well.
Another option would be to try neutron and make sure you have it set to where it is on, use the sample rate of the track.... Or something similar. I can't remember exactly how it's written. There's a bit perfect option there as well. What I'm not sure about and what I can't really find anywhere is how this, or if this affects the pixels spatial audio. Honestly, I think it's too new for there to be enough information about it
Yeedatoy said:
I thought that was what you asked about? I know you initially asked what kind of DAC the pixel has, but didn't you ask about an external as well? The DAC in the pixel 7 is nothing special. It's just similar to the other ones that are capable of pro audio output. Because it doesn't have its own amplifier like LG devices or some of the ROG Devices you'll be better off with an external. I have noticed on my pixel, however, that even when not using headphones, it outputs at 44.1 the majority of the time. If you click on the internal high res audio menu, there's also a bit perfect setting in there as well.
Click to expand...
Click to collapse
Thanks
Yes I asked about internal DAC just out of curiosity, after all an internal DAC is used only in two occasions: if you plug headphone via 3.5mm jack (not the case here) or if you use phone's speakers (and in this case, who cares). Sometimes for convenience I use Bluetooth buds, but also in this case I don't really care being all compressed anyway... Most of the time I listen to music with headphones plugged via an external HiRes DAC.
Reason why I believe internal DACs are overrated
Now, since I know that Android audio driver has limitations (capped at 96 and resamples 44 to 48, I've read), since most players use Android driver including Qobuz app, I need to use UAPP (as also suggested on Qobuz website).
There are three settings I am not sure about:
Settings > Internal Audio Driver (original android, hires direct)
Settings > Audio Hires > Bit Perfect (Off, On, When possible)
Settings > Audio USB > Bit Perfect (Off, On, When possible)
I have chosen, in order: hired direct, on, on
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Thought my post might be more relevant here. Currently post the June update, I have stopped using UAPP till the issue gets fixed. I am using the sample rate unlocker module which lets me stream 192kHz files from Qobuz through my external DAC Chord Mojo and I can confirm through the lights on it, but it's still using the Android pathway rather than the direct pathway that UAPP uses.
WhoIsJohnGalt1979 said:
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Thought my post might be more relevant here. Currently post the June update, I have stopped using UAPP till the issue gets fixed. I am using the sample rate unlocker module which lets me stream 192kHz files from Qobuz through my external DAC Chord Mojo and I can confirm through the lights on it, but it's still using the Android pathway rather than the direct pathway that UAPP uses.
Click to expand...
Click to collapse
I am not going to root my pixel...
Can you quickly summarize your post pls I do not have any problem playing Qobuz with UAPP with an external DAC
Music stops playing 15 seconds after screen turns off through UAPP. When a DAC is connected to a pixel phone, you get a prompt depending on whether you are using a 3.5 mm adapter or a USB C DAC. If you select No the issue doesn't occur, but if you select Yes which you should music stops playing after the screen turns off.
Kind of straying away from the original question but still on topic, Android 14 is implementing bit perfect audio natively on pixels.
WhoIsJohnGalt1979 said:
Music stops playing 15 seconds after screen turns off through UAPP. When a DAC is connected to a pixel phone, you get a prompt depending on whether you are using a 3.5 mm adapter or a USB C DAC. If you select No the issue doesn't occur, but if you select Yes which you should music stops playing after the screen turns off.
Click to expand...
Click to collapse
Did that just happen on a recent update? Because I didn't experience this issue when using my external DAC about a month ago. I know they roll out frequent updates. Also, what Android version are you on?
Looks like they may have fixed it in the recent update
Yeedatoy said:
Looks like they may have fixed it in the recent update
Click to expand...
Click to collapse
Yes they did. They say it's a workaround lets see what happens when Google releases July update if the workaround holds. As I said since February this year since I started tracking this issue it's a cat and mouse game.
I've never had a problem with UAPP but I'm really happy that A14 will implement but perfect: I prefer Qobuz app over UAPP.