I am having problem with Android Studio where my Andrdoid virtual device gets terminated for no clear reason!
I tried searching all over internet and Stackoverflow but nothing seemed to work for me.
Tried everything from installing just SDK, Buildtools, Envoirnment-variables, to completely deleting and reinstalling android studio but issue persists. Ps it's not space issue as i have plently available
Solution
it's temporary fix but works!
open Android Virtual Device manager.
click 3dots(located right after the pencil)
click show on device
delete the cache file. (there will be file named cache)
There will be file named config.ini, (open it and change hw.ramSize=3068 hw.cpu.ncore=1 ) cores and ram
you can also change ram and cores from that pencil and going to advanced.
after that do a cold start and wait patiently!! it will load up after a while! it works ....
i just did it.. but i have to do it everytime...😒
Related
Relatively new to intermediate level Windows user here. I recently installed a game which kept restarting (automatically) every few seconds even after I closed it every few seconds. Windows (I use Windows 8.1) kept trying to open the .exe even after I uninstalled. I tried deleting a couple of registry entries of it (I guess I deleted a dll registry related to it)
After deleting a couple of registry entries
but it still keeps trying to open it. What can I do about it?
These guys keep coming up as I close them
Currently doing a CS course. This is my first question on stack overflow!
EDIT: This window keeps popping up every few seconds. (I have uninstalled it)This one. The game is Battlezone(1998) from Microsoft which itself is legit. I found it on a really old CD which I found in my house recently and I just installed it. It is clear on Avast Antivirus. Nothing suspicious there in Task Manager or in Startup
Try using the Taskmanager to stop any process that is related to that programm.
If you have uninstalled it and the programm still starts it probably is still installed -> the .exe file hides somewhere.
Try find and delete it manually.
You can check if you have a system tray icon as well, some programms don't close if you close them but minimize into a system tray icon. These can often be closed using right click -> close.
Does the programm start automatically after pc start? -> check your autostart folder and the autostart tab of your taskmanager and remove it.
Anymore stuff you can provide us with? -> which game, screenshots, you sure it's not maleware?
I have a Windows 10 64-bit PC (fresh install, not an upgrade).
When I run the setup file (web or offline alike) in order to install Visual Studio (2013 or 2015, Community edition), all I get is a small black rectangle on the screen (which I later found out that this is actually the title of the setup popup window), without the actual window of the installation.
I have tried it also after a reboot, and with various "versions" of the installation files (web, iso, standalone), but it's always the same situation.
What can I do about it? VS is my main development tool and I really need it on this computer as soon as possible.
Similar problem here. Program install ok but display blank screen after launched.
Problem solved when I changed my Nvidia graphics's global 3D setting to integrated graphics.
Right click desktop
Select Nvidia Control Panel
Select Manage 3D Settings
Under preferred graphics processor, select integrated graphics.
Apply.
If you are using a laptop with an external monitor, try unplugging it and using your primary monitor to launch. This worked for me. Laptops often have dual graphics cards and I believe we're hitting some issue with the way the Installer for VS was written (likely WPF)
Once I launced it and started the installation, I could safely plug my monitor in and it kept working properly.
I'm using an AMD GPU, It was a blank white screen but when I hover the mouse over it, I can see the text events
By the way
I went to my AMD Radeon Settings and saw that vs_installershell.exe and vs_setup_bootstrapper.exe were added automatically to the Switchable Graphics list
they were with Not Assigned Option which usually is like High Performace Option
means It would run it with my ATI GPU.
So I clicked on them
Selected Power Saving Option (to work with my Intel GPU)
Which worked and I can see the window of visual studio installer back
after restarting visual studio installer for sure.
whether is your graphics card, just turn on power saving for it.
Had the same issue. Since this topic is not accept any answare, there is one from https://developercommunity.visualstudio.com/content/problem/150888/visual-studio-installer-shows-blank-screen.html
Try to open installer as Admin.
You will probably have blank screen. Do not close it!
Open installer once more.
Hope it help other people with same issue.
the same thing happened to me, i didn't do anything i just waited for it and it started showing it's status, i suggest you close other running programs to avoid conflicts and performance hindering, and try it again.
This seems like a very shoddy issue. I've run into this problem too, and I tested all solutions that I came across online. These all work:
Running the installer as administrator, which is a blank screen. Leave it open and run a second instance of the installer, which will not be blank (doesn't need to be run as administrator the second time.
Changing screen settings so that the laptop screen is not being used.
Downloading the AMD Settings application, and setting vs_installershell.exe to run on powersaving mode. Restart the installer after saving the settings.
Use a default graphics driver instead of the AMD one.
I had the the same problem in my laptop. The temporary solution is: start the installer only without the battery, if installer starts you can connect the cable, it works fine.
I had to run integrated graphics rather than my Nvdia. That solved it for me.
Remember to change it back when programming in OpenGL and DirectX otherwise you may get a list of messages staying that nothing works.
I had the the same problem in my laptop. The work around is, in device management, remove the amd graphics or start the installer only with battery.
I am getting the following error when I try to launch Xamarin Android Player.
I have tried reducing the allocated memory in Virtual Box, as suggested in some other forums but no results.
I am using Virtual Box V5.0.4.
Kindly guide on resolving the issue.
The Android is working in Virtual Box when I change
Settings>Network>Adapter1>Attached to
to NAT by going into the in virtual box but as I launch the Xamarin Android Player or GenyMotion. it resets it to Host-Only Adapter and the emulator stops working.
Check if you have Virtualization Enabled in your BIOS settings.
Another workaround:
Uninstall previous versions of XAP.
Open up VirtualBox and remove all of the XAP devices, choose to delete files.
Open the VirtualBox Virtual Media Manager and ensure there are no data.vdi, system.vdi or sdcard.vdi files remaining. If there are,
release and remove them.
Delete C:\ProgramData\AndroidPlayer
Source: https://bugzilla.xamarin.com/show_bug.cgi?id=24817
I would update virtual box to 5.0.20 from here try it again.
If that doesn't work then try reinstalling Xamarin Android Player.
If that doesn't work then I would recommend trying GenyMotion
Check this forum post too
They say this:
I solved this issue by reducing the RAM Value in Virtual Box.
Go to Virtual Box
Select Your Device
Go to settings -> System -> Motherboard.
Reduce Base Memory.
Or this might help:
Try starting the emulator in VirtualBox. It will give you a specific error, which you can then google for more info.
In my case, the issue was VERR_INTNET_FLT_IF_NOT_FOUND, and the solution was here
solution https://www.virtualbox.org/ticket/14604#comment:1
I have accidentally deleted the file System/Library/Extensions/IOStorageFamily.kext by mistake. I know how stupid this was!
Now my iMac (model 2008, running Mavericks) gets stuck on the grey startup screen and hangs forever after the Apple logo turns into a no entry sign whilst the wheel continues to turn forever, see the following link for image showing this screen:
No entry sign on startup screen
I have run Disk Utility from the install CD and repaired the disk permissions with no success.
I have tried to run the rescue partition by using the Command + R key but this just displays my exsisting HD and does not show another option.
I have tried to boot into single user start with no success. The screen eventually hangs and says it can not find IOStorageFamily.kext.
I have tried to boot into safe mode with no success. It simply fails with the no entry sign as above.
I have reset the PRAM but this did not make any difference.
I have done a hardware test using the D key on startup but this returned no errors.
Please can someone advise if there is any way to fix this problem and if the is then what is the best way to do it? I know that it is not a harddrive failing or anything else and is simply because I accidently deleted the IOStorageFamily.kext file. Surely there is a way to repair this?
I appreciate any help or advice.
Many thanks
I have managed to fix the problem by using the following method:
http://support.apple.com/kb/PH13842
It says:
If you have two Mac computers with FireWire or Thunderbolt ports, you
can connect them so that one of them appears as an external hard disk
on the other. This is called “target disk mode.”
Connect the two computers with a FireWire or Thunderbolt cable. Start
up the computer to be used as a disk in target disk mode: If the
computer is off, start it up while holding down the T key.
If the computer is on, choose Apple menu > System Preferences, click
Startup Disk, then click Target Disk Mode.
When the computer has started up, a disk icon appears on the desktop
of the other computer.
Transfer files by dragging them to and from the disk. Eject the disk
by dragging its icon to the Trash. While you drag, the Trash icon
changes to an Eject icon.
On the computer you used as a disk, push the power button to shut it
down, then disconnect the cable.
After connecting to another Mac I simply copied the deleted file back into the correct directory from the host Mac.
I then booted my Mac successfully and repaired the file permissions via Disk Utility.
I have been working on a project, and when I run the project in android studio it had been running correct and when I ran in debug mode it ran correctly.
All of a sudden, when I try to run the project normally, it pops up on the device waiting for debugger
and in the logcat I get this:
02-07 10:38:46.444 3968-3968/com.geog.test D/dalvikvm﹕ Late-enabling CheckJNI
02-07 10:38:46.784 3968-3968/com.geog.test W/ActivityThread﹕ Application com.geog.visitdub is waiting for the debugger on port 8100...
02-07 10:38:46.804 3968-3968/com.geog.test I/System.out﹕ Sending WAIT chunk
and it goes no further. I don't know why this is happening, there is no debug command in the manifest, I have killed the adb and restarted as I did with android studio.
It's a real pain in the a*** as I can't run the app without going through debug mode. If anyone has any ideas I'd like to hear them
Thanks
Restart your Android Device once and also check there should not be any breakpoints in your java classes.
The above suggestions were too invasive for me so I digged a little more into it. The following solution works for me in android studio:
Start debugging. (You'll get the wait chunk message here)
Select the Debug pane with the bug icon.
press the small cross at the side menu.
press "Force close" on your device.
Restart debugging.
In my case, there was an AsyncTask whose doInBackground() method called android.os.Debug.waitForDebugger(), and this was being picked up even in run mode. Disabling the line fixed it. Restarting the device didn't help.
try this , always work :
1 - close Android Studio and any other IDE you have opened (maybe you have Eclipse also running?) and emulator instances;
2 - remove USB cable from PC and restart your phone if you use one ;
3 - run adb kill-server from console;
4 - open Android Studio;
5 - click on run/debug;
6 - when the window to select the device appears, attach your device to USB and USB to your computer;
In my case it was a service to which I had added android.os.Debug.waitForDebugger(). The service was in a separate process by defining in the manifest android:process=":sepprocess"; after removing this line (such that the service is in the same process as the main activity), debugging started to work in the service and I did not experience the
I/System.out﹕ Sending WAIT chunk
anymore.
First clear all the break points from your project using ctrl+shift+F8 for windows or for mac cmd+shift+F8. Restart your android device. Then run
In my case, there are multiple debuggers. I have native code running in my app.
I cleared it by selecting the Debugger and Process from Run->Attach Debugger to Process
I deleted the emulator and recreated. It worked for me.