I don't see how publishing a research without disclosing specific details about the app itself or any kind of "crack" could stomp on motivation to develop something ... unless you trust in "security through obscurity" of course ... which was proven more than once to be a fail :)
good point although the post is just a simple PoC ... to fool the kind of behaviour you're talking about, one could simply install a signal handler, call the fake function, handle the sigsegv or whatever, and then use the function as data ... also, since ARM instrutions are 4 bytes each, you could play with 3 bytes declaration ... funny things happen ;)
author here ... it's not THAT easy, that specific piece of code was highly obfuscated by proguard ( you know the a.class, b.class, c.class thing? XD ) and everything made me think about the "correct" algorithm, still I can't find where that 0xFF... is being set :P
yeah I thought about physical sniffing and wanted to buy/build a bt sniffer myself ... but you know, some Android versions have a builtin bt sniffing feature ;)
I have a lawyer who can manage this thing, it's just not worth it. Regarding the grammar, English is not my native language (although this is not an excuse of course).