which NDK version you were using?

[StaringTheWorldAtMyRearView123]

Hi there, I have trouble compiling your sources, could you provide a more detailed guide please?

[goffioul]

It is designed to be compiled with AOSP, as an additional repo.

[StaringTheWorldAtMyRearView123]

as an additional repo? sir, sorry, I don't understand it at all.

[goffioul]

What I mean is that it isn't designed to be compiled as a standlone project. It is supposed to be integrated as part of the regular Android firmware compilation. If you don't know what I'm talking about, you can find more information at https://source.android.com/setup.

More specifically, this project has been designed to be integrated into android-x86 (which is a derivative of AOSP), see https://www.android-x86.org/

[StaringTheWorldAtMyRearView123]

Thank you gentleman, which android-x86 version I should integrate to.

[goffioul]

IIRC I used Android 9 at the time. For the record, although I could get something partly functional, the result was disappointingly slow. The JIT compiler of qemu (TCG) was just not on par with alternatives like ndk_emulation or houdini. It's also possible I did something wrong in my approach.

I'm not sure what is your goal, but if you've never compiled AOSP, or are not familiar with AOSP/QEMU internals, you might be entering a world of pain.

[StaringTheWorldAtMyRearView123]

My goal is to record every assembly instruction of my favor process. And yes, I did compiled AOSP but not expertize with QEMU. I know there're alternative choices like ndk_emulation / houdini, but they both closed source which mean it's not possible to achieve my goal at the moment.

[IamHuskar]

IIRC I used Android 9 at the time. For the record, although I could get something partly functional, the result was disappointingly slow. The JIT compiler of qemu (TCG) was just not on par with alternatives like ndk_emulation or houdini. It's also possible I did something wrong in my approach.

I'm not sure what is your goal, but if you've never compiled AOSP, or are not familiar with AOSP/QEMU internals, you might be entering a world of pain.

According to your replay in google groups .maybe it's Android 10

link1
link2

[IamHuskar]

and I try to build ax86-nb on q-x86 branch. too many build errors.

[IamHuskar]

My goal is to record every assembly instruction of my favor process. And yes, I did compiled AOSP but not expertize with QEMU. I know there're alternative choices like ndk_emulation / houdini, but they both closed source which mean it's not possible to achieve my goal at the moment.

兄弟你编译成功了吗？ 留个联系方式交流讨论一下？

[StaringTheWorldAtMyRearView123]

你不会是看雪论坛的huskar吧

[IamHuskar]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

[19245222]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

祝你顺利，这套方案不成熟，我钻研了4个月后放弃了。

[19245222]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

痛点就是太慢，你努力。

[IamHuskar]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

祝你顺利，这套方案不成熟，我钻研了4个月后放弃了。

1 你是否编译成功运行了？
如果编译成功运行了，对arm的支持如何，是只能跑简单的arm example还是复杂的arm so也可以？是否主要是性能问题。

[19245222]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

祝你顺利，这套方案不成熟，我钻研了4个月后放弃了。

1 你是否编译成功运行了？ 如果编译成功运行了，对arm的支持如何，是只能跑简单的arm example还是复杂的arm so也可以？是否主要是性能问题。

我没编译成功, 但脑里模拟执行了这套代码, 发现会太卡. 放弃了. 而且项目有很多Bug没做处理. 他不是用来Reverse Engineering的, 距离真正能实战的工具还要做很多 tuning (优化, 排错).

[cnRrex]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

你好，我也准备研究一下这个项目。请问可以分享一下编译好的文件吗，我想先简单地分析和测试一下。

[IamHuskar]

ID 太熟悉了吧。看样子得隐藏一下。我已经通过邮件和作者联系 编译成功了。但是暂时没有进行后续测试。现在没时间。

你好，我也准备研究一下这个项目。请问可以分享一下编译好的文件吗，我想先简单地分析和测试一下。

个人认为用qemu的这个翻译速度太慢了。可以看一下yuzu suyu
suyu
可以用这个框架改，但是二翻用suyu之类的会快一些。