I'm using Windows 10 64bit.
So I downloaded Android SDK for a project I need to do for college, and when I'm installing everything goes fine, until (what seems to be) the end.
When it's about to finish I get a blue screen saying something like "error occurred, collecting crash info, we will restart the computer for you when finished" or something like that. Below that it says something like "WHEA_UNCORECTABLE_ERROR". Also when it finishes collecting the info (it gets to 100%) it doesn't restart like it says it will, I have to shut down the computer my self and turn it back on.
Does any one know what is going on or how to fix it? I'm kind of screwed if I don't find a solution fast.
Thanks in advance.
You can try the following:
-Run the installer with compatibility mode for windows 7/8
-Re-download the SDK to avoid corrupted files in the installer
-Download the Android SDK from another source, or a different version of it.
If nothing works out, it might be a problem with your computer, which would require more research to specify whats the problem. You can try to run the Windows Recovery Tools to try and fix it.
Related
Okay, so I just installed Android Studio on my new (to me) Macbook Pro. It's a mid 2014 model with i7 and 16Gigs of ram. It's fully updated to what Apple will allow, which should be plenty for Android Studio.
I've setup Emulators and coded with them using Flutter through VSCode no problem.
When I go into the terminal and run adb, all I get is Segmentation fault: 11. That's it, nothing else. It simply will not run. I plug my phone in, and of course it's not detected. I can run adb devices, which just shows none.
I've tried googling, but it seems Segmentation fault: 11 is super popular, so I can't find my way through the weeds to anything related to what I'm experiencing.
So, I've gone into Android Studio and forced it to remove the platform tools and reinstalled them through the Brew command, same thing. Is it that the latest version is incompatible with Big Sur? Should I install an older version of Android Studio? Has anyone else run into this problem? I'm hoping I'm simply overlooking something simple, but I can't for the life of me figure it out. I'm hoping to get a bit of feedback before I have to dump the whole thing and put an older version on. I have the emulator working nicely, I just want to use a physical device too.
Okay, so maybe this will help a fellow adb noob out. I recently (finally) figured out my problem, sort of. At least it's working now, so that's all I care about.
Okay, so, the first thing I ran into was that I was using a power cable, not a data cable. Rookie mistake there. So, once I had that head smacking realization, at least my phone started acting normally with the debug request.
That is, once I ran across an article the pointed out adb start-server existed. I mean, it makes sense. Maybe I'm wrong, but I would have figured that just typing adb into the terminal by itself would try and start the adb server. So, once I got that working, it finally connected with just the minimum pain that seems to go along with these types of things.
Still, I cannot understand why calling adb by itself causes a Segmentation fault, but I'll leave that up to the people who work on Android Studio to figure out, cause I'm moving on.
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.
My device is no longer allowing me to install apk files manually. The install screen shows up like normal, only it will not allow me to click the install button. I am allowed to click the cancel button, so the screen is still responsive and not lagging or frozen, but there are no error messages or any kind of UI element telling me what the problem is.
I've previously installed apps this way and I can't think of any settings I've changed since, especially not the kind that would break this. Any advice would be greatly appreciated!
Running Cyanogenmod 10.2/Android 4.3.1 (Jellybean), install from unknown sources is checked. Screenshot below:
Try these steps:
1). Goto the package installer app and clear data and then try to install the app.
2). Boot to recovery, wipe cache and dalvik cache, reboot and then try to install.
If you are able to install from playstore then this should fix your problem. I hope it helps.
So I finally figured this out. I was searching around and found someone with the same problem here. Their problem was Talkback, but I started experimenting with closing my running apps and Twilight turned out to be the culprit. Not sure what Twilight had to do with this...but can now install from unknown sources again.
NB: It's enough just to pause Twilight, you don't need to uninstall/disable/clear cache or even force stop it.
I've done everything to the 'T' in regards to installing the Android SDK/ADT. I've tried all methods to resolve this (adb kill, wipe data), but still nothing.
When I run it from the SDK manager, the loading process works, but once it is done, a flash of the emulator appears then quickly disappears.
Sometimes after it loads, nothing happens.
At the worst when it loads, I get the "too many emulator instances are running on this machine. Aborting" message.
I want to start making apps, but this seems to be the only thing stopping me!
Eclipse Indigo; r12, Windows 7 (64)
If you have Windows Firewall (or another software firewall) active, try temporarily turning it off and then running the emulator. If that clears up the problem, then you need to teach the firewall how to open up the ports the emulator needs.
Go through your services and kill anything you find from it, including the java runtime, then run the AVD Manager as Admin and start the emulator from there, that should fix it.
I try to always make a habit of running Eclipse as Admin too because it's needed for the Emu to run properly.
I am using IntelliJ IDEA (10.5) for Android development with latest Google USB Driver (version 4) for debugging. After some time of development in IntelliJ IDEA when Android device (Nexus One) is connected via USB, the computer (with Windows 7, 32 bit) freezes. No blue screen just freeze. Everything is visible but screen is not updating. I have to restart the computer.
Is anyone experiencing similar issues? Any solutions?
Sorry, not sure how to comment on your original post (the field is not displayed).
I'm experiencing the same issue and I'd love to determine a solution. It's very annoying!
I use Eclipse (Windows 7 64-bit) with a Nexus One (2.2) and my PC will randomly, completely freeze. The mouse pointer locks up, Caps Lock button (and others) don't toggle, touch pad doesn't react, etc. No blue screen and nothing is ever written to the system's event log. I have to physically shut down the machine and restart it each time.
At first, it happened in the same manner for me -- developing within Eclipse. I noticed it didn't happen on compile or debug launch, more during development (again, randomly). Then I noticed it started happening when Eclipse wasn't open at all. That's when I started to suspect a driver or similar issue. But I'm not sure how to troubleshoot further from here.
If anyone has ANY insight into this issue, it would be greatly appreciated.
UPDATE: Incorrectly reported N1 version as 2.1 -- corrected to 2.2
Idea is known to have long GC pauses sometimes - it may freeze completely for some time. And it takes even longer if it goes into swap - in this case, whole system may become unresponsive. See this issue and discussion in forums.
So, if it is indeed your case, try using statically-compiled version from here - it's proven to work faster.
It sounds like OS/Hardware problem