View Single Post
Old 02-12-2024, 10:03 PM   #2
elinkser
Groupie
elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.
 
Posts: 186
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
***
So cool to have a community toolkit (in addition to KOReader's) like rmkit running on all these quirky devices via FBInk...


I tried the new binary KoboRoot.tgz package from https://build.rmkit.dev/fbink/latest/kobo/ and it ran without a problem on my Clara HD.


People who need to debug can still invoke it from an SSH shell to the Kobo as:
# RMKIT_KOBO_ANY=1 sh /opt/bin/remux.sh


A couple of notes:

1. Rmkit is not guaranteed to start at boot.
Since rmkit is started by /etc/udev/rules.d/99-rmkit.rules, which "runs early at boot", and "onboard *might*" (i.e. *might not*) be mounted at that point - as per the comments - that means rmkit is not guaranteed to start every boot.
So we take the command from 99-rmkit.rules, and wrap it in a nice NickelMenu item, so we can start it manually:
Code:
menu_item :main    :rmkit              :cmd_spawn          :quiet :/usr/local/rmkit/startup.sh
    chain_success                      :dbg_toast          :Started rmkit
    chain_failure                      :dbg_toast          :Error starting rmkit
And another nice NickelMenu item to check if rmkit is running, before we wear out the right margin trying to swipe the rmkit launcher into life:
Code:
menu_item :main    :rmkit status       :cmd_output         :500:ps | grep remux
2. Rmkit install creates /opt folder as symbolic link to /mnt/onboard/.adds/rmkit, which may interfere with other app installation, or even abort rmkit installation if /opt already exists.
As a possible workaround, you can delete the /opt symbolic link to /mnt/onboard/.adds/rmkit:
(*Note WITHOUT the trailing slash, i.e. /opt NOT /opt/)
# rm /opt
Second, recreate /opt as a normal folder:
# mkdir /opt
Then recreate symbolic links for rmkit subfolders:
# ln -s /mnt/onboard/.adds/rmkit/bin/ /opt/bin
# ln -s /mnt/onboard/.adds/rmkit/data/ /opt/data
# ln -s /mnt/onboard/.adds/rmkit/etc/ /opt/etc
# cp /mnt/onboard/.adds/rmkit/enable_remux /opt/
Now, check everything is still there:
# ls /opt/
bin data enable_remux etc
# ls /opt/bin/
apps/ remux.sh


3. To use dithering_demo, you need to put colorspace.png, gradient.png, and palette.png (get them from the source package) in the /mnt/onboard/.adds/rmkit/etc/dithering_demo/ folder.


4. To try menu.sh (a simple application script from the source package), you need to put both menu.sh and simple in the /mnt/onboard/.adds/rmkit/bin/apps/ folder.


5. If you're artistic, you can draw cool scenes with Harmony tools:
https://rmkit.dev/apps/harmony
If you're not artistic, you can trace cool scenes from your cellphone camera photos with Harmony layers:
https://www.mobileread.com/forums/sh...62&postcount=8


6. Like puzzles?
https://github.com/mrichards42/remarkable_puzzles


7. The entire rmkit (including apps) builds in 6-7 minutes on my low-end Acer chromebook (converted to MXLinux).
Now try Qt (lol).
Me I probably won't be venturing too much into C++ because of stuff like:
https://blog.tartanllama.xyz/initialization-is-bonkers/ ,
but Harmony alone already makes this port worthwhile to me.


***

Last edited by elinkser; 03-13-2024 at 06:12 PM. Reason: remove old puzzle link,KOReader toolkit
elinkser is offline   Reply With Quote