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.
Related
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.
From last 2 days I have tried everything uninstalled and installed eclipse, sdk and adt plugin several times, tried everything on every single post on stackoverflow and other forums but nothing is working for me. I am trying to run MyfirstApp hello world program on emulator but emulator always hangs on -
Starting activity com.example.myfirstapp.MainActivity on device emulator-5554
and never displays anything on the emulator screen. I waited hours to see if something happen, log cat show some processing though all the time. I have also seen something like -Can not find class java.lang.utilities etc in the logcat.
my computer configuration is as follow -
1.3 GHz Intel atom processor
1 GB Ram
160 GB hard disk
I was so motivated at start but this thing has frustrated me, any suggestion and help will be appreciated. thanks.
OK found solution to my problem. Hopefully it helps you as well. My app was running in the background. I unlocked the phone and my app was there the whole time.
http://androidforums.com/application-development/118051-hello-android-stops-running-eclipse-can-not-display-app-emulator.html
The emulator won't launch my apps even on a real device! I've tried every solution online, even reinstalling android sdk,ADT plugin. The app run SOMTIMES(4x to be exact) though, like awhile ago, when i got home i tried it again, and it run on my first try then i began working on the code again then i tried to run it, won't run again. Even basic apps like hello world won't run most of the time. I've set the run configuration to let me choose my device everytime, but even the device chooser wont show up(showed up once only), i tried waiting for 30 minutes(also tried the kill-server start-server) but it just wont run! my real device, or the emulator is listed on the DDMS perspective and there's nothing on console. please help, cause I've wasted 2 days for this already.
Have you also tried, taking the USB cable then disabling debugging and then enabling debugging and putting the USB cable back.
I remember this happen to me, so I did what I mentioned and surprisingly it works. Hope it work for you too.
Maybe you should try deleting your emulator and creating a new one. Make sure that all your settings are correct and that you are targeting the right OS version.
I've had quite a few problems with the emulator and wiping them and starting from scratch worked more often than not.
As for the real device, the first real hurdle is getting the right drivers so that your PC can recognize it, after that kill-server start-server usually does it. I'm surprise that didn't work for you.
I read all threads about this problem but the mentioned answers in the threads don't work for me. Can I find out which is the timeoutproblem with the help of a logfile? Is it possible that on my pc are drivers which have problems with the adb? How the adb works in detail if i start the debug process? Can anybody help me with this problem? I spent 16 hours of finding out what the problem is, but the only things I found out are that the problem has nothing to do with the installation of the eclipse, the adt plugin or the android sdk installation. Something with the connection between the emulator or my real device dont work.
If i create a new project and only change the appname or the text in the standard textview, then the app can be launched on the devices. If i do more changes for example create a new layout or something then the app wont work anymore. I am very frustrating in finding out whats wrong with the adb but till now i dont have luck to solve the problem. I hope someone can help me and others with the same problem. thanks.
In eclipse, you can increase the timeout. In Eclipse, Go to preferences>In the dialog select android>DDMS>increase the timeout value
you could also try to reboot your phone, or restart your adb server
adb kill-server
adb start-server
it worked for me :)
(increasing timeout value didn't work for me)
I have a problem with the Android emulator. After I run my application on a device it disappear from DDMS at some moment with no reason, even if it is still started. The only way to run again is to close the previous emulator and reopen it by running my application.
Do you have any solution for this strange error ? I must say that I can't deactivate my firewall if that is the problem. Also I tried to reset ADB but still doesn't work.
An answer for others that will come here looking for a solution.
You just need to restart ADB (kill-server and then start-server).
More details on how to do so: http://developmentality.wordpress.com/2010/09/13/android-disappearing-emulator-restart-adb-server/