Related
Hi
I am using a PX5 system and have an OBD2 elm227 (tried 2 different brands, 1x icarly and a white label product) and a iphone 7 paired.
The iphone BT works, i can call etc and in my BT settings menu all the devices are listed as paired etc..
Problem:
When i start Torque Pro and i want to choose the BT adaptor there is nothing shown...
According to Torque there is NO BT adaptor paired at all which i can choose from.
I use the latest offcial (paid) PRO version of Torque!
I rebooted the device already but this had no effect.
Is there a fix for this?
I am using malaysk rom on my PX5 device, so it is rooted and has xposed installed.
Who can help/advise
[update]
It worked after a reboot but it seems BT does not work after ACC off/on, only on a reboot or cold start.
Hi there, i also use OBD2 with torque and works like a charm!
Try to delete all the BT paired connections first and after that, pair first the OBD2 adapter and test it!
Regards.
1. Press reset button
2. Unpair
3. Start the phone app and pair from there
Go to torque app and select the obd
it seems when my system goes standby (acc off) the BT connection is lost after power on.
All paired devices are simply not working anymore...
Sometimes they aren's even visable anymore in BT menu after ACC off/on, on a cold start or system reboot they work again.
Is there a way that when the system goes to sleep (acc) these apps keep running in background or are restarted when ACC is turned on again (not cold start/boot).
Also other apps are killed and not started anymore on resume.
Also i cannot find any option too change the ACC time, in an other rom i could set this time for example to 10 seconds and if then returned on it would cold start.
On PX5 Malaysk rom i cannot find any menu for changing ACC sleep/shutdown time
it seems when my system goes standby (acc off) the BT connection is lost after power on.
All paired devices are simply not working anymore...
Sometimes they aren's even visable anymore in BT menu after ACC off/on, on a cold start or system reboot they work again.
Is there a way that when the system goes to sleep (acc) these apps keep running in background or are restarted when ACC is turned on again (not cold start/boot).
Also other apps are killed and not started anymore on resume.
Also i cannot find any option too change the ACC time, in an other rom i could set this time for example to 10 seconds and if then returned on it would cold start.
On PX5 Malaysk rom i cannot find any menu for changing ACC sleep/shutdown time
Search the thread for the no-kill mtcmanager.apk
This will keep all apps on resume
To be able to see they menu for shut down delay you have to be on an mcu higher than 2.48 I think.
I'm having a similar problem. Iphone via bluetooth and torque worked perfect until yesterday.
Now, Iphone is not on the paired devices, nor I can pair with it again. And torque sees the obd adapter, but can´t talk to ecu and I dont see the obd under bluetooth devices .
What shoud I do?
Audiofanx said:
I'm having a similar problem. Iphone via bluetooth and torque worked perfect until yesterday.
Now, Iphone is not on the paired devices, nor I can pair with it again. And torque sees the obd adapter, but can´t talk to ecu and I dont see the obd under bluetooth devices .
What shoud I do?
Click to expand...
Click to collapse
I have the exact problem. was able to pair iphone before, now can't pair anything
B3rt said:
Hi
I am using a PX5 system and have an OBD2 elm227 (tried 2 different brands, 1x icarly and a white label product) and a iphone 7 paired.
The iphone BT works, i can call etc and in my BT settings menu all the devices are listed as paired etc..
Problem:
When i start Torque Pro and i want to choose the BT adaptor there is nothing shown...
According to Torque there is NO BT adaptor paired at all which i can choose from.
I use the latest offcial (paid) PRO version of Torque!
I rebooted the device already but this had no effect.
Is there a fix for this?
I am using malaysk rom on my PX5 device, so it is rooted and has xposed installed.
Who can help/advise
[update]
It worked after a reboot but it seems BT does not work after ACC off/on, only on a reboot or cold start.
Click to expand...
Click to collapse
unfortunately I have the same issue - BT works till next power on of the radio...then only after reboot but I can not connect the paired devices...
I think, it wasn't so in original ROM...
I am using malaysk rom on my PX5 device too.
Ok I was able to get Bluetooth back full time by reinstalling maylaysk rom. Does anyone have a copy of the original torque that came with the factory rom? I have the paid version but I'm having issues with it
Same here hoping for original version of torque that came with px3 device.
Sent from my SM-G892A using Tapatalk
The torque app that came with the unit and torque pro did the same thing for me as soon as I went from MCU 2.75 to 2.8 for my HA MTCD unit.
See this thread for the torque app you need... It's at the bottom of post 1.
https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155
I just posted in Dasaita and Hal9k_ threads regarding my BT OBD.
1. Connecting but not recognized by apps
2. Not connecting to MCU anymore.
Both have been resolved with...
1. Update to latest MCU (my HA is 2.83).
2. Install/update rom to latest Dasaita or Hal9k_ rom.
3. Do a Factory Reset
4. Connect to BT OBD
5. EVERYTHING WORKS FLAWLESSLY NOW FOR ME.
OBD2 Bluetooth Issues with Oreo 8.0
demetry14 said:
I just posted in Dasaita and Hal9k_ threads regarding my BT OBD.
1. Connecting but not recognized by apps
2. Not connecting to MCU anymore.
Both have been resolved with...
1. Update to latest MCU (my HA is 2.83).
2. Install/update rom to latest Dasaita or Hal9k_ rom.
3. Do a Factory Reset
4. Connect to BT OBD
5. EVERYTHING WORKS FLAWLESSLY NOW FOR ME.
Click to expand...
Click to collapse
For all those wondering about the connection problems - I have spent the last week trying everything - then randomly saw a video on connecting one of these devices. Stock setting for the bluetooth is password 0000 - it showed changing the password under bluetooth settings to 1234 which is the stock setting for all OBD2 devices. I went into settings - deleted all bluetooth devices - changed the password to 1234 - searched - found the OBD2 sensor (BLUEDRIVER) and it instantly connected and showed in paired devices. Fired up BlueDriver App and BAM! shes working without a hitch - fired up Torque Pro Lite and bam - connected without a hitch - for others with ELM you need to download the App for ELM because it only works with certain devices. After all the work I did trying to get it to work it was really just one little issue with the handshake *being the password* since you cant enter the password from the Bluetooth device like you would from your phone. Setting them both to the same solved the issue.
Pineapple5809 said:
For all those wondering about the connection problems - I have spent the last week trying everything - then randomly saw a video on connecting one of these devices. Stock setting for the bluetooth is password 0000 - it showed changing the password under bluetooth settings to 1234 which is the stock setting for all OBD2 devices. I went into settings - deleted all bluetooth devices - changed the password to 1234 - searched - found the OBD2 sensor (BLUEDRIVER) and it instantly connected and showed in paired devices. Fired up BlueDriver App and BAM! shes working without a hitch - fired up Torque Pro Lite and bam - connected without a hitch - for others with ELM you need to download the App for ELM because it only works with certain devices. After all the work I did trying to get it to work it was really just one little issue with the handshake *being the password* since you cant enter the password from the Bluetooth device like you would from your phone. Setting them both to the same solved the issue.
Click to expand...
Click to collapse
That worked for me for a week... Now my OBD still connects, but my phone no longer auto connects.
pavllo1980 said:
unfortunately I have the same issue - BT works till next power on of the radio...then only after reboot but I can not connect the paired devices...
I think, it wasn't so in original ROM...
I am using malaysk rom on my PX5 device too.
Click to expand...
Click to collapse
good evening I have the same problem with bluetooth that does not work after a reboot, I want to know if you have find the solution? thank you
ps: i'm french sorry for spelling
Pineapple5809 said:
For all those wondering about the connection problems - I have spent the last week trying everything - then randomly saw a video on connecting one of these devices. Stock setting for the bluetooth is password 0000 - it showed changing the password under bluetooth settings to 1234 which is the stock setting for all OBD2 devices. I went into settings - deleted all bluetooth devices - changed the password to 1234 - searched - found the OBD2 sensor (BLUEDRIVER) and it instantly connected and showed in paired devices. Fired up BlueDriver App and BAM! shes working without a hitch - fired up Torque Pro Lite and bam - connected without a hitch - for others with ELM you need to download the App for ELM because it only works with certain devices. After all the work I did trying to get it to work it was really just one little issue with the handshake *being the password* since you cant enter the password from the Bluetooth device like you would from your phone. Setting them both to the same solved the issue.
Click to expand...
Click to collapse
After quoting a a large post with meaningless correlations, I found postive shockra!
Hi there,
Have read similar threads in the forum, but have not find enough information to resolve my issue.
I have one of the latest Erisin ES8049U unit, with Android 9, Octa Core Cortex A53 1.5 Ghz,
BT works fine with the OBDII adapter (a bit slower in live data transfer, compared to my old BB Passport phone), maybe for a month. Suddenly, the BT pairs to OBDII, but does not respond. OBDII apps like Torque says there are no respond from the adapter.
In the mean time, BT pairs without any problems with my old BB Passport phone and can be used for hands free calling and music streaming with all controls working. Ha!
BT cannot be turned off via icon from the fade menu. I cannot delete BT devices history also. Cleaning cashe, forcing BT apps to stop also does nothing. I have done hard reset, which brings me nothing but apps lost. After hard reset, the BT keeps devices history, which seems to be strange?.
Tried to replace the BT adapter with another one in Factory Settings menu (3368 code), also tried all possible settings.
OBDII ELM327 dongle works without problems, when I pair it with my phone or other device.
BT module board is SD-936.
Should I upgrade to another ROM, any ideas will be appreciated.
Thanks,
Kalin
The things I have done so far with no result:
- pairing code changed from 0000 to 1234;
- cleaned BT cache;
- reloaded factory software';
- removed car battery for 24 h;
- erased wifi and bluetooth settings;
- removed all paired devices;
Most strange things is that I have managed to run the ELM once, then again I have lost it. Using additional bluetooth app shows me something weird - even with ELM removed from OBD connector, seems like the headunit keeps in it memory the device? Even when removed, most programs shows that the ELM is alvailable for pair?
Did you find the cure for this? I have similar Bluetooth issues to my OBD2 system
ka-lin said:
The things I have done so far with no result:
- pairing code changed from 0000 to 1234;
- cleaned BT cache;
- reloaded factory software';
- removed car battery for 24 h;
- erased wifi and bluetooth settings;
- removed all paired devices;
Most strange things is that I have managed to run the ELM once, then again I have lost it. Using additional bluetooth app shows me something weird - even with ELM removed from OBD connector, seems like the headunit keeps in it memory the device? Even when removed, most programs shows that the ELM is alvailable for pair?
Click to expand...
Click to collapse
=========================
Can you share how to cleaned BT cache?
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 :-(
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 am a recent FYT user on UIS8581A, Android 11 (fake).
I have a sim card connected to it that provides internet. When I connect WiFi with OBD, internet connectivity is broken. WiFi without internet has priority in data transmission over SIM card connectivity.
Is there any way to configure or an application that will allow you to have internet from the SIM card and OBD via WiFi at the same time?
I asked this before buying and the answer from the seller made no sense, not trusting the answer as it seemed to be just selling their Wi-Fi OBD I went OBD BT and USB which both work.
I can't force BT to work. Whatever I try won't pair. That's why I bought obd wifi which works, but disconnects the internet.
Hands down best, no connectivity issues on my uis7862 FYT and fastest OBD throughput is genuine OBDlink SX - USB connected.
USB will work as long as you have an OTG adapter in the USB cable. BT will work as long as the BT OBD's name starts with OBD and you change the default pair code in the Head Unit to match that of the BT OBD. I have the OBDlink LX which is the BT version and that works well as does a cheap ELM USB.
kommando said:
USB will work as long as you have an OTG adapter in the USB cable. BT will work as long as the BT OBD's name starts with OBD and you change the default pair code in the Head Unit to match that of the BT OBD. I have the OBDlink LX which is the BT version and that works well as does a cheap ELM USB.
Click to expand...
Click to collapse
Thank you very much for the explanation. I finally understand how Bluetooth works on this device.
Is it possible to disable this fake BT limitation?
lano7 said:
Thank you very much for the explanation. I finally understand how Bluetooth works on this device.
Is it possible to disable this fake BT limitation?
Click to expand...
Click to collapse
No, it's in place to force you to buy their overpriced extras.
kommando said:
USB will work as long as you have an OTG adapter in the USB cable. BT will work as long as the BT OBD's name starts with OBD and you change the default pair code in the Head Unit to match that of the BT OBD. I have the OBDlink LX which is the BT version and that works well as does a cheap ELM USB.
Click to expand...
Click to collapse
Sorry I didn't understand, I have the same radio with ELM bluetooth and the same connection problems. what should i do to fix it?
Can you help me?
Thank you
fabius12 said:
Sorry I didn't understand, I have the same radio with ELM bluetooth and the same connection problems. what should i do to fix it?
Can you help me?
Thank you
Click to expand...
Click to collapse
1. What is the name of the OBD2 unit when in bluetooth
2. Do you know what the pairing code is for the OBD2 unit, have you changed the default pairing code in the radio BT to match the OBD2 unit pairing code
3. Are there any other BT pairings on the radio.
kommando said:
1. What is the name of the OBD2 unit when in bluetooth
2. Do you know what the pairing code is for the OBD2 unit, have you changed the default pairing code in the radio BT to match the OBD2 unit pairing code
3. Are there any other BT pairings on the radio.
Click to expand...
Click to collapse
1: OBDII
2: ok it is 1234
3: yes, my smartphone
2. so have you gone into the radio BT app and changed the default to 1234 ?
3. Remove the phone from the pairing list, the OBD2 unit has to be the only one in the list until used at least once in the OBD2 app you plan to use, then and only then re add the phone.
Note that this could still not work even if you follow the instructions correctly.
Today I try to delete each pairing and do what you tell me.
Then I write the result here.
Thanks for now
I've never had to change my head units pairing code for my ELM OBDII Bluetooth adapter.
The OBDII uses 1234. It simply asks me when I pair what the code is and accepts it.
Obdlink SX usb for the win. Bin the chinese knockoff.
Yesterday I tried to pair by changing the radio name, password and all the craziest tests I could think of but nothing.
My bluetooth screen is the first photo I attach
When I try to connect one of my three working ELM327 minis, nothing happens, I touch the symbol of the chain to connect, it asks me for the pin of the ELM module, I insert it (it is 1234), after a few seconds a message appears "pairing succeeded". But that's not true, because the chain symbol doesn't change, in Torque I don't see the module (try various versions of torque) and I can repeat the bluetooth pairing indefinitely but it never works.
Any app I use for bluettoth tells me that bluetooth is not working or can't be turned on. But if I connect a smartphone it works.
I do not know what to do
Whats App Image 2023 03 08 at 10 49 16 — Postimages
postimg.cc
nobody can help me? I do not know what to do
Just a general comment.
The OBD connector is on the dash, the head unit is on the dash.
Why would you want to go wireless?
Avoiding WiFi or BT where it's not necessary sounds good to me.
Ok, I have OBD1 on my old truck.
I just made my own level converter/µC/USB converter.
Renate said:
Just a general comment.
The OBD connector is on the dash, the head unit is on the dash.
Why would you want to go wireless?
Avoiding WiFi or BT where it's not necessary sounds good to me.
Ok, I have OBD1 on my old truck.
I just made my own level converter/µC/USB converter.
Click to expand...
Click to collapse
Can I use a usb ELM module with an android radio?
On the pc I know that it needs specific drivers to work, does it work on android?
fabius12 said:
Can I use a usb ELM module with an android radio?
Click to expand...
Click to collapse
https://www.amazon.com/PARANNIC-Diagnostic-Scanner-ELM327-PIC18F25K80/dp/B08887TNBB
If you can get USB OTG to work on your radio, that's the first step.
Then the question is: what USB UART standard is it following (copying).
Usually it's FTDI, PL2303, CP2102 or CDC.
In short, I can't tell.
I'm not sure which of these are supported directly by (which) Android.
But I'd like to know.
If you have one and plug it into a PC with Windows or Linux it's easy to see what it is.
Do you even have a FYT unit? You mention "I have the same unit". Same as who? the OP?
And below "with an Android radio".
fabius12 said:
Can I use a usb ELM module with an android radio?
On the pc I know that it needs specific drivers to work, does it work on android?
Click to expand...
Click to collapse
Yes, it does work with a FYT but FYT has crippled Bluetooth and USB stack/drivers. There is a very specific stepwise approach to use: forget phone, make pin-code of unit the same as pincode for ELM dongle, couple the ELM dongle, then couple the phone again (if desired). And the BT identity of your OBD dongle must start with OBD otherwise you can't pair it at all as that OBD* is hard-coded in the crippled BT program/stack/drivers of FYT.
This has already been described in many posts/threads (too many to link to) for FYT units. Do not only ask here, but search the FYT subforum.
And if your unit is not a FYT, you are even in the wrong sub-forum.