yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] dyabolikarl:
Does this work on 6.0.1? I need to get my odblink running

I don't know how to retrieve the pin from the ODBlink nothing pops up in the unit

but it goes "set pin true setconfirm true"

Pairing 11

Unpairing 10

Cannot connect due to bad passkey

I will add when i select the odb on the detection screen the selection flashes orange but then it deselects itself. there is no link icon either?
[FYT Android Head Units] brian8179:
I have had callers on bluetooth complain intermittently about terrible background noise during calls. It appears to be an issue with the mic on the unit picking up blower fan noise. The background noise starts out loud, but after a few seconds you can hear the noise stepping down and getting quieter almost as if the unit is gradually turning down the mic sensitivity. It's bizarre. Its not just blower fan related either. If you adjust the volume knob on the unit, the caller on the other end can hear it quite loudly, but once the sensitivity "steps down" the caller can't hear it at all. It has to be some sort of mic or software issue. I have tried both mic sensitivity settings in car settings with no effect.
[FYT Android Head Units] kampfschachtel:
Need help please: device bricked

My joying Intel on 5.1.1 with 14 March update, rooted with superSUsuddenly doesn't boot anymore. Done nothing and unit was working for 3 weeks like charm but started the car and it get stuck in the boot animation with the lovely "haven't been able to get into systemUI many time"...

Fantastic, soft brick...so I got a the new firmware 28march unzipped it on a USB stick and wanted to reinstall/upgrade from recovery. Reset with USB stick plug in.

Updates startes and I get the Andoid guy with the new firmware installing BUT after 5mm in the progress bar it suddenly stops and shuts off...no error shown, nothing just shuts off.

Same 3 times....also with the 14march update...with and without sd card installed

What to do?
[FYT Android Head Units] surfer63:
Did you check the USB stick itself for errors?
[FYT Android Head Units] kampfschachtel:
How?

I formatted it and this worked. Unzipped soft on it and worked too.

Used the Same Stick for installing before. Used 2 different sticks and Same with both
[FYT Android Head Units] surfer63:
That might be due to the fact that you're on windows. Windows is not so strict. If windows detects errors it simply continues until it can't go further. Linux will stop and tell you that your disk is not correct.

On windows you have disk management (Datenträgerverwaltung, Festplatten etwas ?) where you can check the USB disk.

Edit: Another option is to leave your car switched off for at least 30 minutes to make sure that all electronic components are switched off completely.

Then try to reinstall. If that doesn't work, disconnect all power to your joying unit. Reconnect and try again.

(That would be the steps I would try)
[FYT Android Head Units] kampfschachtel:
Having mac, checked and 0 errors. Also 2 different sticks Used before and same problem. Downloaded firmware under Mac and then unzipped in windows as joying wrote, done it with win, too download and unzip.

Cannot get into recovery menu either...

I will disconnect the harness and connect it just to a separate battery. Just sucks as I had the final dashboard install done and now rip it out again...connectors are not getting better doing this 20times....
[FYT Android Head Units] surfer63:
Good that you're on a Mac :)

Mac or Linux doesn't matter to unzip and write to USB.

Joyings advice to do it in Windows is nonsence.

Did you check the formatted state of your USB-disk? Is it exFAT (Mac's default for USB-sticks) or Fat32?

Make it Fat32, or if necessary Fat (=Fat16)
[FYT Android Head Units] kampfschachtel:
Ok, will ignore joyings advice on this in the future....

It's fat 32. Hate win but forced to use it at work...

Also 2 different sticks, same issue??? Quite unlikely...

Must it be the exact same firmware or can I flash the 28march at the same time?
[FYT Android Head Units] surfer63:
Yes, that's very unlikely.

Theoretically it shouldn't matter what you flash. It replaces the total system. That is how flashing works, but Joying (or maybe it is the Intel approach) seems to be a little different.

Joying also mentions that once you are on Android 6 you can't go back to 5.

I haven't tested that myself.
[FYT Android Head Units] treel:
Just to let anybody know.

The modified app only work on 5.1.1 version of android.

I have tried to make the modification on the new version ( 6.0.1 ) but without luck :((

I'm still trying but i'm on the end of my knowledge.

1.) i have problem on my unit to get running the stock android setting

2.) i have made a pairing app for testing on every android device its working without problem but on joying unit it doesn't

3.) i'm only able to pair without problems fitbit charge2 other devices (keyboards,obdlinMX or GarminGLO ) are not working

