Alright here is my dilemma: I have a android head unit for my car An6b01 (Adayo, FORYOU, K1) it runs on froyo 2.2 it has a 6.1 inch screen, 1 sd micro slot & and 1 regular sd, 3 usb ports wi-fi and bluetooth 1ghz arm8 processor etc. I'm able to go on the market place web and all that good stuff my problem is that although the unit runs on android 2.2 it has its own native apps which seem to control some of the hardware on the unit. For example it has a bluetooth app thats designated for pairing with your phone which lets you play music off of it receive calls and go through your phone book, This app also enables if the bluetooth is on or not. Now if you go to android settings the bluetooth option is not there and i'm unable to pair with different device such a ODB2 module. I was wondering if there is a way that i could add the bluetooth option back into my setting in order for me to pair with other devices. I have tried some of the apps of the market place like "Bluetooth Enabler" and "Bluetooth Manager" but when i try turning on the bluetooth through there it just says "Turning on Bluetooth" and nothing happens. My unit is rooted and i'm familiar with editing the system files and flashing roms. Could any one give me some tips on how i can enable the Bluetooth setting in my android setting? I also have all the system files if anyone is willing to look at it. thanks:
i just relized that i might of put this in a wrong area... feel free to move it sorry
Hi all!
I wanted to open up a discussion about the new Oreo features for Bluetooth codecs in the developer section. I haven't been able to find a comprehensive guide or info anywhere that covers how it actually should work, and I don't believe it's working correctly - I would like to explore more with you.
I'm on a Google (carrier free) Pixel, using a fresh install of OPR6.170623.012 - which is working brilliantly by the way.
It seems to me that I can't make the settings stick, if I for example change the Bluetooth Audio Codec to aptX, or modify any of the other settings when I go back in it always reverts to the 'Use System Selection (Default)' option. I'm typically trying this with Bluetooth off, changing the setting and turning Bluetooth on. I've also tried rebooting in-between, as well as different variations. The developer toggle is set to on of course.
It may be my misunderstanding of how this works, but it even if I stay on the developers screen and change the codec, if I turn Bluetooth on and it connects to a device, for instance my in-car Bluetooth audio, which I believe supports aptX, it doesn't care what the codec setting is and displays 'Streaming: SBC', which is of course what I'd expect would be overridden.
The only thing that seems to stick is the AVRCP version. I'm wondering if the Bluetooth HCI snoop log will provide any information?
Have any of you had any experience with this, or have anything to add to the conversation?
Many thanks in advance,
OK so it seems this codec list doesn't allow you to set a 'default', it just allows for modifying the codec during playback?
What I've experienced so far is that it does work with 'Use System Selection' to use the best codec available on the device you are connected to. It also allows you to change the codec to another while streaming/playing. The sub-text under Bluetooth Audio Codec does dynamically change from SBC to AAC.
Example: My headphones support SBC and AAC, the Pixel defaults to AAC on establishing a Bluetooth connection but does allow downgrading to SBC by picking from the list (as a test).
It however doesn't retain whatever you pick in the list if bluetooth is turned off then back on, it basically always defaults to system selection, then auto-picks on every connection. Perhaps this is by design, it is developer tools after all.
I haven't been able to get this to work with aptX in my car yet with my Pixel, even though it is apparently supported?
Also of note: To achieve AAC on my Bluetooth headphones I had to put them into a 'Priority on sound quality' mode and also turn off the Bluetooth phone (i.e. call connectivity, music ONLY) on the Pixel connection to achieve AAC.
are you sure that your car supports aptx? before this developer option it was very hard to actually see the codec being used.
I believe so, the Bluetooth product states that it supports EDR and aptX, but yes, I cannot be 100% certain.
Are you suggesting it should be possible with Pixel and the Oreo build as-is?
I've paired my pixel 2 with my uconnect system in my Jeep. Two issues, 1 the metadata (song titles and track info) doesn't show on the screen in my car. This worked fine on my last several phones. I've tried deleting and pairing again but it doesn't help. 2, the navigation directions from Google maps do not come through my car's speakers despite having that option checked in gmaps settings. Anyone having similar problems and figured out a fix? I'm on 8.1 Dev preview, and this also did not work on 8.0. I can't imagine that the phone isn't capable.
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
pabarker said:
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Terrible, hope they fix it soon. Thought maybe 8.1 would help but no luck.
I feel sorry for you guys. OG Pixel had bluetooth issues on some cars and some of those issues are still not fixed 1 year later.
Bluetooth is great for me on my cars. Both newer GM vehicles. One with Android Auto, one without.
I have an SRT Hellcat with UConnect. It completely does the same type of stuff. Sometimes it fails to transfer calls. It also shows "Pixel 2" often rather than song titles, etc. If I disconnect BLE and reconnect it usually works better the second time. It is annoying.
How do they screw this up every year. Using play music now completely locks up my uconnect RHR radio. I really wish Google would test things before rolling out. I wish they would just release there new phones on the previous Android version and have a beta of the current since they always screw something major up.
---------- Post added at 04:53 AM ---------- Previous post was at 04:17 AM ----------
I upgraded my uconnect from 2.600 to 2.700 and deleted the device pairing a couple of times and now I can at least play media again although I no longer have song data displaying which was there before at least before my radio would lock up.
I also tried changing the Bluetooth codec via developer settings to ACC. However, after changing, it reverts on its own. I read that the November security patch supposedly contains some BT fixes, fingers crossed!
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
fishsupreme said:
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
Click to expand...
Click to collapse
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
fishsupreme said:
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Click to expand...
Click to collapse
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Not just with vehicles
760hacker said:
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Click to expand...
Click to collapse
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
phonefreedom said:
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
Click to expand...
Click to collapse
This is similar to what I see, both with my new Pixel2 and also my previous OnePlus3 on my Mazda 3. Phone will pair, but after a few seconds (or sometimes minutes) disconnect. Usually it will try to reconnect, and then be fine until the next time I use my car. Both phones behave identically, so it seems to be more a problem with vehicle systems that some phones (none I've owned unfortunately!) are more forgiving of.
Anyone know of a fix for this? I'm using uconnect and same issue, however my maps navigation does play over Bluetooth. Sometimes it seems to disconnect or mute after songs change, and the metadata issue is there. Super annoying that we go backwards in technology. My HTC M9 does this stuff flawlessly.
So I did the developer preview thing and set it back to 1.3 which helps the metadata issue. However, the music still pauses every once in a while, mostly between songs. I have to click to my AM/FM radio and back to bluetooth to fix that.
Well, it's always the same circle. There's a new device with a brand new Android version. Of course buggy a.f. They fix it over the time. The device works perfect. And then... a new major upgrade, which is buggy again.
7.1.2 worked perfect on my Pixel. Then came 8.0.
Bluetooth was messed up again. Now i use the Pixel 2, which is a great phone. But still has the complete bandwidth of bugs that were present in 8.0 on the Pixel 1.
Nice to have monthly patches. But instead of fixing so called security issues, they should focus on functionality bug fixes instead. Who has had a major security issue with hs phone at all, yet??
Google is like: "Fix: Someone could attack your phone using a backdoor in your bluetooth driver."
WTF?!
I can't even use my bluetooth to listen to audio correctly! Fix that first!
Long story short:
Yes, I have the same issue with meta-data in my car audio (Pioneer AVH-X2800BT). Sometimes it works. Sometimes it doesn't.
Just got November security patch which is supposed to include Bluetooth fixes but hasn't changed anything.
Sent from my Pixel 2 using Tapatalk
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
scoliosis said:
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
Click to expand...
Click to collapse
AVRCP 1.3 wasn't available in stock 8.0 either -- I had to put the 8.1 Developer Preview on to unlock it.
What is your Uconnect firmware version?
> the metadata (song titles and track info) doesn't show on the screen in my car
Mine does unless I'm running Android Auto
Hello,
I have a simple case:
- I have PX5 radio in car
- and Huawei Mate 20 Lite as a phone
Both devices are paired with bluetooth.
Since PX5 radio is full Android device that can run Google Play apps itself.
I would like to use bluetooth only for calling and as trigger for Tasker(start WiFi hotspot).
But since it is possible my phone sends also multimedia sound(but it won't be played on radio, since specific app for A2DP is not working - and I'm fine with that), I would like my phone to simply play multimedia itself, not via bluetooth.
I know it is possible in vanilla Android(https://fscl01.fonpit.de/userfiles/6983662/image/androidpit-lollipop-bluetooth-forget-w628.jpg) but since Huawei has it's "awesome" custom settings menu it is not there, do You guys have any idea how to change that settings?
ADB or any application would be great.
I'm not interested about any solution with root.
Apparently there is small "i" button on the right of paired device in bluetooth settings - not that easy to click(because when I tried to hit it for a first time I couldn't hit it correctly - that why I created that topic) - where You can change what sound is passed via bluetooth.
Currently on Android 11 with Android Auto v 7.0.614134 and V4A v 2.7.1.6. When connected via bluetooth music is processed via V4A and sounds fantastic. When connected with Android Auto via USB, music does not get processed via V4A even though there is a USB setting in V4A. Music also does not get processed via the Speaker tab, which it defaults to when plugged in with Android Auto. I have researched this extensively and found it's a limitation for whatever reason. Also odd that I can't find any recent topics on it. The newest discussions are from 2019 to mid 2020.
I have tried disabling USB audio routing in Developer Settings to no avail. My solution is to use the EQ settings on Rocket Player to compensate, and it helps...but it's not the same as V4A.
However, I read somewhere that Android 12 "fixed" this issue. Or perhaps I misunderstood what I read. Any any case, can anyone on Android 12 using V4A and Android Auto confirm if audio is processed with V4A while connected to AA? FWIW, I have a PIxel 4a 5G and have been putting off the upgrade to 12 (hate setting up phones) but if A12 will "fix" this issue I will bite the bullet.
Thanks!