Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Touch screen does not respond on Hanvon E960 plus #4630

Closed
OSIMLY opened this issue Feb 21, 2019 · 8 comments
Closed

Touch screen does not respond on Hanvon E960 plus #4630

OSIMLY opened this issue Feb 21, 2019 · 8 comments

Comments

@OSIMLY
Copy link

OSIMLY commented Feb 21, 2019

  • KOReader version: KOReader 2019.02
  • Device: Hanvon E960 plus

Issue

It can be installed and started normally, but the touch screen of the device does not respond.

Steps to reproduce

Start app, touch screen to operate.

Eink test

  • Manufacturer: Freescale
  • Brand: Freescale
  • Model: EVK_MX6SL
  • Product: evk_6sl_eink
  • Hardware: freescale
@Frenzie
Copy link
Member

Frenzie commented Feb 21, 2019

Cross-ref #4551.

Since the eInktest utility presumably showed no results I'm afraid there's nothing that can be done for now.

@OSIMLY
Copy link
Author

OSIMLY commented Feb 21, 2019

@Frenzie Thank you for your help. I am sorry to trouble you but would you mind provide a fault-tolerant mode on Android devices?

@Frenzie
Copy link
Member

Frenzie commented Feb 21, 2019

That's the default, if "fault-tolerant" is the right term. The fact that it's not working basically means that neither should any other app without special adaptations. It's just a regular Android app.

On the Onyx devices, for example, the app works either way, but a lack of dedicated support just means you don't get support for special E Ink settings (e.g., full screen refresh after x page turns).

@pazos
Copy link
Member

pazos commented Feb 21, 2019

Duplicate of #3517 and probably of #3567. A freescale device that doesn't respond to touch events. (In fact it responds but the e-ink driver doesn't draw the updates in the framebuffer).

The fact that it's not working basically means that neither should any other app without special adaptations. It's just a regular Android app.

It depends on how the driver is implemented. Normally the driver knows which view is active (a ScrollView, a TextView..) and make changes in the screen accordly (ie: enters in a2 mode when scroll starts and does a full refresh when scroll stops).

KOReader is using the NativeActivity api, but einkTest is using the normal android view hierarchy. That means that the eink activity seems to work (and to respond to touches) but KOReader doesn't.

@Frenzie
Copy link
Member

Frenzie commented Feb 21, 2019

It depends on how the driver is implemented. Normally the driver knows which view is active (a ScrollView, a TextView..) and make changes in the screen accordly (ie: enters in a2 mode when scroll starts and does a full refresh when scroll stops).

A lack of explicit support, whether in the app or in the driver, should mean inefficient or possibly inappropriate updates. Doing nothing instead is so inane it boggles the mind.

To be fair, we're probably looking at a situation where it's a miracle that the programmers were able to put out a halfway functional hack job at all.

@OSIMLY
Copy link
Author

OSIMLY commented Feb 22, 2019

@Frenzie @pazos Thank you. I really like this application, simple interface and powerful function. It would be great to get Koreader working on the Hanvon devices.

@pazos
Copy link
Member

pazos commented Feb 22, 2019

@OSIMLY: closing this issue, you can track progress in #3517

@pazos pazos closed this as completed Feb 22, 2019
@pazos
Copy link
Member

pazos commented Jun 14, 2019

@OSIMLY : we added a driver for freescale. Please follow #4551 (comment) and report.

If the tests don't work you can try #4881 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants