yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units Q&A] agentdr8:
If you'd rather look at java code instead of smali, the decompiled MTC apps (from 4.2.2) are on the FTP server. The Android<->MCU communication is done via serial port.

---------- Post added at 09:05 AM ---------- Previous post was at 09:03 AM ----------

It's been on my list of things to-do for XposedMTC, but I haven't had time to work on it. Been busy trying to update my other xposed modules for Lollipop.

I'll get around to it eventually.
[MTCB Android Head Units Q&A] clearchris:
Me too. It was hidden away in the Misc directory... go figure.

Do you know the linux device name of the serial port?
[MTCB Android Head Units Q&A] v1ks:
Yes that's the great thing is that maps are available off line and it gives you option for route as well like Google maps.
[MTCB Android Head Units Q&A] typos1:
Youre the second person to have a "KYD" unit, this is a new manufacturer (or somoene mis-spelling "KLD" at the factory/developers ?).

As someone has mentioned a powered USB hub should sort both your problems.
[MTCB Android Head Units Q&A] Us-Marshal:
Open letter to the EEs participating in the thread.

I've been tinkering with this as well and I've seen/read posts about battery drain risks of extending the 'sleep', but cannot understand how these could use SO much more power than a tablet in stand-by. My car battery has way more capacity than a 3000-5000mah battery in my Android tab, so why the difference?
[MTCB Android Head Units Q&A] jonny80:
Can´t get spotify to start early on my unit.

My install-recovery.sh looks like this:

while ! am startservice com.spotify.music/com.spotify.music.MainActivity ; do sleep 1; done

sleep 2

while ! am startservice com.petrows.mtcservice/.ServiceMain; do sleep 1; done

sleep 2

while ! am startservice com.keisersozey.carservice/.SwcMusicService; do sleep 1; done

sleep 2
[MTCB Android Head Units Q&A] agentdr8:
I believe it's dev/ttyUSB6

I'm not an EE, but maybe it isn't just the android portion that's drawing power when in "sleep". I haven't tested anything, but it's quite possible the internal amp is also powered, even if it isn't actively amplifying any signals. On top of that, the android side isn't optimized for power savings, since the concept of a small battery doesn't really apply. Things like always-on GPS tend to keep devices awake, and draws a bunch of juice.
[MTCB Android Head Units Q&A] Us-Marshal:
I have some work to do installing another outboard amp when it warms up a bit and will try to remember to do some current draw tests to see what it is when the HU is on, off and during the 30 sec. 'hold' after 'powering off'. Should be interesting if nothing else.
[MTCB Android Head Units Q&A] clearchris:
Thanks!!

Also not an EE here, but I'll chime in anyway. ;)

I'd be curious about the difference in draw when the unit is on and when the power button has been pressed. I don't believe the power button (short press) actually turns it off, but sends the unit into a sleep mode.

Anyone have a DC clamp meter to check the draw in both states?
[MTCB Android Head Units Q&A] clearchris:
You know, depending on how KEY1 works, I don't think it would really be bad at all to make a piece of hardware to do this. Instead of opening the unit, you could program the external device to emulate a button, and in android program the button to be the power button. Add in a relay for cutting ACC and that's all you would really need.

With that, you would get the unit to turn off when you take the key out, and (depending on power use) have it turn off cold after an amount of time, or by schedule.

I love simple solutions.

Edit: I rode in silence for 5 mins after hitting power off. When I hit power again, it came back immediately and complained about google location something crashing. If I had to guess, I'd say the GPS is turned off when you hit the power button.
[MTCB Android Head Units Q&A] eh-jhey:
can I just downgrade back to 4.2?

Alright...so I'm in a bit of a situation. If possible, I'd like to go back to 4.2 from 4.4. I updated and it's just taken too much functionality out of it for me. Firstly, the buttons are quite messed up. the home button opens the video player and the back button changes the eq and etc.....also, I can't receive any radio signal in Canada. Yes the antenna is plugged in. Was working perfect before updating. I mean, besides those it seems "okay".. but I really need my radio working.

For reference, I've got the eonon g2110z which is a JY type to my understanding. I used this package to update http://xdaforums.com/showpost.php?p=58254234&postcount=7628.

Can anybody just provide the files and possibly guide me through downgrading back to 4.2? unfortunately I didn't make a backup. Wish I had, but can't happen now so....

