I'm having problem with the Windows Phone emulator.
Last night, when i have finished my works, I wanted to close it, but it didn't shut down properly.
After 10-15 minutes I shut down my computer.
But now, when I'm trying to connect to the emulator again, I can't.
I've tried many things, but it still fails.
I open the Hyper-V Maganger, and I saw that my emulator state is still "Stopping".
What can i do?
Related
I am starting a QGuiApplication (Qt 5.12) and using a remote desktop connection to a Windows 10 PC. Everything works fine while the remote desktop connection is open, but when I disconnect and let the application run during the week-end, I can see in the logs that it stops processing Qt events (mostly network related in my case). The last thing the logs show is an "activation change" event.
When I connect again after the weekend, the Qt event loop starts again (the logs show again "Activation Change event") and of course there is a huge amount of queued events and the application gets in a non responding state (I am logging the number of Qt events queue in the loop using qGlobalPostedEventsCount).
This used to work correctly but stopped working, I think due to an update of Windows on the machine (maybe same root-cause than this thread ?).
Is this the expected behavior for applications when the windows remote connection is terminated? Is there a known fix for this?
I have not managed to properly fix the issue. As a work-around, using Microsoft "Remote Desktop" application instead of using the "Remote Desktop Connection" application avoids the issue.
I installed firebase-tools-instant-win.exe for my flutter app. it works fine after configuring it. However I can't use the
emulators:start --export-on-exit=./saved-data
to save the database locally because when I Ctrl+C, it doesn't shutdown gracefully. There is no message that it shutting down and saving just a ^V
I also get the message that there are multiple instances of the emulator running. I notice the port assigned moves every restart on the (emulator)
browser console: localhost:4000, then 4001 etc...
having a little bit hard time entering the dev mode on my Lenovo 100s Chromebook
after entering the recovery mode, after pressing The Ctrl+D and enabling the risk, the Chromebook is preparing system for developer mode with the loading sign on the left, waiting a couple minutes the screen goes to the "OS VERIFICATION is OFF, waiting about 20 seconds and right after that I am hearing exactly 2 Beeps, and all over again and it repeats the same procedure for about more than 3 hours already and nothing happens to it help anybody?
I think that you successfully entered developer mode.
Try rebooting your device and press Ctrl+D on "OS VERIFICATION OFF" screen. If that does not work, try recovering your device and repeat the same process.
You can refer to this guide: https://chromium.googlesource.com/chromiumos/docs/+/master/debug_buttons.md#firmware-menu-interface
My BLE device uses SSL certificate on connection which is causing the app to hang when the iPad gets locked. It works fine as long as I don't lock the iPad. anyone faced similar problem?
What I tried is to disconnect the device on sleep and reconnect it on resume. It works fine when the app goes into background and comes back, the problem comes when I lock the iPad and then resume to app. Same events fire whether I lock the device or minimize it.
Can anyone tell me how Xamarin handles these 2 things?
I have enabled background modes and tried everything available on the internet but I couldn't get it working.
It starts working when I kill the app and try to reconnect it.
How do I dispose the connection with my bluetooth device properly on sleep and then start as a new?
P.S I'm using dependency services in Xamarin.Forms.
Connecting 192.168.176.128 to ADB failed!
Please check if the Android player was fully started when you got this error. If not, you can either increase the Android player launch timeout on the BlackBerry->BlackBerry Android Development Tools preference page or wait until the Android player is fully started and try again.
This means that Eclipse, or more specifically the BlackBerry Android tools plugin for Eclipse, could not connect to the ADB (Android Debug Bridge) service on the BlackBerry device.
There are a number of reasons for this:
The Android Runtime and associated services including ADB did not load in time. The default timeout is 5 seconds and if you have not run any Android apps on your BlackBerry it will take more like 20 seconds to load the first time.
The Android Runtime has crashed. In which case you will need to reboot your device. My preferred method for this is a '3 finger reset' which means hold down the power button, volume up and volume down buttons for 10 seconds in order to do a full reset.