On Sep 28, 2012, at 10:07 AM, "Steve Sharrock" <[email protected]> wrote:
> I wasn't quite sure if you meant change to this...
>
> <AndroidSupportedAbis>armeabi-v7a,armeabi</AndroidSupportedAbis>
This is Fix #2, which ensures that the armeabi-v7a libmonodroid.so is added to
the .apk before the armeabi libmonodroid.so, allowing the .apk to be properly
installed on Android 4.0-4.0.3. Note that if your app includes any other native
libraries, you may need to reorder the <AndroidNativeLibrary/> elements in your
.csproj so that the armeabi-v7a libraries are listed before armeabi libraries.
> Or change to this:
>
> <AndroidSupportedAbis>armeabi-v7a</AndroidSupportedAbis>
This is Fix #1: drop support for everything older than ARMv7.
Whether this is appropriate or not depends on whether you need to continue to
support ARMv5 devices. Unfortunately, there's no good information on how many
current Android devices can't run ARMv7 binaries; it seems that there a "quite
a few" which are ARMv5/ARMv6, not ARMv7:
https://bugzilla.xamarin.com/show_bug.cgi?id=7013#c14
> Also, while this change doesn't seem to have any adverse effects on my newer
> test tablets and phones, will this change present any issues with current
> users getting our updated code; but, still running on much older phones?
Depends on whether those "much older phones" can run ARMv7 binaries. If they
can't, then you need Fix #2. If they can (and you don't mind losing support for
older devices that only support ARMv5/ARMv6), then you can use Fix #1.
If you have an older phone handy, you can see if it'll support ARMv7 binaries
by running:
adb shell getprop ro.product.cpu.abi
If it prints "armeabi-v7a", it'll run ARMv7 binaries. If it prints "armeabi",
it won't run ARMv7 binaries.
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
