Change screen resolution ... is it possible? - MTCD Android Head Units Q&A

I have tried to get down from 7.1 to android 5.1 by recovery and I have not got it. I try to update the system with the files ndmcu.img and update.img and it gives me error. The unit is started but the screen resolution is changed and part of the menu is left out of the screen and to click on an icon is lucky. it can be fixed?

i have the same problem
I tried to upload the factory files (witson mtcd_mx ) dmcu.img and dupdate.img but it did not work
Please help us

Probably need a different dmcu.ext file. Your units are 800x480?

wobbletop said:
Probably need a different dmcu.ext file. Your units are 800x480?
Click to expand...
Click to collapse
Hai i am also facing the same issue.Do you know how to fix it?

Search for dmcu.ext file here. It's simply a text file with one line:
screen:1
OR
screen:3
depending on your unit.
https://forum.xda-developers.com/showpost.php?p=72587737&postcount=1154

The setting is to find in the factory settings.
Here under "Version". Try different settings depending on the mcu. It´s from 1 up to maybe 5.

I've changed my screen res from 800x400 to 1024x600 and also 1280x720 with a root dpi changer app on my Pumkin unit. I think it can be changed via buildprop as well

[email protected] said:
The setting is to find in the factory settings.
Here under "Version". Try different settings depending on the mcu. It´s from 1 up to maybe 5.
Click to expand...
Click to collapse
@wobbletop @[email protected] @hal9k @typos1
Dear all,
I tried all the ways i can.
Reinstalled the firmware couple of times
Tried installing hal9k 's different versions of firmware
as advised by everyone i created and tried installing dmcu.txt file from 1 to 5 ( All the attempts got failed )
Now my dvd is 800x480 resolution and now in the settings its showing as 1024x600 N.
I really dont know what to do now. I am attaching few pics. Please help.

rohithp said:
@wobbletop @[email protected] @hal9k @typos1
Dear all,
I tried all the ways i can.
Reinstalled the firmware couple of times
Tried installing hal9k 's different versions of firmware
as advised by everyone i created and tried installing dmcu.txt file from 1 to 5 ( All the attempts got failed )
Now my dvd is 800x480 resolution and now in the settings its showing as 1024x600 N.
I really dont know what to do now. I am attaching few pics. Please help.
Click to expand...
Click to collapse
It's dmcu.ext, not dmcu.txt.

Related

How do i change a rom's relsolution ?

hi all ,
i'll be very short , so ... i got ics for my tablet and i only got one problem , the rom i'm using is not for my tablet but it works 'cause they got the same Hardware but here's the problem , this rom is made for 800x480 screen and mine is 800x600 and here's the question , is it possible to change system resolution to fit all of my screen ? sorry for my bad english
JackGalaxy said:
hi all ,
i'll be very short , so ... i got ics for my tablet and i only got one problem , the rom i'm using is not for my tablet but it works 'cause they got the same Hardware but here's the problem , this rom is made for 800x480 screen and mine is 800x600 and here's the question , is it possible to change system resolution to fit all of my screen ? sorry for my bad english
Click to expand...
Click to collapse
you could try installing es file explorer, open the app, go to its settings, then to root settings and check all 4 boxes. next go into the root directory and find the system folder. there you should find the build.prop file. open it using the es file editor. look for the lcd density line and you can change the value. try lowering the number by a quarter. see if that helps.
hope that this wasn't too confusing.
veracu said:
you could try installing es file explorer, open the app, go to its settings, then to root settings and check all 4 boxes. next go into the root directory and find the system folder. there you should find the build.prop file. open it using the es file editor. look for the lcd density line and you can change the value. try lowering the number by a quarter. see if that helps.
hope that this wasn't too confusing.
Click to expand...
Click to collapse
You could use root explorer...
Procedure is same only you have to open build.prop in edit text mode and resize the value...
If you are using a 4.3 inch smart phone then it would be 240, change by 10 or whatever you like...
Just don't change it to very low value or there will be problem...
Reboot the device and see the change...
Rom: CodeBox 1.4.0 Unofficial
Kernel: Horsepower 3.1 by fuss
If you like my post please hit thanks button...
Black_Prince said:
You could use root explorer...
Procedure is same only you have to open build.prop in edit text mode and resize the value...
If you are using a 4.3 inch smart phone then it would be 240, change by 10 or whatever you like...
Just don't change it to very low value or there will be problem...
Reboot the device and see the change...
Rom: CodeBox 1.4.0 Unofficial
Kernel: Horsepower 3.1 by fuss
If you like my post please hit thanks button...
Click to expand...
Click to collapse
How do you compute for that anyway?
gerickjohn said:
How do you compute for that anyway?
Click to expand...
Click to collapse
I have personally changed my resolution first by changing the values so suggested the values...
Values may be different according to your lcd display setting...
Rom: CodeBox 1.4.0 Unofficial
Kernel : Horsepower 3.1 by fuss
If you like my post please hit thanks button...

[SOLVED]Help me please-> I selected the wrong costumer in factory settings

