What to replace `arm-linux-androideabi` with in manifest?

[OptimisticPeach]

I'm trying to get a project to compile that previously (About 6 months ago) compiled, I get the following error when I try to compile it as is:

error: unknown variant `arm-linux-androideabi`, expected one of `armv7-linux-androideabi`, `aarch64-linux-android`, `i686-linux-android`, `x86_64-linux-android` for key `package.metadata.android.build_targets` at line 51 column 1

So, I try armv7-linux-androideabi, which successfully compiles and installs through adb, but fails to launch. I'm trying to run this on a Pixel 2, where I used to use arm-linux-androideabi, cpu-z reports the kernel arch is aarch64 (Which apparently doesn't work) and the closest I could find was armv7-linux-androideabi (Which doesn't work either).

In PR #223 I read the following:

• The default and supported build targets has changed. The default is to build on all targets supported by the current NDK. arm-linux-androideabi was removed. See README for supported targets.

How might I go about making my app compile and run on my Pixel 2?

On a side note, I used to clone cargo-apk locally and edit the NativeActivity code to remove the decoration and navigation bars (It's kind of difficult to play snake with them), where might I inject that code now? "Injected"/"replaced" code is here.

[OptimisticPeach]

Here is the adb logcat dump of compiling a "default" project with this (The only different thing about the default manifest is that I've changed the name and don't ask for the camera)

[philip-alldredge]

The appropriate ABI is "aarch64-linux-android". What do you mean when you say it doesn't work? Does it fail to build or fail to run? Is there an error?

The fullscreen option in your cargo manifest will set the theme so that the status bar will be removed. However, the navigation bars will still be there. I'm not sure of a way to hide the navigation bars at the moment. Long term there should be an API provided.

There may be a way to call the appropriate functions using JNI and include them in the rust portion in android_native_app_glue.c but I don't have experience in that area.

[philip-alldredge]

What NDK and SDK are you using? I don't have a pixel 2 but I haven't had any problems running the examples on the emulator, ARM7, or ARM64 devices. Any warnings or errors when building?

[OptimisticPeach]

What do you mean when you say it doesn't work? Does it fail to build or fail to run? Is there an
error?

It fails to run, with the logcat errors produced. It will try to "flash open" expanding from the app icon, and then it will simply go back to the home screen (Or the app drawer).

There may be a way to call the appropriate functions using JNI and include them in the rust portion in android_native_app_glue.c but I don't have experience in that area.

I tried that some time ago, when originally making the app, but I found that it is illegal to call said functions in the native activity thread, therefore forcing me to run them in the NativeActivity code, which runs in the main thread.

What NDK and SDK are you using?

PS P:\sdk\tools\bin> .\sdkmanager.bat --list
Installed packages:
  Path                                                | Version      | Description                                     | Location
  -------                                             | -------      | -------                                         | -------
  build-tools;27.0.3                                  | 27.0.3       | Android SDK Build-Tools 27.0.3                  | build-tools\27.0.3\
  build-tools;28.0.3                                  | 28.0.3       | Android SDK Build-Tools 28.0.3                  | build-tools\28.0.3\
  build-tools;29.0.2                                  | 29.0.2       | Android SDK Build-Tools 29.0.2                  | build-tools\29.0.2\
  emulator                                            | 27.3.10      | Android Emulator                                | emulator\
  extras;android;m2repository                         | 47.0.0       | Android Support Repository                      | extras\android\m2repository\
  extras;google;m2repository                          | 58           | Google Repository                               | extras\google\m2repository\
  extras;intel;Hardware_Accelerated_Execution_Manager | 7.3.2        | Intel x86 Emulator Accelerator (HAXM installer) | extras\intel\Hardware_Accelerated_Execution_Manager\
  ndk-bundle                                          | 20.0.5594570 | NDK                                             | ndk-bundle\
  ndk;20.0.5594570                                    | 20.0.5594570 | NDK (Side by side) 20.0.5594570                 | ndk\20.0.5594570\
  patcher;v4                                          | 1            | SDK Patch Applier v4                            | patcher\v4\
  platform-tools                                      | 29.0.2       | Android SDK Platform-Tools                      | platform-tools\
  platforms;android-18                                | 3            | Android SDK Platform 18                         | platforms\android-18\
  platforms;android-25                                | 3            | Android SDK Platform 25                         | platforms\android-25\
  platforms;android-26                                | 2            | Android SDK Platform 26                         | platforms\android-26\
  platforms;android-27                                | 3            | Android SDK Platform 27                         | platforms\android-27\
  platforms;android-28                                | 6            | Android SDK Platform 28                         | platforms\android-28\
  platforms;android-29                                | 3            | Android SDK Platform 29                         | platforms\android-29\
  sources;android-18                                  | 1            | Sources for Android 18                          | sources\android-18\
  sources;android-25                                  | 1            | Sources for Android 25                          | sources\android-25\
  sources;android-26                                  | 1            | Sources for Android 26                          | sources\android-26\
  sources;android-27                                  | 1            | Sources for Android 27                          | sources\android-27\
  system-images;android-18;default;x86                | 3            | Intel x86 Atom System Image                     | system-images\android-18\default\x86\
  system-images;android-18;google_apis;armeabi-v7a    | 5            | Google APIs ARM EABI v7a System Image           | system-images\android-18\google_apis\armeabi-v7a\
  system-images;android-25;google_apis;x86            | 15           | Google APIs Intel x86 Atom System Image         | system-images\android-25\google_apis\x86\
  system-images;android-27;google_apis;x86            | 8            | Google APIs Intel x86 Atom System Image         | system-images\android-27\google_apis\x86\
  tools                                               | 26.1.1       | Android SDK Tools                               | tools\

I installed the Android-29 packages, but then realized that the Pixel 2 runs on api level 28, so there was no point.

Any warnings or errors when building?

PS Z:\android\doze_widget\doze_widget> cargo apk build
Compiling injected-glue for aarch64-linux-android
warning: use of deprecated item 'std::mem::uninitialized': use `mem::MaybeUninit` instead
   --> Z:\android\doze_widget\doze_widget\target\android-artifacts\debug\injected-glue\lib.rs:298:30
    |
298 |             let mut thread = mem::uninitialized();
    |                              ^^^^^^^^^^^^^^^^^^
    |
    = note: `#[warn(deprecated)]` on by default

warning: use of deprecated item 'std::mem::uninitialized': use `mem::MaybeUninit` instead
   --> Z:\android\doze_widget\doze_widget\target\android-artifacts\debug\injected-glue\lib.rs:347:30
    |
347 |             let mut events = mem::uninitialized();
    |                              ^^^^^^^^^^^^^^^^^^

warning: use of deprecated item 'std::mem::uninitialized': use `mem::MaybeUninit` instead
   --> Z:\android\doze_widget\doze_widget\target\android-artifacts\debug\injected-glue\lib.rs:348:61
    |
348 |             let mut source: *mut ffi::android_poll_source = mem::uninitialized();
    |                                                             ^^^^^^^^^^^^^^^^^^

   Compiling doze_widget v0.1.0 (Z:\android\doze_widget\doze_widget)
    Finished dev [unoptimized + debuginfo] target(s) in 2.04s
aapt2.exe W 08-31 18:14:02 10756  5924 ApkAssets.cpp:138] resources.arsc in APK 'P:\sdk\platforms\android-29\android.jar' is compressed.
 'lib/arm64-v8a/libdoze_widget.so'...
Verifying alignment of Z:\android\doze_widget\doze_widget\target\android-artifacts\debug\apk\doze_widget.apk (4)...
      49 AndroidManifest.xml (OK - compressed)
    1248 res/mipmap-mdpi-v4/ic_launcher.png (OK)
    3272 res/mipmap-hdpi-v4/ic_launcher.png (OK)
    6496 res/mipmap-xhdpi-v4/ic_launcher.png (OK)
   10616 res/mipmap-xxhdpi-v4/ic_launcher.png (OK)
   16716 res/mipmap-xxxhdpi-v4/ic_launcher.png (OK)
   25072 resources.arsc (OK)
   26303 assets/fonts\Ubuntu-R.ttf (OK - compressed)
  198688 lib/arm64-v8a/libdoze_widget.so (OK - compressed)
Verification succesful
PS Z:\android\doze_widget\doze_widget> adb install --abi arm64-v8a .\target\android-artifacts\debug\apk\doze_widget.apk
Performing Streamed Install
Success

Those are mostly code-etiquette things, so they shouldn't really do much (Unless you're doing something wrong with uninitialized memory which would explain this).

