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

Tolino Shine 4 EPD support #532

Open
pazos opened this issue Dec 11, 2024 · 4 comments
Open

Tolino Shine 4 EPD support #532

pazos opened this issue Dec 11, 2024 · 4 comments

Comments

@pazos
Copy link
Member

pazos commented Dec 11, 2024

continuing from the post

One more thing need to mention: There is a property 'persist.mode.global' which the default value is 8000 after reboot. The NGL4 driver dose not work with value 8000. If i set the value to 0 (after i root the device and use adb shell setprop), the NGL4 driver will work.

When I for this driver it looked like any internal code indeed tried to reset it to zero everywhere, probably disabling this global mode of refresh to be active. On my Nook Glowlight 4e it is zero on start, probably depends on the manufacturer. Random thoughts:

  • The problem with these system properties that they require root access to be changed so not so great to be used in KOReader
  • Just refreshed my understanding, according to the docs, persist properties survive reboot, to theoretically this can be some last software that you used before the reboot that forgot to reset it.
  • For ones with root access there's always several ways to force it to zero on start (independently of KOReader), but this solution is not ok for mass use.
  • I recall that I seemed to notice the initial value for this property in some system start up script, but I'm not sure. Just looks at some variant of Android image from my device, could not find it in default.prop and system/build.prop so it can be false memories.
  • can not currently decode this 8000 value, at least for the sources I managed to quickly find.

Originally posted by @Codereamp in koreader/koreader#11110 (comment)

@Codereamp
Copy link
Contributor

A suggestion for @f-coco (from the post). Have you noticed the same effect on your Tolino 4 (If it is ... Shine, I'm not very familiar with this manufacturer's models :) ? Maybe you can add something? Thanks

@f-coco
Copy link

f-coco commented Dec 20, 2024

A suggestion for @f-coco (from the post). Have you noticed the same effect on your Tolino 4 (If it is ... Shine, I'm not very familiar with this manufacturer's models :) ? Maybe you can add something? Thanks

Ok, I will check all my B300 devices made by Netronix this weekend.

@f-coco
Copy link

f-coco commented Jan 4, 2025

For Mooink S, run getprop from adb shell after a reboot.
persist.mode.global=0
For Tolino Shine 4, run getprop from adb shell after a reboot.
persist.mode.global=0
For Tolino Vision 6, run getprop from adb shell after a reboot.
persist.mode.global=0

For Mooink S and Tolino Shine 4, these 2 devices are not offically supported by Koreader yet because the devices info are not in the Koreader database. I fake these 2 devices as a Nook Glowlight 4, the Koreader works fine on those 2.

Tolino vision 6 is already supported by Koreader in the latest stable version.

@Codereamp
Copy link
Contributor

For Tolino Shine 4, run getprop from adb shell after a reboot.
persist.mode.global=0

Somehow I missed the fact that you're the same person :) Ok, does your latest observation (here in quote) make your previous one about necessary to change persist.mode.global after reboot irrelevant? So refresh works as expected after reboot and doesn't requires additional actions?

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

No branches or pull requests

3 participants