You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
# General
|
|
|
|
|
|
Various Wi-Fi QoL improvements (#6424)
* Revamped most actions that require an internet connection to a new/fixed backend that allows forwarding the initial action and running it automatically once connected. (i.e., it'll allow you to set "Action when Wi-Fi is off" to "turn_on", and whatch stuff connect and do what you wanted automatically without having to re-click anywhere instead of showing you a Wi-Fi prompt and then not doing anything without any other feedback).
* Speaking of, fixed the "turn_on" beforeWifi action to, well, actually work. It's no longer marked as experimental.
* Consistently use "Wi-Fi" everywhere.
* On Kobo/Cervantes/Sony, implemented a "Kill Wi-Fi connection when inactive" system that will automatically disconnect from Wi-Fi after sustained *network* inactivity (i.e., you can keep reading, it'll eventually turn off on its own). This should be smart and flexible enough not to murder Wi-Fi while you need it, while still not keeping it uselessly on and murdering your battery.
(i.e., enable that + turn Wi-Fi on when off and enjoy never having to bother about Wi-Fi ever again).
* Made sending `NetworkConnected` / `NetworkDisconnected` events consistent (they were only being sent... sometimes, which made relying on 'em somewhat problematic).
* restoreWifiAsync is now only run when really needed (i.e., we no longer stomp on an existing working connection just for the hell of it).
* We no longer attempt to kill a bogus non-existent Wi-Fi connection when going to suspend, we only do it when it's actually needed.
* Every method of enabling Wi-Fi will now properly tear down Wi-Fi on failure, instead of leaving it in an undefined state.
* Fixed an issue in the fancy crash screen on Kobo/reMarkable that could sometime lead to the log excerpt being missing.
* Worked-around a number of sneaky issues related to low-level Wi-Fi/DHCP/DNS handling on Kobo (see the lengthy comments [below](https://github.com/koreader/koreader/pull/6424#issuecomment-663881059) for details). Fix #6421
Incidentally, this should also fix the inconsistencies experienced re: Wi-Fi behavior in Nickel when toggling between KOReader and Nickel (use NM/KFMon, and run a current FW for best results).
* For developers, this involves various cleanups around NetworkMgr and NetworkListener. Documentation is in-line, above the concerned functions.
4 years ago
|
|
|
When connected to Wi-Fi you can find the IP address and root password for your
|
|
|
|
|
reMarkable in Settings -> About, then scroll down the GPLv3 compliance on the
|
|
|
|
|
right (finger drag scroll, not the page forward/back buttons). This should also
|
|
|
|
|
work for the USB network you get if you connect the reMarkable to your computer
|
|
|
|
|
with a USB cable.
|
|
|
|
|
|
|
|
|
|
# Install
|
|
|
|
|
|
|
|
|
|
scp <koreader-package>.zip root@<your-remarkable>:
|
|
|
|
|
|
|
|
|
|
ssh root@<your-remarkable>
|
|
|
|
|
|
|
|
|
|
unzip <koreader-package>.zip
|
|
|
|
|
|
|
|
|
|
# Launching using the included launcher
|
|
|
|
|
|
|
|
|
|
KOReader includes a very simple launcher called `button-listen` which starts
|
|
|
|
|
KOReader when the middle button is held down for 3 or more seconds in the
|
|
|
|
|
default UI (xochitl).
|
|
|
|
|
|
|
|
|
|
cp -v koreader/*.service /etc/systemd/system/
|
|
|
|
|
systemctl enable --now button-listen
|
|
|
|
|
|
|
|
|
|
To return to the default UI just exit KOReader (swipe down from the top of the
|
|
|
|
|
screen, select icon in the top right, Exit, Exit).
|
|
|
|
|
|
|
|
|
|
Some reMarkable software updates will wipe the new systemd units so you will have
|
|
|
|
|
to run the two install steps again when that happens.
|
|
|
|
|
|
|
|
|
|
# Using a different launcher
|
|
|
|
|
|
|
|
|
|
The command that the launcher needs to run is:
|
|
|
|
|
|
|
|
|
|
/home/root/koreader/koreader.sh
|
|
|
|
|
|
|
|
|
|
Alternatively, if you want the default behaviour of KOReader exit starting the
|
|
|
|
|
default UI you can run (once on installation):
|
|
|
|
|
|
|
|
|
|
cp -v koreader/koreader.service /etc/systemd/system/
|
|
|
|
|
|
|
|
|
|
Then to start KOReader the launcher needs to run:
|
|
|
|
|
|
|
|
|
|
systemctl start koreader
|
