Related
Hello everyone,
I would like to know if it is possible to somehow "download" the Android software from a MTCD unit?
Like how you use update.img to update the software, except in reverse. Is there any way to download a copy of the system image, preferably in a convenient, usable update.img form, from a unit?
Thanks in advance.
I don't know the answer, I also want to know!
+ The same question but for the mcu.img
Sent from my Moto G (5) using Tapatalk
Sould be possible with the stock HA ROM from dasaita.
[email protected] said:
Sould be possible with the stock HA ROM from dasaita.
Click to expand...
Click to collapse
HA ROM from dasaita - what's that? Never head of a manufacturer like that?
What I meant was is there a possibility of downloading the ROM from any Android MTCD device (KGL, KLD, MX, GS, whatever), in a re-usable form (such as update.img) to be used on another Android-based device?
Yes, HA has an OTA update function for ROMs but I am not sure if it works. When the last update came out I've tried to update but it showed me that there is no update available. So I had to update manually. I am not sure if it didn't work because I have a GS with HA ROM, if the update wasn't published via OTA or if this function isn't workning yet because it is new.
OTA MCU updates aren't available.
NaviPR said:
Hello everyone,
I would like to know if it is possible to somehow "download" the Android software from a MTCD unit?
Like how you use update.img to update the software, except in reverse. Is there any way to download a copy of the system image, preferably in a convenient, usable update.img form, from a unit?
Thanks in advance.
Click to expand...
Click to collapse
TitaniumBackup once you get it set up you can create a update.zip
As for the MCU when your done fixing your factory settings before you exit his export
Cid6.7 said:
TitaniumBackup once you get it set up you can create a update.zip
As for the MCU when your done fixing your factory settings before you exit his export
Click to expand...
Click to collapse
Do you have a specific configuration for TitaniumBackup that can be used?
bump
bump!
Hi all you clever people
I just bought this unit, https://www.aliexpress.com/item/7-I...igation-Sat-Nav-Radio-Player/32772807019.html, and installed in my car.
I have set up a bluetooth connection with my phone and using a hotspot from the phone to give Internet access.
I have a lot of questions, and I have searched this site, but haven't really found clear answers.
First the facts. here are the data from my settings:
Model: px5(1024x600)
Android version: 8.0
Android security patch level: October 5. 2017
Kernel: 4.4.93+
[email protected] #336
px5-userdebug 8.0.0 OPR5.170623.007 eng.htc.20180804
MCU version: MTCE_MX_V2.92.1
Aug 21 2018 20:10:21
CPU: 8 core 64-bit CPU Coretex-A53 @ 1.5G
Memory: 3891 MB
I know I'm asking a lot of questions, it's just a bit confusing to get started in this new world. I have numbered my questions, so it's easier to reference
1) I would like to get hands free phone calls and texting and navigation. I tried Android Auto, and that was very stable, but I couldn't get the phone to work. I assume thats because it's meant to be run on a phone and then mirrored to the head unit. Now I'm trying with Google Assistent, but it's not really stable. At first it worked pretty well, but now it just works as Google Now, so it won't make phone calls for instance. Any advice on what to choose, and how to get it to work?
2) I found this thread about a custom ROM, https://forum.xda-developers.com/an...t/rom-hal9k-rom-3-mtcd-e-head-units-t3847477/, my unit should be compatible for that, right?
3) As far as I understand, I can not go back to the stock ROM, if I install the new ROM. Then I should flash it with my old ROM. But how do I find out the name of my existing ROM? Is it risky to flash a new ROM, or will I always be able to flash back, if something goes wrong?
4) It's a requirement for the Hal9k ROM, that my MCU is upgraded to at least 2.93. I found this thread, https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155, but how do I find out if this MCU upgrade is compatible with my MCU?
5) Finally, I installed Tidal app, so I could download playlist for my head unit, but when I start the app and enter my credentials (and they are correct, because I get an error if I enter a wrong password) it just starts up with a black screen with a play icon in the middle, and previous and next symbols, but no menu, except for a hifi menu in the top left corner, where I can choose streaming quality. I will post a picture tomorrow. Does anyone know how to fix that?
Can someone please help me or at least point me in the right direction? I have spent multiple hours searching this site, but right now I'm a bit confused
Kind regards
Allan
Hi! Ok I should be able to answer most of these:
1) If you use the Hal9K 3.1.1 ROM then calling is linked to the phone through Android Assistant, but I haven't got a good solution for SMS at this stage.
2) Yes is is definitely compatible with your unit.
3) Not true, you can definitely go back, just flash a stock ROM. In my case I was sent the ROM by my seller Eonon
4) Your MCU is MX so just find the correct version of that. Check for the MX version here: https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
5) Not sure, but hopefully the Hal9K rom will help fix that!
Good luck Allan
millab said:
Hi! Ok I should be able to answer most of these:
1) If you use the Hal9K 3.1.1 ROM then calling is linked to the phone through Android Assistant, but I haven't got a good solution for SMS at this stage.
2) Yes is is definitely compatible with your unit.
3) Not true, you can definitely go back, just flash a stock ROM. In my case I was sent the ROM by my seller Eonon
4) Your MCU is MX so just find the correct version of that. Check for the MX version here: https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
5) Not sure, but hopefully the Hal9K rom will help fix that!
Good luck Allan
Click to expand...
Click to collapse
Thank you very much, it sound like it should be pretty safe to try the Hal9K ROM. I just have a couple of extra questions:
3a) My seller on AliExpress seems to have no clue, when I'm asking for stock ROM. But I should be able to find something close to my Stock ROM, if I don't succeed with Hal9K, right? Something like the Original Android 8.0 MX ROM mentioned in this thread: http://www.androidiani.com/forum/au...ndroid-rockchip-px5-2-4-gb-ram-32-gb-rom.html
4) I found this thread, https://forum.xda-developers.com/an...evelopment/update-media-auto-mtcd-mx-t3828177, with a link to yadi.sk, where I can find a MTCE_MX_V3.00.rar. That should be compatible with my device, right?
I hope you will bare with my ignorance, I'm really trying to get into this
Kr
Allan
Did you manage to get Tidal working ?
for Android Auto. I'm running the app called `Head Unit Reload` that would turn the Android system as host. essentially it's helper app for `DHU` (Desktop HeadUnit by Google for android auto debugging).
with HUR you can do either wireless Android Auto or USB tethered. This would handle SMS and phone call hands free.
I'm running Hal9K 3.1.1 ROM on my MCUE HK + Car launcher pro as launcher.
Hi,
Is there firmware update for ZHAN platform with the attached specs. It is FYT compatible, can I install Joying FW instead where it has similar specs. Did any one try it?
Thanks
Hello,
I have this platform too.
Are you found any alternative rom?
Any alternative application for Radio? Bluetouth phone etc?
[email protected] said:
Hello,
I have this platform too.
Are you found any alternative rom?
Any alternative application for Radio? Bluetouth phone etc?
Click to expand...
Click to collapse
Hi,
I found some platfroms pretty similar to ours but not with the same name. Like Joying, Tyes, Witson, and FarCar. The one that is most similar from my point of view is FarCar. I didn't do a full flash for any of them because I was afraid that any of the functionalties will get broken for any reason. So, I was asking for anyone who did it and successed before doing mine. For the time being, I extracted some OEM Apps from Allapp.pkg and updated mine to resolve some issues and it was working.
mashrom said:
Hi,
I found some platfroms pretty similar to ours but not with the same name. Like Joying, Tyes, Witson, and FarCar. The one that is most similar from my point of view is FarCar. I didn't do a full flash for any of them because I was afraid that any of the functionalties will get broken for any reason. So, I was asking for anyone who did it and successed before doing mine. For the time being, I extracted some OEM Apps from Allapp.pkg and updated mine to resolve some issues and it was working.
Click to expand...
Click to collapse
I was afraid too update my radio, becaus I`m not android developer.
I`m Windows developer and c#
If you update some application can you write what application you modified and what bug resolved?
If you wont share my this apps?
mashrom said:
Hi,
I found some platfroms pretty similar to ours but not with the same name. Like Joying, Tyes, Witson, and FarCar. The one that is most similar from my point of view is FarCar. I didn't do a full flash for any of them because I was afraid that any of the functionalties will get broken for any reason. So, I was asking for anyone who did it and successed before doing mine. For the time being, I extracted some OEM Apps from Allapp.pkg and updated mine to resolve some issues and it was working.
Click to expand...
Click to collapse
[email protected] said:
I was afraid too update my radio, becaus I`m not android developer.
I`m Windows developer and c#
If you update some application can you write what application you modified and what bug resolved?
If you wont share my this apps?
Click to expand...
Click to collapse
I updated Winca app as it had couple of annoying bugs like AC every moment pops up on the screen with no reason, and the reverse Camera lines weren't moving with the steering. And updated the bluetooth app in a hope to get the OBD to get paired ,but it didn't unfortunatly and it made no change from the older one I had.
I knew that @mclaudio did already the firmware upgrade for ZHAN to Joying a while ago. Can you give here your experience with that tips and tricks and any malfunction you face?
mashrom said:
I knew that @mclaudio did already the firmware upgrade for ZHAN to Joying a while ago. Can you give here your experience with that tips and tricks and any malfunction you face?
Click to expand...
Click to collapse
It is not that difficult.
- do not update the MCU.
- Check your config.txt for sys.fyt.bluetooth_type. Joying uses sys.fyt.bluetooth_type =1, maybe yours is different. From terminal do: `getprop sys.fyt.bluetooth_type` and add that value to the config.txt.
- check your manufacturer id: `getprop ro.build.fytmanufacturer` and open the Joying allap.pkg and edit the fyt.prop, set `ro.build.fytmanufacturer` to `ro.build.fytmanufacturer=<ZHAN id>` (Joying is 43) and repack the Joying Allap.pkg. Now you can flash the Joying firmware.
surfer63 said:
It is not that difficult.
- do not update the MCU.
- Check your config.txt for sys.fyt.bluetooth_type. Joying uses sys.fyt.bluetooth_type =1, maybe yours is different. From terminal do: `getprop sys.fyt.bluetooth_type` and add that value to the config.txt.
- check your manufacturer id: `getprop ro.build.fytmanufacturer` and open the Joying allap.pkg and edit the fyt.prop, set `ro.build.fytmanufacturer` to `ro.build.fytmanufacturer=<ZHAN id>` (Joying is 43) and repack the Joying Allap.pkg. Now you can flash the Joying firmware.
Click to expand...
Click to collapse
Thanks Boss seems easy.
I got the parameters values of mine it is ro.build.fytmanufacturer=53 and sys.fyt.bluetooth_type=3. I will give it a shoot wish me luck
One another question about sys.fyt.bluetooth_type. I changed it to 0 as you described in a your post and finally the OBD is connected. Now phone is unable to connect to the orignal OEM phone dialer and the phone dialer is not searching any more. Returning back to the default 3 in my case dialer works again but the OBD not seen anymore. Is that normal and happening to all and is there a way to connect to either OBD or the phone without changiing the parameter every time?
cheers,
mashrom said:
I got the parameters values of mine it is ro.build.fytmanufacturer=53 and sys.fyt.bluetooth_type=3. I will give it a shoot wish me luck
One another question about sys.fyt.bluetooth_type. I changed it to 0 as you described in a your post and finally the OBD is connected. Now phone is unable to connect to the orignal OEM phone dialer and the phone dialer is not searching any more. Returning back to the default 3 in my case dialer works again but the OBD not seen anymore. Is that normal and happening to all and is there a way to connect to either OBD or the phone without changiing the parameter every time?
Click to expand...
Click to collapse
I don't know. I also (or actually finally) bought an OBD dongle around Christmas time. For me it connects and a few seconds later it disconnects.
And to be honest: I completely forgot about that 'sys.fyt.bluetooth_type' property myself for OBD. I will start testing the coming days.
Please you have any mod or rom for my model?
If yes - can you share it ?
I have winca s300 and I have a problem with the mcu and I contacted winca and did not find a response and I want that mcu "zhan_53_c63l_g32190000d5" ver:1.0
waleed atef said:
I have winca s300 and I have a problem with the mcu and I contacted winca and did not find a response and I want that mcu "zhan_53_c63l_g32190000d5" ver:1.0
Click to expand...
Click to collapse
I don't understand what you want.
You want that ""zhan_53_c63l_g32190000d5" ver:1.0"?
You hve it already as your screenshot shows.
I make wrong update another version and not working ... I need this version
waleed atef said:
I make wrong update another version and not working ... I need this version
Click to expand...
Click to collapse
What is wrong? Does your unit not work at all? Do you have erorr messages to share with us?
and the button not assign right
this mcu after wrong updated
waleed atef said:
View attachment 5897525and the button not assign right
Click to expand...
Click to collapse
This yellow bar means that your FYT layer does not correspond with your MCU. That does not mean that your unit need to be reflashed.
First try my scipt from my thread post #3: 3. Script to correct the fytmanufacturer id in the fyt.prop.
If you still have your original firmware check first for the manufacturer.id. If you don't have it then try first with value 53 which is for a Winca. However, Zhan is also 53.
surfer63 said:
This yellow bar means that your FYT layer does not correspond with your MCU. That does not mean that your unit need to be reflashed.
First try my scipt from my thread post #3: 3. Script to correct the fytmanufacturer id in the fyt.prop.
If you still have your original firmware check first for the manufacturer.id. If you don't have it then try first with value 53 which is for a Winca. However, Zhan is also 53.
Click to expand...
Click to collapse
I make upate from mcu update or another way .... thank you
I don't know make it ... Please help me
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Selvinlyh said:
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Click to expand...
Click to collapse
short answer, no. Note, MCU is not android.
You have latest mcu (53) = YIN. what is it you actually want or think the joying firmware will provide?
Suggest reading forums.
marchnz said:
short answer, no. Note, MCU is not android.
You have latest mcu (53) = YIN. what is it you actually want or think the joying firmware will provide?
Suggest reading forums.
Click to expand...
Click to collapse
Hi, so my issue is that the UI that it provided is not to my liking... i would want to change the UI but the seller told me that he have no idea how to do it. my friends model... same but 10 inch.... has the option in changing the UI.
In my Factory setting page... the only available UI is UI17. I was looking at other threads and was wondering if TS10 firmware works for my device. The UI that TS10 provides looks nicer.
Sorry... but i dont really understand much despite reading. IMO its just a hardware trying to flash with different firmware... and base on the similarity of the device... i fail to understand the complexity in it.... (Im probably wrong in this aspect)
P.S. Im totally new to this and is trying to digest....
I'm not sure if your firmware will allow it, but there are other launchers that can be installed from the Google Play Store. They will change the interface and many of them have different themes that you can switch to. You can view them directly on your head unit from the Play store. Here are a few:
CarWebGuru Car Launcher - Apps on Google Play
Car launcher with themes, widgets, music control, gps tracker, and customization
play.google.com
Car Launcher - Apps on Google Play
Launcher for use in the car
play.google.com
AGAMA Car Launcher - Apps on Google Play
Home screen for car multimedia systems for Android OS (30 day TRIAL)
play.google.com
After installing one or more of them, they may ask you to switch the default launcher when you run them. You don't have to. You can try them and if you don't like them, delete them. I believe if you go "home", if will go back to your original launcher if you didn't switch the default. When you go into the settings, under Apps, one of the options is to display and define the default applications for different functions. You can also change them there. I use CarWebGuru and it looks very different from my original launcher.
If anything goes wrong, as a last resort, you can always switch back to your original firmware.
Just out of curiosity, go to Google Play and look for "Fake Device Tester" and check if that is really an Android 10. I have an unbranded FYT in my car (vertical Tesla-style) and it's a fake.
I need firmware for this car stereo I don't know model and name can you tell me please? Where and how to download?
Tarz89 said:
I need firmware for this car stereo I don't know model and name can you tell me please? Where and how to download?
Click to expand...
Click to collapse
What did the reseller offer
Selvinlyh said:
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Click to expand...
Click to collapse
ido the same after that bluetooth and radio not working
dont do that
istill serach for solution for this problem and icant fix it
ali libya said:
ido the same after that bluetooth and radio not working
dont do that
istill serach for solution for this problem and icant fix it
Click to expand...
Click to collapse
You first should have read the documentation on this forum, including how to make a flashable backup of your unknown FYT unit before flashing it with something else.
And what did you do? Flashing the firmware or trying to upgrade your MCU with a Joying MCU (rule no. 1: Never ever do that !!!, and this is also rule no. 2 to 15)
Your flashed Joying firmware probably has in its config.txt the following line
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
The radio not working is probably due to a mcu firmware mismatch. Joying is type 43 (ro.build.fytmanufacturer=43). Your unit is probably 0 or 116, or some other value. Do you still have your orignal firmware with the original fyt.prop?
surfer63 said:
You first should have read the documentation on this forum, including how to make a flashable backup of your unknown FYT unit before flashing it with something else.
And what did you do? Flashing the firmware or trying to upgrade your MCU with a Joying MCU (rule no. 1: Never ever do that !!!, and this is also rule no. 2 to 15)
Your flashed Joying firmware probably has in its config.txt the following line
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
The radio not working is probably due to a mcu firmware mismatch. Joying is type 43 (ro.build.fytmanufacturer=43). Your unit is probably 0 or 116, or some other value. Do you still have your orignal firmware with the original fyt.prop?
Click to expand...
Click to collapse
Now every thing ok radio working
Only problem is bluetooth software or app now working
Give me messeage
Activation failed error 65535
Due u know any solution
Thnx again bro
surfer63 said:
You first should have read the documentation on this forum, including how to make a flashable backup of your unknown FYT unit before flashing it with something else.
And what did you do? Flashing the firmware or trying to upgrade your MCU with a Joying MCU (rule no. 1: Never ever do that !!!, and this is also rule no. 2 to 15)
Your flashed Joying firmware probably has in its config.txt the following line
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
The radio not working is probably due to a mcu firmware mismatch. Joying is type 43 (ro.build.fytmanufacturer=43). Your unit is probably 0 or 116, or some other value. Do you still have your orignal firmware with the original fyt.prop?
Click to expand...
Click to collapse
First of all iwant to say thanks
U are hero
Bluetooth working now
Tank u again
surfer63 said:
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
Click to expand...
Click to collapse
Hi. Can I access this directly in my unit?
Or do I need to reflash with my backup of unknown FYT unit. I've been getting the activation failed error 65535 when I bought it.
notJimz said:
Hi. Can I access this directly in my unit?
Or do I need to reflash with my backup of unknown FYT unit. I've been getting the activation failed error 65535 when I bought it.
Click to expand...
Click to collapse
Install a terminal app and give the command in the terminal:
Code:
getprop > /storage/sdcard1/properties.txt
Copy the "properties.txt" to your pc/laptop and check the *fyt* lines.
Did anyone find a fitting mcu for this unit ? I have the same problem
Selvinlyh said:
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Click to expand...
Click to collapse
I was able to flash Joying software. posted some notes before, see if it helps:
Carlink change DPI?
I recently bought FYT based head unit that comes with wireless car play (reseller called Xima). the app for wireless car play is Carlink. default resolution is about 480p. the Carlink app setting page doesn't give much options beside noice...
forum.xda-developers.com
Hi my car link apk version is : 2.22.0512.1110 is it latest version?
You can try updating it to this version: https://drive.google.com/file/d/1hM_BCkwcYrLCwOiKJWKguxQjrAocB68p
It was compiled on 2022-09-16 11:31:20
daviddosa said:
You can try updating it to this version: https://drive.google.com/file/d/1hM_BCkwcYrLCwOiKJWKguxQjrAocB68p
It was compiled on 2022-09-16 11:31:20
Click to expand...
Click to collapse
Do you know what has changed? any changelog or smtn
No, just recently downloaded the full ROM for my M300S and this is the file I extracted from it. I doubt that anything major has changed.
daviddosa said:
No, just recently downloaded the full ROM for my M300S and this is the file I extracted from it. I doubt that anything major has changed.
Click to expand...
Click to collapse
Thanks for sharing, just updated and it's works
daviddosa said:
You can try updating it to this version: https://drive.google.com/file/d/1hM_BCkwcYrLCwOiKJWKguxQjrAocB68p
It was compiled on 2022-09-16 11:31:20
Click to expand...
Click to collapse
Not sure why but this version of CarLink doesn't work for me. I plug in my phone and it doesn't detect it. Only version 2.22.0107.1105 works for me but night mode doesn't work with headlight dimming.
Moniushko said:
Not sure why but this version of CarLink doesn't work for me. I plug in my phone and it doesn't detect it. Only version 2.22.0107.1105 works for me but night mode doesn't work with headlight dimming.
Click to expand...
Click to collapse
It’s working fine for me. I only use it wirelessly, never plugged my phone in, I’m using CarPlay. Headlight dimming works too on my M300S, but I had to change that in the settings for the headunit itself and not in the app.
daviddosa said:
It’s working fine for me. I only use it wirelessly, never plugged my phone in, I’m using CarPlay. Headlight dimming works too on my M300S, but I had to change that in the settings for the headunit itself and not in the app.
Click to expand...
Click to collapse
Same, all works for me too. never plugged my phone. wireless only.
Moniushko said:
Not sure why but this version of CarLink doesn't work for me. I plug in my phone and it doesn't detect it. Only version 2.22.0107.1105 works for me but night mode doesn't work with headlight dimming.
Click to expand...
Click to collapse
What's your firmware version? Joying mentioned somewhere in May that you have to update the firmware to make it work with the newer versions of Carlink.
Other resellers simply add it to a complete new firmware to prevent these kind of issues. That's why @daviddosa took it from the latest complete M300S firmware.
surfer63 said:
What's your firmware version? Joying mentioned somewhere in May that you have to update the firmware to make it work with the newer versions of Carlink.
Other resellers simply add it to a complete new firmware to prevent these kind of issues. That's why @daviddosa took it from the latest complete M300S firmware.
Click to expand...
Click to collapse
I'm honestly not sure how to tell. The firmware is stock from when I got it sk I assume it's dated back to 2021. My HU's brand is "D-Noble" and I haven't been able to find a website that has all the unit's firmware. Searching on XDA, there's only like 2 or 3 mentions of this brand. The seller ghosted me on AliExpress so can't get it from there. I was thinking about flashing the firmware from another brand like Joying, but I was afraid that my HU's firmware is too "custom" and I didn't wanna mess that up. By custom, I mean that it looks like it was specifically configured to work with and look like a VW HU.
Edit: Just checked my FYT.prop and my FYT manufacturer is 94. I found an FYT manufacturer list on here and it only says 94 is "VAG". Sorry if this doesn't help much.
I just flashed Joying's 8-15-22 update from their website (just the kernel, no apps) and still no luck. I plug in my phone and Carlink fails to detect it. Still only works on 2.22.0107.1105.
Moniushko said:
I just flashed Joying's 8-15-22 update from their website (just the kernel, no apps) and still no luck. I plug in my phone and Carlink fails to detect it. Still only works on 2.22.0107.1105.
Click to expand...
Click to collapse
Then I suppose the "support" for the new carlink is in the AllAppUpdate.bin. You need to adapt it for your unit before you flash it.
I can't help you further as I don't use Carlink. I have a nice uis7862 Android unit who has all functionality itself (just like you).
surfer63 said:
Then I suppose the "support" for the new carlink is in the AllAppUpdate.bin. You need to adapt it for your unit before you flash it.
I can't help you further as I don't use Carlink. I have a nice uis7862 Android unit who has all functionality itself (just like you).
Click to expand...
Click to collapse
Thanks for your help! I know you wonder why people want to use AA on a full-fledged Android unit. For myself, I like the seamlessness between my phone and the screen. I don't want to fuss much on my unit, including having to use my phone as a hotspot just to get internet on the unit. AA provides a simple car-centric interface that I can use to simply navigate, get messages from my phone and listen to Spotify.
Moniushko said:
Thanks for your help! I know you wonder why people want to use AA on a full-fledged Android unit. For myself, I like the seamlessness between my phone and the screen. I don't want to fuss much on my unit, including having to use my phone as a hotspot just to get internet on the unit. AA provides a simple car-centric interface that I can use to simply navigate, get messages from my phone and listen to Spotify.
Click to expand...
Click to collapse
Its probably best to obtain a genuine Android Auto headunit instead of knockoff Kang emulator, the latter you could expect to be endlessely chasing updates for bugs.
@surfer63 I was able to figure it out. As per your suggestion, I flashed the full firmware from Joying (including the AllAppUpdate.bin) and I was able to successfully get the newer of version of CarLink to work. It even switches day/night mode with my headlights too! Unfortunately, the firmware update broke some other stuff such as
UI and MCU not matching error
I now get a "hybrid driving" page that doesn't go away every time I drive/switch drive modes on my car
RDS text no longer appearing on radio apps
I know how to fix the first error, and I think I can fix the second error by replacing the com.syu.ms.apk from my backup. Unfortunately, I have no idea how to fix the last issue but I guess I'll have to live with it. Seems like the latest FYT firmware updates may have changed something fundamental with how the MCU handles RDS text?
Anyway, thank you for your help!
Moniushko said:
the firmware update broke some other stuff such as
UI and MCU not matching error
I now get a "hybrid driving" page that doesn't go away every time I drive/switch drive modes on my car
RDS text no longer appearing on radio apps
Click to expand...
Click to collapse
If you change the FYT manufacturer id back from 43 (Joying) to your manaufacturer (I assume you saw my script at the bottom of post #1 of the "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware" thread), issue 1 should be solved. However, this might also solve issue 2 and 3.
Note that the FYT firmware also checks this manufacturer ID to send/receive different commands/codes/data to/from the MCU. The Android ms.apk, plus a few other apks, behave differently towards the MCU based on the manufacturer id.
Hi, when I get a call on carplay I just noticed quality is poor. How can I fix that.
Android Version : 10
Baseband version : FM_BASE_18B_W21.20.4|sc9863A_modem|05-20-2021 10:13:14
MARLIN3E_TRUNK_W21.27.3|uwe562_marlin3E_usbhub|07-07-2021 01:36:43
Build number : QP1A.090711.020 release-keys
System Info : APP2022-05-30 11:44:00
CPU Info : CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version : 2022.06.24 14:34:07 NOR_53_L6315_G23P48F64_E60_V:1.0_FYTR
Bluetooth Version : BLINK_2161_RELEASE/2022:06:16:17:41:56_blink
CAN Protocol Version : VER.BG-RN11.1
Is it FYT unit,, post Android system information including MCU version
marchnz said:
Is it FYT unit,, post Android system information including MCU version
Click to expand...
Click to collapse
Yes it is.
Android Version : 10
Baseband version : FM_BASE_18B_W21.20.4|sc9863A_modem|05-20-2021 10:13:14
MARLIN3E_TRUNK_W21.27.3|uwe562_marlin3E_usbhub|07-07-2021 01:36:43
Build number : QP1A.090711.020 release-keys
System Info : APP2022-05-30 11:44:00
CPU Info : CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version : 2022.06.24 14:34:07 NOR_53_L6315_G23P48F64_E60_V:1.0_FYTR
Bluetooth Version : BLINK_2161_RELEASE/2022:06:16:17:41:56_blink
CAN Protocol Version : VER.BG-RN11.1
v2022 oct 12