View Single Post
Old 12-05-2023, 03:59 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,648
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Which of the patches did you enable and install? Please note the Metazoa patches are horrendously out of date now. The KoboPatch packages are what you should be using now. For firmware 4.38.21908, see the Instructions for patching firmware 4.38.21908 thread. Some of the Metazoa patches will break newer firmware in horrid fashion.

You might want to check if you have AutoUsbGadget=true set under [DeveloperSettings] in the Kobo eReader.conf file (found in the .kobo/Kobo directory in the root of the exposed storage. I use NickelMenu to toggle this setting depending on whether I want to see the Connect/Cancel popup.
Code:
[DeveloperSettings]
AutoUsbGadget=true
You may also want to restart your Kobo to ensure the on storage and in memory databases are synchronized. If you have the KoboUtilities plugin installed, I would suggest using the Check the device database under the Database options.

If this doesn't fix your issues, you may have to do a factory reset on your Libra 2.
DNSB is offline   Reply With Quote