Kobo files monitor

[Ken Maltby]

Originally Posted by Markismus

Don't make the file in windows! You would get the wrong end-of-line codes.

Content reboot.sh:
#!/bin/sh
reboot

I've attached the file.

Or you could use "Notepad++" with it set for Linux file output.

Or, since these are very small files any HexEditor can be used to remove the "0B" hex (the carriage return)s from the file.

Luck;
Ken

[sergeyvl12]

Slightly improved reboot.sh
(with reboot screen)

#!/bin/sh
zcat /etc/images/reboot.raw.gz | /usr/local/Kobo/pickel showpic
/bin/busybox reboot

Paola! Be carefull You can occasionaly touch reboot button on your screen and reboot will happen As fo me I added reboot option to KoboLauncher...

Where I can find good "power off" standard picture? For now I can see it in my kobo (spleepy ebook + "Powered off" text). But I don't understand where I can find it??? I looked into /etc/images but nothing... The problem that Kobo Touch, Kobo Glo and Kobo Aura have different screen resolutions and we can't make single custom "power off" picture.

[paola]

thank you so much guys: however I use Crimson editor, and generally it does not add carriage returns, and at any rate with the hex editor no carriage returns are showing in the file.
I don't know why, but the "power off" entry in the kobolauncher never did anything for me, otherwise I would use that one: if I press on it, nothing happens.

EDIT: The kobo_launcher.ini file looks like this

Chess    = pbchess-1.2.5/pbchess
Checkers = checkers/checkers
Sokoban  = sokoban/sokoban
Reversi  = reversi/reversi
Gomoku   = gomoku/gomoku
Notepad  = notepad/notepad
Calculator  = calculator/calculator
usbnet   = usbnet/start.sh
Power off = poweroff

but I have no "poweroff" file in the KoboLauncher directory, that explains it (I think). Would it be correct to put a file "poweroff" with the following code:

#!/bin/sh
/bin/busybox poweroff

[sergeyvl12]

Originally Posted by paola

but I have no "poweroff" file in the KoboLauncher directory, that explains it (I think). Would it be correct to put a file "poweroff" with the following code:

#!/bin/sh
/bin/busybox poweroff

Yes, it should work

[paola]

Originally Posted by sergeyvl12

Yes, it should work

well, for some reason it does not. Tried the same with kobolauncher, but it does not work. Who knows why, but I'll manage with the restart, which is working fine, as sleep is ok (i have switched the power button to taking screenshots).

[giorgio130]

Originally Posted by paola

well, for some reason it does not. Tried the same with kobolauncher, but it does not work. Who knows why, but I'll manage with the restart, which is working fine, as sleep is ok (i have switched the power button to taking screenshots).

Could be the space in "Power off"? try with "Power_off"

[paola]

Originally Posted by giorgio130

Could be the space in "Power off"? try with "Power_off"

thanks Giorrgio, you mean literally with the underscore and capital P? Is just that in the list of Busybox commands I found"poweroff", but I will try with your suggestion and report back.

[paola]

is it possible firmware version 2.6.2 has broken filesmonitor? The icons just don't call the programme anymore. Kobolauncher works fine, though, but I have to launch it from the Tweaks.

[sergeyvl12]

Originally Posted by paola

is it possible firmware version 2.6.2 has broken filesmonitor? The icons just don't call the programme anymore. Kobolauncher works fine, though, but I have to launch it from the Tweaks.

Paola, try reinstall the launcher?

[paola]

Originally Posted by sergeyvl12

Paola, try reinstall the launcher?

Thanks sergey, I reinstalled fmon, and it works now. I still cannot launch koreader from the tweaks, but that is a different issue.
Thanks again for all your work!

[Turtledog]

Can anyone tell me how to ¨Just install KoboRoot.tgz¨?

[paola]

Originally Posted by Turtledog

Can anyone tell me how to ¨Just install KoboRoot.tgz¨?

it means that you have to copy the file "KoboRoot.tgz" in the .kobo subdirectory of your device. Then eject the device and disconnect it, and you will see the device "updating", and eventually restarting. Better to do this with your device charged up. Also, do make sure you copy the file in the .kobo subdirectory - otherwise (as with all hacks) you risk bricking it (it happened to me..), i.e. making your device unusable. To fix this may require opening your device and replacing the internal SD card (assuming your device has one), which many people don't like to do, as not doing it properly (e.g. if you happen to break one of the plastic thingy holding the device together) will show the device has been open and void your warranty.

[Skinkie]

I have attempted to install fmon by:

- Syncing to the latest Aura HD software version. 2.10
- Copy KoboRoot.tgz to .kobo
- Restart the device

At the previous version I had succesfully installed Launcher.

Now all I see is a 'restart' animation. (5 boxes, going from white to black)

Anyone has a suggestion to surpass this problem?

It really seems the animation is 'on top' of the normal interface. Overriding it.

This post helped me to do a factory reset on the Aura HD.
https://www.mobileread.com/forums/sho...44&postcount=4

I'll attempt to do a reinstall of the fmon software, don't mind some tips. [It worked]

[Ken Maltby]

Originally Posted by Skinkie

I have attempted to install fmon by:

- Syncing to the latest Aura HD software version. 2.10
- Copy KoboRoot.tgz to .kobo
- Restart the device

At the previous version I had succesfully installed Launcher.

Now all I see is a 'restart' animation. (5 boxes, going from white to black)

Anyone has a suggestion to surpass this problem?

It really seems the animation is 'on top' of the normal interface. Overriding it.

This post helped me to do a factory reset on the Aura HD.
https://www.mobileread.com/forums/sho...44&postcount=4

I'll attempt to do a reinstall of the fmon software, don't mind some tips.

Not sure what you mean by " Syncing to the latest Aura HD software version. 2.10" The latest official current firmware for the AuraHD is, at least 3.0.0., are they still pushing 2.10 when you sync? I am using 3.0.0, downloaded from the firmware sticky.

I would update your firmware first as long as you are starting over anyway.

Luck;
Ken

[swamp thing]

Can the fmon "daemon" be triggered if the png file is accessed indirectly?

For example, an HTML page containing hyperlinks to various png's (or even inline png's in an HTML page that the browser needs to fetch and render)...?

This could be an easy way to build menus for different fmon-based actions.