Autostarting KOReader on device startup

[wujekbogdan]

Hey,

I've just modded my Kindle 7th gen with WinterBreak and installed KOReader. Now, I'd like to start it on device boot to replace the default Kindle UI with KOReader.

It seems I have to place a startup script in /etc/upstart, but I don't know the exact script syntax or how to choose the right KOReader mode - I want KOReader to start in no framework mode.

[Ebookus]

You can’t

[wujekbogdan]

I can't start KOReader specifically, or I can't auto-start any script upon boot?

[mergen3107]

Don’t mess with upstart at all, you can brick Kindle.

There is no way to autostart KOReader on start, for a good reason

[wujekbogdan]

> Don’t mess with upstart at all, you can brick Kindle.

I'm not asking for advice; I'm asking if it's possible or not.

> There is no way to autostart KOReader on start, for a good reason

Is there no way to autostart KOReader specifically, or is it impossible to autostart anything?

[mergen3107]

You be you, just warning you right now so don’t bakc sith another post “Guys I bricked my Kindle”

It is both - it is hard to add anything (safely) to upstart on Kindle.

On KOReader side, if say KOReader crashes on startup, and it is part of upstart, the upstart will not be happy and send you to a restart. That means it will be in a loop, so that’s probably why I haven’t seen it done yet

[mergen3107]

What’s the main reason you would like to have KOReader start on boot anyway?

There are at least four ways that I know to start KOReader:
KUAL
KOL
WinterBreak’s scriplet
By hand (via ssh/telnet)

[wujekbogdan]

Don't be a gatekeeper. Every guide on modding a Kindle starts with warnings about the risk of bricking the device. We're adults - I get it, I've been warned. If I brick it, then ¯_(ツ)_/¯ - it's not the end of the world.

> On KOReader side, if say KOReader crashes on startup, and it is part of upstart, the upstart will not be happy and send you to a restart. That means it will be in a loop, so that’s probably why I haven’t seen it done yet

If I do the following:
- Place the true startup script in userland - in a directory accessible via USB.
- Place a script that simply triggers that userland script in /etc/upstart.

Then a boot loop isn't that risky. If it happens, I can replace the userland script with a dummy bash echo script, and I'll escape the boot loop.

> What’s the main reason you would like to have KOReader start on boot anyway?

What's the reason people who mod consoles want the modded dashboard to start without any additional interaction? What's the reason people set up useless screensavers or other irrelevant modding stuff?

One reason is improving UX; another reason is pure curiosity or "just because." I believe many people in the modding scene do things just for the sake of doing them - just to prove that something perceived as undoable is actually doable.

[pazos]

It isn't a matter of gatekeeping. It is a matter of telling you it isn't a very good idea even to try. Also, the way you're expecting to recover from a bootloop suggest you have no proper knowledge about how embedded linux work and you picked the worst platform to learn.

If you really want to try then yes: Do your own research. If you need to ask some questions do it on the proper subforum (kindle development)

Here nobody knows and the people offering support on the program doesn't really want to know.

But if you want to know, please do. Be our guest. Hopefully you're able to get some outcome. We just warned you about the more likely outcome you'll get.

[Frenzie]

I don't know if old methods like https://www.mobileread.com/forums/sh...d.php?t=221019 are still applicable. Take special note of https://www.mobileread.com/forums/sh...8&postcount=14