KindleLazy - remote control page turns + brightness

[knc1]

Originally Posted by heavinessruscles

Hi,

I bought a PW3 and did the JB. KUAL and Kindlelazy are installed. The rotate 180 function is working.

I have a different presenter remote, which I think is very generic but doesn't seem to work. What is the process for having the PW3 recognise this different presenter remote?

Many thanks in advance.

Have the required kernel drivers installed.
The kernel drivers required for Kindlelazy are version & build specific.
Translation:
You must provide more information on your device / firmware / install actions for us to have a question we stand a chance of answering.

[mrpops]

Just finished reading this thread in its entirety.
jscris you have a KV model, could you tell me more about your experience with everything.

What firmware version do you have? and have others upgraded to the latest firmware (5.10.2) and reported success with using this (after the prerequisite jailbreaking).

jscris you also noted a large amount of power drain, and this thread seems to hint at the causation being the mod not allowing the device to go into deep sleep. (Is my assessment correct? If so does this still remain, as the post about power drain was quite early in the thread).

If the above is correct, does disabling KL after usage restore the deep sleep functionality of the KV?

Thanks for any insight any of you can share.

[jscris]

Originally Posted by mrpops

Just finished reading this thread in its entirety.
jscris you have a KV model, could you tell me more about your experience with everything.

What firmware version do you have? and have others upgraded to the latest firmware (5.10.2) and reported success with using this (after the prerequisite jailbreaking).

jscris you also noted a large amount of power drain, and this thread seems to hint at the causation being the mod not allowing the device to go into deep sleep. (Is my assessment correct? If so does this still remain, as the post about power drain was quite early in the thread).

If the above is correct, does disabling KL after usage restore the deep sleep functionality of the KV?

Thanks for any insight any of you can share.

That was a long time ago. I'm not using the KV any more but I do remember a large power drain. I was using the same presenter as the developer. I didn't mind charging it often. It was worth it for the remote page turn capability. Sorry, I don't remember which firmware, but I don't think I upgraded after doing the jailbreak. Sorry I can't be of more help. Maybe someone who's using it currently can.

[heavinessruscles]

Originally Posted by knc1

Have the required kernel drivers installed.
The kernel drivers required for Kindlelazy are version & build specific.
Translation:
You must provide more information on your device / firmware / install actions for us to have a question we stand a chance of answering.

Apologies, I should have provided more info.

This is the remote I bought:
Doosl DSIT011
https://bigupgadgets.com/au/doosl-ds...06-kb3303.html

I have a PW3 4gb, serial number starts with G090 G105. Firmware is 5.9.6.1.

Ive run the jail break test app, and that worked so I believe I jail broke it correctly. I also have the jail break book installed.

I have kindle lazy in the kual menu and have used it to flip the screen so I think that’s installed correctly too.

I think the correct steps for using the remote are:
1. Turn on kindle,
2. Plug in USB receiver,
3. Open kindle lazy.

However, kindle lazy seems to crash on opening each time.

Any ideas?

[knc1]

What is the kernel version and build?
as in:

uname -a
Linux HP8300 4.15.0-33-generic #36~16.04.1-Ubuntu SMP Wed Aug 15 17:21:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Obviously, that return info is not from a Kindle, but the command is identical on your Kindle.

[mrpops]

So... all my stuff arrived and I was eager to test it with my Kindle Voyage KV on the latest 5.10.2 firmware. I purchase;
https://www.amazon.co.uk/gp/product/B07HRKP6HS
https://www.amazon.co.uk/gp/product/B06XWYM8PF

installed the latest release 0.9 and it didn't work. I also installed 0.7 and it didn't work.

The only change it seems to have made to my KV was that the physical buttons acted in a weird fashion. A forward click would also initiate a backwards click, as though it was calling both inputs. I suspect its something to do with https://www.mobileread.com/forums/sh...&postcount=112 but I have no proof.

Not sure where to go from here.

I guess i'll fire up evtest and see if the inputs are different. need to install some vm software.
edit: fired up evtest and the keys correspond to the ones listed at OPs initial page. I'm at a loss now what to do.

[knc1]

Originally Posted by mrpops

So... all my stuff arrived and I was eager to test it with my Kindle Voyage KV on the latest 5.10.2 firmware. I purchase;
https://www.amazon.co.uk/gp/product/B07HRKP6HS
https://www.amazon.co.uk/gp/product/B06XWYM8PF

installed the latest release 0.9 and it didn't work. I also installed 0.7 and it didn't work.

The only change it seems to have made to my KV was that the physical buttons acted in a weird fashion. A forward click would also initiate a backwards click, as though it was calling both inputs. I suspect its something to do with https://www.mobileread.com/forums/sh...&postcount=112 but I have no proof.

