Database Users

Bluetooth Steering Wheel Remote Control. Warning!

I recently bought a bluetooth steering wheel remote control in hopes it would work with my android HU since my truck does not have steering wheel controls.
https://www.ebay.com/itm/Wireless-B...Control-Button-for-Android-AC908/263368511739
This particular BT Remote does not work with android HU's, my HU will not even recognize it. When I do a BT search it doesn't appear in the devices section. It connects to my phone and tablet easily, so that tells me that our android HUs are missing a BT profile that allow HID (human interface devices) to connect. Definitely not a limitation of android, the BT profiles were just left out. Unfortunitely I cannot root my Eonon with Android 7.1.2 to solve the problem.
I saw where Car Joying was selling a similar BT controller but it only works with Joying Launcher and a special BT App that I could not get to work on my Eonon.
So beware of these BT controllers for now, until either you can root your HU and install the BT HID profile or the manufactures start adding the profile into the ROMS.

I have the same problem. I ordered with this part directly in China. Can't get it connected to my Isudar radio (link in signature).
Okay, I got root on the device.
Do you have a tip or link what I need to do?

have you tried this app https://play.google.com/store/apps/details?id=com.brachcon.btautopair&hl=en ?
here https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249 gudsten wrote "Difficult to pair BT devices - Forces device pairing into database - Device pairs normally once HU thinks it has connected previously. I was able to pair TPMS, keyboard, etc using this method(s)."
maybe in combination with "Modified stock bluetooth app to allow connection to all devices" https://forum.xda-developers.com/showpost.php?p=71280945&postcount=88

Thanks for reply.
Okay i'll give it a try

i have the same bt remote steering wheel....has some user solved the problem? I have the PX5 (GS) with Oreo

tried a lot of BT app of Playstore but nothing ..the "X09" won't connect or is not recognized by the PX5... i'm very disappointed...i don't want install a control box wired to battery.

Chinese law is very different than western law, especially when it comes to goods for export.
They actively and aggressively engage in what western law calls "anti-competitive" practices.
They do this by intentionally disabling devices that are sourced from someone besides themselves, by intentionally mislabelling things, and doing their best to lock you out.

Joying Head Unit (4GB, PX5 Octa Core) - Bluetooth Tethering

Hi All,
Recently purchased and installed a Joying head unit (4GB, PX5 Octa Core) (link to product)
As this head unit runs android I am trying to tether the mobile data on my android mobile over to the head unit via the bluetooth tethering function. Problem is I dont think its working. Does anyone have any experience with this or know how to get it working?
Steps:
On the mobile, make sure its connected to mobile data
On mobile, turn on bluetooth tethering
Pair mobile and head unit via bluetooth
Still no internet access

Can you access data via hot spot? Make you mobile device a wifi hotspot and connect the headunit to your hotspot.
Sent from my ONEPLUS A5010 using Tapatalk

chper said:
Can you access data via hot spot? Make you mobile device a wifi hotspot and connect the headunit to your hotspot.
Click to expand...
Click to collapse
Yeah I tried this and it works fine. I just though it be better to use bluetooth tethering seeing as the phone is already hooked up to the head unit via bluetooth. Using the WiFi hot spot option just adds another process to the mix.
Because Joying remove a lot of the standard android setting I was thinking there might be a way to access the default android settings again to be able to play around with bluetooth properly. While writing this thread up however I did email Joying about the ability to bluetooth tether and their response was:
"Our head unit can not support Bluetooth tethering"

Hi, I am trying to achieve the same solution however I do not think it's possible. My understanding is that the bluetooth connectivity allowed by the hardware in the head units doesn't cater for the 'full stack' of bluetooth functions, so we're stuck with telephony and audio only with no data transfer.
I would *really* love to be corrected though! It would be great if it could be solved by software alone.
Failing that, could a bluetooth USB dongle work to provide full BT support?

proto__ said:
Hi, I am trying to achieve the same solution however I do not think it's possible. My understanding is that the bluetooth connectivity allowed by the hardware in the head units doesn't cater for the 'full stack' of bluetooth functions, so we're stuck with telephony and audio only with no data transfer.
I would *really* love to be corrected though! It would be great if it could be solved by software alone.
Failing that, could a bluetooth USB dongle work to provide full BT support?
Click to expand...
Click to collapse
I consider this a bug. It did work on the Sofia 3GR units on Android 6.0.1.
It (currently) does not work on the Android 8 PX5 FYT units (like the OP has as well). Can't say anything about the QD units.

