Screen tearing about miyoocfw

[dilbirin]

I found a hardmod on this site:

https://steward-fu.github.io/website/handheld/miyoo/fix_te.htm

But I guess, that's for v1. I can't find on my bittboy v2.

[TriForceX]

Yeah, this is a hardware problem, it wont be fixed maybe until the 3rd release of the console (rev3).
We are working to make the guide for rev1, i dont know if theres one for rev2.
Stay tuned.

Edit: This problem wasnt fixed on lastest revisions, is still present.

[alexandershalin]

Is it correct that this issue was not fixed in rev3?

[krasny2k5]

I also would like to know if v3 fixes the screen tearing problem.

[TriForceX]

@alexandershalin @krasny2k5 Bittboy developers decided to delay the old v3 and they already released a different v3 (ghost key fix + glass screen), but screen tearing was not fixed yet...

I remind you thats a hardware issue. According to steward, they messed up on TE pin because it only reports 30 Hz, not 60Hz. The tearing occurs because it is trying to refresh twice
So it can only be minimized...

[chipxsd]

Can you give more detail on the hardware issue? What's the TE pin? Is it the thing that selects the 30Hz/60Hz refresh rate?

I wonder how the screen is driven anyway, I'd love to see the schematics, if they're available?

[TriForceX]

Can you give more detail on the hardware issue? What's the TE pin? Is it the thing that selects the 30Hz/60Hz refresh rate?

I wonder how the screen is driven anyway, I'd love to see the schematics, if they're available?

This is the last conversation with @steward about it:

Steward says:
-------------
ok
it is hard to explain something
first
not all of screen has TE pinout
ex: v2 bittboy
second
the TE pin is open on PCB for some bittboys
so, for v1, you need short it manually
and
even though all of hardware are ready
the trigger rate is only 40hz in f1c500s
I mean TE is output around 60hz
but f1c500s only get 40hz in kernel driver
so, many issues
I dont know how to say that
but
if you fix your hardware, maybe, you can check kernel whether it is somgthing I overlooked
any question ?

People says: 
-------------
kernel gets 40Hz instead of 60Hz because it is too slow to process it or the signal got lost in hw, for example by lack of filtering or filtering too much?
i have bittboy v2.5

Steward says:
-------------
we use oscilloscope to double check and hw can ouput 60hz
in kernel, I just accumulate and print it
and the result is 40hz
even though boost priority for innterrupt
the result is same as without boos priority
we also check with some engineers who developed f1c500s
they havent checked this when produce this ic
I mean no any verification with interrupt speed
so, I dont know whats the root cause
maybe, kernel or IC
if you know this, please tell me
thanks :)

You can get more info at #new-bittboy or #pocket-go channesl on our Discord https://discord.me/retrogamehandhelds Some developers like @steward can give you more details about it, but i warn you no one is interested in the Bittboy development anymore due the main company doesn't support us...