Clara HD Display time when reading

[NiLuJe]

That should indeed be the right keycodes for the Forma .

Non multitouch devices will NOT emit ABS:MT_POSITION_X, although, AFAIK, everything should emit KEY:BTN_TOUCH .

EDIT: ... at least for actual touch events. No idea for swipes. In which case, the obvious non-mt equivalent to ABS:MT_POSITION_X is ABS:ABS_X

[desterly]

Does "devinputeventdump" ignore the SYN reports or it returning multiple events on it's read?

The check_event() looks like it's could receive multiple events...

Just curious before I drop it on tonight to test.

[frostschutz]

you can see what it returns if you set debug=1

after some trial and error with dd and hexdump - it worked yet didn't. short reads missing the event we were interested in, delay due to unwanted pipe buffereing or waiting for additional block when read wasn't short, and added to that the general cumbersomeness of doing this for more than one device in parallel, etc. etc.

I caved in and wrote a little C helper to just poll across devices and just dump whatever events there are. The interpretation of those still happens on the shell side

A few things fell under the bus while doing so (whoops, touchscreen= button= update= is currently uneffective) I'll re-implement those later.

Right now it's experimental and the main question is, does it drain the battery or not, and does it work otherwise too.

[poczynek]

Perfect thank you @frostschutz - have installed and buttons work. Will now watch and confirm battery.

EDIT:

Two hours later and so far so good. Buttons work and no battery drain!

[frostschutz]

Originally Posted by poczynek

EDIT:

Two hours later and so far so good. Buttons work and no battery drain!

I'm glad to hear it

[poczynek]

Originally Posted by frostschutz

I'm glad to hear it

Well no battery drain but read for an hour and it didn't come up with using buttons unfortunately.

Sent from my SM-G970F using Tapatalk

[frostschutz]

touchscreen still works?

anything appear if you set debug=1 in config file as well as add {debug} to the date format?

it could be in permanent cooldown mode but that should require one input device to be permanent ballistic

if there's nothing even with debug, it might have quit entirely ... is it back after reboot?

on my two H2O's everything is normal after a night of standby... also reacts to (power) button... don't have a Forma to test other device conditions myself, unfortunately

[poczynek]

Originally Posted by frostschutz

touchscreen still works?

anything appear if you set debug=1 in config file as well as add {debug} to the date format?

it could be in permanent cooldown mode but that should require one input device to be permanent ballistic

if there's nothing even with debug, it might have quit entirely ... is it back after reboot?

on my two H2O's everything is normal after a night of standby... also reacts to (power) button... don't have a Forma to test other device conditions myself, unfortunately

No touch screen didn't work either.

Yep will try the debug.

Sent from my SM-G970F using Tapatalk

[jackie_w]

@frostschutz,

A second set of test observations. I've just installed the July 23 version on my Forma in the last few minutes. Here are my Forma's current config settings.

Spoiler:

# -------------------------------------------------------------------
#   MiniClock config example file. For settings to take any effect,
#     copy or rename this file to .addons/miniclock/miniclock.cfg.
# -------------------------------------------------------------------

#
# To uninstall, set to 1
#
uninstall=0

#
# To debug, set to 1 (will print event parser)
#
debug=0

# listen to touchscreen events
# listen to button events (will patch nickel, only active after reboot)
# if you set both to 0, MiniClock will still show as per update frequency
#
touchscreen=0
button=1

#
# whitelist of accepted events that should update miniclock
# ABS:MT_POSITION_X/Y: touchscreen coordinates
# KEY:F23/F24: forma forward backward buttons (to be confirmed)
# KEY:POWER: going into standby manually
#
whitelist=ABS:MT_POSITION_X ABS:MT_POSITION_Y KEY:F23 KEY:F24 KEY:POWER

#
# cooldown num time
#
# after receiving num unrecognized events in a row,
# stop listening to all input for <time> seconds.
# (helps avoid power consumption during standby)
# 
cooldown=3 30

#
# Update frequency: (update once every 60 seconds)
#
update=60

#
# Delay: (update delay 1 second repeat 3 times)
#
delay=1 1 1

#
# Date format string ( see 'man strftime' )
#
# In addition may also use {month}, {day}, {battery}.
# (Look for battery and locale settings further below).
#
# {debug} will show the reason for miniclock update and uptime
#  one of (touch)screen, (butt)on, or update (freq)uency event
#
format=%H:%M [{battery}]

#
# Where to print the clock
#
offset_x=25
offset_y=1860

#
# Font:  (IBM, UNSCII, ALT, THIN, FANTASY, MCR, TALL, BLOCK,
#         LEGGIE, VEGGIE, KATES, FKP, CTRLD, ORP, ORPB, ORPI,
#         SCIENTIFICA, SCIENTIFICAB, SCIENTIFICAI)
#
font=SCIENTIFICAB

#
# Font Size:
#
size=3

#
# Color: (BLACK GRAY{1-9A-E} WHITE)
#
fg_color=GRAY4
bg_color=WHITE

#
# TrueType support:
#
# For fonts inside the MiniClock directory:
#     truetype=yourfont.ttf
#
# For fonts stored elsewhere in the filesystem:
#     truetype=/mnt/onboard/fonts/something.ttf

