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.
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
New to forum, as well as new to the Android, Android Auto head units
I am looking for a better understanding of what's needed exactly to display the 'Torque Pro' app directly to a 'Head' unit without passing through a third device
I have the scanner port device
I have the 'Torque Pro' app running on the s9+ mobile device
Goal is to have the app running on a head unit minus the s9+
I have been reading, researching
Down to a Sony Android Auto unit
Or
Joying head unit that uses a sim card?
I am also concerned about quality of music playback, radio and FLAC files
Many thanks for your thoughts
To have OBD directly your only option is an Android based unit like the Joying. Android Auto just mirrors certain apps from your phone.
You'll need an OBD2 dongle. Just install Torque on the head unit and link it with the dongle same as you would with an Android phone.
Sent from my SM-T550 using Tapatalk
Would this obd2 dongle be a USB, Bluetooth or WiFi connection?
I'd still want to be able to connect to phone to the head unit for calls etc. But for the torque Pro to work without the phone.
[email protected] said:
Would this obd2 dongle be a USB, Bluetooth or WiFi connection?
I'd still want to be able to connect to phone to the head unit for calls etc. But for the torque Pro to work without the phone.
Click to expand...
Click to collapse
Yes, Bluetooth connection from head unit to OBD II adapter. You can have multiple Bluetooth connections so your Anroid head unit will be connected to your phone for voice and media and the OBD II adapter for data.
So several years ago I did a custom install on my 500 Abarth for an Ownice C500. I was happy with the sound and display clarity, but it hasn't aged well.
I need to find a replacement for it.
Problems it has:
1) GPS wanders and dances all over the place. Can no longer lock. I have changed the GPS dongle but it doesn't work.
2) Audio has developed a background whine.
3) It reboots randomly while driving. Didn't used to do this.
In my other car, I have a Joying unit that is mostly good but has its own issues.
REQUIREMENT 1: (non negotiable) is any replacement must have full OBD2 support, including support for a high rate OBD2 dongle such as the OBDLink MX/LX. Unfortunately the Joying devices won't work with these dongles because they use newer security than the older Chinese units. I have also experienced that even with the cheap Chinese OBD2 plugs you can get for $20, they don't connect consistently. This is the primary holdup for me upgrading, I don't want to waste my money on a unit that won't let me properly use Torque Pro.
REQUIREMENT 2: Must be able to have a proper AV-IN that allows me to switch to my car's bluetooth module for calls and bypass the radio completely other than speaker output. The Ownice C500 does this fine, but the Joying in my other car does not.
REQUIREMENT 3: No 800x600 units, needs to have a resolution that works properly with modern Android software.
Built-in Dashcam like the Joying is preferable.
Any suggestions?
Hi, you got your player ? also looking for player got full obd2 support.
efan94 said:
Hi, you got your player ? also looking for player got full obd2 support.
Click to expand...
Click to collapse
Obd2 support depends on the adapter and application, not the headunit.
marchnz said:
Obd2 support depends on the adapter and application, not the headunit.
Click to expand...
Click to collapse
I afraid not that what happening to my case. My headunit wont connect to my obd2 but all my phones, tablets just work fine with the obd2 ?
I have the above head unit fitted and working fine in my car but I have an engine management device that contains a bluetooth low energy module in it. I would like to connect to this module via the provided app however it appears my head unit does not see or connect to BLE devices.
Does anybody know of a USB type device that I can connect to the head unit which will provide the ability to connect to BLE devices?
I'm using standard Dasaita android 10 and 3.69C.
Thanks
I have a similar issue. I have an Axxess signal processor which you make adjustments to it through Bluetooth. The processor connects to my phone but won't even be seen by my head unit (Dasaita max10). These head units only seem to recognize a phone or (select) obd dongles. It's pretty basic. I have been looking for ways to expand this, but so far unsuccessful.