NickelDBus - monitor and run actions over d-bus

[Rid]

Originally Posted by sherman

Thanks for the reports, I'll have to investigate this when I get time.

I think it may not have been working as I expected because I did not know about the device going into standby (thread).

[Rid]

Is it possible to have NickelDBus start the Kobo sync and also send a signal back to say it has completed the sync, successfully or otherwise?

[sherman]

Originally Posted by Rid

Is it possible to have NickelDBus start the Kobo sync and also send a signal back to say it has completed the sync, successfully or otherwise?

Are you talking about syncing to the Kobo severs? It might be possible, but it is not something I've looked into, so can't say for sure.

[Rid]

Yes I believe it is to the Kobo servers.

New books I buy from Kobo, bookmarks etc. I am one of those people that every month the sync stops working and it can drain the battery from 90% to 10% in 30min. I usually have to delete the larger collections to get it working again.

Made a script that turns off the wifi after a certain amount of time, and would like to streamline the process and include starting the sync, as it takes a several more steps to start the sync while reading a book.

Even if it not possible that would be great to know so I can get this monkey off my back!

[compurandom]

Originally Posted by Rid

I am one of those people that every month the sync stops working and it can drain the battery from 90% to 10% in 30min. I usually have to delete the larger collections to get it working again.

I have the same problem. I think this is caused by database corruption in the encrypted database.

Another way to fix it is to use calibre to back up the database daily, and when sync stops working, unpack the backup calibre made from the day of (or day before) the last successful sync, and replace the KoboReader.sqlite and BookReader.sqlite on the device and reboot it and let it re-import the books you've added since, and then use calibre to update the bookmarks for books you've read since.

This has worked a few times for me now, and is a lot better than doing a factory reset or deleting lots of stuff and putting it back.

[Rid]

Thanks I did not think about the database backup!

Edit: I do use Calibre always wondered if that could be an issue?

[mullse01]

Hello, I'm attempting to create a shell script with NickelDBus triggered fron MickelMenu. The goal is to show a dlgConfirmAcceptReject prompt when choosing the "reboot" option in NickelMenu, but I can't seem to get NickelDBus to actually *do* anything after the dialog box appears. Here's the text of the shell script as I've got it:

#!/bin/sh

signal=$(qndb -t 10000 -s dlgConfirmResult -m dlgConfirmAcceptReject "Reboot Kobo" "Are you sure you want to reboot?" "Yes" "No")

if ( $signal -eq 1 )
then
qndb -m mwcToast 3000 "Rebooting..."
qndb -m pwrReboot
elif ( $signal -eq 0 )
then
qndb -m mwcToast 3000 "Reboot cancelled."
fi

Am I missing some obvious syntax issue?

[NiLuJe]

Originally Posted by mullse01

Am I missing some obvious syntax issue?

Yes, parens are for subshells, not tests.

You want square brackets.

[hatuluang]

Originally Posted by Rid

Yes I believe it is to the Kobo servers.

New books I buy from Kobo, bookmarks etc. I am one of those people that every month the sync stops working and it can drain the battery from 90% to 10% in 30min. I usually have to delete the larger collections to get it working again.

In my case, I always sideload the book purchased from the Kobo store and manage my own collection with Calibre, so I don't depend on the Kobo sync server. The downside of course the sideload books don't sync with Kobo, but I only read books on Kobo e-reader, so its fine with me.

Edit: I do use Calibre always wondered if that could be an issue?

It won't be an issue if you are using Kobo Touch/Kobo Touch Extended, make sure to check "update purchase book"

[mullse01]

Originally Posted by NiLuJe

Yes, parens are for subshells, not tests.

You want square brackets.

Thanks so much! This got me pointed in the right direction - I also realized my variable was not outputting "1" or "0", but "dlgConfirmResult 1" and "dlgConfirmResult 0", which was also preventing anything from happening.

Either way, your help is greatly appreciated, both here in this thread, and in the community as a whole!

[hatuluang]

deleted

[lordeagle]

Tried to install NickelDBus on Kobo Elipsa 2E, 4.38.23171

My attempt:
- cobied KoboRoot.tgz to .kobo on the mounted reader
- unmount ... update process is running
- after reboot: ssh into the device

Findings:
- most of the files in KoboRoot.tgz are not installed:
- no '/usr/bin/qndb', nor '/mnt/onboard/.adds/nickeldbus'
- however, there exists an empty 'etc/dbus-1/system.d/'com-github-shermp-nickeldbus.conf'

Workaround?
- tried the official latest release from github
- also a fresh build from 'main' branch leads to the same effect.

Could it be that Kobo started to block this? Anything I can check to trace the update process?

[sherman]

Originally Posted by lordeagle

Tried to install NickelDBus on Kobo Elipsa 2E, 4.38.23171

My attempt:
- cobied KoboRoot.tgz to .kobo on the mounted reader
- unmount ... update process is running
- after reboot: ssh into the device

Findings:
- most of the files in KoboRoot.tgz are not installed:
- no '/usr/bin/qndb', nor '/mnt/onboard/.adds/nickeldbus'
- however, there exists an empty 'etc/dbus-1/system.d/'com-github-shermp-nickeldbus.conf'

Workaround?
- tried the official latest release from github
- also a fresh build from 'main' branch leads to the same effect.

Could it be that Kobo started to block this? Anything I can check to trace the update process?

Ok, this is a new one for me...


My immediate thought is user permissions, although I'm not sure why this would be the case.


The upgrade is performed in the init script at

/etc/init.d/rcS

. I see nothing in there that would explain this.

[geek1011]

Corrupt tar? The dbus conf is the first entry in it, so it would make sense that the rest doesn't exist, and the first is incomplete.