yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units Q&A] typos1:
The equaliser is 3 band, since 4.4.2 there has been 6 extra fake bands (theyre not simulated cos nothing actually happens when you move them), this is stupid, however it has nothing to do with the RGB LEDs or any bug in them on later MCUs.

Your comment on sales claims of "imported" products is bizarre and implies that non imported products are perfect which they arent (there are many manufacturer of "domestic" products that have "inflated" claims) although it too is also irrelevant in the light of the previous poster's possible problem. The Indian developer who makes the firmware for ALL these units has chosen to add 6 fake bands in the equaliser, the manufacturers are probably not even aware that they are fake, it is pointless and stupid but does not necessarily reflect on the rest of the unit. It also suggests a bias against products form manufacturers not from your home country where ever that is. These products are no more or less "caveat emptor" than any other product from any other manufacturer, you appear to be citing that the lack of a known brand name on the front means that somehow bugs are faults are to be expected this is nonsense and history is littered from bugs or problems from known brand manufacturers who charge far more for their products. But none of this is an answer to the potential RGB bug either and the comments dont help solve the problem.
[MTCB Android Head Units Q&A] Petrows:
By the way - found a moment of a BT API modification. FW 141223 uses old API, and FW 150123 uses NEW API!

So, the "Edge" could be 1 jan 2015 to switch between old and new api's.

Question for all: I have seen that in build.prop value ro.build.date.utc - has the readable timestamp. It is safe to test it with 1420070400 (1 jan 2015)?
[MTCB Android Head Units Q&A] Petrows:
Yes, supporting of both versions is highly important. My app is targeted for Google Play distribution and many, many people once configured their devices - dont touch the firmware for a long time.. But got updates via Play market. Check out the staticstics from google play: Android 4.4 only 25% of users of my service!

About exception - you are right, there is no one. The different between old and new classes - some moved numbers. In old interface command 42 - "Dial Number", and in new 42 - "Stop Scan". So, old app called 42 which was sorking on old and stop works on new... Check out the files in project folder /app/src/main/java/android/microntek/
[MTCB Android Head Units Q&A] haxigi:
I got one but hmmm... It isnt that good. Only noise, sometimes acceptable strengh
[MTCB Android Head Units Q&A] Siffion:
Hi. Anyone using a higher KGL MCU than 1.83 for an bmw e46 unit. There are higher revisions available however since 1.83 back light illumination was permanently on whereas on 1.83 the lights come on and off with the cars headlights.

Cheers in advance
[MTCB Android Head Units Q&A] agentdr8:
Make sure you call the one in the current working directory; if you place the flash_image binary in /data/local/tmp, chmod 755 it, and then either specific its path explicitly, or change to that directory and use the dot-slash notation (./flash_image recovery blahblah.img). There might be a conflicting/non-usable flash_image binary in the system path (/system/bin) that is getting called first.
[MTCB Android Head Units Q&A] Petrows:
The com.microntek.dial intent is important too - this is an external API provided by the service. You can call it from the external app or widget. Also, it is used by the Call history widget. Look at this as some standart micronteck api extension.
[MTCB Android Head Units Q&A] Smykel:
I would like to ask, if there is any option to go back to original 4.2.2 android? I have Klyde version of Pure android unit. I updated unit to kit kat but unfortunately radio doesn't catch any signal and I have no idea why.

I will be happy if some one will help me to sort out this problem.
[MTCB Android Head Units Q&A] haxigi:
downgrade with same way as upgrade
[MTCB Android Head Units Q&A] typos1:
Have you updated your MCU, if so have you deffo used the correct MCU ?

Have you tried the radio settings in factory settings, both the FM service area and the radio chip type ?

---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------

Try a more powerful one ?
[MTCB Android Head Units Q&A] Smykel:
I didn't upadted MCU. Mine version it is 2.4. All I updated was firmware. According to "http://dl-1.va.us.xda-developers.com/2/8/5/5/0/1/6/HuiFei-KLY-RM.pdf?key=dBE7ndtZvDB-j2C7gWfi_w&ts=1426363182" my radio should be set on TDA7706, and mine after update was different. Because it is late I will check tommorow. Anyway I would love to go back to original firmware which is v1.86 - KLD(140701).rar . Unfortunately I can't find it anywhere.
[MTCB Android Head Units Q&A] Ninonuk:
No matter what I try, nothing works!
[MTCB Android Head Units Q&A] typos1:
Well if its on the wrong radio IC type than that would appear to be your problem.

