yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kaween:
Hi there !

1) I agree about the Yandex, but to solve that, you'll need someone who'll take this to heart and keep maintaining. Same is true for the front page of this thread which "hasn't aged all that well". But I'm not volunteering for that. :) And anyhow, the owner (xdaan21u) will probably be Russian, so this request is more something for the people at 4pda.ru

2) The mcu codes are especially a pain if someone does start toying with new mcu's without noting the initial, original version that a unit came with in my experience. Since you're not on the Huifei-side of XDA, no-one will blast you for whatever you say or do. "We" are friendlier. :) It stands to reason there's a good reason for the various MCU updates (otherwise they wouldn't be made, I'm sure) and if your unit does funky stuff it's worth examining them. But if your unit works without issues after upgrading your system version and you have no access to your original mcu, I still advise against it. -Personal opinion-.

Being said, there's really no way to tell exactly what kind of radio tuner or Rohm chip is inside your specific unit if you haven't checked the original mcu and decoded the ID string (other than opening up the unit and have a look-see). Some stuff can be excluded : the radio chip for example : the SI47xx series is a digital tuner so it's not very likely that you have this one. If you have acces to the AM band the radio chip will be a TEF for sure, and if you choose the wrong one, all you'll hear is static. Problem is, you can't easely visually inspect the Tuner version, as it's enclosed in a not-that-easy-to-remove RF-shielded case (trust me, I've done this, not as simple as "pop the hood" or something, soldering is involved).

With the audioprocessor, it SHOULD be the same situation : either you open the unit and look what you find on your MCU board, or you try-by-trial. A wrong choice would mean wrong switching or no sound at all. But if you're already "doubting everything", nothing replaces a visual check of the used audio-processor. The Rohm for example has totally no connection to the android platform. There's no other way to determine this than ... doing exactly the thing you say you can't/won't do.

As for the mcu flash problem, when I had to look for a correct mcu a year ago, the procedure was not to copy those into the system/ect/mcu like you do but to have the needed mcu file on the root of my SD card, choose "update mcu" just like you'd do with a new firmware, and after THAT and a reboot I was able to choose the new models from "choose model".

PS : I see you removed that mcu-flash part of your question just now. I guess that's cleared up then.
[Android Head-Units] Skratchuk:
Hi all,

Has anyone got a spare one of these units for sale] or at least the buttons as 2 of my push buttons have gone!?
[Android Head-Units] copper7op:
Also, do we have updated Root instructions??
[Android Head-Units] macca017:
The Russian forum has posted a link to a new MCU for the new 2.9.5 firmware, however, the link is dead

Attached File mcu 2.9.5.zip (30.88 MB)

Anyone know where to get it please?
[Android Head-Units] balaes:
MCU 2.9.5

http://4pda.ru/forum/dl/post/6195800/mcu+2.9.5.zip

Apps 2.9.5

http://4pda.ru/forum/dl/post/6195784/app+2.9.5.zip
[Android Head-Units] Skratchuk:
Links are still dead mate
[Android Head-Units] kaween:
Just flashed the 2.9.5 in my experiment-unit.

Different laucher buttons (getting more ugly with each new revision so it would seem).

RDS Radiotext still broken : some radio stations work correctly, other radio stations only show info when the full radiotext buffer gets filled up (64 characters long).

no perm-root after baidu (probably possible with the manual trick discribed earlier, still would have to test that)

Only odd difference : the second USB OBD interface I've got which refused to work earlier does work with 2.9.5. Torque pro 1.8.2.. Recognized as "generic usb ...." by the unit. Baudrate set automatic gave some issues, lowered it to 57.600, stable after that).

Worth it compared to 2.8.8 permroot ? Don't think so.
[Android Head-Units] majB:
Hi Kaween, and others

Do you remember me,

I had an issue about the reverse camera not working when starting the engine. The problem appeared to be related to the voltage. With my new camera (the old one was fried) I got it working using a Relais with a stable 12 volt.

Regrettably I burnt a few diodes on the main board testing the old camera, the main board is still working without any problems but the section responsible for the reverse camera is damaged.

So I ordered a new main board and installed it yesterday.

