Gee, my Droid X didn't have any problems. I guess that's my punishment for
not having the latest iPhone.
"Hachiroku ハチ*ク" wrote in message news:5lvfp.3240$bd5.358@newsfe02.iad...
Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
going!
Apple iPhone and iPod touch users are reporting all kinds of erratic
behavior with the clock application — on AT&T and Verizon alike — with
some alarms going off early, others late, and plenty of others working
perfectly.
Users of Apple's iPhone fired complaints all over the Internet Sunday when
their phones did not properly "spring forward" one hour to daylight
savings time that went into effect overnight Saturday.
One user complained of missing church, another of almost missing yoga. One
called her iPhone stupid and several just asked for help.
This has not been the first clock problem for the Apple iPhone. Yahoo News
reports a clock glitch prevented alarms from sounding on New Year's Day,
causing slumbering revelers to oversleep.
And back in November, venturebeat.com reported the alarm clock application
of iPhone users in Europe and the U.S experienced a bug related to
Daylight Savings Time.
At the time, European iPhone owners were reporting that their alarms were
going off one hour late. And some users in the US reported alarms going
off an hour early.
Users in Australia and New Zealand first reported the issue when they
switched over to Daylight Savings Time. Apple had mentioned that a fix was
on the way, but one didn’t arrive in time to avoid problems.
Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
going!
Apple iPhone and iPod touch users are reporting all kinds of erratic
behavior with the clock application — on AT&T and Verizon alike — with
some alarms going off early, others late, and plenty of others working
perfectly.
Users of Apple's iPhone fired complaints all over the Internet Sunday when
their phones did not properly "spring forward" one hour to daylight
savings time that went into effect overnight Saturday.
One user complained of missing church, another of almost missing yoga. One
called her iPhone stupid and several just asked for help.
This has not been the first clock problem for the Apple iPhone. Yahoo News
reports a clock glitch prevented alarms from sounding on New Year's Day,
causing slumbering revelers to oversleep.
And back in November, venturebeat.com reported the alarm clock application
of iPhone users in Europe and the U.S experienced a bug related to
Daylight Savings Time.
At the time, European iPhone owners were reporting that their alarms were
going off one hour late. And some users in the US reported alarms going
off an hour early.
Users in Australia and New Zealand first reported the issue when they
switched over to Daylight Savings Time. Apple had mentioned that a fix was
on the way, but one didn’t arrive in time to avoid problems.
On Mon, 14 Mar 2011 17:35:19 -0400, its only me wrote:
> Gee, my Droid X didn't have any problems. I guess that's my punishment
> for not having the latest iPhone.
My 6 year old Palm was no problem either. Neither was my 4 year old
BlackBerry.
Guess I just have to move up to the present and get something that doesn't
work...
(I wouldn't be doing this if Oxford didn't dribble his fanboishness all
over the place. The iPhone is one cool piece of equipment, but Oxford
seems to imply Apples have NO problems whatsoever...)
>
> "Hachiroku ハチ*ク" wrote in message
> news:5lvfp.3240$bd5.358@newsfe02.iad...
>
> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> going!
>
> Apple iPhone and iPod touch users are reporting all kinds of erratic
> behavior with the clock application — on AT&T and Verizon alike — with
> some alarms going off early, others late, and plenty of others working
> perfectly.
>
> Users of Apple's iPhone fired complaints all over the Internet Sunday when
> their phones did not properly "spring forward" one hour to daylight
> savings time that went into effect overnight Saturday.
>
> One user complained of missing church, another of almost missing yoga. One
> called her iPhone stupid and several just asked for help.
>
> This has not been the first clock problem for the Apple iPhone. Yahoo News
> reports a clock glitch prevented alarms from sounding on New Year's Day,
> causing slumbering revelers to oversleep.
>
> And back in November, venturebeat.com reported the alarm clock application
> of iPhone users in Europe and the U.S experienced a bug related to
> Daylight Savings Time.
>
> At the time, European iPhone owners were reporting that their alarms were
> going off one hour late. And some users in the US reported alarms going
> off an hour early.
>
> Users in Australia and New Zealand first reported the issue when they
> switched over to Daylight Savings Time. Apple had mentioned that a fix was
> on the way, but one didn’t arrive in time to avoid problems.
Hachiroku ハチ*ク wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> going!
>
> Apple iPhone and iPod touch users are reporting all kinds of erratic
> behavior with the clock application — on AT&T and Verizon alike — with
> some alarms going off early, others late, and plenty of others working
> perfectly.
Has the iPhone clock EVER worked correctly at a time change? It even
messed up at Jan 1st
On 3/14/2011 3:57 PM, Justin wrote:
> Hachiroku ハチ*ク wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
>> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>> going!
>>
>> Apple iPhone and iPod touch users are reporting all kinds of erratic
>> behavior with the clock application — on AT&T and Verizon alike — with
>> some alarms going off early, others late, and plenty of others working
>> perfectly.
>
> Has the iPhone clock EVER worked correctly at a time change? It even
> messed up at Jan 1st
RTC chips and computer clocks have often had programming errors related
to DST. It seems like it should not be so hard to get the programming
right, and to test it.
SMS wrote on [Mon, 14 Mar 2011 16:31:19 -0700]:
> On 3/14/2011 3:57 PM, Justin wrote:
>> Hachiroku ハチ*ク wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
>>> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>>> going!
>>>
>>> Apple iPhone and iPod touch users are reporting all kinds of erratic
>>> behavior with the clock application — on AT&T and Verizon alike — with
>>> some alarms going off early, others late, and plenty of others working
>>> perfectly.
>>
>> Has the iPhone clock EVER worked correctly at a time change? It even
>> messed up at Jan 1st
>
> RTC chips and computer clocks have often had programming errors related
> to DST. It seems like it should not be so hard to get the programming
> right, and to test it.
The occasional screw up is OK, but it seems like EVERY time change the
iphone messes up.
> On 3/14/2011 3:57 PM, Justin wrote:
>> Hachiroku ハチ*ク wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
>>> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>>> going!
>>>
>>> Apple iPhone and iPod touch users are reporting all kinds of erratic
>>> behavior with the clock application — on AT&T and Verizon alike —
>>> with some alarms going off early, others late, and plenty of others
>>> working perfectly.
>>
>> Has the iPhone clock EVER worked correctly at a time change? It even
>> messed up at Jan 1st
>
> RTC chips and computer clocks have often had programming errors related to
> DST. It seems like it should not be so hard to get the programming right,
> and to test it.
But, Apples products are *perfect*! HOW can this be?!?!?!
In article <slrnint79u.2hj.nospam@ubuntu.nitsuj.net>,
Justin <nospam@insightbb.com> wrote:
> Hachiroku n`N wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
> > Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> > going!
> >
> > Apple iPhone and iPod touch users are reporting all kinds of erratic
> > behavior with the clock application \ on AT&T and Verizon alike \ with
> > some alarms going off early, others late, and plenty of others working
> > perfectly.
>
> Has the iPhone clock EVER worked correctly at a time change? It even
> messed up at Jan 1st
You guys are really cute. I know it may be hard for you to fathom, but
some problems don't actually affect all customers. For instance, my
iPhone 4 clock and alarms have worked perfectly ever since I bought it
back in June 2010. My iPhone 3G clock and alarms worked perfectly too.
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
Jolly Roger wrote on [Mon, 14 Mar 2011 20:17:15 -0500]:
> In article <slrnint79u.2hj.nospam@ubuntu.nitsuj.net>,
> Justin <nospam@insightbb.com> wrote:
>
>> Hachiroku ÉnÉ`ÉçÉN wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
>> > Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>> > going!
>> >
>> > Apple iPhone and iPod touch users are reporting all kinds of erratic
>> > behavior with the clock application Å\ on AT&T and Verizon alike Å\ with
>> > some alarms going off early, others late, and plenty of others working
>> > perfectly.
>>
>> Has the iPhone clock EVER worked correctly at a time change? It even
>> messed up at Jan 1st
>
> You guys are really cute. I know it may be hard for you to fathom, but
> some problems don't actually affect all customers. For instance, my
> iPhone 4 clock and alarms have worked perfectly ever since I bought it
> back in June 2010. My iPhone 3G clock and alarms worked perfectly too.
Then you mustn't have had any repeating alarms in November, as according
to every news story everyone was affected by it.
On Mon, 14 Mar 2011 20:17:15 -0500, Jolly Roger wrote:
> In article <slrnint79u.2hj.nospam@ubuntu.nitsuj.net>,
> Justin <nospam@insightbb.com> wrote:
>
>> Hachiroku ÉnÉ`ÉçÉN wrote on [Mon, 14 Mar 2011 16:59:39 -0500]:
>> > Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>> > going!
>> >
>> > Apple iPhone and iPod touch users are reporting all kinds of erratic
>> > behavior with the clock application Å\ on AT&T and Verizon alike Å\
>> > with some alarms going off early, others late, and plenty of others
>> > working perfectly.
>>
>> Has the iPhone clock EVER worked correctly at a time change? It even
>> messed up at Jan 1st
>
> You guys are really cute. I know it may be hard for you to fathom, but
> some problems don't actually affect all customers. For instance, my iPhone
> 4 clock and alarms have worked perfectly ever since I bought it back in
> June 2010. My iPhone 3G clock and alarms worked perfectly too.
The article said "...others are working perfectly".
The whole thing is the World According to Oxford states that Apple
products are the Plus Perfect devices du monde, in fact, the ENTIRE
UNIVERSE!!! They NEVER have problems!
nospam stated in post 140320112350471481%nospam@nospam.invalid on 3/15/11
12:50 AM:
> In article <slrnint9ra.2hj.nospam@ubuntu.nitsuj.net>, Justin
> <nospam@insightbb.com> wrote:
>
>>>> Has the iPhone clock EVER worked correctly at a time change? It even
>>>> messed up at Jan 1st
>>>
>>> RTC chips and computer clocks have often had programming errors related
>>> to DST. It seems like it should not be so hard to get the programming
>>> right, and to test it.
>>
>> The occasional screw up is OK, but it seems like EVERY time change the
>> iphone messes up.
>
> apple can't write code to properly handle time zones to save their
> lives.
nospam stated in post 150320110004210333%nospam@nospam.invalid on 3/15/11
1:04 AM:
> In article <C9A4318B.91EAF%usenet@gallopinginsanity.com>, Snit
> <usenet@gallopinginsanity.com> wrote:
>
>>>>>> Has the iPhone clock EVER worked correctly at a time change? It even
>>>>>> messed up at Jan 1st
>>>>>
>>>>> RTC chips and computer clocks have often had programming errors related
>>>>> to DST. It seems like it should not be so hard to get the programming
>>>>> right, and to test it.
>>>>
>>>> The occasional screw up is OK, but it seems like EVERY time change the
>>>> iphone messes up.
>>>
>>> apple can't write code to properly handle time zones to save their
>>> lives.
>>
>> Time zones? That works fine as far as I know.
>
> daylight saving time affects time zone calculations, particularly when
> some places switch and others don't. os x finder still to this day has
> problems switching time zones, such as when flying across country.
Maybe I never run into problems because there is no DLST in my neck of the
woods and I do not have a portable computer. It handles it fine in terms of
adding appointments from different time zones and handling the correction -
even with DLST included.
In article <slrnint9ra.2hj.nospam@ubuntu.nitsuj.net>, Justin
<nospam@insightbb.com> wrote:
> >> Has the iPhone clock EVER worked correctly at a time change? It even
> >> messed up at Jan 1st
> >
> > RTC chips and computer clocks have often had programming errors related
> > to DST. It seems like it should not be so hard to get the programming
> > right, and to test it.
>
> The occasional screw up is OK, but it seems like EVERY time change the
> iphone messes up.
apple can't write code to properly handle time zones to save their
lives.
In article <C9A4318B.91EAF%usenet@gallopinginsanity.com>, Snit
<usenet@gallopinginsanity.com> wrote:
> >>>> Has the iPhone clock EVER worked correctly at a time change? It even
> >>>> messed up at Jan 1st
> >>>
> >>> RTC chips and computer clocks have often had programming errors related
> >>> to DST. It seems like it should not be so hard to get the programming
> >>> right, and to test it.
> >>
> >> The occasional screw up is OK, but it seems like EVERY time change the
> >> iphone messes up.
> >
> > apple can't write code to properly handle time zones to save their
> > lives.
>
> Time zones? That works fine as far as I know.
daylight saving time affects time zone calculations, particularly when
some places switch and others don't. os x finder still to this day has
problems switching time zones, such as when flying across country.
On Mon, 14 Mar 2011 16:59:39 -0500, Hachiroku ハチ*ク <Trueno@e86.gts> wrote:
> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> going!
>
> Apple iPhone and iPod touch users are reporting all kinds of erratic
> behavior with the clock application — on AT&T and Verizon alike — with
> some alarms going off early, others late, and plenty of others working
> perfectly.
>
> Users of Apple's iPhone fired complaints all over the Internet Sunday when
> their phones did not properly "spring forward" one hour to daylight
> savings time that went into effect overnight Saturday.
>
> One user complained of missing church, another of almost missing yoga. One
> called her iPhone stupid and several just asked for help.
>
> This has not been the first clock problem for the Apple iPhone. Yahoo News
> reports a clock glitch prevented alarms from sounding on New Year's Day,
> causing slumbering revelers to oversleep.
>
> And back in November, venturebeat.com reported the alarm clock application
> of iPhone users in Europe and the U.S experienced a bug related to
> Daylight Savings Time.
>
> At the time, European iPhone owners were reporting that their alarms were
> going off one hour late. And some users in the US reported alarms going
> off an hour early.
>
> Users in Australia and New Zealand first reported the issue when they
> switched over to Daylight Savings Time. Apple had mentioned that a fix was
> on the way, but one didn’t arrive in time to avoid problems.
Heh-heh, 8-6, once again (of course) it's Apple in the lead: *they* know what the
*true* DST/non-DST changeover dates should be, and so their phones are programmed
to implement *those* dates -- it's up to the rest of the world now to catch up to
Apple's wisdom :-) .
"Hachiroku ????" <Trueno@e86.GTS> wrote in message
news:5lvfp.3240$bd5.358@newsfe02.iad...
> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> going!
>
> Apple iPhone and iPod touch users are reporting all kinds of erratic
> behavior with the clock application - on AT&T and Verizon alike - with
> some alarms going off early, others late, and plenty of others working
> perfectly.
>
> Users of Apple's iPhone fired complaints all over the Internet Sunday when
> their phones did not properly "spring forward" one hour to daylight
> savings time that went into effect overnight Saturday.
>
> One user complained of missing church, another of almost missing yoga. One
> called her iPhone stupid and several just asked for help.
>
> This has not been the first clock problem for the Apple iPhone. Yahoo News
> reports a clock glitch prevented alarms from sounding on New Year's Day,
> causing slumbering revelers to oversleep.
>
> And back in November, venturebeat.com reported the alarm clock application
> of iPhone users in Europe and the U.S experienced a bug related to
> Daylight Savings Time.
>
> At the time, European iPhone owners were reporting that their alarms were
> going off one hour late. And some users in the US reported alarms going
> off an hour early.
>
> Users in Australia and New Zealand first reported the issue when they
> switched over to Daylight Savings Time. Apple had mentioned that a fix was
> on the way, but one didn't arrive in time to avoid problems.
On 3/14/2011 2:59 PM, Hachiroku ハチ*ク wrote:
> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> going!
>
> Apple iPhone and iPod touch users are reporting all kinds of erratic
> behavior with the clock application — on AT&T and Verizon alike — with
> some alarms going off early, others late, and plenty of others working
> perfectly.
>
> Users of Apple's iPhone fired complaints all over the Internet Sunday when
> their phones did not properly "spring forward" one hour to daylight
> savings time that went into effect overnight Saturday.
>
> One user complained of missing church, another of almost missing yoga. One
> called her iPhone stupid and several just asked for help.
>
> This has not been the first clock problem for the Apple iPhone. Yahoo News
> reports a clock glitch prevented alarms from sounding on New Year's Day,
> causing slumbering revelers to oversleep.
>
> And back in November, venturebeat.com reported the alarm clock application
> of iPhone users in Europe and the U.S experienced a bug related to
> Daylight Savings Time.
>
> At the time, European iPhone owners were reporting that their alarms were
> going off one hour late. And some users in the US reported alarms going
> off an hour early.
>
> Users in Australia and New Zealand first reported the issue when they
> switched over to Daylight Savings Time. Apple had mentioned that a fix was
> on the way, but one didn’t arrive in time to avoid problems.
>
>
I wonder how many people lost their jobs due to this ****up
by Apple.
In article <4SSfp.20338$yR1.17669@newsfe03.iad>,
John Slade <hhitman86@pacbell.net> wrote:
> On 3/14/2011 2:59 PM, Hachiroku n`N wrote:
> > Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
> > going!
> >
> > Apple iPhone and iPod touch users are reporting all kinds of erratic
> > behavior with the clock application \ on AT&T and Verizon alike \ with
> > some alarms going off early, others late, and plenty of others working
> > perfectly.
> >
> > Users of Apple's iPhone fired complaints all over the Internet Sunday when
> > their phones did not properly "spring forward" one hour to daylight
> > savings time that went into effect overnight Saturday.
> >
> > One user complained of missing church, another of almost missing yoga. One
> > called her iPhone stupid and several just asked for help.
> >
> > This has not been the first clock problem for the Apple iPhone. Yahoo News
> > reports a clock glitch prevented alarms from sounding on New Year's Day,
> > causing slumbering revelers to oversleep.
> >
> > And back in November, venturebeat.com reported the alarm clock application
> > of iPhone users in Europe and the U.S experienced a bug related to
> > Daylight Savings Time.
> >
> > At the time, European iPhone owners were reporting that their alarms were
> > going off one hour late. And some users in the US reported alarms going
> > off an hour early.
> >
> > Users in Australia and New Zealand first reported the issue when they
> > switched over to Daylight Savings Time. Apple had mentioned that a fix was
> > on the way, but one didnft arrive in time to avoid problems.
> >
> >
>
> I wonder how many people lost their jobs due to this ****up
> by Apple.
>
> John
What ****up? For the overwhelming majority of iPhone owners, there is no problem.
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
> On Mon, 14 Mar 2011 16:59:39 -0500, Hachiroku ハチ*ク
> <Trueno@e86.gts> wrote:
>
>> Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>> going!
>>
>> Apple iPhone and iPod touch users are reporting all kinds of erratic
>> behavior with the clock application — on AT&T and Verizon alike —
>> with some alarms going off early, others late, and plenty of others
>> working perfectly.
>>
>> Users of Apple's iPhone fired complaints all over the Internet Sunday
>> when their phones did not properly "spring forward" one hour to daylight
>> savings time that went into effect overnight Saturday.
>>
>> One user complained of missing church, another of almost missing yoga.
>> One called her iPhone stupid and several just asked for help.
>>
>> This has not been the first clock problem for the Apple iPhone. Yahoo
>> News reports a clock glitch prevented alarms from sounding on New Year's
>> Day, causing slumbering revelers to oversleep.
>>
>> And back in November, venturebeat.com reported the alarm clock
>> application of iPhone users in Europe and the U.S experienced a bug
>> related to Daylight Savings Time.
>>
>> At the time, European iPhone owners were reporting that their alarms
>> were going off one hour late. And some users in the US reported alarms
>> going off an hour early.
>>
>> Users in Australia and New Zealand first reported the issue when they
>> switched over to Daylight Savings Time. Apple had mentioned that a fix
>> was on the way, but one didn’t arrive in time to avoid problems.
>
> Heh-heh, 8-6, once again (of course) it's Apple in the lead: *they* know
> what the *true* DST/non-DST changeover dates should be, and so their
> phones are programmed to implement *those* dates -- it's up to the rest of
> the world now to catch up to Apple's wisdom :-) .
>
> All clear, now? Cheers, -- tlvp :-)
Well, the *true* changover dates have been changed in the US. So does that
mean on the *true* changeover dates, iPhone users are going to have
*another* problem?
You mean to tell me the Great Minds at Apple can't configure the things to
change over according to local standards? That's really the bottom
line...Apple's fallibility comes into play, when so many say their
products are infallible...
Jolly Roger wrote on [Tue, 15 Mar 2011 18:56:04 -0500]:
> In article <4SSfp.20338$yR1.17669@newsfe03.iad>,
> John Slade <hhitman86@pacbell.net> wrote:
>
>> On 3/14/2011 2:59 PM, Hachiroku ÉnÉ`ÉçÉN wrote:
>> > Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>> > going!
>> >
>> > Apple iPhone and iPod touch users are reporting all kinds of erratic
>> > behavior with the clock application Å\ on AT&T and Verizon alike Å\ with
>> > some alarms going off early, others late, and plenty of others working
>> > perfectly.
>> >
>> > Users of Apple's iPhone fired complaints all over the Internet Sunday when
>> > their phones did not properly "spring forward" one hour to daylight
>> > savings time that went into effect overnight Saturday.
>> >
>> > One user complained of missing church, another of almost missing yoga. One
>> > called her iPhone stupid and several just asked for help.
>> >
>> > This has not been the first clock problem for the Apple iPhone. Yahoo News
>> > reports a clock glitch prevented alarms from sounding on New Year's Day,
>> > causing slumbering revelers to oversleep.
>> >
>> > And back in November, venturebeat.com reported the alarm clock application
>> > of iPhone users in Europe and the U.S experienced a bug related to
>> > Daylight Savings Time.
>> >
>> > At the time, European iPhone owners were reporting that their alarms were
>> > going off one hour late. And some users in the US reported alarms going
>> > off an hour early.
>> >
>> > Users in Australia and New Zealand first reported the issue when they
>> > switched over to Daylight Savings Time. Apple had mentioned that a fix was
>> > on the way, but one didnÅft arrive in time to avoid problems.
>> >
>> >
>>
>> I wonder how many people lost their jobs due to this ****up
>> by Apple.
>>
>> John
>
> What ****up? For the overwhelming majority of iPhone owners, there is no problem.
For the overwhelming number of time changes iPhones have failed to work
correctly
On Tue, 15 Mar 2011 19:56:36 -0400, Hachiroku ハチ*ク <Trueno@e86.gts> wrote:
> ...
> Well, the *true* changover dates have been changed in the US. So does that
> mean on the *true* changeover dates, iPhone users are going to have
> *another* problem?
>
> You mean to tell me the Great Minds at Apple can't configure the things to
> change over according to local standards? That's really the bottom
> line...Apple's fallibility comes into play, when so many say their
> products are infallible...
Not at all -- I meant that what "the Great Minds at Apple can't configure"
is the world's tendency to adopt a whole lot of conflicting local standards
for ST/DST changes, instead of bowing to Apple's superior wisdom in that
regard :-) .
'Zat make things clearer? Cheers, -- tlvp :-)
--
Avant de repondre, jeter la poubelle, SVP
> On Tue, 15 Mar 2011 19:56:36 -0400, Hachiroku ハチ*ク
> <Trueno@e86.gts> wrote:
>
>> ...
>> Well, the *true* changover dates have been changed in the US. So does
>> that mean on the *true* changeover dates, iPhone users are going to have
>> *another* problem?
>>
>> You mean to tell me the Great Minds at Apple can't configure the things
>> to change over according to local standards? That's really the bottom
>> line...Apple's fallibility comes into play, when so many say their
>> products are infallible...
>
> Not at all -- I meant that what "the Great Minds at Apple can't configure"
> is the world's tendency to adopt a whole lot of conflicting local
> standards for ST/DST changes, instead of bowing to Apple's superior wisdom
> in that regard :-) .
>
> 'Zat make things clearer? Cheers, -- tlvp :-)
(Just between you and me, I have absolutely nothing against Apple
products. We just get a fanboi who tells us Apples are the GREATEST thing
on the planet, nay, the UNIVERSE, and everything else pales in comparison.
They are INFALLIBLE!!! )
On Wed, 16 Mar 2011 00:52:41 -0400, Hachiroku ハチ*ク <Trueno@e86.gts> wrote:
> On Tue, 15 Mar 2011 23:30:15 -0400, tlvp wrote:
>
>> 'Zat make things clearer? Cheers, -- tlvp :-)
>
> (Just between you and me, I have absolutely nothing against Apple
> products. We just get a fanboi who tells us Apples are the GREATEST thing
> on the planet, nay, the UNIVERSE, and everything else pales in comparison.
> They are INFALLIBLE!!! )
:-) . Cheers, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP
"Justin" <nospam@insightbb.com> wrote in message
news:slrninvvk5.2hj.nospam@ubuntu.nitsuj.net...
> Jolly Roger wrote on [Tue, 15 Mar 2011 18:56:04 -0500]:
>> In article <4SSfp.20338$yR1.17669@newsfe03.iad>,
>> John Slade <hhitman86@pacbell.net> wrote:
>>
>>> On 3/14/2011 2:59 PM, Hachiroku n`N wrote:
>>> > Hey, Oxford. Please! Keep telling us how Apple is the greatest thing
>>> > going!
>>> >
>>> > Apple iPhone and iPod touch users are reporting all kinds of erratic
>>> > behavior with the clock application \ on AT&T and Verizon alike \
>>> > with
>>> > some alarms going off early, others late, and plenty of others working
>>> > perfectly.
>>> >
>>> > Users of Apple's iPhone fired complaints all over the Internet Sunday
>>> > when
>>> > their phones did not properly "spring forward" one hour to daylight
>>> > savings time that went into effect overnight Saturday.
>>> >
>>> > One user complained of missing church, another of almost missing yoga.
>>> > One
>>> > called her iPhone stupid and several just asked for help.
>>> >
>>> > This has not been the first clock problem for the Apple iPhone. Yahoo
>>> > News
>>> > reports a clock glitch prevented alarms from sounding on New Year's
>>> > Day,
>>> > causing slumbering revelers to oversleep.
>>> >
>>> > And back in November, venturebeat.com reported the alarm clock
>>> > application
>>> > of iPhone users in Europe and the U.S experienced a bug related to
>>> > Daylight Savings Time.
>>> >
>>> > At the time, European iPhone owners were reporting that their alarms
>>> > were
>>> > going off one hour late. And some users in the US reported alarms
>>> > going
>>> > off an hour early.
>>> >
>>> > Users in Australia and New Zealand first reported the issue when they
>>> > switched over to Daylight Savings Time. Apple had mentioned that a fix
>>> > was
>>> > on the way, but one didnft arrive in time to avoid problems.
>>> >
>>> >
>>>
>>> I wonder how many people lost their jobs due to this ****up
>>> by Apple.
>>>
>>> John
>>
>> What ****up? For the overwhelming majority of iPhone owners, there is no
>> problem.
>
> For the overwhelming number of time changes iPhones have failed to work
> correctly
Re: Apple gets behind the time with iPhone 
)
Linear Mode