Not sure where to go from here.

I guess i'll fire up evtest and see if the inputs are different. need to install some vm software.
edit: fired up evtest and the keys correspond to the ones listed at OPs initial page. I'm at a loss now what to do.

Try replying to my post above.
When you do, also post the relevant part of dmesg when the otg and serial modules are loaded.

[mrpops]

I'm not so great at parsing the logs but i'll try my best.

[root@kindle root]# uname -a
Linux kindle 3.0.35-lab126 #2 PREEMPT Tue Dec 4 17:14:27 PST 2018 armv7l GNU/Linux

https://pastebin.com/zkhisH6T full log here but i think its

[  435.420043] pmic_soda_connects_notify_otg_in:391 OTG!
[  435.490077] Unknown wakeup.(OTGSC 0x8282b20)
[  435.630136]
[  435.630143] Schedule OTG enumeration triggered recovery
[  435.630550] max77696_uic_adc_work adcval 0 in_otg 1
[  435.640700] switch to host?
[  436.179760] usb 1-1: new full speed USB device number 2 using fsl-ehci
[  436.389792] usb 1-1: device descriptor read/64, error -71
[  443.650010]  otg_enum_fn not enumerated, catcha!
[  443.656682] usb 1-1: USB disconnect, device number 2
[  443.666356] fsl_otg_event ID changed to [0] during work
[  443.666377] asking for device mode and in host mode, thats okay
[  443.666404] switch to gadget

edit: googling around, is this relevant?
https://ubuntuforums.org/showthread.php?t=1402799
https://www.mobileread.com/forums/sh...d.php?t=276501 maybe https://www.mobileread.com/forums/sh...6&postcount=13 comment is relevant?

further logs https://pastebin.com/zNSTuL9H

it seems like some kind of OTG issue?

it keeps triggering this recovery in the last log, and then sequentially going up in number of device whilst attempting to connect?

hmm

[  147.282655] usb 1-1: new full speed USB device number 2 using fsl-ehci
[  147.492662] usb 1-1: device descriptor read/64, error -71
[  154.762918]  otg_enum_fn not enumerated, catcha!
[  154.769556] usb 1-1: USB disconnect, device number 2
[  154.780057] fsl_otg_event ID changed to [0] during work
[  154.780078] asking for device mode and in host mode, thats okay
[  154.780104] switch to gadget
[  157.720190] usbcore: registered new interface driver usbhid
[  157.720201] usbhid: USB HID core driver
[  158.751617] mousedev: PS/2 mouse device common for all mice
[  160.842917] Unknown wakeup.(OTGSC 0x9280b20)
[  160.992939]
[  160.992945] Schedule OTG enumeration triggered recovery
[  161.003613] switch to host?
[  161.532658] usb 1-1: new full speed USB device number 3 using fsl-ehci
[  161.793688] input: Genius Wireless Mouse as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/input/input3
[  161.794678] generic-usb 0003:0458:0189.0001: input: USB HID v1.01 Mouse [Genius Wireless Mouse] on usb-fsl-ehci.0-1/input0
[  161.801245] input: Genius Wireless Mouse as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.1/input/input4
[  161.801809] generic-usb 0003:0458:0189.0002: input: USB HID v1.01 Device [Genius Wireless Mouse] on usb-fsl-ehci.0-1/input1
[  161.834892] input: Genius Wireless Mouse as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.2/input/input5
[  161.835505] generic-usb 0003:0458:0189.0003: input: USB HID v1.01 Keyboard [Genius Wireless Mouse] on usb-fsl-ehci.0-1/input2
[  169.002870] is_otg_connected() 1 audio_enumerated 1

it seems to find the devices though, i think its to do with the labeling of the input numbers

[knc1]

IIRC, the Amazon kernel build did not (at the time of this project start) ship a complete set of USB serial modules (dynamically loaded drivers, loaded by the kernel).

See first post, where this work is based on the adding of mouse support (which also requires USB serial modules).

Start at post #1 here (or better yet, at the mouse support thread, which this extends).
Look for a mention of the kernel build information, it MUST match what you just listed or the modules have to be rebuilt.
(The kernel will not load modules not built specifically for it.)

OR
do a modinfo command on the modules that this (or the mouse support thread, if KL is using those modules) - they must match:

3.0.35-lab126 #2 PREEMPT Tue Dec 4 17:14:27 PST 2018 armv7l GNU/Linux

This thread was started Sept. 2016, so the modules could not have been built to match a Dec. 2018 kernel.
As I originally posted, build the required modules to match your kernel build or get someone to do it for this project thread.

[mrpops]

i've done

 
[root@kindle root]# ls /dev/input
by-path  event0   event1   event2   uinput

When I attached the otg and other bits, it becomes

