I've just uploaded my app to the android market place and it works on my Samsung Mini, but when trying to download it to a Samsung Galaxy I get the error message device not supported.
The app is listed with
API level: 10-16+
Supported screens: small-xlarge
OpenGL textures: all
Required device features:
android.hardware.touchscreen
Any ideas why it doesn't support the Samsung Galaxy phone?
Have you mentioned minimum sdk version & also target sdk version in your manifest file ?
Also android Os version of both the devices are same?
Related
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
I don't know if I'm allowed to ask this question but I really can't figure out how to use ARCore on Android Emulated Device.
According to the official guide I'm supposed to use API 8.1 on pixel/pixel 2 device in order to run any app which uses ARCore. Sadly those emulator don't come with the support for Play Store, and without Play Store I can't Instal ARCore on the device.
The device images that come with built in Play Store can't run ARCore instead. I'm really confused about how am I supposed to test anything for ARCore in this way.
I need it to develop an app for a University program and I need to become familiar with Augmented Reality Development but I can't even get started because of this issue.
Updated: October 20, 2022.
For using ARCore Emulator, at first, you have to create a virtual device with support for AR. I'm running Android Studio Dolphin | 2021.3.1 on macOS Monterey 12.6.
I created Pixel 6 Pro virtual device:
ARCore's targetSdkVersion has been set to Android API level 33.
Here are the steps you have to make in order to get a working Emulator:
Set up Android Debug Bridge. I set up adb for Mac.
Download Google_Play_Services_for_AR_1.34.0_x86_for_emulator.apk from GitHub repository.
Run your AVD.
Type in Bash Terminal the following command (to be sure that the port is 5554):
adb devices
Result:
// emulator-5554 device
Go to the folder where Google_Play_Services_for_AR_1.34.0_x86_for_emulator.apk is located. For instance:
cd ~/Desktop
To install Emulator, type in Terminal the following line, while the virtual device is running:
adb install -r Google_Play_Services_for_AR_1.34.0_x86_for_emulator.apk
Repeat previous steps for additional AVDs you’d like to use.
Delight!
P.S.
Take it into consideration: Android Emulator does not support such ARCore APIs as: Depth API, Geospatial API or Augmented Faces API. That's because Emulator doesn't have corresponding sensors. When any of these features are enabled, the Emulator picture can't render correctly: a screen will be entirely black, although UI elements drawn on top of the Emulator picture still be rendered.
Sergei's answer was right at the time, but the version of the ARCore app in his link (v1.1.0) is now too old. The following worked for me (after many false starts):
VIRTUAL DEVICE SPECIFICATIONS
Device: Pixel API 27
System image: Oreo / API Level 27 / ABI x86 / Android 8.1 (Google Play)
LINK TO ARCORE APK:
https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-5-18091013-release/arcore-1-5-180910139-android-apk-download/download/
Download the ARCore APK to your desktop. In Android Studio, set up and then start the virtual device as specified above, open the Play Store app on it and sign in. Then drag the ARCORE APK file onto the virtual device; it should silently install. Finally, run hellosceneform on the virtual device.
Just install to emulator ARCore_1_1_x86_for_emulator.apk. Just drug to emulator. Check this link https://github.com/google-ar/arcore-android-sdk/releases/tag/v1.1.0
I am trying to install some APKs which have the minimum OS version parameter set to 4.4.4 KitKat and minimum SDK #16.
The platform is the Epson Moverio BT-200 see-through glasses which is basically a tablet.
More on the device:
https://www.cnet.com/products/epson-moverio-bt-200-smart-glasses-8-gb/specs/
The BT-200 itself comes without Google Play Store and needs to be rooted and Play Store installed. This part is done.
I also tried to install APKs and edit the build.prop file first. Set the OS version to 4.4.4 but got the exception that minSDK version criteria failed. Tried with ADB install as well. Of course when I set the SDK version in the build.prop file it ruined the installed apps and most of them freezed, suddenly stopped etc.
My question is, how could I "fool" the APK installer to install the APK(s) to get the programs running? Is there a way?
My reason: the BT-200 is a fantastic FPV device with android. The newest BT-300 model has android 5 but while this still works like a charm I'd spend my money rather on beers than another FPV glasses. :)
Any help appreciated.
4.4.4 KitKat is api 19 , did you set your targetsdk to api 19 ? as for minsdk just change it to api 15 . the bt moverio from what i know is either api 15 or api 19, check on your bt moverio glasses what api it supports and then set the target sdk to that api.
When I try to install apk on Xamarin Android Player I'm getting next error:
Failure [INSTALL_FAILED_NO_MATCHING_ABIS]
I use:
Xamarin Android Player
Nexus 5 Lollipop Android 5.1.0 - API 22
USB Debugging is allowed and it displays in attached devices list (adb devices)
INSTALL_FAILED_NO_MATCHING_ABIS : This error says that you try to install an app that has native libraries and they don't match with your CPU architecture. Make sure to compile the app for the CPU architecture (armeabi-v7a/Intel) of the test device. E.g if the app is compiled for arm and the deployment device has Intel this error will be shown.
some days ago, I bought a phone Sumsung s4.then I find that I couldn't use ndk debug on the phone. I have surching lots of infomation , but not get a solution.
The question is Sumsung have changed some code for the system./data/system/packages.list is used by 'run-as' both to get the data directory for an app, and to start gdbserver on the device. Most samsung phones have this moved to /dbdata/system/packages.list, but 'run-as' wasn't rebuilt to reflect this change, and throws an error. So, the ndk-gdb script can't connect to these phones.
so please help me!!!!
The gdb (and invoking script) built into the Apportable SDK has a workaround for the ndk-gdb run-as issue on the Samsung S4 (and many Android 4.3 phones)
More details available at run-as Package 'a.b.c' is unknown - Galaxy S4 Jellybean or Android 4.3