Well that gives me some hope at least.
I did note at least 3 'Bluetooth' apps running on my device (that I've been playing with since my previous post).
Perhaps a custom mod may be the answer...

Sorry proto, I've had about five units and all the same. You're right and it sucks. I don't think it's a big as I've come across it many times and only in a few eBay postings did the seller actually specify it has a general bluetooth connection. Otherwise toy even have to buy their obd to get that to work
Sent from my SM-G950U using Tapatalk

Ok thanks for the replies. Hopefully it will be fixed with a firmware update in the future or something.

Is there are any news about this Bluetooth tethering?
I am really interested because my WiFi is really really slow...
I saw that some Bluetooth function are missing, like the possibility to remove paired device or select Bluetooth tethering.

It’s highly unlikely Joying will fix the Bluetooth, they would need to produce a seperate rom with normal BT configured and u would not have access to the Joying BT app.
Currently Joying route all Bluetooth communication via a service called btlink, from there it goes to the joying bluetooth app.
Joying have fundamentally changed the way the Bluetooth is configured so it functions with only their software.
All these headunit manufactures do this to the BT so it functions with their software and they never offer a fix

shanetrainST said:
It’s highly unlikely Joying will fix the Bluetooth, they would need to produce a seperate rom with normal BT configured and u would not have access to the Joying BT app.
Currently Joying route all Bluetooth communication via a service called btlink, from there it goes to the joying bluetooth app.
Joying have fundamentally changed the way the Bluetooth is configured so it functions with only their software.
All these headunit manufactures do this to the BT so it functions with their software and they never offer a fix
Click to expand...
Click to collapse
From which library/framework/binary/whatever is this btlink service started/called?

surfer63 said:
I consider this a bug. It did work on the Sofia 3GR units on Android 6.0.1.
It (currently) does not work on the Android 8 PX5 FYT units (like the OP has as well). Can't say anything about the QD units.
Click to expand...
Click to collapse
Remember that it only worked with a HACK. Joying intentionally disables this functionality.

Bluetooth information
Init.sy.rc
Service blink /vendor/bin/blink
Init.connectivity.rc
Chmod 0666 /dev/tty (This should be tty00)
Now I have modified mine but I think the system/vendor/ect/Bluetooth/bt_vendor.conf is set to
- UartPort = /dev/tty00
Blink is interacting with /dev/tty
Android system is interacting with /dev/tty00 ?
Hopefully all the information is correct as I have modified my unit lots to try give back the Bluetooth to the system and I didn’t keep many notes.
But in short the the system is trying to access the Bluetooth on the wrong Uart port, where as the blink is attaching to the tty device, allowing the joying software to work.
This prevent the android system & apps interacting with the Bluetooth.
Also this is the test app I have been using to try to get it to allow permissions to turn BT on, but it get denied every time
Bluetooth Discovery : Bluetooth LE Scanner
https://play.google.com/store/apps/details?id=com.manjul.bluetoothsdp

i have the 10.1 american version.
if i remember correctly, bluetooth has an issue when your using it as a "media" access point
i think the bluetooth is set for A2DP... probably physically somehow.

shanetrainST said:
Init.sy.rc
Service blink /vendor/bin/blink
Blink is interacting with /dev/tty
Android system is interacting with /dev/tty00 ?
Also this is the test app I have been using to try to get it to allow permissions to turn BT on, but it get denied every time
Bluetooth Discovery : Bluetooth LE Scanner
https://play.google.com/store/apps/details?id=com.manjul.bluetoothsdp
Click to expand...
Click to collapse
Did you try to create a symlink like
Code:
ln -s /dev/tty /dev/tty00
And is it indeed tty00 or tty0?
Did you give the scanner root access?

Bumping this for a slightly odder issue. I'm trying to connect my Joying stereo to a Hondata KPro ECU, it sees the ECU but refuses to link to it in settings, rendering apps like Hondata or RealDash useless, so in turn I'm using a crappy $20 tablet until someone can show how to fix this BT issue.
Joying was no help other than to tell me to buy their OBDII adapter, which I did, but LONG story this is a 2008 Honda engine in a 91 MR2 that has no OBDII port. I've bought an OBDII port off eBay and tried using pinouts from the ECU to hack together an OBDII port but no luck.
Having it via Bluetooth would be easier, it sees the KPro, so there must be a way.

same problem
dont buy this joying head unit
its rabish

I bought a Joying Px5 9inch Octa8, And i need some advise guys

a. I am a normal user, mainly need to use Bluetooth for phone calls, GPS maps and spotify. I realized that the caller apps does not allow me to put short cuts (quick dials) to my favorite numbers. Is there any way I can do it?
b. It is rather useless to have a headunit if there is no internet connection. I have my HP for WiFi tethering, and also a WiFi dongle. Both doesn't work well because the head-unit can only detect WiFi upon restarting the system. I am not sure why, If I were to shut off my engine, start it up again. The system will not be able to detect WiFi.
c. My head-unit comes with Zlink (apple car-play). Okay, this is funny. I connected my iPhone to the head-unit, but upon connecting to zlink, the Bluetooth connection is cut.
d. I intend to get the ELM327 so that I can see those cool gauges. But can the head unit support both ELM 327 and my iPhone Bluetooth simultaneously.
e. Lastly, do I really need to root it to get it perform? I am not good in all these.
For advice pls.
MCU: 2019-01-23

Can someone give me some advise pls

Hi Tweakmax,
i have the same version as you have. i bought mine from Isudar and is currently installed in my skoda.
A)I'm also not verry happy with the dialer app. First of all, the app is called bluetooth and has a bluetooth icon while it is a dialer. The contacts showed up after 2 hours!! The default launcher does not support custom widget elements such as a shortcut to person. I suggest installing an other launcher.
b) I'm not expierencing this problem.
C) My usb ports don't work. How did you manage to install car play? I have android Auto. By the way. Why do you want to use car play if you have an android head unit?
D) I can confirm that the ELM327 is working. Make sure to unpair the OBD2 dongle from your phone. Then unplug/plug the obd2 adapter.
E) root is not required. You can install other launchers and install APK's.

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

