Firmware 5.0.175773

[rantanplan]

Originally Posted by Gymnar

and Tolino is probably dying, with weltbild now ceasing operations.

That is a ridiculous statement, as Weltbild was a relatively small part of Tolino. I addition to that, Thalia is looking to buy a lot of Weltbild assets and may take over their ebook operations.

1/3 of Tolino is owned by Thalia alone. To be honest, I think that Thalia is playing the long game where they either buy smaller Tolino partner or just wait them out.

[Laen]

is there today for a vision color?

I mean in the Kobo ereader.con is
[DeveloperSettings]
EnableDebugServices=true

but nothing to see in the Menü

[rantanplan]

By the way, Thalia really did take over all of Weltbild ebook operations and as far as I understand they’ll migrate all Weltbild accounts.

[Laen]

ok i make a libra color out of my vision color through that manual
in Post 176
https://www.mobileread.com/forums/sh...&postcount=176


the one downside i see is no automatic Updates possible

[Laen]

Originally Posted by DNSB

Of course, not. Tolino ereaders have never used KoboRoot.tgz and the current v5.0 code is for installing on Tolinos. Copy update.zip to the root directory is the Tolino equivalent of copy KoboRoot.tgz to the .kobo directory.



That's hardly the list of items breaking that I asked for. You did say that "it breaks too many things" and I asked for a list of those things.

I would suggest that you either supply your list of multiple items that break or be quiet on the topic until you have something useful to share with the community.

not full correct. the update file 4.XX to 5.1.184318 des vision color has the Koboroot.tgz in it.

as a late hint

[Laen]

doppelpost

[Laen]

So i test on my Shine 5 the Firmwares.it seems that Firmware 5.0.175773 was the Last mit Development Mode through Devmodeon.
On 5.1.184318 und 5.2.190625 no Devmode Visible through the command

[Redundantant]

I just registered to share a thought I had. I may overlook something or I'm plain dumb, but please bear with me.
My Tolino Shine 4 just died and I was looking into a replacement, which might be the Clara BW or the Shine 5. So...

Since it looks like firmwares unify to some extent and I recall reading that older devices might follow, could the Shine 4 become a better performer than the aforementioned two?