Any help would be appreciated.
[MTCB Android Head Units Q&A] clearchris:
Sounds like you need to run through all the settings. When I upgraded, it was setup for russian radio band, etc

I have the same model, mine is a KLD. So unless they changed supplier, id try a different rom. Btw, the kld 4.4.4 on the repository is really 4.4.2. I used coudas kld 4.4.4 rom and it works great.
[MTCB Android Head Units Q&A] eh-jhey:
Ya that was my first thought too. when I checked the radio frequency settings in factory options it was defaulted for china. I tried America 1 and America 2 as well as europe and none of them work :(
[MTCB Android Head Units Q&A] koimr:
There should also be a "Radio" drop-down in Factory Settings. See if that's the problem. I know when I changed mine (was playing around) I got nothing but static until I put it back to the correct one.

Sorry for the horrible pic:
[MTCB Android Head Units Q&A] clearchris:
You responded quicker than my edit above.

I have the same model, mine is a KLD. So unless they changed supplier, id try a different rom. Btw, the kld 4.4.4 on the repository is really 4.4.2. I used coudas kld 4.4.4 rom and it works great.
[MTCB Android Head Units Q&A] eh-jhey:
alright, saw the original g2110 listed as JY so I used that, but I'll give the kld a go. Wasn't able to downgrade back to 4.2.2 anyway. just stayed as 4.4.4 :/ I'll let you know how it goes in a bit
[MTCB Android Head Units Q&A] clearchris:
It took me four tries to make it stick. Use a freshly formatted SD card, formatted on a windows box at fat32.

If it reboots quick, it didn't go, try again.
[MTCB Android Head Units Q&A] eh-jhey:
well just tried it, I think the kld rom itself flashed because the launcher changed, however still had the same button and radio issue. Also, in MCU version it says MTCB-JY-V2.11 and model S07. Are you sure we have the same unit? I mean shouldn't it now be showing kld if it really was? I just flashed the kld mcu after all (I think I did). That said, I haven't formatted the whole micro sd yet...
[MTCB Android Head Units Q&A] typos1:
If you flashed a KLD MCU onto a JY unit then youre lucky you havent bricked it, as it says on the first page ONLY the Android side is interchangeable between units, the MCU isnt - you cannot change MCU manufacturer, if you have a JY you can only use JY MCUs.

You will have only flashed the MCU of you put the MCU.image on the sd card as well. What sd card are you talking about formatting - the internal one or the one youre using to update ?

The MCU controls the buttons and radio IC, not Android, so it doesnt matter which version you flash or from which manufacturer, go into factory settings and play about with everything, including key and button maps and as clearchris says, also try changing the radio IC version.
[MTCB Android Head Units Q&A] nrjdgn:
What news on KLD2_KK444_800x480_150113_root_mod_boo_

2015-03-04

_v1.0.0
[MTCB Android Head Units Q&A] eh-jhey:
Ya that's what I was thinking and had me worried as well. I was surprised it didn't brick myself. however the fact that the settings still says it's a JY MCU might have something to do with that no? I'm gonna have one more go at messing around with the factory settings.

if there's anyone in Canada that can tell me exactly which radio settings they use that works, that would be great lol
[MTCB Android Head Units Q&A] tolymatev:
I have the same device and its a KLD.

Just saying
[MTCB Android Head Units Q&A] eh-jhey:
ugh...well that is the same serial batch as mine so that seems most correct. I guess they switched from JY after the original g2110 for the g2110z. And I'm also guessing that the 2.40 mcu isn't available. I'll try one of the other versions

*update*

so I flashed Coudu's 4.4.4 for KLD and KLD MCU 2.21. The buttons at least seem to be working properly now. Radio is still down, but I've only gone through a couple of the settings so I'll try again after work or on break. Really wish there was a nice list that detailed what settings to use for what country :(

Also, do I really need to reboot every time I change the radio settings? not that big a deal, just asking
[MTCB Android Head Units Q&A] typos1:
No you do not have the same device if yours says KLD in the MCU entry - you have a, surprise, surprise, KLD, thats why it says "KLD" !

He has a JY thats why his says "JY" !

This front is used by all the manufacturers of these units and on many, many more Chinese head units of all different types, Android (including the AN21-U, the Ownice C200), Win CE and non OS types, its a generic front.

They are not the same serial batch, they come from entirely different factories and are made by different manufacturers, Eonon is simply a re-seller, they buy them, put their stickers on the front and sell them on.

There doesnt need to be a detailed list of what settings to use, its obvious, pick your area from the list, that is all that is needed. Have you tried the radio type setting in factory settings yet ? This would be the nxst thing to try once youve changed the area setting. If that doesnt work I would check your antenna connection. also check that if you car has a booster built into the antenna you have fitted an aftermarket antenna power injector (so the booster gets power to work), if none of that solves your problem then take the lid off your unit and make sure the antenna is connected to the board.
[MTCB Android Head Units Q&A] eh-jhey:
oh I was aware that it was just a re branded unit, although I admittedly thought that the serial would have been a decent indicator. Guess not :/

I guess my issue was that there wasn't specifically a "Canada" setting. Just assuming it was one of the 2 Americas. So yes the next thing I was going to fiddle with was the Radio Type. When I re-installed the unit yest morning the antenna was okay. radio was working with the original 4.2.2. I May take it out again to solder it in but I'm fairly confident it didn't just pop out with as little driving as I did in a day.

Luckily the KLD mcu fixed the button situation at least so i'm less inclined to downgrade now since I normally listen to my own music anyway. Will report back if I can get the radio going
[MTCB Android Head Units Q&A] typos1:
Lol, Canada is on the continent of North America, the other America setting is for South America, the settings are for areas of the world, not specific countries - there are approximately 200 countries in the world, you dont expect a setting for each one do you !! ?

TBH I ve never compared serial numbers, but its irrelevant really as yours is a JY and the other poster's is a KLD, both from different factories.
[MTCB Android Head Units Q&A] eh-jhey:
ya I know they wouldn't have put every country. But the north/south america setting would have been nice :P either way it's only 2 to swap between so no big deal.

and I'm not so sure mine is actually JY anymore...since the KLD mcu is the only one that's gotten the buttons to work properly now...also, if he bought the exact same model from the same reseller, chances are he's on to something. I mean I know the original g2110 was a JY unit, but I know the G2110z had very slightly different specs..whereas the newest G2110zv is literally the same as unit as the z with upgraded software. That said, If there's one thing I can say about this unit...with all the flashing between different roms and MCU types, it seems pretty resistant to bricking lol. *knock on wood*
[MTCB Android Head Units Q&A] typos1:
Well, yeah, they could have named them North America and South America, but as you say, theres only 2 settings to try.

Youve got to forget about the Eonon model numbers, theyre totally irrelevant, the only thing that is relevant is what it says in the MCU box - who MANUFACTURES the unit - not who sells it, all Eonon do is buy then sell on. The ZV version is the same as the Z version its just that someone has flashed KK on it, this is all marketing rubbish, forget it and go by what it says in the MCU box.

If youve flashed a KLD MCU and things are working then its a KLD, not a JY, changing the MCU to a different manufacturer's version will mess it up.

I m confused how you can get your version wrong - what did it say in the MCU box when you first had it ? Have you read the first page ?
[MTCB Android Head Units Q&A] eh-jhey:
What happened was that I (noob mistake I know) solely went by the spreadsheet that told which version you had based on manufacturer and Model. That one only has the G2110 listed. At the time I guess I hadn't thought they they would switch models for the z. And yes I definitely should have checked the mcu in the setting menu first. That was my mistake, and the root of my issues
[MTCB Android Head Units Q&A] typos1:
The spreadsheet is correct, if you went by that then you wouldnt have made a mistake, the spreadsheet shows the differences between 3 of the manufacturers, there is no mention of re-sellers on the spreadsheet, there is no mention of "G2110" and no mention of Eonon, it just mentions manufacturers, not re-sellers, so I dont know which spreadsheet you were looking at. You do not have a G2110, you have a Klyde unit !

A few people have reported similar radio and button problems recently, I guess they ve all done what you did and flashed the MCU from a different manufacturer on their version.

The lesson for all here is : FULLY READ THE FIRST PAGE BEFORE YOU POST OR DO ANYTHING TO YOUR UNIT !

EDIT: just looked at the first page and Pakidermo has added a spreadsheet on Googledrive that I ve not seen before, this is for notes on experiences with firmware rather than to establish what unit you have, so I guess thats wheat you meant, I thought you were talking about the pdf which explains the differences between manufacturers. The pdf I was talking about is below the link to the spreadsheet.
[MTCB Android Head Units Q&A] letadlo:
Resolution

Can I install KGL firmware with 1024x600 resolution if my unit has got original firmware with 800x600?
[MTCB Android Head Units Q&A] nzdreamer55:
I tried this and it was not pretty. Had to revert. Could only see about 1/4 of the screen. The rest of the image was off the screen. Let me know if it works for you.

---------- Post added at 09:23 AM ---------- Previous post was at 09:17 AM ----------

This got merged but it is a different topic. I was trying to help the previous poster and also had a new problem that I wanted to post. Sorry for the confusion.

Cannot install apps from play store because I am getting out of memory error. I cannot figure out where the memory error is being generated from (not enough internal memory, not enough external memory, not enough working memory) as when I go to storage, it looks like there is enough space. The smallest memory space is the internal memory and I have 190 mb available.

Could someone point me in the right direction to trouble shoot this?

Thanks
[MTCB Android Head Units Q&A] eh-jhey:
ya it shows the original Eonon G2110 as MTCB-JY-V2.07 which confused me

but yes I'll admit my own misdoings. I did read the first post, but not as thoroughly as needed.
[MTCB Android Head Units Q&A] typos1:
Why would you want to do this ? The KGL 800x480 firmware is exactly the same as the 1024x6000 with the exception of the screen resolution/DPI.

Yep, address queries to Google, ask them why they made KK give not enough space errors for apps when there IS enough space, its a known KK problem, affects lots of devices, try using an app like AppCacheCleaner, or manually clearing app's caches, or re-parting so you have more space for apps. What version are you on, stock or rooted custom from here ?

Well at least we now know that the people who kept getting button problems and radio problems probably didnt bother to read things properly as well, so when we get people asking why they get button/radio problems after flashing firmware again, I ll know exactly what to ask first, so youre misdoings will help others :)

