Firmware 5.0.175773

[Cootey]

Originally Posted by DrChiper

AFAIK, Android (core) is also Linux based. So this is a replacement of one *nix system with another *nix system.

If this was a move from a UNIX based system to a Linux based system, it would be more complicated, but you’re correct. Google used a modified Linux core for Android. Unfortunately, that doesn’t mean that it’ll be an easy process. As somebody who’s ripped his hair out looking up solutions for Linux problems on his raspberry pi, all the different variations of Linux have their different flavors. An aspect of a command on one system may not be supported on another. Since Google tweaked Linux to meet their Android needs, I imagine that’s giving Kobo the biggest headache.

However, if Kobo is unifying both firmware to be the same, and keeps cloud support for Europe, we might have things to look forward to here in North America.

[Aleron Ives]

You can learn about which commands Kobo supports via BusyBox here:

https://boxmatrix.info/wiki/BusyBox-Commands

[DNSB]

Originally Posted by DrChiper

AFAIK, Android (core) is also Linux based. So this is a replacement of one *nix system with another *nix system.

Android is based on Linux but Google made a mass of changes and programming for the two OS is very different. Originally, most Android apps were written in a modified version of Java while the programming language of choice is now Kotlin. A non-trivial C/C++/C# program is not easily portable between the two.

One friend of mine works for a company that uses both Android and Linux on their building control systems. A lot of the time, they claim that porting between the 2 OS is more of a total rewrite than a port.

[PeterT]

Just wondering if it's possible to tell which version of RMSDK is being used in f/w 5.x ?

[Quoth]

Originally Posted by DrChiper

AFAIK, Android (core) is also Linux based. So this is a replacement of one *nix system with another *nix system.

Hardly at all. Completely different frameworks for file access, SD Card access and GUI.
Also all Android since 4.0 uses MTP (originally for DRM on Zune) and most Linux based systems use USB Mass Storage.
Really only the Kernel on Android is like Linux and it's not a standard Linux Kernel either.
Some Android app additionally need the Google Framework (Of course Google Books App and PlayStore needs it). Some Android Apps need either Google's Web View or Chrome (and some Androids even the same version 8.x can't install a late enough Chrome).

User input is different on Android. Android changes how things work dramatically between versions. The ONLY reason to have Android on a ereader is lazy devs or Playstore. It's a mess.

Programs/apps are completely different.

[user105]

Hello, I am new to kobo.
I have the new tolino shine ( kobobclara bw )on fw v5
It is opening books extremely slow, both in kobo and tolino mode. (Devmode switch to…)
It is slow for both epub and the kepub.epub by the calibre extended driver files
The files are drm free and both calibre edit epub checker and the java epubchecker don’t find any errors
A 300 page books takes several minutes to load
In devmode I have render engine for sideloaded books set to default, this is incredibly slow in opening books , if i set this setting to rmsdk the books are opening within 5 seconds.

Is this behaviour normal for kobos? Is fw really broken? Are all my books broken? On my kindle they open as kfx from the source epub very fast

Thanks ! I am really confused

[Sirtel]

Originally Posted by user105

Hello, I am new to kobo.
I have the new tolino shine ( kobobclara bw )on fw v5
It is opening books extremely slow, both in kobo and tolino mode. (Devmode switch to…)
It is slow for both epub and the kepub.epub by the calibre extended driver files
The files are drm free and both calibre edit epub checker and the java epubchecker don’t find any errors
A 300 page books takes several minutes to load
In devmode I have render engine for sideloaded books set to default, this is incredibly slow in opening books , if i set this setting to rmsdk the books are opening within 5 seconds.

Is this behaviour normal for kobos? Is fw really broken? Are all my books broken? On my kindle they open as kfx from the source epub very fast

Thanks ! I am really confused

No, slow opening is not normal on a Kobo. It should take a couple of seconds at most for an average book. No idea about Tolinos, though.

[user105]

Thanks, that makes sense. And it’s very fast on rmsdk,
The kepub.epub shows up as tolino epub and are super slow in opening with default engine.

Same happens in kobo mode, while the device lists it self as Clara bw

I wonder if that is a bug in the v5 fw

[sherman]

Firmware v5 appears to be a massive overhaul, so I'm not surprised if there's going to be some teething issues.

[rashkae]

Hmm, it sounds like Kobo is going to open sideloaded epubs with their, what's it called, Access? Reader instead of RMSDK by default. That is... interesting.

[Quoth]

Originally Posted by rashkae

Hmm, it sounds like Kobo is going to open sideloaded epubs with their, what's it called, Access? Reader instead of RMSDK by default. That is... interesting.

Will Jon like that?

[DNSB]

Magic 8 Ball says 'Very doubtful'.

[JSWolf]

Originally Posted by geek1011

The tar can be compressed with anything supported. If you have a tgz, it must be named tar. If it doesn't have a driver.sh, it doesn't do anything.

Does driver.sh have to be different for each .tar?

[JSWolf]

Originally Posted by PeterT

Just wondering if it's possible to tell which version of RMSDK is being used in f/w 5.x ?

One way to tell if it's a newer RMSDK then is being used in 4.38 is to see if it supports small-caps. If it does, it's a newer RMSDK.

[JSWolf]

Originally Posted by rashkae

Hmm, it sounds like Kobo is going to open sideloaded epubs with their, what's it called, Access? Reader instead of RMSDK by default. That is... interesting.

That may be a bad idea as you need to be able to open ePub with RMSDK in case it has DRM.