Quote:
Originally Posted by NiLuJe
Unfortunately, either there's no debug logging in the Journal stuff, or the logging level is reset by the updater, so, nothing new in the latest logs. It's even more cryptic without the books in fact... :/
If someone knows what these Journal*.jar are supposed to do, I'm all ears.
Basically, the update patches the two files (version tags) fine, then launch the Journal-update, which fails, which then makes the update revert the two patches and fail. :/
Not even sure if we could learn anything with a log of a successful update, but it's worth a shot. (Unfortunately, I don't have a K2 US :/. And don't have logs of my 2.5.3 update).
And, no, not sure how to avoid the autoupdate. (Well, leaving Whispernet off  ). Or using some of the nasty tricks laying around in some older posts to avoid the todo requests or stuff like that. Or maybe patching version/prettyversion to fake a 2.5.6... |
Thanks for trying to help, NiLuJe, and since it doesn't seem to be a critical update, I suppose for now I'll just choose the easiest option and leave Whispernet off. I guess I could always contact Amazon CS, but they'd probably want me to do a factory reset, and I don't feel like reloading all my books at this point - too lazy, lol!
