old shit, figured someone may be interested though if they're on older recoveries: https://gist.github.com/landr0id/f0ed787c5ca9beb1c06d
There is another XeX floating around that fixes the disconnect issue that results from changing the KV. IIRC it does not use static addresses, but what is different between that and this? Is this issue caused by something else?
No idea. I never looked into that as a possibility for the issue. I recall someone mentioning something about it though, I just never correlated the two since it only happened at a certain kernel revision. I created this method when I enabled extended logging and saw the error string in the screenshot being logged to Watson every time I got a disconnect. Never bothered tracing it back any further, but you could patch somewhere related (somewhere down the call stack or elsewhere that's actually exported) I guess to get the same affect.
