Database Develop

Viper4android/Audio Processing with AA

Is there any way to have viper process audio being routed to the navi when using Auto? Or does the file get processed by the head unit? Might be a silly question, but I've been searching the google for days and can't find any information about how AA processes audio. Nexus 6 with latest Chroma build, 7100nex

Isn't the whole purpose of doing AA is to have the headunit process the audio? I'm not certain too but given that you need to have a usb connection, I'd imagine thats how it works. It better not be via the bluetooth...

arrico21 said:
Is there any way to have viper process audio being routed to the navi when using Auto? Or does the file get processed by the head unit? Might be a silly question, but I've been searching the google for days and can't find any information about how AA processes audio. Nexus 6 with latest Chroma build, 7100nex
Click to expand...
Click to collapse
don't know for navi, but i know it processes music, in the bluetooth section of Vipr.

Does this apps can be use on my Xiaomi redmi Note 3G?
Sent from my HM NOTE 1W using TapaTalk

I was wondering this as well. In my current setup, simple Bluetooth to car stereo, v4a works great! But my next car will have AA, which I think uses USB as well as Bluetooth in some cases, I believe. Can anyone with v4a and AA confirm being able to use v4a via AA?

It does not work with AA.

When using AA the head unit will process the music, so it's similar to playing off of a flash drive. While I love V4A I prefer it this way because there is no gain limit to overcome like with Bluetooth or Aux.

menissalt said:
When using AA the head unit will process the music, so it's similar to playing off of a flash drive. While I love V4A I prefer it this way because there is no gain limit to overcome like with Bluetooth or Aux.
Click to expand...
Click to collapse
Is this still the case? Audio volume is low with with AA and i have to increase head units volume when listening music with AA. I hoped V4A would fix this.

Bluetooth Bugs - OOS Open Beta 8

Starting this thread to see how prevalent this bug is, and if it's something fixable or just a bug that will need to be fixed in the next update. It appears to be affective at least a few other users as well (https://www.reddit.com/r/oneplus/comments/5g89wa/oos_beta_8_bluetooth_issue/)
Much like in the linked thread, I have been having issues with BT connectivity with my car, such that BT audio plays but voice search feedback on android auto doesn't play. also noticed that BT subsettings are all unchecked for all paired devices (phone audio/media audio) despite that both work. Anyone else seeing other bluetooth issues on this build?

Yeah, I can no longer even pair my phone to my car (Mitsubishi). It just won't work no matter what I do.
It worked just fine before.

Tested mine tonight, device paired and everything was working well.

Had no problems using various bluetooth devices like speaker, gamepad and BMW car unit
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Only issue I am having is with the mi band 2. Notoriously awkward when it comes to BT at the best of times.
Wife's Audi took two attempts my MB worked without issue.
Bose stuff working perfectly.
Sent from my ONEPLUS A3003 using Tapatalk

Got the same issue, pairing well but reading sms function doesn't work anymore even on stable version!

Having problems with vivoactive hr and the Garmin Connect app. Not getting notifications, and have to toggle Bluetooth off and on to sync.

Sometimes having trouble connecting via BT to my JBL sound bar. One time it doesn't connect at all, sometimes my phone connects, but no sound. Now testing again, all works fine. Using Deezer as I type.

Allow 720p/1080p video output developer options won't turn on/turns itself off?

Hi,
I've seen some fairly old information about enabling the "allow 720p video output" option in developer options, resulting in better quality image on certain head units. I wanted to try this out for my Ford Fiesta, but the setting seems to disable itself as soon as I leave the Android Auto app, and even if I enable it and plug straight into the car it seems to have no effect (not sure if head unit doesn't support it, or the app, or both).
I'm using a Nexus 6P. Tried reinstalling the app and it made no difference. Android Auto: 3.1.581054-release
Anyone else had this issue?
I saw this Android Police post https://www.androidpolice.com/2018/...ow-message-previews-hd-graphics-apk-teardown/ - it looks like Google are setting up to make HD projection functionality official, but for the time being I'd really like to play with these options.
Sent from my Nexus 6P using Tapatalk

Shure your car support 720p resolution?

henno88 said:
Shure your car support 720p resolution?
Click to expand...
Click to collapse
I'm not sure no, but the app seems to reset the setting all by itself regardless of whether or not I connect it to the car - so like I said, I don't know if it's the app or the head unit.
Sent from my Nexus 6P using Tapatalk

Maybe your car doesn't support this.
This causes AA to reset this option.
What car?
AA wireless working on your Nexus?
Any wireless settings in AA app ?

