It didn't take me very long to decide that the iPhone would not be replacing my Sprint Treo 700p anytime soon (even setting aside the financial details of contracts and monthly fees). There is too much I would have to give up. But, part of my original idea was that maybe the "reinvented cellphone" would be something that my wife (hardly a technophobe, but not a "gadget gal") might find useful to replace her aging Nokia 6015i on Verizon.
So, she had the use of the iPhone for two days at work, to find out about it's performance and usefulness, mainly AS A PHONE. That would be mostly as a part-time phone: she averages only about 25 minutes monthly! Her most frequent call is to me at home to say "I'm late" or "I'm coming now", so that I can finish cooking supper, and get it on the table on time.
Although it was snazzy in appearance, and easy to use, there were several reception problems in various places at her work. The home "noPhone" became an office "sometimePhone". The AT&T network is no match for Verizon or Sprint here in East Lansing, Michigan.
Once I have more time to talk with her at length, I'll also report more about the actual operation of the phone. She did give me a few notes. I need to ask more about her experience. However, she was underwhelmed.
Bottom line evaluation: "enhh..."
Showing posts with label ATT wireless network. Show all posts
Showing posts with label ATT wireless network. Show all posts
Friday, July 13, 2007
Black, bleak Friday
Today was Friday the 13th. It was also the end of the 14-day iPhone trial period.
Unable to resolve the problem of "No Service" at home and spotty service elsewhere, I returned the iPhone to the AT&T store for a refund. At first, the new cashier tired to tell me that it was 15 days! But the manager allowed the return on the more realistic basis that two Friday after purchase is indeed 14 days. Unfortunately, they imposed a 10% restocking fee. This had not been disclosed to me in spite of asking lots of questions in advance. They claimed to have included a form disclosing the fee in the bag (which they hadn't). The fee was also NOT mentioned in the brochure that I received and read while in the store waiting to be served.
I will dispute the extra $50+ charge to my credit card. It's bad enough that I will be on the hook for the $36 activation fee and 1/2 month service (about $30), at least $66+taxes.
There are certainly some limitations and flaws to the iPhone, but the AT&T network is the real problem. What good is a phone that can't make or receive calls?
Now comes the bleak, black depression of "NoPhone"...
(But I will still write and write to describe my experiences, so don't go away. I promise at least a post per day for the rest of July.)
Unable to resolve the problem of "No Service" at home and spotty service elsewhere, I returned the iPhone to the AT&T store for a refund. At first, the new cashier tired to tell me that it was 15 days! But the manager allowed the return on the more realistic basis that two Friday after purchase is indeed 14 days. Unfortunately, they imposed a 10% restocking fee. This had not been disclosed to me in spite of asking lots of questions in advance. They claimed to have included a form disclosing the fee in the bag (which they hadn't). The fee was also NOT mentioned in the brochure that I received and read while in the store waiting to be served.
I will dispute the extra $50+ charge to my credit card. It's bad enough that I will be on the hook for the $36 activation fee and 1/2 month service (about $30), at least $66+taxes.
There are certainly some limitations and flaws to the iPhone, but the AT&T network is the real problem. What good is a phone that can't make or receive calls?
Now comes the bleak, black depression of "NoPhone"...
(But I will still write and write to describe my experiences, so don't go away. I promise at least a post per day for the rest of July.)
Thursday, July 12, 2007
Going to Chicago ...
On Saturday morning, we (me & my wife) drove from East Lansing to Chicago to visit my son for the weekend. Another opportunity for "bar driving" and testing some of the iPhone features.
Once we had driven the 6 blocks or so from our house to the freeway (US127), the reception was up to 3 bars and it stayed that way (3 to 5 bars -- 4 bars typical) pretty much all the way to (& from) Chicago (I496/I69/I94/I294) and certainly while in the "big city", even on the El.
While she was driving, I was able to read e-mail and surf the net with ease. I browsed to the MLS Web site and downloaded a 32-page PDF of game notes for the Chicago Fire v Toronto FC soccer match that we were planning to watch that night. Even the PDF was able to be zoomed with the "double tap" and "pinch" gestures to make it very easy to read. Wow! This will put the program vendors out of business.
Of course, I was also able to call my son and let him know we were underway and when our expected arrival would be.
The iPhone is a pretty awesome "HiwayPhone" ...
Once we had driven the 6 blocks or so from our house to the freeway (US127), the reception was up to 3 bars and it stayed that way (3 to 5 bars -- 4 bars typical) pretty much all the way to (& from) Chicago (I496/I69/I94/I294) and certainly while in the "big city", even on the El.
While she was driving, I was able to read e-mail and surf the net with ease. I browsed to the MLS Web site and downloaded a 32-page PDF of game notes for the Chicago Fire v Toronto FC soccer match that we were planning to watch that night. Even the PDF was able to be zoomed with the "double tap" and "pinch" gestures to make it very easy to read. Wow! This will put the program vendors out of business.
Of course, I was also able to call my son and let him know we were underway and when our expected arrival would be.
The iPhone is a pretty awesome "HiwayPhone" ...
Saturday, July 7, 2007
Is 07-07-07 my lucky day?
I hope so, because yesterday was just depressing.
After my "Bar driving" experience, I decided to call the AT&T store and see what, if anything, they could suggest to "improve your experience" -- like being able to make a freakin' phone call from home! or receive one!
While "Bruce" was polite and appologetic, he didn't really offer any solution to my issue with the AT&T network. No known tower problems, no knowledge of when or if they would address the East Lansing "dead zone". I pried out of him that a repeater anntenna might help, but they don't know of anything. "We just refer people to anntenna.com" or Wireless Giant (a local accessory store). He concluded (actually several times during the call), noting that there is a 14-day return policy on the iPhone. Sad, just sad.
My wife suggested I call Apple. (well, duh! good idea!).
I was on hold for about 2 minutes to the support number that was included in my activation e-mail (AT&T's local store answered as soon as I got through the menus). "Steve" in Cupertino (or where ever), heard out my problem, but had no suggestions either, short of wireless.att.com and apple.com/support discussion forums. He opined that describing the return policy was not the best response to a problem with "No Service" on the cell network. He was also puzzled (or at least silent) about the "baseband log" files that have appeared on my Windows computer ("I don't know much about that"), even when I described the contents as looking like records of failed phone calls that may be being sent back to the Apple mother ship. (Is Apple watching us? Are they gathering data on the "quality" of the AT&T network to bludgeon them with? I hope so!)
Today, we are going to visit my son in Chicago (also an MSU Computer Science grad), enjoy some of the food at "Taste of Chicago", watch a Chicago Fire MLS soccer match at Toyota park, and (suprise!) show off the iPhone. Coverage ought to be wonderful.
It's 07-07-07! It ought to be my lucky day...
After my "Bar driving" experience, I decided to call the AT&T store and see what, if anything, they could suggest to "improve your experience" -- like being able to make a freakin' phone call from home! or receive one!
While "Bruce" was polite and appologetic, he didn't really offer any solution to my issue with the AT&T network. No known tower problems, no knowledge of when or if they would address the East Lansing "dead zone". I pried out of him that a repeater anntenna might help, but they don't know of anything. "We just refer people to anntenna.com" or Wireless Giant (a local accessory store). He concluded (actually several times during the call), noting that there is a 14-day return policy on the iPhone. Sad, just sad.
My wife suggested I call Apple. (well, duh! good idea!).
I was on hold for about 2 minutes to the support number that was included in my activation e-mail (AT&T's local store answered as soon as I got through the menus). "Steve" in Cupertino (or where ever), heard out my problem, but had no suggestions either, short of wireless.att.com and apple.com/support discussion forums. He opined that describing the return policy was not the best response to a problem with "No Service" on the cell network. He was also puzzled (or at least silent) about the "baseband log" files that have appeared on my Windows computer ("I don't know much about that"), even when I described the contents as looking like records of failed phone calls that may be being sent back to the Apple mother ship. (Is Apple watching us? Are they gathering data on the "quality" of the AT&T network to bludgeon them with? I hope so!)
Today, we are going to visit my son in Chicago (also an MSU Computer Science grad), enjoy some of the food at "Taste of Chicago", watch a Chicago Fire MLS soccer match at Toyota park, and (suprise!) show off the iPhone. Coverage ought to be wonderful.
It's 07-07-07! It ought to be my lucky day...
Friday, July 6, 2007
WAR walking, Bar driving, and bunny running
Among other things the WiFone is a pretty good WiFi network detector.
There is a time-honored hacker pastime called "WAR driving". WAR is an acronym for "Wireless Access (point) Recognition" -- at least I think that's what it stands for -- like a lot of hacker jargon, the term is so often used without explanation that it takes on meaning without needing decoding. [If I'm wrong, or even if I'm right, post a comment. I'm too lazy to look it up in Wikipedia or Google right now.] "WAR driving", as you might guess by now, is driving around town with a notebook computer, or special-purpose WiFi detector, and noting the location, name, and accessibility of WiFi access points: a source of free (leechable) Internet bandwidth.
As we take out dog for a walk every evening, I've been doing some WAR walking around the neighborhood. It's interesting to see the names of my neighbors' networks pop up one after another as we stroll down the block.
Also today, I had to take the car in for an oil change, so on the way home, and again when out to fill up with gas, I engaged in what I dubbed "Bar driving" -- noting the number of bars on the iPhone's AT&T cell network indicator at different locations in Okemos, the MSU campus, and East Lansing. Signal strength is generally between 2 and 4 most places. It was a full 5 at the car dealership, but one of the sales staff told me that there is nearby cell tower and all the networks have good coverage. It is pretty near to the major Okemos I-96 freeway exit, so that makes sense.
Pretty much the only area that didn't have good service was when I got within a mile or so of home :(:(:( Then the "No Service" message popped up or at most 0 or 1 bar. Depressing!
And "bunny running"? That's what our dog wants to do during the evening walks as the little critters are out and about in several placea along our usual routes.
There is a time-honored hacker pastime called "WAR driving". WAR is an acronym for "Wireless Access (point) Recognition" -- at least I think that's what it stands for -- like a lot of hacker jargon, the term is so often used without explanation that it takes on meaning without needing decoding. [If I'm wrong, or even if I'm right, post a comment. I'm too lazy to look it up in Wikipedia or Google right now.] "WAR driving", as you might guess by now, is driving around town with a notebook computer, or special-purpose WiFi detector, and noting the location, name, and accessibility of WiFi access points: a source of free (leechable) Internet bandwidth.
As we take out dog for a walk every evening, I've been doing some WAR walking around the neighborhood. It's interesting to see the names of my neighbors' networks pop up one after another as we stroll down the block.
Also today, I had to take the car in for an oil change, so on the way home, and again when out to fill up with gas, I engaged in what I dubbed "Bar driving" -- noting the number of bars on the iPhone's AT&T cell network indicator at different locations in Okemos, the MSU campus, and East Lansing. Signal strength is generally between 2 and 4 most places. It was a full 5 at the car dealership, but one of the sales staff told me that there is nearby cell tower and all the networks have good coverage. It is pretty near to the major Okemos I-96 freeway exit, so that makes sense.
Pretty much the only area that didn't have good service was when I got within a mile or so of home :(:(:( Then the "No Service" message popped up or at most 0 or 1 bar. Depressing!
And "bunny running"? That's what our dog wants to do during the evening walks as the little critters are out and about in several placea along our usual routes.
Labels:
ATT wireless network,
cell phone service,
iPhone review,
WiFi
Thursday, July 5, 2007
Take me out to the ball game ...
Thursday summer nights in Lansing means "Thirsty Thursday" ($2 draft beer) at Oldsmobile Park in the heart of downtown, when the Lugnuts are in town to take on an opponent in the Class A- Midwest League of minor league baseball. Since we have a ticket package, I got to try out the iPhone in a new environment. It also meant 3+ hours actually on the AT&T EDGE network with 4 or 5 bars!
I also brought along my bluetooth headset (Jabra BT350) and, of course, my Treo 700p. I fiddled around with the headset and got it paired easily with the iPhone. I also forwarded my Treo number to the iPhone as well, so I could see how any calls I got sounded. Unfortunately, I didn't get that done before a call came in. And it was too noisy at the park without headset to really talk, so I had to ask the caller to catch me tomorrow. My wife did a couple test calls (from the seat next to me -- awkward -- not much to say) after I had things set up and sound quality was good on both ends.
I did receive a few e-mails easily, and made quite a bit of use of the Safari browser. I always keep a scorecard at a baseball game (old school!), and as it happened, they didn't have any preprinted rosters this night. So when a pitching change took place, and the announcement was drowned out by between-inning entertainment, I despaired until I remembered I had the Web in my pocket. The speed was not quite up to Treo standards, but the full page rendering and easy zooming of the South Bend Silverhawks roster page, made it worth a slight wait. And I easily called up the player profile page, so I not only got the name, but full stats (last 10 outings), picture, etc.
Of course the Palm platform supports ScorePad, a complete full-color, wonderfully detailed baseball scoring software package on the Treo (and other Palm devices). I've had a copy for several years and use it on and off. Lately though I've gone back to pencil and printed scorecard, since it doesn't require as much commitment -- I can always just annotate a batter as "IWW" (I Wasn't Watching) and move on, where the software demands to know what really happened: "K"? "1B"? "W","6-3"?
One downside to the touchscreen though: it's not easy to answer a call when in the midst of eating an order of "Super Nachos" unless you want sour cream and salsa on the screen!
All and all, a pleasant evening at the ball park. And the Luggies won 5-3, too, with the winning runs coming from a grand slam homer!
I also brought along my bluetooth headset (Jabra BT350) and, of course, my Treo 700p. I fiddled around with the headset and got it paired easily with the iPhone. I also forwarded my Treo number to the iPhone as well, so I could see how any calls I got sounded. Unfortunately, I didn't get that done before a call came in. And it was too noisy at the park without headset to really talk, so I had to ask the caller to catch me tomorrow. My wife did a couple test calls (from the seat next to me -- awkward -- not much to say) after I had things set up and sound quality was good on both ends.
I did receive a few e-mails easily, and made quite a bit of use of the Safari browser. I always keep a scorecard at a baseball game (old school!), and as it happened, they didn't have any preprinted rosters this night. So when a pitching change took place, and the announcement was drowned out by between-inning entertainment, I despaired until I remembered I had the Web in my pocket. The speed was not quite up to Treo standards, but the full page rendering and easy zooming of the South Bend Silverhawks roster page, made it worth a slight wait. And I easily called up the player profile page, so I not only got the name, but full stats (last 10 outings), picture, etc.
Of course the Palm platform supports ScorePad, a complete full-color, wonderfully detailed baseball scoring software package on the Treo (and other Palm devices). I've had a copy for several years and use it on and off. Lately though I've gone back to pencil and printed scorecard, since it doesn't require as much commitment -- I can always just annotate a batter as "IWW" (I Wasn't Watching) and move on, where the software demands to know what really happened: "K"? "1B"? "W","6-3"?
One downside to the touchscreen though: it's not easy to answer a call when in the midst of eating an order of "Super Nachos" unless you want sour cream and salsa on the screen!
All and all, a pleasant evening at the ball park. And the Luggies won 5-3, too, with the winning runs coming from a grand slam homer!
Wednesday, July 4, 2007
Two Bars!! ... I made and received my first phone call at home
My daughter, among others, was over for a 4th of July cookout. After we'd had lunch and she was getting ready to go to work at her part-time job, I glanced at the iPhone and beheld the AT&T legend and TWO BARS. Quickly I dialed her mobile number, and it rang in her pocket. "Who's calling me? Oh, it's Daddy on his iPhone!"
So she was honored to be the receipient of the my first successful call from inside my house. Just as quickly, I said, "Call me back!". In a few seconds, she was greeted by the ringtone "Quack, Quack. Quack" ... I had assigned her the "Duck" ringtone ;) We hung up, chuckling.
The signal faded. She still had three bars on her Verizon phone, as did I on my Sprint Treo. So, at least once per five days, the iPhone can actually be used to make and receive phone calls.
So she was honored to be the receipient of the my first successful call from inside my house. Just as quickly, I said, "Call me back!". In a few seconds, she was greeted by the ringtone "Quack, Quack. Quack" ... I had assigned her the "Duck" ringtone ;) We hung up, chuckling.
The signal faded. She still had three bars on her Verizon phone, as did I on my Sprint Treo. So, at least once per five days, the iPhone can actually be used to make and receive phone calls.
Monday, July 2, 2007
It's the Network, stupid!
As I contemplated my iPhone experiment (buy one, test it, take it back if it doesn't work out), one of my biggest concerns was "the new AT&T" Wireless network, and the "EDGE" data service.
I've had a cellphone since 1992 on Verizon (actually Cellular One --> Airtouch Cellular --> Verizon Wireless: same carrier, three names in 15 years), with an account that my wife and mother-in-law still share. VZW and I parted ways a while back -- when I did a paralell test for two weeks of the Treo 600 on their data network vs Sprint PCS. I've been on Sprint ("now together with Nextel") since 2004 with my Treo. I upgraded to the 700p last year.
In the Lansing market, we can also choose "the new AT&T" (Ameritech Wireless --> SBC Wireless + AT&T Wireless + Cingular --> AT&T) or Alltel (20th Century Wireless --> CenturyTel --> Alltel). T-Mobile has not really been much of a presence here, so mostly it's the big two: VZW or Sprint, with AT&T a contending third.
One of the obvious concerns was the EDGE data network of AT&T vs the EVDO on Sprint or VZW. Right from the iPhone announcement, this was the clear weakness. Reviews last week by the tech gurus (Walt Mossburg for WSJ and David Pogue for NYT) both cited this as a potential liability. But is it a deal breaker?
In my experience so far, there is a far more serious concern. Can I even make or receive calls? "iPhone"? -- "noPhone" is more like it. The AT&T regular cell voice network, let alone the EDGE data, is mostly "No Service" or sometimes 0 or 1 bars, at our house in the heart of residential East Lansing. Hardly the "more bars in more places" that was promised! After I activated the iPhone at about 2 in the morning Friday night, I was a bit concerned that the AT&T indicator only flickered on occasionally, but, then I was tired and maybe the network was overloaded or maybe the phone needed a full charge. I'd try again after some sleep.
In the cold, gray dawn of Saturday morning, a beautiful Michigan summer day was shaping up, but my iPhone couldn't even contact the voicemail service to set it up!! I looked up their coverage map, and, sure enough, a vast area of the residential neighborhoods of East Lansing have only "moderate" voice service! Overall, the coverage in Michigan is pretty much along the major highways only, outside of the Detroit mega-opolis. (The newer, true high-speed data network is only available in parts of Detroit and Ann Arbor.) But this is 2007 folks, and Lansing (I think) is not Podunk. VZW & Sprint seem to agree.
So, I took the iPhone outside, and got all the way up to 1 bar, but still no "E" to indicate data service. The coverage map showed that things were better to the south and west of me. It turns out that I'd left behind my lawn chair at the AT&T store, so I went back to retrieve it, and, indeed, I finally started to see more bars! And the "E" appeared! When I stopped in to the store, they all wanted to know what I thought so far. The answer was easy -- an amazing device on a crappy network. I don't even know how fast it is, because I can't even get enough service coverage to set up my voicemail, let alone browse the InterWeb! I earnestly requested that they put in a new tower within a mile of my house right away, or I'd probably have to (sadly) return the iPhone. They were stunned, but no one offered to strap on the tool belt and follow me home.
I went ahead and set up the voicemail sitting in the parking lot, and drove on to further experiments. In a later post, I'll report on some timings I've done of Web page retrievals, comparing my Sprint Treo 700p to the iPhone, both on the AT&T network (outside my house) and on WiFi (inside and out).
But, for now, the iPhone is just a JulyPhone, and not a DecemberPhone -- at least in Michigan -- if you have to take it outside to receive or make a phone call...
Message to Apple and AT&T: "It's the NETWORK, stupid!"
I've had a cellphone since 1992 on Verizon (actually Cellular One --> Airtouch Cellular --> Verizon Wireless: same carrier, three names in 15 years), with an account that my wife and mother-in-law still share. VZW and I parted ways a while back -- when I did a paralell test for two weeks of the Treo 600 on their data network vs Sprint PCS. I've been on Sprint ("now together with Nextel") since 2004 with my Treo. I upgraded to the 700p last year.
In the Lansing market, we can also choose "the new AT&T" (Ameritech Wireless --> SBC Wireless + AT&T Wireless + Cingular --> AT&T) or Alltel (20th Century Wireless --> CenturyTel --> Alltel). T-Mobile has not really been much of a presence here, so mostly it's the big two: VZW or Sprint, with AT&T a contending third.
One of the obvious concerns was the EDGE data network of AT&T vs the EVDO on Sprint or VZW. Right from the iPhone announcement, this was the clear weakness. Reviews last week by the tech gurus (Walt Mossburg for WSJ and David Pogue for NYT) both cited this as a potential liability. But is it a deal breaker?
In my experience so far, there is a far more serious concern. Can I even make or receive calls? "iPhone"? -- "noPhone" is more like it. The AT&T regular cell voice network, let alone the EDGE data, is mostly "No Service" or sometimes 0 or 1 bars, at our house in the heart of residential East Lansing. Hardly the "more bars in more places" that was promised! After I activated the iPhone at about 2 in the morning Friday night, I was a bit concerned that the AT&T indicator only flickered on occasionally, but, then I was tired and maybe the network was overloaded or maybe the phone needed a full charge. I'd try again after some sleep.
In the cold, gray dawn of Saturday morning, a beautiful Michigan summer day was shaping up, but my iPhone couldn't even contact the voicemail service to set it up!! I looked up their coverage map, and, sure enough, a vast area of the residential neighborhoods of East Lansing have only "moderate" voice service! Overall, the coverage in Michigan is pretty much along the major highways only, outside of the Detroit mega-opolis. (The newer, true high-speed data network is only available in parts of Detroit and Ann Arbor.) But this is 2007 folks, and Lansing (I think) is not Podunk. VZW & Sprint seem to agree.
So, I took the iPhone outside, and got all the way up to 1 bar, but still no "E" to indicate data service. The coverage map showed that things were better to the south and west of me. It turns out that I'd left behind my lawn chair at the AT&T store, so I went back to retrieve it, and, indeed, I finally started to see more bars! And the "E" appeared! When I stopped in to the store, they all wanted to know what I thought so far. The answer was easy -- an amazing device on a crappy network. I don't even know how fast it is, because I can't even get enough service coverage to set up my voicemail, let alone browse the InterWeb! I earnestly requested that they put in a new tower within a mile of my house right away, or I'd probably have to (sadly) return the iPhone. They were stunned, but no one offered to strap on the tool belt and follow me home.
I went ahead and set up the voicemail sitting in the parking lot, and drove on to further experiments. In a later post, I'll report on some timings I've done of Web page retrievals, comparing my Sprint Treo 700p to the iPhone, both on the AT&T network (outside my house) and on WiFi (inside and out).
But, for now, the iPhone is just a JulyPhone, and not a DecemberPhone -- at least in Michigan -- if you have to take it outside to receive or make a phone call...
Message to Apple and AT&T: "It's the NETWORK, stupid!"
Subscribe to:
Posts (Atom)