Android 10 Snapdragon 625 HU kswcarproject

Hi, does anyone know how to disable ksw Bluetooth? I can only add phone using their overlay tool, the android native built in Bluetooth is disabled and blocked by kswcarproject.
My goal is to add an Xbox gaming controller , I would rather use the native android Bluetooth settings if I can or unlock ksw BT to allow any device to connect to the HU. With ksw BT I have tried both pin code 0000 and 1234 without success, the error message I get is paring failed or rejected.
thanks !!

am I the only one having this issue to pair a non phone device to android Head unit ? There must be someone else who solved this.

I think it's more the opposite, all these headunits are crippled around the BT and only support phones and some OBD2 devices. Not sure anyone has a solution outside of totally custom firmware.
getting access to setting is not the issue, that's simple enough, it's that the BT is crippled at lower level.

gottahavit said:
I think it's more the opposite, all these headunits are crippled around the BT and only support phones and some OBD2 devices. Not sure anyone has a solution outside of totally custom firmware.
getting access to setting is not the issue, that's simple enough, it's that the BT is crippled at lower level.
Click to expand...
Click to collapse
here is what my tests show. If I restart the unit and quickly get into applications and terminate running applications kswcarproject and ksw BT, I get around 1 minute to enable Bluetooth in android and I can search for devices, I find my Bluetooth devices but somehow kswcarproject or any other service is deactivating native Bluetooth and I don’t have enough time to pair any unit. However this is evidence that the technology is capable, we just need to investigate how to disable services or whatever task that is forcing native bluetooth off after reboot. But I do not have knowledge in android infrastructure , but I can help in running tests and dig out logs

You can install default android settings or launchers like CarWebGuru or Nova give you these settings, there you get full BT settings, scan, probably even pair your device, but it won't connect and work. I found this on my IDoing UIS7862(FYT). BT is crippled. I believe they have done the same with 4g SIM connections.

It does work here is the evidence that it works:
And how to do it:
BMW 3-Series and 4-Series Forum (F30 / F32) | F30POST - View Single Post - 10.25" Android 10 HU discussion
Forum for BMW 1-Series 3-Series 5-Series 7-Series M3 M5 M6 Z4 X1 X3 X5 X6 Z2 Z4 325i 330i 335i 535i 550i 755i BMW Forums
f30.bimmerpost.com
Bluetooth is, yes, “crippled” after the device is completely booted up. So we just need to identify what service is blocking or crippling Bluetooth.

Hello guys,
I recently purchased a car that has the Qualcomm snapdragon 625 msm8953 NBT headunit for BMW 7 series (Native Android 10 unit).
I have tried everything to connect carplay but Zlink keeps saying waiting and won't take my iPhone.
I have read online that i need to update the firmware of the device, the version I have is KSW-Q-Userdebug_OS_v2.0.0.
Can someone please tell me where i can find the firmware update for free.
Thank you,