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
Related
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.
Hey guys...
With the release of CM12+ and derivatives comes a rare issue for Z1c owners that only a few people are experiencing and we're trying to track down it's origin.
We believe that it is tied to the new thermanager.xml which replaced sysmon.cfg when LP came out and also the type of display that your Z1c has. Sony used 2 versions of the display when they produced the Z1 and the Z1c.
We'd like to try and find as many of those who like us experience this black line issue which randomly appears when certain conditions are met (we have yet to discover exactly what they are ) but in combination with battery temp rise so you feel the device getting hot.
Here is a video of the issue in action :
https://www.youtube.com/watch?v=E9wyRHnjH3E&feature=youtu.be
Please let us know the display type you have which can be read via ES file explorer
Nick
Black lines:
- JDI, revision 14W09
- JDI, revision 14W04
- JDI, revision 14W15
No black lines:
- AUO, revision 14W26
- JDI, revision 14W32. Replaced screen on AUO - no black lines.
- AOU, revision 14W32
P.S. Check revision of your Z1c by opening sim tray, and look on back side of paper "tongue" .
rtimoff said:
Black lines:
- JDI, revision 14W09
- JDI, revision 14W04
- JDI, revision 14W15
No black lines:
- AUO, revision 14W26
- JDI, revision 14W32. Replaced screen on AUO - no black lines.
- AOU, revision 14W32
P.S. Check revision of your Z1c by opening sim tray, and look on back side of paper "tongue" .
Click to expand...
Click to collapse
Yes.... thanks Roman.... the revision number is also good additional information please folks (indicates production run... lower number= earlier production date)
mine is JDI, revision 14W12 for the record
I have stripes on CM12+
On stock LP - nothing stripes
Display: JDI/ Date of manufacture my phone - 14W04
AUO, revision 14W46 here. No black lines.
It seems that only screens JDI is a problem(
JDI 14W11 no black lines.
JDI 14W15
https://www.youtube.com/watch?v=2jC887JEVcM
Wanted: JDI panel ROM testers
John.D.. said:
It seems that only screens JDI is a problem(
Click to expand...
Click to collapse
yes... indeed it seems the JDI panel is the culprit.
We need a few of us with the JDI panel and unlocked bootloader to install the FXP AOSP 5.1 Build 150522 (needs fastboot flash) and run it to try and invoke the black line issue.... so whatever you have had running previously on your device when you've experienced the issue needs to be replicated to see if it happens using this ROM (which has the original thermanager.xml.)
EDIT:.... if you run this test and get the issue still happening please can you take a photo of it while on the 'about phone' tab scrolled down to show the Kernel and Build Number info which displays that the device has AOSP 5.1 installed..... then either post here or send to me whichever you like.
Once we get the results of this we have a way forward to get this issue fixed for any ROM use.
iNDEX3 said:
JDI 14W15
https://www.youtube.com/watch?v=2jC887JEVcM
Click to expand...
Click to collapse
Ah... Hitchhikers guide fan.... ..... early revision JDI is causing a few of us this problem.... but Robin and myself have set out to find a solution and having narrowed it down we need the ROM tested as per my request above.
If your English is not so good then I'm sure one of the other Russians can translate for you...?
cheers
On http://uploaded.net/f/ub0dtu i look last AOSP for amami from 150522. But today 150526.
160lightning said:
yes... indeed it seems the JDI panel is the culprit.
We need a few of us with the JDI panel and unlocked bootloader to install the FXP AOSP 5.1 (needs fastboot flash) and run it to try and invoke the black line issue.... so whatever you have had running previously on your device when you've experienced the issue needs to be replicated to see if it happens using this ROM (which has the original thermanager.xml.)
Once we get the results of this we have a way forward to get this issue fixed for any ROM use.
Click to expand...
Click to collapse
F***! There still remain the strips! I have just checked..They begin from the loading screen. I installed 150522
John.D.. said:
F***! There still remain the strips! I have just checked..They begin from the loading screen. I installed 150522
Click to expand...
Click to collapse
Ok.... thanks for trying this John.... lets see if others also confirm.... but don't worry, this was not intended to fix but rather to pin down the source. We are organised for a developer who has a good connection direct to Sony to get the appropriate changes made for those of us with the JDI panels once we know absolutely for sure that the issue stems from the original Sony thermanager.xml which is what resides inside this AOSP 5.1 ROM.
iNDEX3 said:
On http://uploaded.net/f/ub0dtu i look last AOSP for amami from 150522. But today 150526.
Click to expand...
Click to collapse
Where is 150526....? I only see 150522.... but it should not matter which one you have
160lightning said:
Where is 150526....? I only see 150522.... but it should not matter which one you have
Click to expand...
Click to collapse
I took AOSP_L_MR1_150522_amami.zip it to the bottom of the list of references
So... which version of the test?
John.D.. said:
I took AOSP_L_MR1_150522_amami.zip it to the bottom of the list of references
So... which version of the test?
Click to expand...
Click to collapse
I'm fairly certain that any of the builds will be ok to use for this test.... especially as you just tested the latest and still get the black lines. I doubt very much whether thermanager.xml has been changed at all since it was released for amami.
But of course the other ROM devs such as CM may well have made changes.... this is why we need to be sure it originates from the Sony file.... so this test is the logical way to discover the answer.... begin with the source.
160lightning said:
I'm fairly certain that any of the builds will be ok to use for this test.... especially as you just tested the latest and still get the black lines. I doubt very much whether thermanager.xml has been changed at all since it was released for amami.
But of course the other ROM devs such as CM may well have made changes.... this is why we need to be sure it originates from the Sony file.... so this test is the logical way to discover the answer.... begin with the source.
Click to expand...
Click to collapse
Well, I have installed this AOSP_L_MR1_150522_amami.zip version, and the strip is still there)
This latest version, therefore no changes
John.D.. said:
Well, I have installed this AOSP_L_MR1_150522_amami.zip version, and the strip is still there)
This latest version, therefore no changes
Click to expand...
Click to collapse
John.... please can you open your 'about phone' tab and scroll down so you can see 'kernel' and 'Build Number' info showing the AOSP as installed and with the black lines over the top and take a photo of this please....?
The more ammunition we have to give Sony the better for us to get our fix... the right people at Sony can then see with their eyes also.....
160lightning said:
John.... please can you open your 'about phone' tab and scroll down so you can see 'kernel' and 'Build Number' info showing the AOSP as installed and with the black lines over the top and take a photo of this please....?
The more ammunition we have to give Sony the better for us to get our fix... the right people at Sony can then see with their eyes also.....
Click to expand...
Click to collapse
Sh*t, I have returned to stock
I can ask somebody from the Russian-speaking community, to make it
John.D.. said:
Sh*t, I have returned to stock
I can ask somebody from the Russian-speaking community, to make it
Click to expand...
Click to collapse
Apologies.... I thought you probably would have returned to your original ROM after the test.... Ideally I should have thought to ask for the photo with original request.... not to worry.... if you can find anyone else this would be a bonus
thanks
I just change my phone from my old one (Xperia C3 Dual) to A2 lite, and the first thing I noticed is that every time I scroll, it fell slower/less responsive; It's like you are scrolling something heavier (that what I fell?). My old phone is really laggy, running android 5.1, but still give me the better feeling when scrolling through setting, fb, web,... Is this how most xiaomi phone is like, or is there something with my unit?
I don't think there's something wrong with your unit. I have the same problem too, especially when typing something (for example in WhatsApp)... If anybody knows a fix, please post it.
After some research, there seem to be a same problem on the mi A1.
(add reddit dot com here)r/Xiaomi/comments/756lh5/facing_motion_blur_issue_on_my_new_mi_a1_texts/
HoangP05 said:
After some research, there seem to be a same problem on the mi A1.
(add reddit dot com here)r/Xiaomi/comments/756lh5/facing_motion_blur_issue_on_my_new_mi_a1_texts/
Click to expand...
Click to collapse
It sends to this topic here in XDA.
It says that it's a screen problem. You could check the LCD model installed in your device entering the test menu *#*#6484#*#* and doing the first test on the list "Version information". Then you could report it here, so we can check if the problem is related to some brand of screens or not.
For my device, that doesn't seem to suffer this problem at the moment, the screen (and other related hardware) is:
Code:
Board ID:
PCBA_V2_GLOBAL
LCD:
oncell,vendor:bird,IC:lol898
TP:
[Vendor]Biel(TP) + EBBG(LCD), [TP-IC]GT917D, [FW]Ver501c,[CFG]Ver0x53
TP surface color:
0x32 Black
BubuXP said:
It sends to this topic here in XDA.
It says that it's a screen problem. You could check the LCD model installed in your device entering the test menu *#*#6484#*#* and doing the first test on the list "Version information". Then you could report it here, so we can check if the problem is related to some brand of screens or not.
For my device, that doesn't seem to suffer this problem at the moment, the screen (and other related hardware) is:
Code:
Board ID:
PCBA_V2_GLOBAL
LCD:
oncell,vendor:bird,IC:lol898
TP:
[Vendor]Biel(TP) + EBBG(LCD), [TP-IC]GT917D, [FW]Ver501c,[CFG]Ver0x53
TP surface color:
0x32 Black
Click to expand...
Click to collapse
Have same LCD as you and do not feel there is a problem with the Input latency. But to be honest sometimes the sensor does not register some touch events. It is really occasionally, for example after unlock the phone with the fingerprint and try to swipe right in the launcher, sometimes I need to touch two times, could be probably the unlock animation still does not finish (but I see the launcher).
Sometimes while typing if I do not press exactly in the center of the letter it does not register my touch input.
Could be probably that I had a Huawei y9 2018 with 18:9 (instead of 19:9) and bigger camera and I used to that and needs more time for the a2 lite.
niko_3100 said:
Have same LCD as you and do not feel there is a problem with the Input latency. But to be honest sometimes the sensor does not register some touch events. It is really occasionally, for example after unlock the phone with the fingerprint and try to swipe right in the launcher, sometimes I need to touch two times, could be probably the unlock animation still does not finish (but I see the launcher).
Sometimes while typing if I do not press exactly in the center of the letter it does not register my touch input.
Could be probably that I had a Huawei y9 2018 with 18:9 (instead of 19:9) and bigger camera and I used to that and needs more time for the a2 lite.
Click to expand...
Click to collapse
No, it's not only you. I have your same problem with the touchscreen, but not always, sometimes it works fine.
BubuXP said:
No, it's not only you. I have your same problem with the touchscreen, but not always, sometimes it works fine.
Click to expand...
Click to collapse
Could be a software issue? I mean not the latency but the not recording touches occasionally.
niko_3100 said:
Could be a software issue? I mean not the latency but the not recording touches occasionally.
Click to expand...
Click to collapse
Yes, I think so, because of it not happening always, and because doing the touchscreen test (from the test menu I posted before) it looks fine.
same problem here i also had this issue on on older redmi note which was fixed by flashing with different firmware.
I can't replicate any of these problems. Maybe I got lucky with the touchscreen model? My version information is the same though..
Happens to me also on home screen with a heavy lwp and typing on messenger. Maybe a cpu or gpu issue? Can't handle the load?
BubuXP said:
It sends to this topic here in XDA.
It says that it's a screen problem. You could check the LCD model installed in your device entering the test menu *#*#6484#*#* and doing the first test on the list "Version information". Then you could report it here, so we can check if the problem is related to some brand of screens or not.
For my device, that doesn't seem to suffer this problem at the moment, the screen (and other related hardware) is:
Code:
Board ID:
PCBA_V2_GLOBAL
LCD:
oncell,vendor:bird,IC:lol898
TP:
[Vendor]Biel(TP) + EBBG(LCD), [TP-IC]GT917D, [FW]Ver501c,[CFG]Ver0x53
TP surface color:
0x32 Black
Click to expand...
Click to collapse
Yay that's the LCD i have
That sounds like a complete dealbreaker...
I was just going to buy the phone tomorrow
I had a similar problem when I had Xposed installed, removed it and now the phone is working great. So if you have Xposed,this is probably your problem.
Can you guys shed some more light on the issue? I am interested how many of you are encountering it and to what level.
No issues here. The phone is smooth, and I neither have Xposed nor Magisk installed.
I have the same problem
Help
i did this , open developer option then tick force gpu rendering and set animation scale to 0.5
it helps to get rid off laggy
anyone using crossbreeder lite (magisk module) on a2lite?
Me too with Mi 6x,
having high latency input and got keyboard typing errors, latency is prominent when scrolling smth even in settings scrolling. I hav compared with redmi note 5 side by side and note 5 did really fast touch TBH...
may b it got fixed by getting miui + touchpanel firmware updates Zzz
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.
Hi,
I'm using Bliss-v14.10-x86_64-OFFICIAL-opengapps-20230201 on a Dell optiplex 7050 micro with 16gb RAM and a Dell 2418HT touch screen monitor.
Video in apps is corrupted with green and black bars. The video plays smoothly but the entire screen is covered with thin alternating green/black bars.
I can play video fine with firefox/via etc.
I have tried many kernel parameters, such as
video=1920x1080, other valid resolutions
video=HDMI-1:d video=1920x1080, other valid resolutions
video=vga
vga=hex codes/decimal
vga=ask
nomodeset
xforcevesa
nomodeset xforcevesa
uc_mode=vesa (i believe that was it)
i've tried using the vga output instead of hdmi, with all the same parameters
If I choose a valid resolution below 1920x1080, the console seems to change resolution while booting but Bliss never changes, it's always 1920x1080.
The issue seems to persist in Bliss 15.8.4, and across gapps and foss versions. (edited: had Bliss 16 instead of 15)
Here is a screenshot that was taken in an app called Devinfo. Thank you to anyone who can help.
switch gralloc to something else like
Code:
GRALLOC=minigbm HWC=drm_minigbm
on kernel parameter.
HMTheBoy154 said:
switch gralloc to something else...
Click to expand...
Click to collapse
Thank you very much. Everything is working great now.
When I tried both parameters the green and black bars would blink.
When I tried just GRALLOC=minigbm by itself the green/black bars disappeared and everything is fine.
twolittlepennies said:
When I tried both parameters the green and black bars would blink.
Click to expand...
Click to collapse
I don't understand, can you explain ?
HMTheBoy154 said:
I don't understand, can you explain ?
Click to expand...
Click to collapse
I'm unable to replicate what happened. The green and black bars were no longer static but now flashed on and off like on a switch, which is the first and only time it ever happened.
I'm sure I did something wrong.
Everything works great, and I'm (now) using both of the parameters you provided. Thanks again.
And thanks to everyone who worked so hard to bring Android to PC.
twolittlepennies said:
I'm unable to replicate what happened. The green and black bars were no longer static but now flashed on and off like on a switch, which is the first and only time it ever happened.
I'm sure I did something wrong.
Everything works great, and I'm (now) using both of the parameters you provided. Thanks again.
And thanks to everyone who worked so hard to bring Android to PC.
Click to expand...
Click to collapse
Hi, please can You write out the steps, on how to fix that issue. Where do I input aforementioned commands and so on.
Please, for the love of god, someone guide me this ****fest. I NEED to fix the exact same issue. Ive been siting here for hours and hours trying to find out how the F* can I modify the system property You guys are talking about. My brain is melting.
Boot the device, when you see the boot selection screen hit 'e' to edit the boot parameters.
on the second line after 'quiet' put the following
'GRALLOC=minigbm' 'HWC=drm_minigbm'
then hit f10 to boot and see if it fixed it.
if it did, you can make it permanent by (in my case) doing the following
boot back to the boot selection screen and pick debug to boot
after it boots, type
mkdir /mnt/hd
mount /dev/sda1 /mnt/hd
vi /mnt/hd/EFI/Android/android.cfg
hit 'i' to be able to make changes
go to almost the bottom and look for "Create Main Menu"
on the first entry, after quiet, enter GRALLOC=minigbm HWC=drm_minigbm
hit escape
hold shift and type :
then type wq and hit enter
vi should save and quit
type
umount /dev/sda1
then reboot
this is what I did in my case, there is probably a better way. I'm using Bliss 15.8.4 on bare metal.