According to DxDiag on a Windows 10 PC, the System Information shows Miracast: Not Available, the Display Device NVIDIA GeForce 210 (driving 2 displays) shows Miracast: Not Supported by Graphics driver, and the Display Device Intel(R) HD Graphics 4600 (driving two displays) shows Miracast: Supported.
WiFi is provided by D-Link DWA-171 Wireless Adapter to a non-5G local network.
But Windows-k is showing "Your PC or mobile device does not support Miracast". The mobile device is a Samsung S7 FE tablet which does support screen sharing.
How can I make Miracast work on this configuration?
Related
I'm using a Minew G1 Gateway to collect both beacons and BLE devices.
Doing some test, I see that it detects beacons and various devices (smart TVs, smartwatches) but I can't find any of smartphones nearby. I find several unknown devices, but their mac address doesn't correspond with those of my phones.
Smartphones used are at least 4.2 bluetooth version.
Do you have any idea about what I'm doing wrong?
As Emil said, you need an app to enable BLE adverts on smartphones to make them discoverable to scanning devices. Have a look at the links below:-
BLE is working between two mobile phones
Are BLE enabled devices discoverable by default
I am developing an app to scan for the peripheral devices using the Android phone.
When the Application tested using Samsung S6 device (Model used are Indian, EU and US version), I have seen that the device stopped discovering the BLE devices during scanning as soon as the phone screen is locked.
It almost took 4-5 hours to resume the discovery when the phone kept in same locked state.
Configuration Details:
Lollypop Scanner with scan filter UUID's using Low Power Mode.
ignore Battery Optimization was set to True.
Phone screen locked after some time when the scanning was started.
Samsung Models used: SM-G920F, SM-G920A
Test results :
The app was able to see the discovery when it was in the foreground and device discovery stopped immediately when the phone screen was locked.
Important Note : The same application is working fine on Samsung S7,S8,S9 and pixel
I've built a device using an IMUduino board, which is supposed to be similar to Arduino Leonardo board with a nRF8001 bluetooth. I was able to connect my device to an Android phone using the nRF UART v2.0 app, I tested some examples and it worked with success.
I would like to connect the device to a Windows 10 PC via bluetooth. I have installed the driver of the nRF8001, and I am able to pair both PC-UART. However, when I open the Master control Panel, I cannot find any Master emulator, the menu is empty. Master control panel version is 3.10.0.14.
Is there any way to connect a device with nRF8001 to a Windows 10 PC?
Thanks.
I would like to control an Arduino device with a Motorola phone.
I have a Lilypad (preferred), an Uno, and a Mega Arduino board and I have two Motorola phones (a Droid Bionic and a Droid Razr Maxx) both running Android 4.1.2. According to an App called "USB Host Diagnostics" neither phone has USB Host Mode capability.
A variety of sites suggest the problem is that the phone doesn't provide enough power to the Arduino. Their solution requires cutting up and reconnecting the wires inside the cables. Others say the creation of a special "dongle" solves the problem, as long as it is in the phone when it starts to boot up but is removed before it finishes. Others suggest that it requires rooting the phone, which I'm afraid is probably beyond my comfort level and skill set. And many of these postings are several years old.
Has anyone figured out an smarter/better way to either enable or work-around the host mode capability issue of these phones? Or would it just be easier to find a used Nexus or Galaxy phone?
There's a sample provided for CDC compliant USB devices here. Are vendor-specific USB devices supported too? Or are CDC compliant USB devices the only ones supported in Metro apps?
Your help is much appreciated!!
Vendor specific USB to UART bridge devices will not be supported under CDC, only a USB CDC class device would be supported in that case.
However, since Microsoft has opened up a USB API you could still access vendor specific devices. The downside here is that the devices will not look like a COM port, you would need to use the Windows.Devices.Usb namespace to access the device directly through it's USB protocol. This means that the vendor for a specific device would need to publish their protocol, or you could reverse engineer or use the Linux source as an example of what the setup packets for certain commands should look like.
Since you're using an FTDI converter you can get the device protocol information from their Linux Source (this is from 3.13 kernel) and use this to access the device through Windows RT.
FTDI might support Win RT in the future (today is 2014-Apr-15), you can ask for a beta driver here:
Windows RT Driver