Database Users

Bluetooth Media Browsing notification (confused?!?)

I recently changed from stock TouchWiz (5.1.1) to an unnofficial load of Cyanogen 13. When I pair my phone to my car, it comes up with a notification titled
"Bluetooth Media Browsing"
with the contents of
"Peer supports advanced feature
Re-pair from peer to enable it"
I googled, and came up it nothing at all about this, which surprised me.
Does anyone have any idea what it means, and how I could pair differently than using the menu of my car stereo?

This showed up on my Nexus 6P today when I paired to my car's pioneer head unit. It got dismissed and I haven't gotten it to show again even after repairing it. Its the first time I've seen it and I'd love some info on this.

This happens in my HTC One M8 CM13 too, when i pair it with my car's audio system. Sadly the playback isn't working good...any solution?

Anyone find the result? I have a Pioneer head unit in my truck and noticed this on my nexus 6 running custom cyan rom.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Which Pioneer head unit do you have? I have the AVH-5700 unit and with my nexus 6 the bluetooth is really buggy.
hibby50 said:
This showed up on my Nexus 6P today when I paired to my car's pioneer head unit. It got dismissed and I haven't gotten it to show again even after repairing it. Its the first time I've seen it and I'd love some info on this.
Click to expand...
Click to collapse

Same message here to, no one knows what its for?

I've also seen this message on a CM13 build for the Note 4 Developer Edition. When I connect to the factory stereo in my car (BMW iDrive) for the first time, I get the message. If I tap it, nothing happens. If I swipe it away, I never see it again. I'm not sure if this is related, but I also have an issue where the phone will repeatedly ask if I want to give the iDrive system access to my messages every time I get in my car. If I wait through 5-10 notifications every 30 seconds, or if I open the notification and say "YES" or "NO" it will stop, until the next time I get in my car. It's annoying, because it will cause my audiobook app to pause and rewind 30sec due to the interruption, so I listen to the same part about 5 times before I'm able to continue.

