binary bitness mismatch?

[lapisxalpha]

Hi. Thanks for writing a very interesting app. In addition to its future ambitions, it makes editing android properties much more pleasant.

I was snooping around and may have noticed something you'd like to take notice of:

SNA:/data/data/com.android.shell/AxManager/bin $ uname -m
armv8l

SNA:/data/data/com.android.shell/AxManager/bin $ file /system/bin/toybox
/system/bin/toybox: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker), for Android 34, BuildID=1bc41aced62f0185216aab4e1e64a3a2, stripped

SNA:/data/data/com.android.shell/AxManager/bin $ file ./busybox
./busybox: ELF executable, 32-bit LSB arm, static, for Android 35, built by NDK r27b (12297006), BuildID=f7c2167886a0eb86009bb414f6883817ad3fa549, stripped

SNA:/data/data/com.android.shell/AxManager/bin $ file ./resetprop
./resetprop: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64), for Android 23, built by NDK r27-beta2 (11902837), BuildID=4cf7768c32f15bce141b5e44be9d787f24d79b55, stripped

IS "resetprop" SUPPOSED TO BE A 64BIT DYNAMIC ON MY MACHINE? BECAUSE /system/bin/linker64 DOESN'T EXIST HERE.

So, I've got a fully 64bit CPU and 64bit kernel but am saddled with a 32bit android userland due to manufacturer stupidity. I'm working on a project myself to deal with that particular issue and am always looking for interesting binaries, so I was being nosey and stumbled across that bit of info. I was really only looking to see if they were static or not. (If it had been static it would have run fine on my cpu and kernel despite the userland.)

Um, casper is very happy to finally have a neighbor in com.android.shell! AxManager might work well with my project, love to discuss it privately sometime if that can be arranged. Peace.