yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units Q&A] ptclabs:
4.4.2

I just tried 2 version on my GS 1.91 with RM 4.2.2 firmware.

First attempt gives a failed to load / reload metadata error, it reboots again and just says no command and loads the bl

Second attempt tried with 2.08 GS and another 4.4 image same result

I a wondering if it is caused by using the rm firmware as it messes up the internal SD and you have to reformat it when you install RM. any other ideas?
[MTCB Android Head Units Q&A] agentdr8:
No, just remove it from the list of additional sources that are switched with the mode button in XposedMTC preferences.

So the problem with the dimming is that not all units offer the same dimmable range; some devices have backlights that can turn completely off, others will only go down to 10. I have plans to add a screen blanking mode, much like Screen Standby, that'll turn the screen off until you touch it.
[MTCB Android Head Units Q&A] ESTIMULO:
Thanks but it doesn't get root
[MTCB Android Head Units Q&A] R4D3N:
I have just installed the KK 4.4.2 Pre-rooted + V1.86 MCU on my BMW E46 unit

At the first install it got stuck in a bootloop. I reflashed it again and now its working.

Now, the Xposed module is working correctly (before, on 4.2.2 I could not get it to work), everything moves very fast, sound and radio seems a bit improved and I like the new Menu style.

Downsides:

-when I press the Mode button, it appears the logo on the screen and it gets stuck and it is only working after I press Reset button (I checked all the modes manually and they are working)

-the Music application, as in other versions, I would like that somebody makes the song list larger (exactly as in previous 4.2.2, the MTCMusic List Style)

-boot time, is around 35-40 seconds

All in all, I am happy with the update. If I could fix the above bugs it would be awesome.
[MTCB Android Head Units Q&A] bourdier:
My first post here, and must said thanks for all the hard work....

I received this unit on Friday

http://m.ebay.com/itm/191377437325?_mwBanner=1

Was installed on Saturday and today updated to OK with the image with the today's update, that was awesome guys thanks for that.

Below some pictures.

Thanks, really appreciate.

Bourdier

Edit: Sorry for the bad quality images.
[MTCB Android Head Units Q&A] agentdr8:
If you have Line-In (AUX) added into the sources that are part of the modeswitch, I believe this is causing a system crash. Try removing it. If that doesn't work, disabling mode override should resolve that until I can fix it.
[MTCB Android Head Units Q&A] R4D3N:
The MODE override is disabled. Should I enable it and disable AUX from there?

If I press on the AUX app it works, though.
[MTCB Android Head Units Q&A] Danielitoss:
Hi,

Does the KitKat release allow bluetooth or usb tethering ?

It will be nice to see on the 1st post, the tethering subject, capabilities and workarounds.

Thanks

---------------------------------------

Erisin 9781XX, (4.2.2) KGL V2.03
[MTCB Android Head Units Q&A] reecho:
Thanks to all that have shared the latest KK 4.4.2 images..!!...:svetius:

I have a GS unit (using 2.02 mcu) and have got everything to work including TomTom with the 4.4.2 non rooted image. My only issue is with the bluetooth. I use a OBDlink MX bluetooth dongle in conjunction with Canion, an android app which monitors Mitsubishi's I-Miev electric car as well as it's cousins in Europe.

While the dongle is detected and appears to pair, the app asks to turn bluetooth on. BT hands free and streaming audio work fine. this worked ok with 4.2.2. I would dearly love to stick with 4.4.2 if i can. A great step up.

I have contacted the developer and advised the issues. Can anyone shed some light on whats happening?
[MTCB Android Head Units Q&A] buccaneerbob:
I don't think there is any Android bluetooth stack included in the 4.4.2 build. I tried copying over the missing lib's and bluetooth.apk from 4.2.2 but it just kept crashing. I'll try using the files from another 4.4.2 build.

The MCU bluetooth side is working fine, it's just that Android doesn't know that bluetooth exists.

Maybe they are still working out the kinks in their bluetooth implementation on KitKat.
[MTCB Android Head Units Q&A] ptclabs:
4.4.2

I got it working on the GS. You cannot go RM directly to 4.4.2. Had to put a klyde rom on it.

It works but the google now launcher will not. I added another launcher from play store, and when restarted I lost my touchscreen. Had to reflash again to get it back. I did not try a mouse though.
[MTCB Android Head Units Q&A] tomato18:
Edit: nvm, didn't realized it was already replied earlier. [emoji14]

