search

Pittvandewitt / Wavelet

A quick rundown on each feature and its settings
https://pittvandewitt.github.io/Wavelet/
664 stars 35 forks source link

Legacy mode on Android 14 on Pixel 6 does not work for Bluetooth [edit: specifically for aptx. SBC seems to work fine]] #273

Closed Mautomate closed 4 months ago

Mautomate commented 10 months ago

When enabled, legacy mode does not show up when using Bluetooth device. It does show up when using on device audio though (phone speakers), but only for on device audio. The regular version still works with Bluetooth but only for the designated apps. The reason I was using legacy mode was for YouTube and other such apps. Attached are pictures showing differences Screenshot_20240110-162401~2 Screenshot_20240110-162406~2 Screenshot_20240110-162537~2

dknikolov commented 8 months ago

I have the same issue on the Pixel Fold with the B&W P8. Disabling HD audio: Qualcomm aptX" HD audio in the headphones Bluetooth settings worked for me. I am stuck using SBC if I want to use Wavelet.

Mautomate commented 7 months ago

Holy crap thank you, yeah that fixed the issue. I'm using a pixel 6 (I'm going to edit that in the description because it seems like if you're having the issue on a pixel phone as well then maybe it's related) I'm not sure why having aptX enabled makes it not function. Hopefully a future update will fix this issue, especially because of the latency is worse without using aptX

Mautomate commented 7 months ago

Sorry I didn't mean to close the issue

jonasfreudig commented 4 months ago

I'm having the same issue on my Pixel 7 Pro with Sony Linkbuds S trying to play via TIDAL. With Spotify, everything works fine (w/o legacy mode), but TIDAL does not work even in legacy mode. When I deactivate HD audio (LDAC in this case) it works.

It would be nice to be able to use it with HD audio on!

I tried it with TIDAL and my Bose QuietComfort 35 headphones and there it works even with HD audio on - but they use AAC, not LDAC or aptX.

Pittvandewitt commented 4 months ago

Seems to be a known platform issue: https://issuetracker.google.com/issues/261579107

When no effects could be instantiated, the blank screen shows up like you are experiencing. It's not something I can fix unfortunately.