workshop, reduced screen

[Quoth]

Originally Posted by daniel bastida

I think it's too much for me
This is the main board

Nice pic. I don't see any obvious option settings. Likely it's a parameter written in the boot section of flash memory.

Double check the socket for dirt / fluff / hairs and reconnect the ribbon.

[daniel bastida]

Originally Posted by DNSB

A broken substrate is noted for curved lines. Controller/cable issues are noted for straight lines.

To your previous question,
Yes, the screen arrived in sleep mode.

I've reconnected the two flat cables.
The image remains the same, reduced in one corner, and in that useful area it looks perfect... the touchscreen is still fine and still in full screen.

The only thing that's changed is the pattern of horizontal lines in the lower area that's "off-screen."

Now, perhaps what I'm interested in is knowing which e-book models can use this ED060KC1 screen model.

[daniel bastida]

Originally Posted by DNSB

A broken substrate is noted for curved lines. Controller/cable issues are noted for straight lines.

To your previous question,
Yes, the screen arrived in sleep mode.

I've reconnected the two flat cables.
The image remains the same, reduced in one corner, and in that useful area it looks perfect... the touchscreen is still fine and still in full screen.

The only thing that's changed is the pattern of horizontal lines in the lower area that's "off-screen."

Now, perhaps what I'm interested in is knowing which e-book models can use this ED060KC1 screen model.

[daniel bastida]

Any help?

[Renate]

Originally Posted by daniel bastida

Any help?

Yes. I think that it's just misconfigured, possibly from misreading the identity of the panel.
Why did you replace the panel? General failure?

This is Android, right? Do you have ADB enabled?
If you have a problem reconciling touch you can use a mouse if this supports it.
(That's just to get you through testing, not a solution!)

The native display is landscape with the origin in the upper left in your photo, so it looks like it's working fine.
I would have expected that startup would have wiped the entire screen as that stuff is pretty hard coded.

This device, iMX6 is similar to older B&N Nooks.

If you get ADB working, try:

C:\>adb shell
$ wm size
$ wm density
$ wm size reset
$ wm density reset

If it gives you funny numbers on size you can try

$ wm size 1072×1448

But always use bigxsmall or smallxbig whichever you got the first time.

[Renate]

I think that it thinks that the display is 768 x 1024.

[daniel bastida]

Originally Posted by Renate

I think that it thinks that the display is 768 x 1024.

I thought the same, but the resolution of the ED060KC1 screen and the book is 1072x1448

[daniel bastida]

Originally Posted by Renate

Yes. I think that it's just misconfigured, possibly from misreading the identity of the panel.
Why did you replace the panel? General failure?

This is Android, right? Do you have ADB enabled?
If you have a problem reconciling touch you can use a mouse if this supports it.
(That's just to get you through testing, not a solution!)

The native display is landscape with the origin in the upper left in your photo, so it looks like it's working fine.
I would have expected that startup would have wiped the entire screen as that stuff is pretty hard coded.

This device, iMX6 is similar to older B&N Nooks.

If you get ADB working, try:

C:\>adb shell
$ wm size
$ wm density
$ wm size reset
$ wm density reset

If it gives you funny numbers on size you can try

$ wm size 1072×1448

But always use bigxsmall or smallxbig whichever you got the first time.

Thanks everyone for the answers.

Please, what is ADB?

[Renate]

Originally Posted by daniel bastida

I thought the same, but the resolution of the ED060KC1 screen and the book is 1072x1448

Yes, they are both the same.
But your device thinks that it's connected to a 768 x 1024 display.

Originally Posted by daniel bastida

Please, what is ADB?

That is "USB debugging".
You need to enable it in Settings under "Developer options".
You need to enable that under Settings, About, Build number 7 times.
Google "enabling ADB".

[daniel bastida]

Originally Posted by Renate

Yes, they are both the same.
But your device thinks that it's connected to a 768 x 1024 display.


That is "USB debugging".
You need to enable it in Settings under "Developer options".
You need to enable that under Settings, About, Build number 7 times.
Google "enabling ADB".

Thanks, Renate.
I'll try. I'll need time and luck.

[PeterT]

You also need to install ADB on the PC...

[Renate]

Yeah, but I didn't want to scare them off until they realized that they needed that too.

Also, once ADB is working, a screen grab will be informative.
We'll see how big it is and what it shows.
You can try my AdbGrab.exe (in my sig).

C:\>adb devices
12345678
C:\>adbgrab.exe /s.5

This also allows you to mouse on the desktop which simplifies the scaling problem of the touch screen.

[daniel bastida]

Originally Posted by Renate

Yeah, but I didn't want to scare them off until they realized that they needed that too.

Also, once ADB is working, a screen grab will be informative.
We'll see how big it is and what it shows.
You can try my AdbGrab.exe (in my sig).

C:\>adb devices
12345678
C:\>adbgrab.exe /s.5

This also allows you to mouse on the desktop which simplifies the scaling problem of the touch screen.

I've only been able to install ADB on the PC.
I don't see a "build number" on the e-reader.
Can you see it in the attached photos?

[Renate]

Try tapping on the "Software"
I presume that your touch is scaled by 0.7 and you have to tap wide to hit the correct thing?
Try tapping everything on that page.

[daniel bastida]

Originally Posted by Renate

Try tapping on the "Software"
I presume that your touch is scaled by 0.7 and you have to tap wide to hit the correct thing?
Try tapping everything on that page.

I have touched (7 touches) on software (the number) and on the other numbers... without result.
I use a 0.7/1.41 template for a rough approximation.