Cortex A53 but 32bit ABI? (Samsung Galaxy Grand Prime SM-G530FZ)

[Ben]

I purchased a Samsung Galaxy Grand Prime SM-G530FZ for testing the arm64-v8a version of a library.

However, the armeabi version seems to be installed. I have verified that the apt contains armeabi, armeabi-v7a, arm64-v8a

getprop on the device gives me the following:

[ro.product.cpu.abi2]: [armeabi]

[ro.product.cpu.abi]: [armeabi-v7a]

The Cortex A53 supports 32bit and 64bit operation. 

Is there any way I can make the device run the 64-bit version?

Thank you!

[Philippe Simons]

Nope, if the device reports armeabi and armeabi-v7a, you can't run 64bit code. Nothing to do about that.

BTW: It's not because the CPU support 64bit code, that the manufacturer (Samsung) will enable and compile a ROM to enable 64bit.

It's like running a modern desktop CPU on a 32bit OS. Even if the CPU can run 64bit code, the OS won't allows it.

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ndk...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-ndk.
For more options, visit https://groups.google.com/d/optout.

[Ben]

Thank you for the reply. That is what I was afraid of.

Is there any hope for a future OS update, or an alternate OS distribution?

[ands...@gmail.com]

I purchased an ASUS ZenFone 2 ZE550ML with an Intel quad core Z3560 64-bit processor to be able to test my x86_64 build. Guess what? It only loads the x86 version of my library (I hope I'm doing something wrong).

When trying to force load the x86_64 version of my JNI library this error is displayed:

dlopen("/data/app/com.mycompany.myapp/lib/x86/libjni-x86_64.so", RTLD_LAZY) failed: dlopen failed: "/data/app/com.mycompany.myapp/lib/x86/libjni-x86_64.so" is 64-bit instead of 32-bit. This must mean it can only use 32-bit libraries.

So although the device has a 64-bit processor, ASUS hasn't made it possible to run in true 64-bit mode. This is the same problem as with the Samsung Galaxy Grand Prime SM-G530FZ. I guess I was lucky when I purchased my Nexus 9 device, it has an ARM 64-bit processor and loads my arm64-v8a library fine.

How can we make sure (before we purchase it) that an Android 64-bit device really runs in 64-bit mode and not only in 32-bit mode?

Does anyone know about a “true” Intel x86_64 Android device?

[ands...@gmail.com]

Den torsdag 16 april 2015 kl. 02:46:13 UTC+2 skrev Ben:

I purchased an ASUS ZenFone 2 ZE550ML with a quad core Intel 64-bit processor to be able to test my x86_64 build. Guess what? It only loads the x86 version of my library (I hope I'm doing something wrong).

When trying to force load the x86_64 version of my JNI lib this error is displayed:

dlopen("/data/app/com.mycompany.myapp/lib/x86/libjni-x86_64.so", RTLD_LAZY) failed: dlopen failed: "/data/app/com.mycompany.myapp/lib/x86/libjni-x86_64.so" is 64-bit instead of 32-bit.

So although the device has a 64-bit processor, ASUS hasn't made it possible to run in true 64-bit mode. Of course ASUS doesn't tell a customer that this is the case, same as with the Samsung Galaxy Grand Prime SM-G530FZ. Guess I was lucky when I purchased my Nexus 9 device, it has a ARM 64-bit processor and loads my arm64-v8a fine.

[f34nc015]

Hi, I would need recommandation too, for a device with intel which runs in 64 bit mode
Thanks for nay kind of help
f

 

[jsw...@arxan.com]

Don't bother with the Nokia N1. My company purchased one hoping we could get an x86_64 userspace device. The device has a 64-bit kernel (unlike our Dell Venue 8340 which has a 64-bit Atom proc but 32-bit kernel) but still a 32-bit userspace. Disappointing.

Cheers,

Jevin

[mike digioia]

Submit me

  agentInfoReply.rtf

  Shorter2ResumeEmbeddedUpton46n.doc

--