The new board came with firmware 2.9.5 already installed. I agree completely with you kaween it has an ugly interface., but it runs a little bit smoother than 2.9.3 (in my opinion).
[Android Head-Units] 8541hog:
hey kaween, do you have a screen shot of the basic pages (radio, music player, home) on 2.8.8 that you are using?

I am still using 2.7.29 but considering this upgrade.
[Android Head-Units] kaween:
I'll make a couple of screenshots and I'll post the tomorrow. But the radio app I've already posted pics about that when I was talking about my RDS RadioText issue. And here's the funny part : those screenshots are being used on the Ownice part of the forum (a quad core RK3188 device) as an example of how a good radio app should look like (really, theirs looks like crap - which is sad as theirs does seem to have a fully working RadioText .... but no working RDS presets ... ). It is really just the launcher and the radio app that might look different to older version, but I think I've used 2.7.29 too in the past, and it looked virtually the same. Do a search in the forum where I comment about the RDS Radio Text issue of the AN21 : you'll find screenshots of the radio app there already.

If you want nicer-looking apps, I suggest looking for the skinned versions chris r.r. made available some months ago.

[MENTION=855932]majB[/MENTION] : sure I remember you (Groetjes maat ! :) ) I also remember warning you explicitly against "hooking up stuff without making sure of stuff first". :angel:

But I'm glad you've got a working situation in the end. Hope it didn't break your wallet in the process. :) Can't comment on the 2.9.3 thing as I skipped that version.

Also I think I remember you having a 1024x600 unit, so maybe the 2.9.5 has been optimized with higher resolutions in mind. Can't say for sure.

I wish you smooth sailing from now on !
[Android Head-Units] bettuccio:
I hope someone can build a recovery .I can not do it. I hope you boys

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

Before you make changes you have to have a recovery as you do with all Android devices. We solve .Thanks to all.
[Android Head-Units] MoonPie2000:
system file update include MCU

Quick easy, I hope, question- do system update files include MCU files? A few pots ago there was a MCU file post and a system update post. So if I were to load the system update would it also update the MCU file? Thanks:cowboy:
[Android Head-Units] iscle:
Hi guys, i've updated the MCU for my unit to "4.3.10-8-10-E501" and yes, it was the one on my device except that it is a newer version, and the firmware to v2.9.5 and now the setting to enable my GPS on Settings -> Location Services won't show up. Does this mean that it has killed my GPS? I tried downgrading to 2.8.8 permroot and it won't show up either.

Any suggestions?
[Android Head-Units] j2gifted:
[MENTION=4736782]kaween[/MENTION] and [MENTION=2388665]TheSSJ[/MENTION]

Idk what happened, but for some reason everything started working again some time yesterday. I thought it might by a fluke, but today it's still working after many reboots.

Just as random as it happened, is as random as it corrected itself.
[Android Head-Units] macca017:
Logo

Can anyone please tell me if it's possible to add your own logo to the startup?

I don't mean the boot animation, there is a selection of car manufacturer logos to select from, I want to add another one.

:confused:
[Android Head-Units] kaween:
No. Updating System and Updating MCU are 2 sepearate actions & files. One does not automatically invoke the other.

---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------

Afaik, the boot logo is stored raw in /dev/block/mmcblk0p2 partition . Have not toyed with it myself. ZexGx did a complete custom logo + animation project if I recall. Search for his posts regarding, if need be contact him because I seem to remember he bumped into a couple of issues while doing so but it did work in the end.

---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------

Odd. Just tested it on my testing unit, location services is still there with 2.9.5.

Factory reset ? If that fails, "clean install" like done by j2gifted.

---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------

?! Glad to hear it, but that is very odd.
[Android Head-Units] iscle:
I was talking about the GPS option INSIDE location services, the tab itself is there, and I can select to use google services but the GPS checkbox is not there anymore!

Tried doing a full format with the files from yandex, tried downgrading do 2.8.8 permroot and then doing a fullformat and it isn't there. Everything is working perfectly except for that missing option. the strange thing is that if i open up copilot it will show on the notification bar the "Searching for GPS" thing....

Do you think this means it's dead or that it's always on? I haven't tried it outdoor since i'm under age and can't drive a car (it's from my dad)

Edit:

this is what it shows:

And my board is different than the others i've seen on this forum but it is a an-21 u!

And the board number is:

TFZ-MB-V1

2014.1.2

Edit2:

the setting is not there but GPS is working fine.... very strange... anyway, thanks!
[Android Head-Units] kaween:
Ah, didn't understand you the first time round. Sorry for that.

Yep, it would seem the 2.9.5 has indeed removed the "GPS on/off" switch, resulting in a "GPS always on" situation : GPS is working in GPS test, SDVC function and Igo.

Same here : the switch is byebye.

The only thing I can imagine is they got too many "my unit is broken blablabla" caused by people who inadvertedly switched the GPS off or forgot they had done so. Other than in a phone (power consumption), I can't imagine a real reason to be able to switch off the GPS (?).
[Android Head-Units] iscle:
No problem hahaha

Yes, probabbly they've done it because of that...

And what do you think about my board being different, could this cause problems if I want to change the bluetooth module of the radio tuner?
[Android Head-Units] kaween:
No not really.

I've seen several variations of the MCU board so far, but as you correctly stated, they're all basically TH8685/AN21-U's. The BT boards are all the same.

However, make sure you have access to a MCU version for your board that supports the BC6 board, otherwise you end up with a non-working BT in the end.

---------- Post added at 03:54 PM ---------- Previous post was at 03:50 PM ----------

By the way : why change BT board ? Your MCU (4.3.10-8-10-E501) is build for a BC6 BT board anyhow, and most BC6 boards have a blue PCB (like on your picture). All the BC5's I've seen so far where all green. So basically, you already have the latest BT version there.
[Android Head-Units] MoonPie2000:
Update File Question(s)

According to this article <http://4pda.ru/forum/lofiversion/index.php?t522762.html> there are four different manufacturers, each with their own interface (UI) layout. I currently have and am happy with the Create UI. I would like to update to 2.9.5 with the firmware file in the same post however I am not sure what UI it is. Is there a way to tell which UI is contained in the file? Is there an emulator/virtual device that you can load the file on to see the UI before loading on the actual device? Also why do some system updates only have one file in them (8e3513e2-ea4a-11e2-8a0f-000c29ba27c0) while others have two files in them (8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 | 8d8d1b1a-ea4a-11e2-a661-000c29ba27c0)? Thanks for your help in advance.
[Android Head-Units] iscle:
Oh! I thought i had the ond one because it was giving me lots of problems and I read some time ago that by upgrading the bt board those problems were gone, but after doing a fullformat and updating firmware+mcu everything is solved :D good to know I have the last one!

Thanks for the help!
[Android Head-Units] cjackolass:
DVD issue

Hi guys, my dvd worked perfectly but during a movie my screen go to black screen and now my DVD information was recognize has unknow :

[IMG="DVD ISSUE"]http://img15.hostingpics.net/pics/79397720150503174416.jpg[/IMG]

Could we flash the dvd firmware ? or it's dead ?
[Android Head-Units] iscle:
I've installed the 2.9.5 and it has this radio app (in red):

I don't know which manufacturer is it but it was that ui

---------- Post added at 06:15 PM ---------- Previous post was at 06:03 PM ----------

Well, i'm not an expert but if you haven't changed recently the mcu or firmware and it happened just while reading a dvd, i think it's a hardware problem and probabbly it could be dead. If it happened while driving, maybe a flex connector disconnected?
[Android Head-Units] kaween:
[MENTION=1913395]cjackolass[/MENTION]

Probably the drive is indeed dead.

Cool_Head had a similar issue, at the time he doubted if it was the mainboard or the DVD.

I know he bought a Huifei-clone afterwards, and tested the drive of the Huifei in his AN21-U : it worked correctly, so in all likelyhood, the drive is dead.

If the unit still is under warranty, contact the seller. If not, you can try opening the unit and inspect the Flex cable between mainboard and drive to exclude that possibility.

AFAIK, there no possibility to flash the DVD firmware while it is connected in the unit itself.
[Android Head-Units] MoonPie2000:
can you show me what the Home Screen looks like - that is what I am most interested in. Thanks...
[Android Head-Units] iscle:
I downgraded to 2.8.8 because i wasn't able to get root, but it had the dock at the bottom, with big icons similar (the same really) to the iOS icons. It really is the same Home Screen as the 2.8.8 only changing the icons theme
[Android Head-Units] Pazens:
Toeveryone who ****ed up with installing the wrong MCU and looking for the right MCU to bring it back to normal: Install Root to your Radio and install a Root Explorer. There is a directory with dozen MCUs. After trying several ones i hit the right so i think for every radio there is the propper MCU so i recommend to check that out :good:
[Android Head-Units] iscle:
Yesterday while I was messing arround with it I found that, but there are 20+, and if you flash a wrong MCU cam't your radio die completly?
[Android Head-Units] Pazens:
I tried about 10 and everytime just the buttons or audiooutput did not work but after a time i got the right MCU