Just as I was about to buy the parts to make a powered hub. Can you re-post your solution as you say that the combination that works for you is NOT making use of the rear USB port, then you say that you use one of the rear USB ports for your USB stick.

I ve tried my stick in both rear ports and the front, nothing works, well 10% of the time music plays fine, but 90% of the time it cuts in and out, on my JY unit and my KLD unit.
[MTCB Android Head Units Q&A] alfeny:
Someone did the test and reported the results on an italian forum:

HU on and fully functioning: 900mAh,

HU in standby mode for 30 seconds after powering off: 230mAh,

HU totally off: 50mAh.
[MTCB Android Head Units Q&A] Us-Marshal:
Awesome. Thanks for pointing that out. Most car batteries are between 30-50Ah (amp-hours) so even on the smaller side of the capacity scale, at 230mAh, a 30Ah battery should have no problem sustaining the draw - with plenty left for starting, overnight.

Working from a number of assumptions and using quick/crude math:

230mA draw on a 30Ah battery would yield about 130 hours, but we dont want to drain a battery fully. The draw at 230ma over 24 hours is about 5.5Ah - not going to kill a car batter in a day, but sure could over 2-3 days. I'd say to make this workable in the real world, that draw has to be down at (or below) 100ma - and even then, dont let your car sit for 2 weeks while you're on vacation...
[MTCB Android Head Units Q&A] nrjdgn:
I have test KLD2_KK444_800x480_150113_root_mod_boo_2015-03-04_v1.0.0.zip

