Windows 10 and Your Phone call connection

I will finally close out this thread and perhaps provide some motivation for others to work with Microsoft to fix the problems. 

I have found no solution.  My case was escalated to Level 3 MS support where for over 3 months it existed as an open case.   MS support spent several hours on phone calls and remote computer access trying to get the problem fixed.  And to be clear, MS is well aware of the problem and can replicate the issue in their labs.  According to the rep handling the case MS will not or cannot fix the problem since it appears to be a near random event. Some phones reliably work and others do not.  Some computers (or computer manufacturers) systems work and others do not.  MS  claims that the Bluetooth connectivity is root cause for why the call feature will not work. 

The final suggestion from MS was to purchase a separate BlueTooth Radio for my computer and see if that would allow a connection.  The alternative - and more expensive route - is to purchase a phone that can work with the software. But even on that score MS was not much help. They could not tell me what brands or style within brand of phones were problematic.

I find the whole Bluetooth radio story to be a bit of a stretch.  Once a phone is paired I can sit in any of the  cars I own or rent and make a Bluetooth enabled call without a hiccup.  I have a difficult time believing that the protocols for pairing and connecting a phone to a device are not well worked out.  MS seems not to have implemented them in a robust manner.   In short, what could be an extremely useful piece of software is left to wilt owing to insufficient development support from MS.  Who knows, maybe MS simply wants to push you to using Skype.

I have a hard time believing that the matter is related to cable versus wireless.  It is still all the same network.  But by moving to wireless, that would change the ip address of both phone and computer and would also reset the ip stack.    One can do that manually from the command line using the netshell utility. The sequence is:

netsh winsock reset and press Enter.

netsh int ip reset and press Enter.

ipconfig /release and press Enter.

ipconfig /renew and press Enter.

ipconfig /flushdn s and press Enter.

Then restart the computer. 

I did all that and I now have most functionality in YourPhone, even the call icon is available. But, wait for it,  still no dialpad. That is pure Bluetooth and there is some setting that is preventing the computer from controlling the phone.  Not sure what that might be but I think it may be related to discoverability of the computer by the phone and vice versa.  Beyond that though everything is working fine.  One more session with Microsoft to root around the Bluetooth settings and I think a durable fix is in the offing.

But I am happy to hear that your problem has been resolved at least for now.

You were very helpful.

I too have noted the same behavior with the icon.  Not sure what it means.  I sometimes feel we are experiencing the electronic software version of Gaslighting. 

I broke down, called Microsoft and got a really talented tech on the phone.  Bluetooth was a clear problem and that has now been fixed, but the YourPhone call problem still existed.  I pointed out the odd behavior of Bluetooth and the solution was a clean reinstallation of the Bluetooth Drivers straight from the computer manufacturer and not the cab files.  So the Bluetooth is now working flawlessly.

But about those phone calls.  She conferred with someone internally and I was told that, no, phone calls cannot be placed with YourPhone.  When I showed her this thread, she stated we were all in error. Then I showed her the Microsoft support page that stated that, yes, you can make phone calls with the app:  https://support.microsoft.com/en-us/help/4531605/setting-up-and-using-calls   That threw her for sure and she conferred again and said, yes, it does look like that phone calls can be made, but only with people who are "Windows Insiders".  That makes no sense whatsoever.  So with more conferring the tech person concluded that phone calls could be made but that I would have to perform an in place repair of Windows 10 to get it to work.  This is equivalent of giving your computer a lobotomy and is always the default position of MS tech when they cannot resolve or even describe the problem.  I suspect that, in fact, the app is buggy and MS is having a tough time with it.  They should just come clean and say that there is no workable, stable,  call option. 

And so it goes some more.......

Hello. Try this.

1. Make sure you have the correct versions

PC Windows 10 1909, Your Phone 1.19122.138.0

Android >7.0, Your Phone Companion 1.19122.149.0

Reboot device(s) if you have to make any changes.

2. Go to PC Settings>devices>select phone>remove

 Go to Phone Bluetooth and select PC>unpair

3. Go to PC Settings>Apps>Apps and Features

Select Your Phone and advanced options (uninstall greyed out)

Select Terminate

Select Reset (check means success)

Uninstall/reinstall Your Phone Companion on phone

4. Reconnect PC and phone Bluetooth
5. Open Your Phone on PC and configure. You should have Call option. It is very picky and you have to connect the PC and phone like the first time, getting rid of any traces of prior connections. You might have to go through the procedure several times.

I have tried this approach many many times and no success.  The failure seems to occur at the very last step when the "Call" set up on the YourPhone app on the computer is trying to access the phone by Bluetooth.  That connection does happen successfully...I get a notice in the Windows Action center, I get a notice on my phone, but the YourPhone app is  reporting a non-specific error message that says it could not finish connecting.  All other bits of the phone are present, picture, text messages and notifications.

For a second I thought I had the problem corrected since, once booting the YourPhone App on the compter a keypad briefly flashes but then it reverts back to the error message.