View Single Post
Old 04-19-2020, 01:33 PM   #115
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,808
Karma: 7423683
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by davidfor View Post
Did you go to page 2 of the settings? The sleep cover option is at the end of the page, so on the small screen of the Mini, I would expect a second page.
In the event that this doesn't work, I can write a patch for it.

Quote:
I don't think so. Kobo stopped releasing updates for the Mini at about 3.14. They only release 3.19.5761-s when they officially dropped support for the Mini. Which was done when they removed support for older security protocols from their servers. It was released to allow the Mini to keep connecting to the store and download books.
The thing is, 3.19.5761-s is identical from what I looked at. As in, the checksums of the extracted files match... so... I don't know why they released it.

Quote:
I don't know why they stopped releasing updates for the Mini. The screen size and resolution probably makes some things difficult, but, it is probably something else. I don't think it was a popular device, so maybe there aren't many in use. My guess that the reason the recent firmware is still working on the Mini is because removing the support would actually be a reasonable amount of work. And I wouldn't be too surprised me the actual developers are keeping it working for their own purposes.
The developers do seem to be doing at least the minimum to keep it working (and they haven't removed it from the Device class, but to be fair, they haven't removed any device from there before). The other thing which keeps it working without much to do on Kobo's part is their brilliant (and confusing) three-layered codename system, which groups a cohort of similar devices (see https://www.mobileread.com/forums/sh...d.php?t=325471) by a single parent codename (which is used whenever possible in CSS selectors and is on). The only thing I don't understand about this system is why they group them with the same codename as one of the devices in the group (not even always the first one). It means that a lot of their code needs to check if it's the main one, and then check the next level of codenames, but with the fallback used to detect the main one (although this might to be to enforce a way make it easier to add new devices without having to redo all the sizes).
geek1011 is offline   Reply With Quote