yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] avenant:
Thanks, I went into the chinese bleutooth app and changed the pin to 1234, then the odb2 dongle connected in the android settings, tried your app but it gave a dialog that it crashed the settings app, I guess the normal bluetooth settings just worked on my unit, the problem only was the pin in the chinese bluetooth app, duh.

But I noticed another problem ( I build the android radio into my car just today because I had to wait weeks for a 2din dashboard unit for my car from another seller wich arrived today, I had the radio allready for weeks connected in my home to a power suply), when the key is in ignition, the unit starts, so Torque can connect, but when I move the engine key further to start the engine , so torque can connect to the ECU, the unit powers of and restarts....
[MTCD  Android Head Units Q&A] doitright:
That crash didn't impact its functionality, and has been corrected in latest version.

What that program DOES, is it LAUNCHES that normal bluetooth settings menu.

YOU CANNOT ACCESS THE NORMAL SETTINGS MENU WITHOUT IT!!!

You have it wired wrong. Pay closer attention to the RED and YELLOW wires.

Yellow wire (thicker) is ALWAYS POWERED ON.

RED wire (thinner) is switched by key.
[MTCD  Android Head Units Q&A] sodiumspain:
had your HU the info car app from joying? the one displaying temp, engine rpm, fuel remaining ,etc ...? if afirmative, could you extract the apk and share with the rest of the world :D ?
[MTCD  Android Head Units Q&A] avenant:
I have a diagram of the iso connector of my car and it matches the iso connector of the radio, then they must have made a mistake in the wiring from the iso connector to the mini connector you need to plug in the back of the radio, that sucks, changing the wires on the mini connector is not an option, then I need to open the dashboard again to unplug the iso connector and unsolder the red and yellow wires on the iso connector and switch them. I hate soldering I suck at it.

---------- Post added at 08:47 PM ---------- Previous post was at 08:20 PM ----------

do you mean the app posted on page 9 of this thread? http://xdaforums.com/android-auto/m.../2gb-ram-intel-cpu-heres-specs-t3468322/page9

Vehicle_com.microntek.controlinfo.apk

I would also like and apk of the launcher, my unit has a completely different launcher, it has a widget which can't be moved, which displays the time rather large, and on the product page of the manufacturer the widget also displays the weather info, but displaying weather in the widget doesn't work, so I decompiled the launcher and looked through the code, it mentions com.microntek.weather and com.hct.weather, neither of these apps are present on my unit, so I found the com.microntek.weather app somewhere on this forum, tried several versions, only 1 version worked, installed it as a root app, but the widget still does not display the weather.

The launcher I have is: Launcher2mtc3_5.apk https://drive.google.com/drive/folders/0BwQC1xSgCO86VFNpT3RMd1oyNEU

I was able to install other launchers from rk3188 units found on this forum, wich installed as an update to my launcher, so could revert
[MTCD  Android Head Units Q&A] sodiumspain:
Yeah ! im gonna try on my rk3188 hu . fingers crossed :fingers-crossed:

