Kobo Start Menu 08 - Page 59

aklenatlus · 11-06-2017, 04:55 AM

Hi everyone, I was thinking about to try koreader on my Aura One. I have installed the latest firmware (4.6.9995), is it safe intalling KSM 8?
Thanks in advance

David0226 · 11-06-2017, 07:07 AM

Quote:

Originally Posted by aklenatlus

Hi everyone, I was thinking about to try koreader on my Aura One. I have installed the latest firmware (4.6.9995), is it safe intalling KSM 8?
Thanks in advance

I have successfully installed KSM 8 on my Aura One running 4.6.9995.

stats · 11-06-2017, 09:27 PM

It's working on my H2O. Dictionary support is broken in koreader. There is a fix on the koreader wiki, but I haven't tried it yet.

Cheers,
Rich

Sent from my SM-T810 using Tapatalk

Question Mark · 11-06-2017, 10:00 PM

Quote:

Originally Posted by stats

It's working on my H2O. Dictionary support is broken in koreader. There is a fix on the koreader wiki, but I haven't tried it yet.

Both KSM 08 and Koreader are working fine on my KA1 with the 4.6.9995 Kobo FW.

Initially, dictionary support seemed to be broken on Koreader with this most recent Kobo FW update. However, found some help in the following thread in the Koreader forum and that fixed the issue. Dictionaries are working fine now. Just wish I had more time for reading.

https://www.mobileread.com/forums/sh...33#post3595933

stats · 11-06-2017, 10:40 PM

That's the same as I found. It fixed the issue on my Kobo. All is good now!

Cheers,
Rich

Sent from my SM-T810 using Tapatalk

Frenzie · 11-07-2017, 06:28 AM

Still broken on the latest Kobo FW? Drat, I was hoping the problem would resolve itself (since apparently 4.6.9990 or something was rather buggy).

stats · 11-07-2017, 11:44 AM

With the exception of the one workaround, everything is fine on 4.6.9995. Replace sdcv with the patched one. Nickel is better and everything seems snappier.

Cheers,
Rich

Sent from my VS995 using Tapatalk

gilali · 11-11-2017, 02:12 PM

Hi,
Is it here to report an issue ? maybe a bug :
I cannot access from ssh to my 2 devices (H2O2 and KA2), either by wifi or by usbNET.

From KSM, I am able to ping both devices, on both support (usbnet and wifi)
To be sure, I've added "useDropbear=true" in [general] section

Result :
with putty, I have "connection refused" on default ssh port, and no message on telnet.

I have insisted before posting (many factory resets, many reinstalls...)
Because, for a fresh supported device (H2O2) why not, but with Kobo Aura 2, it's very curious.

Somebody can confirm SSH is working on Kobo Aura 2 ? (and at the same time I am not very talented)
Regards,

tshering · 11-11-2017, 03:47 PM

Quote:

Originally Posted by gilali

Hi,
Is it here to report an issue ? maybe a bug :
I cannot access from ssh to my 2 devices (H2O2 and KA2), either by wifi or by usbNET.

From KSM, I am able to ping both devices, on both support (usbnet and wifi)
To be sure, I've added "useDropbear=true" in [general] section

Result :
with putty, I have "connection refused" on default ssh port, and no message on telnet.

I have insisted before posting (many factory resets, many reinstalls...)
Because, for a fresh supported device (H2O2) why not, but with Kobo Aura 2, it's very curious.

Somebody can confirm SSH is working on Kobo Aura 2 ? (and at the same time I am not very talented)
Regards,

Are you aware that KSM uses the dropbear provided by the vlasovsoft kobo launcher (PBChess)? I hope it is still include in the more recent versions of the kobo launcher. Another point to note is, that KSM switches dropbear on only when you choose USBnet.
Did you enable telnet on your device? If not, see the first post of this thread under "enable USBNet". If security is not a problem, you can simple telnet into your device without having dropbear running.

gilali · 11-12-2017, 07:00 AM

I'm running Win7, and i've missed to install KevinShort's package.

Quote:

plus this post, if you are running Windows 10. To make telnet work install KevinShort's package

I have misunderstood. Thank you for your patience.

Telnet is now running on H2O2

And over WIFI it's very comfortable.
I confirm NO need to activate USBnet. Kevin's patch + wifi activation is enought. It's the best for geeking underwater

geekraver · 11-14-2017, 12:01 AM

@tshering, it's probably okay for you to remove the warning about the H202 in the first post now. We still have koReader problems but KSM is operational at least.

I had done a factory reset after installing the new firmware, and I had to reboot twice after installing your patch on page 57 of this thread before it worked, but it is working.

rba · 11-17-2017, 04:16 PM

Quote:

Originally Posted by tshering

You need only to re-install the patch.

Hey - I'm having the same issue here. However, the instructions linked in the solution above require that you can boot into KSM, which I can't do after the firmware upgrade to 4.6.9995. Is there another way to run the patch scripts besides the following instruction?

select (in KSM home) "handle update" > "install update" (do not select "install partial update")
?

tshering · 11-17-2017, 05:10 PM

Quote:

Originally Posted by rba

Hey - I'm having the same issue here. However, the instructions linked in the solution above require that you can boot into KSM, which I can't do after the firmware upgrade to 4.6.9995. Is there another way to run the patch scripts besides the following instruction?

