Kobo Start Menu 07

[cakesmashers]

Originally Posted by tshering

I think this is serious. In this situation nickel will not process any books that you put anew to the reader. Maybe you do not use nickel anyway and therefore you do not care so much. But something is wrong with your device. Maybe you should factory reset it.

Do you have any other "irregular" software that runs after boot beside KSM?

This same issue happened to me. I fixed the issue by completely uninstalling KSM and then reinstalling it. However the second go around I installed each KSM update one at a time. Before, I added all 3 updates in the .adds folder (as suggested), which I think messed up the install.

[tshering]

Originally Posted by cakesmashers

This same issue happened to me. I fixed the issue by completely uninstalling KSM and then reinstalling it. However the second go around I installed each KSM update one at a time. Before, I added all 3 updates in the .adds folder (as suggested), which I think messed up the install.

I just uninstalled KSM, and then installed it anew, and immediately after that I installed the three updates all in one go. I can still connect via usb without inserting an sd, from KSM and from nickel. So this way of installing the updates was maybe not responsible for the issue.

Maybe we could figure out what was happening, if we knew some specific user patterns shared by you and juequ.

[tshering]

Originally Posted by flip1314

I have a Glo HD. KSM installs fine, but when I go to process update 1 the geometry flips 90 degrees clockwise on the "tap&close" page and I cannot move forward from there.

Could you give me some more information. I understand you tried to install only the first of the three updates. Right? Before you installed it did you start nickel? If yes, did you exit nickel via the png and did KSM then still work?
When you installed update 1 and the tap&close page appeared, tapping at the middle of the screen had no effect at all. Did you tapping all over the place? Sure the bottom menu did not appear but did something else happen? Was there a screen refresh?

Originally Posted by flip1314

Ya, I tried that stuff before I got your message. I had to pull the SD card and remove the kbmenu folder to get it working again. It just became a blank screen and would no longer boot nickle.

That means you forced the device to power off. After powering on again, you waited for some time but there was only a white screen. Was that the sequence of events?

[AlterusPrime]

Hello, it's me again.
I'm not actually sure i should ask it in this thread, but since it's kinda related to KSM..
Anyways, i'll ask, if it's not right place to - i'll leave and ask in a new thread.
So, since there's a busybox and there's an ability to run terminal i was wondering if i can use telnet in it. I tried and found out that it doesnt work properly. When i try to connect to the local (192.168.1.*) PC where's no telnet-server running it does it's job and gives me output (connection refused etc). But whenever i try to connect to any "global" telnet server (by ip or domain name) it just hangs my Glo and never gives any output (nslookup works fine), i have to force power off to make my way out of there.
So i wonder if there's any way to fix it.
Thanks in advance.

UPD: looks like it can't handle any server answer. kinda strange..

[johnnyb]

Originally Posted by cakesmashers

This same issue happened to me. I fixed the issue by completely uninstalling KSM and then reinstalling it. However the second go around I installed each KSM update one at a time. Before, I added all 3 updates in the .adds folder (as suggested), which I think messed up the install.

I think something similar happened to me as well. Maybe the updates could be integrated into the main KSM file or at least into one big upgrade?

[tshering]

Originally Posted by AlterusPrime

Hello, it's me again.
I'm not actually sure i should ask it in this thread, but since it's kinda related to KSM..
Anyways, i'll ask, if it's not right place to - i'll leave and ask in a new thread.
So, since there's a busybox and there's an ability to run terminal i was wondering if i can use telnet in it. I tried and found out that it doesnt work properly. When i try to connect to the local (192.168.1.*) PC where's no telnet-server running it does it's job and gives me output (connection refused etc). But whenever i try to connect to any "global" telnet server (by ip or domain name) it just hangs my Glo and never gives any output (nslookup works fine), i have to force power off to make my way out of there.
So i wonder if there's any way to fix it.
Thanks in advance.

UPD: looks like it can't handle any server answer. kinda strange..

Maybe there are several issues. I think one issue is that kbterminal is not a real dash terminal. It is just a one-shot thing. It just writes one command into a new shell, and waits for the answer. At the moment kbterminal is displaying the answer, the shell is already closed. when you chose "file mode" instead of "direct mode", the text of the input line is written to a file and the file is executed in a new shell. That gives you the possibility for a little bit complexer tasks, but it is still a single shot. I am not sure whether I can make myself understood in this way.

[AlterusPrime]

The thing is it hangs even if in file mode. Well, since it's a "one-shot" anyways, then it doesn't even deserve further research. Thanks again

[tshering]

Originally Posted by AlterusPrime

The thing is it hangs even if in file mode. Well, since it's a "one-shot" anyways, then it doesn't even deserve further research. Thanks again

I guess it hangs because it is waiting that the process that is called finishes, but the process does not finish without further user input.

[tshering]

Originally Posted by johnnyb

I think something similar happened to me as well. Maybe the updates could be integrated into the main KSM file or at least into one big upgrade?

I was planning to make a new KSM package anyway in the near future that would include all update packages published at that point.
But even then I would be interested in knowing what is happening. As I reported yesterday, I installed KSM 7 anew and applied the three updates in one go. And it worked without any problems.

[juequ]

Originally Posted by tshering

I think this is serious. In this situation nickel will not process any books that you put anew to the reader. Maybe you do not use nickel anyway and therefore you do not care so much. But something is wrong with your device. Maybe you should factory reset it.

Do you have any other "irregular" software that runs after boot beside KSM?

Thanks for your reply.

Yes, it's true that since I installed KSM6, nickel has hardly processed any "new" books storing in reader itself.
But if I store some books in an SD card, nickel can process those books correctly.

