[rjmoose]

Dont know if this has been posted yet, but it's a start:

http://mytreo.net/archives/2006/11/s...-carriers.html

[lgreenberg]

What am I missing?

The MTDN article was posted 11/2.

T.C. posted on about the issue on 10/19.

http://www.treocentral.com/content/Stories/945-1.htm

[Malatesta]

What am I missing?

The MTDN article was posted 11/2.

T.C. posted on about the issue on 10/19.

http://www.treocentral.com/content/Stories/945-1.htm

I think the OP is implying that other sites are finally picking up on it

TC was a start but seriously, no Engadget, still waiting on PCSintel (not holding my breath), mobility today, etc... We need as much coverage as possible.

[rjmoose]

I think the OP is implying that other sites are finally picking up on it

TC was a start but seriously, no Engadget, still waiting on PCSintel (not holding my breath), mobility today, etc... We need as much coverage as possible.

And Phonescoop.com just completely blew me off...NOTHING from them!!!

[Jdoc]

guys; trust me: engadget hasn't posted anything yet because it has not received many emails about it. they NEVER reject a story when a lot of people write about it.

AND its the most visited technology blog. one that actually has an impact on these companies.

EVERYBODY WRITE TO ENGADGET! no duplicates, write your own message and it WILL get posted!

just go engadget and look for 'send us a tip'

[Malatesta]

guys; trust me: engadget hasn't posted anything yet because it has not received many emails about it. they NEVER reject a story when a lot of people write about it.

AND its the most visited technology blog. one that actually has an impact on these companies.

EVERYBODY WRITE TO ENGADGET! no duplicates, write your own message and it WILL get posted!

just go engadget and look for 'send us a tip'

Agreed.

Can people click this link and type a few words?

http://www.engadgetmobile.com/tips/

[Certs]

Agreed.

Can people click this link and type a few words?

http://www.engadgetmobile.com/tips/

As you were writing this post I was doing exactly this. I hope it helps, we'll see. I've hoped a LOT of things helped, and they haven't yet...

[hannip]

I sent them a nice detailed tip.

[SprintJunkie]

Hannip can fix it, I KNOW he can!

[SprintJunkie]

Agreed.

Can people click this link and type a few words?

http://www.engadgetmobile.com/tips/

Done

[Malatesta]

Woohoo..

C'mon people. Lets get like 10 more!

Write a tip to Engadget!
http://www.engadgetmobile.com/tips/

[Certs]

Add this to your sticky on the other site also..

[Malatesta]

Add this to your sticky on the other site also..

good point, will do.

actually, a little funny tid bid that was posted at that thread today:

What I found very interesting and a credit to those on this site that have contacted Sprint about this issue is that in his database there is a direct link to the PPCGeeks post for more information which has the details that Malatesta posted as an official explanation.

I thought this was really cool that Sprint is officially linking to this site (ppcgeeks) for more detailed information.

[hannip]

Hannip can fix it, I KNOW he can!

Believe me I've tried... Still trying, but everything to me points back to Sprints network. How it could've worked fine for a month just can't be escaped. If it was what they claimed then it would've never worked on vzw, t-mobile, aim forwarding etc. But it worked fine for a whole month! And even if the 700wx did things a little different, why on earth can't they treat it like they did for that month? I just don't believe that Palm needs to make an update to get this working like it already worked for a month.

Sorry, just venting.

[stroths]

I sent engadget a request as well.

[Jdoc]

well I was hoping we could send a tip to regular engadget, not mobile, as it has much much less page views. humm howsabout writing to both, then? ill do my part when I get home I'm on my treo in a food cort on lunch break lol.

[Certs]

Believe me I've tried... Still trying, but everything to me points back to Sprints network. How it could've worked fine for a month just can't be escaped. If it was what they claimed then it would've never worked on vzw, t-mobile, aim forwarding etc. But it worked fine for a whole month! And even if the 700wx did things a little different, why on earth can't they treat it like they did for that month? I just don't believe that Palm needs to make an update to get this working like it already worked for a month.

Sorry, just venting.

Yeah, but the whole coding aspect makes sense. 50 other phones use the "sprint" network, yet ONLY this phone has the problem.

Let me rephrase- NOTHING really makes sense, but you can make points for both. I'm so tired of this right now, I call Sprint every day hoping to get somewhere. not sure exactly WHERE, but somewhere

[Certs]

The site I posted to was here

http://www.engadget.com/contact/tips/

[hannip]

Yeah, but the whole coding aspect makes sense. 50 other phones use the "sprint" network, yet ONLY this phone has the problem.

But what is interesting is that the base64 encoding problems didn't start happening until after that first month of it working fine. If there was an encoding issue then how did it work for that first month. It's just not statistically possible that the base64 encoding issue started happening for everyone at that same time. Keeps pointing back to Sprint.

[Paulinbna#WN]

I just added to the tip page also.