I have 2 Windows Phone 8.1 devices connected by usb cable to my computer. I can use isetool.exe successfully with each phone individually when it is the only one connected. I know I need to use deviceindex:n but EnumerateDevices only returns one device (index 0) when both are connected.
I cannot find any specific examples online nor in the documentation that specify that 2 devices physically connected to the computer will be returned, the same line "Lists the valid device targets and the device index for each device" from Microsoft documentation (https://msdn.microsoft.com/en-us/library/windows/apps/hh286408%28v=vs.105%29.aspx?f=255&MSPPError=-2147217396#BKMK_Syntax) but that could include one device and multiple emulators.
I do not have any emulators set up to confirm if EnumerateDevices only helps in the case of multiple emulators and has a max of 1 device.
Can anyone confirm one way or the other, or shed any insight why i only get one device returned?
Only one physical device at a time is supported; the others would all be emulators.
Related
I realized that Android M requires at least one of ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION permissions to scan Wifi.
I don't think it's a technical issue but that there is a sort of philosophical reason (e.g., privacy) for such a weird policy.
But I couldn't find the exact reason for that and I would appreciate if someone give the answer.
The list of available Wifi networks for a device can be indeed used to locate the device.
To locate the device on needs the list of of the wifi networks the device can see and a huge database with known wifi networks and the position of the access points. With this information one can triangulate the position of the phone.
Multiple of these huge databases exist. Apple, Google, etc. have each one and there are also public ones: http://www.openwlanmap.org/
Read more about it here: https://en.wikipedia.org/wiki/Wi-Fi_positioning_system
I am facing an obscure behaviour of device naming when trying to use multiple USB midi devices of the same type of hardware. As this might be hardware/system/driver related, here is my general setup:
host: Windows 8.1 x64 (tested on multiple machines)
usb devices: 2x Livid Brain V2 (a general purpose usb-midi interface)
The two devices (same hardware, let's call them device X and Y) are flashed with two different firmware flavours so that they appear with different names in the midi enumeration. If I only connect device X it shows itself as "Brain2" / if I only connect device Y it's "Brain2B". Those are the names I get from the MIDIINCAPS / MIDIOUTCAPS (winmm.dll). So far so good.
The problem arises as soon I connect both devices at the same time, than both get the same name (of the latter connected) - so the enumeration changes:
first X, then Y => both get the name "Brain2B"
first Y, then X => both get the name "Brain2"
However, I can access and use the devices but I am not able to distinguish between them anymore (which is basically the same starting position as having the identical firmware on both devices).
I'd be happy if anyone could point me in the right direction. Has anyone encountered anything similiar? Could this be a system related issue? (Or is it a bad driver, maybe?) Thanks in advance!
EDIT:
I had a closer look at the usb properties with a tool callled USB Device Tree Viewer (similar to USBView) and it turned out the identifiers are correct there. So, how does winmm.dll get the midi enumeration - could it be a bug in there? (unlikely)
Moritz
(btw: here is the related topic/post in the manufacturer's forum: link)
I have been programming for windows since about v2.1 and am interested in some apps for the phone now that it seems to be coming of age.
Search as I might, I cannot find a developer's unlocked version of a phone other than CDMA one and I can't use that as there is only AT&T and TMo available out here in the boonies.
Buying a dev's version for Android was simple as going to Moto's site and dropping one in the shopping cart.
If msoft are wondering why there are so few win-phone devs and/or, they might start looking at how hard or easy it is to get started. I have installed the SDK and the emulator is OK, but not something I would trust enough without testing it on my own phone.
Any helpful thoughts and suggestion on where to get a phone that it is not against the warranty to unlock?
You can use any windows phone as long as it supports the OS version (windows phone 8/8.1 is not supported in the older models) you're coding for. You don't need a developer version of a phone.
You need a developer's account though (should be 20/year now) and take a look at this page for registering your device. For older devices you need Zune software but it's not needed for windows phone 8 and up.
And if you want to use a real device for testing, without wanting to buy a device, you could use the Remote Device Access service
With it you can use a real device (located in Tampere/Finland) over the internet with your browser. Limitations include the lack of physically touching/rotating the device, and that calls/SMS are disabled both incoming & outgoing ones.
I'm making an app that needs info on whether a certain Bluetooth device, like the car stereo, is connected or not. I'm able to retrieve the list of paired devices but no information is provided on if they are currently connected.
Any advice is appreciated.
One possibility would be to try to connect to each paired device.
I Have windows phone 8 And I want to Develop apps and Deploy it Freely.is this possible.
Ya, max 10 developer app or unsigned apps are allowed to install in your phone.
I assume what you want to do is sideload the apps . For that you need to developer unlock you lumia620 first , which obviously is going to cost you.Please check price for developer unlocking you phone with microsoft.
Other than that it is impossible to load apps freely ,if it is not through App store.
Hope my answer helped you.
It is possible to load any number of unsigned xap files onto a Windows Phone device provided it is fully unlocked (interop unlock). How you go about getting your device to that state presents a challenge. So far, only the Samsung ATIV S has been unlocked to that level for Windows Phone 8.
Once you have fully unlocked your phone you effectively have free reign over your device being able to fully access components such as the registry or file system.
Both Samsung and LG have provided back door diagnostic tools on their phones that facilitate making the needed registry changes to completely unlock their phones. Whether such features are available on other brands has yet to be discovered.
If you are a software developer, you will probably want to get your hands on an ATIV S before they disappear.