I use adb install --abi arm64-v8a <PATH> to install directly to make sure I have the right abi.

[OptimisticPeach]

I tried with both nightly-x86_64-pc-windows-gnu and nightly-x86_64-pc-windows-msvc toolchains, with the appropriate targets installed.

[philip-alldredge]

Would you mind posting a non-functional APK? I have been unable to reproduce so far. Either that or checking the binary to see if the ANativeActivity_onCreate or similar symbol is appearing in the binary.

[philip-alldredge]

Do you happen to be building a release build? We are stripping symbols and that seems to be causing the problem. We won't need to strip all symbols.

[OptimisticPeach]

doze_widget.zip
This app is defined with the following main.rs:

fn main() {
    
}

And the following manifest:

[package]
name = "doze_widget"
version = "0.1.0"
authors = ["OptimisticPeach <optimistic.peach@outlook.com>"]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]


[package.metadata.android]
# The target Android API level.
# "android_version" is the compile SDK version. It defaults to 29.
# (target_sdk_version defaults to the value of "android_version")
# (min_sdk_version defaults to 18) It defaults to 18 because this is the minimum supported by rustc.
android_version = 29
target_sdk_version = 29
min_sdk_version = 26

# Specifies the array of targets to build for.
# Defaults to "armv7-linux-androideabi", "aarch64-linux-android", "i686-linux-android".
build_targets = [ "aarch64-linux-android" ]

