I've successfully ported my Qt-based C++ application to my girlfriend's Windows Mobile device. (A Samsung Omnia 2.)
However, it seems that the Qt Mobility Sensors API is not supported on Windows Mobile, so the application's specific features that would require the accelerometer are not working.
The question is, how to access the accelerometer of a Windows Mobile device from a C++ application?
If your Omnia 2 has WM 6.5 Update you may use the unified sensor API here
Related
We have our fingerprint device which is working properly as USB device.
Data capturing works fine with our proprietary application.
Currently we are using custom vendor USB class for driver development.
When we plug this device, this device is listed in "Universial Serial Bus Controller" catagories in Windows Device Manager.
We want to use Windows Biometric Framework for the same device to achieve Windows Biometric login.
I understand that, we need to write WBDI compitible driver but I have query related to fingerprint device hardware.
We are targeting Windows 7 and later operating systems.
Will there be any changes required in hardware to work with WBDI driver ?
I have a program I am trying to gut the UI from and just let it manipulate data and store it on a harddrive. The program is written using MFC. Can windows 10 IoT run MFC applications?
There are two editions of Windows 10 IoT: Windows 10 IoT core and Windows 10 IoT Enterprise.
Windows 10 IoT Core is a mini version of Windows 10 that is optimized for smaller devices. Its mainly supported app type is UWP and there is some limitation of the traditional Win32 app because there is no Win32 UI stack on IoT Core. More information is here.
Windows 10 IoT Enterprise is a full version of Windows 10 that delivers enterprise manageability and security to IoT solutions.
For your use case, you can choose Windows 10 IoT Enterprise.
I have a hardware device which would communicate with a third party application on Android and IOS over Bluetooth to send to and fro data.
With Android I am able to achieve this, however in case of IOS I don't have any information.
Till now the information gathered to work with IOS devices is:
1. Application runs on Iphone 5
2. Hardware is MFI enabled
3. IAP2 is supported
Please guide how to connect the hardware to an application and what other information is essential?
Is AppName, BundleID, BundleSeedID and ProtocolName required to connect? If yes how we can get these details?
I tried unzipping the application but the Info.plist file looks garbled and not able to get much info from that.
Currently I am able to connect the hardware with IPhone over Bluetooth, but my real concern is how to communicate with a specific application on it.
Also if you can provide some link or pseudo code to initiate a session between hardware and IOS application.
I assume you've already connected the SPP profile on Android. However for iOS the SPP(BLE is another story and do not need MFi) was hidden but need MFi authentication for raw data links.
Since you want to establish the raw data link between your hardware device and your iPhone, you need:
Make sure your hardware has MFi chip, generally this chip is connected with your hardware by I2C.
After step 1 make sure you can communicate with this chip at your hardware, fortunately the hardware vendor or MFi vendor will support this kind of code or binary.
The MFi channel have a specific UUID(which may defined by Apple?) to replace the SPP official(which defined by Bluetooth SIG) UUID, hence if you want to make connection between your hardware and your iPhone, you need register the iOS defined UUID and make them as same as the normal SPP profile.
After the RFCOMM channel created, iOS would first authenticate the link, just like 3-way handshaking or something, so your hardware just communicate with the MFi chip and transfer the token to iOS.
After that iOS would set this RFCOMM channel(same as SPP actually) for your hardware, then you can send/recv data between them.
Can anyone out there provide further information on CPU, RAM, flash storage and battery type of the SmartEyeglass? I need this to compare the hardware specification with other smartglasses for my bachelor thesis.
In addition, it would be nice to know if the firmware running on the SmartEyeglass is based on Android.
Those hardware specifications are not publicly shared. SmartEyeglass is not Android based, but SmartEyeglass apps are Android apps that run on the smart phone.
SmartEyeglass acts as an accessory for the phone. SDK let's you display the user interface on the SmartEyeglass, take photos using camera of SmartEyeglass, get sensor data from SmartEyeglass.
To learn more about it, please consult to SDK pages.
https://developer.sony.com/develop/wearables/smarteyeglass-sdk/api-overview/
I need to develop an iPhone/iPod Touch application that creates a server to send some data stream (characters or bytes) to a Windows C++ application via Bluetooth. I'm thinking of creating a TCP connection, but don't know where to start.
What iPhone API should I use do to something like this? Does anyone knows some code examples that i can use to do this?
And in Windows, what should I use to support this kind of communication?
Thanks
Yes. From what it looks like you can use the PAN bluetooth profile (the same profile used for tethering) with everything except the original iPhone.
Here's an article doing bluetooth over iPhone/iPad using GameKit. The article notes that you would need at least 2 iPhone/iPad devices running iPhone OS 3.0, but I wouldn't take that as an impossibility to talk to any other bluetooth capable device.
Update
This forum indicates that the iPhone is only capable of headset pairing. It could be that the iPhone is "picky" about what you can pair it with.
"The iPhone only recognizes the "headset" profile. Another well thought out idea from Apple. No A2DP profiles, no OBEX."
-sapporobaby
Update 2
As jamone as indicated iPhone 3.0 supports A2DP. How nice is that?
Here's a table listing of iPhone/iPad bluetooth supported profiles
I'm pretty sure third-party developers don't have sufficient access to the Bluetooth stack to do this via published APIs (i.e. via an app you publish to the App Store).
Is using WiFi an option? That's what most developers seem to be using for client/server communications. If that's the case, see if you can distribute Apple's Bonjour runtime with your app. If you search the developer site for Bonjour, they have code samples (though probably no Windows examples).