What do you mean "v1.86" ? 1.86 is an MCU version, not an Android version, you said you were on MCU v2.40.

You want to go back to 4.2.2 ?
[MTCB Android Head Units Q&A] agentdr8:
You need to copy the downloaded flash_image binary to /data/local/tmp first.
[MTCB Android Head Units Q&A] Siffion:
Is there a way to install a MCU without update.img. Could I create a fake img file
[MTCB Android Head Units Q&A] Ninonuk:
I did it. That´s why i change to /data/local/tm. But it won´t work. Sorry, I´ve posted the wrong screenshot!
[MTCB Android Head Units Q&A] agentdr8:
Did you chmod 755 flash_image? It won't run unless you mark it executable.
[MTCB Android Head Units Q&A] haxigi:
http://www.aliexpress.com/item/Free...-Signal-Amp-Amplifier-Booster/1386107362.html

is there any stronger FM signal booster? that's what i got from the HU seller but the signal is still weak :/

[MENTION=456516]typos1[/MENTION]
[MTCB Android Head Units Q&A] Ninonuk:
Yes, I did! I checked it several times. I tested 777 too, but same as 755.
[MTCB Android Head Units Q&A] typos1:
Ah, I see, that is one of the stronger types.

Have you checked inside your unit to make sure everything is connected properly ?
[MTCB Android Head Units Q&A] Ninonuk:
I used this one! http://huifei.fs-fileserver.de/content/firmware/coudu's_roms/flash_image
[MTCB Android Head Units Q&A] haxigi:
i will try it tommorow once again. maybe the seller send me weak **** that only looks like this strong one.

Will post photos tommorow :)
[MTCB Android Head Units Q&A] Ninonuk:
Thanks. I´ve tested it and i got a new problem! ;)

The same in /system/bin!

And, yes. It´s a ROM from Malaysk. So, what else can I do to get the stock recovery back?
[MTCB Android Head Units Q&A] nzdreamer55:
Still having problems with XposedMTC. So no matter what time I set for the dimming to start or stop (manual or automatic with GPS) and no matter what time it is, the screen always will dim. It is like XposedMTC thinks that the time is always between the set time. I have uninstalled both Xposed framework and XposedMTC several times to no avail. Is there a deeper level of debuging than what is within XposedXTC? Why would it not be able to tell what time it is or what the start and finish times are?

If there is someone who could help again that would be great.

Thanks
[MTCB Android Head Units Q&A] johnsonsteven1986:
How do i setup the gps button? I'm trying to make the button launch Sygic. I'm also having trouble running Sygic from sd card.
[MTCB Android Head Units Q&A] Ninonuk:
I have no twrp.img! I thought that the flash_image is rewritten by the execution to twrp.img. So I have to copy the twrp.img to /system/bin before execution? Is that correct?
[MTCB Android Head Units Q&A] nzdreamer55:
Using Root master 2.1.1 to add root 4.2.2 OS is interesting. I can find several places on this thread that state it works, but the instructions posted seem to be for using Root master 1.3.6. There is a small up date, but it isn't even close to what happens when I D/L and install Root master 2.1.1.

After downloading the apk from the link within this thread and clicking to install, you will be asked to change the security settings for your device to allow unknown apks to be installed. Then you will get the first image.

Clinking on the install anyway you finish installing. The next photo shows the big "R". Clicking on this will start the process.

The next photo shows that a newer version is found. I didn't update per previous warnings.

Clicking on the small gears in the bottom left brings up a menu shown in the next picture.

Skipping this menu by using the back button will bring you to the root circle and pressing it will get you the next several screens as unknown non-Western language (Chinese?) flashes across the screen.

Now you are asked if you want to install another package that is a square with 4 symbols inside and more non-Western writing. I have tried to cancel this, but it always comes back to here. So I accepted it and move forward.

It starts to install and now is the fun part, because all the info in this thread talk about pressing the "Purple" button. Not sure which of these buttons is purple.

If you click on the one on the right, it asks you to add a google account (which I had not done yet as I was working on this). If you click on the one on the left it asks for you to grant Supreuser access to a program that I didn't know what it was. I denied it because I realized that Superuser had been installed and thus I had root access.

I then went into the app menu within the settings and uninstalled the weird application that I had to say yes to install.

I hope this is how I was suppose to get root access using the Root master 2.1.1 as the instructions were a little sparse and incorrect (Purple button?)