Assuming it DOES get the same firmware base, it does have:
- a 1.8 GHz quad core processor
- 1 GB of RAM
...which on paper is superior to the Shine 5/Clara BW oddly enough.
(Of course the updates are late if at all coming, and there's Carta 1300 on the newer models, but still.)

Am I mistaken?
Of course this would only apply IF it ends up on the same base.


(Since my Shine 4 is still under warranty, I could get it replaced by another Shine 4 or pay just a couple of Euros to "upgrade", so I'm wondering if there's any merit to stay with the Shine 4 or I am grasping at straws.)

[Laen]

Originally Posted by Redundantant

I just registered to share a thought I had. I may overlook something or I'm plain dumb, but please bear with me.
My Tolino Shine 4 just died and I was looking into a replacement, which might be the Clara BW or the Shine 5. So...

Since it looks like firmwares unify to some extent and I recall reading that older devices might follow, could the Shine 4 become a better performer than the aforementioned two?


Assuming it DOES get the same firmware base, it does have:
- a 1.8 GHz quad core processor
- 1 GB of RAM
...which on paper is superior to the Shine 5/Clara BW oddly enough.
(Of course the updates are late if at all coming, and there's Carta 1300 on the newer models, but still.)

Am I mistaken?
Of course this would only apply IF it ends up on the same base.


(Since my Shine 4 is still under warranty, I could get it replaced by another Shine 4 or pay just a couple of Euros to "upgrade", so I'm wondering if there's any merit to stay with the Shine 4 or I am grasping at straws.)

Shine 5 and Clara BW have the Same Hardware but only a bit other Firmware.
Both based on the Kobo Linux Firmware.
But the Clara on 4.40XX and the shine 5 on 5.2XXX (on factory 4.39 ) .
The 5.0.175773 the Shine 5 can be switched between Kobo and Tolino.
If and When Kobo gets the 5.x Firmware is unclear and if its the same 5.x like on the Tolino ist unclear too.
I dont see a clear difference on a tolino with Kobo firmware to a kobo direct

[Redundantant]

Originally Posted by Laen

Shine 5 and Clara BW have the Same Hardware but only a bit other Firmware.
Both based on the Kobo Linux Firmware.
[...]
If and When Kobo gets the 5.x Firmware is unclear and if its the same 5.x like on the Tolino ist unclear too.
I dont see a clear difference on a tolino with Kobo firmware to a kobo direct

Thanks for confirming, that's most of what I have gathered (and just assumed tbf) as well.

The Shine 5 is 15-20% cheaper here, but I'm still contemplating getting a Clara to be safe firmware-wise. I can't imagine Kobo would be okay with people buying the cheaper reader and just needing to flip the brand switch (assuming a market where both are offered). And it's a potential prevention mechanism that I'm afraid of (if it's not already there; I recall reading posts about missing this switch already[?]).


Regarding my Shine 4 off-topic:
I don't really think this gets some of the unified base. It's probably cheaper to deliver some security patches to Android than to fit a new system to it. If it did, however, it could become a better performer than its siblings. There are more arguments to be made, but I'm already no longer on topic. Maybe some research and a separate thread in the Tolino section worth.

[Laen]

Originally Posted by Redundantant

Thanks for confirming, that's most of what I have gathered (and just assumed tbf) as well.

The Shine 5 is 15-20% cheaper here, but I'm still contemplating getting a Clara to be safe firmware-wise. I can't imagine Kobo would be okay with people buying the cheaper reader and just needing to flip the brand switch (assuming a market where both are offered). And it's a potential prevention mechanism that I'm afraid of (if it's not already there; I recall reading posts about missing this switch already[?]).


Regarding my Shine 4 off-topic:
I don't really think this gets some of the unified base. It's probably cheaper to deliver some security patches to Android than to fit a new system to it. If it did, however, it could become a better performer than its siblings. There are more arguments to be made, but I'm already no longer on topic. Maybe some research and a separate thread in the Tolino section worth.

I think Kobo will switch to V5 in the Near time and then have the switch too.

But the problem ist that on 5.2.190625 and 5.1.186250 you cant access the needed Development menü.
I think they block it with reasons.

But you can downgrade the firmware to the correct on.


But some people prefer the android version over the Kobo. but i prefer the kobo firmware

[Redundantant]

Originally Posted by Laen

But the problem ist that on 5.2.190625 and 5.1.186250 you cant access the needed Development menü.
I think they block it with reasons.
[...]
But some people prefer the android version over the Kobo. but i prefer the kobo firmware

Oh, right, that was it. At least there's always a way.

Regarding Android, that couldn't be me. I even looked into cross-flashing Kobo's OS onto the Shine 4, but I think the SoC just wouldn't have been supported. For me Android is just too power hungry, runs too slow and apps need to be as lean as possible, let alone being usable without outdated, hacky on-screen buttons. And even then I'd spend most of my time on KOReader.

I'll closely follow this thread as well as the updates. I hope this becomes a nice, stable, snappy and feature complete system.

[phantom001]

Here another one with a Tolinio Vison Color so Kobo 5.0 Firmware …

If the actual kobo devices will get 5.? isnt clear but any new devices im sure will do.

The main reason for 5 is the possibility for customer device branding or better switch between device brandings.
So have a little other look and a other shop based on the customers wishes the core system i am shure is the same.
If the next bookshop want another branding lets say BookshopA you can Change the branding between Kobo/Tolino/BookshopA
In the core i believe its the same system.

The bad thing with this they changed the update procedure and its unclear how or if software sideloads will work in the future.

I have noticed the new updates provide everytime a full system image and the install routine is driven by the driver.sh script.

If they realy need everytime a full system image it would be a horror because it would make software sideloads nearly impossible because erverytime you have to provide a full modified system so no more multi sideloads.

But the good thing i dont think its the case because the guys from koreader already work on V5 support.
(https://github.com/koreader/koreader/pull/12401)

Hope that Kfmon and NickelMenu and follow soon :-)

If i can help in anyway let me know ...

[Falkor]

Originally Posted by DNSB

At this time, it appears that the default renderer on Tolino's v5 software is very similar to the WebKit based renderer on a Kobo. Just BTW, the renderer that Kobo originally used for ePub3 was ACCESS (all caps) which was replaced by the WebKit based renderer.

As for RMSDK doing better ePub3? Looking at the latest test results I can find, quite a few of the tests show that neither ADE nor RMSDK are doing all that well. I have to admit that Adobe pushing epubtest.org on their website is a bit of a laugh.



Personally, I prefer RMSDK for it's font handling but very few of the people I know who use ereaders are likely to notice which renderer is being used.

Does the webkit based renderer on Kobo suffer from the same issues as the Shine 5's default renderer?

The letter spacing is way too narrow: https://www.mobileread.com/forums/sh...28#post4471428

I only use RMSDK because I find it makes texts much easier to read with its wider letter spacing.

Also, font weight adjustment, embedded fonts, page breaks, orphans and widows don't work in the default renderer. I often have to switch between fonts a couple of times before sideloaded fonts work. Switching between text alignment settings can be tricky as well: Sometimes I have to close and re-open the book to see the effect. And the last couple of lines of a chapter sometimes get lost.

Originally Posted by user105

which is funny because i am still set to rmsdk as epub engine and cannot switch back. i am worried to factory reset this device because without switching engines, i cannot open books in an acceptable way.

You're still on RMSDK because it's set in the Kobo eReader.conf file.
Change "EpubSideloadedRenderer=RMSDK" to "EpubSideloadedRenderer=default" to go back to the default renderer.

[Sirtel]

Font weight adjustment works in the Kobo kepub renderer. Embedded fonts work with a patch. Orphans and widows don't work, which is a plus in my view (I set them to 1 for RMSDK, to avoid large gaps at the bottom of the page). Haven't seen the last lines issue, and as for page breaks, the best way to do those is separate html files, then they work correctly. I edit my ebooks and split the files if needed. I set the text alignment in the css too.