Originally Posted by armbar
Software related. The Bluetooth can handle a serial connection to obd2 so if the proper drivers were there tethering would be similar
USB ? This works in Linux and every other OS from iPhones . Libimobiledevice , libifuse are used to accomplish this on other Linux distros and other android devices absolutely support this so the sole inclusion of wifi tethering isn't hardware based at all.
yes and no...
The Bluetooth (and i'd assume usb) is not part of the device in the same way as it is with a phone. The mcu provides the interface between android and the hardware. The only programs that have access to the mcu are the mtc apps (and I believe there is an app or service that does run in the background and allow obd/usb devices to connect to apps, but in a limited way). it's all more of a workaround than a built in solution
USB is USB. I have a Logitech webcam working on my Rk3188 Joying in dash head unit without any issue. It's just regular USB. It needed a powered hub in order to run properly but it works.
If bluetooth is capable of streaming audio and obd2 I'm failing to see why it couldn't handle being used as a modem if the correct software was in place.
USB there is no reason why the feature shouldn't be there. If a Logitech webcam can work so can tethering. In linux, again the following software is required:
usbmuxd, libimobiledevice, libplist ( for ipod integration), ifuse, fuse, python dev
Torque will not see my OBDII adapter. I read it had to be plain OBD for it to see it? Is this true? Can this be fixed somehow??? Stock ROM used to show MAC address of OBD-II adapter, this one shows a blank space when you go try to select Bluetooth OBD-II adapter. Any advise?
I lied again! And Google is your friend! Found out those STUPID blue chinese OBD-II adapters all share same Mac address so when I was testing I had another one interfering with the OBD-II on my MCU radio! Once I went to the store it started working like magic, and stopped working when I got home so I googled if maybe the Rokus were interfering and learned about the same mac on chinese obd-ii's...
All or only so in my latest firmware rk3066 800 × 480. It does not match the OBD ||. In previous works. I sew on predyduschuyu.Spasibo.
my HU- JY firmware(2016.01.06) rk3188 1024 x 600. It does not match the OBDII.
But In previous (2015.12.25) works.
since my HU crashed, my OBDII work,whereas before it was not even recognized
Hey guys, I'm having trouble connecting my obd. I see it in the list of devices in the Bluetooth app when I search, then when I select it nothing happens. Help please?
I had this issue a few days ago, only thing i found that fixed it was to reflash the rom. Then reinstalled all my apps and enabled exposed its modules and it seemed to gine. Not sure of the issue that caused this.
Activate in Xposed modules / XposedMTC
After rebooting open it from your your apps page and enable the obd settings, if it has another name as obd you could name it here. As long as it starts with obd youre good as it is.
After pairing select it in Torque in settings ( if you are using torque )
Which is the best and working 100% obd 2 adaptor?
From experience, the small transparent blue one works on vw, rx8 and maybe others foreign cars, for a Ford F-150 I bought a black one with orange/blue label.
I have got the big gray brick
and it works also fine
Hi. I am facing with one Bluetooth problem. I have connected with Bluetooth obd adapter but after first connection i cant connect another one time. I see the blue obd icon at upper side I can see also the device in Bluetooth connections as connected but there is no true connected because torque obd not responding. I am with stock rom. Is there with this rom this problem?
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
Malaysk, Have you seen this? The problem is impacting me as well. I'm just curious if you are aware of the issue or not.
sorry if it has answered before but with latest malaysk 16/03 version i cant connect bluetooth obd for torque..i find it by searching but nothing happens when i press connect.
also my elm27 OBD2 bluetooth adapter will not pair. My galaxy s6 connects fine and works but my OBD2 will not pair. it shows up but pressing connect does nothing. and ideas?
Make sure you aren't connecting your phone to the ELM327. Disable BT on phone or unpair it then reboot radio. Try to pair again. in BT on stereo. Once connected to radio go back into torque and ensure you have the correct mac address for the OBDII adapter. It is ID'd by HU as OBD II right?
I disabled all the exposed modules, rebooted, paired my elm27, enabled the modules and rebooted. Problem solved.
the only issue I'm having at the moment with the latest ROM from Malay (again, awesome work!), is that I cannot pair the ELM bluetooth ODB2 adapter for using it with Torque.
I've tried almost everything I read on the forums. So far:
- Tried to pair it from settings - bluetooth: The system sees the bluetooth adapter (name "CHX"), asks for confirmation to pair it, but pressing yes does not do anything (I also tried choosing no )
- Tried to pair it from the custom BT menu: Does not do anything
- Uninstalled Xposed framework, rebooted, tried to pair it from both places (settings-bluetooth and custom bluetooth app) : Same result
- Changed BT API from Headunit configuration tool to v1: Same result
The BT module on the system works correctly because I have my smartphone connected every day and working without issues (Iphone 5s). I think that the main problem is more or less the same I had with the original firmware (looks like the bluetooth module is working in "passive mode" , just to be able to be paired to an active external device such as a mobile phone, by entering the PIN in the phone. But to pair it with the ELM adapter, it has to work in "active mode", by asking for the PIN and entering it from the headunit. I realize this is not very techhie, but those are my impressions).
MCU version I have is 2.55.
I can confirm that the ELM adapter works, because I can pair it to a Samsung Galaxy S3 and use Torque from within it, but I would like to use it directly from within the headunit.
This is a pretty old issue. The OBD adapter has to be named OBD or OBD2 to work with these units. Search these MTCB threads for the solution, I believe there was an Xposed module that allowed for adapters named differently.
I had exactly the same issue with my Vgate OBD2 device that has a PIN and the HeadUnit is simply not showing anything to type it. What is interesting - some sellers even advertise this function including mine - but it was never working for me - even on original ROM. I think that the issue is like you said - HU not being able to provide PIN code to OBD2 adapter... Someone before also said that our HUs have very limited list of BT profiles that can be used - but is there any way to expand it?
The bluetooth app is very particular about getting an exact match (both in number, number of digits and format, i.e. county code, parenthesis, dashes, etc) for the incoming call.
There are a couple of things you can do, edit your contacts so the phone number listed is identical to how your carrier sends it. i.e if your carrier sends XXX-YYY-ZZZZ then your contacts have to be the same, if it sends XXXYYYZZZZ then make it match formatting wise.
You can use the bluetooth phonebook app on your phone to manipulate the way the phonebook data is shared, so for example if you have all your contacts on your phone saved like +W XXX-YYY-ZZZZ but your carrier sends them has (XXX) YYY-ZZZZ then you can modify the way they are sent to the headunit without having to actually edit the contacts.
Also the xposed module MTCbluetooth makes it so the contact check just looks at the last 9 numerical digits (i.e. ignores all hyphens, parenthesis, etc) and since its just the last 9 the country code is ignored (at least for US/CA).
Between the module and app on your phone you should be able to get it to recognize incoming calls to contacts.
Please help me...Since the ROM with FUSE support I do not have WiFi or 3g...before FUSE it was working perfect now the WiFI will not turn on (it turns off automatically) and 3g does not connect
|Thread Tools||Search this Thread|