View Single Post
Old 11-04-2016, 01:42 PM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ecostin View Post
Yes, using the booklet version. Did everything from scratch today, went to factory / initial, then jb, then to the latest firmware version. Afterwards all packages were installed cleanly via MRPI. No issues except for the reported one.
NiLuJe has it in one of his public repositories, if any 'java guru' wants to take a look at it.
We can't just diff the classes, because every build has different obfuscation.

It seems strange that something as basic as DCbooklet would change with only a x.x.x.0.1 change of version number, but maybe . . . .
(That is the foundation class of all "Device Control Booklets" - Including the home page.)

My KT3 (also an 8th. gen device) is running 5.8.5 -
I could update it and see if I can duplicate the problem, but NiLuJe will probably graduate before I have time to do that.

So it would be best if someone running 5.8.5.0.1 on an 8th gen device see if they can duplicate the problem described.

Last edited by knc1; 11-04-2016 at 01:46 PM.
knc1 is offline   Reply With Quote