I cannot solve this error. The app seems to build just fine but, for some reason, can't seem to connect to the emulator. It always ends with "Lost connection to device" while installing. I also tried it on a physical device, still won't work. I have tried numerous possible solution, but none of them worked.
What I've checked:
Memory enough
No connection problem
flutter doctor -v shows no issues
The problem might be some plugin issue, but I don't know what or how to solve it. It also might be something else. If further code or information is required do let me know. Does anyone know how to solve this issue?
I have two times facing this issue, to fix it sometime it is a bit tricky.
It is coming from 2 possibilities:
Device you are using
Invalid SDK after accidentally updates its version.
But, if the problem is on your device, try this.
Reset the debug authorization on your device
Go to settings > developer options > revoke USB debbuging authorization.
If problem persist.
Check the disable adb auth timeout if it unchecked.
Modify the Logger buffer size to max (Mine is set off before, now it is 8MB, and changing this to 64k is working on small apps, but bigger apps need to log the debug process much bigger so it needs to increase its capacity).
Hope this can helps you mate!
What usually fixes it for me is to close the emulator, go into Android Studio Device Manager and 'Wipe Data' for that emulator. See image:
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.
I didn't know where else to ask this question. I can't find anything on the net about how android "deep scans" apps for threats. I'm debugging my own android game and everytime I install, android gives me the "deep scanning apps for threats" dialogue. This dialogue can stay up for hours, even overnight sometimes, or it can go away in just a 30 seconds or so. This only recently started happening, but with no updates to my device(that I know of). I can install once(taking five minutes to "scan") then change a line of code, install again and it takes half an hour. Does anyone know how I disable this or why it fluctuates?
This only happens for me when using Chrome, if I use the Samsung browser it just downloads the apk, then I have to drag the top bar and manually install the apk.
I fixed this in Chrome by doing 2 things, not sure which it was that resolved it.
options--security, unchecked and re-checked Unknown Sources.
options--security--device administrators and removed permissions from Lookout. (I think this was it)
FYI, once I re-enabled perms for Lookout, I can't get Chrome to redo the deep scanning so not sure if this is a good thing or not. I even went so far as to uninstall Chrome (or disable really) and re-enable from Google Play and do the full update, but Chrome still won't initiate the "deep scan" anymore. While this may not be an answer, I hope this helps somehow.
My problem:
I ran upon an awkward problem as I was developing my application. As mentioned in the title, every time I install my application (in run mode, not debug!) at start-up the waiting for debugger to connect.. message appears for 1-2-3 seconds, and the application starts.
What I want:
What I would like is to be able to start the application without that message appearing (it only started appearing in the last few days, and I can't remember changing anything related to debugging).
What I've tried:
I have tried setting the android:debuggable="false" but if I do this the debugger never attaches and the message never disappears.
I have also tried after installing to disable USB Debugging, but still no results.
Even if I kill the application and wake it up through an external source (it uses Google's C2D Messaging Framework) it still tries to run in debug mode on wake-up.
I have developed several Android applications and never stumbled upon this. Why wouldn't I be able to start the application in RUN mode? Is there any other way to install the application on the device, without hitting the run button in Eclipse?
I can post code-snippets from the AndroidManifest or from other parts of the code if necessary, but as I already mentioned I wasn't getting this kind of weird behavior several days ago.
Make sure your java files dont have any break point and Restart the device every thing should be normal.
I was experience the same problems where my application was always being run in debug mode. Restarting the device did the trick for me.
and make sure you are using
right click on project-->>Run As -->> Android Application
For me the solution was turning off the USB debugging from my device settings, and then turning it on again!
Much quicker than restart the whole device.
I had the same problem using Android Studio. Restarting my cellphone worked for me!
1. Open setting in ur phone.
2. Go to developer options.(About Phone-> Developer Option).
3. Disable the Developer option and again enable the Developer Option.
4. Enable USB debugging and Install via USB.
Run this command and the issue will be resolved
adb shell am clear-debug-app
Check if the option waiting for debugger is actived.
Settings -> Developer options -> Wait for debugger.
I think this it is new from Jelly Bean.
I'm assuming this is in the emulator and not on a device. If it is a device, ignore the rest. :p
It sounds like you saved a snapshot of the emulator as the debugger was connecting.
To fix:
1) Go to the AVD control panel, click on the emulator that's affected and hit start
2) when the window pops up, de-select "Launch from snapshot" and leave "Save to Snapshot" selected
3) Start the emulator.
4) Close the emulator
5) On the AVD control panel again start the emulator
6) Check "Launch from snapshot" again
That should fix things up.
EDIT.
Sorry for the wasted space, I read too fast and missed you talking about trying disabling USB Debugging. I have run into the above situation I describe before so I'll leave this answer posted for those who come along who do have such an issue.
"Wait for debugger"in Developer options may have been set to wait your application.
Do check once that you placed breakpoints. Run app once and if you get the same message do debug as-> debug configuration-> select the app which you need to run and select always prompt to pick device.It will work for sure. It may be stupid, but i faced this problem for a long time and i tried this and this helped me. And if needed restart your device. Thanks
For me, I use Android Studio 2.1.2I, I click on Menu Run > Attach debugger to Android process
There is only 2 lines
__device_name
____app_name
I just select app_name(want to run) and click OK then miracle happens.
I had the same problem.
But restart my Device or clear the Breakpoints don't worked.
I tried :
Run --> Attach to Android Process.
Select your package and press OK.
and it works :)
There was so many adb processes running ,I kill them all and its start debugging
You can also set your Android App as Debugging-App
Settings --> Developer Options --> set Debuging-App
there you can choice your app
You might have added your app in Select app to be debugged on your phone. In Settings -> Developer Options -> Select app to be debugged
To resolve this, go to Select app to be debugged and click on No apps
Your manifest file may contain following permission
Just remove this permission
<uses-permission android:name="android.permission.SET_DEBUG_APP"/>
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/