Y2K37 issue not addressed even on modern devices...

[anon(10181084)]

I recently saw a comment by @Rukbat from earlier this year explaining why Google Calendar didn't go past 2036. Thing is, even my Samsung phone with the Samsung calendar (I am too lazy to install Google calendar) has the EXACT SAME issue. I don't know why this is still a problem when a Samsung GT-Exxxx series dumphone I used years ago, that ran on a crappy 156MHz offbrand dumphone processor, could go to like 2100 or something around that period in its calendar. I know it might seem pointless, but it should be fixed by now. And weirdest thing is that the date & time settings permit one extra year, to December 2037. Setting the clock to today's date in 2037 makes the phone does some really funny things (starts randomly hiccuping for a few seconds, and unrelated to the bug my antivirus subscription also craps out and needs reactivation even when I set back the date, and a few several-second audio glitches hit me after I set the date back to automatic). I thought that the Y2K37 limitation was only on 32-bit devices, but I guess I am wrong...

 

[anon(10614692)]

Not sure what the issue is. I doubt any phone in use today or in 10 years from now will be working in 2037 so I see no reason for this to be high on anyone's list of priorities.

 

[Rukbat]

When we get to around the beginning of 2032, some phones may start getting updates with the problem fixed. And that's still going to be 5 years in the future at that point. (The update will just take the current 32 bit UNIX_TIMESTAMP, add 32 0s to the left and they're converted to 64 bit numbers [which will extend the "wraparound" date to approximately 292 billion years from now, at 15:30:08 UTC on Sunday, 4 December 292,277,026,596 - which should be sufficient for most people. ) (Assuming that "We" still exist then, and that we still use calendars. Maybe by then we'll have evolved to a form of life that has an inherent time sense, or our brains will be many times faster and more powerful than the best that any "computer" could do, so we won't be using them.)

Of course we won't be here - the sun will eventually start to expand and by only 4 billion years from now ("only", compared to 292 billion) Earth will be a cinder, at best.

 

[anon(10181084)]

Thanks for the info. And you ending is funny hahahaha

 

[bodinatorry]

I recently saw a comment by @Rukbat from earlier this year explaining why Google Calendar didn't go past 2036. Thing is, even my Samsung phone with the Samsung calendar (I am too lazy to install Google calendar) has the EXACT SAME issue. I don't know why this is still a problem when a Samsung GT-Exxxx series dumphone I used years ago, that ran on a crappy 156MHz offbrand dumphone processor, could go to like 2100 or something around that period in its calendar. I know it might seem pointless, but it should be fixed by now. And weirdest thing is that the date & time settings permit one extra year, to December 2037. Setting the clock to today's date in 2037 makes the phone does some really funny things (starts randomly hiccuping for a few seconds, and unrelated to the bug my antivirus subscription also craps out and needs reactivation even when I set back the date, and a few several-second audio glitches hit me after I set the date back to automatic). I thought that the Y2K37 limitation was only on 32-bit devices, but I guess I am wrong...

add 32 0s to the left and they're converted to 64 bit numbers [which will extend the "wraparound" date to approximately 292 billion years from now, at 15:30:08 UTC on Sunday, 4 December 292,277,026,596 - which should be sufficient for most people.

 

[Chuck Finley69]

Not sure what the issue is. I doubt any phone in use today or in 10 years from now will be working in 2037 so I see no reason for this to be high on anyone's list of priorities.

My BlackBerry PRIV running BBAndroid Marshmallow 5.1 begs to differ. The flux capacitor is why the hardware runs hot like a pocket handwarmer for a reason.

 

[Chuck Finley69]

When we get to around the beginning of 2032, some phones may start getting updates with the problem fixed. And that's still going to be 5 years in the future at that point. (The update will just take the current 32 bit UNIX_TIMESTAMP, add 32 0s to the left and they're converted to 64 bit numbers [which will extend the "wraparound" date to approximately 292 billion years from now, at 15:30:08 UTC on Sunday, 4 December 292,277,026,596 - which should be sufficient for most people. ) (Assuming that "We" still exist then, and that we still use calendars. Maybe by then we'll have evolved to a form of life that has an inherent time sense, or our brains will be many times faster and more powerful than the best that any "computer" could do, so we won't be using them.)

Of course we won't be here - the sun will eventually start to expand and by only 4 billion years from now ("only", compared to 292 billion) Earth will be a cinder, at best.

Citation link or it didn’t (won’t) happen. That or at the very least I’m double checking your math....

;-D check measure twice cut once