Here's where the notification was introduced to Cyanogenmod,
https://github.com/CyanogenMod/andr...mmit/b753f101dcd965c9577271ad3a0583194d759947
Based on the commit message, it looks like the head units you guys (and I..) are trying to connect to report that they support AVRCP browsing, but the existing connection doesn't have it enabled. In the cars I've seen the notification in, I couldn't find any bluetooth settings to enable additional features, so I'm guessing it was never properly implemented on the head unit side (maybe the bluetooth chipset they're using supports it but they never wrote the user interface to enable and use the data).
Here's what the feature allows you to do: https://www.youtube.com/watch?v=YhjNE1ZrGNI
Not all that exciting, I can survive without it.

is this probem solved?

Eonon Android 5.1.1 bluetooth issues & canbus issues

hi guys
new to the forum, hopefully someone will be able to help me
my unit has stock MTCC-KLD6-V2.97 Aug 02 2016 with a RK3188 and 1024x600 screen
Firstly the Bluetooth is not working, quite a lot of apps hang at the part where it try's to turn the BT on, especially one app i really need to work.
I honestly don't know what model of BT chip is installed in the head unit, apparently its BT 4.0 as listed on there website
I have been into the factory menu and changed the BT from WQ_BC6 to WQ_BC6B (as suggested somewhere in this forum) but it has made no change and the BT is still hanging at powering on.
Eonon have told me that the Bluetooth only work with devices that don't require a pin and the radar detector device i need to connect does not require a pin but still it does not work.
Not quite sure if eonon has set the setting wrong and i need to change it or i need to goto a custom rom or I need to pull the unit apart to find out.
Found someone else having trouble getting there ALPconnect app to work aswell on these units, in know ALPconnect wont work on older unit like the 4.4.4 as they only had BT 2.0 and the ALP BT only supports 4.0, but this android unit has 4.0 so it should not be a problem but it is.
sterod said:
The app I use, ALPConnect, does the exact same thing. Fortunately, the hardware on mine includes a hardwired speaker and GPS setup that work standalone. The benefit of the app was to get a nice big visual notification of a trap, as it would come into focus, duck the audio and play an alarm. It would also report the frequency of the radar and the type of laser hitting me. While I can get by without all that, I can't have the music blaring like I usually do, as the little speaker is only so loud and the Joying head unit doesn't have Mute Input wire to duck the audio.
While this is going slightly off topic, you may want to look into the AL Priority, it can interface with your V1 too and you will also gain laser protection. This thing has saved my a** countless times and paid for itself already many times over.
Click to expand...
Click to collapse
Secondly the control menu in the android head unit for accessing the cars buttons via cambus does not work, all steering wheels button seem to communicate back and work, but i cannot set my clock on my mazda 3.
Also have noticed that the radio wont mute when notification occur or when using other apps like google maps, no way to set the different volumes in this stock rom. Have played around with the factory menu volumes but it makes no diffidence.
Is it viable and worth changing to a different ROM, like Malaysk? or should i message eonon?
any help would be much appreciated
thanks
shane

I'm having exactly the same issue with a Pumpkin MTCC-KLD6-V2.91. (RK3188/1024x600)
The device I want to pair with appears in Bluetooth settings (with a phone icon?) but connecting to it does nothing. It's just a Bluetooth SPP device, like so many other devices.
Malaysk's ROM (from 7/25) doesn't change anything here.
Any suggestions would be most welcome.
-Zandr

zandrm said:
I'm having exactly the same issue with a Pumpkin MTCC-KLD6-V2.91. (RK3188/1024x600)
The device I want to pair with appears in Bluetooth settings (with a phone icon?) but connecting to it does nothing. It's just a Bluetooth SPP device, like so many other devices.
Malaysk's ROM (from 7/25) doesn't change anything here.
Any suggestions would be most welcome.
-Zandr
Click to expand...
Click to collapse
Waiting on a reply from Eonon, but initial news is not good.
Some serious BT issues in this model the MTCC
Anyone know if any Malaysk's Rom's avalable for the MTCC-KLD6-V2.91 that have no BT issues

I'm having the same issue, though my unit (MTCC KLD6) does not show any devices at all to pair with, and the car unit does not appear on my phone.
I'm wondering - if I take a usb BT dongle and attach it to the usb cable, would that work?

I think it might be another issue with your BT, it should connect to your phone at very least.
Have you had a look in your factory menu to see if the MCU has the Bluetooth option set?
Password for me was 126
Unfortunately the unit does not support external USB Bluetooth and probably never will, unless the manufacturer MTC/Klyde adds the required drivers to the unit or a Awesome developer by some stroke of luck here adds it to the unit. I doubt to see the feature in this unit
Sent from my iPhone using Tapatalk

Thanks for the reply. Yes, i checked to make sure Bluetooth was enabled in the system settings. I've tried a few of them (change setting, reboot, attempt pairing), i guess the next step is to try them all one by one to rule that out. I've sent an email to the seller to see if they have any ideas.

The vendor told me to connect the Key-1 & Key-2 wires from the canbus to the car, not sure why they'd think that would solve BT issues?

Did this fix the issue? I'm unable to see any Bluetooth devices and other Bluetooth devices don't see it.

Sorry to dig up an old thread
I have the Eonon GA2180a (android 10) - and having similar issues to here
I want to pair a bluetooth remote (read, steering wheel controls) to the head unit, but the bluetooth search just shows blank! I can connect to it using my phone but it appears some things are hidden to connect to with these android units? Looks like the bluetooth 'app' is the only way to connect too, theres nothing in the android settings to access a bluetooth menu or anything.
Did anyone get anywhere with this ?
cheers

Eonon GA6150 BlueTooth question

Hello xda people!
I recently purchased an eonon head unit for my E46 316i from ebay. Specifically a GA6150 (rk3188), which was sold together with a reverse camera.
I am really happy with my order, and pleased with the HU's performance. I managed to connect succesfully my OBD adapter, my bluetooth phone and my wifi hotspot and all is working great.!
Although, I found out something which bothers me. I have purchased a Bluetooth RGB LED controller from ebay, in order to DIY install some LEDs in the interior of the car, and I wanted to control them from my eonon android HU. I can control them through my S7 Edge Android phone via the app called Happy Lighting. I have found out that the manufacturer of these controllers is called Triones. So my problem is, that when I open the app, it asks me to turn on the bluetooth, and allows me to press one of two buttons, allow and deny. If I press allow, a message will appear saying: "Turning on Bluetooth" or something like that, with a spinning wheel, indefinately. It will not stop and it will stay like this all the time, making the app useless, making me press home button to exit. All this happens, even though I know that bluetooth is actually on (I havent yet found an on/off switch for Bluetooth, so I suppose it is always on). If I press deny, then I can enter the app, but I am not able to see any of the bluetooth controllers, is there any way, to make the app think that the bluetooth is on? Or actually turn it off or anything? Would you please help me figure out what should I do? And one last question, is how can I change my screen orientation from landscape to portrait?
I will attach a photo of the details for the version of my Head Unit.
This is the link of the HU I purchased from ebay: http://r.ebay.com/aegMSa
And this is the link to the controller: http://r.ebay.com/aDfflI
While this is the app: https://play.google.com/store/apps/details?id=com.qh.Happylightgoogle&hl=en
Thank you very mych for your time!

Yep had 3 Paypal disputes with Eonon about that issue a year ago on a MTCB unit, I would imagine it would be the same with the MTCD
I think they route all Bluetooth information through the MCU and use non standard configuration of their Bluetooth drivers. So applications that ask to turn the BT on cannot as it is not configured that way.
This is something they were not willing to fix or were unable to.
Sent from my iPhone using Tapatalk

First of all thank you for your reply, i really appreciate it.!
Second, damn it. Damn them! That is really frustrating, i've managed to find a bit more info digging around here and in russian forums. It's sad that i cannot use anything else via bluetooth other than a few OBD adapters and my phone..
I will shortly contact Eonon for my MCU update file and see if anything can be done there. Otherwise, i will see if anything can be fixed via a custom rom and xposed stuff.
P.S.: If there was any other android HU that could support full BT, i would gladly return my Eonon and buy that instead..

DeejayTelis said:
First of all thank you for your reply, i really appreciate it.!
Second, damn it. Damn them! That is really frustrating, i've managed to find a bit more info digging around here and in russian forums. It's sad that i cannot use anything else via bluetooth other than a few OBD adapters and my phone..
I will shortly contact Eonon for my MCU update file and see if anything can be done there. Otherwise, i will see if anything can be fixed via a custom rom and xposed stuff.
P.S.: If there was any other android HU that could support full BT, i would gladly return my Eonon and buy that instead..
Click to expand...
Click to collapse
Joying intel Sofia units is a bit better with the BT, but do some research first.
Good luck with Eonon
From memory it to do with kernel drivers and BT stack and they would not fix
Also be careful with Eonon and returns, additionally PayPal protection does not cover car audio products.
Sent from my iPhone using Tapatalk

shanetrainST said:
Joying intel Sofia units is a bit better with the BT, but do some research first.
Good luck with Eonon
From memory it to do with kernel drivers and BT stack and they would not fix
Also be careful with Eonon and returns, additionally PayPal protection does not cover car audio products.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Digging up an old thread
I would like to connect bluetooth accessories to my eonon new android 10 head unit (2020) - the above looks familiar as i cannot seem to 'find' the devices when searched for using the strange bluetooth 'app'.
Is there anything that can be done? I'd like to add a bluetooth remote (alternatiev to steering wheel controls) - but its not detected by the HU

Android Auto not coming up on 2020 Subaru Outback

Hi.
Just got a 2020 Subaru Outback. When I connect my Essential with USB cable, nothing happens (other than charging). Works fine on my wife's '19 Nissan Rogue.
Also connected my wife's Samsung Galaxy S8 to Subaru, no problems - Android Auto popped up right-a-way.
Any '20 Subaru Outback, Legacy owners here?
Thanks

This should probably be under Question Answers.

>Nothing happens other than charging
Have you looked under your notifications to see if the USB options are set to charging only? I've never used Android Auto but I know I have to set it to File Transfer every time I plug my phones into my computer, otherwise it only charges.

I had the same issue, but by connecting a unpowered USB hub it should work. I know it sounds stupid, but give it a try.

@levpri I've got a Crosstrek and I was having similar issues. When I got the car I'd found a thread that mentioned a bunch of working and not working USB A to C cables. I ended up getting a couple of these cables and I've not had a problem since.
Amazon Anker Cable

Anker cable. Plug into car first, then phone.

Did you get it going?
I use AA on my outback /18 without issues got a new phone that was on android 10 now my AA not longer works, it connects I get my maps but it won't take any voice commands from the steering wheel.
not sure if it's my LG phone or that it's because it's on Android 10 I may try my old samsung phone set it back up tomorrow just to test.
levpri said:
Hi.
Just got a 2020 Subaru Outback. When I connect my Essential with USB cable, nothing happens (other than charging). Works fine on my wife's '19 Nissan Rogue.
Also connected my wife's Samsung Galaxy S8 to Subaru, no problems - Android Auto popped up right-a-way.
Any '20 Subaru Outback, Legacy owners here?
Thanks
Click to expand...
Click to collapse

Android Auto not functioning with Android 10
levpri said:
Hi.
Just got a 2020 Subaru Outback. When I connect my Essential with USB cable, nothing happens (other than charging). Works fine on my wife's '19 Nissan Rogue.
Also connected my wife's Samsung Galaxy S8 to Subaru, no problems - Android Auto popped up right-a-way.
Any '20 Subaru Outback, Legacy owners here?
Thanks
Click to expand...
Click to collapse
I'm having the same issue. I have a new Subaru Outback 2020. My Samsung S8 connected with AA with no problems. I just got a new Samsung Note 20 5G, running Android 10. Now Android Auto is not launching the map. I get voice driving instructions but no map. I see on my phone, a notification saying the phone is connecting to AA, but it eventually goes away and still no map showing on the head unit. I've tried several different USB-C to USB-A cables and none of them help with this issue. Google markets they've improved AA access by combining it with the Android operating system. Unfortunately, they don't seem to have done sufficient testing with this change. Typical of software giants sending out updates without full testing and ensuring it's functional.
GOOGLE: Get your act together! This is a serious issue. AA is supposed to aid drivers and the map on the head unit stops individuals looking at their phone. Well, you've just increased the chance of a crash now. It won't surprise me if GOOGLE gets sued for someone's death.
If anyone finds an update or resolution to this problem, PLEASE post the fix!!!
PS: We should not have to go through this ridiculous back and forth just to link Android Auto from our phone to our car. This is the 21st century, is it not? We send people to the moon, have smart(?) applicances, and even self-driving cars. Surely, we should be able to get a simple mapping system to show up on a car head unit!

Have you gone into your Android auto settings by any chance? It's an integrated app now so there's no icon for it in Android 10 (depending on phone).
You should be able to easily find it by using the search bar in the app drawer on a Samsung and it will find it in settings. Search key words "Android Auto".
I have both an Essential and Samsung Note9. My Essential phone still has the actual app on stock. I have had more trouble with Essential connecting to AA.
If you haven't tried anything in settings, you could look there and forget all cars to clean it up and start fresh. You could enable developer settings similar to actual Android and try things in those settings. You'll be able to change/set:
> Application Mode (Developer gives AA Server)
>Add wireless projection to settings
>Clear all data
>Unknown Sources
>Debug options
>Video Resolution
>And more...
Might have to experiment. Good luck!

levpri said:
Hi.
Just got a 2020 Subaru Outback. When I connect my Essential with USB cable, nothing happens (other than charging). Works fine on my wife's '19 Nissan Rogue.
Also connected my wife's Samsung Galaxy S8 to Subaru, no problems - Android Auto popped up right-a-way.
Any '20 Subaru Outback, Legacy owners here?
Thanks
Click to expand...
Click to collapse
I started receiving the same "Launching error.. check clock or upgrade google play services" error all of a sudden while I was on a road trip on 2020 subaru outback.
I noticed the time in the display console was off by 1hr so it was definitely some clock issue so I manually tried to set it but still the android auto won't connect. I figured there was some Subaru software issue because when setting the daylight saving to AUTO it was not sowing the correct info, while previously there was no issue with AUTO settings.
Then I tried my wife's phone and same issue.
I tried different cables and same issue.
I tried factory reset of subaru console from settings but still the same issue.
Then I came across some other post and tried the android auto phone app downgrade approach but it didn't work either. With lower phone app version it was not supported to connect to the subaru outback so the phone app forced me to download and install updates again. And then the same issue.
Finally, I went to the service center and asked them to look into this. They checked and fixed the issue in 3-4 hrs. They verbally told me that they updated the head unit and that fixed the issue. And then in the inspection report they had exactly mentioned as below:
"Performed inspection of vehicle and was able to verify customer concern of vehicle not being able to access android auto or apple car play, found TSB 15-261-20R which has an available update for the stereo head unit. Will perform update to make sure latest software is installed. Apple car play is now working. Old software version was F11GHM042-380 new software version is F11GHM072-582"
This is as of 17th Dec 2021. Since then the android auto is working fine.
I am sharing this post so that in case nothing works for you, try showing this message to subaru service center guys to help you fix the issue.
Hope this helps!

AUTOPUMPKIN AA0495B issues with some bluetooth devices

NOTE: I tried to post a fully detailed write-up of my issues, with screenshots and links, but because I'm a new member the forum won't let me post this with those URL's in the post. Since there's no way to upload and attach images, I'm happy to provide all of this via alternative means, or update the post with the original links if an admin is willing to remove this restriction from my account (I promise I'm not a spammer of any kind)
Hi all,
First time poster here with some unique issues (at least for me) with one of the newer Android stereo units. (AA0495B)
I've already contacted AUTOPUMPKIN customer support and they were absolutely no help in solving this; I've also done my own testing and tinkering but haven't been able to get anything working so I'm hoping someone here with more knowledge of these Android units can help.
Late last year I got an AUTOPUMPKIN Android 9.0 unit (AA0495B) for my track car; the main reason I got it was to run my track timer apps directly from my car instead of having to run it from my phone in a dash mount as most do; the specific app I use is Harry's Laptimer. Now obviously this app was programmed with phone use in mind, but after a bit of doing I was able to get it working completely on the Android stereo unit, so my questions aren't around that app, but rather some secondary hardware related issues using the unit. Overall this stereo unit has been great and free of any major issues like ones I've seen on other XDA posts about other Android stereo units. The app works, connects to my GoPro over WiFi flawlessly, and records track sessions and syncs to video perfectly. My issue is that the HLT app also supports connecting to other kinds of devices via bluetooth for additional data capture, such as the XGPS160 for obtaining more accurate GPS lap data (The 160 captures GPS coordinates at 10Hz rather than the 1Hz of the AA0495B and most Android phones) and I'm having issues getting the stereo unit to connect to the XGPS160 device.
There are several problems in getting this to work, but to keep things simple I'll start with the first problem and then work down layer by layer as each issues is solved; hopefully, if we can get it to work, this thread can serve as a guide for others to get this stereo unit to connect to this and other GPS devices.
PROBLEM #1 - Getting the AA0495B unit to pair and connect to the XGPS160 over bluetooth
So obviously the first step is to get the XGPS160 connected to the head unit over BT. The instructions for this are fairly straightforward and in the XGPS160 manual which I followed. The AA0495B unit has its own custom UI for managing connections to bluetooth devices rather than using the native OS bluetooth menu. The native OS bluetooth menu can be found in the system menu, however when attempting to use it to pair to devices, no devices are detected. If we instead use the main menu Bluetooth button to open the custom BT interface and then hit the search button to scan for devices, the XGPS160 shows up when ready for pairing, so we know the BT radio is picking it up at least. I then click on the name of XGPS160 and press the Connect button to pair the device. After a few moments, the device name now shows as an "available device" meaning it is paired to the unit (at least in theory). We can then click on the name and click the Connect button again to attempt to connect the device. This is where it stops, as it never shows as being connected. For comparison, the UI does show blue "connected" icons when the stereo is connected to my Galaxy S9. It appears this custom BT UI will only show the blue symbols when the connected device is a phone; I also have an OBDII dongle paired and it will never show as connected from this screen, however apps like Torque Pro are able to make the stereo unit connect to it and pull OBD data from the car. I was hoping that maybe this was a case of this custom UI simply not showing that the device was connected when it actually is, like the OBDII device. I attempted to run the "Bluetooth GPS" helper app to see if I could get it to connect; however the XGPS160 doesn't even show up in the list of available devices, whereas the "OBDII" dongle is listed even though it's not currently connected. Presumably this menu is pulled from the OS's list of paired devices, so if I had to guess, perhaps the XGPS160 isn't really paired even though the Pumpkin custom BT UI shows it as paired?
In contrast, I was able to connect the XGPS160 to my Galaxy S9, update its firmware via the phone app, and install and run the helper apps to pull data from it, so there aren't any problems in the device itself, but appears to be an issue with the stereo unit.
Here are the About Machine details from the unit for reference:
Builder Number: 201907091031
Kernel Version:
4.4.167
#44 Mon 07 1 10:07:31 CST 2019
uboot-06 28 2019-18:00:06_M11 1024x600
MCU Version: CSN2_06252019_163051
CPU and Memory size:
64-bit 8-core Cortex-A53 1.5GHz
4GB TC:29C TGT:29C F0:1200M F1:816M
Model & Hardware: PX5
Android Version: 9
So with all that, does anyone have recommendations on next steps? I'm a software engineer by background (though not in smart devices) so I shouldn't have trouble performing any troubleshooting steps necessary.
thanks!

Figured out the issue
Circling back to update this one for anyone else who comes across this issue. Here's the response I got from Autopumpkin support
"After checked with our engineer,sorry to tell you that our headunit cannot connect to SkyPro XGPS160.the reason is car stereo Bluetooth is equivalent to a Bluetooth headset and it can only be connected passively.sorry about this."
So yeh, seems they cheaped out on the bluetooth module and that's the problem. Now if only I could find a way to disable it and use a USB bluetooth dongle I have instead.

I also have the problem with a Kingbaets K1+ Android 8.1
Unfortunately, it is only possible to establish the Bluetooth connections up to Android 6.0.
Later Android versions have a "castrated" Bluetooth interface.
My consequence was that I bought an OWNICE C500+ with Android 6.0.
With this device, Bluetooth hardware can pair with PIN input.
It works perfectly.
Dealers at aliexpress