Yes u can rearrange it. First touch on the right app button. Then touch and hold the icons rearrange or remove as usual.
[MTCB Android Head Units Q&A] agentdr8:
If the override is disabled, it shouldn't be modifying (or even hooking) the ModeSwitch() method at all.
[MTCB Android Head Units Q&A] neo_u:
Hello.

I have some strange issues with micrpophone.

If I'm close to it, it's fine and everyone can hear me, but if I'm sitting driving and can't move close to the microphone caller can barely hear me.

I tried to use Micrpohone app with no luck. Maybe someone can suggest something else, without hardware changes or modifications.

I mean, I can connect external microphone, however, maybe there is a solution without hardware changes :)

Thanks in advance...
[MTCB Android Head Units Q&A] pascaltd:
Hello, is it possible to have for mercedes MTCB-KGL1-V2.09.rar , thank you
[MTCB Android Head Units Q&A] kwalsh24:
What kgl mcu version is this? There's 4 different kgl versions per build which can effect the physical buttons on the unit.
[MTCB Android Head Units Q&A] Warlord711:
I might try it today, since 2.09 MCU gives no benefits compared to 2.03 (same 3-time SWC button bug, only marginal CAN BUS for Volkswagen <2009 ).
[MTCB Android Head Units Q&A] zorantoma:
Its mcu4 and there are 6versions by the way.For me is not working on es9401a
[MTCB Android Head Units Q&A] kwalsh24:
Oh, sorry last I seen there were only 4 mcu update files. Will give it a go on my unit and see what happens as v4 in the past typically worked.

Tried it, mustn't be version4 as it messed up my buttons, volume up is now Bluetooth
[MTCB Android Head Units Q&A] parazit26:
you can try a parrot microphone. i had the same issue and a new parrot microphone solved it.
[MTCB Android Head Units Q&A] pakidermo5000:
Great ! Did you have to do any workarounds to get TomTom to work? Someone was having problems a few posts ago.

Some issues I found:

- I noticed a "temporary freeze" of the touch screen until the GPS is positioned. Isn't there any way to overcome this with a xposed module ?

- Volume of google maps is terrible loud compared to other apps. Actually, in general the volume is very loud (I have to set it to 7-8).

- Loud on boot did not work for me. I will make some more trials.

- Automatic date/time set does not work either, it gets the wrong time.

- XposedMTC dimm does not work for me (it did not work on the old firmware either). The lowest brightness level is very high, I have to use "Darker" app to get the screen darker.

Someone said they could not change the apps in the front. To do this, you have to tap the "car" apps, then you can move the ones at the bottom.
[MTCB Android Head Units Q&A] typos1:
Whats the difference between the KGL and KLD versions, just the homescreen ?

Whats the actual problem with the screen res ? I put the first I KLD KK update I was given on mine and it turned out to be the 1024x600 version - the bottom on right side of the screen were cut off. Are you saying that the KGL 1024x600 is set to 800x480 depsite having a 1024x600 screen ?

Any chance you could make an 800x480 version of the KGL KK ?
[MTCB Android Head Units Q&A] ESTIMULO:
I hope you got it. Please share with us!

Thanks
[MTCB Android Head Units Q&A] neo_u:
I can. But, do I need to take off the device and make some hardware adjustments? I mean, can I just connect external mic?
[MTCB Android Head Units Q&A] typos1:
This post from 4pda.ru

http://z5h64q92x9.net/tr-url/ru-en.en/4pda.ru/forum/index.php?showtopic=557670&st=6120#entry35827736

Hows that are less files in KK for BT than in JB, also something in buildprop is set differently, maybe this will help people with BT OBD issues ?

(wait for the page to load a few seconds, its via a tranlation site)
[MTCB Android Head Units Q&A] bourdier:
After Update to KK Google Maps is very slow in navigation, is like the navigation stop then continue and then stop and continue.

Below a video

http://youtu.be/rsNhVJ3APAo
[MTCB Android Head Units Q&A] agentdr8:
I'll try out the build.prop edit later tonight and see if that bricks it ;)

I only notice this touchscreen delay right after the system boots. The boot time is much quicker than the JB image, even with the few seconds delay before you can touch anything.

Try playing with the audio levels in the factory settings app. Sys is all Android sounds. I have mine at 0. If that's still too loud, try adjusting the master volume knob in Poweramp EQ.

Ever since around the 1.86 image, the Loud setting in the amp seems to persist reboots for me. I no longer need to toggle it on via XMTC.