she have only disturbe of handbreak view detector on small pictur car is not displayed

The fonts are small

i have test only

https://play.google.com/store/apps/details?id=com.jrtstudio.AnotherMusicPlayer.Unlocker

It is a good music player
[MTCB Android Head Units Q&A] typos1:
You can adjust the size of the font.

---------- Post added at 10:14 PM ---------- Previous post was at 10:07 PM ----------

Hmm, I was using both leads on the KLD, I only remember having 1 USB on each, I ll have to check which I was using and see if I missed one.

My JY only has 2 rear USBs, on both the music cuts out every few seconds.
[MTCB Android Head Units Q&A] superlover911:
Klyde in GM/Chev

Anyone have any info for hooking up my head unit in my 2013 Silverado? Been through a lot of info tested and tried quite a bit. Cannot get steering wheel controls recognized. Canbus and harness that came with head unit did not come with any info as to what wire is what. The sticker on top of the head unit is pretty limited.

I have purchased a axxess module to allow SWC with aftermarket stereos. Cannot determine what wires are KEY1 and KEY2 going into stereo.
[MTCB Android Head Units Q&A] neno19852:
hi guys,

i make backup of my system(ga5153) with nandroid online in twrp format. it makes some folders and files, but now what can i do to restore this backup? it's not ".img" file.

