Thread: K5 JBPatch
View Single Post
Old 07-09-2012, 01:51 AM   #258
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,903
Karma: 6677559
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Quote:
Originally Posted by aditya3098 View Post
Jbpatch 2 is... Awesome..
Just awesome
Thanks!

Quote:
Originally Posted by aditya3098 View Post
Okay, a little bug with the device info patch. I have every patch enabled, together they don't make 20 patches, yet the device info says "14/20"
That's not a bug, it's a feature

What the display actually tells is how many classes could theoretically be patched (20), and how many have actually been patched (14). It is normal for these numbers to both be higher than the number of patches (a single patch can change many classes), and to be less than the maximum (not all potential changes will be applied: the TTS patch can change 6 classes, but will at most change 2 of them at runtime). The number of applied patches can even change at runtime, because a patch only gets applied when its "target" class gets loaded. This is also (more or less) documented in the README.txt of version 1.3.1.
ixtab is offline   Reply With Quote