Hi, I done a few searches for this, but couldn't find an answer. The Note 10.1 2014 along with the Nexus 10 (both 2500x1600) leave borders when connected to a 1080p TV/monitor via HDMI. This (at least to my understanding) is because they are outputting at a ratio of 16:10 where HD is 16:9. Is there a way to solve this without using some sort of zoom/cropping on the TV side? My guess is the only way to get a perfect image is to have the tablet send a 1080p signal and probably create borders on the tablet as they only allow mirroring. On the plus side this would allow them to run smoother as they would be pushing far fewer pixels.
I've not used Miracast, but am assuming it would suffer from the same problem?
Any info/help would be appreciated, thanks!
Trust my brain to kick-in "after" the last moment and think about searching for a resolution changer!
I found this:
http://forum.xda-developers.com/showthread.php?t=2300248
I've not read it all, but seems to be what I was looking for although it requires a root which I don't really want to do just yet!
Has anyone tired NOMone Resolution Change? Requires Root.
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
Dcoz said:
Has anyone tired NOMone Resolution Change? Requires Root.
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
Click to expand...
Click to collapse
Anyone tested this , or found a non root solution.
I have the same issue with allshare cast
I wouldn't try the resolution changer or script thing if I were you. Apparently it doesn't like our device even when rooted. Someone a while back posted a thread which basically rendered the device useless because of the resolution changer and he had to flash stock firmware again or something to get it back to normal. I have the same issue with the black bars thing when using MHL and I couldn't find a solution for it anywhere for this device.
Thanks C2Q, guest we just have to sit tight and wait for updates. Devices with a resolution of 2500x1600 should be at the top of their lists especially considering the significant performance increases you could expect from dropping the resolution to 1920x1080.
Dcoz said:
Thanks C2Q, guest we just have to sit tight and wait for updates. Devices with a resolution of 2500x1600 should be at the top of their lists especially considering the significant performance increases you could expect from dropping the resolution to 1920x1080.
Click to expand...
Click to collapse
I tried the 1920x1080 and got stuck in a bootloop To fix it I had to use adb pull /data/data/com.android.providers.setting*s/databases/settings.db from TWRP, open the DB in SQLite, remove the 'freeze resolution' entries in the table and push it back. It was a good learning exercise but I don't want to do it again !
Thanks for the warning. That would definitely had been the first thing I would have tried after rooting. I'm sure you've saved few of us.
Hello
The model is JY-UM138N4PX5,
mounts a PX5 with 4Gb RAM and 32Gb ROM
This unit is equipped with the new Orao 8.0 firmware, but in the system information it is not written what kind of "mtc *" has, and many options are missing in the lower android versions.
for example I can not find the deep sleep timeout setting.
A very annoying problem is that at all coldboot (lasting 30-40 sec) the original launcher is reset as default (of course I have set in the nova launcher settings as default).
I also updated to the latest version available on the joying site hoping to solve these problems
Do you know how I can solve? or if I install a malaysk rom could help?
Thank you very much for helping!!
I think joying have their own mcu that's why it didn't have "auto sleep" function on px5
I can not find the deep sleep timeout setting
Click to expand...
Click to collapse
Would love for someone to correct me, but there is no such setting.
...the original launcher is reset as default...
Click to expand...
Click to collapse
Did you set home launcher using the Car Settings app?
Not MTC. Joying use other vendor who ostensibly took HCT and modfied it along with MCU just enough to be different. Enjoy same bugs.
Some time ago I ordered a px6 Max10 with 720p screen. The lcd screen somehow broke in the mail (I think they knowingly sent it to me broken... but that's just my opinion), and I sent them pictures of this. Dasaita sent me a new screen... or at least they were SUPPOSED to. A month and a half later (today) the WRONG part arrived in my mailbox. They sent me the outer glass instead of a new 720p screen. So here I am more than 2 months after I ordered this thing, it is STILL not in my vehicle. I am sooo friggin angry!
Anyway, I sent them an email but we're probably talking yet another 6 to 8 weeks... and that's if they get it right this time, which I doubt. I am fast coming to the conclusion these people are slightly less than honest.... but that's another thread.
I was thinking....
I do have a Dasaita px5 with a 1024x600 screen. Would it be possible just to take the screen off the px5 and stick it on the px6? This might be far easier than expecting much more from Dasaita at this point. After seeing what I saw today in the mail that they sent me, I don't think I am ever going to see a working 720p screen out of them. I have a feeling they are just going to jerk me around until I get tired of trying.
if they are thesame dimension...the only thing really is just flash the right file for the specific resolution
ojuniour said:
if they are thesame dimension...the only thing really is just flash the right file for the specific resolution
Click to expand...
Click to collapse
Yeah that's what I thought. I'm pretty sure the two screens are the same physical dimensions, and I believe the connections are all the same so its just a matter of flashing with the correct resolution.
Bob_Sanders said:
Yeah that's what I thought. I'm pretty sure the two screens are the same physical dimensions, and I believe the connections are all the same so its just a matter of flashing with the correct resolution.
Click to expand...
Click to collapse
Then just flash the 1024x600 update file (including the MCU if necessary )
May be useful to have a 2nd screen handy that you can connect over HDMI to see what you are doing when you try to flash different screen resolutions. For 1024x600 I think you need to flash a dmcu.ext file with "screen:2" in it.
Noway
woggles said:
May be useful to have a 2nd screen handy that you can connect over HDMI to see what you are doing when you try to flash different screen resolutions. For 1024x600 I think you need to flash a dmcu.ext file with "screen:2" in it.
Click to expand...
Click to collapse
Hi woggles,
I am new here, so please excuse me , if my question is stupid.
First, seems I have the same issue. I have PX6 , and the seller recently send me an update containing dmcu and update. files.
I did the upgrade and this almost brick my head unit. So, my display stop working, it have vertical lines , and flicking. My hardware buttons has lost its orders , for example home button become "power" button, and so on. Touch positions on the screen also are displaced. The screen constantly scrolling itself. Error message appear shows Version Unmatch -01.
I plug external HDMI monitor , and there all looks fine. So the issue is in the LCD display .
Then I update dmcu with newest version , and this error message disappear , but I still have issue with the LCD. Tried several update versions, but so far without success. Attaching pictures.
I think that the issue is in the screen resolution do not match , or LCD hardware issue, that is why I would ask you - how to flash dmcu with screen option ? My screen resolution should be 1280*720
Many thanks !
ps. unfortunately I cant attach an image, as new member
HighWay7777 said:
Hi woggles,
I am new here, so please excuse me , if my question is stupid.
First, seems I have the same issue. I have PX6 , and the seller recently send me an update containing dmcu and update. files.
I did the upgrade and this almost brick my head unit. So, my display stop working, it have vertical lines , and flicking. My hardware buttons has lost its orders , for example home button become "power" button, and so on. Touch positions on the screen also are displaced. The screen constantly scrolling itself. Error message appear shows Version Unmatch -01.
I plug external HDMI monitor , and there all looks fine. So the issue is in the LCD display .
Then I update dmcu with newest version , and this error message disappear , but I still have issue with the LCD. Tried several update versions, but so far without success. Attaching pictures.
I think that the issue is in the screen resolution do not match , or LCD hardware issue, that is why I would ask you - how to flash dmcu with screen option ? My screen resolution should be 1280*720
Many thanks !
ps. unfortunately I cant attach an image, as new member
Click to expand...
Click to collapse
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
woggles said:
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
Click to expand...
Click to collapse
May thanks ! I was able to recover screen settings !
For me "screen:12" working fine
Regards,
woggles said:
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
Click to expand...
Click to collapse
Great post.
Some time ago I received a replacement screen panel and apparently it has a resolution of 1280x720, so I installed it ,but the image doesn't fit the screen. I have tried that dmcu ext file ,but the only value that works is screen:12,,,,,any ideas?
Al Ferro said:
Some time ago I received a replacement screen panel and apparently it has a resolution of 1280x720, so I installed it ,but the image doesn't fit the screen. I have tried that dmcu ext file ,but the only value that works is screen:12,,,,,any ideas?
Click to expand...
Click to collapse
Just using reverse thinking on this.....
Wouldn't a bigger image indicate a SMALLER screen? Are you sure the screen resolution is 1280x720 and not 1024x600?
Screen:2 I think is the 1024x600 if you want to try that. Just make sure you can get out of it without the screen just in case it goes blank.
Bob_Sanders said:
Just using reverse thinking on this.....
Wouldn't a bigger image indicate a SMALLER screen? Are you sure the screen resolution is 1280x720 and not 1024x600?
Screen:2 I think is the 1024x600 if you want to try that. Just make sure you can get out of it without the screen just in case it goes blank.
Click to expand...
Click to collapse
When they sent me the new screen they said it was 1280x720, and when I installed it I checked and it showed 1280x720 in settings. There is a setting in factory settings by the name of "Customer Version" and it's referred to the screen version or resolution , Version 1 and Version 2,,,,,,,,I saw somewhere to never change it to version 2 or it will be a blank screen . I did not try to flash the mcu with dmcu ext screen:1, I will try that later.:good:
.
.
Al Ferro said:
When they sent me the new screen they said it was 1280x720, and when I installed it I checked and it showed 1280x720 in settings. There is a setting in factory settings by the name of "Customer Version" and it's referred to the screen version or resolution , Version 1 and Version 2,,,,,,,,I saw somewhere to never change it to version 2 or it will be a blank screen . I did not try to flash the mcu with dmcu ext screen:1, I will try that later.:good:
Click to expand...
Click to collapse
Here is my experience with this similar issue. After figuring out the the dmcu.ext is basically a text file and the only thing in it is screen:x x being a number. The number representing a resolution in relation to what MCU and OS. The default of 1280x720 is 12 on all of the dmcu.ext I could download. I read in most people changing it to 18 depending on which MCU you have installed is what i read. I also was not doing a factory reset erase all before I did an install. So I did the factory reset and the dmcu.ext with screen 12. nothing happened. I did it again with 18 nothing. The 3rd factory reset with screen:0 and on all of these I was using MTCE_HA_V3.62 for dmcu.img. When this one rebooted it had a black screen. I plugged a monitor to the hdmi output and I could see through the monitor just fime but I had to touch my head unit screen where I think it should be according to the monitor so I factory reset again with screen:13 in the dmcu.ext and when the head unit rebooted after installing it was the correct resolution..
sitealpha said:
Here is my experience with this similar issue. After figuring out the the dmcu.ext is basically a text file and the only thing in it is screen:x x being a number. The number representing a resolution in relation to what MCU and OS. The default of 1280x720 is 12 on all of the dmcu.ext I could download. I read in most people changing it to 18 depending on which MCU you have installed is what i read. I also was not doing a factory reset erase all before I did an install. So I did the factory reset and the dmcu.ext with screen 12. nothing happened. I did it again with 18 nothing. The 3rd factory reset with screen:0 and on all of these I was using MTCE_HA_V3.62 for dmcu.img. When this one rebooted it had a black screen. I plugged a monitor to the hdmi output and I could see through the monitor just fime but I had to touch my head unit screen where I think it should be according to the monitor so I factory reset again with screen:13 in the dmcu.ext and when the head unit rebooted after installing it was the correct resolution..
Click to expand...
Click to collapse
Did you use one of the pre-made display fix files on the Russian yandisk repository?
HighWay7777 said:
May thanks ! I was able to recover screen settings !
For me "screen:12" working fine
Regards,
Click to expand...
Click to collapse
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
kiwibird said:
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
Click to expand...
Click to collapse
From reading the forums and contributing, probably FFS.
marchnz said:
From reading the forums and contributing, probably FFS.
Click to expand...
Click to collapse
I tried to look for the right files but wasn't successful. But what do you mean by probably FFS??
kiwibird said:
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
Click to expand...
Click to collapse
I had the same issue and it took forever finding it. Just rename either dmcu.ext. I tried editing the other, the depository I used no longer existed and any Google search came here.
The new place were I got the dmcu.ext file.
Yandex
Finds everything
disk.yandex.com
I had some issues with My 4Runner Dasaita PX6 and the customer support sent me update MCU files. After the update the screen resolution is not right the screen flicker.
Does anybody know the correct dmcu.ext screen number?
I tried screen:10 but it doesn't work
Thank you!
marined said:
I had some issues with My 4Runner Dasaita PX6 and the customer support sent me update MCU files. After the update the screen resolution is not right the screen flicker.
Does anybody know the correct dmcu.ext screen number?
I tried screen:10 but it doesn't work
Thank you!
Click to expand...
Click to collapse
When preparing you drive do you edit the dmcu.ext and write screen:18 to the file?
sitealpha said:
When preparing you drive do you edit the dmcu.ext and write screen:18 to the file?
Click to expand...
Click to collapse
Could you tell me how to change the screen number?
HI
I HAVE THE SAME ISSUE AFTER THE UPDATE FOR MCU AND TRYED TO USE MY OLD 9" SCREEN ON THE SAME HEADUNIT BECUASE I DON'T HAVE WHEEL CONTROL BUS YET, AND REASSEMBLED THE 10.25" DASAITA HA2183-MAX10 NOW ITS FLICKERING WITH LOW BACKLIGHT.
I HOPE YOU FIND ANY SOLUTION AND TELL ME ABOUT IT.
pumatrax said:
Could you tell me how to change the screen number?
Click to expand...
Click to collapse
COULD YOU EXPLAIN HOW TO PREPARE THE DRIVE? OR WHERE I CAN ADD IT?
KHALIL1985 said:
COULD YOU EXPLAIN HOW TO PREPARE THE DRIVE? OR WHERE I CAN ADD IT?
Click to expand...
Click to collapse
I found that screen:11 is what solved my problem. edit the dmcu.ext file and make sure it says screen:11 and put it on the memory card with the MCU and do a MCU update. I see your radio is widescreen like mine and if it uses the 1280x480 resolution like mine but was dim using the screen:10 setting, this should fix it for you. If you cant see your screen because of incorrect screen resolution and have an hdmi out, use an external hdmi display so you can see and get into settings to do mcu update.
pumatrax said:
I found that screen:11 is what solved my problem. edit the dmcu.ext file and make sure it says screen:11 and put it on the memory card with the MCU and do a MCU update. I see your radio is widescreen like mine and if it uses the 1280x480 resolution like mine but was dim using the screen:10 setting, this should fix it for you. If you cant see your screen because of incorrect screen resolution and have an hdmi out, use an external hdmi display so you can see and get into settings to do mcu update.
Click to expand...
Click to collapse
FOR NOW THE DIM IS GONE AND GOOD FOR NOW BUT WHAT ABOUT THE HAIZE AND COLOR ESPICIALLY THE BLACK WIDE LINE ON THE BOTTON OF THE SCREEN HOW DO I FIX IT?
KHALIL1985 said:
FOR NOW THE DIM IS GONE AND GOOD FOR NOW BUT WHAT ABOUT THE HAIZE AND COLOR ESPICIALLY THE BLACK WIDE LINE ON THE BOTTON OF THE SCREEN HOW DO I FIX IT?
Click to expand...
Click to collapse
Ahh I see. I am not sure what native resolution your screen is. If it’s 1280x720 that setting is screen:12. But be careful setting these resolutions because if it’s wrong one you will get no display. If you have external hdmi out you can use that if you lose video on your screen, otherwise I would confirm with vendor.
pumatrax said:
Ahh I see. I am not sure what native resolution your screen is. If it’s 1280x720 that setting is screen:12. But be careful setting these resolutions because if it’s wrong one you will get no display. If you have external hdmi out you can use that if you lose video on your screen, otherwise I would confirm with vendor.
Click to expand...
Click to collapse
NO IT IS THE SAME YOU HAVE 1280X480 ALSO THE SAME ISSUE YOU HAVE ON THE OLD OF PICTURE
KHALIL1985 said:
NO IT IS THE SAME YOU HAVE 1280X480 ALSO THE SAME ISSUE YOU HAVE ON THE OLD OF PICTURE
Click to expand...
Click to collapse
My issue is fixed now with screen:11.
pumatrax said:
My issue is fixed now with screen:11.
Click to expand...
Click to collapse
WHAT IS THE MCU VERSION HAVE YOU USED?
KHALIL1985 said:
WHAT IS THE MCU VERSION HAVE YOU USED?
Click to expand...
Click to collapse
AHA
YOU HAVE OTHER VERSION WITH MTCH-GS BUT I HAVE MTCE-HA THAT I THINK MIGHT DOESN'T WORK BUT I WILL FIGURE THE SOLUTION.
ALSO I WILL KEEP YOU UPDATED.
Good luck!
KHALIL1985 said:
AHA
YOU HAVE OTHER VERSION WITH MTCH-GS BUT I HAVE MTCE-HA THAT I THINK MIGHT DOESN'T WORK BUT I WILL FIGURE THE SOLUTION.
ALSO I WILL KEEP YOU UPDATED.
Click to expand...
Click to collapse
Good luck!
KHALIL1985 said:
AHA
Click to expand...
Click to collapse
If you would please be so kind as to "NOT" post in all capital letters, we would be most appreciative.
Thank you: Badger50
hi
i have good news my screen number is 21.
so any one have model Dasaita HA2183 10.25" this number will help him.
KHALIL1985 said:
hi
i have good news my screen number is 21.
so any one have model Dasaita HA2183 10.25" this number will help him.
Click to expand...
Click to collapse
Thank you! that worked for me too and fixed the issue where I saw 1 pixel length at the top left flickering and repeating from another location so it was a bit annoying.
It even seems like the refresh rate is better and resolution is so much better, back to normal now. I flashed the MCU with wrong screen size. I was glad I found screen:11 but was reluctant to try other numbers, I was nervous if I wouldnt be able to view it via hdmi from messing around. I resuscitated this unit a few times this week already after killing it. LOL
I was using screen:11 so that is not the right one, yours is
Thanks again!
pumatrax said:
Thank you! that worked for me too and fixed the issue where I saw 1 pixel length at the top left flickering and repeating from another location so it was a bit annoying.
I was using screen:11 so that is not the right one, yours is
Thanks again!
Click to expand...
Click to collapse
nice to see this fixed yours
Badger50 said:
If you would please be so kind as to "NOT" post in all capital letters, we would be most appreciative.
Thank you: Badger50
Click to expand...
Click to collapse
sorry for that I will try not to.
KHALIL1985 said:
sorry for that I will try not to.
Click to expand...
Click to collapse
Looks like you might have a solution to your problem now.