And now I can’t start the head unit
I only see a gray screen and I can not even go into recovery ... is there a solution?
EDIT:
Solved!! ??
I bought a cable minihdmi -hdmi and connecting to the TV, where I saw replicated the screen of my head unit, I was able to understand where I pressed on the touch until you get to the factory settings, where I changed the costumer version from 5 to 11 .. so I start my working screen !!
fur0n said:
And now I can’t start the head unit
I only see a gray screen and I can not even go into recovery ... is there a solution?
Click to expand...
Click to collapse
is someone able to create a script to be loaded via microsd, self-installing, that goes to modify the costumer version from 5 to version 11? I can no longer do anything ... I do not know how to do it, I'm desperate ... thanks to those who will deign to me a consideration!
Perhaps somebody could send you a dmcu.cfg file from a same manufacturer like yours (it is saved when using the export command) there you could change that customer version on the text file and reflash the dmcu.img (from your manufacturer) from recovery with the cfg file in the same folder...
Once you flashed and rebooted...you will have again your customer version again as you set up on the cfg file.
If the cfg file you received did it match with your specific car brand perhaps you have to change some settings (like.can bus) on factory settings to adapt to your model...but your headunit can be operated now
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
Perhaps somebody could send you a dmcu.cfg file from a same manufacturer like yours (it is saved when using the export command) there you could change that customer version on the text file and reflash the dmcu.img (from your manufacturer) from recovery with the cfg file in the same folder...
Once you flashed and rebooted...you will have again your customer version again as you set up on the cfg file.
If the cfg file you received did it match with your specific car brand perhaps you have to change some settings (like.can bus) on factory settings to adapt to your model...but your headunit can be operated now
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
baby name suggestions based on parents names
Solved!! ??
I bought a cable minihdmi -hdmi and connecting to the TV, where I saw replicated the screen of my head unit, I was able to understand where I pressed on the touch until you get to the factory settings, where I changed the costumer version from 5 to 11 .. so I start my working screen !!
@fur0n damn, i have the exact same issue created by me of course, out of pure boredom and stupidity....changed from 1 to 3 in customer setting...
i'm looking to connect the HDMI to a small TV with HDMI inputs, powered by a 12V-220V converter in the car.
question: did the touchscreen of the headunit work after you changed the customer version? How did you navigate back to the factory settings/other menu? USB Keyboard or touchscreen of the unit (while looking at the TV to see where you are)?
Thanks!
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
ikerg said:
Perhaps somebody could send you a dmcu.cfg file from a same manufacturer like yours (it is saved when using the export command) there you could change that customer version on the text file and reflash the dmcu.img (from your manufacturer) from recovery with the cfg file in the same folder...
Once you flashed and rebooted...you will have again your customer version again as you set up on the cfg file.
If the cfg file you received did it match with your specific car brand perhaps you have to change some settings (like.can bus) on factory settings to adapt to your model...but your headunit can be operated now
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
the dmcu.cfg is binary, i exported it from another unit with "customer version 3" hoping i can edit it to "version 1"...but no.
so for the blind MCU update you need the actual cfg file from a similar unit with already set customer version.
i'm still not sure if the touchscreen and the capacitative buttons work in this case....(if you **** up customer version in factory settings/other menu)
This has been answered a number of times but it's not easy to search between forums and there are so many forums. Check out post #6 by Etulio. If you search some more you'll find more like it and other recovery tips.
nic2k said:
This has been answered a number of times but it's not easy to search between forums and there are so many forums. Check out post #6 by Etulio. If you search some more you'll find more like it and other recovery tips.
Click to expand...
Click to collapse
what exactly are u referring to?
i need an exported cfg file from someone with a working v1 system...
and as for further development, i opened the ultraslim case up but i can't see any minihdmi ffs...
fur0n said:
And now I can’t start the head unit
I only see a gray screen and I can not even go into recovery ... is there a solution?
EDIT:
Solved!! ??
I bought a cable minihdmi -hdmi and connecting to the TV, where I saw replicated the screen of my head unit, I was able to understand where I pressed on the touch until you get to the factory settings, where I changed the costumer version from 5 to 11 .. so I start my working screen !!
Click to expand...
Click to collapse
can u please read my topic bro , ibeleive you can help me
Rockchip sofia 3gr USB TO HDMI problem
Dear friends i have a android unit ,Naviin NVN 620 There is inside FYT6021 , Device is Rockhip sofia 3gr android 6.0.1 . I want to transfer screen to Tv with usb 2.0 to hdmi device.(i tried with several devices) Device is working well with...
forum.xda-developers.com

Question Firmware update for ZHAN Andriod FYT compitable platform

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

Question China FYT flashing to Joying?

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

HxD MCU???

Hello i just wanna know where to find the latest hxd mcu.img?
No idea if this is the latest MCU, but at least, there are some here:
Яндекс
Найдётся всё
disk.yandex.ru
Alteady checked, anyone else?
dmcu_MTCE_HXD_V3.62e.rar
drive.google.com
Thanks, but i already have that. The main problem with my headunit is bluetooth wont work anymore after i changed my mcu from hxd to gs, now i want to return to 3.70 hxd but i cannot find it.
This is the latest I found on 4pda. You can also install an older version. Or try asking the seller, maybe he has an update. Or try changing the bluetooth type in the factory settings, maybe the GS update switched it for you. If you made a backup of the settings and have dmcu.cfg, update the MCU with it. Anyway, crossbreeding the MCU is not recommended, but you already found that out.
Untzo said:
Thanks, but i already have that. The main problem with my headunit is bluetooth wont work anymore after i changed my mcu from hxd to gs, now i want to return to 3.70 hxd but i cannot find it.
Click to expand...
Click to collapse
Try HA see my thread for cross compatibility
I tried all the bluetooth adapters from the factory settings but nothing works.
I also noticed the name of the bloetooth is blank no name and no pin
The MCU update may have changed the customer's version, you can find it in Factory settings in the Other tab. This can change Bluetooth names and passwords. If you remember what version number you originally had, change it, but first save the image of the factory settings in the dmcu.cfg file. In case of problems with it, update the MCU from recovery, all settings will return to their original state. I must warn you that the change may cause a black screen and change the control of the buttons, so what you do is at your own risk!

Categories

Resources