yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] donaldta:
Well, yes and no. The Parrot Asteroid Smart is much more integrated with Android than these generic head units. Although the video can be switched to view the rear cam regardless of the boot process, the rear cam and the video inputs of the Asteroid Smart are treated as standard Android camera objects after the Android boot process is complete. They even have their own Android camera IDs and there is even a tutorial on Parrot's Developer's site to "Overlay information Rear Inputs/ Video Inputs".

The only caveats is that these overlays cannot appear over the video until the Android boot is complete. A couple of developers have even created their own apps and showcased them in the forums. So for the developers, the Asteroid Smart is actually very customizable. Maybe not so much for the average user whom might be dependant on pre-fab APKs. More importantly, Android 2.3.7 (Gingerbread) is beginning to show signs of obsolescence as the main release of Android 4.x+ has many features not available on the older versions.

Still, the Asteroid Smart is nice as I've been able to pair various bluetooth devices; keyboard, mouse, radars, odb2 scan tools, etc with its internal CK5050 Bluetooth module. Which is something I've not seen on any Generic Android Head Unit do. Not even the name brand Android units from Kenwood or Clarion. The big difference between the Asteroid Smart and the others is it was designed from the ground up as an Android vehicle infotainment system. As opposed to car multimedia system with an Android board plugged into it.
[Android Head-Units] jakejm79:
I've owned 4 DD headunits other the last couple of years:

1. A generic Chinese WinCE unit, didn't keep it for very long, wasn't a fan of the lack of volume knob.

2. Clarion NX501 - Great sound quality, HD Radio and good UI but no customization and no streaming audio app built in (i.e. no Pandora).

