I am looking for mobiles that support AT+CMNI commands to use them as a gsm modem for kannel , because AT+CMNI commands supported mobiles will allow the both MO and MT SMS.
Any suggesting will be welcome , and if there are a way to test if a mobile support AT+CMNI without buying it that will be good.
The AT+CMNI command is standardized in 27.005 and it says
Implementation
Mandatory when any of the new message indications implemented.
so I think you will have a hard time finding a mobile phone that does not support the AT+CMNI command.
Related
I have been developing a Win application that uses 3 Azure Kinects. Since there is no C# wrapper available yet, I made a C++ app that does what I need and the C# app just grabs its output files.
I now need to figure out which camera is which. In the C# app I can get the windows device id in a form similar to
\\.\USB#VID_045E&PID_097C#001007692912#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
However the C API for the Kinect only provides ways to get the serial number of the device.
I tried to dig into the API, since I'm sure it must be somewhere in the code but, due to my limited C skills, I got lost pretty quickly.
Anybody with the same issue or can help?
Thanks,
Guido
The SDK is designed to use serial number specifically to determine which device or devices you are connected to. If you are just trying to use 2 Kinects with 2 instances of your C# then you will need to open devices until you find the serial number you are looking for. If you are trying to use multiple devices in a master/subordinate configuration then you can query for jack state to determine if you have connected to one or the other.
Also please be aware that we just released our own C# wrapper for the SDK. Checkout https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/608 and https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/namespace_microsoft_1_1_azure_1_1_kinect_1_1_sensor.html for more details.
I need the ability to do the following things:
1) read the phone numbers out of received sms messages.
2) send an sms message.
3) finally, this one isn't necessary but would be a bonus: cause the phone to vibrate.
From what I can tell this wouldn't be possible on iphone or windows mobile, what other phone types cannont do this?
It will probably not work on iPhone, considering the limitation on all applications in an iPhone. (Apps are in their own little world so to speak)
Vibration: All that supports vibration.
Sounds to me like you should focus on Android, where you will be able to do all of your mentioned things.
I need to provide a way of users uploading multiple files (can be 10MB each) over Mac, PC and a mobile device (something with an SD slot).
The connection from the mobile device can be poor so I need to enable queuing of the files so they can be delivered when connection becomes available.
I am looking at Silverlight as a potential option using something like this example uses and sending over the files when a connection is available.
http://www.microsoft.com/silverlight/out-of-browser/demo/
I have tried searching for silverlight articles but not found anything appropriate. What I am trying to avoid is writing multiple versions of the software for Mac+PC (browser) and mobile device.
Can silverlight provide this kind of functionality or is something I would have to approach differently?
Silverlight can be used to do that.
You don't need to use the out-of-browser functionality, silverlight gives you low-level control over sockets and threads.
For devices it's a different scenario, as AnthonyWJones points out.
There is a silverlight version for the nokia, but I've know idea if it is actively developed. The is also a c++ version for linux/meego, there is a mono version.
But all those are different versions.
I have used software named my mobiler which displays the screen of any Windows Mobile connected to a desktop PC and allows the user to control the mobile from the desktop.
Are there other similar software available in the market for S60 or Series 40 Nokia mobiles.
My Mobiler is very cool - like Remote Desktop but for a phone.
The Nokia PC Connectivity API doesn't quite do the same thing, as it provides a set of APIs to let you control the phone and get data from it. Neither do the Series 40 or Series 60 emulators, as the phone is emulated rather than real.
Given the significant technology differences between S60, S40 and Windows, I'd be surprised to see this change any time soon.
Now, Maemo (as running on the N900) is a different kettle of fish altogether. Quite remarkably someone has ported VNC there which should do the job just nicely.
I'm also interested in other Symbian SDKs that allow to set their emulator's IMEI.
Emulator has hardcoded IMEI of '000000000000000'. Replace what with whatever you want to use and continue running your code.
Symbian C++:
TPlpVariantMachineId imei;
PlpVariant::GetMachineIdL(imei);
imei.Copy(_L("123456789012345"));
Python for S60 (PyS60):
import sysinfo
my_imei = sysinfo.imei()
my_imei = u"123456789012345"
My general approach to these kinds of things is do it in software.
Put the IMEI fetching code into one globally-accessible function, and only use this function for IMEI fetching.
#ifdef __WINS__ can be used in C++ code to selectively compile in the hard-coded IMEI you want to return in the emulator. In Java, you can probably tell you are in the emulator by other means (eg if the IMEI returned is a fixed weird value in the emulator), and act accordingly.
You can go one step further and have a dynamic IMEI. Once you do that, you will find that testing your code with different IMEIs becomes much easier.
I have never actually tried that but here's my best guess:
The emulator doesn't have a proper telephony implementation unless:
you link it to an actual phone over infrared/usb/serial. In which case the emulator telephony component will need configuration to use AT commands to pilot the phone (even if the phone isn't a Symbian phone). This allows you to make phone calls, send and receive SMS/MMS but certainly not change the IMEI.
you use the SIMTSY module. This is a component that uses configuration files to simulate telephony events. It can pretend to send SMS/MMS, pretend you are receiving a phone call...none of that actually creates any kind of network traffic, you understand. I assume the IMEI is in the configuration file but I don't expect you can properly change it without restarting the emulator. I have never seen SIMTSY used outside of Symbian itself so I don't know whether it is available to third-party developer. It should be open-sourced with the rest of the operating system within the next 2 years, though.
There is also the possibility that the way the SDK itself was built disabled most of the telephony framework for the emulator, using build-time macro. You should check http://forum.nokia.com