windows phone emulator is doing complete OS reboot - windows-phone-7

can someone with expertise help me in this regard? I've tried every possible way, even tried re-installing...couldn't get rid of this error on emulator. Unfortunately i cannot try re-instaling OS on my laptop. I use win7 32 bit OS.
emulator shows "windows phone emulator is doing complete OS reboot.." and then crashes, emulator comesup again. This repeats for 3 times and the i can see error "The RPC server unavailable"
thanks in advance.

minimum ram required is 3GB, i was having only 2GB, hence the problem(i think).
I upgraded to 4GB and now it works fine, still open questions are
1) why i was allowed to install 7.1?
2) why it was working for sometime without any issue?

Related

How to use the Android Studio emulator on an AMD processor computer?

My notebook has an AMD Ryzen 5 3500U processor and I'm trying to use the emulator in Android Studio and I can't get it to work properly. Most of the time the emulator only works the first time it runs when it is created. Some of the recurring problems is that even when running, it does not appear in the flutter device selection. After some research I found out that the solution may be to activate two Windows features: virtual machine platform and windows hypervisor platform. However I am not able to activate because after clicking on the checkbox and giving ok. This message returns to me: "an error has occurred. Not all features have been successfully activated". Does anyone know how I can resolve to have these features activated?
I am using an AMD PC as well and had the same issue. There were drivers that had to be configured and didn't work as expected. The workaround I did was to use genymotion as an emulator. The setup didn't require major setting changes. Here is the link to it :
https://www.genymotion.com/

Can deploy to Windows phone on one machine but not another?

I have been developing a Windows phone app on my lunch breaks at work and spare time at home. The project is stored in my Dropbox so it's the same on both pcs. At work when I debug/deploy to the device everything is fine and dandy. At home however I get the following.
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Now in both cases I'm using the same version of the SDK and of VS on the same Microsoft account on the same phone on the same project. But it doesn't work.
I have reinstall the SDK twice now to no avail.
When I run the device registration I get the following message.
Unable to connect to a phone. Make sure the Windows Phone IP over USB transport service is running
I'm not sure what I'm doing wrong here, has anyone run into this before? Any ideas of a fix for the issue?
Update:
I have uninstalled 2013 r4 and installed 2015. I have done a hard reset on my phone. I have run Windows Update and I'm up to date. I have tried making brand new projects as some of the posts suggest, to no avail. Same issue occurs, except now my emulators get:
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '184901A8-DC44-4CED-869E-DC7733D048D6'
I'm guessing the next step is reinstalling Windows, I think I'll just wait till Windows 10 comes out.
Possible Fixes:
1.Try reconnecting your phone.
2. try re registering your phone as developer device
3. try this fix
https://dev.windowsphone.com/en-US/OEM/docs/Phone_Testing/Configuring_IP_over_USB
Testing apps on windows phones can be frustrating. One common problem I get is the need to reinstall drivers for the phone. I think this may be your problem.
The other problem similar to this I've encountered, was when registering for windows phone not using the correct version on that pc for 8.0 or 8.1.
Aside from this, there is a list with links provided that may help you. Let us know how you get on.
This link Problems and fixes when registering a Windows Phone 8 device to deploy/debug applications covers the major issues, some mentioned by Akash.
The following is a summary of the points discussed in the above link:
Windows Phone IP Over USB Transport(IpOverUsbSvc) service is running
Phone name is already in use by this account
Too many phones have already been registered with your account
Device lockscreen has to be unlocked (and it is unlocked)
Can’t find any devices
Point 5 is also addressed in this answer https://stackoverflow.com/a/30303946/3956566.
Update after comment
The other thing that you may need to do is:
1. make sure you have all your updates in Windows.
2. Make sure you have all VS updates.
3. reinstall VS.
4. Reinstall any .net framework packages for VS.
The first two are the most likely things.
If worse comes to worse, to reinstall windows.
I have needed to do all of the above at one time or another to fix various issues. Painful, yes.
And don't forget to reboot your machine.
Let me know if this works. There MUST be a solution.
I know what you mean about the phone appearing in explorer, update anyway, won't hurt to reinstall them.

Memory causing windows 7 applications to fail on mac (using parallels)

I have been using Windows 7 applications within Mac iOS software for a few months (using Parallels), but recently it has stopped working. Every time I try to open a windows 7 application the application shows a broken, corrupted page that looks like static.
I have tried uninstalling and reinstalling Parallels but this has been unsuccessful.
Thank you in advance.
Also, just before this happened my computer prompted that I was running out of memory.
Restart your computer and reset PRAM by holding down
'cmd+option+p+r'
After that try opening up the application again. If the issue persists, close the windows session and allow it to use some more memory and try again.

Why won't ADB recognize my Samsung Fascinate on Mac OSX?

I am trying to write some android apps on Mac OSX and then test them on my Samsung Fascinate (Verizon), but ADB will not recognize the phone. I have tried everything from restarting adb, to reinstalling the SDK. It works on the linux/windows machine that I have, and I know Mac is recognizing the device, because it shows up in System Information.
Other people posted that EasyTether caused problems for them and I previously used EasyTether, but I removed every trace of EasyTether from my machine so that should not be the problem.
I also recently restored the phone to stock through Odin so the problem is definitely not on my phone. If anything, it is a Mac problem.
Anyone have any ideas why this isn't working? I appreciate the help.
I was having the same problem. What fixed it for me was going in to the USB connection option after it registers on the phone side and changing to USB Mass Storage mode. This was counter-intuitive since PC Mode is supposed to be for debugging, but on the Mac this caused the device to register with the adb server and I am able to debug my apps; it will not work for me when the connection is set to anything else.
Just had the same problem and removing EasyTether and then disconnecting/reconnecting solved the problem for me.
This site has some tips (bottompart of the page) which could help you.

Windows phone7 emulator requires constant refresh

I have the tools installed for windows phone 7 development.
But, when I run the any of the sample apps I have to manually refresh my emulator's app window to see any changes.
Any ideas what I'm doing wrong? Or maybe a setting is wrong?
Thanks
I've got it on every machine I've tried- but they all have various Nvidia cards (desktop and mobile).
When I posted about this on the wp7 forums, they talked about wdm 1.1 (which I've got) and so far I have no fix.
My machines are all 64bit, so I'm wondering if this isn't some issue with them or the nvidia drivers- but I don't experience any other problems with the drivers outside of the emulator.
I think we're stuck for a while anyway...

Resources