Using the Android tools for C++ in VS15, I've been unable to get the debugger working... VS is able to install the app on the test device without an issue, but debugging does not work.
Unable to start debugging. Non-debuggable application installed on the target device. Required file '/data/data/com.AndroidTest/lib/gdbserver' could not be found on the device. Please reinstall the debuggable version.
I've inspected the apk; it does have gdbserver.
The device I'm using is a LG G 7.0 (V400) running Android 5.0.2. The project targets API level 19, but I've also tried targeting API level 21 and still the same issue.
Any ideas?
I've had the exact same problem, "Unable to start debugging" with the LG V400. The solution to that was to root the tablet, and it works just fine now.
I used this in order to root my device:
http://sourceforge.net/projects/avicohh/files/Android/LG_One_Click_Root_by_avicohh.exe/download
After that I've found some Samsung phones also suffer from that same issue.
Related
I am using Flutter for developing my android apps but for some my android studio is not able to recognize my device even though my device is detecting that fully. Is there a way to fix this?
And also for the record, I have tried all the possible methods available on stack overflow and internet like Enabling USB debugging, MTP Transfer, Installing universal USB Driver.
Some phones like OPPO, VIVO, etc is having an extra drivers. It will be shown when you connect your phone with pc. You have to install that driver too. Also check whether this phone is working with another computer or any other phones works in your computer too(to check both your phone and PC is ok). Also check in normal android app development instead of flutter, like checking your phone connection in android studio with java or kotlin.
if all this didn't works then install Visual Studio Code and check the same thing it it. may be this is some issues in Android studio. please inform the details here after all this.
Go to file> Invalidate cache/Restart > click invalid cache and restart button in android studio.
Then run.
If still cannot connect device:
goto file>settings> appearance & behaviour > Android SDK > sdk tools >deselect android sdk platform tools > apply>ok.
It installed the requested components.
then goto app > edit configuration> uncheck allow parallel run in right corner>ok
A young friend of mine would like to push a game created using www.buildbox.com to his Samsung Android Tablet. He is using Windows 10 and Android Studio 3.6.1.
But the Device Drop Down is greyed out and for some reason the AVD Manager, the SDK Manager and the Connection Assistant are missing from this tools menu.
On my Android Studio 3.4 I can still see the Connection Assistant
I checked the Release notes but could not find anything.
https://developer.android.com/studio/releases
I checked that Windows can see the tablet as a USB device and the friend told me that developer mode is enabled.
Any ideas what is going on ?
So I got a chance to look further into the problem.
It turned out, that the problem seems to be with Buildbox not generating a proper Android project. In particular the generated project is missing a proper module and a proper app configuration. Once I added those the missing connection tool reappeared.
However I still got an error.
Recently I decided to learn android dev with Kotlin, I installed JDK, the latest Android Studio release and other stuff but my CPU is AMD so I cannot install intel's HAXM which is required to launch the emulator . I want to know if an equivalent for pc with AMD exist
For your problem there are several ways to fix the issue.
Android Studio with Android Emulator Hypervisor Driver for AMD Processors Tools(Recommended)
Here's the full document
Go to Android SDK -> SDK Tools -> Check Android Emulator Hypervisor Driver for AMD Processors also make sure if they're installed they're updated, since this solution got a problem with using NOX player at same time, and causing Blue Screen of Death
Then go to App & Features -> Turn windows features on or off -> make sure Hyper-V and Windows Hypervisor Platform are disabled. All Windows features enabling Hyper-V either explicitly or silently must be turned off.
Other solution is to use Nox or Bluestack emulator. i prefer nox since idk why but bluestack using so many resource, and also nox multi-instance is also working very well for using several emulators and it's got 3 version of android (4, 5, 7).
Common issues while using nox when trying to develop flutter app or etc is sometime emulator won't appear in your emulator list in android studio which the solution is that you should copy your adb nox file to your android sdk folder. or address the PATH VARIABLES to use nox adb.
Good Luck.
I am trying to run my app on canary build of the android emulator from android studio on AMD processor but I am getting the following error
1:47 PM Emulator: [2440]:INFO:android/android-emu/android/verified-
boot/load_config.cpp:236:Verified boot params were not found.
1:47 PM Emulator: **
1:47 PM Emulator: ERROR:/usr/local/google/buildbot/src/android/emu-master-
dev/external/qemu/fpu/softfloat.c:486:round_canonical: code should not be
reached
1:47 PM Emulator: Process finished with exit code 3
I got to know about the canary build of the android emulator for AMD processor from here. My virtual device' CPU/ABI is armeabi-v7a. I searched for what the 'exit code 3' for the emulator mean but I didn't get any solution.
Can someone help me please!
I got the android emulator working today.
I have done the instalation process for canary build of android studio from the beginning:
1. Enabled "Hyper-V" and "Windows Hypervisor Platform" in "Turn Windows features on or off" settings of Windows. This has been explained in here.
2. Downloaded the latest Canary build of Android studio from here.
3. After downloading the zip file I followed the guidelines in here under "Install alongside your stable version" heading. The guide lines are:
a. Unpack the ZIP file.
b. Rename the resulting folder to something unique like "Android Studio Preview."
c. Move it to a permanent location, such as next to your existing Android Studio install in C:\Program Files\Android.
d. Inside C:\Program Files\Android\Android Studio Preview\bin\, launch studio64.exe (or if you're on a 32-bit machine, launch studio.exe).
4. After launching studio64.exe I got a pop-up message to update Android emulator. After the update I created a new virtual device with an image of x86 with android 9.0. I started the android emulator to test my app. Though I got the
Verified boot params were not found
popup error message initially, the emulator started functioning well.
I am a very new Android developer and was until today having the same issue as yourself. Here is how I got it to work (Please note I am also on an AMD system).
Make sure you have enabled Hyper-V and Windows Hypervisor Platform. If you type "turn windows features on" in your run bar you should be able to locate it. Also enable virtualisation in the Bios. Mine comes under "SVD".
(Please note after this step I was still experiencing the problem but this is a pre-requisite).
Delete all devices from the AVD manager.
Install a new x86 device from the AVD manager. What I did here was select a version down from the one I was previously getting issues on so Oreo from Pie. When it asks to confirm if you want to wipe the user data please confirm positive.
Once setup, run the device from the AVD manager. It may ask you if you wish to enable Instant Run. I elected to disable this. (I had enabled it when I first was trying to run a device).
You will still receive the 1st error regarding no boot parameters but the emulated environment should load. You can now run the APP and it should install the APK. Previously due to the device not coming online properly, the APK would not install. I can also now setup a device on Pie without experiencing the issue so I think it may have been the wiping of the previous data that helped.
I wish I could tell you WHY this worked for certain and previously it would not work, sadly I cannot but hopefully this will get you working.
Yesterday, I installed Android Studio's latest version on Ubuntu. Everything ran fine, until I ran the "Hello World!" program. It asked me to create a virtual device. While creating the device, it shows me an error that the AVD manager cannot find a system image. This makes no sense since I have already installed the latest SDK (API level 25, Android 7.1.1). I downloaded the system image from the AVD manager itself, but to no avail.
Can someone help me sort the damn thing out? I switched from Windows to Linux due to the plethora of problems with Android Studio on Windows. But the thing's bugging once again. Here is a screen shot: