KindleLazy - remote control page turns + brightness - Page 9

zxczxc · 10-05-2016, 03:40 AM

Quote:

Originally Posted by lucida

OK, all BS aside, for KT3 to work: if there is no OTG support in stock hardware/kernel then we're out of luck. Otherwise, someone needs to build KT3 specified modules. Dropping PW3 prebuilt kernel module in KT3 wouldn't work since they have different kernel version.

Ok this makes perfect sense, thank you.
Would it be as simple as compiling the compiler, just as you instructed and I did for PW3, but this time from the sources for KT3?

I assume I will also have to put the kernel module source on github with KindleLazy? I'll try to do it soon.

knc1 · 10-05-2016, 08:41 AM

Quote:

Originally Posted by zxczxc

Ok this makes perfect sense, thank you.
Would it be as simple as compiling the compiler, just as you instructed and I did for PW3, but this time from the sources for KT3?

I assume I will also have to put the kernel module source on github with KindleLazy? I'll try to do it soon.

It is not explicitly stated in the GPLv2, but common practice seems to indicate that just a hyperlink to where the sources can be found is sufficient.

Unless you made changes to the sources.

I now understand that you have not made changes to the kernel sources (as posted by Amazon @ https://www.amazon.com/gp/help/custo...deId=200203720 ) but only building some modules that Amazon does not normally ship.

I think that is what I did when I last built all modules for all (at the time) existing Kindle models / Kernel version in use. (It's posted here, somewhere.)
But I did include the build scripting I used to do it.

It is actually easier to use the 'allmodules' makefile target than to pick and choose just a few selected modules.
(Plus, the output of moddep will be complete to support the module auto-loader.)

jscris · 10-05-2016, 01:31 PM

No luck on old pw2, S/N B0D4..., FW 5.6.5. Tried KL this morning, no response. Did install Voice.

knc1 · 10-06-2016, 04:01 AM

Quote:

Originally Posted by lucida

KT3 definitely wouldn't work since it uses a different 3.10.53 kernel even it still features an i.MX6. insmod will fail with current set of usbhid kernel modules(since these were compiled with PW3 kernel source) so we don't even have proper /dev/input entry to begin with.
- - - - - -

A nice little project for anyone that wants it to run under 5.8.2.1 on anything already tested.

aconicq1 · 10-14-2016, 10:50 PM

Quote:

Originally Posted by jscris

No luck on old pw2, S/N B0D4..., FW 5.6.5. Tried KL this morning, no response. Did install Voice.

I also have no luck with PW2 FW 5.8.2.1 S/N 90D4 using the same presenter mentioned.

KUAL gives "ERROR opening evdev2 device : No such file or directory". Same as for evdev3 device.

I would love to get this working and can post some debug information for this device. I don't know what information is needed to figure out the differences though...

Spoiler:

meadows · 10-15-2016, 02:39 AM

Oh wow, I just had to register to say that I'm so glad you've done this. I've been wanting this functionality out the Kindle for more than a year now (I do a lot of reading in bed). I upgraded to PW3 this week, perfect timing!

Just ordered a clicker, excited to try this out.

jscris · 10-15-2016, 11:02 AM

Quote:

Originally Posted by aconicq1

I also have no luck with PW2 FW 5.8.2.1 S/N 90D4 using the same presenter mentioned.

KUAL gives "ERROR opening evdev2 device : No such file or directory". Same as for evdev3 device.

I would love to get this working and can post some debug information for this device. I don't know what information is needed to figure out the differences

Mine locks up, will go to screensaver but then requires a restart. Is VoiceView included in that version of the FW for the pw2?

aconicq1 · 10-16-2016, 07:59 AM

I don't know how to check if VoiceView is included in FW 5.8.2.1 on PW2. But when the device is plugged in then the number of input devices in /dev/input increases.

Here is a main difference I get. Instead of getting event2 and event3 I just get 'mice'.
Now looking further at this there are issues with the ioctl (whatever that is...).
running

Code:

[root@kindle root]# strace evtest /dev/input/mice
.
.
.
open("/dev/input/mice", O_RDONLY)       = 3
ioctl(3, EVIOCGVERSION, 0xbeb98ac0)     = -1 ENOTTY (Inappropriate ioctl for device)
dup(2)                                  = 4
fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
fstat64(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40024000
_llseek(4, 0, 0xbeb98988, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(4, "evtest: can't get version: Inapp"..., 58evtest: can't get version: Inappropriate ioctl for device
) = 58
close(4)                                = 0
munmap(0x40024000, 4096)                = 0
exit_group(1)                           = ?
+++ exited with 1 +++

whereas there is no problem with device1 or device0.

Another difference is that:
/sys/class/input/mice/* are mostly missing compared to the equivalent for device1 etc, and

Code:

[root@kindle root]# ls -las /sys/class/input/
   0 lrwxrwxrwx    1 root     root             0 Oct 16 22:40 mice -> ../../devices/virtual/input/mice

is different being in a folder called virtual...

I'm not sure what any/all this means though... let alone how to fix it.

meadows · 10-16-2016, 04:25 PM

Okay, set this up yesterday on PW3 and it works perfectly.

I did notice one thing though, after I went away from the device for a few hours, I turned it back on again and KL stopped working. It also crashed/froze KUAL, because I could not even launch that to try and restart KL. It took a full reboot of the kindle to fix.

Not sure if this is something that can be addressed in code, like KL shuts itself off when the kindle goes into whatever sleep-mode it has?

badgoodDeb · 10-17-2016, 04:06 PM

I wonder if that is related to the "hot plug isn't in the code yet", meaning that you have to plug in the remote adapter first, THEN start KindleLazy ..... and stop KindleLazy before removing the remote adapter. Allowing the kindle to go to sleep where my dots are in that sentence might be a problem.

Until somebody knowledgable shows up, you might make a point to stop KindleLazy before letting the kindle go to sleep. [You probably don't need the remote device removed, but I guess that could be another experiment. ]

jscris · 10-17-2016, 04:12 PM

Quote:

Originally Posted by badgoodDeb

I wonder if that is related to the "hot plug isn't in the code yet", meaning that you have to plug in the remote adapter first, THEN start KindleLazy ..... and stop KindleLazy before removing the remote adapter. Allowing the kindle to go to sleep where my dots are in that sentence might be a problem.

Until somebody knowledgable shows up, you might make a point to stop KindleLazy before letting the kindle go to sleep. [You probably don't need the remote device removed, but I guess that could be another experiment. ]

My Voyage goes to sleep and wakes up with KL still working over and over. No problem. I do stop KL before removing the adapter to charge the kindle, but other than that, I just leave the adapter plugged in and KL on.

knc1 · 10-17-2016, 04:22 PM

Quote:

Originally Posted by jscris

My Voyage goes to sleep and wakes up with KL still working over and over. No problem. I do stop KL before removing the adapter to charge the kindle, but other than that, I just leave the adapter plugged in and KL on.

How are you sure your KV is going to sleep?

The Kindles can show the screensaver and turn off the front light without going to sleep.

If you don't have a serial port connection (that does not effect its going to sleep behavior), I guess you could dump the messages log as soon as it (appears) to wake up.
Look for something like "coming out of sleep", messages, "resume completed in ...". at the very end of the log as dumped.
All of the messages are date/time stamp'd be sure you are looking at the right time relative to when you did your test.

Be sure you leave it showing the screen saver long enough for it to complete any work in its job queue - Kindles normally catch up with their 'to do' list just before actually suspending operation.

jscris · 10-17-2016, 06:21 PM

Quote:

Originally Posted by knc1

How are you sure your KV is going to sleep?

The Kindles can show the screensaver and turn off the front light without going to sleep.

If you don't have a serial port connection (that does not effect its going to sleep behavior), I guess you could dump the messages log as soon as it (appears) to wake up.
Look for something like "coming out of sleep", messages, "resume completed in ...". at the very end of the log as dumped.
All of the messages are date/time stamp'd be sure you are looking at the right time relative to when you did your test.

Be sure you leave it showing the screen saver long enough for it to complete any work in its job queue - Kindles normally catch up with their 'to do' list just before actually suspending operation.

Left it about five minutes on screensaver. Hope this is what you need. KL was still active.

161017:170527 wifid[2716]: I ipchandler

ev=resuming:
161017:170527 wifid[2716]: I sysev:dispatch:code=Wakeup:
161017:170527 wifid[2716]: I sysev

ower:action=wakeup, state=Off, persist=0

rocessing Wakeup
161017:170527 wifid[2716]: I wmgr:handleCtrlEvent:ev=Wakeup, state=Powered down:
161017:170527 wifid[2716]: I wmgr:doStatePwrDown:Wireless=Off:not loading WiFi driver
161017:170527 wifid[2716]: I ipchandler:set_property

rop=enable:
161017:170527 wifid[2716]: I sysev:dispatch:code=Suspend:
161017:170527 wifid[2716]: I sysev

ower:action=suspend, state=WakingUp, persist=1

rocessing Suspend
161017:170527 wifid[2716]: I lipc:evts:name=cmDisconnected, origin=com.lab126.wifid:Event sent
161017:170527 wifid[2716]: I netm:event:handleCtrlEvent (Reset) connectionNumber=33 state=[down]:
161017:170527 cmd[2639]: I def

rocess_system_resume::Wireless Enabled Flag=0
161017:170527 cmd[2639]: I def

isable All Wireless Interfaces::
161017:170527 cmd[2639]: I def:tcpreset_proc_entry:tcpreset= /proc/tcpreset:Resetting TCP sockets
161017:170527 cmd[2639]: I def:tcpreset_details::resetparam=43, skiplist=22,5900:TCP Reset details:~:
161017:170527 cmd[2639]: I lipc:evts:name=wirelessEnableChanged, origin=com.lab126.cmd, fparam=0:Event sent
161017:170528 wifid[2716]: I sysev:dispatch:code=SuspendPhase2:
161017:170528 wifid[2716]: I wmgr:handleCtrlEvent:ev=WirelessOff, state=Powered down:
161017:170528 wifid[2716]: I fconf:saving:file=/var/local/system/wifid.conf, nsect=2:
161017:170528 wifid[2716]: W wif_u:start-stop supplicant::Supplicant is not running
161017:170528 wifid[2716]: I sysev:dispatch:code=IF not available:
161017:170528 wifid[2716]: I lipc:evts:name=cmIntfNotAvailable, origin=com.lab126.wifid:Event sent

knc1 · 10-17-2016, 06:26 PM

I only see 2/10 of a second of log, not "about 5 minutes".

jscris · 10-17-2016, 06:34 PM

Quote:

Originally Posted by knc1

I only see 2/10 of a second of log, not "about 5 minutes".

Sorry. Maybe someone who knows better how to read the log files should do this. I can't be the only one using KL.

10-16-2016, 07:59 AM	#128
aconicq1 Member Posts: 13 Karma: 29938 Join Date: Feb 2014 Device: pw2	I don't know how to check if VoiceView is included in FW 5.8.2.1 on PW2. But when the device is plugged in then the number of input devices in /dev/input increases. Here is a main difference I get. Instead of getting event2 and event3 I just get 'mice'. Now looking further at this there are issues with the ioctl (whatever that is...). running Code: [root@kindle root]# strace evtest /dev/input/mice . . . open("/dev/input/mice", O_RDONLY) = 3 ioctl(3, EVIOCGVERSION, 0xbeb98ac0) = -1 ENOTTY (Inappropriate ioctl for device) dup(2) = 4 fcntl64(4, F_GETFL) = 0x2 (flags O_RDWR) fstat64(4, {st_mode=S_IFCHR\|0620, st_rdev=makedev(136, 0), ...}) = 0 mmap2(NULL, 4096, PROT_READ\|PROT_WRITE, MAP_PRIVATE\|MAP_ANONYMOUS, -1, 0) = 0x40024000 _llseek(4, 0, 0xbeb98988, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(4, "evtest: can't get version: Inapp"..., 58evtest: can't get version: Inappropriate ioctl for device ) = 58 close(4) = 0 munmap(0x40024000, 4096) = 0 exit_group(1) = ? +++ exited with 1 +++ whereas there is no problem with device1 or device0. Another difference is that: /sys/class/input/mice/* are mostly missing compared to the equivalent for device1 etc, and Code: [root@kindle root]# ls -las /sys/class/input/ 0 lrwxrwxrwx 1 root root 0 Oct 16 22:40 mice -> ../../devices/virtual/input/mice is different being in a folder called virtual... I'm not sure what any/all this means though... let alone how to fix it. Last edited by aconicq1; 10-16-2016 at 08:01 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Aura HD Brightness control too bright	cefarix	Kobo Reader	7	05-04-2014 02:28 PM
Advanced Automatic Brightness and Wifi Control	hieronymos	Kobo Tablets	2	12-02-2011 09:51 AM
hardware backlight control for brightness?	bells	Apple Devices	3	10-26-2011 11:39 AM
remote control?	shawn	Sony Reader	2	10-10-2007 12:02 PM
Remote Control	ecm	Which one should I buy?	5	03-20-2007 12:08 AM

10-05-2016, 01:31 PM	#123
jscris Addict Posts: 393 Karma: 123456 Join Date: Feb 2009 Location: Central US Device: k1 - KAO2, ipads, h2o, KA1, inkBOOK, T80s, Mars, Nova Pro	No luck on old pw2, S/N B0D4..., FW 5.6.5. Tried KL this morning, no response. Did install Voice.

10-15-2016, 02:39 AM	#126
meadows Junior Member Posts: 3 Karma: 10 Join Date: Oct 2016 Device: Kindle Paperwhite	Oh wow, I just had to register to say that I'm so glad you've done this. I've been wanting this functionality out the Kindle for more than a year now (I do a lot of reading in bed). I upgraded to PW3 this week, perfect timing! Just ordered a clicker, excited to try this out.

10-16-2016, 04:25 PM	#129
meadows Junior Member Posts: 3 Karma: 10 Join Date: Oct 2016 Device: Kindle Paperwhite	Okay, set this up yesterday on PW3 and it works perfectly. I did notice one thing though, after I went away from the device for a few hours, I turned it back on again and KL stopped working. It also crashed/froze KUAL, because I could not even launch that to try and restart KL. It took a full reboot of the kindle to fix. Not sure if this is something that can be addressed in code, like KL shuts itself off when the kindle goes into whatever sleep-mode it has?

10-17-2016, 04:06 PM	#130
badgoodDeb Grand Sorcerer Posts: 8,502 Karma: 64095689 Join Date: Jan 2008 Location: Harrisburg outskirts Device: Palms, K1-4s, iPads, iPhones, KV, KO1	I wonder if that is related to the "hot plug isn't in the code yet", meaning that you have to plug in the remote adapter first, THEN start KindleLazy ..... and stop KindleLazy before removing the remote adapter. Allowing the kindle to go to sleep where my dots are in that sentence might be a problem. Until somebody knowledgable shows up, you might make a point to stop KindleLazy before letting the kindle go to sleep. [You probably don't need the remote device removed, but I guess that could be another experiment. ]

10-17-2016, 06:26 PM	#134
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	I only see 2/10 of a second of log, not "about 5 minutes".

Advert

Advert