#
# The following value can be customized on a per bin/example basis. See multiple_targets example
# If a value is not specified for a secondary target, it will inherit the value defined in the `package.metadata.android`
# section unless otherwise noted.
#

# The Java package name for your application.
# Hyphens are converted to underscores.
# Defaults to rust.<target_name> for binaries. 
# Defaults to rust.<package_name>.example.<target_name> for examples.
# For example: for a binary "my_app", the default package name will be "rust.my_app"
# Secondary targets will not inherit the value defined in the root android configuration.
# package_name = "rust.cargo.apk.advanced"

# The user-friendly name for your app, as displayed in the applications menu.
# Defaults to the target name
# Secondary targets will not inherit the value defined in the root android configuration.
label = "DozeWidget"

# Internal version number used to determine whether one version is more recent than another. Must be an integer.
# Defaults to 1
# See https://developer.android.com/guide/topics/manifest/manifest-element
version_code = 1

# The version number shown to users.
# Defaults to the cargo package version number
# See https://developer.android.com/guide/topics/manifest/manifest-element
version_name = "1.0"

# Path to your application's resources folder.
# If not specified, resources will not be included in the APK
res = "./res"

# Virtual path your application's icon for any mipmap level.
# If not specified, an icon will not be included in the APK.
icon = "@mipmap/ic_launcher"

# Path to the folder containing your application's assets.
# If not specified, assets will not be included in the APK
assets = "./assets"

