In case the subject comes up again, just a few possibly helpful quotes...
Quote:
The debug services also enables a telnet service. This tends to block the WiFi from turning off and the device from automatically sleeping. And that runs the battery down a lot faster.
|
https://www.mobileread.com/forums/sh...1&postcount=27
Quote:
(You can't suspend (any?) NTX boards with Wi-Fi on (or even just *powered* on): it hangs the kernel, either right away, or on resume/next wifi bringup).
|
https://www.mobileread.com/forums/sh...2&postcount=88
Quote:
For the Qt resources, I don't bother getting them myself. In the kobo-patches repository, geek1011 extracts them on every firmware issue. Just find the issue for the latest firmware and look for the comment that includes them.
|
https://www.mobileread.com/forums/sh...4&postcount=34
Quote:
It doesn't help that the branches aren't ABI-compatible, that some are qt6, and that I don't have any devices capable of testing anything other than 4.38.x (which means I either have to do everything statically, or I have to put in the time and effort to backport or emulate the newer branches -- which is possible, but yet another hurdle to overcome before I can get to the fun stuff).
|
https://www.mobileread.com/forums/sh...85&postcount=8
Quote:
Actually, the /mnt/onboard mount
happens only after udev is started, so it's entirely possible it won't be mounted yet...
So if you execute a script on /mnt/onboard/ there might be a possibility it won't run.
|
https://www.mobileread.com/forums/sh...88&postcount=8
Quote:
The difference between restarting only Nickel and restarting the whole device does seem to be up to about 8 seconds btw, so clearly I was wrong about it not making that
much difference (and/or it differs per device).
|
https://www.mobileread.com/forums/sh...postcount=1196