If somebody can me give hint what i'm missing it would be very appreciate.

I think there is a problem either with the android system its self or somewhere else.

I will tried to get it working but i don't see it very positive :((.
[FYT Android Head Units] kampfschachtel:
Use the app called "Bluetooth auto-pair" by Michael Brachmann from the play store and follow the instructions. Costs 2 or 3 buck and worth it, solved all my bluetooth issues.

I could pair everything I wanted with it: phones, OBD dongle from Carly for VAG or obdlinMX, keyboard.
[FYT Android Head Units] dyabolikarl:
Hi there i looked at that but how does it pair with odblink when there is no popup for the pin number ODBlink has rolling pin? Does it force accept any pin?

I some how got it to work on my system though through the BT app that the OP made. I will download that app though if you think it will be all good for the ODBLX for next time.
[FYT Android Head Units] treel:
I have tried the app on 5.1.1 android and it has not work.

To bring up the menu in the app you need to remap one button to the android menu button.

I will try it on the 6.01 android maybe it works.

But i'm searching for a method that is working every time.
[FYT Android Head Units] ajcarson11:
OBDII USB adapter and resume

Afternoon All -- I've been digging into an issue and wonder if anyone here has insight.

I have a USB OBDII adapter (Scantool OBDLINK SX) that i've been trying to utilize with my Joying 5.1.1 on the March firmware. If I completely restart the headunit the Torque application recognizes the adapter and everything works great. After turning off the car and restarting (causing the device to suspend and resume) however I notice that Torque can't find the adapter. I'm wondering what might be different with android suspend/sleep in comparison to a full restart (where everything works great again). I DO have the physical button mapping feature functioning, which to my understanding also removes the auto-kill app suspend feature.

Does anyone have any ideas on what I can do? Its difficult to reach behind the dash to disconnect and reconnect the USB adapter (which I imagine may solve my problem) -- If I could find a software/command way to disconnect/reconnect a device I may be able to throw that into the script that the physical button remapping uses on resume.

Other than that.. any idea what could be happening with USB in android? I suspect its an issue with Torque, as I don't have trouble if i use other OBDII applications (these connect just fine even after resume).
[FYT Android Head Units] edit:
Check if killing the Torque app and relaunching it solves your problem. If so you can issue a kill command for Torque in launcher.sh each time the unit goes to sleep.
[FYT Android Head Units] Clandaries:
Does anyone know a custom rom for the intel headunits with 6.0.1? Sorry if offtopic.

Greetings
[FYT Android Head Units] ajcarson11:
Fair idea -- I'll try to kill it before turning off car (when its working), fire up car, and turn it back on. Standby.

