Hello, I'm back. I'm new in using LAMW and my only Android device is Intel 64-bit. After a full day of testing, here I want to share what I found. Hope it can be useful.
The demos under the Eclipse folder aren't compatible with Intel 64-bit using libhoudini. I opened many of the demos (under Eclipse) and followed jmpessoa instructions properly modifying build.xml and .lpi files based on my successfully new generated app settings (which run properly on my device). All of them can be compiled without error but when running on my device, it said "Unfortunately, [name] has stopped."
Even if I removed all the components on the main form and deleted all the other forms in the demos, I still get same the result. The remain is very basic TAndroidModule jForm class only without any components nor events. Simply to say, it's only a blank app. So it makes me think, there could be something generated by LAMW that causes incompatible with Intel+libhoudini. Because if I started a new app using LAMW, the apk works on my device. I mean, the demos were generated using prior version of LAMW than mine (version 0.6). Can anybody tell me, is there a way we can refresh the files generated by LAMW but keep the 'pure' Lazarus code unchanged?
libhoudini compatibility layer is not 100% compatible with ARM. So far I have tested jTextView, jButton, jImageView, jImageList and jTimer. All of them work correctly on Intel device although my compiler was set to Android-arm. But if the command jCanvasES2.Texture_Load_All is being executed, an error will occur immediately.
All the tests above were compiled using Android-arm setting, because I still have no luck building my Lazaurs to cross compile to Android-i386. When try to compile to Android-i386, I got this error message: "Fatal: Cannot find system used by fcllaz of package FCL." Any idea what should I do?