Please let me know if I did it correctly and maybe someone can change the first part of the thread to reflect the new rooting procedure.
[MTCB Android Head Units Q&A] clearchris:
Hardware implemented and bench tested. Next to find a small box, wire up a harness and tweak the software.
[MTCB Android Head Units Q&A] agentdr8:
Your start and end times are too close in proximity, and not values that I had anticipated. The time comparison works like this:

If the current time is after midnight (00:00) or before the dimming end time, you're in a dimming period. This would cover situations where the current time is in the early AM hours, assuming your end time is sometime in the morning.

If the current time is after your dimming start time, but before 11:59pm of the current day, you're in a dimming period. This covers situations where it's night-time, but before it rolls over into the next day (which the previous case covers)

If the time is exactly midnight, you're in a dimming period.

So, as a test, set your dimming start time to somewhere around current time+1 or 2 minutes, and your end time to somewhere after midnight, say 5am.

If that doesn't work, I'll send you a debug app you can install that will display some useful info related to the time calculation and current start/end times.

---------- Post added at 05:10 PM ---------- Previous post was at 05:04 PM ----------

Very slick. Looking forward to reading about the end result. Are you planning on sharing the sketch once it's done?

---------- Post added at 05:16 PM ---------- Previous post was at 05:10 PM ----------

Looks right for 2.11. You can remove both applications after Superuser is installed (and working). [MENTION=4339055]pakidermo5000[/MENTION] should be able to link your post to the OP for those wanting to root 4.2.2.
[MTCB Android Head Units Q&A] Ninonuk:
Yes it works. I got twrp on it. I copied these 2 files from here and it works. But now i need the recovery.img to finish, but i don´t find it!
[MTCB Android Head Units Q&A] Ninonuk:
I´m back on stock recovery. Thank you dsa8310 and agentdr8 for your help! I´m so happy. :D
[MTCB Android Head Units Q&A] nzdreamer55:
It WORKED! I am so happy. thanks for holding my hand with this. Here is a screen show showing that it changed from one state to another.

On another note,

Anyone got a solution for the Kitkit OS not playing well with bluetooth OBDII devices? This is why I need to root 4.2.2 because none of the 4.4.x OS will work with my OBDII bluetooth device . I can get the device to show up under the bluetooth settings, however none of the applications seem to be able to find the device (torque, dash commander, OBDlink, etc.) It is like the OS isn't able to talk to the app and let it know where the bluetooth device is. If anyone has a Kitkat OS working with their OBDII bluetooth linked device I would love to hear how they got it to work.

Thanks again.
[MTCB Android Head Units Q&A] clearchris:
Lol. I thought if I replied to my last post, it would show the link back. Apparently not.

http://xdaforums.com/showthread.php?p=59393942#post59393942
[MTCB Android Head Units Q&A] clearchris:
That's the plan. I think I'm going to try and wire it all up tomorrow. Going to take at least a few days to test it out and find out what I didn't consider.
[MTCB Android Head Units Q&A] gmanor77:
Had the same problem with obd, it seems like the os bluetooth is off.

What I did is to install dashcommand (obd elm), then in settings when trying to find the obd bluetooth dongle, the app tries to 'turn on bluetooth'. This will turn the os bluetooth on.

Then the obd will work in all obd apps.

Good luck.
[MTCB Android Head Units Q&A] Smykel:
My MCU it is 2.4 version. Can You tell me which version should be set in fabrics settings. ?
[MTCB Android Head Units Q&A] zorantoma:
Just for notice. In this version the bluetooth contact sync doesnt work. When you try to download contacts from phone the bluetooth conection gets disconected. But boot up time is much faster and they have changed the factory settings.when you hit apply you get a prompt to reboot the unit and you lose your radio stations in mamory.
[MTCB Android Head Units Q&A] Smykel:
Thank You for all help. It is working fine now. I have checked all type of radio in factory setting and on last one starts working :D.

---------- Post added at 08:54 AM ---------- Previous post was at 08:22 AM ----------

I would like to ask , because I am still new in this subject, is there any way to customize look of the menu (icons, different sets of desktop, audio player menu and colours) or simple themes?

regards

Smykel
[MTCB Android Head Units Q&A] ErAzOr2k:
Has onyone tried connecting Logilink VG0018 DVB-T/DAB+ Stick via (active) USB Hub?

For me it's not recognized.

The thing is, when I directly connect this stick to my HU, everything is fine.

