MobileRead Forums - View Single Post

frostschutz · 07-25-2019, 06:53 AM

Code:

[1564048341 REP:DELAY 400]
[1564048341 REP:MAX 80]
[1564048341 MSC:RAW 24]
[1564048341 SYN:REPORT 0]
[1564048341 MSC:RAW 28]
[1564048341 SYN:REPORT 0]

These events are new to me (also REP:MAX should be REP:PERIOD... the woes of parsing input-event-codes.h in reverse :-) ). I don't see anything the like on my H2O. They didn't trigger cooldown for you in this instance but it came close (event occured 2 times in a row when 3 times by default triggers the cooldown).

Code:

-- whitelist match -- 
-- cfg_delay = '1 1 1' --
-- clock update Thu Jul 25 10:54:36 BST 2019 --
-- clock update Thu Jul 25 10:54:37 BST 2019 --
-- clock update Thu Jul 25 10:56:11 BST 2019 --

There should be 1 second delay between these but it turned out as almost 2 minutes. Issue repeates at 10:59 and 11:06.

This is probably a case of nickel putting background process in the freezer.

EDIT: You could try and see if it improves by setting delay=1 or delay=2 onstead of 1 1 1. but delay=1 will miss update time if the pageturn (or other screen refresh action) is slower than 1 second. pageflips on H2O can be quite slow hence I used 1 1 1 but maybe Forma has faster pageflip so delay=1 will work. :EDIT

With the current code I guess it is possible to miss the first event after wakeup... as during those 2 minutes, the update was still in progress and no new events were listened to. Most likely the 10:56:11 update then happened straight on wakeup, to be erased by the pageflip that follows.

07-25-2019, 06:53 AM	#248
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	Code: [1564048341 REP:DELAY 400] [1564048341 REP:MAX 80] [1564048341 MSC:RAW 24] [1564048341 SYN:REPORT 0] [1564048341 MSC:RAW 28] [1564048341 SYN:REPORT 0] These events are new to me (also REP:MAX should be REP:PERIOD... the woes of parsing input-event-codes.h in reverse :-) ). I don't see anything the like on my H2O. They didn't trigger cooldown for you in this instance but it came close (event occured 2 times in a row when 3 times by default triggers the cooldown). Code: -- whitelist match -- -- cfg_delay = '1 1 1' -- -- clock update Thu Jul 25 10:54:36 BST 2019 -- -- clock update Thu Jul 25 10:54:37 BST 2019 -- -- clock update Thu Jul 25 10:56:11 BST 2019 -- There should be 1 second delay between these but it turned out as almost 2 minutes. Issue repeates at 10:59 and 11:06. This is probably a case of nickel putting background process in the freezer. EDIT: You could try and see if it improves by setting delay=1 or delay=2 onstead of 1 1 1. but delay=1 will miss update time if the pageturn (or other screen refresh action) is slower than 1 second. pageflips on H2O can be quite slow hence I used 1 1 1 but maybe Forma has faster pageflip so delay=1 will work. :EDIT With the current code I guess it is possible to miss the first event after wakeup... as during those 2 minutes, the update was still in progress and no new events were listened to. Most likely the 10:56:11 update then happened straight on wakeup, to be erased by the pageflip that follows. Last edited by frostschutz; 07-25-2019 at 07:12 AM.