View Single Post
Old 08-15-2018, 04:23 PM   #2
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
To avoid actually entering the "USB Connected" state for testing, you might want to simply: trigger the popup, capture a screenshot, *close* the popup, then display the screenshot with fbink (fbink -g file=usb.png), this ensures that a tap on that "fake" connect button will at worst only open a book or enter the Library .


Because if you do want to really enter the "USB Connected" screen and still keep a shell session alive, that means USBNet, and you'll *have* to reboot your device after that, because trying to fake an unplug event will just crash the device when USBNet is enabled (... possibly with prejudice, on my H2O, it pretty much always wiped the stored WiFi passwords).


I do insist on the snapshot coming from FBGrab, to avoid any and all magical processing Nickel itself might do. The only exception to that rule *may* be for people on FW < 4.2, and even then, that's *in addition* to an FBGrab capture.

Last edited by NiLuJe; 08-15-2018 at 04:42 PM.
NiLuJe is offline   Reply With Quote