trouble during reinstall hololens unseccessful - hololens

i get into a trouble. A few days ago i bought a hololens 2. It was necessary to reinstal that but during reinstallation there were a error and reinstallation wasnt successfully done. Now i wasnt to run the glasese it isnt able to detect device in pc. during a charging still light just first led. I try lots of way to solve that but without success. please could you give me any advice ?
tnak you
jarda
i used advance recovery companion automatic and manual detecting. No feedback from this SW. If i try to reset hololens in a device manager there isnt a hololens recovery device

For this one, best advice is to open a direct support ticket with Microsoft for hardware support:
aka.ms/HLSupport
The Microsoft support team can validate the hardware and assist further.
Thanks,
Nathan

Related

Continuous delivery to Azure using Visual Studio Online: Loss of conectivity

I've followed each step of this tutorial: https://azure.microsoft.com/en-us/documentation/articles/cloud-services-continuous-delivery-use-vso/
When I make check-in It triggers the build, but I receive the error message:
This build has been stopped automatically by the server due to loss of connectivity to the build machine.
I can't find a solution for this problem. I'm retrying the build but without succes.
Can anyone help me with this problem?
Regards
Bizarro issue that showed up on my system without notice.
After a lot of troubleshooting, I found that I had not mapped the Visual Studio solution to my local drive. After mapping, resetting security permissions, it began to work. Sorry, I dont have a clear solution for you.

How do i change the resolution in Kubuntu 14.04

I just installed Kubuntu 14.04 on my HP laptop, but the resolution is off. Everything is way too big...and when i go to my settings, the only resolution available is 800x600....Can anyone please help me fix that.
Also, i have searched online but have not found anything that helps.
You need to change graphic driver. Unfortunately you provided not enough information to give you correct answer. With what you said I can only suspect that you probably don't have intel build in graphic card. It should work immediately. I assume you have nvidia or ati graphic card.
If yes go to Settings > Repositories > Additional Drivers tab and select the correct driver, and click Apply changes.

Windows phone 8.0 error 0x89371B01 when trying to deploy app

I cant find information on this error anywhere. I am connecting to a brand new lumia icon (AKA lumia 929). Dev account is registered. I have attempted:
reinstalling windows phone SDK
restarting phone
restarting computer
ensured the app runs on the emulators properly. the only required capability of this app is network. Capabilities have not been changed from the defaults since the project was created. none of the manifest xml files have been touched.
ensured phone software version is up to date
ensured apphub account is valid and active
ensured the windows phone developer registration tool worked, unregistered and re-registered the phone to make sure
restarting the "ip over usb" windows service thingy
changing the platform built target to ARM or AnyCpu (no difference, same error)
tried alternate deployment methods such as windows phone power tools (the xap deploy) and I get the same error when trying to connect (so I know it's not an issue with visual studio, nor is it an issue with the app code)
I can successfully deploy separate code to a separate WP7 device (so I know it's not an issue with the computer)
tried multiple usb ports
tried two separate laptops
tried visual studio 2013 and 2012
The behavior is this:
Connect the phone via usb and unlock it
Attempt to connect to phone via windows phone power tools OR deploy an app via visual studio
System hangs for about 90 seconds and seems to time out
Error appears
I am able to view the phone contents, name it and explore it on my laptop, but when it comes time to deploy something I am stuck.
Error message is simply: 0x89371B01
What does that mean? Has anyone else run into this?
Have you checked the device drivers on your Windows 8.1 machine? It could be a driver issue with your USB drivers on the computer.
I have also found that, once you get it connected, going into the Device Manager and deleting the device from there and forcing it to reload has helped me in the past.
Out of curiosity, try running "sfc /scannow" at a command prompt on the PC. It may require admin elevation. I've seen some bizarre behaviors due to dll problems in sxs in win 8.1, wondering if this could be caused by that kind of thing.
Couple of things to try:
Have you installed the GDR3 Emulators and tried running it on the 1080p emulator? It looks like the 929 is a 1920x1080 phone and will have the latest the latest updates installed. First place to check.
Based on this feedback in another stackoverflow question it looks like someone was having a similar issue and disabling Hyper-V resolved it for him. If you disable Hyper-V and it works, try re-enabling it and see if you still have the issue.
jmshapland had the correct answer for me, with the same issue. Disabling Hyper-V did the trick! No thanks to microsoft phone dev center forum posting on the issue..
http://social.msdn.microsoft.com/Forums/wpapps/en-US/24bd3e48-e7b4-4d00-8d69-193f49989ce0/0x89731b01-error-during-deploy-to-device?forum=wpdevelop
Looks like I'll be disabling Hyper-V to test on my device, and re-enabling to work in emulator mode:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and
dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
OK I was able to come up with a repeatable solution for the issue. Im HOPING that by posting this I dont tempt fate and have the phone not work again!
Here are the steps I did to resolve it (not sure if all of them are necessary):
On phone, disable wireless
Connect phone to laptop
Open device manager and click to show ALL HIDDEN DEVICES (including hidden devices is important)
Uninstall ALL phone-related devices (one in portable devices, several in USB
devices) anything that mentions lumia must go
Disconnect/reboot phone
Reboot laptop (there seems to be a process keeping the port open)
I had connectivity, then I lost it, then I re-gained it using these steps and it seems to be reliable for me (so far)

I cannot run windows phone 8 emulator

http://i.stack.imgur.com/rfDod.png
Dear Experts,
I am a newbie to windows phone development and when running the project on VS2012, I get this error message (as shown in the link above)and I am not able to resolve it. Trying playing around with the settings on BIOS without any result.
Please assist me. Thanks a lot.
Regards,
Mohammed Mohsen
Did you check if Hyper V is supported by your hardware ? you can read this to get an idea about how to check, that might be the cause

Android emulator constantly rebooting on Ubuntu Maverick

and thank you for your time.
I am using Titanium Appcelerator to write an app for Android, and as compared to Windows, where the emulator was quite stable, in Linux I get the following symptoms:
emulator restart with no reason, sometimes after a runtime error, sometimes right after launching my app, and sometimes just right after booting completely after being launched
emulator informs that "process $1 is not responding", where $1 is generally the system process, but sometimes may be acore, or the calendar. This may happen while installing my app on the emulator, right after loading it, or right after unlocking the screen.
As it is easy to imagine, testing code like this can be quite difficult, so I was wondering, has anyone else stumbled upon this problem, and/or know how it could be solved?
Thank you very much in advance, and pls let me know of any info I should provide.
Leo
You should verify that the emulator is working fine without Appcelerator first. Definitely update to the latest SDK (r8) and create a new emulator AVD and see if the problem is there without Appcelerator.
I think I found a solution, but I don't claim it is universally valid: I just erased the virtual device created under Titanium, changed the project file for it to use SDK 1.4.2, and had it launched again under 1.4.2. It certainly didn't build my app, but at least it created a new virtual device, which I use now to build against 1.5.0, working like a charm so far.
Thanks again Manfred for pointing me in the right direction!

Resources