FBInk: A small tool/library to print crap on your screen!

[readern4vi]

Originally Posted by NiLuJe

@readern4vi: Like the poster above, you'll need to grab a current snapshot from a GitHub Action to get a binary that supports your device.

So do I need to compile the program again? Or just edit one of the files in the KoboRoot.tgz file?

I am not really sure how the github actions thing works.

[PeterT]

Originally Posted by readern4vi

So do I need to compile the program again? Or just edit one of the files in the KoboRoot.tgz file?

I am not really sure how the github actions thing works.

OK. When I go to https://github.com/NiLuJe/FBInk one of the links is to Actions https://github.com/NiLuJe/FBInk/actions

Select the Action "Simplify that again" build #31 https://github.com/NiLuJe/FBInk/acti...ns/11161992771 and under "Artifacts" you'll see FBInk size 585 KB https://github.com/NiLuJe/FBInk/acti...cts/2010744175. Download that.

[readern4vi]

Originally Posted by PeterT

OK. When I go to https://github.com/NiLuJe/FBInk one of the links is to Actions https://github.com/NiLuJe/FBInk/actions

Select the Action "Simplify that again" build #31 https://github.com/NiLuJe/FBInk/acti...ns/11161992771 and under "Artifacts" you'll see FBInk size 585 KB https://github.com/NiLuJe/FBInk/acti...cts/2010744175. Download that.

Thank you. I created a github account and managed to download the FBInk file.

How do I install it on my kobo? Do I create a new zip file with the files named KoboRoot.tgz? or should I replace the files on the previous release with the ones in the new download?

[PeterT]

Normally one just copies the KoboRoot.tgz to the .kobo directory on the device and do a disconnect. the device will detect the file, install it and reboot.

Sent from my Pixel 7a using Tapatalk

[mergen3107]

@readern4vi
In that archive, all you need is a new fbink file (a binary).

Find, where such file is located in your Kobo (I presume it is in .adds/ folder somewhere?)

Make a backup of it (rename it) just in case.
Then put this new fbink in its place.

Script that require fbink will hopefully pick up the new binary when you launch them next time

[readern4vi]

@mergen3107 @PeterT

I couldn't find the FBink file on my kobo to replace (even after running a search for it) so instead I took the latest KoboRoot.tgz release and swapped out the files that matched, including FBink. After installing on my Libra Colour, the QR code works perfectly!

Thank you all for your help

[DNSB]

Originally Posted by readern4vi

@mergen3107 @PeterT

I couldn't find the FBink file on my kobo to replace (even after running a search for it) so instead I took the latest KoboRoot.tgz release and swapped out the files that matched, including FBink. After installing on my Libra Colour, the QR code works perfectly!

Thank you all for your help

Considering that when you look at FBInk-v1.25.0.zip and dig into the innards, (I used 7-Zip), you end up at usr which is on one of the Linux ext4 partitions with fbink and button_scan symlinks being copied into /usr/bin and the actual files being copied into /usr/local/fbink and several subdirectories of /usr/local/fbink, it's not a surprise that a search found nothing.

You can see them by telnet or SSH to your Kobo.

[enthdegree]

For a VT port I'm including FBInk exclusively to call screen refresh. A few questions:

• Are some refresh calls significantly more power-hungry than others? Right now I'm updating the screen by putting a flag up. Another thread loops "sleep, then if the flag is up do a FBink full screen refresh." Settings struct is full of zeros. I'm worried this is expensive.
• Are there examples of including this library in a project? My current approach includes a whole standalone copy of FBink in the program's local environment.
• Maybe not the place but not sure where else to ask... is there a common packaging example to adapt from? The VT needs a wrapper to manage exit + keep the stock UI from sleeping, overwriting the framebuffer, etc.

Thanks!

[NiLuJe]

@enthdegree:

1. It depends ;o). But generally, no, you don't want to refresh in full. (The issue isn't going to be power so much as performance, though). The waveform mode enum has a lot of info about dos and don'ts in fbink.h if you want more context.

2. a submodule and a static link? c.f., InkVT as a potential example (or, well, KFMon, would perhaps be easier to follow).

3. I would punt that off to the user, unless you like maintaining horrible-to-maintain stuff. In which case, something based on KOReader's startup script.

[jagaliano]

The fbink link for Libra Colour in GitHub Action has expired. Could you please provide a new one? Please note that am not programmer and I do not know how to use GitHub.

Thank you.