Author Topic: Screen now bad  (Read 8631 times)

tonyjih

  • Posts: 29
Re: Screen now bad
« Reply #20 on: December 13, 2019, 02:23:51 am »
I'll have a look asap

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #21 on: December 13, 2019, 03:25:30 am »
AFAIK on discord there is only one user that reported their screen going bad (ReverendS3rvo), not two.
Hey, that's me. Lol
Here's a video of what mine was doing. Pretty much the same deal.
<a href="https://www.youtube.com/watch?v=soqJpoXxFnA" target="_blank">https://www.youtube.com/watch?v=soqJpoXxFnA</a>
I recommend that Discord as well.
That is *exactly* what mine is now doing.  Never been dropped, matter of fact it's never left my home.
How did you fix it?

Recce

  • Posts: 58
Re: Screen now bad
« Reply #22 on: December 13, 2019, 06:16:27 am »
Looks exactly like what had happened to my Samsung 55" TV early this year. Initially there's only a few vertical lines, then more and more started appearing and covering almost the whole screen.

I would think this is a hardware issue.

pcercuei

  • Posts: 1676
    • My devblog
Re: Screen now bad
« Reply #23 on: December 13, 2019, 09:16:16 am »
I'll have a look asap
Try with these settings:
320, 240, 320, 240, 60, 30, 8, 60, 20, 8, 2
« Last Edit: December 13, 2019, 10:33:46 am by pcercuei »

a330boy

  • Posts: 174
Re: Screen now bad
« Reply #24 on: December 13, 2019, 05:03:15 pm »
I'll have a look asap
Try with these settings:
320, 240, 320, 240, 60, 30, 8, 60, 20, 8, 2

for those who are willing to test the kernel building where did these magic numbers came from ??
thanks !!

pcercuei

  • Posts: 1676
    • My devblog
Re: Screen now bad
« Reply #25 on: December 13, 2019, 06:24:48 pm »
I'll have a look asap
Try with these settings:
320, 240, 320, 240, 60, 30, 8, 60, 20, 8, 2

for those who are willing to test the kernel building where did these magic numbers came from ??
thanks !!

Revisited values (I think I had them swapped before):
320, 240, 320, 240, 60, 16, 6, 20, 60, 2, 8.

The values are:
bw, bh, dw, dh, fclk, hsw, vsw, elw, blw, efw, bfw.

The screen is 320x240 and you want 60 Hz, so
bw = dw = 320,
bh = dh = 240,
fclk = 60.

You want a perfect 60 Hz from a 6 MHz pixel clock, so you want to find values that gives you:
(320 + elw + blw) * (240 + efw + bfw) * 60 == 6,000,000

One solution is 400 * 250 * 60 == 6,000,000,
which means (elw + blw == 80) and (efw + bfw == 10).

Then in the datasheet, these constraints are set:
- H back porch (blw) between 3..43 pixclocks,
- H front porch (400 - dw - blw) between 2..75 pixclocks,
- V back porch (bfw) between 2..12 lines,
- V front porch (250 - dh - bfw) between 2..37 lines,
- HSYNC (hsw) between 2..43 pixclocks and below H back porch value,
- VSYNC (vsw) between 2..12 lines  and below V back porch value.

So just I pick blw == 20, which means elw == 60, and bfw == 8 which means efw == 2, in order to validate the equation. Then hsw == 16 / vsw == 6, since they just need to be smaller than blw / bfw respectively.

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #26 on: December 13, 2019, 06:47:48 pm »
I don't have a dev environment set up for this but would be willing to test a kernel someone's already compiled with these new numbers.

a330boy

  • Posts: 174
Re: Screen now bad
« Reply #27 on: December 13, 2019, 07:32:58 pm »
I'll have a look asap
Try with these settings:
320, 240, 320, 240, 60, 30, 8, 60, 20, 8, 2

for those who are willing to test the kernel building where did these magic numbers came from ??
thanks !!

Revisited values (I think I had them swapped before):
320, 240, 320, 240, 60, 16, 6, 20, 60, 2, 8.

The values are:
bw, bh, dw, dh, fclk, hsw, vsw, elw, blw, efw, bfw.

The screen is 320x240 and you want 60 Hz, so
bw = dw = 320,
bh = dh = 240,
fclk = 60.

You want a perfect 60 Hz from a 6 MHz pixel clock, so you want to find values that gives you:
(320 + elw + blw) * (240 + efw + bfw) * 60 == 6,000,000

One solution is 400 * 250 * 60 == 6,000,000,
which means (elw + blw == 80) and (efw + bfw == 10).

Then in the datasheet, these constraints are set:
- H back porch (blw) between 3..43 pixclocks,
- H front porch (400 - dw - blw) between 2..75 pixclocks,
- V back porch (bfw) between 2..12 lines,
- V front porch (250 - dh - bfw) between 2..37 lines,
- HSYNC (hsw) between 2..43 pixclocks and below H back porch value,
- VSYNC (vsw) between 2..12 lines  and below V back porch value.

So just I pick blw == 20, which means elw == 60, and bfw == 8 which means efw == 2, in order to validate the equation. Then hsw == 16 / vsw == 6, since they just need to be smaller than blw / bfw respectively.

Got it. ;)
tyvm

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #28 on: December 13, 2019, 11:03:53 pm »
[email protected] is still stalling.  That was the retrogame300.com website I ordered it from.
Until they replace my broken unit, I'd recommend staying away from them.

Second unit I ordered from retromimi as a gift for a friend is still doing OK.  He enjoys it very much and so far the screen hasn't crapped out on him.  And retromimi had some fast drop-shipping straight from the factory, unlike the above named site.

