I am not new to flashing ROMs, been doing it as a novice for years on phones and tablets. I love Android and the openness of the environment so when I was ready to do a Android head Joying seemed like the right choice based on what i read and the float mount (Airmount?); I can still argue FOR joying on many fronts but there are a few Key items that just drive me nuts.
They are trying to be too proprietary, i get it you want to offer a specific environment but i came here for Android and I want just that.
why are the bluetooth settings in the Phone app???? and why is it so hard to connect a device???
Why are the settings in general so custom????
Now what I do like and certainly want to retain is the DSP, but it would be nice if the Sub settings where part of the DSP as they should be.
Communication sucks with joying, that may be a bit of language barrier but that leads into my last issue:
terminology - I am not a stupid person but i can't figure out what specific information is truly needed when I start looking at upgrades.
I think the important information is that I have a 7 inch SC9853 with Android 8.1, correct me though because i want to understand this. What is GTX and PX5 in reference to? Sofia is the non-intel based units, right?
So what ROM should I be looking at? I want to upgrade my current unit to Android 9 but Joying has said it will not get 9 which sucks because I just bought it a year ago.
So my questions are:
-What Custom ROM do I need?
-Is there a custom ROM that is based on 9?
-Does a custom ROM retain the Same DSP functionality? The way I understand it is that the UI is specific to the physical Sound Processor chip on the board, is that true?.
Mr.Adam said:
They are trying to be too proprietary, i get it you want to offer a specific environment but i came here for Android and I want just that.
why are the bluetooth settings in the Phone app???? and why is it so hard to connect a device???
Why are the settings in general so custom????
I think the important information is that I have a 7 inch SC9853 with Android 8.1, correct me though because i want to understand this. What is GTX and PX5 in reference to? Sofia is the non-intel based units, right?
So what ROM should I be looking at? I want to upgrade my current unit to Android 9 but Joying has said it will not get 9 which sucks because I just bought it a year ago.
So my questions are:
-What Custom ROM do I need?
-Is there a custom ROM that is based on 9?
-Does a custom ROM retain the Same DSP functionality? The way I understand it is that the UI is specific to the physical Sound Processor chip on the board, is that true?.
Click to expand...
Click to collapse
In short (as so much has already been written about it):
your questions: There is no custom rom. question 2 & 3 are therefore not relevant.
Based on all licenses they must open their code as they are expanding on the Google system, but they don't. Try to get a loyer working on that in China. (This is for the system with all kind of custom hardware drivers. They do not have to open the source code for their apks). Note that this is FYT, not Joying. Joying is just a reseller of FYT hardware and software.
I do not know what GTX is. PX5 (PX3/PX30/PX5/PX6) are rockchip based units. The Sofia and Airmont SC9853i are Intel based units.
They close Bluetooth as they only want you to buy "their" hardware, e.g. the hardware suppliers they have contracts/arrangements with.
The settings are "so custom", because the unit IS custom. It contains a lot of hardware components and links to car hardware, you will never find in a phone. So that is not something you can blame them for, it is because an Android car head unit IS custom.
Google is in close cooperation with several car brands to make head units that ARE Android Auto. They now run in all kind of "unexpected" hardware "challenges", but they will succeed (google for it).
so then with that and based on what i see there isn't really much aftermarket support for any of these "Android" head units and they all mostly suck in their own way; you have to pick and choose the features you want the most and give up the rest...
so a head unit that just did Android Auto would be better than a on-board Android unit feature wise......
Related
I've bought an Android audio system form AVIAN for my car and it stopped working, the company replace it with another head unit (it might be PX5-W211 but I'm not sure) without any documentation at all (not even in theirs sight). I don't have any information about the head unit and the company don't answer my mails. I've asked in Mercedes forum and some one suggest i can use Malaysk ROMs Lollipop 5.1.1. Does anyone have an idea how can I find the hardware type and what ROM version?
1. The AVIAN support said: "We can replace the unit with our new Android 511 Quad core unit for you. This is newer hardware and software. https://avinusa.com/mercedes-benz-e-...w211-w219.html".
2. in the link you can see its Model: PX5-W211 (Android 6.0 Marshmallow GPS Navigation System Octa core CPU (8Core) 2GB RAM memory 32GB internal storage)
3. In the system print screen appears:
"MCU version MTCD_LM_V2.22_1" (from Feb 21 2017)
Android version 5.1.1
Kernel version 3.0.101
What I'd like to have is:
-A good CD player, what i have now is a crappy application, all you can do is: Enter/Exit folder, play/stop, forward and backward. I couldn't find a way to display the tracks names and move to a selected track (when you have 50+ folders and sub folders its a must)
-Enable other android program can access the CD
-BT Tethering.
-Reconfigure some of the hard buttons
Thanks in advance, Haim.
haim_gds said:
I've bought an Android audio system form AVIAN for my car and it stopped working, the company replace it with another head unit (it might be PX5-W211 but I'm not sure) without any documentation at all (not even in theirs sight). I don't have any information about the head unit and the company don't answer my mails. I've asked in Mercedes forum and some one suggest i can use Malaysk ROMs Lollipop 5.1.1. Does anyone have an idea how can I find the hardware type and what ROM version?
1. The AVIAN support said: "We can replace the unit with our new Android 511 Quad core unit for you. This is newer hardware and software. https://avinusa.com/mercedes-benz-e-...w211-w219.html".
2. in the link you can see its Model: PX5-W211 (Android 6.0 Marshmallow GPS Navigation System Octa core CPU (8Core) 2GB RAM memory 32GB internal storage)
3. In the system print screen appears:
"MCU version MTCD_LM_V2.22_1" (from Feb 21 2017)
Android version 5.1.1
Kernel version 3.0.101
Click to expand...
Click to collapse
The new one appears to be a MTCD PX5 system, which is a nice unit and well supported with Malaysk ROMs and other cool tweaks and apps. I just got one for myself and I am very happy with it. These fora have a whole section on MTCD units. Just to make sure, what does Droid Hardware Info say about the CPU?
haim_gds said:
What I'd like to have is:
-A good CD player, what i have now is a crappy application, all you can do is: Enter/Exit folder, play/stop, forward and backward. I couldn't find a way to display the tracks names and move to a selected track (when you have 50+ folders and sub folders its a must)
Click to expand...
Click to collapse
Don't hold you breath, most (all?) MCU apps on these units tend to be sub-par. I am not aware of any nicer replacement app for CD playback, with the reservation that I do not use CDs so I have tried nothing of sorts myself.
haim_gds said:
-Enable other android program can access the CD
Click to expand...
Click to collapse
As far as I know this is impossible. The CD is managed by the MCU rather than the OS.
haim_gds said:
-BT Tethering.
Click to expand...
Click to collapse
Not possible (as far as I know). Once more, the BT module is managed by the MCU rather than the OS. It might be possible to use an external (USB) BT dongle; I have seen reports of this working (but I forgot where...).
haim_gds said:
-Reconfigure some of the hard buttons
Click to expand...
Click to collapse
That should be possible in Malaysk ROMs as well as with third-party apps such as MtcdTools.
Thank you very much sbruda.
I've attached the pictures from Droid Hardware Info
You said "The new one appears to be a MTCD PX5 system", do you mean the system called PX5-W211?
Should I use a special Malaysk ROMs for my radio? (Because it should support Mercedes W211 CAN Bus communication.)
Thanks again
haim_gds said:
I've attached the pictures from Droid Hardware Info
You said "The new one appears to be a MTCD PX5 system", do you mean the system called PX5-W211?
Click to expand...
Click to collapse
Sorry, I got a bit confused by which is one system and which is the other. So:
The one that says "MCU version MTCD_LM_V2.22_1" is an MTCD system, which is great. I am assuming that this is your current system on which you just ran Droid Hardware Info. If so, then the system is an RK3188 rather than PX5 system. It is still well supported by the community. The CPU is a bit slow by today's standards but it may serve your needs (depending on what you plan to do with it). Heck, I have right now in my car an RK3066-based unit (even older and even slower) and it works very well (navigation + Torque + media).
PX5 (aka RK3368) is the latest and greatest from Rockchip and by the name and specs I infer that this is inside the PX5-W211 you mention. I have no way of knowing whether it is still an MTCD unit or something else, so if you are contemplating it you should ask AVIN directly. The PX5 unit is more competent and up to date.
If I were you, I would go like this: If the vendor will replace the current unit with the PX5-W211 free of charge (or at a charge you don't mind) and if said PX5-W211 is also an MTCD unit then I will definitely go for that; I have nothing to loose. If on the other hand the PX5-W211 is not desirable (not an MTCD and/or costs too much money) then I will give the current unit a spin with the Malaysk ROM before exchanging it and see if that satisfies my needs.
Why do I keep mentioning MTCD you ask? Because this MTCD (and MTCB) units have by far the best community support. I would personally not purchase anything else (I tried not long ago and it was not a good experience). Community support is very important because most of the time this is all the support you will ever get; indeed, most vendors are clueless and will provide no support for the OS. In addition, there are several extra things that have been implemented by the community but not by the stock OS provided by the vendor. Mapping buttons to custom actions (which you mentioned in your first post) is one of them.
haim_gds said:
Should I use a special Malaysk ROMs for my radio? (Because it should support Mercedes W211 CAN Bus communication.)
Click to expand...
Click to collapse
You should definitely give it a try. I cannot guarantee but I am pretty sure that you will be pleasantly surprised. Unfortunately I cannot vouch for CAN bus integration (as I never used it) but again I am pretty sure that this will work at least as well as in the original OS.
Thank you sbruda.
I don't think I'm going to upgrade the FW, I have had it with AVIAN crap. I''ll keep it as it now until i got system.
Thanks for the help anyway.
Haim
I do apologize if this is not really the proper category to start this topic. I am not really sure where to begin.
I have an unbranded Android unit now. It’s an Intel Sofia model without a DVD drive. The unit itself, build quality wise, is actually decent. It’s the operating system, and the lack of Sofia support that ultimately lead to wanting to scrap it altogether. Then I realized that it may be possible to replace the Sofia board with a RPi 3. It would give me significantly more performance and open up the Linux OS in my vehicle. I do realize that the unit itself is really a two part unit: MCU and motherboard, but I am not sure how interfacing it with the RPi would happen.
So question is: Would it be possible to control the MCU, and if so, does anyone have information they could share that would help me along on this project.
Also: Could the OS on the current Sofia board be replaced with a full Linux distro instead?
Thanks everyone for your help. I don’t know what I would do without XDA.
Hello,
Recently discovered these Chinese Head units like seicane and dasaita. I tried to pick one out on AliExpress and eBay but I am having trouble deciding how to select one. From my understanding there's three main options PX3 (oldest) PX5 (old) and PX6 (newest most expensive). In addition there seems to be some Intel processor versions as well but I do not know how new those are or how much developer support there is. Ideally I want a unit with good sound (DSP) and fast enough to run Waze, Spotify, Google Play Music, and Headunit reloaded. I plan to install it in an 8th gen civic (2006-2011). Which processor currently has the best developer support for custom ROMs because I would also want to wipe the factory ROM off of the device since I don't trust Chinese OS.. In addition what is the principal behind MCU / MTC versions? Is that how the device communicates with the cars computer?
Thank you!
Hi all,
Some time ago I found a thread on here that directed people how to reimage the head unit with an Android Auto. Is this possible for all head units, or are there things to watch out for? I tried searching but could not find the relevant info(Could be on me).
If I go into About Device of the Head Unit all it shows me RK3368 as name, no more info. All I can find is a thread how to update a headunit with the PX5 to Android 10, which it is already running. If possible I'd really like to flash Android Auto on it, as the current solution feels a bit like a bandaid solution.
Bump
Found some more info. It's a S32F0 MCU, with a PX5 board.
Still trying to figure out if it's MTCB or MTCD and if I can flash Android Auto on it. Any help would be appreciated
DragonSlayer3X6 said:
Found some more info. It's a S32F0 MCU, with a PX5 board.
Still trying to figure out if it's MTCB or MTCD and if I can flash Android Auto on it. Any help would be appreciated
Click to expand...
Click to collapse
Okay so here is an obvious question - why on earth would you put Android Auto on a real Android device? Android Auto is a scaled down version of true Android with some "lite" functionality and support for some basic apps. Android Auto is for those who (for some reason) can't install a proper Android Head Unit.
To put it simply, you can do everything on your Android that you can on Android Auto but not the other way around.
You have S32F0 as MCU, meaning it's not MTCx. Luckily for you, you can still use the only mod that matters - Malaysk. Forget anything else. With Malaysk you can customize your head unit with nearly no limitations to make it fast, user friendly and overall just awesome.
Go to this thread and follow it's instructions.
iceblue1980 said:
Okay so here is an obvious question - why on earth would you put Android Auto on a real Android device? Android Auto is a scaled down version of true Android with some "lite" functionality and support for some basic apps. Android Auto is for those who (for some reason) can't install a proper Android Head Unit.
To put it simply, you can do everything on your Android that you can on Android Auto but not the other way around.
You have S32F0 as MCU, meaning it's not MTCx. Luckily for you, you can still use the only mod that matters - Malaysk. Forget anything else. With Malaysk you can customize your head unit with nearly no limitations to make it fast, user friendly and overall just awesome.
Go to this thread and follow it's instructions.
Click to expand...
Click to collapse
Hi Ice,
Thank you for you answer!
My main reason is the ability to mirror screen. I don't have a 4G dongle attached to my radio, as that is quite expensive over here. So I was thinking to be able to use my own phone as mirror onto the radio to navigate, play spotify etcetera.
For example I can copy my phonebook to the head unit, unfortunately both me and my wife use the car, which causes a very long contact list with duplicates etc.
What I've seen with friends is that Android Auto fixes some of those issues, as you don't run a seperate instance of the phonebook or whatever, but it's a mirror from your phone.
I've seen Malaysk's post, but also read in the thread there are quite some issues and support is flaky at best. Are those posts stirring sh*t for no reason, or do they have a point?
Finally, the seller claims my headunit is real Android 10, with build number 205150. I cannot find anywhere if this is real Android 10, or the so called fake android 10.
DragonSlayer3X6 said:
Hi Ice,
Thank you for you answer!
My main reason is the ability to mirror screen. I don't have a 4G dongle attached to my radio, as that is quite expensive over here. So I was thinking to be able to use my own phone as mirror onto the radio to navigate, play spotify etcetera.
For example I can copy my phonebook to the head unit, unfortunately both me and my wife use the car, which causes a very long contact list with duplicates etc.
What I've seen with friends is that Android Auto fixes some of those issues, as you don't run a seperate instance of the phonebook or whatever, but it's a mirror from your phone.
I've seen Malaysk's post, but also read in the thread there are quite some issues and support is flaky at best. Are those posts stirring sh*t for no reason, or do they have a point?
Finally, the seller claims my headunit is real Android 10, with build number 205150. I cannot find anywhere if this is real Android 10, or the so called fake android 10.
Click to expand...
Click to collapse
Mirror screen functionality on Android Head Units is shaky at best.
You don't need 4G dongle - hotspot from your phone to give access to the Internet on your head unit - that way you can run any Android app on the head unit, Spotify, YouTube, Internet Radio etc etc. Make sure to give full permissions to your phone
Use BlueTooth on your phone to use handsfree calling. Use Google Voice to dial any number (no need to mess with Contact Books), your wife can do the same and your Android Head Unit will not sync contacts back to your phone
I know Malaysk developer as I'm also a Russian-speaker and his work is exemplary. If anything, his firmware is by far more stable and effective compared to anything you get from factory. People who complain about it, simply do not have the right skills of installing it and using it. Spend some time with Malaysk tutorials - well worth it. Malaysk also offers ROOT natively and Viper4Android which means you can tweak most parameters on your head unit and considerably improve the sound in your car.
Doesn't matter what Android version you have. You should go with Malaysk firmware for Android 9 (most stable). You will need to get a "rollback" software to successfully install it if your Android is anything but version 9. For that you'll need to purchase MOD Installer Pro 2 for €10
Whatever is possible to do your Android Head Unit will only be possible with Malaysk. If Malaysk can't support it, then it's simply not doable.
You can also look into "profiles" on your Head Unit. I.e one profile will have your stuff, and the other one will have your wife's.
I am in the market for a custom project I am working on. I am looking for at least a 10" screen, 4 camera inputs (can be 360), carplay, very powerful 6gb ram, and a decent processor. I was looking at the FYT 7862 units. I would like the ability to customize the launcher and have the ability to have a can decoder built-in not only for steering wheel controls. So I have a few questions:
1. Would you suggest the 7862 based units? what other information do I need to get from the supplier to make sure this is a good unit? (I have seen FYT, Ayi, etc as mcu manufacturers so trying to figure out which is best)
2. If not a 7862 based unit, what would you suggest?
3. If I wanted to go all out and have a custom unit designed and money for this project isn't a factor, what components/specs would you suggest? What would make the absolute ultimate head unit with the most functionality?
Thank you for all the help