Dark mode on Libra H2O

[Semwize]

David, I generally meant this message.

[Pjama]

Using the setup from Robert (thank you again), I at least have a workable pseudo-dark mode.

I can change between the two modes by powering off and on again. Which is a bit clunky, but it works.

I know it is using the old invert screen command, because everything is inverted, not just the inside of books.

I still don’t understand why the dark mode used to work for me and no longer does, but I’m going to leave it for now as I have a useable workaround.

[NiLuJe]

@Semwize: I was basing my answer on https://www.mobileread.com/forums/sh...3&postcount=23, where the error message somewhat implies an "outdated" NM (although the actual error message may not be entirely too helpful on that front, ping @geek1011 ;p).

EDIT: Which is indeed the exact error I get when running the last NM release, as opposed to a build from the `elipsa` branch that features the new option .

[Semwize]

Originally Posted by NiLuJe

EDIT: Which is indeed the exact error I get when running the last NM release, as opposed to a build from the `elipsa` branch that features the new option .

I have already written this, verbatim. But interestingly, they persistently claim that they have installed a new version of NM, more than once. I don't know what to think)) And in both cases we are talking about Libra.

[Pjama]

Originally Posted by NiLuJe

@Semwize: I was basing my answer on https://www.mobileread.com/forums/sh...3&postcount=23, where the error message somewhat implies an "outdated" NM (although the actual error message may not be entirely too helpful on that front, ping @geek1011 ;p).

EDIT: Which is indeed the exact error I get when running the last NM release, as opposed to a build from the `elipsa` branch that features the new option .

Does this mean I should use the Elipsa version somehow? I really don’t understand. And I definitely get the error implying an outdated NM. Even though I’m using the most up to date one for the Libra.

I don’t know how to use builds from git hub so I need to wait until the non-Elipsa NM is updated to include workability for the dark mode toggle. Is that correct?

ETA: (Still doesn’t explain why it worked for me before.)

[NiLuJe]

As mentioned earlier, the OCP bundles the release version of NM. Besides a failed install of the newer dev build, that's the only sensible reason I can think of for your experience .

(The name of the branch is irrelevant, it was simply named elipsa because that was the only device with that option at the time).

[Pjama]

Originally Posted by NiLuJe

As mentioned earlier, the OCP bundles the release version of NM. Besides a failed install of the newer dev build, that's the only sensible reason I can think of for your experience .

(The name of the branch is irrelevant, it was simply named elipsa because that was the only device with that option at the time).

Hi, yeah I originally used the one-click package, when I was installing KOreader, but after my last reset, I used the most recent stand alone Nickel zip, as linked to earlier in this thread. Shouldn’t that one work? It doesn’t for me.

I have tried various things, and it’s been confusing for me living through it, I’m sure it’s much more confusing reading about it. Thanks for trying

[Pjama]

And suddenly, I have it working!

Only thing I did differently this time was to delete the previous tgz file from the .kobo directory - even though it had the same file creation date of 7/21, that seemed to do the trick! Very weird. Thanks everyone for helping.

I wish I'd asked for help in the first place instead of doing all the resets and losing my badges and reading history. Ho hum. It was just five months worth, will be easy to build it up again.

[DNSB]

Originally Posted by Pjama

And suddenly, I have it working!

Only thing I did differently this time was to delete the previous tgz file from the .kobo directory - even though it had the same file creation date of 7/21, that seemed to do the trick! Very weird. Thanks everyone for helping.

I wish I'd asked for help in the first place instead of doing all the resets and losing my badges and reading history. Ho hum. It was just five months worth, will be easy to build it up again.

If there was a KoboRoot.tgz file in the .kobo directory, that indicates that an error prevented it from installing as a successful install will delete the KoboRoot.tgz file as part of the install cleanup.

[ZodWallop]

Originally Posted by davidfor

Dark Mode is a replacement for Invert Screen... But, it is only officially supported on the Elipsa... as it needs a new waveform to work properly.

Is there any reason for that or is it just the way Kobo programed it? Don't all (current) Kindles have dark mode now? If so, are they using the same new waveform as the Elipsa?

[NiLuJe]

@ZodWallop: IIRC, it's only implemented properly on Zelda devices (i.e., the Oasis 2 & 3), so, not quite the full current lineup .

And, yeah, AFAICT, the waveform and processing code is mostly designed by eInk (not Kobo, and not even their OEM), so that's not something that can just pop up out of nowhere .

(But, yeah, the implementation is similar, except that the Kindles do some extra trickery to the frontlight level to alleviate the flashing issues even more).

[davidfor]

Originally Posted by ZodWallop

Is there any reason for that or is it just the way Kobo programed it? Don't all (current) Kindles have dark mode now? If so, are they using the same new waveform as the Elipsa?

Basically what @NiLuJe said. But, they are not exposing the option on the older devices as they do not believe it gives a good enough result. They, or at least the Kobo developers, accept you can do it using the config file, and that becomes a user choice to hack the device. And anything else they did, would cost money (paying someone for the waveform or paying someone to answer a phone and explain why it didn't work very well) without any chance of them earning money from it.