Closed NiLuJe closed 5 years ago
i.e., my final log entry is
May 2 19:13:50 UNCaGED: Nothing more to do? (KU: 255; BS: 61)
Good morning NiLuJe,
Hopefully I'll have a chance to get KU installed on my Kobo this morning and do some debugging. Now that the scripts are sorted out, that should make debugging things a lot easier.
I've merged the changes. We can change the above comment at a later date.
Yeah, making that bypassable sounds good, and/or forgetting about it for now ;).
This was mainly because I think this has the greatest potential for screwing things up, and the only crash I ever got was during a run while plugged in ;).
But, yeah, definitely agree that it might not make much sense for now.
I definitely think it's a good idea to have, because you're right, being attached to the PC would be the biggest danger of this whole mess...
Edit: Moved to #3
I'd somehow forgotten about the final block ;).
I'm still not getting it to actually connect to Calibre, but I now have more info:
When I mentioned that it hanged during the "Running Kobo-UNCaGED" step, I actually failed to notice that it's actually chugging along at 100% CPU, so I assume it's doing... something ;).
Then it finally prints "Connecting to Calibre", but doesn't actually connect, and it then fairly quickly returns -1
The second hang is then FBInk waiting for a processing pass that never happens, until it finally exits w/ ENODATA