KindleLazy - remote control page turns + brightness

[banid0]

Right now I am trying just to work with native reader.

Did you manage to do it?

[NiLuJe]

There were patches and ideas about how to do the whole thing better/saner for pure KOReader use in the early days, IIRC.

[banid0]

I am sorry I don’t understand.

I am not a koreader user.

What’s the best way of using a PowerPoint presenter to turn pages on a PW4 with jb?

[banid0]

I have managed to find what I bought

https://a.aliexpress.com/_mP2weY7

I bought the air Mouse version
I have and micro USB adapter that it works, as both work together on an android phone

But I can’t manage to work in kindle
The receiver doesn’t have a led, but it appears to me the kindle doesn’t give it power as the presenter never stabilizes the led/connection.

I only have the kual and kindlelazy installed
Is there something else I need that I didn’t installed?

[arooni]

The moment that someone gets this working on koreader I'm buying that presenter. Maybe I should buy one from aliexpress now since it'll take a few months to arrive lol

[banid0]

But is it possible to put it to work in native reader?

[arooni]

so the consensus is still: no way to make this work with koreader correct?

[NiLuJe]

@arooni:

Originally Posted by NiLuJe

There were patches and ideas about how to do the whole thing better/saner for pure KOReader use in the early days, IIRC.

[katadelos]

If anyone is wondering why support for KOReader isn't currently possible, it's because KOReader works very differently to the stock Kindle reader.

KindleLazy works by writing raw touch events back to the touchscreen event device, which isn't an issue with the stock reader. However, the GUI of KOReader is drawn on top of the default Lab126 GUI, which means that it has to issue the EVIOCGRAB ioctl to take full control of the touchscreen event device (otherwise, touch events will be sent to the window that is actually in focus - i.e the Lab126 GUI - and everything will break horribly). When that ioctl is issued, KindleLazy can't access the event device either. It's possible to bypass this by creating a named pipe, patching KOReader to use this an a secondary event device and writing to the pipe instead but this is incredibly hacky and unreliable.

The other issue is orientation detection; KindleLazy uses lipc-get-prop to detect this, but KOReader causes problems here too - attempting to read the orientation property whilst KOReader is running causes lipc-get-prop to hang, and even if it didn't, the value it returns would still be incorrect as KOReader handles orientation internally. To work around this one, you'd need to patch KOReader to provide an interface that allows you to access information like this from outside of the program. I did find a way to do this (by creating a query/response protocol using named pipes and input events/handlers to communicate between KOReader and a Python port of KindleLazy that I'm working on) but again, this is a hideously hacky way of doing so.

[NiLuJe]

@katadelos: KOReader already has a fake input sink, you could *probably* plug into that with some more FAKE event codes and call it a day?

(I don't recall the breadth of the original proiect, but I kind of fail to see where orientation comes into play if we're just talking about PgNext/PgPrv?)

----

Or tackle this another way, and create a new user-space input event device, one that proxies the hardware one, plus includes the KindleLazy stuff, and just patch KOReader's devcap to point to the synthetic one and patch the event mapper to include new keycodes if need be.

[NiLuJe]

Or, well, just a plain new custom user-space evdev device, since KOReader doesn't really care how many input event devices it needs to listen to .

[banid0]

But is possible to put kindle lazy to work right now with the stock reader?
That's the only thing I wanted

[jabingb]

Will the jailbreak work on this s/w version of a PW3? The third number is less than 7 or does that only apply up to 5.8.x?

https://www.mobileread.com/forums/at...1&d=1611369451

[j.p.s]

Originally Posted by jabingb

Will the jailbreak work on this s/w version of a PW3? The third number is less than 7 or does that only apply up to 5.8.x?

https://www.mobileread.com/forums/at...1&d=1611369451

5.9.6.1 is the highest version for PW3 software jailbreak and 13 is greater than 9, so no.

But why do you ask in this thread?

[jabingb]

I'm stumbling around with the goal of implementing a remote page turner, where should I be researching this? I presume by your answer I will need to do the hardware serial procedure?