select (in KSM home) "handle update" > "install update" (do not select "install partial update")
?

Copy the KoboRoot.tgz into the .kobo folder of your device, and safely eject the device. The inbuilt update mechanism will take care of it.

CmplxAdSys · 11-18-2017, 10:51 PM

Quote:

Originally Posted by tshering

Thank you for reporting. I have a similar report from an Aura HD user (also on FW 4.6.9995). According to his observation he can reproduce the rotation by

(ksm home) start nickel
switch/leave in nickle wifi on
exit nickel by opening "switchtokoreader.png"

When the "wifi is on! Switch it off: yes/no" menu appears, the screen is rotated. I cannot see why having wifi on, or exiting nickel by "switchtokoreader.png" (without being in a nickel - koreader loop), or both together can trigger the rotation issue.
Could you try how this is on your device?

I've the same problem on an H20 (first gen) with FW 4.6.9995, except wifi is off. The only reliable pattern I've found concerning it is that it is fixed if I reboot KSM.

masterz87 · 11-25-2017, 02:33 PM

koreader is upside down from the start of the system. It's upside down and the touch event's aren't even right. Tapping the bottom of the menu only registers midway through the menu and the touch events are switched too even somehow. The screen's registering of touch events is opposite of what it seems like too.

11-07-2017, 11:44 AM	#877
stats Member Posts: 17 Karma: 574 Join Date: Dec 2008 Device: sony pr505	With the exception of the one workaround, everything is fine on 4.6.9995. Replace sdcv with the patched one. Nickel is better and everything seems snappier. Cheers, Rich Sent from my VS995 using Tapatalk Last edited by stats; 11-07-2017 at 11:47 AM.

11-14-2017, 12:01 AM	#881
geekraver Addict Posts: 364 Karma: 1035291 Join Date: Jul 2006 Location: Redmond, WA Device: iPad Mini,Kindle Paperwhite	@tshering, it's probably okay for you to remove the warning about the H202 in the first post now. We still have koReader problems but KSM is operational at least. I had done a factory reset after installing the new firmware, and I had to reboot twice after installing your patch on page 57 of this thread before it worked, but it is working. Last edited by geekraver; 11-14-2017 at 12:19 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kobo-Adding alternative readers using Kobo Start Menu	Ken Maltby	KOReader	75	01-10-2020 01:35 PM
Kobo Start Menu	tshering	Kobo Developer's Corner	918	10-12-2017 02:32 PM
Kobo Start Menu 07	tshering	Kobo Developer's Corner	644	03-02-2017 06:40 AM
QT Browser for Kobo Start Menu?	gloriousglib	Kobo Developer's Corner	1	05-24-2014 03:59 AM
Calibre start menu icon	Cy1clown	Calibre	1	02-06-2010 02:10 PM

11-06-2017, 04:55 AM	#871
aklenatlus Enthusiast Posts: 30 Karma: 16190 Join Date: Jul 2016 Location: Rome, Italy Device: Kobo Aura One	Hi everyone, I was thinking about to try koreader on my Aura One. I have installed the latest firmware (4.6.9995), is it safe intalling KSM 8? Thanks in advance

11-06-2017, 09:27 PM	#873
stats Member Posts: 17 Karma: 574 Join Date: Dec 2008 Device: sony pr505	It's working on my H2O. Dictionary support is broken in koreader. There is a fix on the koreader wiki, but I haven't tried it yet. Cheers, Rich Sent from my SM-T810 using Tapatalk

11-06-2017, 10:40 PM	#875
stats Member Posts: 17 Karma: 574 Join Date: Dec 2008 Device: sony pr505	That's the same as I found. It fixed the issue on my Kobo. All is good now! Cheers, Rich Sent from my SM-T810 using Tapatalk

11-07-2017, 06:28 AM	#876
Frenzie Wizard Posts: 1,758 Karma: 731681 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Still broken on the latest Kobo FW? Drat, I was hoping the problem would resolve itself (since apparently 4.6.9990 or something was rather buggy).

11-11-2017, 02:12 PM	#878
gilali Connoisseur Posts: 74 Karma: 28960 Join Date: Oct 2017 Location: Paris Device: KOBO Libra + H2Ov2 + Aura2	Hi, Is it here to report an issue ? maybe a bug : I cannot access from ssh to my 2 devices (H2O2 and KA2), either by wifi or by usbNET. From KSM, I am able to ping both devices, on both support (usbnet and wifi) To be sure, I've added "useDropbear=true" in [general] section Result : with putty, I have "connection refused" on default ssh port, and no message on telnet. I have insisted before posting (many factory resets, many reinstalls...) Because, for a fresh supported device (H2O2) why not, but with Kobo Aura 2, it's very curious. Somebody can confirm SSH is working on Kobo Aura 2 ? (and at the same time I am not very talented) Regards,

11-25-2017, 02:33 PM	#885
masterz87 Connoisseur Posts: 56 Karma: 2072578 Join Date: Jan 2017 Device: Kobo Aura H20	koreader is upside down from the start of the system. It's upside down and the touch event's aren't even right. Tapping the bottom of the menu only registers midway through the menu and the touch events are switched too even somehow. The screen's registering of touch events is opposite of what it seems like too.