You mean automatic date/time from GPS? Or via wifi? I usually uncheck all the options in Date/Time, and adjust the clock and timezone manually, then enable the GPS time option.

Does your headunit have a DIMM button?
[MTCB Android Head Units Q&A] pakidermo5000:
Yes, I notice it only after boot. Agree, boot time is much faster. But I do not see the point on freezing everything for just the GPS location...

Thanks, this did the trick. With the previous version I had it at 12 and it was fine..

Ahhh true, I will try again and let you know.

Both, I tried with both and none were accurate. I opted for your solution as well...

no, no dimm button. Is that related ?

I have a tasker task that turns on darker app and modifies its value every 10min to a darker or lighter depending on the time of the day. It is not ideal, but it works.

I will play a bit more with the unit tonight, and see if I find more solutions/problems

cheers!
[MTCB Android Head Units Q&A] webdude12:
From what I have seen report there are a lot of subtle differences.

Launcher

Radio App - While they look similar, there are several minor differences in the design. I have had zero problems with radio reception, RDS, etc working in the US.

Bluetooth Menu - I have full bluetooth android menu. I have paired everything from my OBDII adapter to my Beats Audio Pill to my Roku that thats in my house without issue.

My idea to provide a root only update will not work with Rockchip like it works with others. The Rockchip firmware requires re-writing the entire system partition. My idea was to take the KDL update image, and strip everything out of it. Add back the files for root and modify the build.prop to make the unit resemble a Galaxy Note 7" This works on some of my other devices, where you can tell the firmware to append files, and not re-write the whole partition. Just not an option on the Rockchip

Looks like I will have to wait for the KGL 1024x600 update image to do that.
[MTCB Android Head Units Q&A] genge:
Regarding rds do you have station names?. Thanks
[MTCB Android Head Units Q&A] agentdr8:
Not exactly, but I'm using the same method that the dimm button calls to do brightness changes. It should be the same method that's called when it detects your running lights are turned on (via the illumination wire). Does your headunit dim when your lights come on?
[MTCB Android Head Units Q&A] kavo77:
Hi,

I've just read this entire thread so I have a few questions.

which apps have limitations with the 800*480 screen?

Whats the benefit of pure android?

I found this quad core with WInce and unsure of the benefit of android only units

aliexpress (dot)com/store/product/TOYOTA-Corolla-EX-Android-Car-DVD-Navigation-Android4-1-dual-system-multi-point-touch-capacitive-touch/432439_1139125630.html

or is it just a fake listing?
[MTCB Android Head Units Q&A] Vladimir2k9:
But on this video, or the other same we can see that it have android 4.1.1. And I can not find truth about android and processor in it. You can see table in my post in up, also manual and other videos.
[MTCB Android Head Units Q&A] kevinnku20:
I'll leave the resolution question to those that are more familiar with the topic. I have owned both a win ce and an android unit, and the major benefit of android is access to apps. If you're just looking for a radio that just works* and is limited to built in functionality then win ce is for you. However, if you want to customize and tinker you're going to be very disappointed with a ce unit. Unless of course, you are a developer that knows how to write ce apps.

There are merits to both options but for me, I found the ce units to be far to limited for me.

*by "just works" I mean works as well as a rushed to market with less than adequate quality controls can "just work".
[MTCB Android Head Units Q&A] 1-2-Hak:
Just spent some time doing some optimisation.

On a clean factory reset install I can now get startup to 15sec down from 30sec. Looking promising as only optimised 4 files so far.

Getting further on the MTU mods now too.

Have recoloured my Radio totally now doing a midnight blue theme. Changed the settings for the Radio Pty as mine kept saying Educate when it was a rock station.

More soon.

Hopefully people are still interested in this unit. I think its potential is just starting ;)
[MTCB Android Head Units Q&A] Blaylock1988:
That boot optimization time is fantastic, you are helping to convince me to buy this.

So anyone know if SWC works with 3rd party apps?

EDIT:

I just looked on android-caraudio and they now have a section for 1024x600, and every single one of them have the brown interface with the 1GHz dual core A9. :(
[MTCB Android Head Units Q&A] ajws7036:
Hi, How did you achieve Bluetooth Dialing on this Pure android Car unit? I've been lookinh all over for solutions, but couldn't find one.
[MTCB Android Head Units Q&A] dark alex:
I wrote to keylo about some optimizations. In fact its a list of now 16 Ideas and comments. Will see if they will take the chance and improve the unit further :)