#
# Only set these if you use *italic*, **bold**, ***bold italic*** in your format string:
#
#     truetype_format=*%a* **%b** ***%d*** %H:%M
#     truetype_bold=yourfont-bold.ttf
#     truetype_italic=yourfont-italic.ttf
#     truetype_bolditalic=yourfont-bolditalic.ttf
#
# Technically, this can also be used for completely different font styles,
# instead of italic or bold variants of the same font.
#
# NOTE: Will fall back to regular mode when font file is unavailable.
#       (e.g. while the device is connected to USB)
#
#truetype=Avenir.ttf
truetype=/mnt/onboard/fonts/Trebuchet.ttf
truetype_size=8
#truetype_x=1330
truetype_x=1250
truetype_y=1878

#
# TrueType Padding helps prevent visual fragments to appear
# at the cost of adding extra whitespace. Set to 0 to disable.
#
truetype_padding=1

#
# NightMode support:
#
nightmode_file=/mnt/onboard/.kobo/Kobo/Kobo eReader.conf
nightmode_key=InvertScreen
nightmode_value=true

#
# Battery percentage value (0-100%)
#
# Use {battery} in the format string.
#
# Will only be used if the battery is between min max.
# Default: only shown when battery level drops to 50% and under.
battery_min=0
battery_max=100
battery_source=/sys/devices/platform/pmic_battery.1/power_supply/mc13892_bat/capacity

• At first glance the buttons seem to be working OK for me. What did surprise me was that touching the screen often (but not always) also brings up the time/battery display despite me having settings as
  

  touchscreen=0
  button=1

• A small cosmetic bug with the {battery} display. There is a double % character. My format setting is
  

  format=%H:%M [{battery}]

  but the current display is
  

  11:35 [94%%]

I'll test the battery drain once I've recharged the Forma back to 100%.

ETA follow-up:
I read normally for a little while. Turning the page via button works often, but not always. I haven't spotted a pattern of when it does/doesn't work.

There was no excessive battery drain whilst reading. I'm about to put it in standby mode for a few hours, using a sleepcover. I'll add more when I wake it up again.

[desterly]

Originally Posted by jackie_w

@frostschutz,

A second set of test observations. I've just installed the July 23 version on my Forma in the last few minutes. Here are my Forma's current config settings.

Spoiler:

whitelist=ABS:MT_POSITION_X ABS:MT_POSITION_Y KEY:F23 KEY:F24 KEY:POWER

[LIST][*]At first glance the buttons seem to be working OK for me. What did surprise me was that touching the screen often (but not always) also brings up the time/battery display despite me having settings as

touchscreen=0
button=1

the touchscreen=0/button=1 was removed in this latest round.

If you want just buttons only try changing your config so it shows this:
whitelist=KEY:F23 KEY:F24

[jackie_w]

Originally Posted by desterly

the touchscreen=0/button=1 was removed in this latest round.

Ah, OK. Those settings are still present in the miniclock.example.cfg file so I assumed I still had to set them.

Originally Posted by desterly

If you want just buttons only try changing your config so it shows this:
whitelist=KEY:F23 KEY:F24

Thanks. I'll try this plus I'll comment out the above touchscreen/button lines.

[desterly]

I half wonder if it wouldn't be better to hook into libnickel and update ReadingFooter or TextHeader and inject the clock into the formatted footer/header...

Granted there'd be more upkeep for different firmware versions but it wouldn't need to rely on external methods.. I'd think it resolve any potential batter drain as well.

The things I think about while data processes on my machine at work during the day.

[MGlitch]

Originally Posted by desterly

I half wonder if it wouldn't be better to hook into libnickel and update ReadingFooter or TextHeader and inject the clock into the formatted footer/header...

Granted there'd be more upkeep for different firmware versions but it wouldn't need to rely on external methods.. I'd think it resolve any potential batter drain as well.

The things I think about while data processes on my machine at work during the day.

Except lots of people hide the header and footer. Unless this could be displayed regardless. I imagine that this would also limit where you could position the clock

[poczynek]

Just to clarify my testing yesterday:

8am - installed experimental version. Quick test and buttons worked showing date/time.
10am - quick check and no battery drain and tested a few times with buttons and worked
4pm to 5pm - the first time where i actually read a book since this version. Still no battery drain but more often than not pressing the buttons would not give me the date/time. Maybe around 1 in 15 pages it would come up.

[frostschutz]

Originally Posted by desterly

I half wonder if it wouldn't be better to hook into libnickel and update ReadingFooter or TextHeader and inject the clock into the formatted footer/header...

feel free to do so... for an example you could have a blink at the old nightmode hack, which hooked into screen updates to set inverted flag (I think). so in a similar fashion you might be able to hook into it to piggy back clock updates to nickels regular screen updates.

I don't want to make this kind of mod, myself.

Not really sure what is going on with the Forma, any chance any of you could enable debug=1 for a while? (guess I should have made that a debug log textfile instead of on-screen display... I might do that in the next version.)

Need more info or it's a blindfold guessing game