do not install in my hu :(
[MTCD  Android Head Units Q&A] doitright:
Well, yeah. That would definitely suck.

You *definitely* need to open the dash.

What I would do, is check the pins with a volt meter. Make sure you know which of the wires is constant on and which is switched... and trace it through ALL of the steps of the ignition switch. I could imagine some cars with really dumb old fashioned radios to switch ALL of the power off... make sure that yours doesn't do this. If it does, then you'll need to run a wire to your junction block. You can use an add-a-fuse to connect in. DO NOT tie into battery power without a fuse, because your could burn your car down if the wire shorts out.

If you need to solder, which it sounds like you will, get some DUAL WALL HEAT SHRINK TUBE. Strip about half inch of insulation off of the two wires to be connected, twist each of the wires to bind them together, slip on the tube and send it down one of the wires out of the way, then overlap the two stripped pieces of wire in an X about half way down, and twist them together such that they run INLINE. I.e., you don't twist them to make the cut ends line up, you twist them to make each cut end point UP the wire you are twisting it around. Then when you solder, it becomes an INLINE connection. Take your soldering iron, heat it up REALLY good, hold the iron in your right hand (if you're right handed), solder in your left. Clean the tip off on a damp sponge so that it is shiny, then apply a SMALL amount of solder to the tip to just coat it evenly. Now apply the tip to the copper of the wires you are twisting together, hold it for about 3-4 seconds, and then add solder. You can add a small amount of the solder against the tip, but try to add the solder to the WIRE. The solder should soak in to the wire. Once you have the joint saturated with solder, remove the solder first, then the iron, then let the joint cool. Once the joint is cool, slide the heat shrink tube up over the joint, and apply fire.
[MTCD  Android Head Units Q&A] avenant:
so basically the radio needs to have constant power, even if the engine is off and there is no key in the ignition and when you turn of the engine and remove the key, the unit needs to go into some sort of sleep mode, like when you press the power button on the unit, then it also goes into some sleep mode? well that's not the case with my car, when the key is removed, on my previous radio that came with the car, there was no power on the radio... I also remember reading some topic some time ago, about someone installing an extra battery in his car, so the android unit would always be in sleep mode so it would start faster, because android booting from powered off to on takes more then a minute, which is frankly annoying, which is also the case with my unit... also when android is in some sort of sleep mode doesn't it drain your battery constantly, then you also need to watch not letting your car parked for too long, that was also the reason I remember for the guy installing an extra battery for his android head unit.
[MTCD  Android Head Units Q&A] CadillacMike:
Excellent explanation of how to solder
[MTCD  Android Head Units Q&A] avenant:
Today I tried your newer version of the app, but it still crashes, by crashing I mean, it does nothing when you click the icon, it just displays a message dialog: settings stopped, and then you can press ok,(this dialog is in dutch because my android language settings are set to dutch) it does not open the original android bluetooth settings

I removed the radio from my car and connected it again in my home to a power supply, is there some way to emulate the behavior of the ignition key when it's connected to a power supply?

about the "add-a-fuse" and not connecting the battery without a fuse, there is a fuse on the back of the radio already, just below where the iso connector connects to the radio
[MTCD  Android Head Units Q&A] doitright:
I may have missed something then... is your unit not a Joying N2?

Yep. Connect black to -, connect YELLOW to + (always on), and then HOLD the red to + (ignition on), and when you want to simulate ignition OFF, remove the red from the +.

NO!!!!!

That fuse on the back of the head unit is PERFECTLY USELESS!!!

You MUST not rely on it. EVER!

Think about it; how much wire (by length) do you need to reach from the closest power junction or battery to the back of the head unit? 3 feet? 6 feet? That ENTIRE length of wire is UNPROTECTED. If that wire SCRAPES against anything that is SHARP METAL, the insulation (plastic around the wire) will eventually wear down and allow the wire to SHORT OUT against that piece of metal!

---------- Post added at 03:07 PM ---------- Previous post was at 02:17 PM ----------

Yes.

Well, depends on the radio. On the older ones, they didn't go into a sleep mode, but rather, when they sensed that the ignition was off, they would first delay for a few seconds, and then initiate a system shutdown. Obviously, it will still be consuming power until it has completed that shutdown, so you can imagine that it will consume power for roughly 15-20 seconds beyond ignition off. When the ignition goes back on, it sends a powerup signal, so it starts booting up.

Note that the fact that you are unable to TURN ON the radio, does not imply that there isn't a live power supply wire running to it. It just means that one of its on/off switches is off.

Think of it like this;

You have the main power wire running into the radio, that is a bigger wire, capable of delivering enough current to power the whole thing, speakers and all. On that wire, there are TWO switches wired in SERIES. If EITHER of those switches is off, the radio won't turn on. One of those switches is connected to the power button on the front of the radio. The other of those switches is a RELAY, and that RELAY is triggered by the IGNITION switch. So the ignition switch ends up being a low current signal to switch on the relay.

You mind if I ask what kind of car you have?

Those radios that he was making up that hack for *did not have* a proper sleep mode. It was either ON or OFF, and his hack was to keep it ON. He would initiate a PARTIAL power down, by turning off the tuner and screen, but it would still be on.

Now THESE units seem to have a more proper sleep mode.

