Firmware 4.31.19086

[sherman]

Originally Posted by Deobulakenyo

I use it for nanoclock. Though when i tested it, i have not installed nanoclock and/or nickelmenu yet

I am not sure if nickelmenu needs it.

No, NickelMenu does not need it.

[Deobulakenyo]

Originally Posted by sherman

No, NickelMenu does not need it.

Thanks. will try to patch without that one, and see.

Thanks


Edit/Update:

So i factory reset again, and everything is fine. after syncing new update 4.31 is now found, so i decided, i will try that since it is available already. Updated to 4.31 via wifi. Libra 2 rebooted to update but got stuck in 3 cycling dots. gave it some time but nah. it hanged. I pressed power button to turn off console. Then power button again to boot. it booted fine in the new fw 4.31. Tested charging while sleeping (setting turned on), and now after 3 led blinks, led light turns off (but charging is fine but no led light). I have no patch at this time. nothing. just ofw.

and once again the 1A charging brick i had does not charge my Libra 2 in fw 4.31.

and Rebooting hangs on the rebooting 3 cycling dots.

Gonna go back to 4.30

Edit/update: Got back to 4.30 after factory resetting. And... led light behaves buggy again. Two leds flash and gone

[choc96]

I also am still having issues with turning the Libra 2 on after being upgraded to firmware 4.31.19086. It updated successfully to latest update 4.31 via sync. However it still gets stuck on the dots as it turns on after being off. To temporary fix the problem I've changed my setting to never power off. I still want to access the sync feature to borrow library books you see. It will just continue to update again if I downgrade.

[Deobulakenyo]

Originally Posted by choc96

I also am still having issues with turning the Libra 2 on after being upgraded to firmware 4.31.19086. It updated successfully to latest update 4.31 via sync. However it still gets stuck on the dots as it turns on after being off. To temporary fix the problem I've changed my setting to never power off. I still want to access the sync feature to borrow library books you see. It will just continue to update again if I downgrade.

fw is buggy.

i reverted back to fw 4.30 and the led light while sleeping is okay... until i sync and downloaded the dictionaries.

I do not know how the dictionaries would affect the charging led light when sleeping but it does hahahaha.

Anyway, i have a qusetion, why is the annotations in .txt format appearing in my books? is this really the way it is or i noticed this only now when i restored my books on the device after factory reset?

[choc96]

Originally Posted by Deobulakenyo

Anyway, i have a qusetion, why is the annotations in .txt format appearing in my books? is this really the way it is or i noticed this only now when i restored my books on the device after factory reset?

Usually annotations are stored as .annot in a directory titled Digital Editions and in the database KoboReader.sqlite (in .kobo). The only reason I can think of is if you've clicked 'Export Annotations' which exports the selected book's annotations as a text file.

[davidfor]

Originally Posted by Deobulakenyo

Anyway, i have a qusetion, why is the annotations in .txt format appearing in my books? is this really the way it is or i noticed this only now when i restored my books on the device after factory reset?

The annotations are stored in the database. But, if you use the export, it will create a text file with the annotations in them on the device. The next time the device looks for new books, it will probably find the annotations text files and add them as books.

[avm]

Originally Posted by geek1011

Since this is disruptive, I'll try and make time to get a fix out tonight.

is there a fix for the bug that highlighting will trigger a popup "NickelMenu Could not find the required SelectionMenuView and SelectionMneuController symbols for adding selection menu items (this is a bug)"?

That would be wonderful! Thanks for all the great work.

Best,

Anne

[JSWolf]

Originally Posted by avm

is there a fix for the bug that highlighting will trigger a popup "NickelMenu Could not find the required SelectionMenuView and SelectionMneuController symbols for adding selection menu items (this is a bug)"?

That would be wonderful! Thanks for all the great work.

Best,

Anne

Yes, it has been fixed. Check the NickelMenu thread.
https://www.mobileread.com/forums/sh...d.php?t=329525

[Calenorn]

I have two Claras and a Libra H2O. All unpatched but with side-loaded additional fonts.

Updated the firmware on them all; fonts are all working properly.

No problemo.

[Deobulakenyo]

Originally Posted by Calenorn

I have two Claras and a Libra H2O. All unpatched but with side-loaded additional fonts.

Updated the firmware on them all; fonts are all working properly.

No problemo.

On epubs or kepubs?

[Calenorn]

Originally Posted by Deobulakenyo

On epubs or kepubs?

Epubs

[NiLuJe]

Originally Posted by Deobulakenyo

I use it for nanoclock.

NanoClock doesn't require this, FWIW. MiniClock did (assuming you wanted to handle physical page turn buttons).

[mathil]

Has anybody experienced occasionally freezing with the latest update? I wasn't doing anything special to make that happen either - once I was reading normally and then the page wouldn't turn; another time it hung up inside the My Books menu; both times I hadn't interacted with the device for a short amount of time (no more than 1 minute, or the time it takes to read a page). Holding the power button to turn it off worked, but the screen didn't refresh until I turned the reader back up again.

I have a Libra 2 with patches installed. I also ran a database check with the KoboUtilities plugin and it went well (the reader also doesn't have any other issue that is usually related to corrupted database).

[Deobulakenyo]

Originally Posted by mathil

Has anybody experienced occasionally freezing with the latest update? I wasn't doing anything special to make that happen either - once I was reading normally and then the page wouldn't turn; another time it hung up inside the My Books menu; both times I hadn't interacted with the device for a short amount of time (no more than 1 minute, or the time it takes to read a page). Holding the power button to turn it off worked, but the screen didn't refresh until I turned the reader back up again.

I have a Libra 2 with patches installed. I also ran a database check with the KoboUtilities plugin and it went well (the reader also doesn't have any other issue that is usually related to corrupted database).

Three of my fellow members in a Kobo group on fb here in the Philippines got stuck in a loopin booting sequence immediately after the update. This firmware is so buggy. Wehn i was in in 4.31, i had to spend more than 30 minutes in a looping boot before it eventually reached the homescreen.

I factory reset and now in 4.30.

[JSWolf]

Originally Posted by Deobulakenyo

Three of my fellow members in a Kobo group on fb here in the Philippines got stuck in a loopin booting sequence immediately after the update. This firmware is so buggy. Wehn i was in in 4.31, i had to spend more than 30 minutes in a looping boot before it eventually reached the homescreen.

I factory reset and now in 4.30.

You did not have to factory reset to go back to 4.30.