About a month ago, I loaded the Android emulator "Andy" on my windows 8 laptop and it seemed to work fine (except it kept kicking me out of Clash of Clans after a couple minutes, but the emulator kept running).
Yesterday, something happened. While in Clash of Clans, the background turned all black and just the small images were visible. This has happened before and I would kill Andy using the X in the upper right corner. I would then restart Andy and things worked OK again.
However, yesterday when this happened, I killed Andy in the same way, but when I tried to restart Andy the frame would display for a second or two and then go away.
I figured that a bit got twisted somewhere, so I uninstalled that version of Andy and downloaded and installed a newer version, but I get the same results.
I checked the web and the closest I came was "Andy won't launch on windows 8". The suggested solution was to roll back the display driver. I did that with the same results.
I figure that there may be a flag somewhere that thinks Andy is running, so it shuts down any new version, but that is just a guess.
Has anyone else run into this problem?
If so what was the solution?
Try to change the compatibility setting to windows 7/8
Related
I started noticing that it was taking several minutes (5-10) to build and run apps on my iPhone 4S from Xcode. I was running XCode 4.5.2 and iOS6.0 on my 4S and decided to figure out the problem. There was another similar question posted here but it was closed without a definitive answer. (which is a shame since this is a valid concern for folks.) I am reposting the question to explain what I observed. Hopefully it will help someone.
First I rebooted my Mac after several impatient attempts to install a relatively small app seemed to hang. I tried removing all of my old provisioning profiles from my Mac and my iPhone thinking I was having trouble with expired certs/profiles. I tried a few more times and decided to let it just hang to see what happens. It eventually launched the app on my device after about 5-10 minutes. I Googled around and found some hints that maybe I should try rebooting my iPhone and re-synching with iTunes. (I had already made an unsuccessful attempt at synching which also seemed to take forever.) On my next attempt to synch I decided to remove some larger apps (700+MB) to clear space since I was down to my last GB.
Things were still slow so I decided to reboot my iPhone and then re-synching it. I rebooted my phone and went to sync in iTunes again and this time the sync went quickly. I had cleared an extra 3+GB leaving me about 4+GB of free space. I restarted XCode and my app is now installing quickly.
My take-away is such that I believe there may be extra daemons running over time on the device and restarting my phone is what ultimately helped restore install times. Also, I'm not sure if clearing space helped or not. I would like to know what the root cause/solution is but that depends on others having similar experiences and responding.
I've scoured the questions asked here and thought I had found an answer earlier with deleting the data for the simulator, but my issue appears to be slightly different.
When I run the app, which was working on the last version of xcode and has been run on other systems in the simulator, in the simulator, it opens up the simulator and the simulator screen is black. Not the normal black issue that I've seen where it is black but you can see the iPhone or iPad frame around the edge still, the whole simulator window is black like it hasn't loaded.
When I look in the debug log it always says this and only this "error: failed to attach to process ID 0".
I've tried the steps located Xcode compiles my App, but can't run it in the simulator and I've uninstalled and re-installed xcode. The issue still persists.
If anyone has any ideas would be much appreciated.
Ok, I had this issue for a couple of days recently. I changed the device in the "Hardware" menu and it automagically started working.
The issue turned out to be the root doesn't run the simulator so we gave various folders and files permissions, sorry, long list and I was half working on it another person did the rest of the work, but if you run into this issue, start working in the non-root account (system admin also didn't work).
been using the gwt plugin in eclipse for about a year, has worked pretty fine.
However, i recently upgraded to OSX lion, and i also upgraded intellij to latest version.
Now, i have a standard gwt project. I have historically been able to start it with the devconsole, change stuff and reload page in firefox. (using firefox5 currently)
But now, i can only start it, but as soon as i reload page, devconsole crashed. Yesterday it just hung, this morning i upgraded to GWT2.4 and now i just get permgen space outofmemory on first reload. I have the memory settings set to 1024m!
If someone could give me pointers it would me much appreciated...
I experienced that same issue after upgrading to Lion. I believe it has something to do with the memory management of OSX, not Eclipse or GWT. It was a source of huge inconvenience to me, and the benefits of the Lion upgrade weren't enough to justify dealing with an impaired capacity for development, so I rolled back to Snow Leopard. That resolved the problem.
I've since tried (unsuccessfully) going back to Lion and using different browser combinations, including Safari and Chrome, but Firefox still seems to be the best choice if you're using Lion- Chrome is exceptionally slow with GWT (oddly), and Webkit in general seems to not support some of the features GWT offers, so Safari's out.
I say go back to Snow Leopard, unless there's something preventing you from doing so. Good luck, and please keep us updated if you figure out a workaround.
Answering my own question since i've found well, not an answer but a workaround.
In intellij, i changed the agent (only using one in development to speed things up) from gecko1_8 to safari, and used chrome.
As i mentioned, the console crashed in firefox on every reload, in Chrome i'm at 30 page reloads/recompiles and not a single console crash!
It also recompiles faster than in FF.
Have no idea why it works so crappy in FF though...
You can fix it - just add -XX:MaxPermSize=384m for jvm.
I've imported an iPhone app that I have developed for iOS and am now maintaining it. I've came across a couple of bugs when trying to add to the iPhone's calendar, which I'm happy to try and sort out myself with a bit of debugging.
One problem is that when I go to run the application on the iPhone simulator, it seems to run an older version of the app than the one I am running. I've removed and added another button since then and the old button is still showing when I run it in the simulator. However, when I compile and run this on a device, it loads the correct version and displays the correct version number in the 'about' view.
But... my main problem is that it doesn't seem to debug on the device properly. The app actually works fine except for the calendar problems, but if I put a few breakpoints in so I can see exactly where this is going wrong, it just doesn't seem to step through! The app pauses, and Xcode says the app has paused! I can press step over and continue execution etc and it appears to work, but I can't see it stepping over the code, nor can I hover over variables to see their values.
I've tried reinstalling Xcode multiple times (I did have a problem installing an older version, so I had to wait until the next version was available before Xcode would install).
The stress is: Today is my last day at work, and I'd really like to get this app ready for iOS 5 before I leave.
Has anyone seen these symptoms before? Is there a debug setting that I've missed? Or is it a corrupted installation?
I wish I could help people a bit with more information, but I don't even know where to start looking here. Any code I can post? any settings? (not too familiar with this, I'm a .NET guy usually).
Thanks!
Sorry you're going through a tough moment there Connell; as you said you're not too familiar with all this, I'm laying down a few steps which might help you out. Some are pretty basic, yes, but I've resolved to these steps myself several times when I've encountered similar scenarios;
If you're testing on the simulator, do a 'Reset Content and Settings' from the 'iOS Simulator' main menu. This will remove all old data and settings and give you a clean start.
Do a 'Clean All Targets' from the Build menu. Then go to your physical project folder and delete the Build folder from it altogether before starting to build again.
Restart both XCode and the Simulator (and your Mac too if possible)
Make sure the mode is set to Debug and not Release or Distribution
Even on the device, remove the old app before putting the new one in, and restart it for good measure.
Delete all Provisioning Profiles from the device and install just the one you need.
On the code;
I've noted that the app appears to 'pause' like this a couple of times when I had accidentally created an infinite loop in the code. Double check to see whether there's something which may cause this.
Unless you haven't already done so, throw an NSLog or two in there to see if its really not being executed beyond the breakpoint.
I've had the exact same problem with a project that I started on xcode 3 and then switched to xcode 4. What fixed it for me was changing the compiler in the project settings.
The default compiler up to xcode 3 was gcc, while the default compiler on xcode 4 is LLVM gcc.
Now, I don't know exactly what's the issue that gdb could have with LLVM gcc, but switching the compiler back to gcc in my project settings and doing a clean build fixed my debugging issues.
Might be worth a try.
Have you checked which debugger is being used GDB or LLDB? Select Edit Scheme from the Product menu, and see what the Debugger setting is under the Debug scheme. You could try switching between GDB, LLDB, and None and running in between.
I have an iPhone app that I'm trying to run on my phone via Xcode.
It installs and runs without an issue
I make a change in the source code (negligible, like an NSLog())
It installs without an issue
Running causes the error:
Error Starting Executable 'myApp'
Don't know how to run. Try "help target".
I uninstall the app, and reboot the phone
It installs and runs without an issue (until I make another change; then I have to repeat this dance)
Needless to say, having to uninstall the app, reboot the phone, and reinitialize the environment (i.e. set prefs) takes an unreasonable amount of time, and is probably indicative of a serious problem. The issue is, the only vague error message I receive gets me nowhere on Google. Where on earth could this issue be coming from?
With some help from #iphonedev, I figured it out. Turns out it's a glitch in iOS 5 beta. The way to fix it is to remove the device from Development Devices, then re-add it.
Yeah just restarting the iPhone with the lock and home buttons fixes this. Had it happen a few times to me