Since disconnecting the Treo 680 from an active network connection is now a PITA, I better not see huge network charges when I get my first bill from Cingular after I've upgraded to the 680.

With my 600, for example, if I received an MMS picture, it would download it then automatically disconnect from the network. The Treo 680, OTOH, will connect to the network to download a picture, then stay connected after it's done.

Hopefully it's not constantly sending and receiving packets, which would incur a charge for every up and down byte, which Cingular will gladly charge me for.

Add to that the 54 steps you now have to go through to disconnect from the network, and it smells of collusion. ("Hey Treo, can you make disconnecting a little bit more burdensome on the new 680? Our statistics show that revenue from our data plans aren't as high as our CEO wants them to be, so I in trying to bump them up a little bit we figured that making disconnecting from the network less automatic--and requiring more user input--that it would slowly increase network usage. If/When the user ever finds out on their next bill, they'll have a tough time arguing that it was usage that didn't stem from their usage. I mean, if it's connected that means they were browsing a web site or downloading a picture, right?! Thanks Treo, Love Cingular."

Paint me cynical, but how else do you explain the strange network connectivity issues from the 600 to the 680? And why would the process to disconnect be MORE difficult and cumbersome, not LESS?

I got a picture message four hours ago. I just checked my phone and the green arrows above my signal bars have been on the entire time, even though I only downloaded the one picture four hours ago. Since the bills don't show detailed byte usage down to the day/time, it's so easy for them to stick me with extra charges. How am I supposed to know for sure that nothing, after my original picture, was exchanged between my phone and the network?

Does anyone know of a packet analyzer application for our Treos?