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 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.
It seems that Android Auto (including wireless via Motorola M1) works flawlessly for a few days after setting it up.
Once it enters the "looking for Android Auto" mode there's no other way than removing cache and app settings and establishing the phone -car connection from scratch. And after doing so, it will work for a few days until it starts looking and not connecting again.
Is this a known issue? Is this specific to the wireless adapter? Once the error occurs, wired connection doesn't help.
I also have the AAWireless device somewhere and I'll have a look.
Check the Android Auto forums, maybe some info there...
Android Auto General
General discussion about Google's Android Auto.
forum.xda-developers.com
My wife and I have been using wireless (and wired) Android Auto in our car with the P7P for three weeks with no issues like this. Our car's head unit doesn't have native wireless AA, though - we're using AAWireless. Could be just the head unit or the car needs a firmware update (my car has occasionally received one when I have it connected to my home's Wi-Fi).
roirraW edor ehT said:
My wife and I have been using wireless (and wired) Android Auto in our car with the P7P for three weeks with no issues like this. Our car's head unit doesn't have native wireless AA, though - we're using AAWireless. Could be just the head unit or the car needs a firmware update (my car has occasionally received one when I have it connected to my home's Wi-Fi).
Click to expand...
Click to collapse
I didn't have these issues with my old Huawei.
domi_niku said:
I didn't have these issues with my old Huawei.
Click to expand...
Click to collapse
I've noticed very different Android Auto experiences with the same phone but different car brands before. I've used Android Auto in either 4 cars so far, two of them rentals. I believe my rental VW's Android Auto was horrendously slow and hard to get the touchscreen to respond, whatever the next rental was, was fine. Chevy and Subaru have been fine, too, although my Chevy Android Auto experience seemed better than Subaru, but the Subaru is acceptable.
Hello Everyone,
I am a new AndroidOS user and recently had a friend help me install a head-unit to my Audi A4. The head-unit is similar to the following model:
Audi/Seat | Qualcomm 665| Android / iPhone | Octa Core | 6GB RAM &128GB ROM | Integrated 4G Solution | IQ82A4AL
XTRONS IQ82A4AL is a brand new Octa-core car sereo for Audi/Seat with Qualcomm 665 6GB RAM 128GB ROM Integrated 4G solution plus the latest in-car entertainment features premium quality built-in DSP, CarPlay & Android Auto and more.
xtrons.com
Background:
I have noticed that when I INITIALLY pair my iPhone to the Android head-unit over BT, it will ask me to pair on my iPhone (which I confirm), and then switch to CarPlay automatically. At this point everything dealing with CarPlay is handled over Wifi (not BT), but if I go back to the main AndroidOS UI, and check if my BT is still paired, is it DISCONNECTED. I am also able to confirm that the BT connection is disconnected on my iPhone as well. Each subsequent connection, as soon as I turn on the car and it connects to my phone (over BT), it switches to CarPlay, and then the BT disconnects. I would have assumed the BT connection would still be active and paired at this point.
Question:
Is the BT connection being disconnected (after CarPlay is initialized) expected behavior? I chatted with my friend who is an Android-Auto user, and he said with his setup (using similar head-unit), the BT connection is ACTIVE even after Android Auto takes over control.
Any feedback on how this is supposed to work for Apple iPhone users, utilizing the CarPlay functionality, would be greatly appreciated. If I could provide any additional information on my side, to assist with troubleshooting, please let me know.
Thanks,
Asif
Hi, I have connected z link to my phones bluetooth and to the oem audi for mercedes. When i connect zlink no audio comes out through the system? What settings do I have to switch.
As attached no audio is coming from the spd bt setting
Is the unit MTCD type, post Android system information including MCU version.
Crickets....