# If set to true, makes the app run in full-screen, by adding the following line
# as an XML attribute to the manifest's <application> tag :
#     android:theme="@android:style/Theme.DeviceDefault.NoActionBar.Fullscreen
# Defaults to false.
fullscreen = false

# The maximum supported OpenGL ES version , as claimed by the manifest.
# Defaults to 2.0.
# See https://developer.android.com/guide/topics/graphics/opengl.html#manifest
opengles_version_major = 3
opengles_version_minor = 2

# Adds extra arbitrary XML attributes to the <application> tag in the manifest.
# See https://developer.android.com/guide/topics/manifest/application-element.html
[package.metadata.android.application_attributes]
"android:debuggable" = "true"
"android:hardwareAccelerated" = "true"

# Adds extra arbitrary XML attributes to the <activity> tag in the manifest.
# See https://developer.android.com/guide/topics/manifest/activity-element.html
[package.metadata.android.activity_attributes]
"android:screenOrientation" = "unspecified"
"android:uiOptions" = "none"

# Adds a uses-feature element to the manifest
# Supported keys: name, required, version
# The glEsVersion attribute is not supported using this section. 
# It can be specified using the opengles_version_major and opengles_version_minor values
# See https://developer.android.com/guide/topics/manifest/uses-feature-element
# [[package.metadata.android.feature]]
#name = "android.software.app_widgets"
#name = ""

[[package.metadata.android.feature]]
name = "android.hardware.vulkan.level"
version = "1"
required = false

# Adds a uses-permission element to the manifest.
# Note that android_version 23 and higher, Android requires the application to request permissions at runtime.
# There is currently no way to do this using a pure NDK based application.
# See https://developer.android.com/guide/topics/manifest/uses-permission-element
[[package.metadata.android.permission]]
name = "android.permission.WRITE_EXTERNAL_STORAGE"
max_sdk_version = 18

[[package.metadata.android.permission]]
name = "android.permission.CAMERA"

End of manifest

I'm not using release mode currently, and using it produces the same result.

[OptimisticPeach]

doze_widget.zip
Here's a version (Still debug like the last) which has default targets enables in case you needed that.

[philip-alldredge]

Are you using rust 1.37.0. I wasn't able to reproduce your issue. I just upgraded and now I have the same results.

@mb64 what version of rust are you using when you started encountered your symbol issue?

[OptimisticPeach]

PS Z:\android\doze_widget\doze_widget> rustup default
nightly-x86_64-pc-windows-msvc (default)
PS Z:\android\doze_widget\doze_widget> rustc -V
rustc 1.39.0-nightly (4295eea90 2019-08-30)

I just updated today (And yesterday) for trying to get this to work.
I can try stable, give me a moment.

If I use

PS Z:\android\doze_widget\doze_widget> rustup default
stable-x86_64-pc-windows-msvc (default)
PS Z:\android\doze_widget\doze_widget> rustc -V
rustc 1.37.0 (eae3437df 2019-08-13)

(Which was updated just moments ago, and has the appropriate targets, etc, etc)
I still get the same error on logcat, and the same behavior on the phone.

[OptimisticPeach]

Huzzah! You were right, using

PS Z:\android\doze_widget\doze_widget> rustup default
1.36.0-x86_64-pc-windows-msvc (default)
PS Z:\android\doze_widget\doze_widget> rustc -V
rustc 1.36.0 (a53f9df32 2019-07-03)

I get a working APK, so it seems that something in rust 1.37.0 broke the build process 😬

[philip-alldredge]

Sorry, I wasn't clear. I was on 1.36 and it was working. 1.37 broke things for me.

I looked at the symbol table and on

1.36.0 ANativeActivity_onCreate is in both .symtab and .dynsym. On 1.37.0 it is only in .symtab. That would explain the issue.

[OptimisticPeach]

I don't know what .symtab or .dynsym are, but I assume they have to do with the symbols given their name and what you've explained. Is there any clear way to fix this or am I is everyone forced to use rust 1.36.0?