I am trying to use to use the network profiler but I am unable to select a portion of the graph in order to see the content of the network packets.
I saw this answer and I activated the advanced profiling but as expected it changed nothing (as advanced profiling seems to be required only below API 26 ; my device is with API 29.
Do you see how to solve this problem ?
Thanks !
EDIT: it seems that there is a kind of bug in Android Profiler: sometimes I can select a range and sometimes I can't ; any solution to remove this bug?
Answer to my own question: it seems that the Network Profiler doesn't allow to select a range in order to see the connections when the app is executed in Android 10 emulator or device. I ran on Android 7 emulator and device and it works fine if you additionally activate 'Advanced profiling' in the Edit configuration menu of your target. Works perhaps also on Android 8 and 9, not yet tested.
Android Studio Not Showing My Phone for Run Application:
I want to run my developed application directly on my phone but I'm unable to run this. Because It's not showing in android studio. It also not working on emulator also. I already ready Google Development Guidelines(https://developer.android.com/studio/run/oem-usb.html). But these are not working for my system.
Have you enabled Developer mode on your phone?
If you haven't done yet follow these steps:
Go to settings -> About phone.
Tap on Build number 7 times and the developer option will be on.
If you have already enabled it then:
Go to Settings and find Developer options.
Check whether it is enabled or not.
Swipe down and find USB debugging. This option should be enabled. (Also enable Wireless ADB debugging if you're running app wirelessly)
Sorry for the late answer
I am also facing this issue couple of month ago, I had checked that I had enabled the USB debugging in developer but there is an issue with the Redmi phones that along with the USB debugging you will need to do the following
Go To Settings > Additional Settings > Developer Options
Enable USB debugging
Enable Install via USB
Disable Turn on MIUI optimization
On Select USB configuration select MIDI or File transfer (this is
what solved the problem for me)
also, keep in mind to give an RSA permission
you also check the link https://developer.android.com/studio/run/device?hl=ro
I have solved my problem on my own. The problem was in Android SDK. I'm using 2 windows in my same pc so I just used android studio on my another window then it's was working perfectly so I thought i have to try with changes that windows Android/Sdk folder in other windows which one I had problem. So I just copy (C:\Users{MyUserName}\AppData\Local\Android\Sdk) in getting the problem window and try again the android studio & Wawu... It's starting working. I hope it's will be helpful for you also.
I was using my phone earlier today for testing apps. I plugged it in later today to test another and eclipse wouldn't recognize it. I looked everywhere. I'm not sure why it wont work. Im using a Samsung Galaxy S3 device. All of the drives properly installed and updated. And debuggin is on.
This is not a problem with eclipse, devices get detected by adb(Android Debug Bridge that comes with the SDK) and the underlying driver(Install Samsung Kies to get the correct driver for S3), Ensure you have the correct drivers installed. Then it will detect successfully. Ensure USB debugging connected in Settings -> Developer Options
I have only used my phone to test for one day. And all day i had my phone connected cause i was teathering. I turned my teather back on and viola, problem solved.
Install google usb driver throu android sdk manager
I am using LG-P500. When I try to select it in the 'Android device chooser', Eclipse recognizes the phone but not the target. It says target "unknown". Because of this problem, I can't choose the phone as the Android device.
How can I get Eclipse to recognize the target?
Had the same problem with an LG phone. Rebooting it (phone) worked for me
One solution I am aware of is to just turn off and on USB Debugging on your phone. It also happens to solve a bunch of other device-not-recognized kinds of problems.
Follow these steps, if your device is recognised but the eclipse is stating it as unknown:
->open cmd
->go to the your android sdk directory --> Go to platform-tools
->adb kill-server
->adb start-server
this will definitely solve your problem :)
If you already installed USB driver and still your device showing as unknown then follow this solution. I had same problem with my MOTO G and this solution works fine for me
Check your device that
USB connected
and
USB debugging connected
or Check the following
The solution was to create a udev rule for the device. See http://developer.android.com/guide/developing/device.html#setting-up for how to setup a udev rule for your specific vendor device.
With the rule in place. Eclipse was able to launch and debug.
One simple trick works fine for me.
Disconnect device from PC
Tap revoke USB debugging authorization in phone setting
Reconnect device to PC
Tap OK for RSA authorization
The reason that my SCH-I535 device was not being targeted... is because I had the device plugged into a USB 3.0 port.
Once I plugged it into a 2.0, everything began to work properly.
Also try this, On your phone:
Go to "USB computer connection"
Select Connect as "Media Device (MTP)"
I tried these suggestions, but unfortunately, nothing worked.
What worked for me was:
close Eclipse
end the adb.exe process (using Windows Task Manager)
restart Eclipse (the device was now recognized in Android Device Chooser)
Go to Settings -> Storage -> Click on Top right menu button -> USB computer connection-> Check Media device(MTP) is enable or not
Do you have a driver for your phone installed on your computer, eclipse doesn't automaticly come with drivers for phones.
My problem solved by changing the cable. Nothing else worked for me.
For this problem I had tried disconnecting/reconnecting the USB cable, toggling on/off the USB debugging and relaunching Eclipse with no effect. Trying a different android device showed exactly the same eclipse errors, with two entries marked 'offline' and after disconnecting the USB connection it still showed one entry while nothing was connected.
My problem was solved by rebooting my computer and starting again. Probably ending the adb.exe programme (answer 4) would have done it too in my case.
GALAXY S5
I know this has been answered heaps of times already but if you have a Galaxy S5 then the turn off and turn on of USB debugging works to resolve this problem
When the phone is plugged in and the Eclipse window shows the "Unknown" icon...on the phone turn off USB Debugging then on again, it will then ask to allow that computer to connect, and you can say to always let it do so. Then it comes up OK.
create a udev rule for your development device.
I had this same issue, and I found this post, which fixed it for me.
Just download
http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip
unzip it and replace your "C:\Program Files (x86)\Android\android-sdk\platform-tools" directory with that
Credit goes to hack_on
Here is his post that helped me:
https://stackoverflow.com/a/15000565/342497
Thanks! :-)
If you cannot select the ok button when choosing a device it probably means you cant do things like adb logcat either in my experience.
I usually kill adb from Task Manager and it starts working. I noticed adb kill-server only sometimes works, and that there are often multiple processes called adb running... not sure if this is a bug or by design.
step 1 : rigth click on the project => properties => android => select api level that your device suport.
step 2 : restart your phone
work for me ...
Had the exact same problem. Working fine for over two years then all of a sudden this error pops up. The fix for me was running the SDK Manager.exe located here on my machine: C:\Program Files (x86)\Android\android-sdk
Turns out I did not have the ability to run on the device with Android operating system 4.2.2, only 4.0.2. After the SDK updated recognition worked perfectly. Turns out my phones operating system was updated and I forgot to update the SDK.
Had the same problem. Turns out I had changed my USB connection mode from MTP to MSC. Changing it back to MTP solved the problem. Thanx.
I used to debug w/o problems in my HTC One X, I broke the screen and until they repair it I managed to get an HTC One (M7 I think it's called internally).
I was unable to debug with this same problem, what actually happened is that besides having to follow a weird procedure to make Debug options appear (press 7 times in the firmware version in "About" menu) the phone was showing a message asking me to verify that the computer trying to debug on it was authorized.
I had not seen this behavior before in any the the phones I have used, not sure if this is a new functionality or simply it was not enforced on the other ones.
It is because that you didn't allow your phone to be debug by this computer.
Lock your screen, unplug and plug it then unlock screen click allow in the dialog.
KITKAT 4.4.2+ users, TRY to switch from ART to DALVIK or from DALVIK to ART. :) solved mine.
I tried different drivers, turning USB debugging on/off, rebuilding program with lower level API, killing ABD and restarting. Then I saw post on here regarding cable swap. Changed USB cable to Samsung USB cable and worked immediately.
you need to authorize the device to that computer. I was connecting the phone to my centos VM and kept getting this. I had to kill the adb server and then run it as root user. then you will get the prompt on the phone to authorize machine.
For me it worked by disabling and enabling the USB-Debugging option while ADB is running. Thanks for all the suggestions.
I had the same problem, restarting the PC worked for me.
(Debugging was already on, USB cable plugged in, fresh restart)
SOLUTION:
Switched USB connection from Media Device (MTP) to Camera (PTP).
When I did this it the PC installed device drivers, then phone gave me my computer's fingerprint and had a dialog concerning allow device to use USB Debugging. Accept. Device shows up in eclipse. All good.
(On Samsung Note II API 19)
Note: it's good habit to always try toggling the USB mode. I don't think it's the act of designating Camera (PTP), but the dialogs that are generated when doing so. Also, I had my phone replaced: I remember seeing this dialog before but not on this phone. Maybe there's an option somewhere to enable it per device?
I had the same problem. Turns out my device was prompting a dialog asking me whether I should allow connecting to my laptop or not. After clicking yes this problem went away.
The problem for me turned out to be insufficient rights of adb server.
I run Android Studio through remote desktop (used laptop to connect to a local, more powerful computer). Apparently i didn't have all the privileges when running through remote desktop.
After stopping adb server and restarting it with root privileges solved the problem.
sudo ./adb kill-server
sudo ./adb root
Edit:
Turns out i had to do this just the first time. Since the first time i don't have to do this anymore.
I am running Windows 7 32-bit Starter OS and I wonder if anyone would be willing to help walk me through the set up for the Java SDK, Eclipse "Indigo" IDE and Android SDK/ADT set-up as I have basically made a bloody mess of it.
I am working out of a couple of books whose instructions are more or less: "go to the download page and follow the instructions" and of course I have, but I keep hitting a brick wall and I am going to delete, re-download, and re-install the entire set-up starting from scratch in the morning.
I was using App Inventor, and had no appreciation of how much work was being done for me behind the scenes until I jumped off into this and will probably try to go back to it if and when Google completes the hand-off of the software to MIT and makes the sourcecode public like they are saying next year. Hmmmm.......
If I can work this out, I will make a click-by-click tutorial out of it and post it for others -who are bound to be having the same issues- to use... it's a rough thing to try to work out something starting from jump street and not knowing where to go when its holding up your entire operation.
I come looking for help -but will help back in return and have lots of stuff I can help with... GUI design is one area I see a lot of folks needing help with- simple little things sometimes make an unbelievable difference, etc.
Anyway if someone will help, point to help, or mention anything that will help, I will be glad.
I also have a list of compiler/console errors and warnings that I am getting when I try to import/run the example code from the books I am working out of -if that will tell anyone anything-. Also glad to receive e-mails about this from anyone.
Kind Regards, mark-p.
http://www.vogella.de/articles/Android/article.html is one of the best step by step on-line instructions on how setup your development environment
I successfully installed Android SDK in my Windows 7 machine last week and that too with all the latest updates.
http://developer.android.com/sdk/installing.html is itself a good resource. These instructions are applicable to the latest JDK version 7, Eclipse Indigo, and SDK Version 15.
The basic steps would be:
Download Install JDK 7 from Java site.
Download Eclipse Indigo as you would have done already.
Install the Android SDK from http://developer.android.com/sdk/index.html. Use the latest installer available ( Currently installer_r15-windows.exe). Note that this installation will install the sdk into Program Files\Android by default.
Run Eclipse. Go to Window -> Preferences. You will see a Android tab on the left if your SDK was installed properly.Ensure that your SDK location is same as your actual installation path.
5.Install the ADT Plugin for Eclipse.Go to Help->Install New software. Check http://developer.android.com/sdk/eclipse-adt.html#installing for detailed instructions.
Now go to Window-> Android SDK Manager.This should launch a window and the SDK Manager will try to retrieve the list of installed/available packages from the Google repository. Make sure that your internet connection is correct. If your are using a proxy server, go to Tools of SDK Manager and give the IP and port of the proxy server. I believe I wasted a lot of time since I missed the proxy settings. Also you may need to force https:// to http request.
The above step should list out a set of packages including Android 4.0(API 14) which is the latest platform available today. Select the different packages and on installation and restart of Eclipse, you should be ready to start with your Hello Android program.