Do I need a special OTG USB Hub for this?
[MTCB Android Head Units Q&A] jimsiv:
To me that didn't help. Still haven't found a solution to work my obdii with stock 4.2.2. My machine is a KLD. Also Bluetooth do not disconnect my phone when I put my phone's Bluetooth off.

Sent from my GT-i9506
[MTCB Android Head Units Q&A] typos1:
is your hub plugged into the OTG port ?

TV sticks normally only work with OTG, even though normal USB ports do have host capability.
[MTCB Android Head Units Q&A] ErAzOr2k:
Well, I have only two Ports on the back side of the HU. I don't know which one is the OTG one.

I will try both ports and report back
[MTCB Android Head Units Q&A] typos1:
I dont think any are, the OTG port is normally the front port.

You could try using the USB OTG helper app, I tried it with some success on a non OTG port, although not on these devices..
[MTCB Android Head Units Q&A] ultradj83:
Dears, can anybody explain how to avoid Google voice search crashes?

Tks.
[MTCB Android Head Units Q&A] clearchris:
Heh, it looks complicated, but its actually one of the less complicated arduino projects I have done. Its a combination of 5 very simple circuits and two prebuilt modules (clock and relay), which looks all complicated packed together on a board.

I dont expect everyone to do this. I will detail it out at the end and will answer questions to anyone so inclined. Its probably not for someone who has never touched a soldering iron before.
[MTCB Android Head Units Q&A] haxigi:
What will happen if i install different MCU than mine?

Will i brick it or?
[MTCB Android Head Units Q&A] typos1:
A few weeks back someone was reported that their button mapping had changed and that their radio didnt work after an update, turned out that theyd not read the first page and updated their unit with an MCU and the Android part from a different unit.

I think its highly likely that more people have done this (ie not read the first page properly and gone ahead and flashed the wrong MCU for their device) in the past because having spent more than a year reading/contributing to this thread I ve read many, many, many posts where people have had the same faults.

I wouldnt do it, but I dont think youd have anything to worry about if you did, your button mapping would be different and your radio probably wouldnt work, although it may work if the MCU came from another manufacturer that uses the same radio IC as the manufacturer of your unit, in which case youd just probably get the button mapping problem.

Why would you want to anyway though ?
[MTCB Android Head Units Q&A] Siffion:
So. I think Ive finally finished my setup on my bmw e46 KGL.

MCU 1.86

Using a prerooted JY rom.

Only issue is I keep getting a Google app error when trying to voice search. I think it's to do with the latest version of Google from the app store.

Does. Anyone know of a fix for this
[MTCB Android Head Units Q&A] ftsur:
I'm super interested. What was your all in cost?
[MTCB Android Head Units Q&A] nzdreamer55:
Thanks. Which os are you running and who makes your headunit? Just tried clouds 4.4.4 JY (because my using is a JY) and I can connect the OBD to the os (at least the OBD symbol shows at the top). But when I try any app, it says that bluetooth is not supported on this device. Maybe my head unit is bad? Love the Kitkat interface but hate this issue. Anyone use a wifi adapter how about a wired adapter? It seems harder to set up.

Lastly, does this headunit support a usb hub? Powered?

Thanks for all the help.
[MTCB Android Head Units Q&A] haxigi:
i've been thinking about changing/trying new MCU (KLD - its most common in here) because of my radio problem.

Here are photos of

signal booster:

inside:

Radio inside:

when i plug antena wire:

This red wire on right is Ground as im thinking. Maybe should i connect another one but solding it to the radio body?

This signal booster looks good inside or it's just fake?
[MTCB Android Head Units Q&A] typos1:
Couldnt say if the booster is fake or not I m afraid.

I think KGLs are slightly more common than KLDs, it would probably mess your buttons up if you changed to a KLD MCU and I cant see how it would make your radio work though.

Probably best to contact your supplier or send it back.

KGLs used to have a different (flat) earth wire, it seems theyve changed it.
[MTCB Android Head Units Q&A] haxigi:
the seller doesn't respond to my mail. i need to fix it on my own way :/
[MTCB Android Head Units Q&A] clearchris:
Not sure most of this was from my electronics stock. At current prices you could pick up

Arduino nano 2$

Usb to nano adapter 2$

pcb board ?

Box?

Relays module 1.5$

Clock module 1.5$

Assorted resistors, 1uf cap, headers, wires (?)

Arduino proto shield 5$ (couldnt wait, bought from US seller)

2303 (i think) coin battery 6$ (bad luck with imported batteries)