Actually it doesn't matter, because I never use nickle after I installed KSM.
Most of the books I read are in .pdf format, so I installed KOreader in KSM to read these pdf books. And KOreader is the only software I installed after boot beside KSM.

[tshering]

Originally Posted by juequ

Yes, it's true that since I installed KSM6, nickel has hardly processed any "new" books storing in reader itself.
But if I store some books in an SD card, nickel can process those books correctly.

Nickel scans the internal storage for new books only when it detects that the reader has been disconnected from the pc (which does not happen if you connect from KSM).

Originally Posted by juequ

And KOreader is the only software I installed after boot beside KSM.

Thank you for this information. Maybe you could tell me more about how you installed KSM 7. Maybe you did anything spacial like, installing update 1; and than later all three updates in one go; or installing updates 1 and 2, and later all three in one go. Or something like this. I would like to know why there is this usb issue.

[flip1314]

Originally Posted by tshering

Could you give me some more information. I understand you tried to install only the first of the three updates. Right? Before you installed it did you start nickel? If yes, did you exit nickel via the png and did KSM then still work?
When you installed update 1 and the tap&close page appeared, tapping at the middle of the screen had no effect at all. Did you tapping all over the place? Sure the bottom menu did not appear but did something else happen? Was there a screen refresh?

That means you forced the device to power off. After powering on again, you waited for some time but there was only a white screen. Was that the sequence of events?

Hey tshering, It doesn't matter if I install one or all three. When I tell it to handle the updates the screen rotates 90 degrees CCW and I can tap the centre to see the close option, but the GloHD is not recognizing the tap to the bottom. This is most likely because the software doesn't realize the screen has been moved. I have tried taping the centre of the screen in normal orientation, incase the touch orientation had stayed normal, but no joy.

I did let nickel boot before the updates were loaded onto the device, and yes when I started it the second time it went to a blank screen and stayed there indefinitely. I had to do a hard reboot. The light, under the power button, kept flashing but there was no activity on the screen.

In the end I had to pull the sd card and re-flash it.

[tshering]

Originally Posted by flip1314

Hey tshering, It doesn't matter if I install one or all three. When I tell it to handle the updates the screen rotates 90 degrees CCW and I can tap the centre to see the close option, but the GloHD is not recognizing the tap to the bottom. This is most likely because the software doesn't realize the screen has been moved. I have tried taping the centre of the screen in normal orientation, incase the touch orientation had stayed normal, but no joy.

Very annoying situation. Especially since the tap&close message seems to prevent the successful completion of the update. Did you by chance make a copy of the sd before you re-flashed it? Would be interesting to see the files of the .adds/kbmenu folder and the rcS.

Originally Posted by flip1314

I did let nickel boot before the updates were loaded onto the device, and yes when I started it the second time it went to a blank screen and stayed there indefinitely. I had to do a hard reboot. The light, under the power button, kept flashing but there was no activity on the screen.

In the end I had to pull the sd card and re-flash it.

So you had to reflash the sd several times, once after starting nickel the second time, and once (or serveral times), when trying to update? I wonder what running nickel for the second time can change on the sd, so that KSM can not start.

[juequ]

Originally Posted by tshering

Nickel scans the internal storage for new books only when it detects that the reader has been disconnected from the pc (which does not happen if you connect from KSM).

Thank you for this information. Maybe you could tell me more about how you installed KSM 7. Maybe you did anything spacial like, installing update 1; and than later all three updates in one go; or installing updates 1 and 2, and later all three in one go. Or something like this. I would like to know why there is this usb issue.

Thanks very much for your KSM, cause KSM make it possible to run Koreader on my Kobo H2O. The Kobo pdf app is not user friendly, I can hardly read any books in pdf format without KSM+Koreader.

I bought my Kobo H2O on October 3 last year, I had a bad experience at that time because of its bad pdf app.

I updated the FW to 3.11 in Nov. 2014; and installed patch_kobo_3110 to change some configuration of the Kobo pdf app which made a little progress in the performance of the Kobo pdf app, but still not good enough.

Things has been changed since the beginning of Dec. 2014 when I installed KSM06 and Koreader. (I followed the spoiler in webpages to install the KSM & Koreader.) I felt much better to read pdf books after that even though Koreader crashed sometimes.

Since I installed KSM06, usb to PC connection in nickel has seldom worked.
Even I tried the logo "simulate_usb_connection.png", it seemed to work after reboot only. So, I have no choice but to connect USB in KSM.

Then I installed KSM6_update01b in Jan. 2015. And I updated the kobo FW to 3.12 several days later.

At the end of Feb. 2015, I installed KSM7 and KSM7_update001. The usb connect to PC function still worked in KSM only.

Then I installed update002 & update003 together on May 8. And I updated the kobo FW to 3.15 on May 9. This time, I found unexpectedly that the usb enable function would fail in KSM without the SD card.

I also have installed different versions of the Koreader app my Kobo H2O, including the nightly versions. But I don't think the Koreader app affects the usb connection function much.

There is nothing special except the usb connect to PC function problem in nickel.

I hope the information is useful to you.

Thanks again for your help.

[Jellby]

Originally Posted by Jellby

Damn! Now nickel ignores the SD card. I can browse the contents from KSM, I can mount the SD while in nickel, fsck says the card is OK, and yet all the books in the card have disappeared.

I have reinstalled 3.15.0 to get rid of KSM, and the card is back.

Now I have the booting up alternate between nickel and KSM, if it happens again I'll see if KSM has anything to do with it.

I'm still suffering this. Very often, but not always, when I start nickel from KSM the card disappears. So far, I haven't had a problem when I boot directly to nickel.