Status Update
Comments
ia...@gmail.com <ia...@gmail.com> #2
<item type="id" name="metricsStateHolder"/>
<item type="id" name="metricsDelegator"/>
These are assigned unique values at build time. As long as they are only ever used to assign objects of the correct type with those tags, there shouldn't be the kind of classCast exception seen above, and the assignments look correct, eg:
metricsStateHolder = Holder()
rootView.setTag(R.id.metricsStateHolder, metricsStateHolder)
and
delegator = DelegatingFrameMetricsListener(delegates)
decorView.setTag(R.id.metricsDelegator, delegator)
Logging shows ids are indeed unique and off by one, eg:
2131230959, 2131230958
Still investigating
sc...@gmail.com <sc...@gmail.com> #3
We synchronize access to some structures in JankStats already for other potential race conditions; we should be able to similarly protect access to the tags array for use between threads.
ka...@gmail.com <ka...@gmail.com> #4
There are various other calls to getTag/setTag that have been modified to ensure they are called from the UI thread, so things should be more solid (in an upcoming fix).
ni...@gmail.com <ni...@gmail.com> #5
According to datadog a user clicked a deeplink that navigates into our app.
java.lang.ClassCastException: com.xxx.ui.main.MainActivity cannot be cast to androidx.metrics.performance.PerformanceMetricsState$Holder
at androidx.metrics.performance.PerformanceMetricsState$Companion.getHolderForHierarchy(Unknown Source:27)
at androidx.metrics.performance.a.onFrameMetricsAvailable(Unknown Source:162)
at android.view.FrameMetricsObserver.onFrameMetricsAvailable(FrameMetricsObserver.java:59)
at android.graphics.HardwareRendererObserver.lambda$notifyDataAvailable$0$HardwareRendererObserver(HardwareRendererObserver.java:93)
at android.graphics.HardwareRendererObserver$$ExternalSyntheticLambda0.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:980)
at android.os.Handler.dispatchMessage(Handler.java:104)
at android.os.Looper.loopOnce(Looper.java:238)
at android.os.Looper.loop(Looper.java:357)
at android.os.HandlerThread.run(HandlerThread.java:85)
le...@gmail.com <le...@gmail.com> #6
Is there any update on this issue? I can see pending code changes linked to this bug, but they are not yet merged (seems like CR is hanging without any action for a few months already).
an...@gmail.com <an...@gmail.com> #7
Project: platform/frameworks/support
Branch: androidx-main
Author: Chet Haase <
Link:
Make use of View tags thread-safe, and simplify delegate scheduling
Expand for full commit details
Make use of View tags thread-safe, and simplify delegate scheduling
We stash a single library-wide instance of our pre draw listener on
the DecorView on lower API levels. This could previously happen from a
couple of different threads, and View tags are not thread safe, which
can cause potential race condition errors if the underlying tag
storage is accessed in parallel from different threads.
This fix posts any changes to both the onPreDrawListener and the tags
to happen from the main thread to make them safe.
This also removes unnecessary logic from the onPreDraw loop itself,
since delegates cannot be scheduled for addition or removal during the
loop due to the synchronized block.
This fix also simplifies logic of singleFrameState removal (it now
happens while processing frames directly, on the following frame),
which gets rid of the need to synchronously get and use the state
holder from the FrameMetrics thread.
Bug: 311218678
Test: Manual testing to verify correct threading behavior, JankStatsTests passes
Relnote: Fix crashes `DelegatingFrameMetricsListener cannot be cast...`
Change-Id: Id891c0cfdd7f45ef9e3b068644a113f39c8fc383
Files:
- M
metrics/metrics-performance/src/androidTest/java/androidx/metrics/performance/test/JankStatsTest.kt
- M
metrics/metrics-performance/src/main/java/androidx/metrics/performance/JankStats.kt
- M
metrics/metrics-performance/src/main/java/androidx/metrics/performance/JankStatsApi16Impl.kt
- M
metrics/metrics-performance/src/main/java/androidx/metrics/performance/JankStatsApi24Impl.kt
- M
metrics/metrics-performance/src/main/java/androidx/metrics/performance/PerformanceMetricsState.kt
Hash: 68264e9d7d70b0af375d6cf4c27a3407657a5b80
Date: Mon Jan 08 17:23:46 2024
an...@gmail.com <an...@gmail.com> #8
I still see issues in the API24+ impl, reopening.
ch...@gmail.com <ch...@gmail.com> #9
Project: platform/frameworks/support
Branch: androidx-main
Author: Chris Craik <
Link:
Improve tag/listener update safety on API 24+
Expand for full commit details
Improve tag/listener update safety on API 24+
Improve JankStats API 24 impl to reduce thread hops and simplify
delegate iteration/adding/removal. This brings the API 24 impl to be
much closer to the API 16 implementation.
Also ensures that delegates and window frame metrics available
listeners are consistently set on main thread.
Test: JankStatsTest
Fixes: 311218678
Change-Id: I2ab7c892ae114708f3cd8e80f180ab73e32b9d11
Files:
- M
metrics/metrics-performance/src/main/java/androidx/metrics/performance/JankStatsApi24Impl.kt
Hash: f185f92ddcc005dfaa62ab4ed2816faabddc2288
Date: Wed Feb 26 15:03:31 2025
sc...@gmail.com <sc...@gmail.com> #10
Any ETA on the new release?
an...@gmail.com <an...@gmail.com> #11
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.metrics:metrics-performance:1.0.0-beta02
di...@gmail.com <di...@gmail.com> #12
kr...@gmail.com <kr...@gmail.com> #13
This fix was released yesterday with androidx.metrics:metrics-performance:1.0.0-beta02
, see
Please try it out and let us know if it doesn't address the problem.
tr...@gmail.com <tr...@gmail.com> #14
ro...@gmail.com <ro...@gmail.com> #15
ro...@gmail.com <ro...@gmail.com> #16
Thank you for reaching back out to us.
Our Tech Team has assessed the matter, and the issue is not with TIDAL it's within the Pixel system. Because of this, we advise connecting with the Google Support Team for further assistance.
ch...@gmail.com <ch...@gmail.com> #17
Google, please do something!!
cr...@gmail.com <cr...@gmail.com> #18
ga...@gmail.com <ga...@gmail.com> #19
na...@gmail.com <na...@gmail.com> #20
an...@gmail.com <an...@gmail.com> #21
Astell & Kern PEE51 DAC. Skipping sound and screeching noise.
sl...@gmail.com <sl...@gmail.com> #22
wf...@gmail.com <wf...@gmail.com> #23
Pixel 6 Pro fully patched.
Garbled audio and then a disconnect and no further sound.
I suspect listening via Android Auto in my F150 may have a similar or the same issue as after listening for some random period of time the same behavior occurs
jo...@gmail.com <jo...@gmail.com> #24
je...@gmail.com <je...@gmail.com> #25
ke...@gmail.com <ke...@gmail.com> #26
ru...@gmail.com <ru...@gmail.com> #27
kh...@gmail.com <kh...@gmail.com> #28
Please, Can you fixe it.
mr...@gmail.com <mr...@gmail.com> #29
It may seem minor to you but I'm concidering returning the phone because of this, its bad enough a dongle wasn't included and I can't claim the buds for almost a month after purchase. It now appears I can't even enjoy my music on the phone anyway.
in...@gmail.com <in...@gmail.com> #30
la...@gmail.com <la...@gmail.com> #31
cr...@gmail.com <cr...@gmail.com> #32
Google, please make this an urgent task to fix external DAC support.
be...@gmail.com <be...@gmail.com> #33
ch...@gmail.com <ch...@gmail.com> #34
Google. Please fix as this should be an high end android device with high end USB device options.
I've told three people so far who were looking to get phones in 2021/2022 to avoid the pixel 6 and pixel 6 pro until fixed.
ja...@gmail.com <ja...@gmail.com> #35
I also will have to tell people to avoid the Pixel phones if you want good audio playback.
ja...@gmail.com <ja...@gmail.com> #36
apps using the USB host API to access USB audio interfaces fail to play.
It's not specific to Android 12 since the Pixel 3 and 4's work with Android 12.
ja...@gmail.com <ja...@gmail.com> #37
jf...@gmail.com <jf...@gmail.com> #38
zi...@gmail.com <zi...@gmail.com> #39
sc...@gmail.com <sc...@gmail.com> #40
ja...@gmail.com <ja...@gmail.com> #41
At the very least can you confirm whether you're going to fix this or not? If not, I need to get rid of your product and replace.
sd...@gmail.com <sd...@gmail.com> #42
bd...@gmail.com <bd...@gmail.com> #43
sa...@gmail.com <sa...@gmail.com> #44
en...@gmail.com <en...@gmail.com> #45
ar...@gmail.com <ar...@gmail.com> #46
cl...@gmail.com <cl...@gmail.com> #47
en...@gmail.com <en...@gmail.com> #48
ja...@gmail.com <ja...@gmail.com> #49
Re one comment above , there's another similar complaint thread and one person claimed a DM from Google that they were on it. I'm skeptical.
ch...@gmail.com <ch...@gmail.com> #51
ar...@gmail.com <ar...@gmail.com> #52
There's no reason we shouldn't be able to use our own highres DACs.
ja...@gmail.com <ja...@gmail.com> #53
ba...@gmail.com <ba...@gmail.com> #54
Please fix this issue with the highest urgency.
Kindest Regards.
wa...@gmail.com <wa...@gmail.com> #55
R42 changelog mentions potential DAC fix.
sc...@gmail.com <sc...@gmail.com> #56
C'mon Google if a 3rd party dev can fix it you can too.
The fact this this bug remains unacknowledged much less unfixed for 3+months is terrifically disheartening, Google DO BETTER
ch...@gmail.com <ch...@gmail.com> #57
What third party Dev fixed it. Is there a custom kernel somewhere that fixes it?
Thanks
ch...@gmail.com <ch...@gmail.com> #59
ni...@gmail.com <ni...@gmail.com> #60
Thanks for the update. Do custom kernels allow direct access in apps like UAPP and Tidal? (e.g., MQA playback up to 96 kHz)? Any recommendations besides the one above?
ja...@gmail.com <ja...@gmail.com> #61
When a DAC is plugged in to the Pixel 6 and software tries to access it directly ( meaning bypassing internal DAC ) only high volume static is heard or nothing at all.
Seems Google is unwilling to address this issue in a timely fashion or not at all.
Extremely disappointed
ch...@gmail.com <ch...@gmail.com> #62
an...@gmail.com <an...@gmail.com> #63
And to be honest I'm not ready to go to custom kernel.
I want to use stock pixel 6 pro
an...@gmail.com <an...@gmail.com> #64
je...@gmail.com <je...@gmail.com> #65
Maybe it will take some prominent Android YouTuber to embarrass them enough
to work on fixing the issue.
Jerald McConnell
On Sat, Jan 15, 2022 at 5:30 AM <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #66
Interestingly if I don't click the Tidal USB prompt it plays music but no high-res outputs. Might be linked to giving apps control over the USB connection.
up...@gmail.com <up...@gmail.com> #67
jo...@gmail.com <jo...@gmail.com> #68
Ik have the same issue, USB audio player and Tidal sees the external dac. Wen I push the play button it gives An error.
Groeten,
Jos Lohuis
18 jan. 2022 06:37:05 buganizer-system@google.com:
dr...@gmail.com <dr...@gmail.com> #69
si...@gmail.com <si...@gmail.com> #70
jo...@gmail.com <jo...@gmail.com> #71
Met vriendelijke groet,
Jos Lohuis
On 18 Jan 2022, 19:42 +0100, buganizer-system@google.com, wrote:
ni...@gmail.com <ni...@gmail.com> #72
Found in can be updated to SQ1D.220105.007 and subsequent builds until this is fixed
ja...@gmail.com <ja...@gmail.com> #73
When a DAC is accessed directly by any program running on a Pixel 6 then either static or no sound is heard.
When a DAC is used in bypass mode, meaning the DAC in the Pixel 6 is used then sound is heard from the external DAC ( which is just passing it to the attached headphones ).
With build SQ1D.220105.007 there is now pops and hisses heard in bypass mode, thus audio with an external DAC is now worse then the November 2021 build.
Please understand that the Pixel 6 has an an internal DAC ( that is how you make phone calls and hear sounds from the speakers ).
Also please understand that this issue is ONLY with the Pixel 6 and Pixel 6 Pro. External DACs work on all other Pixel phones as well as other phones.
ni...@gmail.com <ni...@gmail.com> #75
Can a Googler change the status of this bug to "accepted?"
sc...@gmail.com <sc...@gmail.com> #76
If they've fixed it they need to include it in the February update not July!
jp...@gmail.com <jp...@gmail.com> #77
te...@gmail.com <te...@gmail.com> #78
da...@gmail.com <da...@gmail.com> #79
Not cool.
st...@vanbeerschoten.net <st...@vanbeerschoten.net> #80
an...@gmail.com <an...@gmail.com> #81
dr...@gmail.com <dr...@gmail.com> #82
already on the Pixel 7/Pixel 7 Pro.
I have always been loyal Google/Android user, so this is really
disappointing.
On Sun, Mar 20, 2022, 13:32 <buganizer-system@google.com> wrote:
ro...@gmail.com <ro...@gmail.com> #83
st...@vanbeerschoten.net <st...@vanbeerschoten.net> #84
he...@gmail.com <he...@gmail.com> #85
he...@gmail.com <he...@gmail.com> #86
ga...@gmail.com <ga...@gmail.com> #87
cg...@gmail.com <cg...@gmail.com> #88
I've waited since October and also replaced my phone once, and still cannot conf consistently use a word headset. Half the time it doesn't work.
no...@gmail.com <no...@gmail.com> #89
jo...@gmail.com <jo...@gmail.com> #90
sa...@gmail.com <sa...@gmail.com> #91
ja...@gmail.com <ja...@gmail.com> #92
).
Can anyone else PLEASE verify my results with your config?
That is can your Pixel 6 or Pixel 6 Pro play via USB-c to dongle ( use a USB rendering app like HiByMusic ) and now instead of getting static you hear the song chosen?
Please make sure that the app is accessing the external DAC via USB-c you need to see a Android permission screen to know that Android is sending data to the USB-c port and NOT analog sound single ( which is how a $8 Amazon usb-c dongle works )
Thank you for all your comments this issue MAYBE OVER AT LAST!!!!!
da...@gmail.com <da...@gmail.com> #93
I understand June is the potential fix date for this continuing issue.
dr...@gmail.com <dr...@gmail.com> #94
Appreciate a general announcement to the media on progress for this issue.
On Sat, May 7, 2022, 11:54 <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #95
ni...@gmail.com <ni...@gmail.com> #96
If you uninstall then reinstall Tidal (or clear app data then log in again), you will get the DAC access prompt for the first day or so, then it will stop prompting. This is on the latest beta or using the Kirisakura kernel on stock
jo...@gmail.com <jo...@gmail.com> #97
ma...@gmail.com <ma...@gmail.com> #98
ce...@gmail.com <ce...@gmail.com> #99
th...@gmail.com <th...@gmail.com> #100
yu...@google.com <yu...@google.com> #101
Direct USB access is now available in June 2022 Feature Drop for Pixel 6 and 6 Pro.
an...@gmail.com <an...@gmail.com> #102
From what I can see, for now, pixel 6 pro process MQA track and send the processed signal to the usb DAC (THX Onyx). Instead it is supposed for the external DAC to perform signal processing, not the crappy pixel built-in DAC.
So it took 6 months just for another f**k up by Google.
Good work.
Keep that way
mi...@gmail.com <mi...@gmail.com> #103
In that case no point of having KA3 as high quality DAC? It is only working as headphones amplifier?
I use Spotify premium with highest quality which is not high-resolution anyway so it may not matter much ...
yu...@google.com <yu...@google.com> #104
The built-in DAC in Pixel 6 / 6 Pro is only for driving the built-in speaker. So, the external DAC will process the original music data as long as the app you use intends to do so.
ac...@gmail.com <ac...@gmail.com> #105
I'm absolutely gutted! Guess it's time to buy a new phone.
ga...@googlemail.com <ga...@googlemail.com> #106
However, the Tidal app still isn't recognising the external DAC. My suspicion is that this is on the app side rather than the OS side since UAPP is working. I think that the Tidal developers just disabled the external DAC feature on the version of the app that's available on the Play store for Pixel 6/6 pro devices. Either that or the method that the app uses to detect the external DAC isn't compatible with the way that the Pixel 6/6 pro exposes the functionality to the app. I'm hopeful that an update to the Tidal app will enable this functionality but in the meantime I'm fine with using UAPP.
If anyone has had different results with the Tidal app, please comment with how you fixed the issue.
ni...@gmail.com <ni...@gmail.com> #107
Can confirm the same with Tidal while the fix was in beta. Not sure how to communicate anything with Tidal without going through level 1 support
an...@gmail.com <an...@gmail.com> #108
ni...@gmail.com <ni...@gmail.com> #109
In past experience, reinstalling works initially then the direct access prompts stop in a day or two of reconnects
ac...@gmail.com <ac...@gmail.com> #110
This has always been the case, before and after June Pixel update.
It seems to affect all playback bitrates, not just Hi-Fi.
I have tried reinstalling Tidal and clearing the cache. This does not help.
ka...@gmail.com <ka...@gmail.com> #111
be...@gmail.com <be...@gmail.com> #112
ba...@gmail.com <ba...@gmail.com> #113
Pixel 6 Pro using Audioquest Dragonfly Black and USB Audio Player Pro
V6.0.7.4 which is now available on the Google Play Store.
On Tue, 7 Jun 2022 at 11:23, <buganizer-system@google.com> wrote:
in...@gmail.com <in...@gmail.com> #114
jk...@gmail.com <jk...@gmail.com> #115
jk...@gmail.com <jk...@gmail.com> #116
I get purple MQA on my Cobalt.
jk...@gmail.com <jk...@gmail.com> #117
jk...@gmail.com <jk...@gmail.com> #118
ce...@gmail.com <ce...@gmail.com> #119
After clearing the Tidal app cache and data, and a phone restart, Tidal is still freezing after I give it access to my DAC. It just hangs at the splash screen even though the phone isn't frozen. Anyone else having this issue?
DAC works great on USBAPP, despite it not working with Tidal.
ch...@gmail.com <ch...@gmail.com> #120
Also works (for now) on Tidal but I had to uninstall and reinstall the app.
Note as some others have noted until I uninstalled and reinstalled Tidal I only got the red light on Ztella (which means >= 46kHz but not MQA)
Oh, and remember to re-select MQA in the streaming options if doing over cellular as default is "normal"
UAPP worked without uninstall/reinstall
Chris
ro...@gmail.com <ro...@gmail.com> #121
ipad mini 5th gen with these dacs - no issues. all good with MQA. ipadOS 15.5
pixel 3xl with helm bolt and THX onyx - no issues. all good with MQA. android 12
ni...@gmail.com <ni...@gmail.com> #122
Same here with Tidal. Tidal support pins it on Google support and vice versa
nb...@gmail.com <nb...@gmail.com> #123
I tried it with two different audio interfaces including a Zoom U-44. Playback from apps like Spotify works ok.
ch...@gmail.com <ch...@gmail.com> #124
Chris
ch...@gmail.com <ch...@gmail.com> #125
I just returned and it had lost mqa, but when it happens you don't need to uninstall and reinstall... Just wiping settings data for Tidal is enough.
I've tested force close since she I kept mqa even without wiping. Also freezing UAPP seems to help.
This suggests to me the issues are with the Tidal app now, not the phone.b or possibly a conflict of both Tidal and UAPP try to grab the device, with tidal losing out
ni...@gmail.com <ni...@gmail.com> #126
Can confirm issue occurs when UAPP is not installed. So far, Tidal has not owned the issue
ch...@gmail.com <ch...@gmail.com> #127
th...@gmail.com <th...@gmail.com> #128
ch...@gmail.com <ch...@gmail.com> #129
ni...@gmail.com <ni...@gmail.com> #130
I think you have a different issue. This thread refers to USB DACs. There was another issue where LDAC would stutter at 660 kbps+, but in my experience, that has been improved significantly with the same update (I have the same earbuds)
ma...@gmail.com <ma...@gmail.com> #131
ch...@gmail.com <ch...@gmail.com> #132
ke...@gmail.com <ke...@gmail.com> #133
Google Pixel 6 Pro
Gustard X26 DAC USB in
Tried with UAPP installed and not
Tidal freezes after asking if it can use the DAC, tried reinstalling/clearing Tidal a few times. Local files through UAPP worked fine all up to 192KHz, high bit rates etc. All Tidal streams through UAPP at 44KHz. Native Tidal app freezes/hangs etc
Honestly, I am a huge Google fan with at least 30 automation and Nest devices around my home, so I moved from Samsung to Pixel flagship earlier this year - worst decision ever. They really produced a bad phone, it is garbage and will be going back to Samsung (or ANYTHING ELSE) after this latest discovery that it cannot even handle proper USB audio output capabilities. The phone overall is a joke, I hope Google manages to repair the damage and release a proper phone 1 day
ch...@gmail.com <ch...@gmail.com> #134
Which firmware are you on using?
I have Pixel Pro 6 including the June security patch firmware SQA.220605.009.B1 that has the USB DAC fix - I no longer have the issues as described above.
Have you reported issue from within the phone?
Chris
ka...@gmail.com <ka...@gmail.com> #135
Just in case anyone wants to know, I can confirm the Pixel 7 pro plays nicely with my Zen, Fiio, and Audioquest DACs, with no issue (tested with Apple Music, Tidal, Amazon Music HD, and USB Audio Player).
Description
Upon connecting to external hifi dacs via USB, apps such as USB Audio pro, Poweramp, Fiio Music, etc, crashes/freezes, with no sound coming from headphones. My other phones have worked fine.