View Single Post
Old 09-04-2022, 05:49 AM   #11
embryo
Fanatic
embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.
 
embryo's Avatar
 
Posts: 529
Karma: 64554
Join Date: Aug 2013
Device: Kobo Glo, GloHD
Quote:
Originally Posted by NiLuJe View Post
Nothing actually unmounts anything until you actively switch to the USBMS tool (and, even then, it'll do a bunch of more in-depth checks to avoid doing anything, to the best of the kernel's ability to actually report useful stuff (which is... subpar on Mk. < 7), if the host doesn't actually support data).
Just guessing.. I'll have to see the partition table and report back if I find a PC.
Quote:
As for the actual popups, again, we simply trust what the kernel tells us, they should only happen when connecting to a host w/ a data line, but it's an ntx kernel, so it's full of weird little bugs . (e.g., the PowerCover on the Sage is a great candidate for fucking things up on that front ).
So nothing can be fixed here..
Quote:
That said, you can inhibit how we react to those events by toggling the canToggleMassStorage Device cap to false (I imagine it's probably easily done in a user patch, now).
Is it something I can manually do (like editing a lua file or something? It could be a nice switch to have in the GUI ;p
Quote:
But IMHO it's a red herring . (I have, in fact, tested USBMS while connected to a CDP, and it's perfectly harmless, it just requires an unplug to exit). (e.g., it's either a coincidence and the SD card died at the same time, or your esoteric charging setup and/or a wonky cable fried something and/or facilitated killing the card.
I don't believe it's a coincidence. Also the card was not dead. Last year I flashed it back and worked OK for a year. I'll try to flash it again and see how things go. As for the charging setup, I've used it already with the reader and my phone many times, without anything else happening.
Quote:
Plus, you know, KSM ;p. (snark aside, assuming non-catastrophic hardware failure, KSM does prevent you from recovering from that sort of stuff as easily as the stock boot, because it breaks the factory reset capabilities)).
I can understand this about recovery, but my problem is what caused it in the first place..
As for reset, last year after many restarts, something ask me for one. I didn't do it, but I suppose it's still available..
Also a reset is almost the same as no reader, because no books, no reading..😀
embryo is offline   Reply With Quote