Consider a half decent Android tablet. Turn off the wifi and the screen, and just let it sit there in DOZE mode, how long does the battery last? A month? Two months? And those batteries are TINY compared to the battery in a car, which would probably keep them dozing for a year or four. Well, that is assuming that the battery doesn't NATURALLY discharge itself over time (which it will). Even after that tablet has been dozing for a month, when you press the power button, how long does it take to come up? Maybe half of a second? That *appears* to be what these new Joying units achieve.
[MTCD  Android Head Units Q&A] KamaL:
Before knowing these android units, I was trying to build something similar using a 2012 nexus 7.

There are specific ROMS (like Timur roms) with USB host support and Sleep modes using PowerEventManager. Basically the tablet goes into sleep mode with airplane mode and very low power consumption until the next time you turn on the ignition, and then the tablet wakes up instantly. This way the tablet usually can last a few days with the built in battery, and then it charges while the car is on.

I don't know if joying are using this, is there any battery inside these devices? For me olif it can keep the unit in deep sleep mode for 30 minutes effectively it would be great. Booting up each time I turning off the car for a few minutes would be irritating.
[MTCD  Android Head Units Q&A] avenant:
No I have an Isudar unit.

A 2010 Toyota Aygo.

On my Aygo when the ignition key is turned off the unit just instantly powers of, like you would pull the power cord from the unit. it doesn't go into a sleep mode.

Anyhow all the fun seems to be over now, because I managed to short circuit the unit, when trying to simulate the ignition key when it was connected to the power supply I touched the + with the - now it doesn't work anymore lol.

and you where right about the fuse on the unit being useless, it didn't prevent the unit from short circuiting lol
[MTCD  Android Head Units Q&A] DonJuma:
Hey guys.

I have the newer version of this unit that shipped with Android 6.0.1.

I've been looking into rooting the HU. I noticed the exploit that was posted a few pages ago but I'm concerned that it

will not work on my HU since it is on a newer version of Android. Can anyone shed light on whether or not this will work.

If not, are there any exploits for Android 6? It is the same unit (Bonroad) with Intel CPU and 2GB RAM.

I'm available to help get data, pull firmware, etc.. if you tell me what you need.

Thanks! :)

*edit*

Not sure how to add images to the post on XDA but here is a link to the photos I took. Including the about screen. I noticed that I also don't have the 'factory settings' that everyone seems to be talking about. The settings app seems pretty stripped down and bare..

imgur dot com /a/4dmtC
[MTCD  Android Head Units Q&A] doitright:
That would explain it.

Blueballs.apk is intended *specifically* to address the Joying N2 situation.

Toyota is pretty standard with the wiring. Of course that one is some kind of joint venture unit with Citroen.... so who knows who was responsible for the wiring.

My guess, is that yours is one of those units that I read about on a russian forum that have their red and yellow wires reversed.

What kind of power supply did you have it connected to? Is it possible that you cooked the power supply rather than the head unit? If you're pulling the power from your car, it *probably* has a radio fuse on one of its fuse blocks.
[MTCD  Android Head Units Q&A] avenant:
to a 2 amp 12v power supply for a led strip, at first I also hoped the power supply was cooked, but little chance because the bleu led of the power supply was still on, so I connected it in my car again, which to no surprise also didn't work.
[MTCD  Android Head Units Q&A] doitright:
Well that sucks :(

Try harassing the manufacturer, say it was dead on arrival.

If they tell you to suck an egg, then you could try opening it up and maybe see if you can find anything that is obviously fried.

I'm still unclear on what happened though.

You said "I touched the + with the -" -- if you did THAT (at least the way I picture it), then that would just short circuit it out BEFORE the head unit -- it shouldn't actually hurt it.
[MTCD  Android Head Units Q&A] CadillacMike:
here you go http://imgur.com/a/4dmtC
[MTCD  Android Head Units Q&A] twokidsandaphone:
Are you sure this in an intel? The CPU and MCU looks strange. I have an Intel unit from Bonroad on my front porch from DHL today so we will see...
[MTCD  Android Head Units Q&A] DonJuma:
I originally thought it was intel but after posting this earlier today at work, I started having second thoughts. I'm thinking I missed a portion of the "about" from the settings in my photo.

After work, I'll go down to the parking lot and make sure I took a photo of all the information. In case I can't find anything more, is there a way to check the architecture without opening the unit? I recall there was some confusion at the start of this thread regarding the authenticity of what some apps are reporting as the CPU type.

I'll dig around for some app on the play store that can offer this information and I'll post back.
[MTCD  Android Head Units Q&A] ikerg:
Bonroad intel units are based on mtcd mcu so...it is clear that you dont have a mtcd type unit according to the images you posted.

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] avenant:
on the iso connector that goes to the radio, the + and - pin on the iso connector are only like 2mm apart, the red and back wire pins, so I pulled the red wire, to emulate ignition being off, when puling the red wire I touched the iso pin of the black wire, and saw a little spark on the - pin.
[MTCD  Android Head Units Q&A] apollo1976:
Hi avenant,

