Install problem on Galaxy S5 Neo

02-04-2016, 12:50 AM #1

Hi everyone. I know this probably will sound like the n-th identical question but: i can't install dolphin on my S5 Neo. I have read the FAQ, but i can't find the problem: i have an Exynos SoC 64-bit able with a Mali720 cpu ES3 capable. The problem may lie in the OS build: i am currently running a 5.1.1 build, BUT, after countless different tries, i can't figure out a way to discern wether i am on a 32 or 64 bit OS build. Does anyone know a way to check this on an unrooted device?

YellowDart · 02-04-2016, 01:00 AM #2

(02-04-2016, 12:50 AM)SilverBeam Wrote: Hi everyone. I know this probably will sound like the n-th identical question but: i can't install dolphin on my S5 Neo. I have read the FAQ, but i can't find the problem: i have an Exynos SoC 64-bit able with a Mali720 cpu ES3 capable. The problem may lie in the OS build: i am currently running a 5.1.1 build, BUT, after countless different tries, i can't figure out a way to discern wether i am on a 32 or 64 bit OS build. Does anyone know a way to check this on an unrooted device?

Try running the app CPU-Z from the Play Store. Under the System tab, see if it says your kernel architecture is "armv8l". If it says armv7 instead, that means you're running 32-bit.

Note, I'm not actually sure yet if this is a reliable way to tell whether or not your OS is 32-bit. That is, it could say armv8 on a phone that's not running a 64-bit userspace; but this is probably the quickest way to rule it out if it doesn't say that.

Note also that the app will fail to install even on a compatible phone if you have the play store version installed. So if it does say armv8, try uninstalling the play store version, and then trying the dev build again.

02-04-2016, 01:06 AM #3

Aarch64, so....

YellowDart · 02-04-2016, 01:14 AM #4

Yeah, I'm not sure what to say then. The Android platform is what's rejecting the application though; it's not some check the application does to determine whether or not it likes you.

There are more in-depth steps that can be taken to examine the device to determine the cause of the rejection, but I'm not smart enough to know what those are. You'll probably want to grab the Android SDK though, as that will likely be required to dig up this information.

02-04-2016, 01:35 AM #5

Ok, but all the more in-depth solutions involved the use of the android terminal, which requires root to run )':
P.S. is there a link where i can download a 32 but version to do a testrun? I know that 64bit support started in may, so maybe something of april idk

02-04-2016, 01:42 AM #6

Nevermind. I finally made something work and it seems that i have an armv7abi. I cry.

YellowDart · 02-04-2016, 01:43 AM #7

The 32-bit version of the app stopped being *built* around May 2015, but you'll have to go all the way back to Octoberish of 2014 to find a build that will work. That's not going to be a very representative experience.