I cant guarantee you that it wont die forever but i dont think so
[Android Head-Units] kaween:
... this is old news. or better said, it should be.

Problem here is this : it is perfectly possible the MCU you need for you unit is not there. just like it _can_ be there. Hoping/counting on "ah but the mcu I need should be there no ?" is nothing more or less than luck of the draw. Hence : NOTE DOWN, MAKE A SCREENSHOT, TATTOO IT ON YOUR FOREARM or whatever works for you but DO know your unit's mcu before toying with it.

Is it possible to completly break it ? Can't exclude it. Most of the time In worst case, choosing a wrong mcu will result in non-working or wrong working buttons (like your power button ... ouch ... had that happen once), bad or no sound due to the wrong sound processor chip or wrong FM tuner chip, not working BT (...wrong chip), bad EQ behavoir, failure to change button colors ... ect ect

The crux of the matter is : up till now, I've not seen a unit gaining extra functionality when you started from a good-working unit and flashed a new MCU in it. I'm not saying it can't be the case, I'm just saying that until now, I personally never experienced any gain from flashing an MCU. I did however experience 5 months of searching for a correct mcu after the mcu my seller send out turned out the be the wrong one, and the one I needed was nowhere to be found (and has never surfaced again : I was lucky to find a new version of the mcu 5 months later that did "stick").
[Android Head-Units] TheSSJ:
Yep, I agree with kaween - these MCUs come pre-shipped with the firmware you flashed (or was already flashed), there is no guarantee that the correct one for your unit is available there (I am the best example for this :D have a unit with a motorized screen and all MCUs I found didn't match the code I had on my previous MCU - it's just too uncommon). Had the big luck that I found the dropbox of the support forum for my unit there it was!

So I strongly assume you have a pretty standard model (like for VW or so) - lucky you, dear Pazens :D
[Android Head-Units] dcmtnbkr:
I've got a BC6, now what?
[Android Head-Units] kaween:
http://xdaforums.com/showthread.php?p=54893713&highlight=obd+pair#post54893713
[Android Head-Units] djblaze852002:
Ask Kaween pointed out, you need to pair it using the bluetooth app. Then you can run Torque and select that you're using a bluetooth OBDII and it should all work fine. The only issue I have had is that I cannot get it to work with any other OBDII app, specifically Dash If anyone knows any tricks to get it to work, I would greatly appreciate you sharing.
[Android Head-Units] dcmtnbkr:
Thanks, I must have missed that.

If I figure out your issue with dash, I will let you know.
[Android Head-Units] djblaze852002:
Zhoon (infidini) an-21 u

I am writing this post with regards to the recent unit I purchased seen HERE. It is a variation of the typical AN-21 U models out there. Having owned one of the standard models, I noted a few differences and would like to share them with you.

Notable Features:

Full 7" Screen

No DVD

DVR Capable

Bluetooth OBDII (BC6)

GPS + Glonass

External Mic

(much more... see listing)

My unit came with System Version 2.9.3_20150126 and MCU Version 4.3.11-16-10-650101. The system recognized it as Android version 4.2.2, but we all know that it really is version 4.1. I tried the typical passwords only to find that they did not work. I found the passwords to be as follows:

Factory Reset Password: 665076

Extra Setting Password: 662839

User Settings Password: 28012801 (I think)

(Other Possible Password: 61808683)

Next I tried to root the unit to no avail. Baidu Root would not work properly. I believe this has something to do with the newer firmware 2.9.3. I have gotten the manufacturer to send me an older version. I asked for 2.8.8 as it seems to be the most compatible, but they only had 2.8.10. I also had them send me 2.9.4 incase I would like to revert back to a newer version. I will be trying 2.8.10 soon to see if I can achieve root. The main reason I want root is to be able to change DPI on certain apps as well as install Viper4Android to handle the equalizer. I have been warned by the manufacturer to not use any other firmwares as it could brick the unit. I believe them since there are many special qualities to this unit (DVR App and other unique things). If anyone has any questions let me know otherwise I will continue to post my findings under the same title.

