I have just installed the latest version of SDK and ADT .when i open the logcat i found that the whole logcat was filled with the following message.still i am not start any project on eclipse!
PgaSocketWriteAllHdipc: hd_ipc_send() failed
hd_ipc_send: not connected
I just 10 minutes the number of this kind of messages reached more than 10,000 and i am fed up with this. Please tell me how can i remove this message from appearing in the logcat.
I was getting this error and discovered that it was a problem with Bluestacks. Bluestacks is an Android emulator for the PC that I had recently installed. Once I quit Bluestacks (which always runs in the background) the problem stopped.
Update:
If you really need bluestacks you can filter this messages by creating logcat filter or just go "System tray (which display in lower-right corner, in windows) then right click on blustack icon and click on "quit" then your problem will solve.
Check this link . Looks like its an official bug related to the emulator system image.
i have also same problem but i knew that it create by blustack , so please go "hidden icons" (which display in lower-right corner) then right click on blustack icon and click on "quit" then your problem will solve , try it...
if any problem then ask me...
Bluestacks needs to be closed(COMPLETELY) for this error to disappear. Just to add to bala's answer, it is important to end all bluestacks processes. For this, see the processes from all the users in the task manager(assuming you're on Windows) & kill each bluestack process.
Uninstall Bluestack. In my case, just stopping the program (quit option) was not enought.
The problem was definitely Bluestacks.. Though I do suggest you to close Eclipse if you're considering to uninstall! The LogCat does not adapt quickly to environment changes and you might get the message even after you uninstall.
Related
I would like to be able to execute previous breakpoint that I've just stepped over
I know Android Studio is based on Intellij Idea where it's possible link here.
Similar question asking the same but its related to Eclipse IDE link here
There is also one answer that say's it's impossible.
link here
I can see "Drop Frame" button. But it's disabled by default.
So is there any way to enable this button?
The answer you are referring to regarding Eclipse is still valid for Android Studio:
You cannot step back to previous breakpoint in Android Studio because DalvikVM and Android Runtime (ART) do not support it.
You can enable the "Drop Frame" button if you debug JUnit tests as they run on a standard virtual machine (although I'm guessing this is not what you are after).
It is probably the only reason why the button exists.
Google's User Guide ignores it completely.
I'm fairly new to Android Studio, so I'm not entirely sure if this is what you are looking for, but have you tried playing around with the Frames window?
It allows you to backtrack the app's process, even reaching old breakpoints.
You cannot step backwards to a previous breakpoint that you have already chosen to continue past. You would have to create a saved state of your program at every break point to be able to do this, which would consume more memory than is worth designing the debugger with. You could although emulate this sort of functionality by forking your program everywhere you want to put a breakpoint.
-edit: This would be more feasible in eclipse than in android studio, as you would have to start another virtual device for android. say goodbye to your memory :p
Android 10 (Q) has supported this feature. It works well on my Pixel 2.
Please see below image
Using red down arrow to step in and blue up arrow using to step out.
:
Use ALT + F9 for next break point.
For me (macOs Sierra) it's Previous step cmd + alt + R
i had logcat, console etc showing in java portion of the ADT, one day i closed it, then it was not showing in the java portion of the ADT, i tried to open it as window/show view/logcat,but nothing happens,same happens with the case of console also, but i was able to open it up in DDMS using the same way. why it is not showing in JAVA? is there any fix for my issue, please help
In my Eclipse, there are two LogCat views. One says "deprecated". Perhaps you're clicking on the deprecated one and it doesn't work at all on your box anymore?
I read few topics about sdk manger and java issues but my problem doesn't correspond to any.
When i'm launching SDK manager.exe I get as output :
flashplayerplugin
As I was thinking that it was a Java issue I've launched sdk\tools\libs\find_java.exe (the .bat returns a blank line)
I get as output :
flashplayerpluginC:\Program Files\Java\jdk1.7.0_17\bin\java.exe
I really don't understand why this flashplayerplugin is coming in the output and crashing the program.
I had the same issue. My problem was caused by the tool airfoil. It wrotes a registry entry on:
HKEY_CURRENT_USER\Software\Rogue Amoeba\Airfoil\WhiteList\WhiteListItem_12
with entry:
name = *flashplayerplugin
Solution: just remove the * before flashplayerplugin and then SDK Manager.exe will start properly.
It's not an issue with Java, it's an issue with Flash. See this Super User thread. The poster there was able to solve it, but I could not and had to use System Restore to get back to the point before I updated to the latest Flash player. In my case I think the difference may have been Chrome's custom Flash player.
Simply un-installing Airfoil worked for me if this is an option for you.
Update Flash Player and Java...might help
I have installed all of the necessary parts and the ADT plugin for Eclipse. When I create an Android virtual device and start it, nothing appears. I get the box where the green status bar shows up and says 'Starting emulator for AVD'. However, nothing appears afterwards. No logs in the Console either....does anyone have any suggestions? thanks.
You will have more chances to debug the issue if you start emulator with “emulator” command:
emulator #avd-name
“avd-name” is your emulator image name as you created it.
And if you don't happen to have “emulator” command, try adding “android-sdk-linux_x86/tools/” (where android-sdk-linux_x86 is your android SDK installation directory) to your PATH.
I had the same issue for a bit and realized it was because when you set the skin it is default set to WVGA800 but for whatever reason it only worked if that was set to HVGA.
I found the problem is the graphic card. The emulator may not recognize you graphic card try again with another one.
For Ubuntu (I use Xubuntu):
Mine Android Virtual Devices didn't started because i used NVIDIA drivers for ubuntu.
After changing drivers to Nouveau it booted in 15sec.
Go to "Settings Manager" -> Software & Updated -> Additional Drivers
chose: "Using X.org x server -- Nouveau display driver (open source)"
NVIDIA F# U
http://www.youtube.com/watch?v=55XVnJ_0qhg
I had a similar issue.
Windows 7.
ADT Bundle 64-bit.
I was logging in to my PC with Active Directory credentials(corporate).
Emulator was not starting at all, after I tried many different things.
I switched to a local administrator login, and everything worked.
This is not necessarily the solution. I would rather want to know how to make it work on my AD account.
This also is related to the screen size of the emulator.
I created a fresh AVD with a 768x1280 display. This starts fine. Then I replaced the values of lcd.height, lcd.width, skin.name, skin.path in the config files to represent 1080x1920. After that the emulator does not start anymore.
I start the emulators inside a Xvnc session with 1360x768 pixels, but it also does not work in a Xvnc session with 3000x2000 pixels.
OK, maybe I'm dumb/blind, but in the docs it says "rebuild and restart the server." But I don't see a button to do this anywhere. Or from any contextual menu. And I can't find anything in their docs explaining how to do it. If I just try to start the app again, it gets angry because I already have App Engine running on the needed port.
Only solution I've found is to restart Eclipse... any other ideas? A screenshot of a button would help if possible. :)
In eclipse, there is a view that contains your Console. If you click on that, you will see the STDOUT and STDERR output of your running application. In the upper right, there should be a red box that will terminate the currently running program.
I have a different and possibly more productive solution for you. Like with most web development environments you probably want to change your source code and have Google Appengine server reload the new code for you.
You need some version of the traditional "touch" unix command (if you work on windows you can download a version from here).
Then go to you project properties, Builders and add a new build step as a "Program". Under "Location" enter the path to your "touch" command ("D:\bin\UnxUtils\usr\local\wbin\touch.exe" for example - on Posix systems just "touch" should be enough since it's already in your PATH) and in "Arguments" put something like "${project_loc}/war/WEB-INF/appengine-web.xml".
Also go to the "Build Options" tab and check "During auto builds".
"touch" will update the timestamp in you appengine-web.xml. When the App Engine server detects changes to you appengine-web.xml it will reload the app automatically. The load process is very fast so it can be done whenever you change any file in your project (which normally triggers the auto-build in Eclipse) - you can tweak the builder to only run when you change certain types of files.
I might add that the "little red box" is not always visible. It drove me crazy reading that same instruction but not seeing the terminate button until I discovered that the Console windows has "layers" that you can select from using the drop-down button on the far right of the controls for the Console view. You just need to go "back" to the console screen that says the server is running and you will see the little red terminate button.
The previous answer wasn't cutting the cheese for me. Upon first starting App Engine, the red square would be available above the text entry area. If I then clicked the run button again, then red square would go away and the console for the previous launch would be replaced by the console for the new launch. To manually stop the App Engine server, you can kill it from the terminal:
http://geekbrigade.wordpress.com/2009/02/26/how-to-find-and-kill-a-process-that-is-using-a-particular-port-in-ubuntu/
In short, "sudo netstat -lpn |grep :8888" and kill the service by process ID.
Strangely, adding Google Web Toolkit to the project made my App Engine launch show up in the Development Mode pane, where it could be easily be killed or restarted.
Just Click on Debug perspective (should be on upper right panel), select the instance of web application on Debug panel (if you don't show it, you could enable by menu Window->show view->Debug) and click on red box of view menu.
The best I've found is to setup the keyboard shortcuts for the console's terminate button, and the run/debug start/restart command. By default, you can enable Command-F2 to terminate, and Command-F11 to restart, its fairly painless. Make sure to enable the full debug menu group (click on main toolbar -> customize, etc)
If you include the gwt SDK in your project, the gwt development mode box contains a reload server button that will work just fine.