3. Pioneer Appradio2 w/ ARLiberator - Full android apps and everything would work just like it did with a phone (I used a Gnex as a dedicated device), but ARL is unreliable and MHL connection would suffer from interference, also changing the radio station can be more cumbersome (like the WinCE/Android units, i.e. it can't be controlled via android, have to exit out to the main menu or use some combo of button presses), sound quality wasn't anything special, low preout voltage.

4. The 2.3.7 Ouku unit - full customization, no additional device needed, sound quality is as good if not better than the Appradio (not as good as the NX501 though) preout voltage is higher than the appradio, everything is accessible right from the android home screen (i.e I can have a radio widget, Pandora widget and stored music widget).
[Android Head-Units] donaldta:
That's the catch 22 with asking random people on the internet about the sound quality. It is all based on personal opinions from what they have already experienced. So, fine for me, may not be fine for you. Not everyone has the "golden ear" or deep pockets of an audiophile.

Besides, the interior design of a vehicle isn't standardized, so the acoustical properties of one vehicle can cause an inaccurate bias. The sound quality is also influenced by the other supporting audio components within the vehicle. The only way to get true unbiased review of the sound quality, measurement tools with a standard defined environmental baseline needs to be compared against the unit under the same conditions.
[Android Head-Units] flyboy1100:
Exactly the type of post I was hoping for. Now to find an an-21 I like.
[Android Head-Units] donaldta:
:eek: He didn't even mention ever having an AN-21. :silly:
[Android Head-Units] B.Stromberg:
HI!

I am new in these Chinse Car DVDs and i think i messed up all at start *lol

My Problem is:

I flashed my Unit with the new 2.6.70 Firmware and played some with it.

I come to the extra Menu section where if found the Point "choose Model"

There was only one Model choosable at my Device ( look Attachment.

The Result was a change of Color ( okay i got it back to normal with the Color App ) but more worse, now my Volume Knob is mirrored

If i twist him right Volume is getting quiet and if i twist him left its getting loud :(

Loooks like i got settings with that from a right hand drive car :(

Does anybody know how to change?

Are there anywhere other Models addable / downloadable?
[Android Head-Units] Drakey83:
Id just be happy that is all it did. You should NOT mess with the different models unless you know what you are doing, multiple people have bricked their devices from doing just that.
[Android Head-Units] B.Stromberg:
well........

thats not the whole story i tell.

as i choose that Model and that mess happend i did a factory Reset and was stucked in Android Boot loop.

Solving that Problem was flashing the 2.6.60 ( 7 Files Version )

Sad Point is, that the Volume and Tune Knob are not changeable in the Settings, why ever :(

Does anybody have an Idea how to solve that ?

I read about a 15 Files Firmware...... But i also read about an other User bricked his Unit by upgrading......

Where does all those Firmware Files come from?

Maybe somebody has Contact to Devs who make those Firmware.......

Is there no Gerneric one to totally get back Factory Defaults?
[Android Head-Units] sciallo:
Oh, now now, just because I fried mine with a (now) KNOWN bad mcu update doesn't mean "MCU or model update = bad, always"...

Now, flashing the other firmware, you didn't change your MCU whatsoever, so you're stuck with the single MCU update that came with .70 at the moment.

As far as different roms with different number of files, if you downloaded them in the past you might have some frankensteined ones... just get what's in the wiki or first post and stick to those, don't start mixing files...

First time I get a device, before I mess with anything, I take a picture of the "about device" setting menu for future reference. Do you know what MCU version your unit came with? Also what model do you have? 2 knobs, 1 knob, vol. on the left? do you have a link to sales page?

I messed heavily with MCU's and had my unit in the state you're describing and worse. Always got it back to it's original state just fine, until I went with MCUs contained in *.6.23 (and someone else did too, hence the big red warnings about that one).

I have a list of what MCU did what, let me know if you know what MCU version you had, or what model you have and I should be able to help

---------- Post added at 07:37 PM ---------- Previous post was at 07:25 PM ----------

Or at least do you remember which version of rom it came with?
[Android Head-Units] Android_ski:
For those that are thinking about getting this unit:

Two weeks ago i didnt even know that this unit existed, went through some of this post and decided to click "buy it now" on ebay. Unit came in within three days from China.

My buddy who installs stereos and alarms for living ordered a harness for my silverado and a Metra two din bracket. The radio was about 1/8" bigger than what standard two din is, so he took out a dremel and made it bigger and installed it.

Its been few days now since i have had it and i absolutely LOVE it, sound quality is good, my kid watches netflix, browse net while sitting in the truck etc. I was very hesitant, thought it will be a cheap pacific rim product with sound quality of a christmas card, but no. Its all good. Its the unit with volume knob on the left, i didnt do any updates as everything works and i have no issues whatsoever. So to all the noobs reading this, just get it:) its pretty cool and works just fine.
[Android Head-Units] B.Stromberg:
i have a 2 Knob Version Volume at the right side ( sadly )

I didnt take a Pic or write down Stock Versions, sorry :(

I bought this one at Aliexpress.........sorry cant post link i am not the choosen one right now ;)

I added a pic

btw.

those image verification for new Users sux here! Some Kind of preschool? *lol* And i am also not allowed to post links :(
[Android Head-Units] sciallo:
Ok, we have a few members here with that same unit. Mine is exactly the same but different button labels and volume on the left, so what applies to me doesn't necessarily apply to you... Hopefully one of them ( [MENTION=2678656]ThePapabear[/MENTION] and [MENTION=230437]veletron[/MENTION] come to mind) could tell us what version MCU they have...

Now that you downgraded to .60 how many models do you see in the model change menu? Do you remember what version firmware you had to start? if nothing else, describe the 'desktop' ie big square widgets, nest with birds...
[Android Head-Units] B.Stromberg:
It was shipped with 2.6.60

I updated it to 2.6.70

There was always only one choosable Model, that in my first Post.

I choose that before and the Color switch to Red and nothing worse happens with the Volume Knob.

All get worse after making Factory Reset. Then I choose that Model again ( before downgrade to x.60 ) and Volume get mirrored.

You think its possible also to get Volume Knob on the left Site? Or still to risky to brick?
[Android Head-Units] sciallo:
I don't think you can get the volume on the left, I never got the volume on the right and I tried ALL possible MCUs...

Try a model update now that you're back on .60... also, try to see what you have under /etc/mcu/ (you'll need to be rooted to see those files...)
[Android Head-Units] Drakey83:
I didn't say MCU updates were bad, I said updating your MCU when you have no idea what your doing is bad.
[Android Head-Units] B.Stromberg:
I am back at x.70 already and also tried to change Model.

But not matter if i am on x.60 or x.70 i always have only that one VW Model to choose.

But they MUST be different after Factory Reset coz i tried this already with x.70 and nothing bad happend. Only Color changes to Red that time...

Like I said, mess began as i made Factory Reset. Btw. there was also Stock Apps reinstalled that i already Deleted.......
[Android Head-Units] odysinnerz:
cool! good job!
[Android Head-Units] donaldta:
As I understand, 180 x 100 mm is the ISO 7736 / DIN 7549 standard for double din for most of the world. Where as, the United States doesn't use the metric system (officially), so our "double din" standard is 7 x 4 inches which converts into 177.8 x 101.6 mm as opposed to the internal standard which would converts to 7.08661x3.93701 inches. These dimensions describes the cavernous area behind the radio not the opening for radio in the dash console.

If you search the following key words "173mm x 98mm radio" on eBay, there are listing for a lot of faceplate / bezel / dash kits. Many of them with the following warnings.

So, I suspect that your friend had to use a dremel to widen the opening of the plastic opening of the Metra Double Din Dash kit. Not mangle actual metal cage of the car which the double din standard is based on because that wouldn't have been worth your money or his time to widen for any aftermarket radio.

No, those image verification are discourage advertisements from spam bots. You can post links by surrounding them with an underscore. For example, _http://www.ebay.com/itm/151227214546_ this will bypass the URL parser that makes the link clickable but also prevents you from posting a clickable link since you have less than 10 posts. We all know that we just need to copy and paste the actual URL in the browser board, or in the case of Google Chrome you can highlight the text and right click it for "go to <url>".
[Android Head-Units] B.Stromberg:
Ok lets try it:

_http://www.aliexpress.com/item-img/6-2-inch-Multimedia-Car-DVDCar-Radio-DVD-Players-Android-4-1-Car-GPS-DVD-Car/1504400297.html_
[Android Head-Units] donaldta:
See, easy peasy.
[Android Head-Units] mad212:
Can you post a link to your auction? I think I'm gonna pull the trigger next week.
[Android Head-Units] kmtk:
Since the USDM dash on my car has a wider stereo than the standard, I purchased a JDM dash board that is standard double din, in Japan at least, and these units don't fit. Ended up saving the dash for a tablet install down the road and bought a Metra kit and sanded it down.
[Android Head-Units] donaldta:
Again, the double din standard does not specify the dash board opening for the radio controls. It specifies the hole that the body of radio fits into.
[Android Head-Units] sciallo:
That's kind of why I'm asking questions before telling him to randomly mess with it, though I'm pretty convinced it's fairly safe to mess with mcus that are from later roms.

What's currently showing as your MCU version in settings->about device?

Ok, I didn't quite understand if you tried the model update while running .60. Also, good to know the color app works, so you have a unit with RGB leds...

Looking back to this post I think [MENTION=4836718]PsychoMcSatan[/MENTION] has the same unit as you do as well, and I remember that post. He had a MCU I have not seen in any of the roms: 4.1.0-7-10-2501-1

I had tried a 4.1.0-7-10-2501 which on my unit gave me working color change, no sleep and no working knobs. You can find this MCU and try it by getting the zip file out of the /etc/mcu/ folder while running .62 rooted (other roms might have that but I can't verify that). you can just extract that file to the root of the SD card and run "MCU update" in the settings.

If that one still doesn't work, you will have to find the *-1 version of it. either ask your seller for an exact recovery rom for your model (they'll probably point you to a generic one like all the others you find at wich point you ask them about a specific one for your revision, with the right MCU which they will have to ask their "engineer" for and get back to you in a few days) or hopefully someone here with the same variation as yours is still running whatever rom came with it and can get the files out of /etc/mcu/ for you.
[Android Head-Units] flyboy1100:
true, but i really like the looks/specs of this one:cowboy:
[Android Head-Units] Android_ski:
Mad212, search for this on ebay " Android 4.1 2 Din Car DVD Player Navigation Stereo Radio GPS WiFi 3G CAPACITIVE". When you get results find a guy with Newdealestore2012 id. I got it from him.
[Android Head-Units] flyboy1100:
Do any of the addon eq's work with this unit? Dsp, v4a? I assume they would, just thought I would check first.
[Android Head-Units] Mancubus99:
I also have the 2 knob version with volume on the left. I'll check my mcu version the next time I'm in my car.
[Android Head-Units] KeeZor:
I have installed my unit (1 knob version) today, and things went well until i connected the phone through bluetooth.

Then the unit started boot looping sometimes, and by turning it off and on again it would suddenly boot normally.

Removing the power completely did not solve the issue, or reset any of my settings.

At a point it was boot looping 19/20 times, and i decided to update the firmware to start from scratch.

Tried the 2.6.7 and 2.6.62 versions without success, and i have just tried the 2.6.60-2 firmware.

Common for all these tries are that it completes several files in the first minute, and then even after having been left on for more than 20 minutes, nothing more happens.

I took notes at the 2.6.60-2 update of the files it installed, and which it didn't

It installed these 5 files:

8a36a6ca-ea4a-11e2-9fda-000c29ba27c0

8c46e290-ea4a-11e2-859a-000c29ba27c0

8d8d1b1a-ea4a-11e2-a661-000c29ba27c0

8e3513e2-ea4a-11e2-8a0f-000c29ba27c0

fa6e4352-ec9e-11e2-9ffd-000c29ba27c0

but not these 2:

8b1b92f8-ea4a-11e2-8ad4-000c29ba27c0

8f1149c0-ea4a-11e2-9029-000c29ba27c0

Does anyone know what im doing wrong, or have any input of what i should do next?

/edit:

My unit came with these versions:

Android: 4.1.1

MCU: 4.1.0-1-10-0101

System: 2.6.62

DVD: 2.13.11-hd860mc
[Android Head-Units] gpmg762:
Did you tried factory reset your unit before flashing different fw?
[Android Head-Units] PsychoMcSatan:
Give me an hour or so and I'll post that MCU if I can find it in my etc/MCU directory.
[Android Head-Units] KeeZor:
I didn't try to update the FW, until i came to a point where i gave up hope of getting it to boot properly, so it was not possible to do a factory reset at that point, and it doesn't load android at all at this point, so no chance of getting into the settings.
[Android Head-Units] PsychoMcSatan:
So I just checked my etc/mcu directory and only 3 files. My unit is the two-knob version with volume on the right side (passenger side in a North American car, which makes my wife happy).

4.0.6-6-30-4501.zip

4.0.6-1-10-0301.zip

4.0.6-1-10-0101.zip

By the way, I haven't done any updates at all so I'm still on .60 and these files are what came with the unit.

Odd that I don't have a soft copy of what's installed. Perhaps they just install the MCU in the factory and then copy over generic folders on the way out the door.

[MENTION=3081576]sciallo[/MENTION], so you have a copy of 4.1.0-7-10-2501? None of my MCU files have the extra "-1" at the end so I'm wondering if that is the one that is installed in my unit. Not that I need it. I don't think I'll be messing with MCUs as I can't recall one post where updating yielded a more functional unit.
[Android Head-Units] sciallo:
sounds like one of two possible problems:

1- A corrupt download, the upgrade process does not finish? or does it try to boot once it's done with those files? (if I remember right it is normal for it to leave a couple of files out. - The files in a update are still a mystery to us in many ways, I wish we could reverse engineer that)

Though Unlikely if it's doing it with more than one version update... Just in case, try to compare MD5 sums between your downloaded files and the wiki files (thanks again [MENTION=5389783]donaldta[/MENTION] for doing all that work with the MD5 sums)

2- Seems like a hardware problem, check wiring too, if possible try hooking it up just to power and nothing else... If you bought it recently also bring it up with your seller, so there is a trail of a problem started in case you need to exchange it.
[Android Head-Units] KeeZor:
1 I had one update that did not finish, because it was not done after 20 minutes, however at that point i still had the logo and android bootscreen (but bootlooping, and never made it to any menu).

The other updates has been completed with an "update end", and then i have rebooted the unit, without any possible result.

At the monent the screen is blank on boot, and the only indication that it works is the backlighting, and the messages written when updating.

I should note that i can hear the radio channel it was tuned into before it started bootlooping, and i can adjust the volume, but thats it.

2 Wiring checked, and when i got home i took it into the workshop, and have only the ground, 12v+ and acc connected to a high quality lab PSU.

It will remain wired that way during the troubleshooting, as i see no reason to put it in the car, before it works.

I will contact the dealer, and see if that helps.

It should not affect anything to update the FW, when it's the ones released officially?
[Android Head-Units] B.Stromberg:
Hello!

Here as Attachement all Versions of my Unit and the mcu Folder.

So what can we do now?
[Android Head-Units] sciallo:
Yeah, not surprised.... I'm pretty sure you're right, especially if you never updated your rom. They probably install MCU by some hardware mean (i've been unsuccesfully trying to crack that) and then install whatever version of the rom...

A copy of 4.1.0-7-10-2501 (without the extra -1) exists in .60-2 firmware. (/etc/mcu/ when running .60-2)

form my notes, on the ones you're showing:

ON MY UNIT volume knob on the left....

4.0.6-6-30-4501: NOT FOR MY UNIT (knobs don't work), No color change, No Sleep

4.0.6-1-10-0301: It is for my unit (actually the one mine came with), provides sleep, no color change

4.0.6-1-10-0101: works for mine (knobs), provides color change, no sleep

I'm guessing those last two would mess up your knobs, the first might work? (though don't go trying if you don't have the one to revert back to)

I would like to know what the model change menu shows you (without actually changing it). I bet it only shows you the first one.

The way they packaged those for what I could understand playing with this, is that they could include MCUs for all models in the etc/mcu folder and the model update had a way to know what model you are running it on and only shows you the ones for your specific variant. though this seems to be broken for the ones with volume on the right.

For [MENTION=5725568]B.Stromberg[/MENTION] situation, all I can suggest is to try using the 4.1.0-7-10-2501 (without the extra -1), if that doesn't work, he will have to get the '*-1" from his seller
[Android Head-Units] PsychoMcSatan:
Sorry again for the wait, but I wasn't able to get it to run after uninstalling. I copied the apk, then the whole directory, and rebooted each time, but nothing.
[Android Head-Units] gghghgh:
Thanks to chris.r.r for his apk repack tutor, I've made a red skin for system apps.I have all red displays in my car....so may be smbdy need it... For 2.6.60
[Android Head-Units] sciallo:
No, if you ask me it shouldn't be this easy to "break" these units... Firmware update or model update. There should be a sure way to restore those things no matter what. That's where the manufacturer kinda screwed up if you ask me.... in your case especially, you're still perfectly able to start the update process, so they should be able to provide ther right files to fix it, or call it a defective unit and replace it.

Wow, that is a long list of MCUs, those are all from the latest rom? and only the one you have installed shows up in the model update for your unit?

It's your call, if it was me, I would start trying them all BUT keep two thing in mind:

1 I have done just that and all was fine but I have not done it with those because I bricked my unit before that update came out. AND my unit is slightly different, we already estabilished that the ones that work on my unit don't work on yours.

and

2 They nicknamed me the android headunit bricklayer... I bricked this and the ouku already... (I KNOW for a fact that the 6.23 mcus are the culpirit of my brick, we had a russian that was an early adopter working with the manufacturer to iron out bugs confirm that)

So that's a "do it at your own risk" granted no matter what you do software wise, they should exchange your unit if it's broken... so if that's your only option, I'd still give it a try.

so, again, if it was me...

I would start by trying the ones that end with 2501

maybe even downgrade to .60-2 and try to install the one we mentioned earlier (4.1.0-7-10-2501)

if that still doesn't fix it try them all!!

I would, but it is entirely your call....
[Android Head-Units] B.Stromberg:
hmpf......

I dont have a 4.1.0-7-10-2501 Version.

if you look at my previous Post you see all my Versions start with 4.2.5-xxxxxx but i have a 4.2.5-7-10-2501

How risky is it to Update the MCU files added at my Unit? Are the really that crazy in China to ship Files at that Unit which can brick it?

How do you install them?

Unzip at the SD Card and then ? MCU Update? System Update. Or do i have to place in a Special Folder so they choosable at Model choose?
[Android Head-Units] Niclas.s:
Hello B.Stromberg

I have bought exactly the same unit as you have from Aliexpress. The unit works fine. Except to day. The unit start up fine with radio sound, and when i start Spotify the audio doesn’t switch by auto, i have to start the music app. I also noticed I can’t install apps from google play. some server error message will show in the notification field.

Do you think a factory reset will mess up my unit with stock firmware?

I was on my way to download 2.6.70 and install it but if i understand you right, i should not do?

One thing more. I checked my firmware data. Look at video from my dropbox and picture. orginal MCU file on picture

ht.. w.. dropbox . com/sh/9hjvim0gzfkinot/7PdrBh-RS8

I really appreciate your advice.

Thanks