They already told there will be a 4.4 update
[MTCB Android Head Units Q&A] 1-2-Hak:
Im sorry to tell you they dont develop the software

I am sure they can request changes and maybe some will come but the good news is that this is developed with a standard SDK for Rockchip so update for 4.4 should be coming. Just maybe not many changes in the MTU side.
[MTCB Android Head Units Q&A] nwskipro:
Awesome! I just need to learn how to do what you guys are doing... I have my HuiFei unit but its still just like it was when I got it...
[MTCB Android Head Units Q&A] dark alex:
Well if it only would be possible to use PowerAmp or similar cleanly... I mean includung steering-control and autostart (okay autostart would probably be possible by own launcher service app)...

Well two another questions to you. guys...

1.) Has anyone checked why the beeping noise occures on PreAmp-Output and if there is something you can do against it? I guess it's hadware-related...

And yes I know about the High-to-low-Adapters... But I want to avoid this...

2.) Has anyone tried to use the iPod-App? For me it just closes a ssoon as I open it... What am I doing wrong?
[MTCB Android Head Units Q&A] pakidermo5000:
That's great !

Unfortunately, I cannot help. I cannot get the computer to detect any new device when in bootloader mode. Moreover,. I have not been able to put my unit in bootloader mode from cold boot (I may have to unplug the unit, because booting up the unit to reboot into bootloader mode will not be possible if I brick the unit).

Did you manage to sign the MTU apks and boot the unit?

I have the same problem with the radio stations. Rock stations are considered "Religion", which, well, is another way to see it ;)

Sure. Just commenting on some of the people checking for units. I have been looking for units for more than a year before buying this one. They all had problems, incompatible apps, poorly build units, WinCE, single core, android 2.3, no capacitive screen, etc. There was always a promise of a new and better unit, but never arrived.

Then I decided to go for the HuiFei. I have to say that I am happy with it. It can be improved, yes. But everything, or almost everything, works. The hardware is good. You can listen to music or watch movies with no problems. I can run all the apps I need. I cannot sign in in Chrome, fine. There's firefox, but the stock browser works pretty well, and signs into google. Resolution might be an issue in a future, but I do not think you will be running a lot of apps on this. Remember, you have to drive, and clicking the screen is not easy.

On top of that, we have access to the bootloader, and to the source code. Improvements will arrive, probably soon. Just my 2cts.

Disclaimer: I am not a seller or anything of the kind.
[MTCB Android Head Units Q&A] pakidermo5000:
Yes. Just, pair (allow the unit to access your phone details, always) and then you can access all the options from bluetooth app in the unit. What phone do you have?
[MTCB Android Head Units Q&A] 1-2-Hak:
Yes I can recompile any of the MTU apks now. Trying to work out what bits to change - have to learn smali better

I can upload my blue radio and change the Religion to something else if you like.
[MTCB Android Head Units Q&A] pakidermo5000:
I agree. Using PowerAmp as main player with button function would be great !.

BTW: no need for auto start. The unit auto starts the last app that was used when turned off. In the case of PowerAmp, it just starts, but with the last track on "pause". You just have to play it.

Sorry, no preamp in my car, no beep either. I remeber webdude had problems with the sound too. He had to buy something to fix it, you can find the info on the first post.

I do not use ipod.

Hope it helped.
[MTCB Android Head Units Q&A] pakidermo5000:
cool ! What was the problem?

I appreciate, but I do not dare to flash anything if I am not sure I can recover from a brick. You said you changed the settings of the app to fix the "religion" thing. What do you mean, are these declarations made in the apk ? I would like to learn do it myself.
[MTCB Android Head Units Q&A] genge:
Hi, is possible pairing phone with bluetooth to read SMS on audio car display?

I have a note3. Thanks
[MTCB Android Head Units Q&A] ajws7036:
No, the trouble is, I'm trying to design my own. I'm trying to design my own Android head unit, and I'm trying to figure out how to implement Bluetooth dialing.
[MTCB Android Head Units Q&A] pakidermo5000:
Sorry, did not understand the question. I do not know what kind of headunit you are designing, but in the HuiFei the bluetooth module is not directly handled by android, but by the MCU. Maybe you can get some ideas if you take the MCU apks and reverse engineer them (there are the links in the wikipage). I do not think the kernel of HuiFei is of any use in its current state. Maybe you can try with other headunits like the OUKU.
[MTCB Android Head Units Q&A] Zaphod-Beeblebrox:
See here:

