Develop Reference

Android app slow when installed from Android Studio, but runs fine when installed from adb

I'm not really sure how to word this.For some reason when I install an app that I'm working on from Android Studio it runs very slow (when an option is pressed it takes 10-20 seconds to register). But if I install the app from either my coworkers Android studio or adb from my own machine it works fine.
My specs are:
OS: Windows 10
Android Studio Version: 3.0.1
Phone OS: Android API 24
It was working fine this morning, but during the course of the day, something has happened. Has anyone run into this sort of problem before?
I'm using a Samsung Galaxy S8 physical device. I have tried a factory reset on the phone which worked for one install after I changed some things I'm back where I started. I have also restarted both the machine and phone multiple times. I'm at a loss as to what is going on. If you guys need any more info let me know. Also INSTANT RUN IS NOT ON.
EDIT: I'm at a total loss as to why this is happening. I've tried everything from restoring the phone, reinstalling Android Studio, changing wires, changing settings, but nothing is working. If anyone has a suggestion I will gladly try anything.

I've finally found a solid solution to my problem. I'm positive now that something went wrong with m usb drivers for windows 10. I went to this page https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-slow-usb-30-transfer-speeds/a5e1eebb-74bb-4777-8902-5131f3e8ec3e and I completed the steps in method 1 and that did the trick for me. it took a while to find this out, but hopefully, someone else will find this helpful.

Have you compared your yesterday build and today build which is making your app slow. Any Significant change in code?

Have you set up breakpoints or similar? Some debugging options can significantly slow the app down at runtime. When this happens, if you disconnect the phone from ADB - e.g. pull out the cable - and it speeds up again, then it's likely related to your debug connection to that particular instance of Android Studio.

Android AVD With HAXM Takes 1 Minute to Load APK Every Time, Normal?

Man, I'm getting frustrated.
I just re-installed the Android ADT bundle because my AVD speeds were horrible, we're talking 2-3 minutes to load an AVD with a new APK, crazy. After the re-install, I found HAXM.
Installing HAXM has made a HUGE difference, however, I'm finding that the build, upload and install of my app through Eclipse and the AVD is still taking 1 minute! This is terribly frustrating as I like to make subtle changes, test, and then continue. Imagine a minute wait between each build, ugh...
Anyway, is this normal? If so, how do you cope with it, are there any tricks as far as .ini settings etc? I really appreciate it, I'd love to have sub 20 second load times, I think that is reasonable as my actual phone loads in less than 5 seconds.
Please let me know, thanks!
EDIT: Ok, it appears that this is a disk utilization issue! Sometimes, when the emulator is installing the APK disk read/write hits 100% capacity, it's like the emulator is writing or reading out of control, yet only 0.1 mb/s is being written... Very strange..

You can use genymotion emulator. It works very fast compared to any emulator offered by eclipse or android studio. You can download it for free.

Android emulator just won't start

i really need some help with this..i have done a lot of search and googling but none of the solutions worked out for me..
until 2-3 months ago i could get the emulator running at a decent time..but lately the emulator won't start..it will stay forever in the "android" screen..
i ve uninstalled and reinstalled sdk 2-3 times
after uninstall i also had system checked and restarted for potential errors..but no result
i ve installed all the necessary files, images etc..
i ve tried cmd launching no difference..disabling boot aniumation, still nothing..
i even left the emulator all night long to load but still no success..
the only solution left that i can think of is fresh install of the windows from the scratch.. :(

can you run
adb -e logcat
Command, try to see if there's anything meaningful displayed there?
That command accesses the log for the currently running emulator.
It might shed more light on the boot loop.

Android Eclipse Plugin Too Slow

I'm currently on a Windows 7 box with 1.83GHz processor and 1 GB RAM. I used be able to use all applications with no speed issues. I recently installed Android Plugin in Eclipse Helios and now Eclipse has slowed down badly. Running projects/creating projects/saving code changes all takes 3-4 minutes to happen. When the emulator is launched, it takes a good 10 minutes to be able to use my app. What is causing Eclipse to slow down ?? Wasting a lot of time on this. Please help.
Thanks in advance !

Your system should be running on the edge of the limit when you have Eclipse and the Emulator running. If possible work on a device or check the CPU/RAM usage while working. You should be able to see where the bottleneck is.
If you have Windows XP somewhere, I strongly recommend to switch back to XP...

Usually when your using programming envionments such as eclipse it is very taxing on your computer. The emulator taking up to ten mins to run is not shocking. I also had the same problem but if you have an android device you can use it to test your programs (its almost instant compared to the emulator.)

Having a problem loading the Android Emulator in Eclipse. All it says is ANDROID_. Any suggestions?

I went through the simple hello world application on the android developers forums to an absolute T. But, when I start the emulator all it comes up with is a large black screen that just says ANDROID_. The '_' is flashing. Does anyone know what may have caused this or why it is not working.

It can take a while to start. Remember it is emulating an ARM processor so that can take a while depending on the specs of your machine. Start it and give it 5 min. If it hasn't come up by then you may want to close and restart. While it is starting up, if you open ddms you can follow what is going on in logcat.
Good news is that if you enable snapshots, once you get it started and saved (it does this on its own). Subsequent starts should be pretty quick.

For some reasons, the android emulator does not work properly on any of the laptop's i have. It lags even on my high end laptop with 4 gb Ram, i5 processor and 1 gig graphics processor, so i connect my phone using usb cable, enable debugging mode and run the app on the phone from eclipse. You will need a working adb connection as stated on android developer website though. It works pretty good and is way better than using an emulator. :)

It takes about 3 mins for the emulator to load on a laptop. Wait for about 5-6 mins if not. close it.
In case when you restart still you get the same, go to AVD Manager delete the image and create a new one.

As the others have said, the emulator is very, very slow to start up. It can get wedged on startup for me, every now and again, but shutting it down and trying a second time almost always works. And yes, you can leave it running the whole time, but note that Eclipse and/or ADB can get wedged as well. You'll see logcat stop updating inside of Eclipse. I can usually get it restarted by doing
adb kill-server
adb start-server
Sometimes, just doing an adb logcat on a command line will get things moving again. Good luck.