Hi everyone, I have a joying rk3188 1024x600 head unit and recently flashed the most recent malaysk rom. Before the flash, obd dongle would pair fine. Now I cannot get out to connect. I can connect my phone to the headunit, can connect my phone to the obd dongle, but cannot connect the obd dongle to my headunit whatsoever. It shows up in "available devices" and can be clicked then click "yes" to connect, but it doesn't connect.
I've tried to play around with xposedmtc but no luck.
Anyone have any ideas?
Thanks!
did you click enable xposedmtc in xposed?
TRY disable xposed-bt or manager in xposed
and roboot will be done
Yes, all are activated in xposed. And tw0119, I will give that a try.
Malayskâs rom Dec.2015 on my JY-HU clould pair fine ,but Feb.2016&Jan.2016 roms could not.
So i try disalbe all Xposed modules ONLY enable Xposed mtc ,OBD dongle works after roboot
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
dannyboy223 said:
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
Click to expand...
Click to collapse
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
tw0119 said:
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
Click to expand...
Click to collapse
No XposedBT whit OBD.
Prob is that there are number of overlapping Xposed modules, conflicting with each other and even underlying ROM features.
Until Malaysk and module devs coordinate their activities you have to experiment and make compromises. In order to get something you have to drop something.
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
4. Rebooted
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,
C.
i have 2 adapters and neither will work for me. one will not pair no matter what combination of things i choose in xposed but works great with my phone. the other adapter works so good i don't even have to put in the pass code when using my deck, but it will not communicate with my 2001 fords ecu.
Hi
Not working bluetooth. Not scaning anything
Which BT chip sellected? WQ BC5 ,WQ BC6, IvtBt,Sd bt, WQ BC6B. My sytem rk3066 arm vortex 1.6 dual core .
April 2016 malaysk rom.
I tryed xposed disable combination but not working bluetooth
Help pls
Sytem starting i see pop-up bt connecting,version2
OBD adapter
Unfortunately I have the same problem with the OBD adapter are connected may not apply to find and get information...
The machine is KLD2-RK3188 1024x600 machine with the latest of Rom Malaysk 21/1/2017 (21 version)
I have tried all the above solutions but still not the OBD program works.
OBD connection Joying
Can somebody tell me where to get to "Xposed module manager" in Joying system please? For OBD bluetooth issue
i had same problem but solved it.
Don't use the bluetooth menu in system settings but use the bluetooth app instead (which came with the rom (android 6)).
Using the bluetooth app search here and here pairing worked without any problems for me, after pairing it worked as normal again.
cheatman said:
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
4. Rebooted
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,
C.
Click to expand...
Click to collapse
That worked for me. But found also additional tips are needed to check:
1. If adapter name is not OBDII per default then in BT app settings (last tab) set exact name. This option is available in modded BT apps in Malaysk ROM (4.4.4), dunno for other ROMs. So there is no need for any exposed modules, just change adapter name in app.
2. Adapter with correct name can pair even if pin code is incorrect! Looks like paired but will not work in apps. So check that pin code in BT app settings is correct for your adapter.
3. In Torque, if you had any other adapter used before, clean all app data (in Android app info). Also noticed that even after app data cleaning, old Mac address is shown instead of new one paired in BT app. Looks like MCU somehow wrongly saves and provides old, even removed from BT app, adapter Mac address. But new paired adapter is working. So there is some mess with MCU and BT and Torque... Not sure where is the issue, but noticed that latest Torque ver listed something about 'improved listing of BT devices'. So it may be known issue on Torque side....
I had the same problem (obd bluetooth not working) using Pumpkin Android 7.1.2 with malaysk ROM 4.1 and found the following solution:
Go to app settings, select "show system apps" an delete data+cache of all (4 in my case) apps regarding bluetooth.
Then connect your devices again. Enjoy
I'm currently working with a software developer who produces an OBD2 reader and the associated app (Hondash). The device and app work perfectly on conventional Android devices, but not our awkward headunits. The OBD2 device connects and pairs to the headunit, however the app cannot detect it. It seems that the headunit's Bluetooth hardware is not visible to the app. The developer says he "don't know how or why the system doesn't deliver a Bluetooth device list to my app when requested". He goes on to say "For some reason the head unit doesn't expose a device list to my app, and without it it's blind and not able to initiate a connection"
My understanding is that the Bluetooth hardware is handled by the MCU part of the software, rather than Android itself.
Does anyone know of a way to convince the system to expose the Bluetooth device list? Or has anyone got access to the programming documentation for the head unit Bluetooth API?
What is puzzling here is that apparently Torque works on our headunits. Torque is compatible with our Bluetooth so it does seem possible. I assume that Torque isn't the only OBD2 reader app that is compatible, there's probably other too, so any tips on how he could get his app to work would be appreciated.
Hi all,
just a simple question - had anybody succeeded with MirrorLink? And with full phone mirroring (not just with the limited number of apps allowed)? If so, how? My A320FL is updated to the latest available Android 6.0.1, then rooted.
I tried several apps and guides together with two cars (Toyota & Skoda) with no success:
1) Samsung CarMode - the latest available from the market is not the latest, as I found somewhere here, but anyway: it doesn't do anything with Skoda and does show "Your phone is connected through MirrorLink" when connected with Toyota Touch 2, but shows nothing on the display. No option to start it is displayed on Toyota display, Skoda Amundsen says "no compatible app found".
2) LG MirrorDrive - does not even start, but it's shown as compatible app in Skoda. And once, I got the display in portrait mode shown on Skoda display for few seconds.
3) Android Auto - even though it's not accessible in my country (don't know why), I installed the latest version, but it is possible to start this app only on the phone, no car sees it.
check this
https://www.youtube.com/watch?v=F-TNAXxFqDw&t
shaggyxda said:
check this
https://www.youtube.com/watch?v=F-TNAXxFqDw&t
Click to expand...
Click to collapse
Thanks for idea, but it's unfortunately not the right thing - this deals with app flickering when the phone is already connected via MirrorLink. In my case, I don't see anything related to phone display on the car's display. In the meantime, I found out, that the possible problem could be system incompatibility - Samsung supports only MirrorLink 1.1 and Toyota is MirrorLink 1.0 (that's why all the videos online with Toyota are shown with the old S3). I also found out, that Samsung dropped the backward compatibility on Bluetooth, so i.e. old integrated handsfree in 2007 Yaris is now unusable. Shame on Samsung, did those people ever see a car?
Finally, got it working. But not thanks only to myself
The first is thanks to Toyota - there has to be at least HE3934 firmware version loaded (that I found out only when trying to make the mirrorlink running in a new Yaris).
The second is, that in phone, only one mirrorlink app is allowed and it shall be LG MirrorDrive for make it running in Toyota (Samsung CarMode app supports only VW group vehicles - possibly because they provide VW with the whole infotainment and related electronics).
The third and most important is the cable - it has to be a cable that "somehow" supports mirrorlink - Samsung original cable is ok, but I firstly tested it with another "noname" cable, which works only sometimes. Only during longer continuous driving period I found out, that the "impossible to connect" periods happen when the phone and cable shake - maybe some contact is doubled in the original cable.
As last I need to say, that LG MirrorDrive mirrors any running app, but after you run an app, mirroring quits with message, that the function is not available during driving. But it starts the app in background anyway, so when you run LG MirrorDrive on the infotainment again (without disconnecting or anyhow touching the phone), the system opens directly in the app you started before. It's also good to turn off the notifications for LG MirrorDrive, as it shows a message about incompatibility every time it's started.
So I hope that the lines above help also somebody else.
Can a samsung a3 2017 screen mirror? If yes then how please??
... but only working with nougat. Android 8 not working any more. ?
Please send me
hello everyone,
I just installed a SEICANE chinese android head unit in my Fiat Ducato from 2017.
I connected the ISO port directly to the 2 connectors from the car, I've first tried to use a power harness including the CanBus decoder, but then the HU is dead. Without harness , the HU works (I guess the car already has a CanBus built in?).
The radio works very well. Also Wifi works well, I can surf on the Internet. But some apps I can not download (using Play Store). For example when I try to download TomTom GO, the HU tells me that there is no Wifi (although there actually IS Wifi!). Other apps are no problem to download (I've "fixed" this problem by installing Sygic i.o. TomTom).
I paired my Samsung XCover3 via Bluetooth and also problems: when I try to make a phone call, sometimes it goes to handsfree (like it should), but sometimes it does not (although the phone display opens on the HU). I did the pairing 10 times , but no difference. I also tried to make an Internet connection using Hotspot or tethering, but that also does not work.
I resetted the HU, but no improvement.
Does somebody knows these problems (and has sollutions to it)?
Regards,
Peter
Hi everyone, looking to pick up an octacore headunit from aliexpress, "KANOR" branded.
[can't post link because new member]
But one of the main reasons I want it is to connect with my ECU through a google play app called MDash. It connects via bluetooth. Through my reading over these android head units, I've seen a lot of mentions of the bluetooth functionality only working for music, phone calls, and the obd2 adapters. Does anyone have experience on whether or not the bluetooth is still this limited for the newer Android 8.0 octacore units? And if so, is there a way I can get the functionality I need out of the headunit by rooting it?
Thanks for your time and help!
bump
bump. Any help is greatly appreciated before I spend my money on a headunit.
Yes mate still crap. In fact Id say worse.
I have a new erising octa px5, mtcE, android 8 and bluetooth is minimal. Phone app is rubbish, sounds / looks terrible and it just about works .
Dont no for sure what profiles it has stock but seems everywhere I read now ppl are going the android auto route (which uses 'OK' google everything (surprise surprise)) and always on data. etc.
Lemmings!