Ron wrote:
> On Thu, 21 Aug 2008 13:34:35 -0700, SMS <scharf.steven@geemail.com>
> wrote:
>
>> Ron wrote:
>>> http://www.tgdaily.com/content/view/38996/118/
>> Thank goodness for early adopters that rush out and buy new gadgets
>> before they're debugged!
>
>
> Based on the grief I had with 3g and ATT phones last year,
> I blame it on ATT's network.
It's happening all over the world, not just with AT&T.
On Thu, 21 Aug 2008 14:11:57 -0700, SMS <scharf.steven@geemail.com>
wrote:
>Ron wrote:
>> On Thu, 21 Aug 2008 13:34:35 -0700, SMS <scharf.steven@geemail.com>
>> wrote:
>>
>>> Ron wrote:
>>>> http://www.tgdaily.com/content/view/38996/118/
>>> Thank goodness for early adopters that rush out and buy new gadgets
>>> before they're debugged!
>>
>>
>> Based on the grief I had with 3g and ATT phones last year,
>> I blame it on ATT's network.
>
>It's happening all over the world, not just with AT&T.
It's happening with all ATT phones not just the iPhone 3G.
Ron <ronclifford@peoplepc.com> amazed us all with the following in
news:hqrra459cglc8mcqh58melcfojjjjh866a@4ax.com:
> On Thu, 21 Aug 2008 14:11:57 -0700, SMS <scharf.steven@geemail.com>
> wrote:
>
>>Ron wrote:
>>> On Thu, 21 Aug 2008 13:34:35 -0700, SMS <scharf.steven@geemail.com>
>>> wrote:
>>>
>>>> Ron wrote:
>>>>> http://www.tgdaily.com/content/view/38996/118/
>>>> Thank goodness for early adopters that rush out and buy new gadgets
>>>> before they're debugged!
>>>
>>>
>>> Based on the grief I had with 3g and ATT phones last year,
>>> I blame it on ATT's network.
>>
>>It's happening all over the world, not just with AT&T.
>
>
> It's happening with all ATT phones not just the iPhone 3G.
>
Actually, not it's not. Please provide a link to any independent article
making the same claim that all AT&T phones are having the same issue.
In article <Xns9B01B565D47Fbob@216.196.97.136>,
The Bob <nospam@bob.com> wrote:
>Ron <ronclifford@peoplepc.com> amazed us all with the following in
>news:hqrra459cglc8mcqh58melcfojjjjh866a@4ax.com :
>
>> On Thu, 21 Aug 2008 14:11:57 -0700, SMS <scharf.steven@geemail.com>
>> wrote:
>>
>>>Ron wrote:
>>>> On Thu, 21 Aug 2008 13:34:35 -0700, SMS <scharf.steven@geemail.com>
>>>> wrote:
>>>>
>>>>> Ron wrote:
>>>>>> http://www.tgdaily.com/content/view/38996/118/
>>>>> Thank goodness for early adopters that rush out and buy new gadgets
>>>>> before they're debugged!
>>>>
>>>>
>>>> Based on the grief I had with 3g and ATT phones last year,
>>>> I blame it on ATT's network.
>>>
>>>It's happening all over the world, not just with AT&T.
>>
>>
>> It's happening with all ATT phones not just the iPhone 3G.
>>
>
>Actually, not it's not. Please provide a link to any independent article
>making the same claim that all AT&T phones are having the same issue.
>
>I won't hold my breath.
I've been anticipating the Nokia E71 since it was announced, and have been
following the threads on HoFo, especially since the NAM version started
shipping earlier this month. There has been a rash of problem reports of
dropped calls, some due to apparent failed 3G-to-GSM handoffs on the AT&T
network. This may or may not be related to iPhone 3G issues. However, there
also seem to be RF issues with the E71-2 - part of which may be related
to the position of the antenna on the bottom - but there seems to be more.
> Actually, not it's not. Please provide a link to any independent article
> making the same claim that all AT&T phones are having the same issue.
>
> I won't hold my breath.
The most likely scenario is that in the U.S. it's a combination of
network issues and phone issues, but in the European countries with
robust 3G networks that it's strictly a phone issue.
In any case, it's best to hold up on purchasing 3G GSM phones in the
U.S. until the network and phone problems are corrected. No need to be a
guinea pig while the big boys sort this all out.
SMS <scharf.steven@geemail.com> amazed us all with the following in
news:c2ork.11226$vn7.9190@flpi147.ffdc.sbc.com:
> The Bob wrote:
>
>> Actually, not it's not. Please provide a link to any independent
>> article making the same claim that all AT&T phones are having the
>> same issue.
>>
>> I won't hold my breath.
>
> "http://gizmodo.com/5039611/blackberry-bold-plagued-by-same-3g-problems
> -as-iphone"
>
> The most likely scenario is that in the U.S. it's a combination of
> network issues and phone issues, but in the European countries with
> robust 3G networks that it's strictly a phone issue.
Awful convenient to be willing to blame the problem on network in one
country and yet blame the phone in others.
And why would the "most likely scenario" include additional UNPROVEN
variables only in the US? Answer- Steve hate AT&T.
> In any case, it's best to hold up on purchasing 3G GSM phones in the U.S.
> until the network and phone problems are corrected. No need to be a guinea
> pig while the big boys sort this all out.
If a sample size of one is relevant (which it isn't), I've had very good
experiences with the 3G iPhone up & down the San Francisco Peninsula, as
well as both Madison and Waterloo, Wisconsin. 3G doesn't work in the
farmland between Madison & Waterloo, but it does fall back to the Edge
network quite gracefully. I had no disconnected phone calls, and only a
couple of "server timeouts" that occur when surfing the 'net without a
useful connection.
So far, it's been a very useful gadget. First Apple product I've bought
since a Mac 512 many, many years ago. But perhaps my expectations are too
low to recognize its limitations.
--Mike Jacoubowsky
Chain Reaction Bicycles www.ChainReaction.com
Redwood City & Los Altos, CA USA
"SMS" <scharf.steven@geemail.com> wrote in message
news:c2ork.11226$vn7.9190@flpi147.ffdc.sbc.com...
> The Bob wrote:
>
>> Actually, not it's not. Please provide a link to any independent article
>> making the same claim that all AT&T phones are having the same issue.
>>
>> I won't hold my breath.
>
> "http://gizmodo.com/5039611/blackberry-bold-plagued-by-same-3g-problems-as-iphone"
>
> The most likely scenario is that in the U.S. it's a combination of network
> issues and phone issues, but in the European countries with robust 3G
> networks that it's strictly a phone issue.
>
> In any case, it's best to hold up on purchasing 3G GSM phones in the U.S.
> until the network and phone problems are corrected. No need to be a guinea
> pig while the big boys sort this all out.
On Thu, 21 Aug 2008 18:49:55 -0500, The Bob <nospam@bob.com> wrote:
>Ron <ronclifford@peoplepc.com> amazed us all with the following in
>news:hqrra459cglc8mcqh58melcfojjjjh866a@4ax.com :
>
>> On Thu, 21 Aug 2008 14:11:57 -0700, SMS <scharf.steven@geemail.com>
>> wrote:
>>
>>>Ron wrote:
>>>> On Thu, 21 Aug 2008 13:34:35 -0700, SMS <scharf.steven@geemail.com>
>>>> wrote:
>>>>
>>>>> Ron wrote:
>>>>>> http://www.tgdaily.com/content/view/38996/118/
>>>>> Thank goodness for early adopters that rush out and buy new gadgets
>>>>> before they're debugged!
>>>>
>>>>
>>>> Based on the grief I had with 3g and ATT phones last year,
>>>> I blame it on ATT's network.
>>>
>>>It's happening all over the world, not just with AT&T.
>>
>>
>> It's happening with all ATT phones not just the iPhone 3G.
>>
>
>Actually, not it's not. Please provide a link to any independent article
>making the same claim that all AT&T phones are having the same issue.
>
>I won't hold my breath.
Ron <ronclifford@peoplepc.com> amazed us all with the following in
newsn7sa499bpq57cslk9af0ii882jnbgu9g1@4ax.com:
> On Thu, 21 Aug 2008 18:49:55 -0500, The Bob <nospam@bob.com> wrote:
>
>>Ron <ronclifford@peoplepc.com> amazed us all with the following in
>>news:hqrra459cglc8mcqh58melcfojjjjh866a@4ax.co m:
>>
>>> On Thu, 21 Aug 2008 14:11:57 -0700, SMS <scharf.steven@geemail.com>
>>> wrote:
>>>
>>>>Ron wrote:
>>>>> On Thu, 21 Aug 2008 13:34:35 -0700, SMS
>>>>> <scharf.steven@geemail.com> wrote:
>>>>>
>>>>>> Ron wrote:
>>>>>>> http://www.tgdaily.com/content/view/38996/118/
>>>>>> Thank goodness for early adopters that rush out and buy new
>>>>>> gadgets before they're debugged!
>>>>>
>>>>>
>>>>> Based on the grief I had with 3g and ATT phones last year,
>>>>> I blame it on ATT's network.
>>>>
>>>>It's happening all over the world, not just with AT&T.
>>>
>>>
>>> It's happening with all ATT phones not just the iPhone 3G.
>>>
>>
>>Actually, not it's not. Please provide a link to any independent
>>article making the same claim that all AT&T phones are having the same
>>issue.
>>
>>I won't hold my breath.
>
>
> Here you go.
>
> http://discussions.apple.com/thread....392&tstart=210
>
I'll assume that you missed the word INDEPENDENT in my last post.
Ron <ronclifford@peoplepc.com> wrote in
news:hqrra459cglc8mcqh58melcfojjjjh866a@4ax.com:
>>It's happening all over the world, not just with AT&T.
>
>
> It's happening with all ATT phones not just the iPhone 3G.
>
>
This all sounds like them saying HIV causes AIDS. If HIV causes AIDS, all
AIDS patients would test positive for HIV. They don't. And, conversely,
all HIV positive people would get AIDS, which has just never been the
case....
Apple and ATT are BOTH to blame! Apple for rushing the product to market
with poor QC and debugging.....ATT for slapping up just a few towers near
the Apple stores and their own stores with 3G service on them, hoping noone
will notice the difference.
On Thu, 21 Aug 2008 14:11:57 -0700, SMS <scharf.steven@geemail.com>
wrote:
>It's happening all over the world, not just with AT&T.
So I've heard, but check this out: This may be a little hazy
for those unfamiliar with NYC, but I live in Manhattan and have been
having most of the usual problems with my iPhone 3G. No problems
calling or receiving calls, as far as I can tell, and no dropped
calls, but data has been the pits. Web sites won't load or crap out
halfway, mail "connects" endlessly before giving up, can receive (just
barely) but can't send, etc. etc. ad nauseum.
Today I had to travel throughout Queens, the large, spread-out
borough immediately east of Manhattan. Wherever I went, and I covered
a very wide area, my iPhone gave me a full five bars of 3G, fast (~600
kbps) web access, immediate mail sending and receiving, and so on. Of
course I had other business to conduct, so wasn't checking the signal
constantly, but the phone seemed to work perfectly wherever I did
check it.
I return to Manhattan, and everything is back as it was - zero
to two bars, dropping to Edge, can't send mail, etc.
So what does that say? You tell me. But I can tell you it was
the same device in both places. In Queens, where population and tall
buildings are far less dense, the thing works like a champ. In
Manhattan it intermittently works, but largely sucks.
This doesn't really sound like a defective device, does it?
Sounds more like either a network problem or a problem with the way
the device coordinates with the network, or the way it works in an
environment where the network is more heavily taxed, or... As I say,
you tell me.
> Awful convenient to be willing to blame the problem on network in one
> country and yet blame the phone in others.
It's simple logic. In the U.S., the 3G GSM phones all have problems, so
there must be a network problem, but in the ROW only the iPhone 3G is
having problems, so there must be a phone problem.
There's no rush. Wait until AT&T gets their 3G network up to speed, and
wait until Apple solves the iPhone 3G issues. Neither should take all
that long. Six months from now it'll all probably be working fine.
On 2008-08-22, SMS <scharf.steven@geemail.com> wrote:
> The Bob wrote:
>
>> Awful convenient to be willing to blame the problem on network in one
>> country and yet blame the phone in others.
>
> It's simple logic. In the U.S., the 3G GSM phones all have problems, so
That doesn't seem to be true. I've been using a Motorola V9 on AT&T's
3G network, both by itself and tethered to a laptop, and it seems to
work pretty pretty well. AT&T 3G service with the laptop tethered
to the phone is faster than the Verizon EVDO Rev. A modem I used to use.
> > Based on the grief I had with 3g and ATT phones last year,
> > I blame it on ATT's network.
>
> It's happening all over the world, not just with AT&T.
seems to be mostly fixed with 2.0.2, so that chapter is coming to a
close.
"David Moyer" <davmoy@world.com> wrote in message
news:48ae7431$0$48227$815e3792@news.qwest.net...
> SMS <scharf.steven@geemail.com> wrote:
>
>> > Based on the grief I had with 3g and ATT phones last year,
>> > I blame it on ATT's network.
>>
>> It's happening all over the world, not just with AT&T.
>
> seems to be mostly fixed with 2.0.2, so that chapter is coming to a
> close.
that article didn't contain any facts, did you even read it?
there are widespread reports that 2.0.2 did not initially fix the
problem, but a few days later the problems disappear. so it looks like a
iphone fix is tied to an att fix, so most of the issues for the 2% of
ipohone owners who were having problems are now gone.
The problem has been traced (apparently) to a problem with the 3G
chipset (believed to be from Infineon), combined with usage in areas
where the 3G signal isn't at maximum strength.
No one, not AT&T or Apple, guaranteed maximum data rate coverage in all
areas, so I doubt if the class action law suit will have the effect of
forcing a hardware fix which would be enormously expensive. The class
will likely end up with some coupons, just like with the original iPhone.
Thank goodness for the early adopters that are willing to shell out big
bucks on new products the instant they appear on the shelf. They are a
big help to those of us that have the patience to wait for the
inevitable early design and manufacturing issues to be worked out.
> Today I had to travel throughout Queens, the large, spread-out
> borough immediately east of Manhattan. Wherever I went, and I covered
> a very wide area, my iPhone gave me a full five bars of 3G, fast (~600
> kbps) web access, immediate mail sending and receiving, and so on. Of
> course I had other business to conduct, so wasn't checking the signal
> constantly, but the phone seemed to work perfectly wherever I did
> check it.
The problem has been traced (apparently) to a problem with the 3G
chipset (believed to be from Infineon), combined with usage in areas
where the 3G signal isn't at maximum strength.
You'd expect good 3G coverage in Manhattan, but I know that the old AT&T
Wireless 800 MHz network (which became Cingular's 800 MHz network after
Cingular bought AT&T Wireless and stopped using T-Mobile's 1900 MHz
network) always had problems in NYC due to both buildings blocking the
signal, and due to extremely high usage. Perhaps the problems they had
with voice coverage have continued.
"David Moyer" <davmoy@world.com> wrote in message
news:48aec928$0$48215$815e3792@news.qwest.net...
> In article <0Mvrk.35230$co7.12746@nlpi066.nbdc.sbc.com>,
> "Kevin Weaver" <kevinkeithweaver@sbcglobal.net> wrote:
>
>> Yeah, It's fixed all right.
>>
>> Try reading this.
>> http://www.tgdaily.com/content/view/38996/118/
>
> that article didn't contain any facts, did you even read it?
>
> there are widespread reports that 2.0.2 did not initially fix the
> problem, but a few days later the problems disappear. so it looks like a
> iphone fix is tied to an att fix, so most of the issues for the 2% of
> ipohone owners who were having problems are now gone.
>
> please keep up on the news.
So your saying there is no truth to this ? Then if it was a fix then how
come it's not working huh ?
You should try to keep up yourself.
The problem is still out there.
Apple is lost on how to fix it. Or it would have been fixed already.
> Apple is lost on how to fix it. Or it would have been fixed already.
They almost certainly know exactly what is required to fix it. Fixes
don't appear overnight, especially if, as has been reported, it's a
hardware issue. You can fix a lot of things in software, but usually not
RF issues. I could tell you stories of amazingly complex firmware
workarounds to hardware problems, but there's a limit to what can be done.
"Industry watchers remain convinced that Apple will address the 3G issues
with a more substantial 2.1 firmware update scheduled for an October
release. "
You know, if Apple can drag its sorry *** LONG enough, all these units will
be way out of RETURN POLICY time.....and if they drag it even further,
they'll all be OUT OF WARRANTY.....which will solve Apple's problem,
completely!
Wanna bet they get coupons for $50 on a 4G FruitFone?.....like they did
before?
My advice to all 3G owners is to RETURN THE PHONES TO APPLE OR ATT FOR A
FULL REFUND BEFORE YOUR TIME RUNS OUT.....then wait to see if it ever gets
fixed so you can BUY ANOTHER ONE WHEN THEY GET THE DAMNED THING
FIXED!....instead of waiting through all this bureaucratic foot dragging to
avoid RECALLS and get screwed because the time was too long!
RETURN THEM IMMEDIATELY!....TOMORROW!
ATT can put your old phone back in operation until they get this crap
straightened out....or they can issue you a 99c cheap phone to use to keep
you as a customer.
(Get one with Bluetooth DUN tethering in case Apple refuses so you can get
the neat N820 or N830 Linux tablets with WiMax and use the same phone for
your modem....(c
"SMS" <scharf.steven@geemail.com> wrote in message
news:wGIrk.10803$L_.4755@flpi150.ffdc.sbc.com...
> Kevin Weaver wrote:
>
>> Apple is lost on how to fix it. Or it would have been fixed already.
>
> They almost certainly know exactly what is required to fix it. Fixes don't
> appear overnight, especially if, as has been reported, it's a hardware
> issue. You can fix a lot of things in software, but usually not RF issues.
> I could tell you stories of amazingly complex firmware workarounds to
> hardware problems, but there's a limit to what can be done.
This is not a overnight problem. From almost day one that the 3G was
shipped.
Over 2 months. Hardly overnight. So while apple tries to fix it they send
out BS firmware to make people think it's been fixed.
> This is not a overnight problem. From almost day one that the 3G was
> shipped.
>
> Over 2 months. Hardly overnight. So while apple tries to fix it they send
> out BS firmware to make people think it's been fixed.
they have? it seems the connection issues have been resolved pretty
quickly. 2.0.2 fixes most of the remaining issues. Please try and keep
up with what is happening.
In message <48afce35$0$89876$815e3792@news.qwest.net> David Moyer
<davmoy@world.com> wrote:
>they have? it seems the connection issues have been resolved pretty
>quickly. 2.0.2 fixes most of the remaining issues. Please try and keep
>up with what is happening.
2.0.2 appears to have solved some of my random crashes, but I've just
recently had a couple dropped calls, never had any at all before 2.0.2,
so from personal experience, I'm not sure what to make of it.
Safari and iPod still crash consistently though, but a couple different
third party app crashes seem to have backed off.
Apple sued over 3G issues 
n7sa499bpq57cslk9af0ii882jnbgu9g1@4ax.com:
Linear Mode
