Today I got a problem .There is neither usb device nor virtual device in the dialog.
But I can find device with commond.
Maybe there is something wrong with Android Studio.
How can I fix the problem?
After a day,I found the problem. The error is
WARN - #com.android.ddmlib - Unable to open connection to: localhost/30.129.144.64:5037, due to: java.net.ConnectException: Operation timed out
So I add localhot 127.0.0.1 to host file，and then restart AS.Everything is OK
Related
I currently cannot setup my Android Studio since it seems not to be able to download packages from google, particularly from "https://dl.google.com/...".
Details:
Updating the IDE, download SDKs, etc. does not work and ends in a "Read timed out" error
According to the idea.log file, it looks like this
2022-12-30 08:19:42,842 [ 132503] INFO - er.configure.SourcesTableModel - Downloading https://dl.google.com/android/repository/addons_list-5.xml
2022-12-30 08:19:43,143 [ 132804] INFO - s.RepoProgressIndicatorAdapter - Downloading https://dl.google.com/android/repository/addons_list-5.xml
2022-12-30 08:21:02,106 [ 211767] INFO - er.configure.SourcesTableModel - IOException: https://dl.google.com/android/repository/addons_list-5.xml
2022-12-30 08:21:02,106 [ 211767] INFO - er.configure.SourcesTableModel - java.net.SocketTimeoutException: Read timed out
2022-12-30 08:21:02,417 [ 212078] INFO - s.RepoProgressIndicatorAdapter - IOException: https://dl.google.com/android/repository/addons_list-5.xml
2022-12-30 08:21:02,418 [ 212079] INFO - s.RepoProgressIndicatorAdapter - java.net.SocketTimeoutException: Read timed out
The file IS accessible from within my regular browser
I do not require any proxy, nor there is any proxy set up in my network setup
If I go to Setting > Appearance & Behavior > System Settings > HTTP Proxy and do "Check Connection"
it perfectly works for "https://www.google.com"
but it does NOT work for "https://dl.google.com"
Does anyone have an idea what that could be? Android Studio behaves as if it would deal differently with this domain AND/OR "dl.google.com" acts differently for the built-in HTTPS client in contrast to a regular browser.
I tried
Uninstalling/Reinstalling various versions of Android Studio (-> same issue)
I also made sure that there are no leftovers of any configuration between the different versions
I also removed anything that has to do with gradle
Accessing the domain from within different browsers (-> no issue at all)
Deactivated the Windows firewall (-> same issue)
Started Android Studio with administrator privileges
I tried to connected Android Auto DHU r1.1 in windows with the Android Emulator in Android Studio，but got this error.
In emulator:
Communication error 8.
In desktop head unit:
Shutting down connection due to authentication failure.
I have checked the time, time zone and got the newest android auto.
adb forward tcp:5277 tcp:5277 (set adb proper port)
Stop head unit -> Start head unit (on the phone)
Launch desktop-head-unit.exe
and read https://developer.android.com/training/cars/testing#running-dhu
Work fine for me
I have upgraded an Android Project from 3.2 to 3.4.1 and now I have gradle Problems.
The only indication is the bar at the top
and a message in the Event Log.
Gradle sync failed: EventQueue.isDispatchThread()=false Toolkit.getEventQueue()=com.intellij.ide.IdeEventQueue#34e0424
Current thread: Thread[ApplicationImpl pooled thread 19,4,Idea Thread Group] 388194366
SystemEventQueueThread: Thread[AWT-EventQueue-0,6,Idea Thread Group] 847161915 (1 s 526 ms)
I have cleaned rebuilt project.
Clicking on Open Build View -> nothing happens.
Log File contains:
INFO - e.project.sync.GradleSyncState - Finished source generation of project 'Chronica'.
2019-05-26 10:04:57,336 [thread 126] INFO - ule.android.SdkModuleSetupStep - Set Android SDK 'Android API 26 Platform' (C:\Users\andreas\AppData\Local\Android\Sdk) to module 'LVLLibrary'
2019-05-26 10:04:57,340 [thread 126] INFO - ule.android.SdkModuleSetupStep - Set Android SDK 'Android API 28 Platform' (C:\Users\andreas\AppData\Local\Android\Sdk) to module 'app'
2019-05-26 10:04:57,425 [thread 126] INFO - e.project.sync.GradleSyncState - Gradle sync failed: EventQueue.isDispatchThread()=false Toolkit.getEventQueue()=com.intellij.ide.IdeEventQueue#34e0424
Current thread: Thread[ApplicationImpl pooled thread 126,4,Idea Thread Group] 812028699
SystemEventQueueThread: Thread[AWT-EventQueue-0,6,Idea Thread Group] 847161915 (852 ms)
2019-05-26 10:04:57,425 [thread 126] WARN - ject.sync.ng.SyncResultHandler - Gradle sync failed
com.intellij.openapi.diagnostic.RuntimeExceptionWithAttachments: EventQueue.isDispatchThread()=false Toolkit.getEventQueue()=com.intellij.ide.IdeEventQueue#34e0424
Current thread: Thread[ApplicationImpl pooled thread 126,4,Idea Thread Group] 812028699
SystemEventQueueThread: Thread[AWT-EventQueue-0,6,Idea Thread Group] 847161915
at com.intellij.openapi.application.impl.ApplicationImpl.assertIsDispatchThread(ApplicationImpl.java:1133)
at com.intellij.openapi.application.impl.ApplicationImpl.assertIsDispatchThread(ApplicationImpl.java:1122)
at com.intellij.openapi.fileEditor.impl.FileDocumentManagerImpl.saveAllDocuments(FileDocumentManagerImpl.java:289)
at com.intellij.openapi.fileEditor.impl.FileDocumentManagerImpl.saveAllDocuments(FileDocumentManagerImpl.java:282)
at com.intellij.openapi.vfs.encoding.EncodingProjectManagerImpl.tryStartReloadWithProgress(EncodingProjectManagerImpl.java:361)
at com.intellij.openapi.vfs.encoding.EncodingProjectManagerImpl.reloadAllFilesUnder(EncodingProjectManagerImpl.java:366)
at com.intellij.openapi.vfs.encoding.EncodingProjectManagerImpl.setEncoding(EncodingProjectManagerImpl.java:180)
at com.intellij.openapi.vfs.encoding.EncodingProjectManagerImpl.setDefaultCharsetName(EncodingProjectManagerImpl.java:408)
at com.android.tools.idea.gradle.project.sync.validation.android.EncodingValidationStrategy.fixAndReportFoundIssues(EncodingValidationStrategy.java:83)
at com.android.tools.idea.gradle.project.sync.validation.android.AndroidModuleValidator$AndroidModuleValidatorImpl.fixAndReportFoundIssues(AndroidModuleValidator.java:63)
at com.android.tools.idea.gradle.project.sync.ng.AndroidModuleProcessor.processAndroidModels(AndroidModuleProcessor.java:63)
at com.android.tools.idea.gradle.project.sync.ng.SyncProjectModelsSetup.setUpModules(SyncProjectModelsSetup.java:143)
at com.android.tools.idea.gradle.project.sync.ng.ProjectSetup$ProjectSetupImpl.setUpProject(ProjectSetup.java:69)
at com.android.tools.idea.gradle.project.sync.ng.SyncResultHandler.setUpProject(SyncResultHandler.java:136)
at com.android.tools.idea.gradle.project.sync.ng.SyncResultHandler.onSyncFinished(SyncResultHandler.java:88)
at com.android.tools.idea.gradle.project.sync.ng.SyncResultHandler.lambda$onCompoundSyncModels$6(SyncResultHandler.java:268)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:314)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Howto analyse this, How to get a meaningfull message. Its very frustrating to be blind every upgrade of Androidstudio.
Is there a way to execute the sync by console / terminal ?
Update
I could restrict the case. I found out this happens only if I am adding a android library (module). I can't understand why thi happens.
Update 2
I found the solution for me. The upgrade process added the following into my gradle script, which caused the problem. After removing it worked:
compileOptions.encoding = 'ISO-8859-1'
productFlavors {
}
The question is still open. How can we analyse this kind of issue in a professional way. I had to compare files without knowing without any contextual path.
It was good for me.
Download some components:
I used this trick to fix the problem I had with my gradle. First get a good internet connection and go to your local disk C: \Users \YourUsername. You will see a .gradle file there. Delete it and run android studio again for it to download everything again.
Though not in Android Studio 3.4.1, but I got a very similar error message in a newer version (4.1.3), so I ended up here.
For me the problem was that Kotlin version that is used for Gradle differed from the IDE plugin version.
The message was:
Gradle sync failed: EventQueue.isDispatchThread()=false Toolkit.getEventQueue()=com.intellij.ide.IdeEventQueue#3e2d155f
Current thread: Thread[ApplicationImpl pooled thread 6,4,Idea Thread Group] 219783907
SystemEventQueueThread: Thread[AWT-EventQueue-0,6,Idea Thread Group] 255359391
Make sure that ext.kotlin_version in your buildscript is the same as the plugin version (File/Settings/Plugins in Android Studio 4.1.3).
I am using Mac OSX El Captain with Android Studio 2.2.
Android Studio start to don't show Android devices suddenly. I try to kill adb server and start it again and this errors appear on terminal.
List of devices attached
daemon not running. starting it now on port 5037 *
adb E 1165 84563 usb_osx.cpp:307] Could not clear pipe stall both ends: e0004051
adb E 1165 84563 usb_osx.cpp:289] Could not find device interface
daemon started successfully *
When I try to kill server twice for understanding the issue it gives this error message:
error: protocol fault (couldn't read status): Connection reset by peer
Try restarting your Mac and devices. I ran into a similar error and restart got rid of it :)
I remote(chrome remote) to my desktop which runs android studio. When I try to run the emulator from android studio, i see the window with the virtual device open. But the device doesn't power on. This is not the behavior when I use the desktop directly to run the android project. Could this behavior be because of the remoting? If so how do i change it?
My need is to work on android studio on a remote connection, if there is a way to achieve it, kindly advise.
This is the AVD log
C:\Users\xxx\AppData\Local\Android\sdk\tools\emulator.exe -avd Nexus_5_API_21 -netspeed full -netdelay none
emulator: device fd:1228
HAX is working and emulator runs in fast virt mode
creating window 61 83 462 820
logcat
04-29 12:06:39.077 1966-1966/com.example.xxx.four4 E/libprocessgroup﹕ failed to make and chown /acct/uid_10053: Read-only file system
04-29 12:06:39.077 1966-1966/com.example.xxx.four4 W/Zygote﹕ createProcessGroup failed, kernel missing CONFIG_CGROUP_CPUACCT?
04-29 12:06:39.078 1966-1966/com.example.xxx.four4 I/art﹕ Not late-enabling -Xcheck:jni (already on)
04-29 12:06:39.183 1966-1986/com.example.xxx.four4 D/OpenGLRenderer﹕ Render dirty regions requested: true
04-29 12:06:39.186 1966-1966/com.example.xxx.four4 D/﹕ HostConnection::get() New Host Connection established 0xa607f4c0, tid 1966
04-29 12:06:39.319 1966-1966/com.example.xxx.four4 D/Atlas﹕ Validating map...
04-29 12:06:40.050 1966-1966/com.example.xxx.four4 I/Choreographer﹕ Skipped 42 frames! The application may be doing too much work on its main thread.
04-29 12:06:40.184 1966-1986/com.example.xxx.four4 D/﹕ HostConnection::get() New Host Connection established 0xa607fa60, tid 1986
04-29 12:06:40.231 1966-1986/com.example.xxx.four4 I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-29 12:06:40.469 1966-1986/com.example.xxx.four4 D/OpenGLRenderer﹕ Enabling debug mode 0
04-29 12:06:40.521 1966-1986/com.example.xxx.four4 W/EGL_emulation﹕ eglSurfaceAttrib not implemented
04-29 12:06:40.521 1966-1986/com.example.xxx.four4 W/OpenGLRenderer﹕ Failed to set EGL_SWAP_BEHAVIOR on surface 0xa6083580, error=EGL_SUCCESS
04-29 12:07:12.637 1966-1973/com.example.xxx.four4 W/art﹕ Suspending all threads took: 13.570ms
Thanks.
I have the same issue using a remote desktop. I solved it using another remote access application TeamViewer (http://teamviewer.com)
Using TeamViewer you can run any Android Emulator like x86, x86_64 or arm.
The Android emulator is not using all of your cpu capabilities but rather a single thread and my guess is that the remote desktop and the emulator are sharing the same thread thus preventing from your emulator to run while using the remote desktop. the solution is to use a stronger cpu or a different remote desktop as user2839592 said.