cryptax

Ok this works fine! You need both `e asm.emu=true` and `aae`. May I ask why? Why do we have to "emulate assembly"? A slightly strange this also is that `pd...

@krnick thanks for looking into it. Using call graphs like this is unfortunately going to miss cases where an interface is used, which is the case with `Threads`/`Runnable`. In your...

To enhance Quark at finding better "who calls who", perhaps you could add a specific case for the `run()` methods of `Thread` or `Runnable`. In that case, the "caller" is...

@krnick for this one we had a trick that might help: in the call tree analysis, replace any `Thread.start()` by `Thread.run()`, and this should automatically fix the call tree :)...

Not sure to understand your answers. Am I getting this right: @haeter525 says we are not getting 100% because Quark currently only implements tainted analysis for registers and the string...

that's quite strange, I can't reproduce it. What OS do you have? Do you really have a valid smali.conf file?

mmmm

I use `androaxml.py` from androguard package. I use it when APKTool fails. It does not happen very often, but I encountered the case a few times.

Yes, you are right, there are many improvements that should be made to the x86 support. Actually, part of the docker images are now outdated... and I usually find it...

yes, only on recent versions (Android 11 if I am correct).