Screen of death; my version
I have 4 problems with this screen
1.) I have absolutely downloaded all the requirements
2.) my phone is on developer mode and connected to my laptop but isn't being read
3.) I can't create emulators in android studio
4.) I have added the paths to my env variables...
I'm running on an aspire one of with 2gb Ram...
what do I do different with these same PC specs to get coding?
Well First Of All Enable USB Debugging In Your Phone And See if It Shows Your Device Now.
Now In You Your Command Line Run This
flutter doctor --android --licenses
It will automatically install all the required License And You Are Good to go
AS for CommandLine Tools error Navigate to SDK Folder in your Command by entering
cd "Path of your sdk"
and After That hit this line
"--install cmdline-tools;latest"
I repeat navigate to your sdk folder and then hit this command and you are good to go.
And personally I won't suggest you to install the emulator as you said your ram is of 2gb Then it will Lag alot better turn on usb Debugging and try it on your phone !!
Related
I need to set nox emulator as my default emulator, but I need to set first adb connection, but I don't know where I can find the directory of nox app player.
Fortunately, as a Mac user, you don't have to worry too much about the directory of the Nox app player, because you don't have to use the executable nox_adb.exe, as do Windows users. Instead, you can, with a slight change, follow the steps in the Nox connection guide, but just look out, as a Mac user, for step 6, (according to vandebergz) :
Download & install Nox.
Start a project in Android Studio.
Start Nox App Player, and in Nox go to Nox system settings and turn
root mode to on, then save changes and restart Nox.
In Nox, go to Android settings and scroll down to About Tablet. Keep clicking on Build number until it shows that, "You are now a developer". In Android settings the Developer options will now be visible.
In Developer options, tick USB debugging.
(Mac only) Depending on whether or not adb and other tools are in your PATH (see below), type
adb connect 127.0.0.1:62001
from a suitable location. (This will connect localhost through port 62001 to the Android Debug Bridge.)
Android Studio should now detect Nox Player as a connectable device (although it may not appear named as Nox).
Please bear in mind that for this to work, if you're using Android Studio with default installation settings, you should either do step 6 from the directory of adb , which is usually ~/Library/Android/sdk/platform-tools ; or else you can do this from any location if you have adb and the other platform tools on your PATH. To add them to your PATH, if not done already, you'll need to open your hidden ~/.bash_profile file and add the lines:
export PATH=~/Library/Android/sdk/tools:$PATH
export PATH=~/Library/Android/sdk/platform-tools:$PATH
as described here.
Worked ok for me. :)
I have been trying to use my Nexus 5 as a debuggable device when working with Android Studio. I have used several different resources to get the device to display the RSA fingerprint (which I have accepted), but the device remains "unauthorized". I am currently running ubuntu 12.04 on a Dell XPS-13.
My desktop computer running Windows 7 has had no issues is instantly recognized and a valid debuggable device.
One issue I had just recognized after weeks of trying to get this to work is that in the AVD manager, under the Compatible column for this device when UNAUTHORIZED it says: No,minSDK(API8) > deviceSDK(API 1). I wonder if this could be related as the device is currently up to date.
Here are some of the things I have tried:
Updated 51-android.rules document with the following line, made executable:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0666", GROUP="john"
Series of adb kill/start-server commands
Accepted the RSA fingerprint in one single instance and permanently, deleted the key/re-accepted it.
Checked permissions of usb slot.
Changed device from media device to camera and back (this actually sometimes lets the "adb devices" command return a value of device for the phone, but then the abd process locks and crashes).
I haven't really seen anyone with the issue where they were able to accept the RSA fingerprint but the device remains unauthorized, or that the AVD manager reports deviceSDK(API 1).
Any help is greatly appreciated, thanks!
Edit: It should be noted that I'm a bit of a linux noob so keep that in mind.
I have also experienced this problem after upgrading from an earlier version of Android Studio to the latest 1.0 release.
My phone was in the "Unauthorized" state and the compatible column said
"No, minSdk(API18) > deviceSdk(API1)"
I fixed my issue with the following steps:
Firstly, when I upgraded Android Studio I inadvertently moved the SDK directory.
To make sure your SDK folder and environment variables match up, open the command prompt and run the following command:
echo %ANDROID_SDK_HOME%
If your SDK is in a different location correct the environment variable using the command:
setx ANDROID_SDK_HOME "C:\Android\sdk"
Now we know the SDK is pointing to the correct place at the command prompt navigate to the "sdk\platform-tools" directory and issue the commands
adb devices
adb kill-server
Notice in the image my device in the "unauthorized" state.
Now on the phone itself navigate to the developer options page and select "Revoke USB debugging authorization".
Now head back over to Android Studio and select "Run -> Run app" menu option.
Now, when you attempt to run your application your phone should pop up with the following dialog:
When you see this you should be home and dry. Now when you start adb it should be authorized.
Finally, if you are upgrading Android Studio from a beta make sure that your target SDK and minimum SDK are set correctly. Right-click on the app folder and select "Open Module Settings".
Hope this helps..
I have read a few articles that BlueStacks App Player can be used to debug android apps via Eclipse, instead of the default android emulator.
Example article
But I think this refers to the Windows version, I was unable to get to it work on MacOS. Does anyone know how to debug using BlueStacks/eclipse on MAC?
adb connect localhost:10001
should do the trick.
Well, you can try another way:
1) First, open the DDMS via Window->Open Perspective->DDMS under Eclipse.
2) Then open BlueStacks App Player.(leave it opens)
3) After that switch back to Eclipse and you should notice there're two emulator under the Device tab.
Then click Reset adb under the small triangle at the Device tab.
After a few seconds, the another one emulator will disappear and you can proceed to the next step.
4) Then return back through Window->Open Perspective->Java under Eclipse.
5) Select your project and right click on it, choose Debug As->Debug Configurations
6) Under Android Application select your configuration or create a new one. On the Target tab choose Always prompt to pick deviceAfter this, select Apply then Debug.
7) Then select BlueStacks emulator in the prompt window, and finally select OK.
Alternatively, you can also open the BlueStacks App Player before Eclipse using the above steps(with minor changes).
For more info, visit the below links.(However, in Chinese...)
http://www.cnblogs.com/hbbbs/archive/2012/10/30/2746950.html
http://www.cnblogs.com/hbbbs/archive/2012/10/30/2746979.html
Hopefully this will help you.
C:\>cd Program Files (x86)\Android\android-sdk\platform-tools
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb connect 127.0.0.1:5555
connected to 127.0.0.1:5555
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Run Bluestacks.
open Command Prompt in Windows.
Go to Platform-tools using following command.
cd C:\Users\<username>\AppData\Local\Android\sdk\platform-tools
then write:
adb devices
With SDK tools 27 and later!
You get a list of devices detected by adb .. if BlueStacks-4 is installed you should see the device listed (emulator-555x).
For Mac users: localhost:5037 worked for me
BlueStacks bundles its own copy of adb, %PROGRAMFILES(x86)%\BlueStacks\HD-adb.exe. You can connect localhost with it, or any other command. BlueStacks 3 uses the default port 5555.
When i enter "adb install asdasd.apk" to cmd returns "error:device not found". How can I fix this?
Just copy that apk file into ( D:\android-sdk\platform-tools ) android sdk platform tools.
and then open the cmd prompt.
then, come into that platform tools path in cmd prompt.
then, give like this in cmd -- adb install (appName).apk
wait few minutes and get success respomse in cmd prompt..
First, familiarize yourself with a concept of AVD. That's basically an instance of the emulator - it has a bunch of settings, like the Android version to use and screen size and an SD card image.
You cannot install stuff "in the emulator" - you can only install stuff into a specific AVD. For that, you need to create and run an AVD first. For that, use "AVD Manager" from Eclipse or standalone.
Under the Android SDK folder in Explorer, run "AVD Manager". Choose an AVD (or create a new one if you don't have any). Select, click "Start".
Does the emulator show up when you run the following command?
adb devices
If not, you might have to boot up the AVD first, but if I remember correctly it should be starting it up by itself.
Have you created a new emulator for your project? And are you using Eclipse? Eclipse has an ADT plugin which is useful as it allows you to open the AVD manager through it. This plugin will give you this option in the Windows tool bar of Eclipse: Windows>AVD manager.
Create a new project based on the emulator and click the run button which will install your project onto the emulator. If you have an Android device I recommend turning USB development mode in your phones settings and running your project straight onto your device as it will be a lot faster. Hope this helps
this is what i did :
first run the "AVD Manager"-> choose an AVD -> click "Start"
immediately after
you click on "Start"
use command on cmd as,
adb install asdasd.apk
then in my case (Windows), asked to place .apk file in data/local/tmp/
what i did was copy and paste .apk file into data/local/tmp
and again use command
adb install asdasd.apk
then cmd prompted-> Success
You can also use command
adb devices
command for check whether emulator is in the list
Actually you may need to run AVD several times
I developed an application. Now I want to deploy it on real device. Can any body please tell me the steps and the requirements to deploy it on a real device.
Thanks
Deepak
There are multiple ways:
If you don't use eclipse, you can use adb tool. adb -d install PATH_TO_YOUR_APK_FILE
If you use eclipse, you can click run application in eclipse's launch menu. If this doesn't work, make sure you have "USB Debugging Mode" checked on your android phone. It's in the application menu.
You can export your package and sign it! And then browse to it to install.
I just copy the APK for my project out of the /workspace/project/bin folder, and use Dropbox to send it to my device. Then I install the APK from Dropbox client on the device. (No need for cables!)
Hook up your SmartPhone through USB-cable and set your phone i debug mode found in Settings > Applications > Development > USB debugging. Next - run your project in eclipse and chose your device.
make sure 'Run configurations' is set to manual, or this will fail if set to automatic and the target is a emulator. To change this behaviour, go to 'Run > Run configurations > Target' and set 'Deployment Target Selection Mode' to manual. Click 'Close' and try again.
FYI, if you're on a Galaxy Nexus, you need to fish around Samsung's website to find the driver installer. Here it is : http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
Note: If you're using adb -d install PATH_TO_YOUR_APK_FILE to install the apk on to your device,
you will need to run it from the adt-bundle-[magic]/sdk/platform-tools/ folder.
Better yet, add adb.exe to your $PATH, and you can run adb from your windows command line/ terminal.
Also, you have to set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If you're developing on Linux see official Android guide here