Has anyone tested if the Gnex with ICS now supports AVRCP 1.3+ when connecting it via Bluetooth to their car stereo?
1.3/1.4 should support displaying Track info when playing music via Bluetooth. I have a 2010 Mazda which should support it, but I wanted to see if others had tried this?
If it does have support I would think Google Music would support it, but hopefully it extends system wide for things like Spotify?
It did not work in Gingerbread, but I had hoped to see it in ICS.
Here is a thread from earlier:
http://forum.xda-developers.com/showthread.php?t=723622&page=2
Some background info:
http://en.wikipedia.org/wiki/Bluetooth_profile#Audio.2FVideo_Remote_Control_Profile_.28AVRCP.29
I believe Android is using the BlueZ Bluetooth stack which appears to support AVRCP 1.3:
http://www.bluez.org/profiles/
http://article.gmane.org/gmane.linux.bluez.kernel/15551/match=avrcp
My 2010 Mazda would be much better if the display didn't just say "BT" but rather the track title
Sent from my Galaxy Nexus using xda premium
same with my 11 explorer. it just says galaxy nexus where the title goes
My BMW with connecteddrive shows "No track info" , so i'm guessing it's not working
No. ICS has no AVRCP 1.3+ support. At least for now.
I read somewhere that there will be changes made to bluetooth with 4.0.3.
Maybe Google finally woke up and implemented the latest bluez.
Seems like we have to wait....
Would be awesome if it did. Loved my HP Veer because it did. Also tired of seeing just BT on my radio
I can add to all of this with a few personal experiences. Back and forward work, however, music info doesn't work on the following that I have tested:
BMW ConnectedDrive system (someone confirmed that above)
Ford Sync system
Acura system
Let's hope that 4.0.3 incorporates this.
Has anyone tried one of the .3 custom roms to see if anything has changed?
Same issue on 2011 Nissan Maxima, track and artist info is blank.
cpcrazyfly said:
My 2010 Mazda would be much better if the display didn't just say "BT" but rather the track title
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
MrTek said:
Has anyone tested if the Gnex with ICS now supports AVRCP 1.3+ when connecting it via Bluetooth to their car stereo?
1.3/1.4 should support displaying Track info when playing music via Bluetooth. I have a 2010 Mazda which should support it, but I wanted to see if others had tried this?
If it does have support I would think Google Music would support it, but hopefully it extends system wide for things like Spotify?
It did not work in Gingerbread, but I had hoped to see it in ICS.
Here is a thread from earlier:
http://forum.xda-developers.com/showthread.php?t=723622&page=2
Some background info:
http://en.wikipedia.org/wiki/Bluetooth_profile#Audio.2FVideo_Remote_Control_Profile_.28AVRCP.29
I believe Android is using the BlueZ Bluetooth stack which appears to support AVRCP 1.3:
http://www.bluez.org/profiles/
http://article.gmane.org/gmane.linux.bluez.kernel/15551/match=avrcp
Click to expand...
Click to collapse
Unfortunately I am quite confident that our 2010 Mazdas do not support avrcp 1.3, only 1.0.
Also it has far less to do with the OS than having to do with the bluetooth drivers/stack. My neighbor's droid x sends metadata to his 2011 mits. lancer, but when we tried it on my 2010 mazda3 we saw nothing but "bt audio". The 2011+ on the other hand supposedly do support avrcp 1.3.
While hearing that bluez has finally implemented avrcp support in their nearly ubiquitous bt stack, it unfortunately does not mean that we will be seeing meta data...
One interesting thing to note is that while the 2010s support avrcp 1.0 and the 2011s support avrcp 1.3/1.4 the bluetooth module is a slightly different part number, they are interchangeable (according to my dealer).
Unfortunately the Galaxy Nexus (with FW 4.0.1) has AVRCP 1.0 which means no ID3 tag info, no repeat/shuffle/scan, just basic controls (play/pause/skip).
Let's hope that with the new FW there will be some changes in the BT stack.
As far as I can see it doesn't have the Message Access Profile either. My S2 got my text messages to my sync system, no luck with the Nexus.
Any more word on this? Bought a nice new stereo for my car and would love to see some track information
pictureaday said:
Unfortunately I am quite confident that our 2010 Mazdas do not support avrcp 1.3, only 1.0.
Also it has far less to do with the OS than having to do with the bluetooth drivers/stack. My neighbor's droid x sends metadata to his 2011 mits. lancer, but when we tried it on my 2010 mazda3 we saw nothing but "bt audio". The 2011+ on the other hand supposedly do support avrcp 1.3.
While hearing that bluez has finally implemented avrcp support in their nearly ubiquitous bt stack, it unfortunately does not mean that we will be seeing meta data...
One interesting thing to note is that while the 2010s support avrcp 1.0 and the 2011s support avrcp 1.3/1.4 the bluetooth module is a slightly different part number, they are interchangeable (according to my dealer).
Click to expand...
Click to collapse
T_T I have a 2011 Mazda 3 and my galaxy nexus also won't show any track info. I was excited to see that the gnex had bluetooth 3.0 but didn't realize it would only be AVRCP 1.0... My gf's sister has an HD7 and when it pairs with my car it shows all the info and it also has the reading your text message feature so when she receives a text the car will ask "read it or ignore"
Is there anyway to copy bluetooth files that have the AVRCP 1.3 from another phone to ours?
bumpity bump for hlaalu's question
Bump bump large donation to anyone who hooks it up!
**Bump this
Running a 4.0.3 build and nothing is shared to my Audi Music Interface. Hopefully an official build may address it?
Sent from my Galaxy Nexus using xda premium
I've seen mention of CM supporting it, has anyone tried AVRCP with an unofficial CM build?
Rakinos said:
I've seen mention of CM supporting it, has anyone tried AVRCP with an unofficial CM build?
Click to expand...
Click to collapse
I had CM 7.1 installed on my Desire HD, and AVRCP worked. The screen on my Mazda showed track, album, and artist information information.
Hi all,
This is my first post / thread, let me start by saying thanks to all of you !
I am another happy owner of a nexus phone
Our official android 4.1 version does not support USB DACs, and perhaps we can all ask for support at code dot google
Many audiophiles and headfiers already own USB DACs. Think of them as ‘sound cards’ or ‘USB audio devices’ . DAC is actually an acronym for Digital to Analog Converter. And ‘usb audio’ is a standard as you can see in usb dot org
I can do some alpha / beta testing if any new image with usb audio support enabled comes up, just let me know. Or feel free to suggest any other way of enabling usb audio.
I am not talking about android-only docking stations but regular hifi DACs. There are even portable DACs to take with you on road !
™
+1
Also to have this link to keep track of the issue: http://code.google.com/p/android/issues/detail?id=24614
mengsuan , Thank you for providing a link to code dot google, I am a newbiew so I can’t post links yet.
S III seems to be the best choice right now for audiophiles on the road
To tell you the truth I expected all 4.1 phones to support usb audio out of the box. It was my fault, I should have read the articles referring to usb audio support better.
Hopefully the community will help and provide some custom image for Galaxy Nexus even before google does.
Hi.
I want to playback sound from my Nexus 7 2013 (Flo) in a fixed install environment on a Mutli Channel USB Audio DAC. It is a 7.1 Channel device and has a CMedia CM6206 chip. I currently use the stock Android 5.1.1 build LMY47V.
From what I've read a multi channel source, e.g. a movie, should play fine, but the difficult part seems to be the spreading of stereo sound onto multiple channels. After reading through different articles related to ALSA I finally found an example configuration which does exactly what I need:
http://drona.csa.iisc.ernet.in/~uday/alsamch.shtml
Sadly it is for Linux Desktop Editions and Android seems to be quite different (Driver Layer, Configuration ...). After figuring that out I came across this thread:
http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-surround-sound-t2964809/post57310487
Where I finaly found the place the mixer configuration would probably go to. But now I'm stuck on translating the .acoundrc file into the right XML statements. This is where I want to ask the experts here on XDA Developers...
What I got so far:
- Device is rooted
- Alsa Mixer is installed
- Example .asoundrc
The USB DAC enumerats (with alsa_aplay -L) as "default:CARD=Device" or as (with alsa_aplay -l) "card 1".
Thanks and best regards,
Martin.
Hello guys
I hope i'm right here.
I'm owner of an Peugeot 308 GTi (2016) with a navigation system called "Smeg+" .
I am searching for a long time how to integrate android in my car.
A full head unit with complete new display isn't possible because i need my vehicle configuration like climatronic, light settings etc.
So there is unfortunately only one solution with old android 6.
This:
m.de.aliexpress.com/item/32818864085.html?pid=808_0003_0109&spm=a2g0n.search-amp.list.32818864085
But my idea is, what if i could integrate a simple mirrorlink module?
I need only mirrorlink with usb or hdmi so i could take my old galaxy S5 with Android 8.0 and ready.
But i can't find a module with touch driver.
I just need a module with mirrorlink and a integrated
4-pin lvds switch so that i can simple switch with my steering wheel for example.
But i want also control my Samsung trough the original display so i need a module with touch driver too.
In the link there is a full android system with mirrorlink support but i don't need this android so it's wasted money for me.
Do you have some working ideas?
Maybe a Multimedia Interface or something with mirrorlink and touch driver support?
That would be great.
Sry for my english, i'm from germany.
I have the newest model Shield I believe:
Android ver. 9
SW version: 8.2.2(32.6.509.0)
Kernel ver: 4.9.140-tegra ...
Description: Tegra X1 + mDarcy
While there is audio passthrough via HDMI, USB audio output fixes the bitrate at 16/48 or 16/192 in high quality mode. I have a semi high-end hi-fi setup with good DAC where you want an 'untouched' audio bitrate and 24 to 16 bit downsampling is rather unattractive . I have been looking at: https://source.android.com/devices/audio/usb It appears that using isochronous mode is universally standard, but the sub mode on most Android devices, including the Shield, is set to Adaptive when it needs to be Asynchronous sub mode to do this. I can't find any online source with an kernel mode setting to do this. I am not even sure I am on the right path here.
Any insights, references, tips, or better yet some ADB command line code?
Thanks,
p-we
Hi there - where did you land on this? Thanks!
Never took off...
p-we said:
Never took off...
Click to expand...
Click to collapse
Still no take-off or did you manage something with this? I'm in the exact same hi-fi boat
I did find that sideloading UAPP (USB Audio Player Pro, will cost you 8 dollars or so) on the shield technically works and it can play audio without any re-sampling done (my dac shows the sample rate changing when songs have different sample rates so I know it works), even stream from Qobuz / Tidal, but the UX is pretty much unusable since it's not an Android TV app lol
binasnotatie said:
Still no take-off or did you manage something with this? I'm in the exact same hi-fi boat
I did find that sideloading UAPP (USB Audio Player Pro, will cost you 8 dollars or so) on the shield technically works and it can play audio without any re-sampling done (my dac shows the sample rate changing when songs have different sample rates so I know it works), even stream from Qobuz / Tidal, but the UX is pretty much unusable since it's not an Android TV app lol
Click to expand...
Click to collapse
I've not looked into the USB sub mode since I first looked into it and posted in 2021.
Good idea on UAPP which I am familiar with USB-C on android mobile. Might play around with that as I think I'm already good for the $8. It's indeed a pain when Android apps don't use the Google/Android TV remote system.
I've since solved the problem for my hi-fi audio purity 'fix' by moving to Roon which provides flawless high res audio (via network to an RPi's USB 2.0 audio output) and is controlled by mobile phone via the Roon Remote app. Now if Roon would only make an Android TV compatible remote app the Nvidia Shield would be a great UI experience and the USB output wouldn't matter anymore.
So for what it's worth, over at the Nvidia forums one of the staff members confirmed that this is on their 'to-do-list' so with a bit of luck we can see this fixed in the next Shield update
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/520414/match-content-audio-resolution-for-usb-audio/3359083/