[root@kindle root]# ls /dev/input
by-id    by-path  event0   event1   event2   event3   event4   event5   mice     mouse0   uinput

https://www.mobileread.com/forums/sh...&postcount=112

Is this relevant? Is it merely a case of it just not finding the right device inputs?

I'm not fully comprehending what you wrote, are you saying without direct intervention from the developer, because of my updated kernel I won't be able to get this working?

edit: as i additionally added to the previous post, you can see it actually seems to find the devices

[knc1]

Originally Posted by mrpops

i've done

 
[root@kindle root]# ls /dev/input
by-path  event0   event1   event2   uinput

When I attached the otg and other bits, it becomes

[root@kindle root]# ls /dev/input
by-id    by-path  event0   event1   event2   event3   event4   event5   mice     mouse0   uinput

https://www.mobileread.com/forums/sh...&postcount=112

Is this relevant? Is it merely a case of it just not finding the right device inputs?

I'm not fully comprehending what you wrote, are you saying without direct intervention from the developer, because of my updated kernel I won't be able to get this working?

edit: as i additionally added to the previous post, you can see it actually seems to find the devices

Does not require a developer.
Just compile the required modules against YOUR version of the kernel.
Or check every attachment to this and the mouse support thread.
The index page of the forum has a button to list the attachments to a thread.

Or just hang in here, maybe someone will push the button for you.

[mrpops]

okay thank you, i'll put in another 5 or 6 hours tomorrow and use some of those words you mentioned to progress further.

thank you for confirming it seems possible, that really helps motivation.

[knc1]

Originally Posted by mrpops

okay thank you, i'll put in another 5 or 6 hours tomorrow and use some of those words you mentioned to progress further.

thank you for confirming it seems possible, that really helps motivation.

Are you picture oriented?
Pull up the attached picture.
See the files in the path: KindleLazy-0.9/bin/<name>.ko (ko == kernel object)

Amazon posts the sources of the open source things they used, and if your lucky, the compiler they used.

/proc/config.gz on your Kindle should have the configuration file Lab126 used to build the kernel that is running at that moment.
Use that config file + build as modules the ones listed above, follow the kernel build system instructions.

People have been posting on 'net since 1991 on how to build the kernel and its modules - there is no shortage of pre-written directions.
Or hope someone here offers to do the job for you.

And say something nice about my new dog.

[mrpops]

lhasa apso? very cute

discovered this, maybe it will help me tomorrow

Prerequisites

On Ubuntu 12.04, you will need the following packages installed:
  gawk
  wget
  git
  diffstat
  unzip
  texinfo
  build-essential
  chrpath
  socat
  libsdl1.2-dev
  xterm
  libssl-dev


Building the Toolchain


To build the toolchain, You need to setup a poky 1.8.1 environment


To setup environment:

Clone Poky 1.8.1 by following the instruction from https://www.yoctoproject.org/downloads/core/fido181

Execute the folling command to setup a environment
  $ source poky/oe-init-build-env build
  $ cd build

To build toolchain,execute the follwing command after setting up an environment

  $ bitbake gcc-cross

or this

In order to compile the kernel, use the following configs:

	Kindle Oasis:  imx60_duet_defconfig
	Kindle Paperwhite (6th & 7th generation), Kindle Voyage (7th generation), Kindle (7th generation):  imx60_wario_defconfig

Use the following command to run the configs:
    
    make ARCH=arm CROSS_COMPILE=<path to gcc linaro>/bin/arm-linux-gnueabi- <configure>
    
Use the following command to compile:

    make ARCH=arm CROSS_COMPILE=<path to gcc linaro>/bin/arm-linux-gnueabi-

[knc1]

Originally Posted by mrpops

lhasa apso? very cute

discovered this, maybe it will help me tomorrow

Prerequisites

On Ubuntu 12.04, you will need the following packages installed:
  gawk
  wget
  git
  diffstat
  unzip
  texinfo
  build-essential
  chrpath
  socat
  libsdl1.2-dev
  xterm
  libssl-dev


Building the Toolchain


To build the toolchain, You need to setup a poky 1.8.1 environment


To setup environment:

Clone Poky 1.8.1 by following the instruction from https://www.yoctoproject.org/downloads/core/fido181

Execute the folling command to setup a environment
  $ source poky/oe-init-build-env build
  $ cd build

To build toolchain,execute the follwing command after setting up an environment

  $ bitbake gcc-cross

Check the contents of the Amazon source code package for your device/firmware combination.
https://www.amazon.com/gp/help/custo...deId=200203720 (page down, way down)
It may already have the toolchain built.
If not, you can probably use the one NiLuJe has posted in his snapshots thread.




Close, same family of breeds.
Maltese + Yorky == Morky