Calling it done with fly-by-night Chinesium handhelds like this once Retromimi gets around to shipping me my pre-ordered PG2, which will probably be after they're done shipping a few dozen free ones to YouTubers to drum up more sales.

Back to my 6 year-old GCW-Zero for now.  Wish it had some nice updated firmware though...

ReverendS3rvo

  • Posts: 4
Re: Screen now bad
« Reply #29 on: December 14, 2019, 01:28:41 am »
That is *exactly* what mine is now doing.  Never been dropped, matter of fact it's never left my home.
How did you fix it?

I didn't. RMA'd to retromimi. They have a good warranty program. New one just got here. Will wait and see what happens. I'm gonna wait on a good firmware update before I mess with it much more.

elea

  • Posts: 60
Re: Screen now bad
« Reply #30 on: December 14, 2019, 12:32:28 pm »
fwiw retrogame300.com is run by retromimi.

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #31 on: December 14, 2019, 09:29:29 pm »
fwiw retrogame300.com is run by retromimi.
Well, in that case Retromimi is kind of jerking me around.
They want to ship out a new micro-SD card instead of a new unit. 
Yeah, I've used the original shipping micro-SD, and two different Sandisk micro-SD cards bought in-person at Microcenter and known to be good and reflashing the firmware still didn't fix the problem.

Nicofilms

  • Posts: 10
Re: Screen now bad
« Reply #32 on: December 19, 2019, 09:08:16 pm »
Mine has blown away too..vertically lined thast appeared suddenly
the same problem.. Firmware changes didnt repair it...
Its fried may by abnormal parameters or overclok on screen drivers settings...or just be faulty screens...


« Last Edit: December 19, 2019, 09:11:35 pm by Nicofilms »

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #33 on: December 19, 2019, 11:08:17 pm »
Mine has blown away too..vertically lined thast appeared suddenly
the same problem.. Firmware changes didnt repair it...
Its fried may by abnormal parameters or overclok on screen drivers settings...or just be faulty screens...
Same thing that happened to mine.
I think it's a batch of faulty screens and we're probably going to see more and more going bad as time goes on.

Nicofilms

  • Posts: 10
Re: Screen now bad
« Reply #34 on: December 20, 2019, 07:24:57 pm »
yep...totally agree. there was a bit of discussion about bad timings or overvolts wrong parameters on open dingux operating system screen drivers for RG350...
but if that were the case hundreds not dozens of screens  should have fail down..and by this time we are only a bad luck bunch of 3 or 4 people...at least a few reports only...Because sometimes people talk or explain to bo one... simply drop their faulty item on the litter and end of story...
we will wait and see...if its a plague we will notice early

RxBrad

  • Posts: 19
    • RxBrad.com
Re: Screen now bad
« Reply #35 on: December 20, 2019, 07:32:58 pm »
yep...totally agree. there was a bit of discussion about bad timings or overvolts wrong parameters on open dingux operating system screen drivers for RG350...
but if that were the case hundreds not dozens of screens  should have fail down..and by this time we are only a bad luck bunch of 3 or 4 people...at least a few reports only...Because sometimes people talk or explain to bo one... simply drop their faulty item on the litter and end of story...
we will wait and see...if its a plague we will notice early

Have you tried the most recent 1.7.9.1 Rogue firmware?  I only ask because it looks like you posted this before that version was actually released.  1.7.9.1 is supposed to have specific LCD timing adjustments that might help with this.  Maybe earlier batches of RG-350 LCDs were more tolerant of "incorrect" timings built into previous firmware...

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #36 on: December 20, 2019, 09:44:52 pm »
yep...totally agree. there was a bit of discussion about bad timings or overvolts wrong parameters on open dingux operating system screen drivers for RG350...
but if that were the case hundreds not dozens of screens  should have fail down..and by this time we are only a bad luck bunch of 3 or 4 people...at least a few reports only...Because sometimes people talk or explain to bo one... simply drop their faulty item on the litter and end of story...
we will wait and see...if its a plague we will notice early

Have you tried the most recent 1.7.9.1 Rogue firmware?  I only ask because it looks like you posted this before that version was actually released.  1.7.9.1 is supposed to have specific LCD timing adjustments that might help with this.  Maybe earlier batches of RG-350 LCDs were more tolerant of "incorrect" timings built into previous firmware...
Tried that firmware yesterday and it didn't fix the bad screen.

pcercuei

  • Posts: 1676
    • My devblog
Re: Screen now bad
« Reply #37 on: December 20, 2019, 11:45:12 pm »
I get these fade-outs with the 5.5 kernel, and never saw one with the stock firmware, so while I don't discard it being a hardware fault (probably power related), the software definitely has an effect on it.

iball (OP)

  • Posts: 197
Re: Screen now bad
« Reply #38 on: December 21, 2019, 12:04:57 am »
I get these fade-outs with the 5.5 kernel, and never saw one with the stock firmware, so while I don't discard it being a hardware fault (probably power related), the software definitely has an effect on it.
Stock firmware doesn't fix it on mine. 
But based on the several instances of cold solder joints I saw on the mainboard in mine, it's probably just piss-poor QA/QC at whatever place put it all together with the end result being a damaged screen.

Nicofilms

  • Posts: 10
Re: Screen now bad
« Reply #39 on: December 26, 2019, 06:36:32 pm »
another one bites the dust....faulty screen reported by an user of telegram rg 350 spanish forums...directly faulty from factory shopped at retromimi.com

here the video proof...

https://t.me/rg350spain/18133

 

Post a new topic
Post a new topic