EDIT: Silly question (but to make sure i'm not missing something) -- If I kill the app by swiping right on it in the running-app-view (the stack of apps that you can choose from that are currently running) is that enough to fully kill it? I imagine so..
[FYT Android Head Units] edit:
No... For some apps it's not enough. For instance Poweramp still plays in the background after you swipe to kill it. Go in settings, apps and force stop it the old fashion way.
[FYT Android Head Units] surfer63:
No. There is no custom ROM. They are extremely hard to make for the intel platform.
[FYT Android Head Units] edit:
May I ask why? For the lack of info (source code) from Joying or is something related to Intel?
[FYT Android Head Units] gtxaspec:
Try 6.0?
[FYT Android Head Units] kampfschachtel:
No option. Everything is running fine on 5.1.1, I have all the apps, soft, mods that I need and know how to do the mods.

With 6 I have to start all over again, going hours through threads to find what I need and some bugs are still not resolved. No adavatage at all for me. Just need to have a clean 5.1.1 on 28 march release running.

Sent joying a support request, let's see what they come up with.
[FYT Android Head Units] ajcarson11:
I've tried killing the app fully in two instances, and in both instances it solves the problem upon re-opening the app! So now I just need to kill the app upon suspend. I bet I can do this as part of the script that powers the hardware buttons -- But you suggest that I can also modify launcher.sh?

Thanks for your help -- Simple solutions.

EDIT: Shoot. Somehow I didn't manage to tag Edit's reply in this post. And looks like I can't delete the post to try again.
[FYT Android Head Units] edit:
The custom keys mod that you already have installed has that launcher.sh that I am taking about. In it at acc off section you can kill it and if you wish and find it useful at acc on you can automatically start the app.

---------- Post added at 08:25 AM ---------- Previous post was at 08:11 AM ----------

I might be wrong but it looks like it's a hardware problem on your case and probably​ your best bet is to buy a new motherboard if you want to quickly solve your problem, that's what I would do if I were you. I think the flash storage has given up on you.

Of course you can also send the unit to China for warranty repairs and in the meantime buy a new one, the units have come down in price lately.

Or maybe buy a new one, send the old one for good and maybe ask for a refund?

I am sure you can find a middle ground... I found them to be flexible and decent.

Keep me/us in the loop please, I am curious how things develop. Good luck !
[FYT Android Head Units] dyabolikarl:
I would also suggest killing the torque app i had so many issues with it sleeping.
[FYT Android Head Units] kampfschachtel:
That is exactly what I thought so too, broken flash memory. If I will replace the 2Din metal box with motherboard by the 1Din one, wanted to do this anyhow...

Joying wants a video of it. So I will do 1 till 3 again today...

But why is the 22nd release as the only one updating mcu and running through the update process??? I was on 14 March release, so if then 14th March should be the one to restore on...

Will give it a last try with Android 6 today.....it's broken so I cannot damage it more....
[FYT Android Head Units] edit:
After you make the video for them ask for a separate MCU like they provided for Android 6... MCU only... You put the files on a stick and update only the MCU. I don't think it will revive your unit but it's one more thing to try... Who knows...

And talking about the motherboard ask for the new one (that's compatible with your display) with the 6021 SoM that's a tiny bit faster (wrote in my Q&A about it).... Maybe you buy the new motherboard, i am no expert but overall it looks to be a better build.

Even if you update to 6 and somehow it comes back to life explore with Joying all the options for a replacement... If I were you I would not trust the unit anymore and I would hate to break on you again... And there a good chance that it will catch you in a bad moment like on a trip.
[FYT Android Head Units] surfer63:
No, my answer was way too short and not so precise. sorry.

Rockchip is about the most widespread and the system to create ROM images has actually not changed since the RK-2818 versions in 2011. With so many devices around for such a long time with a hardly changing structure a lot op people have already looked at it and Rockchip themselves delivered also tools.

Alwinner is different but not so much different and also more widespread.

The Intel 3GRs are actually also "Rockchip built" CPUs but relatively new and not so widespread. It limits the amount of developers/modders. And they are definitely different compared to the RK-xxxx and A-xyz chipsets.

Finally: Intel stopped the partnership with Rockchip for the sofia chips (actually Intel® Atom™ x3-C3200) and stopped the entire Sofia project, so there will no new developments either and I assume current builders will gradually switch back to (8-core) Rockchip or Alwinner chips, although support should continue for the coming 2 years (if I'm not wrong).

And we do miss specifics from Joying, but "everyone" can download the AOSP x86/x64 android code and compile his/her own kernel. Getting it to work with all the "extended" hardware, needing specific code and drivers, in a head unit is a totally different story.
[FYT Android Head Units] edit:
Thank you! I knew some of the stuff but not all.

Like I said before in other posts I've chosen this unit for the instant on feature and for the ability to tether via BT that I waited for a very long time. Unfortunately I haven't seen a good BT hardware implementation like with the Intel Sofia and I am afraid I will never have. Too bad the BT software on the Joying Intel Sofia is so poor and thank God for the mods that allows us to make it usable.

Joying just teased us with their new units with digital amplifier build in that have higher audio quality, a better EQ and generates very little heat.... I am wondering if they will keep the Intel Sofia around...
[FYT Android Head Units] joshnat:
I have a VW specific model running 6.0.1. I have never been able to get an auxiliary audio connection to work. There are male RCA connectors on the Joying wiring harness but connecting them either to the aux female connectors on the HU (and the audio source to my car's aux port in the center console) or connecting directly to a 3.5mm plug produces the same results: the Joying aux app tells me "no video signal." I'm not trying to connect video, I'm only trying to connect an auxiliary audio source. Is there some other way to get aux in to work?
[FYT Android Head Units] ajcarson11:
Thanks guys! The modified launcher.sh works like a charm. Torque working at every resume now! Appreciated! :good:
[FYT Android Head Units] treel:
Thanks to dyabolikarl who found a method to pair bluetooth devices with the modified app on android 6.0.1.

Necessary step :

1.) replace the stock bt app with modified one https://drive.google.com/open?id=0B6VvHrCho-0fb3lPUnNQZWU1U3c

you need to replace it , set the right privileges etc.

2.) start bluetooth app set pin in settings to 1234 ( not sure if the set PIN is really required but it works)

3.) go to link in the app

4.) kill the app (not just close you need to kill it )