My Experience:

I highly recommend this unit. It is slightly larger than the usual AN-21 U models even though those are large already. I had to make further modifications to my dash kit to make it fit. The volume knob does not spin, but rather goes side to side to raise and lower volume (its weird, but okay). The internal mic quality is okay, I think I am going to try the external mic to see if it is any better. The 7" screen is wonderful! GPS locks on fast (maybe because of glonass?). I am experiencing the grey wifi bars, but so far it hasn't bothered me (internet still works). The sound quality is great, if I can get Viper4Android I'm sure it will be even better. I really HATE the ring tone it has. When I receive a phone call, the ring tone is really loud and very high pitched. I tried using the Zedge app to change the ring tone, but it did not work. Does anyone know how I can change it? I would like something a little less jarring. Thats all the info I have for now. I will post more as I find out more. I will also post a video soon. I highly recommend this product, the manufacturer is very responsive and has answered all of my questions quickly. The unit also was shipped to me very fast it arrived within a week of ordering.
[Android Head-Units] Malcez:
Thanks kaween

I see there has been a bit of chatter about "random MCU upgrades". Well let me tell you, I've done about 20 MCU upgrades and I haven't killed anything. I just keep trying different ones until I find one which seems to work. Stupid me? Maybe yes, maybe no. My experience is that the HARDWARE REVISION NUMBER seems to be the absolute main important number of all. If you can tattoo one number on your arm, tattoo that one!

So I'm currently on 4.3.9-7-10-650101. That means version 4.3.9, hardware revision number SEVEN, model "Volkswagon" (no idea why!), and 6501 gives me all the functions of a DVD, change the button colours, the Rohm audio chip (audio works), and the tuner which seems to work (but is really crap reception so i listen to internet radio instead). The last two digits "01" i think are redundant - no one can tell me what they are for. Sometimes with different MCU zip upgrades, i might find my knobs go backwards or are switched, but i just fix that in the Extras menu, no biggie.

I have learned that you can put hundreds of MCU files in your /system/etc/mcu directory but only the ones with your box's HARDWARE REVISION NUMBER (in my case 7) will appear on the "Model Choose List". You can try the manual upgrade way (put the zip file on the root of the SD card and do a MCU upgrade from the Settings menu), but if you don't have a compatible zip file, you will start to lose functions. In my case, it's all been totally reversible and nothing irretrievable, nothing fried.

I kinda agree that if something is not broken, don't upgrade. But on the other hand, I'm addicted to upgrading and if a MCU upgrade comes along, and it appears compatible to my system - I will probably give it a go. :)

This is just my experience, would be interested to know what others found.

Cheers

Malcez
[Android Head-Units] wanxu:
Hi guys. I've been out of this thread because I screwed my unit :( Mine was D90-9001 from Audiosources.

They were very kind and told me to send the unit back to China for repair (and pay for shipping and shipping back) but the unit never arrived... After 2 months I know it's in "international destination" but not "final destination" so I decided to buy another unit from Audiosources. This time my choice is a little different unit, D90-810. It's almost the same but with more physical buttons , SD-card slot.

[IMG="D90-810"]http://www.audiosources.net/Private/ProductImg/Other/6355425470186337501250717303.jpg[/IMG]

I'm excited to come back and share my thoughts!
[Android Head-Units] kaween:
[MENTION=4674232]wanxu[/MENTION] : Congrats, Looks nice. Looking forward to your experience. Hope it will serve you long and well.
[Android Head-Units] cchrisv:
Greetings,

I've had one of these units for almost a year now. I'm running into several issues that I want to spend some time working on fixing this week. I had a few questions. I'm sure some might have been answered but the length of this thread makes it a little difficult to find information.

- I primarily use Google Play Music. However, now with Plex music update I plan to migrate to Plex more. Right now when the headunit boots I need to open the music app and then open Google Play Music for it to work. Is there a way to correct this?

- Is there a way to get music to start playing automatically?

- Any suggestions for a good external microphone? Mine is terrible. I would love to be able to use Google Now more

- Is there a way to get rid of the top notification bar?