https://developer.bluetooth.org/TechnologyOverview/Pages/HSP.aspx

https://developer.bluetooth.org/TechnologyOverview/Pages/HFP.aspx

Android devices typically do not support HSP or HFP from the client side (they do from the host side of course). Even on all of the head units I've seen, the bluetooth module is not truly visible to Android. The MCU passes along limited info and allows limited control through a native app.

You may want to take a look at this post:

He's making quite a bit of progress in examining how the MCU communicates with Android.
[MTCB Android Head Units Q&A] 1-2-Hak:
Midnight Blue Radio

https://drive.google.com/file/d/0B3FXCUVt554McHRuS1RPLVdjN1k/edit?usp=sharing
[MTCB Android Head Units Q&A] webdude12:
Mine scrolls through the station name and the song playing. The only thing I do not like about it presently, is the rds scrolls through the preset button as well. So if you change presets mid song / mid RDS scroll. The preset button might show you the name of a song, instead of the station name.
[MTCB Android Head Units Q&A] typos1:
Here is a link to some custom firmware based on the KLD-KK-20141110 from the 4pda.ru forum (by Booroondook, who is also on here)

http://z5h64q92x9.net/tr-url/ru-en.....com/file/d/0BxmzvLRI7-eNQ0gxNHVrLUcySk0/view

Features :

1. Preset multiple applications with the possibility of their removal

2. Size /system reduced from 768 MB to 512 MB

3. Size /data increased from 1 to 3 GB

4. Root Manager - SuperSU

5. The ability to install patches is provided, but has not been tested (KitKat features protection)

Two new menu items in the settings menu:

1.Ethernet (supports USB-to-Ethernet adapters and 4G-NDIS-modems)

2. Update (call my program to install updates)

Differences between this and partition version from XDA :

The biggest difference - the "preinstall", which can automatically install a series of applications when you first start. These applications are not systematic, and therefore the user will be able to delete them in the usual way. In addition, the user can create a list of applications that will be installed automatically in case of an emergency reset to factory settings. For this he will need to put the APK installation of such applications in the folder /mnt/oem/oem/apk/preinstall. In this "emergency kit" may include, for example, Titanium Backup. Then after emergency release it immediately will be installed, and the user will be able to restore the environment, including all accounts, the password to the WiFi access points, configuring 3G modem, installed applications with the settings and so on, even if for some reason you cannot access the Internet (if only he promptly took care of the backup).

Could you not take the KLD firmware and add the bluetooth stuff from the KGL firmware ? Then do 2 versoins for both resolutions ?

Also I posted something earlier from 4pda.ru which shows some differences in the buildprop and bluetooth in the KLD 4.4 could this help ?
[MTCB Android Head Units Q&A] pakidermo5000:
No, it does not. But I do not know whether this happens because the decoder s*cks or because the unit does not have such capability. the last option would be weird, as it would mean that they built different units, which makes no sense.

What method, meaning code, do you use to dimm? I could maybe try it in the terminal emulator to check if it has any effect.
[MTCB Android Head Units Q&A] webdude12:
Problem is we do not have a 4.4 firmware update from KGL yet.
[MTCB Android Head Units Q&A] typos1:
Yes, I realise that, but you could put the radio apk, launcher apk and the bluetooth menu from your KGL firmware into the KLD firmware (removing the KLD ones, obviously), use the bluetooth entries in buildprop from your KGL firmware, tweak the screen res to 1024x600 (and hopefully do an 800x480 version for everyone else ?!) and bingo - a homemade KGL update ! (And possibly take a look at Booroondook's custom firmware from 4pda.ru too, maybe base it on that as some of the mods in there seem quite good, ethernet, 4G modem compatibility etc, I m trying to organise a definitive 4.4 update combining all the best modifications)
[MTCB Android Head Units Q&A] Tung_meister:
Hi guys, got my es9401a today and so far it's great, I've only had chance to have a quick play as I've had to go out so I'll probably have loads more questions later on! The only issue I've noticed so far is that when opening the car door it shows the wrong door open on the screen, as in when the drivers door is open it shows the passenger door vice versa. Is there any way to fix this as its really annoying!
[MTCB Android Head Units Q&A] parazit26:
this depends on your unit. some units have a female connector on the back and some not. if you dont have one, you can easily do one yourself :)