Hey,
I'm struggling for a few days with my Joying Headunit. It is an SC9853i with 4GB/64GB (1280*720 EU-JY-UO134N4GS-H).
The MCU is 2019.09.09 11:04:47 JY_53_C63L_G23P48F64_Ver:1.0
I googled for the last 2 days and couldn't find a solution.
I'm trying to use Torque pro with a Carista OBD2 adapter.
Every time I try to pair the HU and the adapter the pin prompt won't appear.
It tries to pair but after a while it will just fail.
The Pin of the adapter is 0000. I tried setting the pin in the Bluetooth app to 0000 and 1234 but nothing changed.
In the android Bluetooth app the adapter doesn't even show up.
Before I used another OBD2 adapter and it paired just fine. Except that I couldn't use custom PID's in Torque pro.
This should be because of the old Adapter, so I changed to the Carista OBD2.
Here is a video to show the problem.
(Can't post it because I'm new here. I hope you understand my problem anyway.)
The HU is atm unrooted.
What are my options?
Thank you for your help.
Greetings
Philipp
I have the same problem with the same unit. Did you resolve this ?
How are you pairing the adapter? Joying seem to have hidden the Bluetooth menu in Android. I can actually pair my generic ELM372 one with Torque Pro, and it shows connection to the adapter but no connection go the ECU (not entirely sure what an ECU is)
By default joying software will only allow connecting to obd devices with either "obd" or "gooddriver" in its name. What does your adapter identify itself as when you try to pair to it?
Yes only cheap Noname Chinese elm clones work.
I had to purchase a USB connected OBD reader because of this restriction :-(
So, the Bluetooth function in Android Headunits act differently than an Android tablet would, for one, it's a handsfree receiver that does not allow (correct me if I'm wrong) uplink with another device.
I have a DSP amp combo that uses BT to connect to an Android phone/tablet, which works fine, but my Dasaita PX5 won't connect to it. It just sees it, pairs, but doesn't connect.
Is there any way I can use a generic Bluetooth USB dongle to connect to it instead? Or is there any other way to allow connection with other BT devices (I have no luck in connecting OBD dongles too, BT or Wi-FI).
Thanks.
The device isn't an MTCB, being a dasiata it's likely an MTCD.
The answer to the BT question is no, you can thank the developer of the device for the hacked BT implementation.
Requesting mod moves to MTCD general.
Cheers! I've been out of touch for a bit and completely forgotten about the MTCx denominatin,
Thanks.
marchnz said:
The device isn't an MTCB, being a dasiata it's likely an MTCD.
The answer to the BT question is no, you can thank the developer of the device for the hacked BT implementation.
Requesting mod moves to MTCD general.
Click to expand...
Click to collapse
So just to be clear before I go down this path, there is NO external USB bluetooth module that will work with an MTCE head unit? Even if the USB module somehow uses the driver/firmware in the factory settings dropdown?
My Navifly 7862 is having issues with wifi and bluetooth. I am able to connect wifi on the unit to my phone hotspot, but when I try to connect it to the wifi on my Blackvue Dashcam, it connects, but once connected shows an X in the wifi symbol (see picture) and the Blackvue software cannot communicate with the dashcam.
For bluuetooth, it seems to work if I connect my phone to the device, but if I want to connect it to the OBDLink OBD2 reader in my car, it fails. I can search for the OBDLink in the Bluetooth app on the headunit, and select it and click connect, but nothing seems to happen. in addition if I go into the OBDLink software, and try to connect, it says the device is not paired with any OBD readers. I found a video on youtube that says I should use an app call "Bluetooth Pair" to pair the device with the OBD reader, but this also does nothing
Any advice that gets wifi and bluetooth working as I want would be really appreciated, as connecting to webcams and OBD reader are 2 of the main reasons I got this device
The "x" in the wifi means it's not getting internet. This happens when tethered to my phone and theres' no cell coverages. I have noticed that when this happens it does try to connect to other wifi until internet returns. Perhaps that is causing your communication with your dashcam. bring up the wifi settings window and leave it up when you connect, see if it's toggling.
Bluetooth device issues abound with these things, it's well documented here, I am not surprised.
as cool as these things are, there is some very "janky" code in there.
Does your Blackvue have LTE?
I'm using my 7862 and a black use 750X PLUS with LTE connectivity module and it works quite well. Since both headunit and dashcam have LTE I normally doesn't connect HU and cam through wifi -I prefer using blackvue's sky function so I get notifications on my phone.
When I tried the wifi connection I did have some problems but I fixed that by enabling a developer setting to keep mobile data on while connected through wifi.
Sadly the 7862 BT is limited to headset mode (used to connect with phones) + Chinese elm OBD clones. So BT doesn't work with "real brand" OBD dongles like scanmaster. So if Noname elm clones doesn't work for you I recommend a USB obd dongle.
Allan_Hun said:
Does your Blackvue have LTE?
I'm using my 7862 and a black use 750X PLUS with LTE connectivity module and it works quite well. Since both headunit and dashcam have LTE I normally doesn't connect HU and cam through wifi -I prefer using blackvue's sky function so I get notifications on my phone.
When I tried the wifi connection I did have some problems but I fixed that by enabling a developer setting to keep mobile data on while connected through wifi.
Sadly the 7862 BT is limited to headset mode (used to connect with phones) + Chinese elm OBD clones. So BT doesn't work with "real brand" OBD dongles like scanmaster. So if Noname elm clones doesn't work for you I recommend a USB obd dongle.
Click to expand...
Click to collapse
I am trying to connect with an OBD2 on my navifly 7862 and it is not working. Does anybody found a way to fix it?
Allan_Hun said:
Does your Blackvue have LTE?
I'm using my 7862 and a black use 750X PLUS with LTE connectivity module and it works quite well. Since both headunit and dashcam have LTE I normally doesn't connect HU and cam through wifi -I prefer using blackvue's sky function so I get notifications on my phone.
When I tried the wifi connection I did have some problems but I fixed that by enabling a developer setting to keep mobile data on while connected through wifi.
Sadly the 7862 BT is limited to headset mode (used to connect with phones) + Chinese elm OBD clones. So BT doesn't work with "real brand" OBD dongles like scanmaster. So if Noname elm clones doesn't work for you I recommend a USB obd dongle.
Click to expand...
Click to collapse
No it doesnt
uberNoobZA said:
No it doesnt
Click to expand...
Click to collapse
No, it doesn't ??
That's a strange answer to Allan_Huds explanation. It is eacatly as he describes: only phone, ELM OBD dongles and selected FYT allowed Chinese TPMS systems,
Did you search this forum? There are several ways described in this forum to connect an OBD BT dongle, and if you are unlucky it will still not connect.
I will not simply repeat here again what is written in those posts (also some of my FAQ/Q&A posts).
surfer63 said:
No, it doesn't ??
That's a strange answer to Allan_Huds explanation. It is eacatly as he describes: only phone, ELM OBD dongles and selected FYT allowed Chinese TPMS systems,
Did you search this forum? There are several ways described in this forum to connect an OBD BT dongle, and if you are unlucky it will still not connect.
I will not simply repeat here again what is written in those posts (also some of my FAQ/Q&A posts).
Click to expand...
Click to collapse
I think it's a perfectly good (yet brief) reply. The post started with "Does your Blackvue have LTE?". I replied "No it doesn't".
Yes, I did search the forums, and there wasn't an answer that really assisted me with my issues, which is why I posted.
For some reason I didn't get a notification then Allan_Hun replied, and only got a notification today when Matheus Sampaio replied, which is why I only replied now.
I got rid of the Navifly ages ago, but I did get a cheap as chips Chinese OBD reader, and that also failed to work. Even if it had worked I would have gotten rid of the Navifly anyway as the main intended use for it was to connect to my BlackVue, and for some reason the option to stay connected to LTE when on wifi wasn't present on the Navifly (I had already looked before Allan_Hun replied, because I am well aware of this option - I use the exact same thing on my phone when I use my phone with my drone, as phone to drone connection is over wifi, and the drone software needs internet connection to show google maps when flying the drone)
Matheus Sampaio said:
I am trying to connect with an OBD2 on my navifly 7862 and it is not working. Does anybody found a way to fix it?
Click to expand...
Click to collapse
As Allan_Hun suggested, if it doesn't work over Bluetooth, try USB with something like this - https://www.ebay.co.uk/itm/334396331224
Matheus Sampaio said:
I am trying to connect with an OBD2 on my navifly 7862 and it is not working. Does anybody found a way to fix it?
Click to expand...
Click to collapse
Use a genuine OBDLink SX (USB) for lightening fast connectivity. If you really want to use Bluetooth, use a genuine OBDlink LX.
Avoid all cheap Chinese knockoffs.
marchnz said:
Use a genuine OBDLink SX (USB) for lightening fast connectivity. If you really want to use Bluetooth, use a genuine OBDlink LX.
Avoid all cheap Chinese knockoffs.
Click to expand...
Click to collapse
I was using a genuine OBDLink LX and it didn't work with the Navifly. This had nothing to do with the OBD reader (proven by it not working with a cheap chinese OBD reader either) it's plan and simple down to the crap hardware they include in the Android units. No idea what Matheus is using but if using a cheap chinese OBD reader with the Navifly and it doesn;t work, I wouldn't go out and buy an expensive device like a genuine OBDLink, as it most likely won;t work either due to the crap bluetooth on the Android units. More chance using USB OBD reader
I am trying to use with a Vlinker MC+ and the Bluetooth find it but don't connect. Maybe the USB would be better, but how do I know if it will really work? I will look for some that has been already confirmed
uberNoobZA said:
I was using a genuine OBDLink LX and it didn't work with the Navifly. This had nothing to do with the OBD reader (proven by it not working with a cheap chinese OBD reader either) it's plan and simple down to the crap hardware they include in the Android units. No idea what Matheus is using but if using a cheap chinese OBD reader with the Navifly and it doesn;t work, I wouldn't go out and buy an expensive device like a genuine OBDLink, as it most likely won;t work either due to the crap bluetooth on the Android units. More chance using USB OBD reader
Click to expand...
Click to collapse
My units is FYT 116 (mekede 700) Android 10. Before that was MTCD PX5 MCU=HA.
In both units the OBDLink SX and LX works. These are NOT expensive- the chinese OBD units are garbage.
marchnz said:
My units is FYT 116 (mekede 700) Android 10. Before that was MTCD PX5 MCU=HA.
In both units the OBDLink SX and LX works. These are NOT expensive- the chinese OBD units are garbage.
Click to expand...
Click to collapse
I have no idea of those units you mentioned and whether they use same hardware / Android build as the Navifly 7862, but this particular thread is specific to the Navifly 7862. You may have a different idea of what 'expensive' is, it's all subjective to how much it costs to et these devices where you are. I do agree 500% that the chinese models are garbage
uberNoobZA said:
I have no idea of those units you mentioned and whether they use same hardware / Android build as the Navifly 7862, but this particular thread is specific to the Navifly 7862. You may have a different idea of what 'expensive' is, it's all subjective to how much it costs to et these devices where you are. I do agree 500% that the chinese models are garbage
Click to expand...
Click to collapse
You don't know which type of FYT unit you own?!
Once again - Navifly are not a manufacturer, neither is Mekede - they are a "made up" reseller of FYT based units.
What matters is the FYT type number, this number indicates the FACTORY / manufacturer.
Saying "My Navifly doesn't connect to a real OBD BT device" means very little when you don't know what you own nor does anyone know what you've done to the head unit, such as misconfiguration due to misunderstanding, or investigating the issue.
FYI - Mekede and Navifly sell various FYT units, typically Type 116 - details are important.
marchnz said:
You don't know which type of FYT unit you own?!
Once again - Navifly are not a manufacturer, neither is Mekede - they are a "made up" reseller of FYT based units.
What matters is the FYT type number, this number indicates the FACTORY / manufacturer.
Saying "My Navifly doesn't connect to a real OBD BT device" means very little when you don't know what you own nor does anyone know what you've done to the head unit, such as misconfiguration due to misunderstanding, or investigating the issue.
FYI - Mekede and Navifly sell various FYT units, typically Type 116 - details are important.
Click to expand...
Click to collapse
I bought Joying device and i couldn't connect my custom ecu and BT from car to android head unit so i can see some parameters.
The way you can make a workaround is to name your BT device to OBDII (big letters i) you want to connect to, and when you come to BT app from joying it works.
hksaaa said:
I bought Joying device and i couldn't connect my custom ecu and BT from car to android head unit so i can see some parameters.
The way you can make a workaround is to name your BT device to OBDII (big letters i) you want to connect to, and when you come to BT app from joying it works.
Click to expand...
Click to collapse
Hi,
How can I name my BT device? Maybe this method would work for other devices as well
roti86 said:
Hi,
How can I name my BT device? Maybe this method would work for other devices as well
Click to expand...
Click to collapse
well in my example, i reflesh my BT with that name, i used cn2 bluetooth, but i dont see reason why you cant rename for example keyboard BT to OBDII. Im 99% sure everything that you rename to OBDII will work
I tried searching but found nothing relevant. I have a m300s 3gb ram 32gb rom Qled installed in my vehicle it works flawlessly but I have a Bluedriver OBD2 adapter that I would like to use to avoid purchasing another OBD2 device. On my phone I turn on Bluetooth I open the Bluedriver App and scan for the adapter and it pops up and you hit connect. So I downloaded the app on the head unit and open it and scan but nothing comes up. I have downloaded some other bluetooth apps and they see the device but I can't connect with the app still. Is there a workaround or configuration I can try to get this adapter to work? Or does someone have a recommened one that works with the unit. I'd love to use the bluedriver one because of the built in solutions they have for codes and problems with the vehicles.
You need to go in factory settings and enable OBD. Password for factory settings is 3368.