Receiving WAP Push on HTC Tattoo


Last Updated:

  1. stuart121972

    stuart121972 Active Member This Topic's Starter

    Joined:
    Jun 2, 2010
    Messages:
    31
    Likes Received:
    2
    Hi

    New to the forum and hope someone can help. When I do work for a particular customer of mine sends he me a WAP push message. This contains a URL link to the details of the job I'm carrying out for him so that I can update his system with the job progress without having to ring him up, etc.

    The problem is since I got my Tattoo I've not been able to receive these messages from him and can't figure out why. SMS & MMS works fine and so I Can't figure out why these particular types of messages don't get to me.

    Hope I've not been to vague and someone can help.

    Thanks
     

    Advertisement
  2. stuart121972

    stuart121972 Active Member This Topic's Starter

    Joined:
    Jun 2, 2010
    Messages:
    31
    Likes Received:
    2
    I take it no one can answer this :(
     
  3. Abbe dev

    Abbe dev New Member

    Joined:
    Aug 30, 2010
    Messages:
    2
    Likes Received:
    0
    Stuart,

    Android comes without WAP Push support, sort of. In order for he sort of WAP Push messages you receive to work, the device must support the SI (Service Indicator) format of messages. Then the URL in the WAP Push must be opened using WAP protocol stack (also not present in Android) using appropriate GPRS APN (by deafult, as payable content also is delivered this way).

    so, I suggest you call HTC, tell them to get in touch with someone that has such a solution that they can quickly install (e.g. Winwap Technologies - Home) and buy a Android WAP Stack which provides all of the above out of the box. Then you can again with your next Android device receive those important messages from your customer :)

    Not so helpful in your current situation I am afraid, sorry.

    cheers,
    Abbe

     
  4. stuart121972

    stuart121972 Active Member This Topic's Starter

    Joined:
    Jun 2, 2010
    Messages:
    31
    Likes Received:
    2
    Since posting this my customer has now come up with a workaround that seems to work ok.
     

Share This Page

Loading...