Hello TrueTom!
Thank you very much!
Fatal: Cannot find unit fphttpclient used by unit1 of the Project Inspector.Hello m4u_hoahoctro!
I think you can try do like this, please see the attachememts.
Thanks and best regards!
try
http1.HTTPMethod('GET','http://v3.mp3.zing.vn/download/vip/song/ZW6F97CU',stream1,code);
for i:=0 to http1.ResponseHeaders.Count-1 do
begin
s:=http1.ResponseHeaders.Strings[i];
...infomations about site's header can get by command ReponseHeaders ( as above ),
but I couldn't find anything same as it in list of commands of jhttpclient
In the NDK for Intel Architecture, use "APP_ABI := x86 " command line parameter. This generates the shared library under $PROJECT/libs/x86/ $NDK/ndk-build "APP_ABI := x86 "
Add target compile platform to it:
APP_ABI := x86
Use the command below to build the application binary with Intel compiler for x86 architecture:
$ ndk-build APP_ABI=x86 V=1 NDK_TOOLCHAIN=x86-icc NDK_APP.local.cleaned_binaries=true
1. Extract the apk and see if the file structure is correct. Under the unzipped directory, there is a "lib" folder and there should be 2 sub-folders(armeabi & x86) in "lib". Check if the files in those 2 sub folders correspond to the CPU structure.
Have you checked what `adb logcat` says? It's an essential debugging tool for Android.
There is only 1 folder under the lib folder: armeabi. And it contain 1 file: liblclapp.so.This is certainly your problem. Your app is not built for x86 android, only arm.
I can't use adb logcat. Because to test my apk file I have to run it directly on my phone.adb runs on both emulator and phone, run it on the phone (use -d instead of -e).
There is only 1 folder under the lib folder: armeabi. And it contain 1 file: liblclapp.so.This is certainly your problem. Your app is not built for x86 android, only arm.
I can't use adb logcat. Because to test my apk file I have to run it directly on my phone.adb runs on both emulator and phone, run it on the phone (use -d instead of -e).
Thanks jmpessoa. Actually I've already used the latest update of Laz4Android you mentioned (Laz4Android version 1.5-49903). The thing I didn't pay attention was the NDK version 10e (x86-4.9).
So I downloaded Android NDK r10e, unzipped it to C:\laztoapk\downloads\android-ndk-r10e and set my Library Path to:
C:\laztoapk\downloads\android-ndk-r10e\platforms\android-16\arch-x86\usr\lib
C:\laztoapk\downloads\android-ndk-r10e\toolchains\x86-4.9\prebuilt\windows\lib\gcc\i686-linux-android\4.9
Everything seemed okay so I saved the project file, rebuild the project and create the APK again. Unfortunately the result was the same.
Also, as chenyuchih and Leledumbo said, I should have an x86 folder under ..\lib inside the apk file. I don't know why I only get an armeabi folder. After some attempts, I found that if I rename the folder before the generation of apk file I will get the file under the folder "x86". Even now I can generate fat binaries, the code still can't run on my phone. It can be installed, but an error message "Unfortunately, Project1 has stopped." will show up if I run it.
1. Extract the apk and see if the file structure is correct. Under the unzipped directory, there is a "lib" folder and there should be 2 sub-folders(armeabi & x86) in "lib". Check if the files in those 2 sub folders correspond to the CPU structure.
2. Write a simplest "Hello World" test app to see whether it works. If it works, maybe there's something wrong in your code?
Library Path:
$(LazarusDir)\Android_NDK\platforms\android-9\arch-x86\usr\lib;
$(LazarusDir)\Android_NDK\toolchains\x86-4.8\prebuilt\windows\lib\gcc\i686-linux-android\4.8
and no Custom Options.
Maybe you missed my second library path.
I think it's not laz4android problems , laz4android is support android x86 compiled ok.
I think maybe when the Laztoapk build the APK file, it's not include x86 folder into the android APK file.
please try use the attachments(build_debug_apk_new.bat) to build the APK file.
did you look at the sourcecode of laztoapk?
You try to use laztoapk to build x86 android apps. This is not supported by laztoapk.
I would need to change things in laztoapk.
If you look at the code
http://sourceforge.net/p/laztoapk/svn/HEAD/tree/trunk/source/apkmanagermain.pas#l965
and search for "CopyNDKFilesToFPC" you will see that laztoapk copies only arm -stuff from the ndk folder into the laz4android folder.
Hello chenyuchih!
recent 3 laz4android versions is for "Android NDK: r10e" <<-----"e"
Yes, the NDK version I use is r10e. And I tried several different platforms (Android-8,12,19,21) but got the same result.(compile ok, run crash)
Compiling package FCL 1.0.1: Access violation
$00A9E160 TFPCMSGFILEPOOLITEM__GETMSG, line 1030 of etfpcmsgparser.pas
$00A9E881 ADDPATTERNITEM, line 1131 of etfpcmsgparser.pas
$00A9E809 TIDEFPCPARSER__INITREADING, line 1142 of etfpcmsgparser.pas
$006FA7C1 TEXTERNALTOOL__PROCESSRUNNING, line 376 of exttools.pas
$006FE6D1 TEXTERNALTOOLTHREAD__EXECUTE, line 1461 of exttools.pas
$0047E225
$00412D1E
$7683337A
$77269882
$77269855
, Errors: 11
Panic: internal error: Access violation
Panic: internal error: $00A9E160 TFPCMSGFILEPOOLITEM__GETMSG, line 1030 of etfpcmsgparser.pas
Panic: internal error: $00A9E881 ADDPATTERNITEM, line 1131 of etfpcmsgparser.pas
Panic: internal error: $00A9E809 TIDEFPCPARSER__INITREADING, line 1142 of etfpcmsgparser.pas
Panic: internal error: $006FA7C1 TEXTERNALTOOL__PROCESSRUNNING, line 376 of exttools.pas
Panic: internal error: $006FE6D1 TEXTERNALTOOLTHREAD__EXECUTE, line 1461 of exttools.pas
Panic: internal error: $0047E225
Panic: internal error: $00412D1E
Panic: internal error: $7683337A
Panic: internal error: $77269882
Panic: internal error: $77269855
Yes, the NDK version I use is r10e. And I tried several different platforms (Android-8,12,19,21) but got the same result.(compile ok, run crash)
Hello chenyuchih,
I had test your code ,and create a demo to test , it's run ok ,please see the attachments .
Thanks and best regards!
Hello TrueTom!
I installed the LAMW in the new release "laz4android1.4.4-FPC3.0.0RC2"
and build a new "Lamw GUI" project ...but when I tried to compile[build], I got the error:QuoteCompiling package FCL 1.0.1: Access violation
$00A9E160 TFPCMSGFILEPOOLITEM__GETMSG, line 1030 of etfpcmsgparser.pas
$00A9E881 ADDPATTERNITEM, line 1131 of etfpcmsgparser.pas
$00A9E809 TIDEFPCPARSER__INITREADING, line 1142 of etfpcmsgparser.pas
$006FA7C1 TEXTERNALTOOL__PROCESSRUNNING, line 376 of exttools.pas
$006FE6D1 TEXTERNALTOOLTHREAD__EXECUTE, line 1461 of exttools.pas
$0047E225
$00412D1E
$7683337A
$77269882
$77269855
, Errors: 11
Panic: internal error: Access violation
Panic: internal error: $00A9E160 TFPCMSGFILEPOOLITEM__GETMSG, line 1030 of etfpcmsgparser.pas
Panic: internal error: $00A9E881 ADDPATTERNITEM, line 1131 of etfpcmsgparser.pas
Panic: internal error: $00A9E809 TIDEFPCPARSER__INITREADING, line 1142 of etfpcmsgparser.pas
Panic: internal error: $006FA7C1 TEXTERNALTOOL__PROCESSRUNNING, line 376 of exttools.pas
Panic: internal error: $006FE6D1 TEXTERNALTOOLTHREAD__EXECUTE, line 1461 of exttools.pas
Panic: internal error: $0047E225
Panic: internal error: $00412D1E
Panic: internal error: $7683337A
Panic: internal error: $77269882
Panic: internal error: $77269855
Well, if I close and reopen again Lazarus everything is ok....
Note:
laz4android1.5-50093-FPC3.1.1 also had the same error/problem
laz4android1.5-49903-FPC3.1.1 ... works fine!
OKay, I found where the problem is. I use another computer(my laptop is too old to run modern Android) to run the simulator of Android 4.3.1(API 18, armeabi-v7a) and everything become so smooth. The previous test I did is with Android 2.3.3.(API10, armeabi)
But here comes another big question mark. Will the later FPC no longer support old Android version(2.X) or armeabi architecture? For my app, some users still hold a smartphone over 5 years!(such like moto defy) If those old versions will be unsupported, it really could be a big issue for me. Maybe temporarily I would still use the Laz4Android released in July, 2015.
Thanks truetom! I appreciate your kindly help. :)
Best Regards,
ChenYuChih
Compiling package FCL 1.0.1: Access violation
$00A9E160 TFPCMSGFILEPOOLITEM__GETMSG, line 1030 of etfpcmsgparser.pas
$00A9E881 ADDPATTERNITEM, line 1131 of etfpcmsgparser.pas
$00A9E809 TIDEFPCPARSER__INITREADING, line 1142 of etfpcmsgparser.pas
$006FA7C1 TEXTERNALTOOL__PROCESSRUNNING, line 376 of exttools.pas
$006FE6D1 TEXTERNALTOOLTHREAD__EXECUTE, line 1461 of exttools.pas
$0047E225
$00412D1E
$74D038F4
$77B35663
$77B3562E
, Errors: 11
Panic: internal error: Access violation
Panic: internal error: $00A9E160 TFPCMSGFILEPOOLITEM__GETMSG, line 1030 of etfpcmsgparser.pas
Panic: internal error: $00A9E881 ADDPATTERNITEM, line 1131 of etfpcmsgparser.pas
Panic: internal error: $00A9E809 TIDEFPCPARSER__INITREADING, line 1142 of etfpcmsgparser.pas
Panic: internal error: $006FA7C1 TEXTERNALTOOL__PROCESSRUNNING, line 376 of exttools.pas
Panic: internal error: $006FE6D1 TEXTERNALTOOLTHREAD__EXECUTE, line 1461 of exttools.pas
Panic: internal error: $0047E225
Panic: internal error: $00412D1E
Panic: internal error: $74D038F4
Panic: internal error: $77B35663
Panic: internal error: $77B3562E