from personal experience if you did touch the red cable with the black and then the radio stopped working, you have not broken the radio but the problem is the car fuses.

Check the fuse that controls the radio and surely you will find it broken.

I hope I have helped you.
[MTCD  Android Head Units Q&A] twokidsandaphone:
It sounds from this like you short circuited only the power supply side, not through the radio. You are talking about the pins at the 8 pin/5 populated connector, correct?

I got my Bonroad Intel yesterday and bench tested it. I thought it was dead on arrival but after a little bit of investigation I found that in the power harness supplied with the radio that the red wire (acc) was either not making good connection with the pin in the connector that actually mates to the radio or the pin was not pushed forward enough. Once I fixed that the radio sprang to life.
[MTCD  Android Head Units Q&A] avenant:
Today I connected it again just to try and see what happens, this time I used a breadboard to avoid problems and to my surprise and relief it worked again.

On the breadboard, it was easy to simulate the ignition, when the red wire is removed it goes into sleep mode, so that works, and when connecting the red wire again it almost instantly starts again, and the red and yellow wires are not switched apparently btw, so the problem about when turning ignition in the car the unit powering off and rebooting is related to the car wiring of the iso connector in the car apparently. that sucks, so then it comes down to what you posted earlier:
[MTCD  Android Head Units Q&A] joshnat:
Here's a new on on my Joying JY-VL130N2 2gb Intel: no volume control. I don't know if it's been like this since I installed it, but I just noticed it yesterday. Audio is either on or off. Volume knob evokes the volume pop up, but no change in sound. So sound is either on or off (when volume is at zero). I've poked around the CarMediaSettings and can't find anything that seems to affect this. I'm inclined to do a factory reset and start over, but is there even a way to do this with these units? I think I'll try the newest Joying firmware first and see what happens.

Edit: did a factory reset from Settings>Backup & Reset after updating to the December 8 firmware. Volume control works! Interestingly, Google voice typing has been removed from the ROM. I need to research how to add it back.
[MTCD  Android Head Units Q&A] avenant:
How about Tasker with Autovoice, it's much more powerful then Google Voice, and let's you do just about anything with voice commands.... Control your home automation etc...

And If some google apk's are missing which you cannot install with the play store, try apkmirror
[MTCD  Android Head Units Q&A] twokidsandaphone:
I did an update to my Bonroad intel unit using the link in the 1st post. I worked but it still lists as a 9-22 update (not 10-xx) as I was expecting.

Also since I am new to MTC type units (others I have are Newsmy Carpad IIIs) is there a way to change the default music app? I had no issue installing Gone Mad Music Player but it would be nice if the source button switched to it rather than the stock music player.

I also have the issue with GPS taking a while to find a lock. I have only bench tested so far, so I am indoors but it takes many minutes.
[MTCD  Android Head Units Q&A] wanb1i:
This sounds good, I'll give it a try and post back the results.

Looks like a lot of work and very time consuming.
[MTCD  Android Head Units Q&A] joshnat:
[MENTION=6124077]doitright[/MENTION] could you write an app like blueballs to access accessibility services for apps? That also seems crippled in the Joying settings.
[MTCD  Android Head Units Q&A] avenant:
AutoMate is a nice launcher replacement which is basically the same as Google Auto, but with a lot of extra features and with Torque integration, and let's you configure custom music player, navigation etc..

