It looks like most existing remote PC solution using bluetooth-enabled smartphone needs PC side software (especially Java..)
I'm wondering if remote PC control is possible without PC side software at all?
Yes, it is. I once tried Bluetooth remote control with a Sony Ericsson K770i and it worked really great! All you need is a Bluetooth receiver installed on the PC and you need to pair your PC with your mobile phone. Then you can set the phone to control the PC and voila.
I tried this on Windows Vista x86. Worked really great. It was a pleasure to be able to control the PC from my bed when I was sick. Plus, I could bind shortcuts like "Ctrl+C", "Ctrl+V" to certain keys on the mobile phone. The K770i had it all.
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.
I'm trying to use Microsoft's Remote Display Control (version 2.03, copyright 2000) to view my Windows CE device on the desktop (not only is it nice for my "regular" handheld device, because it makes the display easier to see, especially in zoom mode, but it is even more important for the other devices I have to test, whose screen is too dim for me to make out exactly what's on the screen (it's like the vision test from h311) - which is necessary for debugging, of course) but for some reason I am not able to enter key strokes on the device while it's connected to the desktop. I can enter them neither on the desktop/in RDC nor on the handheld device itself while connected via RDC.
This, of course, is untenable (no pun intended).
The .exe is created in XP Mode, copied to a "holding tank" in Windows Explorer on the Windows 7 machine, then copied from there to the handheld device.
Then I connect from the handheld device by selecting Start > Programs > cerdisp > selecting OK in the "Remote Display Control" dialog, then Connect, then OK (and I do connect), then run the app on the desktop in the "WindowsCE" window that RDC supplies. It allows me to select menu items, but the keyboard is broken/mute...???
Is this a known bug? Is there a workaround? The desktop is a Windows 7 machine.
Doing a "cold boot" of the handheld device caused it to come back to responsiveness, keyboard-wise. These devices are betimes more peckish than a put-upon puddle of Platypi.
what is the tool used to project the screen from the phone to the PC?
I've seen it being used in a presentation but can't find it anywhere.
Thanks!
This is an internal tool used by Microsoft staff only at the moment.
Camera / projector is another option.
You can achieve it by using for instance the following tools and after connecting a projector to your pc ofc:
http://www.mymobiler.com/
ActiveSync Remote Display (Microsoft Mobile Dev. Powertoys)
I am pretty new to WinMo development. I managed to write my first app, debug it via the emulators but I failed to run the debug session on my physical phone.
I connected my phone to the development PC via ActiveSync, but that alone did not make my phone show up on the list among the selectable emulators. Is there anything I need to do before this would work?
Alternative: I want to program with the G-sensor and the bluetooth capabilites of the phone. Is there a way to play with them via emulators? How on earth do you shake an emulator? :)
After you hooked up and confirmed that ActiveSync is working, you should be able to select the "Mobile Device" form the target list. It is not listed by name, it simply is the only entry not ending in emulator.