henno88 said:
Maybe your car doesn't support this.
This causes AA to reset this option.
What car?
AA wireless working on your Nexus?
Any wireless settings in AA app ?
Click to expand...
Click to collapse
Maybe, but that doesn't really make sense since as I mentioned, it being reset is completely independent of whether or not I connect it to my car (happens as soon as I close the app and open it again) and for all the app knows I could easily be connecting it to a different car next which does support it.
It's a Ford Fiesta Mk8 (2017 onwards). The car doesn't support wireless AA. I don't see any mention of it in the app - I think I read that it only launched in the US? I'm in the UK.
Sent from my Nexus 6P using Tapatalk

Have the same "bug".
I try it with my Galaxy Note 8 (Stock) and Note 3 (Custom ROM). I install crankshaft on my Raspberry Pi and activate 720p and 1080p.
If i activate the suppord for 720 and 1080 it works one time. After i close the AA-App its disabled.
If i plug my phone on again, i see a error, that my phone or "car" is not supported.
The option in Open Auto / CrankShaft is still activated.

I read somewhere that this issue should be fixed in next release of Android Auto.

tomechio said:
I read somewhere that this issue should be fixed in next release of Android Auto.
Click to expand...
Click to collapse
Just installed 3.2.581534-release and it looks like the issue has been resolved. 720p and 1080p output seem to stay on after killing and relaunching the app. I'll test it in my car tonight but without the car, it works
Enabling the option really makes a big difference in my case. I drive a Skoda Superb 2018 and Waze looks totally pixelated without this option on. I was going to post this question in the forum because I also encountered the issue of disabling the 720p output when closing the app but I'm glad it appears to be fixed now.

ljo13 said:
Just installed 3.2.581534-release and it looks like the issue has been resolved. 720p and 1080p output seem to stay on after killing and relaunching the app. I'll test it in my car tonight but without the car, it works
Enabling the option really makes a big difference in my case. I drive a Skoda Superb 2018 and Waze looks totally pixelated without this option on. I was going to post this question in the forum because I also encountered the issue of disabling the 720p output when closing the app but I'm glad it appears to be fixed now.
Click to expand...
Click to collapse
Yep it's fixed for me as of an update a couple of weeks ago as the option is sticking, but sadly it looks like my car doesn't support it.
Sent from my Nexus 6P using Tapatalk

Apt-X Support?

So, I tried choosing "Apt-X" from within the developer settings - but it doesn't stick. I know my headphones support it, and I looked up the SD660 - it has support for it as well. So, is there a way to enable Apt-X on the A2?

When you say "stick" u mean u can't select it? I can select either of the AptX options and they stay selected. But I'm not closing settings and shutting off the phone to check if it's still "sticking".
If you can't select them, it may be some other BT setting you've changed that's preventing those from being selected? All of my other BT selections are of the 'Auto' type.

AsItLies said:
[...] But I'm not closing settings and shutting off the phone to check if it's still "sticking". [...]
Click to expand...
Click to collapse
Thats exactly right - I can select them, but back out of settings and then check again and its back to the default (auto). I also tried changing the setting while my headphones were connected - in that case, it doesn't even change temporarily and will stay on AAC.

Same here it always goes back to default setting.. can't even use srgb mode

I think the device build is missing the aptx libraries. Currently aptx is not supported. Maybe they will integrate this in any coming release, but I wouldn't count on that.

Weird enough the device is able to use AAC apple Bluetooth driver.
Sent from my Mi A2 using Tapatalk

soulicro said:
Thats exactly right - I can select them, but back out of settings and then check again and its back to the default (auto). I also tried changing the setting while my headphones were connected - in that case, it doesn't even change temporarily and will stay on AAC.
Click to expand...
Click to collapse
After further reflection;
Remembered there are other USB settings that don't persist also. Change the USB connection type (say from Midi to Charge Only), back out, return...
It's not persistent either.
I found a way to work around it, for my purposes anyway, just leave the settings app up, don't close it. And sometimes just connecting with USB set it back, so would have to reset it again. But eventually it worked.
Kind of a pain. Because Android One and Lineage are so similar, I'd check in Lineage forums to see if there's a fix for that.

Small update: I installed Magisk and tried applying two separate modules that should add the Apt-X library files to the phone, but no luck. I've resigned to going back to stock and being hopeful that as community support starts ramping up for our device, we'll see a solution.
Oh well! AAC will need to hold us over 'til then.

need aptX support also

Just came across this in a MiA1 thread, it seems (like camera2API) that it has to be enabled (root access needed) for it to work;
https://forum.xda-developers.com/mi-a1/how-to/guide-enable-custom-bluetooth-audio-t3744371

I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.

AlexX333BY said:
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
Click to expand...
Click to collapse
Where did you read this?

