I'm going to say upfront, please forgive me. I'm a newbie to android development and fairly new to programming. Also on a Mac. You're going to have to talk...real...slow.
I can't get an AVD to load. I've tried it from Eclipse (Juno) and from the Android SDK Manager (20.0.3). Failed multiple times.
Received the same error each time,
"Failed to parse properties from User/myname/.android/avd/nameIGaveEmulator/config.ini."
EDIT: I tried to solve the path problem on my own by checking folders and moving them around to be in the same folder, then resetting the path in Eclipse preferences, but that didn't work, so I trashed everything except for the zip files, uncompressed and started the entire installation all over again. When I opened up SDK Manager and attempted to download tools and platforms, however, I received the following. I'd forgotten that I received it on the first install. Would this have something to do with the problem?
Preparing to install archives
Downloading Android SDK Platform-tools, revision 14
Installing Android SDK Platform-tools, revision 14
Stopping ADB server failed (code -1).
Installed Android SDK Platform-tools, revision 14
Stopping ADB server succeeded.
Starting ADB server failed (code 255).
Done. 1 package installed.
Sidenotes:
When I open Eclipse and SDK Manager, I don't see anyplace to check that I'm the administrator.
If a path needs to be "changed" what exactly does that mean and how do I go about doing so? Is it simply a matter of moving folders and files into the "correct" locations and then trying to load an AVD again?
Using command line, navigate to the /tools folder in your android SDK, then use the command:
$ ./android avd
This will launch the AVD manager.
Related
Migrating my native script application to 8.1.5 version.
Fixed the errors that occurs when migrating the native script application.
Application build successfully in the emulator. After build successfully getting error in the application.
How to fix this issue?
Try this:
Go to AVD Manager, and click wipe data on the selected emulator:
Restart your machine (adb connection might be lost).
Then restart your project by running:
ns clear
ns run android
If that doesn't open the app on the emulator, run:
ns devices
Spot the emulator ID you want to run the app on
ns build android
ns deploy --device EMULATOR-ID
Note:
Make sure you've done all 4 blue steps in the cli message (in blue).
I created a new empty project, switched platform to Android and started Build and Run. But when it comes to "Copying APK File to device" it just freezes and I have to restart Unity.
I installed Android SDK & NDK tools just before that (through Unity Hub). Android Build Support was installed by me manually a while ago so it was visible as installed in Add Modules window. I did not do any changes to the project. The most interesting thing is that the apk is built in my Builds folder. Not sure if it works though.
I am using Unity 2019.1.0f2. The device Android version is 9.0 (API level 28) and the minimum API set in Player is 16, so the problem should not be with API.
Does anyone know possible reasons for it?
Try to turn off the following setting on your android device.
Settings -> Developer options -> Monitor apps installed by ADB
This setting(if turned on) will ask a verrification if you want to install the app. It feels like this cuts off the connection with unity which causes it to get stuck.
Unplugging and replugging the device seems to work aswell. In case of big projects this is anoying tho since if you are to quick it will just say it lost connection and it will ask if you want to reconnect, which in turn causes the same problem.
This is the only answer that worked for me:
https://answers.unity.com/questions/1248123/build-run-apk-freezes-on-pushing-content-only-one.html
In short, Player settings -> Publishing settings -> Split application binary
First of I would ask you on what computer did you run this on? (performance wise)
Second you can just copy the .apk file to the phone and install it there. If you got to where it prompts for copying to android your apk file is fine and built.
I have just installed Tizen Studio 2.0 and I was trying to update my old application (version wearable 2.2) with new features.
The target device is a Samsung "Gear 2" (not "Gear S2").
By means of the package manager I installed both the Samsung certificate and the Samsung wearable extension.
I removed all the old certificates and acquired a new one via the certificate manager (Samsung option). The new certificate results active.
From the device manager/file explorer I selected "permit to install applications". The result was en error and an invitation to create and activate a Samsung certificate. Exactly what I had done previoulsy!!!!!!
Trying to install the app via debugger the result was:
[Initializing the launch environment...]
RDS: On
Target information: SM-R380
Application information: Id(Z8KnFDT3ds.ride), Package Name(Z8KnFDT3ds),
Project Name(ride)
[Transferring the package...]
Transferred the package: wgt stream -> /opt/usr/apps/tmp/ride.wgt
[Installing the package...]
path is /opt/usr/apps/tmp/ride.wgt
processing result : FATAL_ERROR [61] failed
spend time for pkgcmd is [94]ms
cmd_ret:61
An exception occurred
(Installing the package... > Fail)
An exception occurred
Unexpected stop progress...
(9.763 sec)"
I have already tried (uselessly) to:
regenerate the .medata file,
to create a new the workspace,
to reinstall Tizen 2.0.,
to create a new certificate,
to install the wgt via sdb.
The time and the date on the Gear 2 are correctly synchronized with my host computer (OS Windows 10).
I noticed an anomaly in my Gear 2 DUID (PB+hcyFaLdbqjuVe+Gcn4vBlSYw=)
Considering what reported at the link: http://developer.samsung.com/gear/develop/getting-certificates/permit the DUID should be in any case preceded by a #1.0 or #2.0. This is not true in my case.
By changing manually the DUID to: 1.0#PB+hcyFaLdbqjuVe+Gcn4vBlSYw= a certficate is apparently correctly uploaded on the target even if the FATAL error 61 persits.
Any idea?
Regards
I have been having insurmountable problems with SDK 2.0 as well. Eventually I decided to roll back to the previous version but was struggling to find out how or where to get it. I got a response from the Tizen support team with the following instructions.
Launch Package Manager
click the "Configuration" icon in the top right corner of the Package Manager window.
Turn OFF the "Auto Update" feature
You will be able to see the list of previous versions of Tizen Studio. Select your desired version and click "OK"
This will prompt you that its going to update the previous version. please follow the UI prompt to uninstall this version and install the previous version.
This may or may not work for you.
I've built my application as an x86 native app, and I've ran it on Genymotion. The problem occurs when I try to debug from Eclipse. In the console view, I get the age old:
gdbserver output:
run-as: exec failed for lib/gdbserver Error:No such file or directory
Verify if the application was built with NDK_DEBUG=1
It all works fine with ARM builds though. I checked that the x86 gdbserver is getting included in my .apk lib/x86/gdbserver. I've also read that the x86 versions of android include a gdbserver locally anyway, so not sure what the point of all that is.
I've been able to manually attach the included gdbserver using adb shell, and then get Eclipse to attach to it remotely using this is a starting point: How to get ndk-gdb working on Android?
It doesn't mention anything about x86 or Genymotion though. Unfortunately, it's tedious, and it's seemingly useless since it doesn't load any symbols (though that's probably because of my ignorance.)
Is there any guidance for making this setup, using Eclipse and Genymotion to debug native apps, work?
Sadly, this is due to a bug in Genymotion v2.2
It will be fixed on our next release (I work for Genymotion).
You are right, gdbserver is not deployed from the apk, and this is why it doesn't work.
You can find here a patch to apply that will fix this apk deployment bug for Genymotion KitKat devices created with Genymotion 2.2: native-debug-fix.kitkat.zip
Warning this patch is only for:
Kitkat (Android 4.4.2) devices
created with genymotion v2.2
Don't apply the patch on other devices, it will brake things.
to apply the patch, simply drag n'drop the zip file on genymotion.
I understand there are many threads like mine but I have been trying to get an Android Emulator to work on my Windows XP PC and have encountered nothing but brickwalls. Here is what I've done:
I installed the latest JDK (Version 6 Revision 26) ... no problem
I unpacked "Eclipse" (Version 3.7 - Indigo) ... no problem
I downloaded and unzipped Android SDK ... no problem
I updated Android SDK with Android SDK Tools and two platforms (2.2 and 3.1) ... no problem
I installed the ADT plug-in for Eclipse ... no problem
I configured ADT to point to the Android SDK ... no problems
I created the "Hello World" app from the Android developers site ... no problem
I tried to run it...
And this is where I've been halted. I've tried:
Creating an AVD with default settings in both 3.1 and 2.2 ... no luck
Changing device RAM size ... no luck
Starting the AVD from Android SDK ... no luck
Starting AVD from the command line ... no luck
Starting it with no animation ... no luck
Leaving it to start over night, twice, with different settings ... no luck
I've been perusing websites for hours trying to find other solutions but having absolutely no luck?!?
It basically starts to load, it shows the "A N D R O I D _" animation and then moves to the one where the green "swoosh" moves across the logo and then it just sits there...for hours! If I try and run the "Hello World" app while it's in this state it just fails (obviously.) I don't know if I'm missing something obvious or what?!? I'm happy to uninstall everything and try again but not before I've exhausted reasonable measures to fix what I imagine to be an easy problem to solve?!?
Please try this process.
Close your Eclipse IDE
Restart the IDE and delete the AVD created.
Create the AVD and then relaunch the application.
Please let me know if this process helped you.
Similar issue here:
Newly installed Eclipse and Android SDK. Can't get emulator to work. Hangs on clock screen
Create an APK file (archive for java app for Android), copy to the machine using usb cable or whatever you use, and then just install it. Not the ideal, but it helps.