5.) start the app again

6.) go to link

7.) find devices put pairing PIN 1234 for devices that require PIN or 3368 for device that does not require PIN

This discovered by dyabolikarl ,tested by me and Sphynx0.

I don't know why it is working this way but its work.
[FYT Android Head Units] surfer63:
Thanks for your work.

However, your link is abbreviated: See the "6...3" in your post. Please correct.
[FYT Android Head Units] dyabolikarl:
It was a frustrating time trying to get the BT to work but because i am stubborn i made it work :)

Thanks to all the modders here.
[FYT Android Head Units] treel:
Sorry it is update
[FYT Android Head Units] kampfschachtel:
Done all the possible ways updating and joying sends me a detailed step by step list how to get it back to live with the Android 6 release but it failed...black screen with a vertical line running and no operation during 6 hours.....still bricked..... I would understand if that happens during a app install or rooting etc. but not during listing to music and driving with a setup that ran for 2 month without any problem. so there must be a hardware failure.

I will make them to switch the metal box with the motherboard, not willing to swap the motherboard and get other problems.

Lot of time wasted already, its time for a solution.
[FYT Android Head Units] edit:
I am really sorry man :(

It looks more and more like a hardware failure.

The motherboard is very easy to swap, if they send you one with the heatsink attached it's even easier to swap. The motherboard connects to the display only with a ribbon cable. You can swap it out in 7-10 minutes top. Still, it would be nice if you can swap the whole unit.

I am really curious if the heat killed it.... Not that I can find out...

Keep me posted please !
[FYT Android Head Units] kampfschachtel:
It is definitly not the heat, as in the Audi R8 the radio sits below the center airvent from the climate control. So it gets cooled in hot weather by the cold pipes around it and also the engine is in the back so no additional heat from the firewall front either. Was around 20 degrees and rainy outside when it crashed, so no heat problem.
[FYT Android Head Units] rknuette:
Unfortunately, this does not work for me. I'm trying to pair a Truma iNet Box (heating control in my RV), but although I followed the steps above, I'm not able to pair (the box does not require a pin for pairing)

If I'm using the Truma software, I can connect to the box, but pairing is not writen into the database and hence forgotten once the app is no longer in the foreground.
[FYT Android Head Units] treel:
Can you please some more info about what the bluetooth app put for messages ?

Have you tried to pair it with PIN ?

But its strange that you can connect without pairing android systems usually do not connect to devices that are not paired.
[FYT Android Head Units] ztbishop:
A few things in case this helps anybody or if anyone else has recommendations...

I can move this to a sub forum if needed.

I'm on 6.01 release (May 25).

1.

Google Maps only works normally one time before telling me I need to enable Google Location Service to continue. This happens all the time if I restart the car, or try to navigate more than one time.

THIS ONLY happens when using Bluetooth Tethering apk for connection.

Strangely, if I use WIFI hotspot, this is never an issue.

Two workarounds:

1. Restart the Joying unit.

2. Toggle Google Location service off and back on in system settings. (This normally works but not always).

2.

Android Auto application works, and looks amazing. It has two problems.

1. You MUST exit the application before shutting the car off, or it will force the Joying to reboot once you start the car back up if it sits more than a few minutes.

2. Android Auto app cannot make phone calls as it doesn't see your phone's carrier network (likely no workaround).

3.

Verizon Messages application - this allows you to make text and make / take calls directly from the Joying unit using Internet connection.

Issue is - having this app installed on the Joying forces the system into 'Optimizing app 1 of 1' upon restarting which takes a long time. It never goes away until I uninstall the app.

4.

OBDLink MX / LX models require the system to generate a unique PIN each time they pair, which the Joying does not have the software to do. I see people working around this on older release prior to 6.01

I'll likely return the OBDLink this weekend as I'm coming up on the end of a 30 day amazon return policy. I can use the cheaper devices, but I'm nervous about draining the car battery over time.

5.

Due to the Google Maps issue mentioned above, I'm considering using WIFI hotspot from my phone, rather than bluetooth tethering. However, I'm curious if this has been hard on anybody's battery over time? As in, the over-all life of the battery. Also, if it drains it faster I generally try to avoid plugging in a charger every time I drive since I've had bad experience with Motorola phones developing a loose USB connection over time. (Maybe I'm paranoid).

I can get a cheaper wi-fi hot spot from verizon but they charge the cost of device, activation fees, and then another line access fee (monthly) as a 2nd device. Also the cheaper WIFI hotspots only handle 4G and I worry they won't work in areas with less access, such as 3G.
[FYT Android Head Units] rknuette:
I tried two different methods:

Pairing without pin

After entering the pairing mode at Truma Box I selected "Link - Search button". Once the Box has been detected, "clicked" on the entry in the list (which only highlighted for less than a second, not permanently like on the original apk), then selected the connect button, entered 3368. Message form app: "Pairing 11", after some seconds (appr. 10) "Unpairing 10". The Truma Box is still in the list of devices, but it is not paired (bluetooth led on Truma box is still blinking, the Truma app does not recognise the box (what it should do, if pairing were successful)). Re-doing the steps do not solve the issue.

Pairing with pin

After entering the pairing mode at Truma Box I selected "Link - Search button". Once the Box has been detected, "clicked" on the entry in the list (which only highlighted for less than a second, not permanently like on the original apk), then selected the connect button, entered 1234. Message from app (from my mind): "Set pin for confirmation true". After some seconds a gray system message box aprears at the bottom of the screen telling me that the connection attempt was not successful.

If I'm using the truma app, the app itself searches for the bt device and (temporary) pairs with the box. But as mentioned above, as soon as the app is sent to background it looses the connection, and the box is also not visible in BT app.
[FYT Android Head Units] edit:
All my previous Chinese units had that the usual horrible crippled BT implementation so I was force to turn my phone into a Wi-Fi hotspot all time time. I made an automatic small script in Automate app that turned on the hotspot when the phone was connected to the car BT

Back then I was using an Note 3 and I can tell you that the battery was hit pretty hard so depending on how much time I was spending in the traffic I had to top up the battery at work. During long trips 2-5 hours I had to charge the phone during the trip. Also the phone was heating up even if I was just streaming music and some data for the navigation.

With the Joying Intel Sofia tethering via BT is just awsome. I still don't understand why on earth they crippled it so bad with the crappy BT software. They have one BIG advantage over all the other Chinese Android units on the market, past and present and they chosen to ignore it. The battery drain on the phone is at least 3 times lower with the BT tethering versus the wifi tethering... if not more. The phone does not heat up and I don't connect it to the charger unless the trip is very long 4-6 hours. The only downside with BT tethering is that the bandwidth is lower compared to the wifi tethering... For me it's more then enough because I only stream audio and using Waze or Google Maps that doesn't use that much data.... For video, high bitrate, FHD quality might not be enough... Haven't tested it though.
[FYT Android Head Units] treel:
Every thing seem OK

This the behavior when you don't kill the app first time.

Just run the bluetooth app go to link tam you should see message like reg. recv then kill the app

and then try it again.

if it doesn't work try to reboot the unit before the steps

for explanation

pairing 11 is when the devices request pairing from the unit

unpairing 10 is when the pairing failed

paired 12 is when the pairing is successful