I found Network Sharing on Win8 mobile. (nokia Lumia)...I am trying to write similar application for Win8. But could not find any support on windows website. On Nokia website also, all I could find is how to turn on, but nothing else.
So, I have a lot of questions in my mind:
Is Network sharing is even supported by Windows or is it Nokia that has their own app to do this?
How this network sharing works? Are we tethering WLAN or something else?
Is it possible to write a similar app with the existing Win8 mobile APIs provided?
Does it use DNSMasq? ( I am assuming it is)
Is there any possible way to find the installed apps and the app structures in Win8 phone, like we have in android phones.
Network sharing is fully implemented by WP8 OS but it is under tight control from your cellular operator. You need to pay extra to enable "tethering" (here in USA). The cellular connection (4G, LTE) is then shared and your phone turns into Wi-Fi access point for other devices. When I try to enable network sharing on my HTC 8X (I am not paying for tethering), the screen flics with Wi-Fi details - tells me Wi-Fi broadcast name, password and number of guests connected - and then one second later I get a dialog from T-Mobile to go online and add tethering to my phone plan.
See above.
No, I don't think it is possible. As an app you don't have any control over network configuration.
I'd assume it provides NAT, DHCP and DNS forwarding. I don't think it uses DNSMasq code directly though. :-)
For privacy reasons you can't get a list of installed apps. Only when you are writing apps for enterprises (that don't go through Microsoft Store), you can list other apps signed with the same enterprise key. See http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj207245.aspx.
Related
According to Microsoft's latest docs:
Do I have to pair Bluetooth devices before using them? You don't have
to for Bluetooth RFCOMM (classic) devices. Starting with Windows 10
release 1607, you can simply query for nearby devices and connect to
them. The updated RFCOMM Chat Sample shows this functionality.
However, when I try to connect to my devices using this chat sample, I get a notification that asks me to "set up the device", like I was going through a normal pairing process.
Am I missing something?
The snippet of code that I changed from the sample:
var rfcommServices = await bluetoothDevice.GetRfcommServicesAsync(BluetoothCacheMode.Uncached);
Taken from msdn resources:
Windows 10 Mobile is currently limited to connections with only paired
devices. In Windows 10, you can programmatically pair/unpair. See
scenarios 8 and 9:
https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/DeviceEnumerationAndPairing
Here’s is the related MSDN documentation on pairing and the relevant
device selectors for enumeration.
https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.enumeration.deviceinformationpairing.aspx
https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.bluetooth.bluetoothdevice.aspx
But I also know that you can use direct bluetooth connections on lower level and this way windows won't suggest you pairing. For example, that's how things work with 32feet.net library, discussed in this answer (I worked with it and it was fine, however it is currently unsupported so please beware of it).
First thing to test is the bluetooth protocol used to be RFCOMM in both client and server. Link
Check that both client and server hardware support the RFCOMM
Check the bluetooth versions in both client and server link
based on wikipedia bluetooth has many protocols.
Second is to check windows version
I have searched for hours. I am developing an activesync client in order to send sms from PC to a phone that will send it. Specifically a windows phone. Previously I have used Jeyo mobile comp. I have all documentation I need but I can't find the default http address of the activesync server on the Windows phone when it is connected through USB. I should mention that I have a disability and can't access Windows phone itself. The OS is 6 but the whole point of creating the software is so I can upgrade. Many thanks!
alternatively if I am barking up the wrong tree, i need to know what tree to bark. for example serial ports. i would only need code to connect and read/write. otherwise is there a way to detect the information with csharp, ipconfig definitely isn't detecting windows mobile and activesync definitely works.
The question is a bit unclear. But Jeyo Mobile Comp is a remote control software for Windows Mobile (6.x, not Windows Phone 8 or 10).
Another free remote control software you my look at is Sparus EveryWan Remote personal edition (free). It can show the screen of Windows Mobile on your Windows PC and you can use the device remotely using the USB ActiveSync connection.
Another option is MyMobiler (also free).
The ActiveSync connection is made using the IP addresses 169.254.1.1 and 169.254.1.2 or 192.168.55.101/102, depends on Connection Setting:USB:Enhanced Network on device. You will find the IP when the device is connected to your PC, ActiveSync is connected and you start a Windows CMD prompt on the PC; then type "ipconfig" to get a list of IP addresses used by the PC. There will be your IP connected to the LAN/WAN and the one connected to Windows Mobile.
There is NO default http access to the Windows Mobile device.
If you are looking for a programming API, see RAPI at Microsoft (https://msdn.microsoft.com/en-us/library/aa513321.aspx) or OpenNetCF Desktop Communication (https://rapi.codeplex.com/) support.
I have been long interested to develop on the platform. I even got the tools installed already on my desktop but I can't upgrade my WDDM from 1.0 to 1.1. To make things simple: my graphics chips are not up to the task of running the emulator.
If I still buy a Windows Phone (e.g. a Nokia Lumia) for development purposes, can I sideload and test my apps there efficiently instead of going against the emulator?
If I still buy a Windows Phone (e.g. a Nokia Lumia) for development purposes, can I sideload and test my apps there efficiently instead of going against the emulator
Yes, of course. It's very easy and convenient. You have debugger and all the goodies. Advantage of the emulator is the test option for 256MB devices.
That's exactly what I used to do prior to upgrading my devstation. The nominal min spec says 3G but with a real phone it worked fine in 2G and as you say this also sorts out graphics limitations.
Note that the setting for whether the emulator or physical device is used is stored in the project, so if you accept a project from someone else you will have to set it once prior to debugging.
Well there are 2 sides of the coin. With the physical device you can test most of the things, but with a few limitations
You will not be able to test internet related test cases - For example, if you have an app which uses internet connectivity then you will not be able to test it on the device easily because
The device does not use the machine internet connectivity
When connected to the PC the device's internet connectivity(Data connection 3G/ wifi/GPRS) is broken.
You will have to purchase an account right from the first day you want to test your app. If you have the emulator working then you could postpone this for atleast few days.
Where I work, we are building a GUI to run on iOS or Android; the GUI is intended to control an embedded board. The embedded board does not have WiFi, an Ethernet port, or a USB port, but it does have an RS-232 serial port; so we are using a product called a WiSnap.
http://serialio.com/products/mobile/wifi/WiSnapKit2.php
We have been able to connect to the WiSnap using OS X, or using iOS (an iPad 2). But none of our Android tablets recognize the device at all. The WiSnap acts as a WiFi access point, and broadcasts an SSID; the Android tablets do not list this SSID in the list of available WiFi access points. Under Linux Mint 12, my Laptop can see the WiSnap, but attempts to connect to it fail. Interestingly, my cell phone (a Droid 2) is able to see the WiSnap, but I don't have telnet on my phone so I haven't tested to see if it actually works.
Under OS X, I noticed something. In the drop-down list of WiFi access points, there are two distinct groups: the top group, which contains most of the listed WiFi access points, then a lower group, that has a sub-heading that says "Devices" and contains just the WiSnap and something called "hpsetup". (I don't know what "hpsetup" is or where it might be; there are lots of WiFi users in this neighborhood.)
The WiSnap is operating in "ad-hoc" mode with no security at all.
So, my question is: what is the significance of OS X calling the WiSnap a "device"? It is frustrating to try to search Google for "WiFi devices"; you get a giant haystack of results that are not related to this.
Also, is there anything we can do to make an Android tablet see the WiSnap and connect to it?
Can anyone recommend a good resource where I can read up on WiFi? Again Google hasn't helped much; there are so many introductions to WiFi out there, most of them at a very simple level.
Thanks for any help you can give me.
EDIT: The vendor does claim Android compatibility for some models of WiSnap, but not for others.
This lists Android as supported: http://serialio.com/products/mobile/wifi/WiSnapKit2.php
This does not: http://serialio.com/products/mobile/wifi/WiSnapAAA.php
I guess I should contact the vendor, but I do want to understand what is going on, so I was hoping to get advice from the StackOverflow community about this.
EDIT: We did contact the vendor. What we found out is that the WiSnap can be a stand-alone device only in ad-hoc mode. If you set up a WiFi router or access point, the WiSnap will join the network in infrastructure mode. But the WiSnap will not act as an infrastructure mode access point.
Android OS at the moment only supports infrastructure mode. So, if we want to use an Android tablet with a WiSnap we would have to set up some sort of WiFi router or access point. We are looking into other solutions now.
I'm relatively sure that hpsetup is the ad hoc wifi for an HP wireless printer. So perhaps the ad-hoc/peer-to-peer qualifier is what causes OS X to classify it as a device.
I followed all the steps from the article but when I try to hit the server from my windows phone it says there is a dns error.
Article for reference.
http://blogs.msdn.com/b/fiddler/archive/2011/01/09/debugging-windows-phone-7-device-traffic-with-fiddler.aspx
How do I know my windows phone is using my local LAN WIFI as opposed to ATT cellular?
Personally, I use Netmon 2.3 for network traffic information from WP7. Fiddler didn't support WP7 up until recently and Netmon/Wireshark did, so I just stick with those.
Using Netmon 2.3, while your device is connected to Zune/WPConnect, you'd be able to see all WP7 device transport on the ZuneComm process. Netmon isn't as user-friendly as Fiddler, but it's fairly darn specific and easy.
You could turn on flight mode and then turn wifi back on.
Or you could take the sim out.
Either of those ways will ensure you're not using the cellular network.
I used the IP address instead of dns and it worked.