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
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
Hi friends I added google play service to genymotion emulator,I drag the zip files of gapps and also arm v1 to it but when I opening the emulator its getting unfortunately google play services has stopped and also when I am trying to add account in it showing loading.. can anyone tell me the solution for it.
I faced this same issue.This issue is generally due to not following order of
flashing Gapps appropriately.Being a beginner in android programming.Well, I learnt following things to keep in mind while setting up google play services:
Download the ARM Translation Installer v1.1 and drag and drop the zip file onto the running Genymotion emulator device. The ARM emulator is only needed for apps that trigger a
INSTALL_FAILED_CPU_ABI_INCOMPATIBLE
error.
You must close and restart the emulator fully before continuing.
The Google Play APK package needed is specific to the Android emulator version. You must use the corresponding Google Play Service package. Otherwise, you may notice problems with Google Play not having Internet connectivity or other strange issues.
If you are using below listed specific versions ,sometimes files you are using get corrupted.
Solution:
Check android version and apk link for gapps to be flashed:
Google Apps for Android 6.0 (see instructions for flashing)
1) (https://www.androidfilehost.com/?fid=96042739161891406 - gapps-L-4-21-15.zip)
2) (https://www.androidfilehost.com/?fid=24052804347835438 - benzo-gapps-M-20151011-signed-chroma-r3.zip)
Google Apps for Android 5.1
(https://www.androidfilehost.com/?fid=96042739161891406 -
gapps-L-4-21-15.zip)
Google Apps for Android 5.0
(https://www.androidfilehost.com/?fid=95784891001614559 -
gapps-lp-20141109-signed.zip)
Google Apps for Android 4.4.4
(https://www.androidfilehost.com/?fid=23501681358544845 -
gapps-kk-20140606-signed.zip)
Google Apps for Android 4.3
(https://www.androidfilehost.com/?fid=23060877490000124 -
gapps-jb-20130813-signed.zip)
Google Apps for Android 4.2
(https://www.androidfilehost.com/?fid=2306087749000018 -
gapps-jb-20130812-signed.zip)
Google Apps for Android 4.1
(https://www.androidfilehost.com/?fid=22979706399755082 -
gapps-jb-20121011-signed.zip)
Update or reinstall Genymotion and Virtual box :
If you are flashing all gapps apk correctly and you are still facing this issue.
You need to check which version of genymotion and virtual box you are using .Use latest version of genymotion and VB.
Uninstall Genymotion and Virtualbox :
If updating or re-installation doesn't work you need to remove old registry files hidden in your computer which are preventing you from flashing Gapps properly.Repeat steps of flashing mentioned above.
Note: Don't forgot to restart genymotion after flashing files.
Hope it helps,Cheers..Happy Coding!!!
I had the same issue and found lots of solutions available on the internet. I followed the steps given in http://www.thecrazythinkers.com/how-to-fix-unfortunately-google-play-services-has-stopped/ and got a perfect solution.
To setup Google Play Service in your genymotion follow my answer in this question, hope it will help you. Question link
i post this question because none of the solutions posted to
already existing threads helped for me.
today morning everything worked fin, i pressed on the Run-Button and
my iOS-Simulator stated out of Xcode showing my implemented App.
few hours later it shows this error-message:
"Xcode cannot run using the selected device. No provisioned iOS devices
are available with a compatible iOS version. Connect an iOS device with
a recent enough version of iOS to run your application or choose an
iOS simulator as the destination."
My Targets iOS SDK is 6.1
Under Summary i chose as Device an iPad (as before)
Under Summary i chose 6.1 as Deployment Target.
I have no "real" iOS Device at home so i always used the simulator.
As i said, since today afternoon not working.
what could be the prblem?
One of my coworkers set me up with a provisioning profile through our corporate profile. I have read through several tutorials and none of them corresponded to the steps he actually took to get it set up. In the end my device was listed under the devices section of the organizer with a green circle next to it (I am guessing that's good?) but when I try to run the application on my device I get the error I mentioned in the subject of this post. I should mention my device is jailbroken running iOS 4.2.6. Is the "jailbrokenness" of my device an issue?
This is like day one with Xcode and it is pretty overwhelming coming from the Linux command line and Emacs. I don't expect a complete walk through from any of you. But if you can point me to a nice long tutorial showing me how to set this up with the latest version of Xcode I would appreciate it.
Check if you can see your device in Organizer and verify iOS version installed on the device with the deployment target for your application. This is very often the case as you won't be able to deploy 4.3 application to 4.2.1 device (for example).
In Xcode Set the target to project_name | iOS Device
Then in Xcode From the product menu=>Build For=> Build For Testing