t-zones home error: "File format unknown" -- ***?

Here's what my Nokia 6610 T-Mobile handset now does when I depress the dedicated 0 key long enough to make a GPRS connection to the t-zones home page:

1) message box "Connecting via t-zones" arises, and GPRS indicator appears;
2) error message "File format unknown" appears, and GPRS indicator disappears; and
3) home screen returns.

On the other hand, if I select any of the bookmarks stored in that handset (other than the t-zones home page), I have no trouble connecting to that bookmark directly "via t-zones," so GPRS connectivity per se is *not* the issue here.

The WAP browser in the Nokia 6610 is one of those WML only, vintage 2003-or-earlier, browsers, that chokes on more general HTML -- could the t-zones home page (at wap.myvoicestream.com) have stopped detecting my Nokia 6610 handset correctly, and be trying to feed it indigestible, non-WML, HTML?

Are others aware of similar t-zones issues with other handsets?

TIA; and cheers, -- tlvp

At 29 Dec 2010 15:54:55 -0500 tlvp wrote:
> Here's what my Nokia 6610 T-Mobile handset now does when I depress the
dedicated 0 key long enough to make a GPRS connection to the t-zones home
page:
>
> 1) message box "Connecting via t-zones" arises, and GPRS indicator
appears;
> 2) error message "File format unknown" appears, and GPRS indicator
disappears; and
> 3) home screen returns.
>
> On the other hand, if I select any of the bookmarks stored in that
handset (other than the t-zones home page), I have no trouble connecting
to that bookmark directly "via t-zones," so GPRS connectivity per se is
*not* the issue here.
>
> The WAP browser in the Nokia 6610 is one of those WML only, vintage
2003-or-earlier, browsers, that chokes on more general HTML -- could the
t-zones home page (at wap.myvoicestream.com) have stopped detecting my
Nokia 6610 handset correctly, and be trying to feed it indigestible, non-
WML, HTML?
>
> Are others aware of similar t-zones issues with other handsets?
>
> TIA; and cheers, -- tlvp


My WinMo phone reports the wap.myvoicestream.com page as a 16k HTML page,
not wml or xhtml, so I suspect your 6610 is choking on it. I haven't
played with a 6610 in years (my wife had one back when I used a 3650,)
but IIRC the browser used to choke on a lot of HTML pages.

On Wed, 29 Dec 2010 17:50:41 -0500, Todd Allcock <elecconnec@anoospaml.com> wrote:

> ...
>
> My WinMo phone reports the wap.myvoicestream.com page as a 16k HTML page,
> not wml or xhtml, so I suspect your 6610 is choking on it. I haven't
> played with a 6610 in years (my wife had one back when I used a 3650,)
> but IIRC the browser used to choke on a lot of HTML pages.

The 6610 used to have no trouble rendering the wap.myvoicestream.com page
as recently as a month or two ago. I believe that page "sniffs" for browser
type, and responds accordingly, sending the 6610 a small WML deck rather
than a 16k HTML page -- or that's what it used to do, anyway.

T-Mo "Engineering" is reportedly examining the sniff-coding of the page ... .

Fortunately, the WAP sites I need are all encoded as links on one .wml page
that I maintain and have entered as a bookmark on the handset ... and
there's a (poorly documented) back door available to those stored bookmarks,
not requiring t-zones :-) .

Cheers, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP