For some reason, I cannot select ok and continue on my pioneer 4100 after I connect to USB. I'm using cm12 with note 4.
Are you running CM12.1 (5.1), i had to downgrade to CM12 (5.0.2).
diagdave said:
Are you running CM12.1 (5.1), i had to downgrade to CM12 (5.0.2).
Click to expand...
Click to collapse
Yes, so downgrading fix the problem.
Thanks 4 the response.
killa2009 said:
Yes, so downgrading fix the problem.
Thanks 4 the response.
Click to expand...
Click to collapse
Yep, the layout was screwed on 5.1. if you force your dpi on your phone to 120 it works - of course your phone then is almost useless. so downgrade was only option.
So when do think there will be a fix? Can I force phone dpi to 120 then change it back normal after I select the box?
I have the save problem but it is intermittent. On 5.02. Thanks for the info. I thought my micro bypass was bad.
For 12.1 you should be able to go back to a nightly around the 22nd and it'll work.
22nd's nightly on one plus still works but anything after I have the display issue.
Andy
akp982 said:
For 12.1 you should be able to go back to a nightly around the 22nd and it'll work.
22nd's nightly on one plus still works but anything after I have the display issue.
Andy
Click to expand...
Click to collapse
Same issue as discussed here I assume? Has to do with the roms built in DPI changing functionality (I THINK)...
s2kpdx said:
Same issue as discussed here I assume? Has to do with the roms built in DPI changing functionality (I THINK)...
Click to expand...
Click to collapse
Since I could not get the CM from before 5/22 from CM I went on a hunt today to find a rom that would work with my 4100nex, I found that Euphoria from 6/02 based on 5.1.1 works for me. I tried several other builds from different devs, I really wanted to be able to find a 5.1.x that worked and it appears I have. I was not able to get past the Don't Show me this again scrunched up screen / DPI issue. I still have a phone book issue that I had on CM 12, for some reason it will not show names in my call log, but at least I got back into Android Auto. Hope this helps someone.
The latest CM12.1 nightlies have been working great for me with Auto. All of the nightlies that I tested in the first three weeks of May did not work, but the end of May nightlies have worked great so far.
bmxchampga said:
The latest CM12.1 nightlies have been working great for me with Auto. All of the nightlies that I tested in the first three weeks of May did not work, but the end of May nightlies have worked great so far.
Click to expand...
Click to collapse
The end of May and early June nightlies were fine, but then it got broke again sometime after that. It's been a crazy roller-coaster ride trying to figure out which build of which ROM has the features that you want and actually works with Android Auto.
WisdomWolf said:
The end of May and early June nightlies were fine, but then it got broke again sometime after that. It's been a crazy roller-coaster ride trying to figure out which build of which ROM has the features that you want and actually works with Android Auto.
Click to expand...
Click to collapse
Yeah, I just updated to the latest nightly and it broke Auto for me again.
how is everyone finding old version of CM 12.1 nightly that they can revert to? I have Oneplus One and i'm trying to revert to 05/31/15 nightly in which others have said works with Android Auto. I'm getting a Hyundai Sonata and want to be able to use Android Auto with it! (excited)
arabcamel said:
how is everyone finding old version of CM 12.1 nightly that they can revert to? I have Oneplus One and i'm trying to revert to 05/31/15 nightly in which others have said works with Android Auto. I'm getting a Hyundai Sonata and want to be able to use Android Auto with it! (excited)
Click to expand...
Click to collapse
Some phones have a better selection of older releases than others: http://download.cyanogenmod.org/
Sometimes other releases are downloadable from elsewhere.
Sometimes people keep copies under /sdcard/cmupdater.
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
http://www.cmxlog.com/12.1/bacon/ is rather useful for keeping track.
Updated mine yesterday and Android auto is back normal
Awesome, I'll have to flash and try myself. Do you think this would also apply to other custom ROMs that are based off of the newest CM?
Sent from my A0001 using XDA Free mobile app
akp982 said:
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
Click to expand...
Click to collapse
Some insight posted there:
density: do not apply to virtual displays Check the incoming configuration density to ensure that it is the same as the device's default density before forcing preferred values. Only apply display metrics if the display is not a presentation.
Click to expand...
Click to collapse
I was able to work around this problem on my Xperia Z2 tablet w/ CM12.1 by lowering ro.sf.lcd.density in /system/build.prop from default 240 to 180.
But this is just a workaround for the REAL problem shown in the comment. It had the side effect of making icons on homescreen smaller.
The REAL problem is that Android Auto uses a virtual display/Presentation to make up the AA display. Some ROMs were applying physical screen DPI of the phone to the virtual display, instead of the AA specified parameters that should come from the headunit. For Pioneer HUs (or at least 4100NEX) the parameters are 800x480 with a reported DPI of 160.
akp982 said:
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
http://www.cmxlog.com/12.1/bacon/ is rather useful for keeping track.
Updated mine yesterday and Android auto is back normal
Click to expand...
Click to collapse
Flashed July 4th build of BlissPop and it works great now with Android Auto. I had to turn off ADB in the developer settings.
Clean install or dirty...ota
Related
!!Forgot to add it to the title, I'm talking about CM11 for KFHD7!!
Earlier this morning I found a thread saying M8 has been released for select devices. I went to CM's download page to check if it was out for KFHD 7 (tate) and found no M8, only the latest nightlies. I checked again a few times, hoping it might appear later today.
I still can't find it for tate, but when I went to Settings -> About Tablet -> CyanogenMod updates and had it check for updates, it found an update with this name: cm-11-20140708-SNAPSHOT-M8. I supposed this was it, so I downloaded it and flashed it to my kindle. Turns out I couldn't open my settings in any way, cause every time I tried to launch them they kept crashing.
I downgraded it again to M7 since I might need it tomorrow, but it's bugging me. This update can't be found in CM's download page (at least I don't see it anywhere), and if the settings aren't even opening, it's probably not too stable. I don't know much about nightlies and monthlies yet, but I thought monthlies were supposed to be more stable than nightlies... Does anybody know what's up with this update?
I've had no issues with m8 as of yet. Installed and working fine, already put my DPI back to 178 and enabled my dual panes and running fine.
YuriPan said:
!!Forgot to add it to the title, I'm talking about CM11 for KFHD7!!
Earlier this morning I found a thread saying M8 has been released for select devices. I went to CM's download page to check if it was out for KFHD 7 (tate) and found no M8, only the latest nightlies. I checked again a few times, hoping it might appear later today.
I still can't find it for tate, but when I went to Settings -> About Tablet -> CyanogenMod updates and had it check for updates, it found an update with this name: cm-11-20140708-SNAPSHOT-M8. I supposed this was it, so I downloaded it and flashed it to my kindle. Turns out I couldn't open my settings in any way, cause every time I tried to launch them they kept crashing.
I downgraded it again to M7 since I might need it tomorrow, but it's bugging me. This update can't be found in CM's download page (at least I don't see it anywhere), and if the settings aren't even opening, it's probably not too stable. I don't know much about nightlies and monthlies yet, but I thought monthlies were supposed to be more stable than nightlies... Does anybody know what's up with this update?
Click to expand...
Click to collapse
Yes i have, settings crashes every time you open, but can be fixed if you clear data. I also had few lag problems and minor glitches and that was it. Hascode didn't realize the m8 had come out for android so i think there may be a problem.
Bao289 said:
Yes i have, settings crashes every time you open, but can be fixed if you clear data. I also had few lag problems and minor glitches and that was it. Hascode didn't realize the m8 had come out for android so i think there may be a problem.
Click to expand...
Click to collapse
Οh, so there's a fix for that. Thanks. Although I think I'll stick to a nightly, it seems like too much trouble to go and fix that when the nightly after M8 hasn't caused any stability issues to me yet.
Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Bump..
abhi.eternal said:
Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Click to expand...
Click to collapse
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Tripple-c said:
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
Click to expand...
Click to collapse
That issue you discribed above would only happen if you did a dirty install and didn't install gapps. The newer version backs up gapps so you only have to install. I recommend a clean install(factory reset and format system) to get the camera to detect the only way and then reinstall with gapps use the newest nightly.
abhi.eternal said:
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Click to expand...
Click to collapse
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
pekcle said:
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
Click to expand...
Click to collapse
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
abhi.eternal said:
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
Click to expand...
Click to collapse
It's all cool. There's no harm in that. But Android 4.1 to 4.4 was fairly mild and incremental. Lollipop was a hefty change in concept and usage. I tried it on my N7 2013, and it was just harder to use. Buttons were smaller and closer together, more taps and swipes just to do something, etc. It feels like they compromised ease of use just to adhere to the material design. Seriously made me consider going to an Apple product. No joke!
So my radio came in today and android auto doesn't work. It says my phone was not compatible. I have a rooted note 4 running android 5.0.2 (cm 12). I also used my fiancée sg5 with the new stock 5.0 and it still doesn't work! Anybody care to help?
Anybody?
Did you try calling pioneer?
I'm having the same issue. I have a rooted T-Mobile LG G3 running 5.0.
I thought I was the only one
smalltownbird said:
Did you try calling pioneer?
Click to expand...
Click to collapse
Close on the weekend
There are YouTube videos of car audio installers using it so it has to work
Same here, I have an HTC One M8 rooted and its not working for me either. I read the manual and apparently you need a CD-MU200 interface cable from pioneer. Don't know if that's bulls**t or not, but we'll find out. I have the USB setup so that I can use the built-in port in my car. I don't know if that's what the reason is or not. I'll have to call pioneer on Monday.
Sent from my HTC One_M8 using Tapatalk
Well that's three people with the same problem
I think you need the Google apps loaded for one thing, and having an account enabled may be even better.
Lollipop is essential at this time, and I think 5.1 is even better.
Nexus also has a better chance of working.
I am trying to get developer mode working and I am mainly using my Nexus 7 2012 w/ 5.1 because my 2013 N7 and N9 both are still on 5.0.
But its just about api21 that AA runs on. 5.1 has api22 and its confirmed AA is working on "normal" lollipop, I mean 5.0.x
I'm running 5.0.1 on my M8 and Android Auto isn't working
Sent from my HTC One_M8 using Tapatalk
Also it's important to have latest GMS installed.
http://www.apkmirror.com/apk/google-inc/google-play-services/
Check version you need, download it and install. I can bet all of you have old versions (as I was surprised some time ago that it's not updating and I was stuck on 6.x when for months there was 7.x available)
brainscollector said:
Also it's important to have latest GMS installed]
Check version you need, download it and install. I can bet all of you have old versions (as I was surprised some time ago that it's not updating and I was stuck on 6.x when for months there was 7.x available)
Click to expand...
Click to collapse
Thanks for the help. Unfortunately it didn't work for me. I went on the reviews for android auto app on Google play and it seems a lot of other people are having the same issue.
Theres a new update on pioneer site, but didn't fix problem.
Maybe
You can generally find the Android Auto button located on the home screen of your car's digital display. How to navigate to the home screen will vary by manufacturer, so check your car's user guide.
I plugged in my phone, found the Android Auto button, but it won't open.
If this is the first time you’re using Android Auto in a particular car, be sure to unlock your phone and accept the terms and conditions on your phone’s screen after you’ve connected and touched the Android Auto button on your display.
Also, make sure that the "Only connect to known cars" setting in the Android Auto app is unchecked.
The voice command button takes me out of Android Auto.
My USB cable isn't working.
Not all USB cables will work with all cars. Your car's user guide should have information about the best USB cable to connect your phone to the display.
Click to expand...
Click to collapse
https://support.google.com/androidauto/
killa2009 said:
Theres a new update on pioneer site, but didn't fix problem.
Click to expand...
Click to collapse
Update for what ? Pioneer firmware ? Can you link ?
mikereidis said:
Update for what ? Pioneer firmware ? Can you link ?
Click to expand...
Click to collapse
Pioneer nex 4100 radio
mikereidis said:
Update for what ? Pioneer firmware ? Can you link ?
Click to expand...
Click to collapse
http://www.pioneerelectronics.com/S...tibility/15MY_FW-Update_v1.03_4G_20150318.zip
http://www.pioneerelectronics.com/PUSA/Car/NEX/AVH-4100NEX
funny that it has tomorrows release date today ^^
brainscollector said:
http://www.pioneerelectronics.com/S...tibility/15MY_FW-Update_v1.03_4G_20150318.zip
http://www.pioneerelectronics.com/PUSA/Car/NEX/AVH-4100NEX
funny that it has tomorrows release date today ^^
Click to expand...
Click to collapse
Yup, I still updated but no change.
Hey guys, I had posted a while back saying that for some reason, after flashing the new build of Marshmallow to my Nexus 6, the load times for web pages and just about everything else seems to be a bit slower than usual. I had said at the end of the post that it was fixed, but now the problem is arising again. Is anyone noticing long load times with all apps that use internet? Web pages load slower, the Facebook app takes much longer to load pictures and posts, Skype took longer to login and show everyone's profile pics etc. Never had this problem before on lollipop!
EDIT: Also, when I switch between my 2.4Ghz and 5Ghz WiFi bands, it shows a push notification that says that this WiFi signal has no internet access, and then it connects just fine after a few more seconds. This is odd. Maybe just a buggy first run of Marshmallow?
Sent from my Nexus 6
H4X0R46 said:
Hey guys, I had posted a while back saying that for some reason, after flashing the new build of Marshmallow to my Nexus 6, the load times for web pages and just about everything else seems to be a bit slower than usual. I had said at the end of the post that it was fixed, but now the problem is arising again. Is anyone noticing long load times with all apps that use internet? Web pages load slower, the Facebook app takes much longer to load pictures and posts, Skype took longer to login and show everyone's profile pics etc. Never had this problem before on lollipop!
EDIT: Also, when I switch between my 2.4Ghz and 5Ghz WiFi bands, it shows a push notification that says that this WiFi signal has no internet access, and then it connects just fine after a few more seconds. This is odd. Maybe just a buggy first run of Marshmallow?
Sent from my Nexus 6
Click to expand...
Click to collapse
maybe an issue with your wifi? how is it when you use mobile data?
simms22 said:
maybe an issue with your wifi? how is it when you use mobile data?
Click to expand...
Click to collapse
It's not loading really at all, but that's also due to my LTE coverage being awful in my area, that's always been bad haha so no change there. My other devices in the house are working just fine on my network, the Nexus 6 however seems to load slower, and it's only now that I'm on Android 6.0! Is it working fine for you?
EDIT: Just an update here, hours later, it may be my internet connection, possibly. But I'm not 100% sure on that either. If nobody else is having this issue, it may just be. Like I said though, it seems to be working fine with my other devices!
EDIT 2: http://imgur.com/gallery/TGiCU55 This is a speed test I did on my phone, I have 30Mbps internet and that shows!
I'm having same issue. Dirty flash. Kinda wondering if a clean factory reset is in order.
no issues here....came from a clean flash, which is standard protocol.
M seems fast so far, but I did change my animations Scale from 1.00 to .50! The only website to load very slow is XDA... go figure!
edif30 said:
I'm having same issue. Dirty flash. Kinda wondering if a clean factory reset is in order.
Click to expand...
Click to collapse
It's weird no? Mine was a clean flash! Formated userdata and cleared cache! Still have this issue.
Sent from my Nexus 6
H4X0R46 said:
It's weird no? Mine was a clean flash! Formated userdata and cleared cache! Still have this issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yup. I did same. I might try the lollipop radio. Idk...
XDA is always sloooooow, even on a fast PC.
I've seen several other people mention slow net speeds on M as well but I've not noticed it yet. The WiFi code of M caused issues awhile back on some previous builds of HellsCore kernel too. I dont know the specifics of it though.
LGtMgG2t said:
XDA is always sloooooow, even on a fast PC.
I've seen several other people mention slow net speeds on M as well but I've not noticed it yet. The WiFi code of M caused issues awhile back on some previous builds of HellsCore kernel too. I dont know the specifics of it though.
Click to expand...
Click to collapse
So there was a definite change in the radio for this build then. More than a subtle change. I wonder if it's just not perfect, I realize having a Nexus means getting the first run of all Android software, but I wonder if this is a bug in the build, or a radio that could use some work. But it does sometimes take longer to load things! I'm on very fast WiFi too!
Sent from my Nexus 6
I honestly don't know and would like to hear more specifics. I can tell you I've seen comments on this board the last couple fo days talking about massive WiFi battery drain as well.
I only know HellsCore adopted the newer M code for WiFi in his kernel and people were affected. He then had to create two builds of the kernel. One with newer WiFi code that didn't cause any issues for people and another build with the older WiFi code from L. Have you checked his G+ site?
LGtMgG2t said:
I honestly don't know and would like to hear more specifics. I can tell you I've seen comments on this board the last couple fo days talking about massive WiFi battery drain as well.
I only know HellsCore adopted the newer M code for WiFi in his kernel and people were affected. He then had to create two builds of the kernel. One with newer WiFi code that didn't cause any issues for people and another build with the older WiFi code from L. Have you checked his G+ site?
Click to expand...
Click to collapse
No I haven't! I'll check that out! So that leads me to believe that it was a change in the new radio! He had to change it to code used in L radio so that may be it! Thanks for the info! I'll look into that some more!
Is it possible to flash the lollipop radio to test? I'd think you could. But I'm not 100%.
edif30 said:
Is it possible to flash the lollipop radio to test? I'd think you could. But I'm not 100%.
Click to expand...
Click to collapse
Yes, radio is independent of rom...
galaxys said:
Yes, radio is independent of rom...
Click to expand...
Click to collapse
So you're saying if I flash the radio file from a 5.1.1 stock image, marshmallow will boot and work correctly? I might try that!
Sent from my Nexus 6
Hey guys! An update here, I just read through another post that was about this same issue, and someone in there said that downloading DNset from the play store fixes this issue! It changes your WiFi settings from ipv4/ipv6 to just ipv4. I did it and it's working so far, but I'm going to give it some more testing and see if it fixed! Try it out
Sent from my Nexus 6
H4X0R46 said:
Hey guys! An update here, I just read through another post that was about this same issue, and someone in there said that downloading DNset from the play store fixes this issue! It changes your WiFi settings from ipv4/ipv6 to just ipv4. I did it and it's working so far, but I'm going to give it some more testing and see if it fixed! Try it out
Sent from my Nexus 6
Click to expand...
Click to collapse
Were you able to solve your slow page load issue?
I having same issue coming out of the box with a new N6P.
On TMO & Wifi - my old OPO had no issues.
But seems at least on LTE about town, my pages for social media & browsers are sloooooow.
perveeus said:
Were you able to solve your slow page load issue?
I having same issue coming out of the box with a new N6P.
On TMO & Wifi - my old OPO had no issues.
But seems at least on LTE about town, my pages for social media & browsers are sloooooow.
Click to expand...
Click to collapse
Hey dude, well honestly it didn't seem to fix it. Placebo effect lol What I think it comes down to is just Marshmallow being rough around the edges at this point because I have stock rooted Marshmallow 6.0 on my Nexus 6 and have cyanogenmod 12.1 installed as a secondary ROM, When booted into cyanogenmod, pages load much faster and it's more responsive as far as I can tell! So, it must be a bug with Marshmallow! Keep in mind cyanogenmod 12.1 uses Android 5.1.1 as a base!
Not sure if this is a nougat issue or a Franco kernel issue, but when using Ford MySync or whatever it's called I show unknown artist unknown song as my display on my car audio screen. This same configuration was working fine on MM with France r10 but once I moved to Nougat it's been unable to give me artist and song info.
I've cleared cache, reinstalled apps, removed and added my car back as an audio source all with no luck in resolving. I have also looked through the Franco thread so I don't think it's related to his stuff. I am also updated to the latest kernel he released, no fix there. Not really anything else special on my device except magisk for root.
Is anyone else having this issue? It's kind of driving me crazy. I almost want to revert to factory and see if that changes anything but don't want to re-root etc.
I have searched this forum and others for a fix but everyone says it's app specific, which mine is not. It won't work in sound cloud, play music, YouTube, or any other media apps it was known working in before the update.
I have the same issue in my Mustang...
Budwise said:
I have the same issue in my Mustang...
Click to expand...
Click to collapse
Are you rooted or using any non stock kernel? If rooted, what method? If kernel which? Thank a for the reply. Its nice to know it's not just me.
Rooted yes. I've tried stock kernel and Franco.
Budwise said:
Rooted yes. I've tried stock kernel and Franco.
Click to expand...
Click to collapse
Took out my wife's 2015 explorer today and it has the same problems. I wonder if 4.10 will fix it? I'm holding off for a while before taking it...
I had the same problems with my car ( VW Passat 2014). I have the Sony Xperia ZX and HTC 10 and no problems with Bluetooth. I am using original rom and Nougat. It seems the is only Oneplus phones.
I've tried 4.10 and also now Lineage and it doesn't fix it on any of them. I'm guessing its firmware related then.
I'm having trouble connecting media on my kia!! Can receive calls but no media! Wtf tried to enable it and didn't work
Sent from my ONEPLUS A3000 using Tapatalk
I believe someone said it's OOS 4.0.3+ so 4.0.2 was fine. I can confirm because I experienced this after updating to 4.0.3.
This bug is actually a pretty big peeve of mine. I'm considering going back to 4.0.2 because of it
7.0 update fixed this for me but when I tired the 7.1.1 update it broke it again and also added a noticialbe lag when using the controls on in my car. I have since reverted back to using the 7.0 software.
Alaris said:
7.0 update fixed this for me but when I tired the 7.1.1 update it broke it again and also added a noticialbe lag when using the controls on in my car. I have since reverted back to using the 7.0 software.
Click to expand...
Click to collapse
So you are saying it does not work with OOS4.1?
PaKii94 said:
So you are saying it does not work with OOS4.1?
Click to expand...
Click to collapse
It does not work on mine, unfortunately. It DID work for a day or two though.
I'm running daily Lineage OS using default kernel (usually Fusion kernel, however not right now since it's not updated for latest source) and working beautifully with my Volvo Sensus Connect, both bluetooth internet connection for car and Bluetooth audio with audio track text working. So probably some Ford mumbo jumbo. ?