View Single Post
Old 04-21-2022, 02:58 PM   #191
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,507
Karma: 26047224
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Flip those two keys to true in your config, do stuff (ideally stuff that breaks ^^), then connect the device to your computer again to get me the .adds/nanoclock/nanoclock.log file .

EDIT: Reading the description (I, err, don't remember the code. This was added as a last resort hack, it's not bullet proof nor particularly well thought out ), you might actually need to do this in *three* steps: flip both settings in the config; eject; do stuff; flip the debug switch *only* in the config; eject; plug again to get updated log.

If possible, the NickelMenu approach described above or in the other thread might be slightly less cumbersome (because, yeah, the stock devmode approach mentioned earlier is no longer viable).

Last edited by NiLuJe; 04-21-2022 at 03:04 PM.
NiLuJe is offline   Reply With Quote