I am working on building a computer for my motorcycle. It consists of a 5" touch screen runing 800x480 with a rockpi 4b+ running android 11. In the past I was running and odroid with android 9 and to fix the resolution I was able to access the boot partition and edit the env.ini and fix the resolution and timing. The rockpi is different as I am unable to access the boot partition once its installed on the onboard emmc. I talked to rockpi about how I can adjust the timings for the screen. They said would have to edit the boot.img to do this. I have come to the masters to see you guys can help me out. I have never edit a boot image before and don't even know what file to edit. Any help would be appreciated.
Here is a video of the flickering.
Related
Hello everyone,
I saw multiple threads already opened for the burn in issue (which I also have from time to time) and I wanted to share my solution with you. It is a simple video, which is changing the three main colors (RGB) very fast. Played for 5-10 minutes on a loop will erease any glitches on your screen (softkeys burned into the screen which is the most commen problem).
Here is the link in youtube:
http://www.youtube.com/watch?v=liMySLZkF5o
Here is the mp4 file to upload directly on your device:
STUCK PIXELS or BURN INS RGB VIDEO FIX
http://www.megaupload.com/?d=878ZGHF0
To the Moderators: I searched over the forum for a solution and did not find it, I hope I am not overlaping with another old thread, just wanted to help.
Regards.
Hi
I don't mean to thread-crap
but....
after having discussed this issue with HTC themselves they have said its a hardware based issue
whilst its true running a slide show/video full screen displaying solid blocks of colour are likely to erase screen burn-in, the issue will still persist, the underlying cause is a faulty screen panel which must be replaced
Could you upload it somewhere? I could use it, i have a stuck pixel. It's blue on a black background, it should fix it.
I once fixed a big bright spot on a LCD TV with one of these RGB movies.
Hi duke_stix, I agree with you that it could be a faulty display panel, but however I didn't find anyone had it replaced due to that issue. And I know it is a temporary solution, but at least there is a solution
AndyJ91, download link available, hope it helps.
Hey guys I have been playing around with the Gingerbread leaks for the O3D and I am loving it so far, but I only have one problem with GB at this stage.
The problem being if I set the LCD Density to 167 (Got used to it on all my Android devices) the Rom only works until it locks. Once it locks the first time after the setup it goes into a boot loop and the only way to restore that would be to flash a ROM with lcd_density set to 240. Then the Rom works perfectly without any issues.
I have noticed that no LCD Density changer app works on the O3D, Ive used a few for different devices and they all worked. I have also seen that there are 2 entries for lcd_density in build.prop. Removing either changes nothing. Changing them both breaks the phone too.
Would there be anyone wise enough to be able to get this done, make the LCD desity either changeable or 167?
Edit : If I set the density lower in 20 increments with font changer (root) then i get it down to 200 before causing bootloops. I dont understand why, it worked fine in Froyo
I appreciate the help.
I cant believe everyone with an optimus 3D runs it at 240 LCD density...
Is there anyone that could help with this?
I have the same problem but didn't bother to ask since i don't think there is a solution until we get the official release.
I tried 160 with my TV and got the perfect resolution. But as you say, as soon as i reboot my phone i get into a boot loop.
I think that the only thing we can do at the moment is to restore the density to 240 if we reboot the phone and put it back to 160 or whatever when it has booted up again.
This is my problem:
I set the density to something below 240, then my phone gets stuck in a bootloop, so I enter CWM and make a factory reset, then i can get in to the phone with the new density. The phone works great until i reboot my phone which will get my phone in a bootloop. This time, the factory reset wont work. So i have to restore the system partition and start from the top.
As you say, it worked fine in froyo for me as well.
EDIT:
I will take a look at build.prop and manually change the settings.
Okay I found the problem and a solution.
I created a new thread so the discussion about the supported densities can be held there separately.
http://forum.xda-developers.com/showthread.php?t=1351420
I'm in the middle of porting CWM 6.0.0.x to dell devices, and I've gotten all but one.
Background:
CWM 6.0 prefers displays of type:
24/32bpp color Edit: after fiddling around with it, this isnt actually true.
Right side up
Double buffered(?)
My last device I'm having trouble with (Dell Streak 5):
16bpp
Upside down
Single buffered(?)
I've re-added screen flipping (for point 2) and fixed the pixels for point 1, but I have no idea how to fix point 3.
My exact issue: I can get CWM 6.0 to boot with correct colors on my S5, but every other buffer(?) is blank.
So blank -> correct screen -> blank -> correct screen -> etc.
It's just a graphics issue as it still works fine while black.
CWM 5.5 preferred single buffers but had board config switches to enable RGBX_8888 and double buffering.
But the move to 6.0 broke RGB_565 and single buffering.
I have no idea where in the code to force it to single buffer, I've already fiddled around in <CWM>\minui\graphics.c and besides the color-space changes, there's nothing changed regarding single/double buffering in it.
Here's my device tree if it helps:
DellInc._Streak_120718.rar
Hi,
I reinstalled Samsung UI 9 on my phone.
Since I have a resolution problem.
There are things that doesn't appear on my screen, like the time when I'm on landscape mode.
I think by changing the resolution it would help, but I don't know how to.
Hi
I have adjusted my radio. With a command (roughly) hcttext256 I adjusted the screen resolution. Unfortunately I can't find a way to undo this. Does anyone know how I can reset this setting to the original screen resolution. An attempt to flash the MCU, DMCU with a corresponding DMCT.ext is unsuccessful, here I tried screen:12, screen:13, screen:18.
Please post all possible solutions
Thanks very much
Have to ask, what led you to want to change resolution
It was a mistake. wrong ...