and with this program: Ownice RK3188 HeadUnit you can configure a custom music player that auto loads on startup and starts playing music when you power on your head unit, even though it says for rk3188, it works fine on intel units...
[MTCD  Android Head Units Q&A] twokidsandaphone:
Thanks! I'll give those a try when I manage to get it installed.
[MTCD  Android Head Units Q&A] MMTK84:
Use Nova Launcher to create a shortcut to *any* possible item in the "settings menu" (shortcut to BT or dev.settings or ....)
[MTCD  Android Head Units Q&A] usa911g:
clock

Hi,

sorry my bad English

I have installed the Joying intel 2GB Ram 5.1.1 unit , The time display on startup shows the wrong time,I have manually set up date and time. but when Cold start or manually restart the unit shows the wrong time

but if unit get the GPS Signal ,the time will auto update correctly

(PS:My car is parked in the basement)

Any ideas on what the issue may be?

or This is a normal condition

Thanks,
[MTCD  Android Head Units Q&A] doitright:
Better option at this point would be to properly replace System Settings with a non-broken version of it, rather than continuously trying to hack around stuff that they screwed up.

---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------

Timezone.
[MTCD  Android Head Units Q&A] KamaL:
Is it doable? Or Joying has to do it in a firmware upgrade?
[MTCD  Android Head Units Q&A] usa911g:
I have set the correct time zone but after Cold start or manually restart the unit shows the wrong time
[MTCD  Android Head Units Q&A] doitright:
We might even have a copy of a non-broken system settings that is ready to go.

Funny thing about the update package;

The update process goes like this;

1) Update MCU,

2) Update Android,

3) Install a bunch of china from a file called AllApp.pkg.

AllApp.pkg contains the broken System Settings.

I'm not exactly sure what System Settings are included in the Android update, but it might be properly built from AOSP. After all, why would they replace it if it already had their broken copy?

---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------

If the clock stopped when you turn it of, it will need to synchronize with either data network or gps before the time will show correctly.

---------- Post added at 03:48 PM ---------- Previous post was at 02:54 PM ----------

This is confirmed.

I just ran a diff on the SystemSettings.apk and SystemUI.apk. All of the UGLY is the one from the AllApp.pkg. The ones from the Android update are more or less AOSP.
[MTCD  Android Head Units Q&A] joshnat:
Agreed. Please let us know how to do that when you think you've got a solution. I saw your later post about the diff of the settings apks, but don't know how to action it.
[MTCD  Android Head Units Q&A] doitright:
Well, you could try just copying it in.

adb connect <ip address of head unit>

adb root

adb connect <ip address of head unit>

adb shell

# mount -o remount,rw /system

# exit

adb push Settings.apk /system/priv_app/Settings/

adb shell sync

adb reboot

Now, there is not guarantee that this will end up working perfectly, I did see some added code that looks like it might be messing around with sound systems actively. Not entirely sure.
[MTCD  Android Head Units Q&A] joshnat:
OK, I will try that. If it ends up crashing settings, do you recommend a reflash, or do I just do the same push with the Joying file?
[MTCD  Android Head Units Q&A] doitright:
You should be fine just by pushing back the original file. Which reminds me to remind you... pull it first, because it is not trivial to extract it from Allapp.pkg.

Remember that you are pulling the "normal" file from the Dec8 update package.

5009_20.zip/system/priv_app/Settings/
[MTCD  Android Head Units Q&A] joshnat:
I wonder if I could do all this with a root-enabled file manager? Backup the original file, paste in the AOSP file, set permissions, reboot?
[MTCD  Android Head Units Q&A] doitright:
Why make things hard for yourself when you can use adb?
[MTCD  Android Head Units Q&A] joshnat:
No good reason, I've just been finding that the adb shell is sort of slow when I go in over wireless, especially since the unit is installed in the car already. Also, I like GUI!
[MTCD  Android Head Units Q&A] doitright:
You still have to get the file to the car.

gui's are... imprecise, and cumbersome.
[MTCD  Android Head Units Q&A] joshnat:
It worked! Full settings available now.

I wonder about SystemUI? Not gonna mess with it without your guidance.
[MTCD  Android Head Units Q&A] doitright:
Cool! How about overall radio functionality? Does it look like anything becomes broken?

You should be able to do SystemUI the same way as Settings.

Edit: But try to go over the system with a fine tooth comb to test out the Settings change first, so that if anything goes weird, you know which package caused it.