pianistaPL said:
Where did you read this?
Click to expand...
Click to collapse
4pda.ru

AlexX333BY said:
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
Click to expand...
Click to collapse
Could anybody verify this method?

AsItLies said:
Just came across this in a MiA1 thread, it seems (like camera2API) that it has to be enabled (root access needed) for it to work;
https://forum.xda-developers.com/mi-a1/how-to/guide-enable-custom-bluetooth-audio-t3744371
Click to expand...
Click to collapse
Does not work for me

soulicro said:
So, I tried choosing "Apt-X" from within the developer settings - but it doesn't stick. I know my headphones support it, and I looked up the SD660 - it has support for it as well. So, is there a way to enable Apt-X on the A2?
Click to expand...
Click to collapse
I have the same with my Sony MDR-1000X. They support aptx to. But the A2 won't stick to it

a5c said:
Could anybody verify this method?
Click to expand...
Click to collapse
doesn't work for me. it immediately switches back to sbc.

soulicro said:
Small update: I installed Magisk and tried applying two separate modules that should add the Apt-X library files to the phone, but no luck. I've resigned to going back to stock and being hopeful that as community support starts ramping up for our device, we'll see a solution.
Oh well! AAC will need to hold us over 'til then.
Click to expand...
Click to collapse
I used to have a MI Max and I was able to enable apt-x hd after installing some libraries with magisk. Which process did you follow? I still can't try it on my phone.

apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813

rulezman said:
apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813
Click to expand...
Click to collapse
Just got the official October update. Aptx is supported nativly now. No need to install any magisk module.

LDAC Playback quality stuck on Best Effort, unable to change

I have a 4XL and have noticed that it is not possible to change the Bluetooth settings under developer settings. For example I have Sony WH1000 M3s and whilst it connects using LDAC it defaults to ‘Best Effort’ for LDAC quality settings and cannot be changed. It also will not let me choose another codec such as APTX-HD.
My understanding is that on Pixels (well for the Pixel 3 at least) that best effort results in a lower bitrate than SBC? So this is potentially crippling thre audio quality.
Anybody else noticed this? If so, any solution?

Lucky you.
I just picked up a pair of V-Moda Crossfade 2 Wireless Codex cans, and I can't get any other codec besides SBC working via the Developer options.

Yes, I have same and noticed that.
Trying to use AptX HD also doesn't stick. You can do it in Developer Options by messing with other BlueTooth settings first to match what AptX HD would allow but the next time I connect my headphones it's gone back to LDAC.
I think the main problem is Sony's Headphones app which defaults to LDAC (of course as it's Sony's proprietary codec!) and lack of controls to use other codecs and settings.
In that app I have Sound Quality preference selected at the bottom which actually may be using a better quality setting, it just isn't reflected in what you see in the Developer Options settings.

Interesting, the LDAC issue might not be fixable but maybe removing the Sony app will allow aptx-hd to be selectable?
Btw, other droids are not much better. Samsung’s do let you change the setting but revert back to best effort every time you connect. Only the P30 pro seems to remember but then Huawei have put that option into the normal settings rather than leave it buried in developer settings.
Sent from my iPad using Tapatalk

arsenal74 said:
Interesting, the LDAC issue might not be fixable but maybe removing the Sony app will allow aptx-hd to be selectable?
Btw, other droids are not much better. Samsung’s do let you change the setting but revert back to best effort every time you connect. Only the P30 pro seems to remember but then Huawei have put that option into the normal settings rather than leave it buried in developer settings.
Click to expand...
Click to collapse
On the Samsung Note 10+ 5G now allows selection of best audio quality for LDAC, but the the connection quality between the Sony XM3s and the 10+ is very poor. All pointless.

Kind of begs the question as to how much the on paper advantage android has with LDAC and APTX-HD really counts in the real world.
Honestly, irrespective of codecs I actually think iPhones sound better over Bluetooth which is a massive shame and totally unnecessary.
Sent from my iPad using Tapatalk

arsenal74 said:
Interesting, the LDAC issue might not be fixable but maybe removing the Sony app will allow aptx-hd to be selectable?
Btw, other droids are not much better. Samsung’s do let you change the setting but revert back to best effort every time you connect. Only the P30 pro seems to remember but then Huawei have put that option into the normal settings rather than leave it buried in developer settings.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Would the headphones even work without the app? I haven't tried.
Would they default to some built-in setting without the app to communicate with?
You go first!

Headphones definitely work without the app, I have used them before on a previous phone and forgot to install it.
BTW everything works as it should the P30 pro, you do not even have to go into developer settings to change it.
Sent from my VOG-L29 using Tapatalk

