i tried youtube, researching using google, and even read a few threads on here but i didnt find anything which could help
im using a windows 10 operating system , ive used flutter on android studio and everything works fine, i enrolled in a course and the IDE used is VSCODE for flutter app development , whenever i try launching the emulator from cmd, it says "no connected devices" , i downloaded an extension on VScode and even when the emulated device is running and i type "flutter run" it still says no connected devices
im not looking to test this on a physical device and would rather use an emulator due to reasons
I am sure you would have started the emulator before running the flutter run. I had faced the same problem earlier. I did these two things to make it work,
Setup path for in your system variables
Restart the system to bring this into consideration,
https://developer.android.com/studio/intro/studio-config
Related
I am using windows in Mac Pro. In Windows Parallel Desktop I am keep on getting error message in Android Emulator like:
Google has stooped working
Settings has stopped working.
Pixel Launcher has stopped working.
Getting error message in freshly installed Xamarin tools in Visual Studio.
Googling suggested to clear the cache or force stop it, but nothing is working
For now I installed Android Studio on Mac and running project on Windows. By Following below link I ran few commands and Windows able to communicate with MAC
https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/questions/connect-android-emulator-mac-windows
Not sure if this is right way. But running virtual device inside virtual machine is giving some problem.
Above thing is working fine. Let me know if there is any other best solution for this.
I'm having trouble getting Processing 3.3.6 (x64) for Windows 10 to recognize my LG V20 android device.
At first, I was getting a NoClassDefFoundError when I tried to run a sketch, and the Android SDK updater had 2 suggested updates that I couldn't install due to more errors. My phone was not listed in Processing. The device was I've enabled USB debugging, and the connection works; I can transfer files fine.
After reading across the internet with little advice or success, I tried uninstalling all Android-related files on my computer, as well as any Processing-related files. I uninstalled Java, JRE and JDK. I then reinstalled them all:
Java 8u161 JDK and JRE
Processing 3.3.6
Android SDK (auto-installed by Processing)
It all installed without complaint, and everything seemed fine. However, Processing still can't find or recognize my device. I've also tried these exact steps on my laptop which has a mostly clean install of Windows 10 (apart from chrome and some bloatware) with the same results.
I also tried running something via Processing's emulator; I may have done this wrong, but this comes up with a "Lost connection with emulator while launching" error.
From this, it feels like it HAS to be an issue with the phone, since it's on multiple PCs. But it also HAS to be an issue with the PC, since it occurs on both a phone and an emulator. Frankly, I'm dumbfounded as to what the problem is.
I'm not really sure what else I can do or try; I haven't found my problem anywhere else, and tried the solutions to all similar problems with no success. Does anybody have any ideas?
EDIT: I fixed the problem. I tracked down the location of my adb.exe, and ran "adb devices" in cmd at that location. It listed one
device (mine), and said it was unauthorized. A prompt appeared on my
phone, and upon confirming it, the device was authorized.
first off all check is your device connected to sdk by running this command
sdk/platform-tools/adb devices
if your device name not found make sure that you have USB debug enabled
goto settings/developer settings/ allow USB debug mode
if you don't see this option search how to enable developer settings for your phone mine was like
goto settings/about/software info
and tap constantly on build-number for 7 times
I love Processing and I dreamed with the chance to use it for making Android apps, as the "Android Mode" promises. Both mentioned issues (no device connection + no emulator available) as well as the endless red Java error messages couldn't never be fixed. I tried everything regarding Android Studio & SDK parameters & component installation, as well as different PC plattforms without success. Trying to configure the SDK for matching Processing's requirements was also a waste of time. Nothing helped. People who got it, they neither know how it runs nor why it doesn't.
Forget Processing for Android, use & enjoy programming with MIT App Inventor, and really start running apps in one hour. Let's use Processing for its original purposes.
I have a macbook pro (Retina, 15 inch, late 2013) that is running High Sierra GM (17A365) and a fresh install and blank project in Android Studio always results in a crash (emulator64-crash-service quit unexpectedly.) when trying to run any android emulator. I have tried every suggestion I can find on the internet, NONE of them work. Here is what I have tried so far:
Since I have an external monitor connected to my mac, I tried both creating emulator-user.ini file with window.x values (Android VM crashes on Launch Mac) AND just tried disconnecting second monitor and running just on the macbook. Still crashes
Tried completely (including all prefs and hidden folders) uninstalling Android Studio, rebooting and reinstalling and setting up brand new default environment. Still crashes
Verified that HAXM is installed correctly and running loaded (kextstat | grep intel returns expected info), but have also tried without HAXM. Still crashes
Tried launching emulator from Terminal. Still crashes
Tried creating new avd from avd manager. All of them crash.
Tried changing settings in avd configs to use (or not use) Hardware/Software graphics, as well as fiddling with more or less memory than defaults. Still crashes.
Does anyone have anything left to try? I am pulling my hair out here. I would like to try my cordova app in Android, but it seems impossible from my mac.
I still don't know what caused it, but as a workaround creating a fresh account on my Mac and launching studio and emulator inside of that allows it to run. So it is something in my original account settings that is causing this crash, and I still don't have a clue what (although there are no active startup items, launch daemons, caches, saved app state, etc that I can find, I have cleared them all).
Today I downloaded Android Studio for my Debian Testing system. I wanted to run a HelloWorld application but weren't able to run it. With adb I can install it without having any problems.
However, if I try to do it with Android Studio, it gets stuck on 'Installing APKs'. The same happens when I try to start it in an emulator (gets stuck on 'Waiting for target device to come online').
My device is a Samsung Galaxy S3 with LineageOS (Android 7.1.2) and root permissions. Android Studio recognizes my phone properly.
What I've already done:
installed openjdk
set android_home
installed all the SDK-platforms since Android 4.3 and Android Emulator from SDK tools
enabled USB-debugging
tried with MTP and PTP
tried another emulated phone
installed lib32stdc++6
restarted my computer
and probably much more
I tried to do it the whole evening and couldn't find a solution. Is there something Debian-specific because I can only find instructions for Ubuntu? I have never experienced anything close to this on other systems.
Thank you in advance.
EDIT: I am now able to use my phone to run the android application by using USB 2.0 instead of USB 3.0! Is that a normal behavior since it works with native adb? I mean, if I buy a new PC after some years which has got only USB 3.0 ports, will I not be able to use phone debugging with Android Studio or is this just an issue? It is still known since 2014 (https://stackoverflow.com/a/9548311/8292104).
However, I still cannot get the app running on an AVD. I changed graphics to software, now it shows the phone but the screen remains black and the phone won't start. What can I do to fix it?
Try to completely delete and install Android Studio again, I think that it will solve the problem
Another possible solution that worked for me is to, in the application, go to
app - build - intermediates - split-apk - debug - slices
and then delete all of the contents within this folder. Then again, this only worked for me, so I would duplicate the document in case of corruption.
I have been working on a particular Android application for sometime and have been able to run these apps via Android Studio quite fine before but since applying a recent update I have not been able to run the app via Android studio because of the following error:
android.os.TransactionTooLargeException
Error: Could not access the Package Manager. Is the system running?
I have tried to troubleshoot this issue by connecting via a different TCP/IP instead of through USB (thinking it was a cable fault of sorts), reinstalling ADB, removing the ADB driver and restarting Android Studio, and all of the above yielded the same error when trying to run the app from Android Studio.
The update that was applied was the addition of the YouTube Android Player to a fragment. The fragment that contains YouTube Player was added to FragmentManager of the parent Activity during the onCreate method of this fragment. Could this be the problem? Or am I looking in the wrong place
Any insight would be appreciated.
You may have gotten this error while attempting to run an Android application on an emulator or device using Android Studio. The most common cause of this error is simple as stated in this link: You have to manually unlock your Android Virtual Device by swiping the "lock" icon on the screen. Security measures prevent the emulator from letting you connect the debugger before doing this. Make sure also that you are running Android Studio version above 0.3.2 or the latest version. There was some issue reported in AS 0.3.2. You can update it from Help >Check for update.
Found this thread which states that it might be an issue with your emulator not with Android Studio. Maybe you are trying to install application before even the emulator started properly. Wait till the home screen appears in the emulator before trying to install any application.
Also try to install any apk in Emulator from command line
Steps to install
Go to $Android_SDK_DIR\platform-tools, right click there keeping shift key pressed and Chose "Open Command Window here".
Run command adb devices to make sure yout emulator is running properly. It will show all your running emulators.
Now if emulators are showing properly, type the command adb install YOUR_FULL_APK_PATH , YOUR_FULL_APK_PATH is of any .apk
file path in your system.
You need to wait for the emulator to full start which may take a few minutes. Once it is fully started (UI on the emulator will change), it should work. You will need to restart the app after the emulator is running and choose the running emulator when prompted. You can check on this bug report the full details.
Hope this helps!
I'm not sure, but check if this works.
menu>> tools>>Android>>Enable ADB integration check it