My WebBluetooth app works in Chrome Version 77.0.3865.90 on another system, so this is not a Chrome problem, this is a Windows setting problem. As soon as my web app tries to pair I am getting the message, "Turn on Bluetooth to allow pairing".
Bluetooth is turned on in Windows 10 and I can manually pair my workstation to my Android phone. I have fiddled with every Windows Bluetooth setting for hours now (disabling devices, etc.).
This is the message:
Any help would be greatly appreciated. Thx!
This is probably a Chrome bug. Since I experienced the same problem, I have opened https://bugs.chromium.org/p/chromium/issues/detail?id=1006688 for it.
Related
I have recently started to have a deeper look into Wi-Fi Direct under Windows 10 (desktop version) and had a look into the API descriptions
from Microsoft => https://msdn.microsoft.com/en-us/library/windows/desktop/dn457945(v=vs.85).aspx
One of the described methods there (WFDStartOpenSession) states that a previous pairing through the "Windows Pairing experience" (WPS ?) is required.
So i started to play a little bit with the pairing stuff by using a Windows 10 (Build 1607, Desktop) together with an Android-based smartphone (version 6.0.1) and
made the following observations:
When i initiate the connection from my PC to the phone, it "basically" works i.e. the pairing dialog shows up on the phone's display and i can connect to it.
Although it works, it's not really stable in my opinion - on my side it works 1 out of 3 times.
After ~ 30 seconds, Windows disconnects from the phone (in the "Devices and printers" view) while the phone itself stays connected a little longer (then it also disconnects).
When i initiate the connection from my phone to the Windows PC, nothing happens - no message box, no pop-up window :-(
Has anybody else seen this or similiar behavior ?
I tried it with 2 different USB adapters, one with a RTL8723BU chipset from Realtek and the other one with a RT5572 chipset from Mediatek Ralink - both show
exactly the same behavior.
In addition, i noticed that the "Realtek Wireless Lan Utility" to control and configure the USB adapter is not working anymore in Windows 10 (1607) when switching
from client to Access Point mode. I think it's somehow related to ICS, missing hosted network support ... don't know yet.
However, actually you don't need the tool from Realtek as you can for example use the mobile hotspot feature of Windows 10 to share your internet connection with your devices.
But without the Realtek tool i have not found any possibility to switch WiFi channels - does anybody have the same problem ? is there are solution available for that ?
Thanks
I would like to control my windows mobile from desktop.
I'd like to have full access, keyboard and mouse as well.
Is there any way to do it?
If both of your devices support Miracast you can use the Connect app. Find more info on Windows Central here.
Edit: If you want to control your phone, just open the Connect app from your Action Center. This will work even for not Continuum enabled phones. You still have to enable the connection in Settings app on PC and you may have to pair the PC with the phone over the Bluetooth.
Seems like there is an app called PC remote, created by microsoft.
If that's something like what you're looking for: https://www.microsoft.com/da-dk/store/p/pc-remote/9wzdncrfhvwt.
Edit: Thats a Danish version, but I think you should be able to find an English version aswell.
Goodmorning,
I'm working quite hard on my own app. At this point I want to run it on my android (galaxy note 3) phone. Unfortunately Appcelerator studio doesn't detect my android phone; Windows does. I've tried it with the new Galaxy s7 of a friend, but same result.
Off course I searched the web like crazy and found several possible (old) answers, but none did the magic.
When I consult the log, there's no new info to be read!
Does anyone have a clue where to look? Looking forward to your answers…
Kind regards!
One thing you should check is if you have set up your phone for development. You can see the instructions here: http://developer.android.com/tools/device.html (... tap 7 times... - took me a while to discover!)
And the small obvious thing is in Appcecelerator Studio you may need to select "Refresh devices" when you try to run the project.
/John
When you say "Windows" detects it, what exactly do you mean? Does adb detect it?
If you run
adb devices
on the command line, does it report your device ID?
On my Mac, I run this and I can see my connected S4:
List of devices attached
9726ea90 device
I'm assuming that the Windows version of adb would output a similar report.
With all the Samsung phones I've debugged with, I always have to go to the notification bar and choose "connect as media device" (or something similar). The default connection mode does not work for debugging. And unfortunately, you have to do this every time you connect the device.
Has anyone gotten the Sample BasicDriveApp App working in Windows 8?
https://github.com/orbotix/Sphero-Win-SDK
When I build and run the Project I get a message "No Sphero is connected" and when I try to connect the Sphero via Windows 8 Bluetooth it does not work.
Can anyone offer any tips?
Thanks.
John.
It indeed works, I've had some problems with connectivity myself, however.. process I use to restore if all goes awry:
Refresh Sphero (return to base for sleep mode, wait a few seconds, wake up)
Refresh Bluetooth in Windows (off / on) without connecting to Sphero
Open your app, wait for it to connect. It'll find Sphero and automatically dig in if all goes well.
[Update]
It appears Windows 8.1 doesn't really know what to do with Sphero. It has a hard time reconnecting after the connection is lost, even if you close all instances of the app and toggle through Bluetooth.
When I try to deploy my XAP to the Windows Phone, I get the "error 0x89731812" message.
Your device has a locked screen. Unfortunately, this is not documented anywhere, but there is a discussion with some hints on page 3.
Turn on your phone (if it isn't already)
Slide open
Type your password to unlock
Retry the deployment after unlocking your screen.
EDIT: My bad (well, that of my search engine). They are documented here. Thanks keyboardP!
As I Stumbled upon this old thread I might have found a solution for this Error code.
I've had the same message as I found out that my device wasn't recognised properly in device manager.
Did some research and saw that the driver wasn't picking the right USB-port as it was registered to one of the other usb ports.
After inserting the Phone to the first USB port where it was registered the Initial first time everything went ok!
If your phone charge is very low, it won't deploy the app too.
To deploy you must:
1.Connect your wp7 phone
2.Open Zune
3.Open the deployer
4.unlock your phone (As said before)
5.Deploy
It requires an unlocked phone (without restrictions) or an Interop Unlocked Phone, and the phone mustn't have low charge.