Support of API < 19

Question

Support of API < 19

skvav opened this issue 9 years ago · 5 comments

Is this constraint critical? It would be great to use library with API >= 9.
I tried to override minSdkVersion, but on API 9 my app crashes with error "Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1311]: 798 cannot locate ' log2'..." that seemed to be fixed in your fork of WebView ericwlange/webkit@9c5abf1, but maybe it's wasn't included in version 2.0.

Answer 1 · 2016-01-15T02:33:59.000Z

I compiled with API 19. I had attempted to build with API 16 because I wanted to test on a MIPS configuration I had in the emulator, but for some reason, although it built, it would not run. I didn't spend any more time on it and reverted back to API 19. Feel free to try and build with a lower API. You can achieve that by editing the following dictionary in scripts/build:

ANDROID_APIS = {
    'armeabi'     : '19',
    'armeabi-v7a' : '19',
    'arm64-v8a'   : '21',
    'x86'         : '19',
    'x86_64'      : '21',
    'mips'        : '19',
    'mips64'      : '21'
}

Change it to whichever API you want.

You will then need to change minSdkVersion in AndroidJSCore/build.gradle to whatever you've changed it to. Then run the build script.

Let me know how it goes. If it works for lower APIs, I will put it in the next release. At the moment, I am working on trying to get the 64-bit architectures to work, and JIT on ARM. Those are my goals for version 2.1. Will include the lower API if it works.

Answer 2 · 2016-01-15T05:22:13.000Z

Here is my test on android(4.0,4.1 4.2 4.3). Only 26.83% passed.
the main reason is because of log2....
so I use another one android-jsc
on my test ,84% passed.

My partner found the project have some problem because of Memory leak。
He have resolved。but he does not know how to contact with you .

Answer 3 · 2016-01-15T09:06:48.000Z

This is great. I can be contacted in any number of ways. If you want to email me, please send to eric at flicket dot tv. Otherwise you can raise a pull request. Would love to see what memory leaks have been uncovered!

Answer 4 · 2016-01-25T05:45:33.000Z

The head version now works with API 16+ (min Jellybean). At the moment, I don't have any plans to go back further because older APIs use an older version of the standard template libraries, but JavaScriptCore requires a newer version. According to Google, API 16+ should cover 94% of devices in the wild. When I release 2.1, this support will be there. Should be in the next couple of days. But in the interim, you can build from source.

Answer 5 · 2016-01-27T17:53:45.000Z

This issue is now fixed in 2.1. API 16+ is now supported. As noted above, I don't plan to add support pre- API 16, as it would require a much older build of webkit, and it is not worth it for the 6% of devices that still require it.