Aren't the alarms actually still on Mountain Time? My phone switched to Central Time, but my alarm still went off at the right time. I was worried as f*** thinking I was an hour late though... >=(
your alarm should be based on the time you set, it's not contextual to your location. so when your phone thinks you're in winnipeg (like mine and others in this thread) it'll wake you up nice and early at 5AM rather than 6AM.
I'm an iPhone 4 on Fido btw. I think it's probably an issue with our network. I've just turned off auto-select now. Apple has failed me one too many times when it comes to this clock thing.
This morning, my Windows Phone was fine, but my iPhone 4 was detecting it was in Central Time.
Quote:
Originally Posted by worth
Thanks for that, but you're clearly not understanding the issue. We're not a bunch of dullards here, we know what DST is. This is an issue with mobile devices that pull time zone information from the carrier based on geographic location being given the wrong time zone for a given region.
Location: Close enough to make a beer run during a TV timeout
Exp:
Quote:
Originally Posted by TorqueDog
Thanks for that, but you're clearly not understanding the issue. We're not a bunch of dullards here, we know what DST is. This is an issue with mobile devices that pull time zone information from the carrier based on geographic location being given the wrong time zone for a given region.
I'm going to guess that you didn't watch the entire video. The last minute or so deals with it, and they build to why there is an iPhone issue from about 5:35 to 5:52.
I'm going to guess that you didn't watch the entire video. The last minute or so deals with it, and they build to why there is an iPhone issue from about 5:35 to 5:52.
I did, but you're not understanding the issue either.
The problem is this:
Normal operation: Phone: "Hi, I'm an iPhone/WinPho7/Android/BlackBerry connecting to Rogers Wireless in Calgary, Alberta." Network: "Hi, I'm the Rogers Cellular Network." Phone: "Hey Rogers network." Network: "S'up." Phone: "What's the time, bro?" Network: "The UTC is 9:09 PM." Phone: "Cool. What time-zone am I in?" Network: "Based on the cellular tower you're connecting to, you are in Mountain Time, which is -7 from the UTC." Phone: "Wicked, so I'll display 2:09 PM. Thanks bro." Network: "Payyyyce dawg!"
What has been happening lately: Phone: "Hi, I'm an iPhone/WinPho7/Android/BlackBerry connecting to Rogers Wireless in Calgary, Alberta." Network: "lol hai im rogers." Phone: "Hey Rogers network." Network: "lol wut." Phone: "What's the time, bro?" Network: "ummm its liek 9:09 in lisbon. so yah tahts the utc." Phone: "Cool. What time-zone am I in?" Network: "Ummmmm... ur in alberta. so im gonna say ur in... central time, -6." Phone: "Wicked, so I'll display 3:09 PM. Thanks bro." Network: "lol trolled." User: "Wtf."
It's not an issue with the network changing for DST, it's an issue with the network telling the phone what time zone it is located in geographically. It's like if your GPS started pin-pointing your location as being in Winnipeg. Both my WinPho7 and my iPhone (on different days) were automatically detecting me as being in Central -6, not Mountain -7.
Location: Close enough to make a beer run during a TV timeout
Exp:
Quote:
Originally Posted by TorqueDog
I did, but you're not understanding the issue either.
<snip> it's an issue with the network telling the phone what time zone it is located in geographically.
Yes, I get that. The network thinks you are in a different location that you actually are. What I am saying is the video talks about different time zones, and how within a few 100 kms there can be different rules.
If the network had thought you were in Maple Creek, Sk instead of Calgary last week; you wouldn't have noticed because the time would have been correct. This week when it does the same thing; it shows the wrong time.
So yes, we all agree that it is a network issue that Rogers needs to fix as it is causing some headaches for it's users. What we don't agree on is how slightly relevant the mildly amusing video was.
Yes, I get that. The network thinks you are in a different location that you actually are. What I am saying is the video talks about different time zones, and how within a few 100 kms there can be different rules.
If the network had thought you were in Maple Creek, Sk instead of Calgary last week; you wouldn't have noticed because the time would have been correct. This week when it does the same thing; it shows the wrong time.
So yes, we all agree that it is a network issue that Rogers needs to fix as it is causing some headaches for it's users. What we don't agree on is how slightly relevant the mildly amusing video was.
Central time zone is nearly 1,000 KM away. The network wouldn't think you were in Maple Creek, SK either, because you would be connecting to a cellular tower in Calgary.
Video was quite amusing, but had very little relevance to what we are discussing.
Location: Close enough to make a beer run during a TV timeout
Exp:
Sorry, but the Saskatchewan border is not 1000 km away. More like 300 km.
And I'm not sure how you came to the conclusion that the network couldn't think your are in Maple Creek; but it could think you are in Winnipeg. The fact is; something somewhere along the line is telling your phone that it is in a different location than it actually is.
From what I have read in this thread; it sounds like everybody with this issue is on Rogers/Fido (which is the same network.) Is there anybody experiencing this issue with Bell or Telus? If not, if I was one of the affected people I would be talking to Rogers as that seems to be the common denominator.
Sorry, but the Saskatchewan border is not 1000 km away. More like 300 km.
And I'm not sure how you came to the conclusion that the network couldn't think your are in Maple Creek; but it could think you are in Winnipeg. The fact is; something somewhere along the line is telling your phone that it is in a different location than it actually is.
From what I have read in this thread; it sounds like everybody with this issue is on Rogers/Fido (which is the same network.) Is there anybody experiencing this issue with Bell or Telus? If not, if I was one of the affected people I would be talking to Rogers as that seems to be the common denominator.
Did I say the Saskatchewan border was 1,000 KM away? Please read again.
I didn't say it "couldn't", I'm saying it is not supposed to because you are not going to be connecting to towers that report the Saskatchewan time zone. You are connecting to towers in and around Calgary. So despite connecting to a tower close-by, the network is reporting the wrong time zone (ie: Central time, as it says right on the device). This has nothing to do with how close the towers in the Saskatchewan time zone are to us.
From everyone that has told me about the issue, the common denominator was cellular provider: Rogers.
No- you said the Central time zone was 1000 km away. Both Manitoba and Saskatchewan are in the central time zone.
Saskatchewan does not change their clocks for DST, and for the purposes of electronic devices that maintain time and date information, they are given a separate time zone entry, "(UTC-06:00) Saskatchewan" and that is the context in which you need to look at this.
A Saskatchewan cellular user will be told they are in the "(UTC-06:00) Saskatchewan" time zone and the device will not change for DST when set to that time zone. A Manitoba user will be told they are in "(UTC-06:00) Central", which tells the device to change the clock for DST. Try it yourself, you can go into "Date and Time" in Windows and change between the two time zones. Central displays a box allowing the PC to adjust for DST. Saskatchewan removes this check box.
So if you go east from Calgary, your device will change to the following time zones:
Alberta: Mountain Time -7
Saskatchewan: Saskatchewan Time -6
Manitoba: Central Time -6
So yes, the 'Central' time zone in this context is almost 1,000 KM away from Calgary. The 'Saskatchewan' time zone is 300 KM away, but no one's devices were indicating the Saskatchewan time zone. It's not a tower proximity issue, it's a network issue. It seems to have resolved itself now.
I've got a BB and am on Rogers, there seems to be one tower in Kensington which is outta wack, we're were working in that area today and all day my phone was busy switching back and forth between Alberta time and Saskatchewan time, I had no idea what the time was anymore, furthermore I think my phone gave up because it just shut itself off and I couldn't get it going again til i pulled the battery out. I haven't had issue anywhere else in the city.