Hi guys, I am looking for some way (software ?), that enables the XDA/Qtek to send and receive SMS picture messages (EMS) -not MMS- using only the GSM network and not the internet, and that is, of course, a stand alone function, I mean by this without having to use a Nokia GSM phone or any other GSM phone.
Thanks for your help
All you really need is an app that associates a particular SMS string with a particular picture. You'd then install this app to both devices - sender and reciever.
You'd open you app, pick a picture and hit send. The app would then send an SMS string, say, 'picture1' via SMS to the receiving xda. That unit would have the app running that would pick up the SMS 'picture1' and, having associated that string with the picture you want (presumably picture #1, for the sake of argument) will display that picture.
That's effectively all EMS does on other handsets (not quite, but effectively) - that's why you can't usually see EMS sent between different devices. Different devices from different manufacturers set up the (proprietary) EMS in different ways.
Try the Philips C12 to the Nokia 7650, for example, then you'll see what I mean.
Tekflow - I think you're talking about EMS - ie the SMS extension 2bit picture format made popular by Nokia phones. I quite miss this, as most of my friends have Nokias, and I often used to send EMSs to them with my 9210.
I've looked into this myself a bit for PPC/PE - the situation's not too good:
Sending is relatively easy, just build the SMS in the correct format and send it out, however receiving it is a nightmare.
Unfortunately, Microsoft have made a complete mess of SMS receiving functionality on the PPC/PE OS, only one single application can ever have the SMS handle open for receive at any one time for a given message protocol (and these are not very fine grained basically Text, Notification, WDP, WCMP, Status and Raw).
This application by default is the SMS handling application of the PocketPC/PE. So basically, you can't use it otherwise you loose the default handling.
On Symbian, it's sooo much easier. There's a 'chain' of receivers, so you just register for a particular message, scan it, and if you don't want to process it, you just pass it on to the next application in the handler chain.
It might be possible to completely rebuild the SMS handling application from scratch, get rid of the default handler, and replace it with your own, however there's quite a lot going on under the surface with SMS handling, so this would be extremely difficult.
One thing you could try is getting the messages after they have been received and placed in the inbox using MAPI. I'm not sure if this would work, as IMHO MAPI is a hopeless API too, and propably would bletch at a SMS type that wasn't plain text. It's worth investigating though.
There are two EMS softs for Pocket PC but not for the "Phone Edition".
These softs used AT commands instead of RIL API.
But as with last ROM it is possible to have access to internal modem with AT commands, these softs should work now.
eMood Messenger for Pocket PC :
http://www.emoodsoft.com/doc/emm for ppc.htm
Pocket Presence SMS Manager :
http://www.pocketpresence.com/smsman.asp
But EzOS (developer of EzWAP 2.5 MMS) proposes MobyKit, a library to develop SMS/EMS/MMS :
http://www.mobykit.com/tech_messaging.php
Anyone knows if there is a possibility to send and receive picture messages (EMS, not MMS) using XDA II ? All the available software I found are not compatible with Pocket PC Phone Edition.
I'm looking for the same as well.
Worse still, the PPC or WM2003 default SMS software does not even NOTIFY or do anything when it received an EMS message. In fact, it did nothing .. I suspect it ignored anything apart from SMS, it didn't even store ANYTHING from an EMS. Some normal phones at least receive the EMS but display garbage on SMS, on Xda II -- zilch !!! NOTHING. Try it.
Smart GSM
Guys, I think Smart GSM is the solution. Try it and let me know the results.
http://www.smartsoftworks.com/download/
ems 4 qtek 1010
do this program work for pocket pc phone edition like qtek 1010 (xda)?
did anyone send or receive a EMS successfully ?
Related
Hello all,
I do a lot of mass mailing and the best phone for that in my experience is the Nokia 9210i.
Mainly because of three things:
1. all you need to do is scroll down through the names and highlight
2. if there is a problem the 9210i will resend automaically.
3. what is great is that, it has the capability to guess the names. it can even guess an initial or a half name.
the problem with the xda is that if you send to more then one person, under the log it shows it only sent one time. therefore if one of your friends did not receive it, it will say that there was an error when sending your sms but you don't know who. plus forwarding again and again making sure all your friend receives the info is such a pain....
i am just wondering is there another sms program out there that may be better then the original...
cheers...et
In my XDA with AT&T latest ROM, I can't receive any vCard by sms! I've tried sending them from my Nokia 6310i both in single phone number and full details mode. The Nokia phone says the vCard has been sent but I don't get anything in the XDA. Sending vCards by sms to other phones obvioulsy works.
Is it just me? Is it a bug or is it a 'feature'?
thanx
PS: do you know of any XDA proggie that will receive/send vCards?
Yeah, me too. I think it must be the setting problem.
However, I don't think anyone can answer me in HK cause I am using WM2003 with ExWAP v2 (downloaded from Yoret.net).
The setting I can see from the official CSL website couldn't tell me how to set it up with my xda1.
cant claim i know what vcard really mean but google give some hits when you search on vcard pocketpc
http://www.google.dk/search?hl=da&ie=UTF-8&oe=UTF-8&q=vCard+pocketpc&btnG=Google-søgning
I have never tried sending/receiving Vcards via SMS, but I have sent & received via IR.
PPC 2003 allows you to receive vCards into contacts and Calendar...however not via SMS indiginously. You need a 3rd party application to do that. If you do a search for "SMS" at either http://www.pocketgear.com or http://www.handango.com you will find the app I'm talking about. Cant remember what its called though, easy to find click through all the pages. :wink:
Thanks for your answers. All soft I have found just manages the vCards stored in the PocketPC. Some let you even send them through email. But I have not found any program that emulates Nokia phone's capabilities of receiving an specially crafted SMS with the vCard inside.
I find interesting is the fact that when you send an sms with an vCard inside from a Nokia phone to another phone (without vCard funcionality), it displays the message in raw format:
BEGIN:VCARD
VERSION:2.1
N:John
TEL;WORK;VOICE:5551234567
END:VCARD
However, my XDA I (WindowsCE 2003) silently ignores such sms while it's happy to receive regular ones!!!
This vCard through SMS capability is probably Nokia-specific... it would ne nice if some one implemented it for PocketPC devices. I'm sure there's a market for it!
hiya
recent convert from mobile to pda
does anyone know if we can stick smilies or ems pic on our sms
or even receive them :?:
no the sms recieve part of the OS dont support ems and cant be made to wihtout rewriting parts of windows ce
but people said that it could be made to send ems if parts of outlook were changed to made those ems codes
you can of cause make manual smilies like
Is the change really that serious? I thought the SMS receiving function was only handled by one DLL called SMSReceiver_DLL.dll.
I have tried sending an EMS from a Nokia phone to Xda II, unfortunately I got no response from Xda II at all, I mean NOTHING, no notification, no garbage characters SMS in Inbox (tmail.exe), not a single sign of any incoming sms or anything!
I suspect that this SMSReceiver thingy is written to handle SMS only, and anything with a header which does not comply to a normal SMS, namingly EMS -- IT DOES NOTHING! This is most unfair.
yeah that might do it
of cause you would also have to make some application to make then
and possibly view them something like mms compose
i dont think that outlook and display pictures like that
of cause i could be wrong
also composing them would also prob be an issue with outlook
i think that phonecompany's and cellphone makers are pushing mms these days so i doubt that it will be in the xda3
do the newer nokia and sonyericsson even support the std anymore ?
Rudegar said:
also composing them would also prob be an issue with outlook
i think that phonecompany's and cellphone makers are pushing mms these days so i doubt that it will be in the xda3
do the newer nokia and sonyericsson even support the std anymore ?
Click to expand...
Click to collapse
there was a program by eMood soft which handles EMS message (sending & receiving) but it's not designed for Phone Edition. I installed it, it looked good but too bad it can only work via Com ports, IR, Bluetooth etc ... Can't use it on Xda II at all. And the website for this eMood seems to have shut for good. No sign of any other software that works under WM2003 Phone Edition.
Well, as you said most providers are now pushing for MMS ... but in many Asian countries, EMS are still widely used for leisure. And for new Nokia phones or SE phones (even P900), EMS seems to be pretty standard.
Hey folks,
So here's the rundown.
My wife is deaf and communicates a whole lot via SMS. She cannot use voice telephony at all.
I am on Verizon, and they do have the Z2 available. I was looking at tablets that should support SMS.
Verizon does SMS via CDMA only so most of their tablets won't do SMS period. They tell me it is impossible, except I have a friend with an older Nexus 7 with CDMA and it works perfectly with straight SMS.
I have a tablet with LTE, and when I send a SMS message from it, it says it is coming from my phone, not the number assigned to the tablet....(this uses the built-in Verizon Messages app)
What I want to know is if I can add an SMS app, set it as the default, and then actually use it?
In the store, I installed 8SMS but Verizon appears to have removed the menu entries for setting default SMS app, and nor could I do it from within the application.
So, two things: Has anyone done this? Could someone give it a try?
Also, I am reading a whole lot about issues with the touch screen I had never heard of. Is this really wide-spread, or just a small sampling of this model? I really want a solid device for her to use. This will replace her phone and existing tablet if I can get the SMS to work. Do you recommend this device overall?
Yes, I know, I could install some crap app that emulates SMS but I really need to port her number and have the reliability of SMS. Frankly, I don't trust the companies providing SMS gateways on the internet...
I could possibly port her number to Google Voice, and just have her use that. Anyone know how reliable that would be?
Hello,
I use/rely on Send SMS actions in multiple macros, throughout the macro stages to give me real time updates of what's happening in the Macros. It works fine for most parts.
The problem with some mobile carriers, specifically the one I use: Mint mobile (which is a MVNO on the T-Mobile network) that after sending many text messages, they might block you from sending new messages or put an invisible bottle neck so some text messages might arrive with a big delay or won't arrive at all. This makes it very unreliable and tricky as some "notification received" based triggers that you know that were supposed to trigger but didn't, so it's not entirely clear if it's because some legit issue with the notification not being received or identified by Macrodroid (yes, I know you can look at the macro logs) or just because your mobile carrier prevented you from receiving new text messages for a short duration.
All of this, is leading me to look for Send SMS alternatives (don't think Send Email is a good enough alternative as I want to receive notifications in my phone - And emails could suffer from the issues described above too) that don't require UI Interaction, and let me explain why: These are the main cons/issues with sending messages that require UI Interaction (for example Send WhatsApp message action that's being offered inside Macrodroid):
a.) If you have any macro that uses UI Interaction, and you want to send a message throughout the macro, because sending a message requires UI Interaction, this could break the existing flow of the macro as you need to be able to return to the same screen and state that you had before you had to send a message through UI Interaction.
b.) If you have multiple macros being triggered at the same time, and they all need to send messages, this will create a race condition - So what do you do? I don't think Macrodroid has a semaphore mechanism to prevent such case? As you basically need to make any existing macro to go to sleep, wait until the current macro that's using ui interaction to send a message finishes, before the ones that wait can continue in the same order they requested to send the message.
With that being said, are there any alternative ways (without rooting the phone) to send messages through 3rd party apps, without using UI Interaction?
Some methods to consider:
1.) Can you use the "send intent" action to tell an app to send a message to a certain user/phone without actually using UI Interaction? I know this could pose a security risk and it's unlikely to exist in any major big 3rd party messaging apps, but maybe smaller ones or ones that were created exactly for this purpose (such as MDHelper is using an older SDK to support certain actions that Macrodroid can't do)?
2.) Could you use some sort of APIs of certain big messaging apps, such as WhatsApp, Skype, Viber, Telegram, etc to send a message to a certain user/phone just by issuing some API call? Is there any support like that in Macrodroid to login to these services and then send messages (This is more Postman program level I suppose so might be a little out of scope)?
3.) Perhaps a more practical approach to avoid issues a & b, is simply not to use UI Interaction but simply send a message with the details (using send email or something like that - which again, as stated above, might not be 100% reliable) to another machine/phone that handles sending the messages, which is creating another point of failure, and could add some overhead/delay, so might not be the most ideal solution either.
Any other methods or alternatives that you know or could recommend?
Thank you.