Loading ...
Sorry, an error occurred while loading the content.

SAMSUNG and forward-lock

Expand Messages
  • adelalom
    Hi, Are the SAMSUNG SGH-E340 and SGH-X460 really DRM forward-lock compliant as mentioned in WURFL? Using WURFL I dynamically serve forward-lock content
    Message 1 of 8 , Mar 31, 2006
    • 0 Attachment
      Hi,


      Are the SAMSUNG SGH-E340 and SGH-X460 really DRM forward-lock
      compliant as mentioned in WURFL?

      Using WURFL I dynamically serve forward-lock content depending on
      the phone capability.

      So far, things have been working well with different makes of
      mobiles but SAMSUNG SGH-E340 and SGH-X460 display "content not
      supported".

      When none forward-lock content is sent to these phones, content are
      correctly received.

      Is anyone has already encounter this issue? What could be the reason
      of this ?

      Bellow is the UA and WURFL ID of the SGH-X460

      UA: SAMSUNG-SGH-X460/1.0 UP.Browser/6.1.0.6 (GUI) MMP/1.0
      ID: id=samsung_x460_ver1_sub10

      Your help will be appreciated.

      Thanks
    • Juan Nin
      I found the same problem with Motorola E380. I sent an e-mail to the list asking if someone could confirm this, but got no reply... (
      Message 2 of 8 , Apr 1, 2006
      • 0 Attachment
        I found the same problem with Motorola E380. I sent an e-mail to the list
        asking if someone could confirm this, but got no reply... (
        http://groups.yahoo.com/group/wmlprogramming/message/20189)

        Does anybody have any of this phones so as to confirm this facts?

        Regards,

        Juan


        On 3/31/06, adelalom <delalom@...> wrote:
        >
        > Hi,
        >
        >
        > Are the SAMSUNG SGH-E340 and SGH-X460 really DRM forward-lock
        > compliant as mentioned in WURFL?
        >
        > Using WURFL I dynamically serve forward-lock content depending on
        > the phone capability.
        >
        > So far, things have been working well with different makes of
        > mobiles but SAMSUNG SGH-E340 and SGH-X460 display "content not
        > supported".
        >
        > When none forward-lock content is sent to these phones, content are
        > correctly received.
        >
        > Is anyone has already encounter this issue? What could be the reason
        > of this ?
        >
        > Bellow is the UA and WURFL ID of the SGH-X460
        >
        > UA: SAMSUNG-SGH-X460/1.0 UP.Browser/6.1.0.6 (GUI) MMP/1.0
        > ID: id=samsung_x460_ver1_sub10
        >
        > Your help will be appreciated.
        >
        > Thanks
        >
        >
        >
        >
        >
        >
        >
        >
        > As of July 14 2005, it's much easier to be banned from WMLProgramming!
        > Please fail to read http://groups.yahoo.com/group/wmlprogramming/ before
        > you post.
        > Yahoo! Groups Links
        >
        >
        >
        >
        >
        >
        >


        [Non-text portions of this message have been removed]
      • Nic Benders
        ... Are you serving the DRM d objects as direct downloads, OMA downloads or inline objects? I ve found that while some phones (Motorola V3) support DRM on
        Message 3 of 8 , Apr 4, 2006
        • 0 Attachment
          --- In wmlprogramming@yahoogroups.com, "adelalom" <delalom@...> wrote:
          > Are the SAMSUNG SGH-E340 and SGH-X460 really DRM forward-lock
          > compliant as mentioned in WURFL?
          >
          > Using WURFL I dynamically serve forward-lock content depending on
          > the phone capability.
          >
          > So far, things have been working well with different makes of
          > mobiles but SAMSUNG SGH-E340 and SGH-X460 display "content not
          > supported".
          >
          > When none forward-lock content is sent to these phones, content are
          > correctly received.
          >
          > Is anyone has already encounter this issue? What could be the reason
          > of this ?

          Are you serving the DRM'd objects as direct downloads, OMA downloads
          or inline objects? I've found that while some phones (Motorola V3)
          support DRM on inline objects (like <img> tags), others (Nokia 6820)
          only support it as a download (<a> tag). I have not found an existing
          WURFL property to determine this though.
        • Sewa Agbodjan
          ... I m serving the content using direct download. The mobile hits an URL like this with the parameters identifying my content:
          Message 4 of 8 , Apr 4, 2006
          • 0 Attachment
            >
            > Are you serving the DRM'd objects as direct downloads, OMA downloads
            > or inline objects? I've found that while some phones (Motorola V3)
            > support DRM on inline objects (like <img> tags), others (Nokia 6820)
            > only support it as a download (<a> tag). I have not found an existing
            > WURFL property to determine this though.
            >
            >

            I'm serving the content using direct download.
            The mobile hits an URL like this with the parameters identifying my
            content: http://192.168.10.0/serv_content.jsp/mel/10/foo.mid

            Ooooh ok I think I understand what I'm doing wrong.
            I'm writing the real type of the extension of my content at the end
            of my URL instead of the .dm file extension.

            A couple of mobile understand the"foo.mid" file although it is a DRM
            file which is generated.

            As soon as I correct this I will let you know about it.

            Sorry for any inconvenience and thanks for bringing it to my attention.

            Sewa
          • Sewa Agbodjan
            I finally corrected my URL as this:: http://192.168.10.10/serv_content.jsp/mel/10/foo.dm when the mobile support DRM forward-lock. I tested with the Samsung
            Message 5 of 8 , Apr 5, 2006
            • 0 Attachment
              I finally corrected my URL as this::
              http://192.168.10.10/serv_content.jsp/mel/10/foo.dm when the mobile
              support DRM forward-lock.

              I tested with the Samsung SGH-X460 which is stated in WURFL to
              support forward-lock and this the the error message I got : " Content
              type not supported"

              I created a dm file using Nokia Mobile Internet Toolkit that I tried
              to download it(http://192.168.10.10/1.dm) with The SGH-X460 and I got
              the same error message.
              ( application/vnd.oma.drm.message dm was added to server mime type)

              The conclusion is the Samsung SGH-X460 doesn't not support forward-lock file.

              What is the procedure to correct this in WURFL ?
              I mean how do you make the decision to correct capability that is
              wrong in WURFL ?


              Thanks.

              Sewa




              On 4/4/06, Sewa Agbodjan <delalom@...> wrote:
              > >
              > > Are you serving the DRM'd objects as direct downloads, OMA downloads
              > > or inline objects? I've found that while some phones (Motorola V3)
              > > support DRM on inline objects (like <img> tags), others (Nokia 6820)
              > > only support it as a download (<a> tag). I have not found an existing
              > > WURFL property to determine this though.
              > >
              > >
              >
              > I'm serving the content using direct download.
              > The mobile hits an URL like this with the parameters identifying my
              > content: http://192.168.10.0/serv_content.jsp/mel/10/foo.mid
              >
              > Ooooh ok I think I understand what I'm doing wrong.
              > I'm writing the real type of the extension of my content at the end
              > of my URL instead of the .dm file extension.
              >
              > A couple of mobile understand the"foo.mid" file although it is a DRM
              > file which is generated.
              >
              > As soon as I correct this I will let you know about it.
              >
              > Sorry for any inconvenience and thanks for bringing it to my attention.
              >
              > Sewa
              >


              --
              "Aller à l'église ne vous rend pas plus chrétien qu'aller au garage ne
              fait de vous un mecanicien"
              Laurence J. Peter
            • Juan Nin
              The same happens with the Motorola E380 With direct download the .dm file doesn t work given a similar error message If you download the midi file without DRM
              Message 6 of 8 , Apr 6, 2006
              • 0 Attachment
                The same happens with the Motorola E380
                With direct download the .dm file doesn't work given a similar error message
                If you download the midi file without DRM it works

                I use Sony Ericsson DRM Packager


                Sewa Agbodjan wrote:
                > I finally corrected my URL as this::
                > http://192.168.10.10/serv_content.jsp/mel/10/foo.dm when the mobile
                > support DRM forward-lock.
                >
                > I tested with the Samsung SGH-X460 which is stated in WURFL to
                > support forward-lock and this the the error message I got : " Content
                > type not supported"
                >
                > I created a dm file using Nokia Mobile Internet Toolkit that I tried
                > to download it(http://192.168.10.10/1.dm) with The SGH-X460 and I got
                > the same error message.
                > ( application/vnd.oma.drm.message dm was added to server mime type)
                >
                > The conclusion is the Samsung SGH-X460 doesn't not support forward-lock file.
                >
                > What is the procedure to correct this in WURFL ?
                > I mean how do you make the decision to correct capability that is
                > wrong in WURFL ?
                >
                >
                > Thanks.
                >
                > Sewa
                >
                >
                >
                >
                > On 4/4/06, Sewa Agbodjan <delalom@...> wrote:
                >
                >>>Are you serving the DRM'd objects as direct downloads, OMA downloads
                >>>or inline objects? I've found that while some phones (Motorola V3)
                >>>support DRM on inline objects (like <img> tags), others (Nokia 6820)
                >>>only support it as a download (<a> tag). I have not found an existing
                >>>WURFL property to determine this though.
                >>>
                >>>
                >>
                >>I'm serving the content using direct download.
                >>The mobile hits an URL like this with the parameters identifying my
                >>content: http://192.168.10.0/serv_content.jsp/mel/10/foo.mid
                >>
                >>Ooooh ok I think I understand what I'm doing wrong.
                >>I'm writing the real type of the extension of my content at the end
                >>of my URL instead of the .dm file extension.
                >>
                >>A couple of mobile understand the"foo.mid" file although it is a DRM
                >>file which is generated.
                >>
                >>As soon as I correct this I will let you know about it.
                >>
                >>Sorry for any inconvenience and thanks for bringing it to my attention.
                >>
                >>Sewa
                >>
                >
                >
                >
                > --
                > "Aller à l'église ne vous rend pas plus chrétien qu'aller au garage ne
                > fait de vous un mecanicien"
                > Laurence J. Peter
                >
                >
                >
                >
                >
                > As of July 14 2005, it's much easier to be banned from WMLProgramming!
                > Please fail to read http://groups.yahoo.com/group/wmlprogramming/ before you post.
                > Yahoo! Groups Links
                >
                >
                >
                >
                >
                >
                >
              • Andrea Trasatti
                ... Juan, Sewa, if we need to fix WURFL it s not a problem. 1) make sure the DRM file is correct, for example download it with another phone that you KNOW
                Message 7 of 8 , Apr 22, 2006
                • 0 Attachment
                  Il giorno 06/apr/06, alle ore 22:24, Juan Nin ha scritto:

                  > The same happens with the Motorola E380
                  > With direct download the .dm file doesn't work given a similar
                  > error message
                  > If you download the midi file without DRM it works
                  >
                  > I use Sony Ericsson DRM Packager

                  Juan, Sewa, if we need to fix WURFL it's not a problem.
                  1) make sure the DRM file is correct, for example download it with
                  another phone that you KNOW supports DRM
                  2) download the unprotected file just to make sure the source format
                  is supported

                  If so, we can update WURFL.

                  Andrea Trasatti
                  My Blog: http://trasatti.blogspot.com/
                  W3C MWI invited expert
                • Juan Nin
                  ... The same .dm (an AMR with forward-lock) file was downloaded to a Nokia 3100 and worked fine ... The AMR file without foward-lock was downloaded to the
                  Message 8 of 8 , Apr 26, 2006
                  • 0 Attachment
                    Andrea Trasatti wrote:
                    > Il giorno 06/apr/06, alle ore 22:24, Juan Nin ha scritto:
                    >
                    >
                    >>The same happens with the Motorola E380
                    >>With direct download the .dm file doesn't work given a similar
                    >>error message
                    >>If you download the midi file without DRM it works
                    >>
                    >>I use Sony Ericsson DRM Packager
                    >
                    >
                    > Juan, Sewa, if we need to fix WURFL it's not a problem.
                    > 1) make sure the DRM file is correct, for example download it with
                    > another phone that you KNOW supports DRM

                    The same .dm (an AMR with forward-lock) file was downloaded to a Nokia 3100 and worked fine

                    > 2) download the unprotected file just to make sure the source format
                    > is supported

                    The AMR file without foward-lock was downloaded to the Motorola E380 and worked fine

                    >
                    > If so, we can update WURFL.

                    so I guess E380 does not actually support forward-lock

                    regards,

                    Juan
                  Your message has been successfully submitted and would be delivered to recipients shortly.