Kobo Start Menu

[booklover6]

Kobos are kind of wacky, anyway. Last month the Aura went haywire when I put KSM and KoReader on it. I believe it was due to the presence of the external SD card. It's now fine, with no ext card. (Had to factory reset it first).

This Glo does not have an ext SD card, but has been opened and internal card replaced. That type of thing tends to invite problems.

If only Kobo would make an Aura with the H20 screen, and say 8gb internal memory! (Then I wouldn't be tempted to open the case and swap the card!)

The Glo is still acting up. I'm going to remove KoReader from it. There is no "official" way to remove KSM, that I can see, but no harm in leaving it on the device, right?

[booklover6]

Does this error

calibre, version 2.18.0
ERROR: Error: Error communicating with device

database disk image is malformed

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 87, in run
File "site-packages\calibre\gui2\device.py", line 503, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1685, in books
File "site-packages\calibre\devices\kobo\driver.py", line 2590, in get_bookshelflist
DatabaseError: database disk image is malformed

Mean that my Kobo disk image is malformed, or my installation of Calibre? (which is up to date)

Never mind, it's the Kobo, darn it. I'll log out and log back in.

[davidfor]

booklover6: That error means the database on the device is probably corrupt. The log out an back in should fix it. Unless you have a recent backup of the database that you can restore. Using that will mean you only lose any changes since the backup was done.

[booklover6]

Thanks, davidfor. I hope that fixes it. It is taking an abysmally long time to finish "processing content" after logging back in.

[tshering]

Originally Posted by booklover6

Thanks, davidfor. I hope that fixes it. It is taking an abysmally long time to finish "processing content" after logging back in.

After nickel has finished processing the content, search in the library for the KSM png files and open them. Otherwise nickel might refuse to start next time. If this happens nonetheless, please tell it, so that we can handle it.

[booklover6]

Originally Posted by tshering

After nickel has finished processing the content, search in the library for the KSM png files and open them. Otherwise nickel might refuse to start next time. If this happens nonetheless, please tell it, so that we can handle it.

The PNG files were there, but KSM (and my patch) seemed to have disappeared. I am putting KSM back on now.

And it was working fine, until I decided to put nightmode on it. It did not process the nightmode file correctly. I pin hole reset and it was not starting nickel, it was going into a bootloop when I tried. Fortunately, with KSM working, I was able to connect to the PC and remove the file and start nickel. But now my disc image is malformed again. So maybe the nightmode was the problem all along.

[tshering]

Originally Posted by booklover6

The PNG files were there, but KSM (and my patch) seemed to have disappeared.

Difficult to imagine that logging out and in can cause this to happen. Your patch should only disappear when the firmware is updated (in this case KSM might also get disabled, but it should not disappear from the sd).

Originally Posted by booklover6

And it was working fine, until I decided to put nightmode on it. It did not process the nightmode file correctly.

What do you mean by saying that it did not process the neightmode file correctly?

Originally Posted by booklover6

I pin hole reset and it was not starting nickel, it was going into a bootloop when I tried. Fortunately, with KSM working, I was able to connect to the PC and remove the file and start nickel. But now my disc image is malformed again. So maybe the nightmode was the problem all along.

With regard to nickel not starting (or rather: starting and immediately exiting) and maybe thereby corrupting the database, I think that this is connected with fmon and suggests that not all images of the folder kbmenupngs have been completely processed by nickel (I mean not all the thumbnails have yet been created). It is important that nickel does this before KSM is installed. But somehow this seems to be difficult to achieve. So if this happens again please download the archive from this post, extract the script and put it into the folder .kobo\kbmenu\scripts. After ejecting select in KSM "scripts" > "start nickel test no fmon.sh" in order to start nickel without fmon. This will give nickel another chance to process the KSM pngs. Open (all four of) them from the library, remove their tiles from the home (if they are put there). Exit nickel by powering off with the slider. After restarting everything should be working.

Originally Posted by booklover6

BTW when I logged out/in it was as if I did a factory reset. Everything was gone. Is that normal?

I never logged out/in myself, but I do not think that this is normal.

[booklover6]

Originally Posted by tshering

Difficult to imagine that logging out and in can cause this to happen. Your patch should only disappear when the firmware is updated (in this case KSM might also get disabled, but it should not disappear from the sd).

So there is something wrong with the image. I think I am going to have to factory reset. I am doing one more log out/log in, first.

Originally Posted by tshering

What do you mean by saying that it did not process the neightmode file correctly?

Instead of going to a restart, it was on the "processing content" screen, for several minutes, so I pin hole reset it. It was definitely the right zip file in the right folder (.kobo)

So then, because I don't have enough of a headache, I decided to remove the nightmode hack from my Aura, since it has KoReader (which has its own nightmode setting) and attempted to do so using the uninstall zip. Bad move. It went to "processing".....so pin holed that and looked in the files, the zip was still there, in the .kobo folder. I deleted it and the 2 nightmode files that were in .kobo. The Aura seems to be doing ok, now.

The Glo is 14% along in processing after signing in. It's going to be awhile.

[tshering]

Originally Posted by booklover6

So there is something wrong with the image. I think I am going to have to factory reset. I am doing one more log out/log in, first.



Instead of going to a restart, it was on the "processing content" screen, for several minutes, so I pin hole reset it. It was definitely the right zip file in the right folder (.kobo)

So then, because I don't have enough of a headache, I decided to remove the nightmode hack from my Aura, since it has KoReader (which has its own nightmode setting) and attempted to do so using the uninstall zip. Bad move. It went to "processing".....so pin holed that and looked in the files, the zip was still there, in the .kobo folder. I deleted it and the 2 nightmode files that were in .kobo. The Aura seems to be doing ok, now.

The Glo is 14% along in processing after signing in. It's going to be awhile.

When installing a KoboRoot.tgz, do you really see the "processing content" screen? Or did you mean the update screen?

[booklover6]

Originally Posted by tshering

When installing a KoboRoot.tgz, do you really see the "processing content" screen? Or did you mean the update screen?

It did actually say "processing content" which is how I knew something was wrong.

[booklover6]

Originally Posted by booklover6

The Aura seems to be doing ok, now.

The Glo is 14% along in processing after signing in. It's going to be awhile.

Spoke too soon. KSM disappeared from the Aura so I reinstalled it, after checking the images. Working now, so reinstalling KoReader.

Now the Aura appears to be A-OK.

The Glo, well she is still processing after the latest log in, currently at 49% after nearly an hour.

[tshering]

Originally Posted by booklover6

Spoke too soon. KSM disappeared from the Aura so I reinstalled it, after checking the images.

I cannot exactly understand from your description at which point KSM disappeared. Did you install the update to KSM 06 too? Please have a look at this post.

[booklover6]

No, I did not install an update. I installed KBStartMenu_06.zip which I downloaded on 1/12/15.

I just installed the update following the instructions in post #591. Fast and easy. Thank you for that information.

I want to be able to switch back and forth between nickel and KoReader and read in either one at will.

(By the way the Glo is still processing. 76% about 90 minutes after logging in.)

[tshering]

[QUOTE=booklover6;3037290]I want to be able to switch back and forth between nickel and KoReader and read in either one at will./QUOTE]I am not sure whether this is working on Aura right now, but it will certainly after the next KSM update

[booklover6]

Originally Posted by tshering

I am not sure whether this is working on Aura right now, but it will certainly after the next KSM update

I can do it, by exiting one and going to the other. I was having issues with it on the Aura last week, but I think it might have been due to the presence of an ext SD card. After I factory reset it, switching back and forth has not resulted in any errors (on my Aura). So you are making a faster way to switch? I like reading in KoReader because I use the minibar showing all the stats, but then I like the home screen and the series info that nickel shows me. So I use both.

ETA the Glo finally finished. It's running fine now with no DB errors. I am not going to add KSM or KoReader to it. I don't dare!