help me please

thanks
[MTCB Android Head Units Q&A] pencilhead:
Hi,

I *think* the Silverado is same as Holden Colorado here in Australia.

My KLD unit harness plugged directly into car. I didn't have to do anything.

My canbus settings:

Navigate to:

System Settings\ Factory Settings (password 126)

Select Application Tab.

Canbus = 05 GM(Raise)

SWC work with this

Hope this helps :)
[MTCB Android Head Units Q&A] superlover911:
Thanks, I will give it a shot. I also have a kld. The can bus sent with the unit says Buick enclave. I've tried lots of the can bus settings in the factory settings. Seen YouTube videos where guys say they use an adaptor like access asw1 or PAC. Had my dash pulled apart 5 times now trying to get this workin! Any suggestions are more than welcome!
[MTCB Android Head Units Q&A] bhitman:
When these is correct, then it means, that the standby-mode is controlled by software!?

And than it should be possible, to enlarge the standy-time.

Very interesting...

Or am I wrong?
[MTCB Android Head Units Q&A] agentdr8:
By "standby", that's the time between the headunit losing 12V on the ACC line, and when it actually powers off. The MCU sends a signal which sends an intent to the MTCManager to perform a shutdown(), which kills off all processes, saves your last foreground app to settings, and then the normal Android power-off sequence. I believe this is a fixed time of around 30 seconds, and is controlled either by the MCU, or hardware (e.g. capacitors are used to keep the HU running until they discharge past a certain voltage).

If we had access to the MCU code itself, all sorts of good things could be done.
[MTCB Android Head Units Q&A] Tung_meister:
I'm not really familiar with android intents, could it be intercepted then resent by another process after a specified time?
[MTCB Android Head Units Q&A] s.tb:
Hi, I've been provided with the original firmware for KYD unit.

6.2 for 800х480, 7.0 for 1024х600

BUT I'm not allowed to share here external links.
[MTCB Android Head Units Q&A] clearchris:
I don't think you need access to the MCU to engage this. I suspect this mode is the same as when you manually press the "power" button on the unit. I also think you could enter this mode from tasker by sending a power down intent, or by emulating a button by using the KEY1 and KEY2 wires. I don't think you can send a command to power down the unit cold (50mah level) without MCU access.

I'm currently researching the KEY1 and KEY2 method. Here is what I have so far...

KEY1 and KEY2 provide 5v+, and are able to detect multiple levels of voltage, which is how you can have more than one key per line, as is described here:

http://www.instructables.com/id/How-to-access-5-buttons-through-1-Arduino-input/?ALLSTEPS

Now, with an arduino, you can also provide 0v to 5v+ through PWM, however, I can't hook that up directly, because they are both positive voltage. So, I think this can be done with a npn transistor as shown, but I'm trying to figure out how to smooth out the signal. Any ideas?

Edit: I think I had a fundamental misunderstanding of how key1 and key2 work. Plz disregard this post for now.
[MTCB Android Head Units Q&A] agentdr8:
It could, but then the device would just be in normal "on" mode. The intent is what starts the shutdown process.
[MTCB Android Head Units Q&A] Tung_meister:
Ah, I misunderstood , I thought you meant the intent was broadcast after the 30 seconds of "standby" time to shut it down.
[MTCB Android Head Units Q&A] agentdr8:
The power button does different things on different units. If I short press the power button on my GS, I get mute. On my KGL, it's a Back key. On both, if I long-press it (for more than 2-3 seconds), it starts the shutdown process. There is no "sleep" or screen-off, like you would find on an Android phone/tablet.

You can either send the same intent that the MTCManager sends to initiate the shutdown (action: com.microntek.bootcheck, extra: class = poweroff), or you could call the shutdown method directly using reflection or Xposed (MicrontekServer.PowerOffAction()).
[MTCB Android Head Units Q&A] somereta:
Music Info

I have a question. When you play music by bluethooth you can see the name of the song, album etc on the radio? Because I have a z1 and I use PlayerPro music player and I see nothing on the radio. I have a kld 2.20 and KGL 4.4.4 800x480 150115 rooted light. Thanks for everything :)
[MTCB Android Head Units Q&A] clearchris:
Interesting. So if you do the long press it shuts down completely? Are you 100% sure? So if you wait 2 mins, then hit power again it takes 30 seconds to boot? Mine comes back instantly, though it said it was shutting down, it doesnt really.