I'm also unable to get my 4XL into 909/990 kbps mode, but I noticed that Pixel 4 XL seems to default to 606/660 kbps mode, which is more or less comparable to aptX HD(576 kbps). And I know for a fact that this is not an issue with the headphones or the app, since I get 909/990 when I connect the same headphones to Sony's Android devices with the app installed via LDAC Bluetooth connection.

Interesting, my 4xl defaults (and is stuck in) to best effort not 660 balanced mode.
I think on Pixels best effort is circa 330 kbps
Sent from my VOG-L29 using Tapatalk

shaobocui said:
I'm also unable to get my 4XL into 909/990 kbps mode, but I noticed that Pixel 4 XL seems to default to 606/660 kbps mode, which is more or less comparable to aptX HD(576 kbps). And I know for a fact that this is not an issue with the headphones or the app, since I get 909/990 when I connect the same headphones to Sony's Android devices with the app installed via LDAC Bluetooth connection.
Click to expand...
Click to collapse
Always defaults to Best Effort here which is 330kbps for Pixel 3 according to https://www.soundguys.com/understanding-bluetooth-codecs-15352/
I can set it to something else and when I next go into Developer Options it's back to Best Effort! Same with setting the codec to something else.

Pixel 4's best effort seems to be 606/660, not 303/330. At least that's what the bug report says. If the 3 only connects at 303/330, that's gonna be a problem when using new BT5.0 stuff from Sony. They're using an MTK chip for BT5.0, so no aptX, only SBC, AAC and LDAC on BT5 stuff from Sony.

shaobocui said:
Pixel 4's best effort seems to be 606/660, not 303/330. At least that's what the bug report says. If the 3 only connects at 303/330, that's gonna be a problem when using new BT5.0 stuff from Sony. They're using an MTK chip for BT5.0, so no aptX, only SBC, AAC and LDAC on BT5 stuff from Sony.
Click to expand...
Click to collapse
That's interesting and encouraging, thanks for that.

That is interesting, sound guys testing of the 3 and 3a indicated 330 for best effort.
Sent from my iPad using Tapatalk

shaobocui said:
Pixel 4's best effort seems to be 606/660, not 303/330. At least that's what the bug report says. If the 3 only connects at 303/330, that's gonna be a problem when using new BT5.0 stuff from Sony. They're using an MTK chip for BT5.0, so no aptX, only SBC, AAC and LDAC on BT5 stuff from Sony.
Click to expand...
Click to collapse
Out of interest, how have you been able to tell the bitrate it used for best effort?
*
Sent from my VOG-L29 using Tapatalk

i was under the impression that this is relative to the device you connect.

Hi All,
There is a fix. I have the Sony WH 1000mx3 headphones and the One Plus 7 pro 12/256 fully updated. Enable developer options in settings on your Android phone if you haven't already done so. Remove then reinstall the Sony connect app (your previous settings will remain after the reinstall). Follow the prompt from the Sony app to connect your headphones by bluetooth. When the headphones are connected go to settings, Bluetooth and Device connection, then Bluetooth. Under available media devices you should see your Sony WH 1000XM3 headphones active. Click the settings icon to the right. Turn off HE audio: LDAC.
Open your preferred music streaming application (Tidal) and play music, verify that the headphones are operating. Go to system, then Developer options. Under Networking scroll down to the Bluetooth settings. The Bluetooth audio LDAC Codec: playback quality has now defaulted to Streaming Optimized for Audio Quality. You can now adjust the Audio Codec, Sample rate, and Bits Per Sample to your preference. The settings will stay and won't need to be reapplied.
I hope this helps.
Acbaines

bumping this thread, because I was looking for an answer, this was the closest to it.
I decided to dump the logs with adb, and found that my Pixel 4XL, latest and greatest updates as of May 2020, is negotiating 990 LDAC, with the 1000XM3s.
I can use the dev options to push it around to 330/660/990.
No matter what setting I use prior, if I go to auto, it will negotiate to 990, which is pretty awesome. I have not tested to see if it drops off if you walk away from the phone, but given the BT range I get with LDAC, I'm assuming not.

clwclw said:
bumping this thread, because I was looking for an answer, this was the closest to it.
I decided to dump the logs with adb, and found that my Pixel 4XL, latest and greatest updates as of May 2020, is negotiating 990 LDAC, with the 1000XM3s.
I can use the dev options to push it around to 330/660/990.
No matter what setting I use prior, if I go to auto, it will negotiate to 990, which is pretty awesome. I have not tested to see if it drops off if you walk away from the phone, but given the BT range I get with LDAC, I'm assuming not.
Click to expand...
Click to collapse
That's good news, thank you for that.

How to know the bit rate is 990 using best adaptive?