And a lot of time for the slow boat from china.

Edit: plus 3.5$ and shipping for a "digital potentiometer" from digikey. (What I thought would work didn't work. Oh well, at least i found these.)
[MTCB Android Head Units Q&A] typos1:
You didnt pay on credit card then ?
[MTCB Android Head Units Q&A] agentdr8:
Originally I had used a calculation like this. The problem I ran into was when the current time crossed over into the next day, which then would push the end time out 24 hours into the next day, which would then make for an unlimited dimming period. After a lot of trial and error, it was easier to get rid of the date components in the calculations, and focus just on times as it pertains to a specific day. In most practical settings, the backlight would only dim during the night hours and early morning hours, so the edge cases where people want dimming outside of this case weren't considered.
[MTCB Android Head Units Q&A] haxigi:
yes
[MTCB Android Head Units Q&A] theblackarrow:
Chevy Trailblazer LTZ Bose Amplified System SWC Connection

Dear All I just finished installing my pumpkin Android Car Stereo (JY-C0227) and for all of You looking to how to connect the SWC and make it Work here is what i did and i managed to make 3 buttons out of the 4 to work as it should be

First i used a PAC RP5-GM11 interface harness and all wires are as normal no worries till you reach the KEY1 and KEY2 wires with the SWC wire from the PAC Harness which is (blue / Yellow) connecting them to either Key 1 or Key 2 won't work what you need to do is to cut the black 3.5 mm Wire which have 3 wire Red Black And White you need to Connect only Key 1 to the Red Wire that's it and then go to the SWC control in the Unit and make it learn the Buttons i was really lucky that my Vol+ and Vol- along with the Mode button is working Perfectly only the Button which Changes the AM/FM (Seek UP) is not working which is not a big deal for me as the other 3 is the most important.

Last tip don't solder or permanent connect the wires for the SWC until you test them and you are sure they are working fine also when you cut the black 3.5 Jack Wire you need to cut it from the Middle or the 2/3 place in case you want later to connect them again and use the wire with another HU as if you cut them from one of the Ends it will be almost impossible to rejoin them once again as the wires are really tiny

Hope you all enjoy and now i need you help as i find the screen color saturation is not good at all when playing a video on you tube where the Red Color is bluish and not the natural red color ( especially the faces and the skin colors which is driving me crazy and i don't know how to fix it still i am waiting for the Seller reply to me

Last thing also some times when starting the car i hear a hissing or buzzing sound and after some time it goes is it a grounding problem and how can i fix it
[MTCB Android Head Units Q&A] typos1:
Then you should be protected, use them to claim for a faulty device.
[MTCB Android Head Units Q&A] clearchris:
Did you install the signal amplifier behind your radio or where the antenna enters the vehicle?

In my car, it's right after the antenna so it gets a clean signal to boost. It's surprising how much signal degrades over a length of wire.
[MTCB Android Head Units Q&A] haxigi:
it looks like this:
[MTCB Android Head Units Q&A] jaisand:
radio

since I solve the radio, no broadcasting station takes me
[MTCB Android Head Units Q&A] clearchris:
Can you put it near the antenna?
[MTCB Android Head Units Q&A] zachd:
Hi all. I am looking to get an Android head unit. Since the Huifei versions seem to have the most user support here, I would like to get my hands on one of those. I found the following: w[w]w.aliexpress.com/item/KD-7-1024-600-7-universal-Car-Radio-Double-2-din-Car-DVD-Player-GPS-Navigation/32297273853.html I had to mess with the link a little, since I don't have enough posts to post a real link yet.

I have no way of knowing if this is one of the Huifei units. The title includes 'KD 7', which I think may be Klyde. Also, the brand is listed as Joying, which I know is a reseller. Anyone know for sure?
[MTCB Android Head Units Q&A] abdoahmed79:
Any one can help to find female end mic shielded as mostly i can find stereo cable in market with 3 pin, my external mic having only 2 pin
[MTCB Android Head Units Q&A] Krisjan89:
The easyest way to find out for sure, is to ask the seller for pictures of the about screen.
[MTCB Android Head Units Q&A] abdoahmed79:
Isit advisable to use like this cable for separating mic, it's very thin
[MTCB Android Head Units Q&A] typos1:
It says the page cannot be found

---------- Post added at 11:36 AM ---------- Previous post was at 11:35 AM ----------

Are you sure that your car does not have an aerial booster already ? If it does there may be confliction.