as much as these are usually fun to laugh at the retards (LOL MICROWAVE UR PHONE FOR SUPER FAST CHARING! SOUNDS GOOD) I sorta feel bad for these people. I honestly might have tried it myself, who would reasonably expect that just changing the date is a potential brick.
I thought it was strange you needed to reboot, but yeah, it's not very obvious. Who would assume that something so simple would brick their phone? It's not like I have an iphone anyway though
fairly clever on whatever prick came up with it though I guess, since this type of thing is super common in general (i.e. if the date is christmas on this device or that website you get snowflakes and that kind of shit)
UNIX counts time by counting seconds starting from 0. 0 is January 1st 1970. The main point here is that it counts based on GMT.
Which means, if you live in a minut GMT zone, like GMT-5, 6 or 7 like USA you will technically end up at December 31st 1969, which brings the time to "minus 0". This causes panic in the software.
Most of *NIX implementations like Android or Linux has fixed this issue a while ago. Apple hasn't.
computers generally tell time by keeping track of how many seconds have passed since Jan 1, 1970, commonly referred to as the "Unix Time" or "Epoch Time".
So when your date is Feb 12, 2016, the seconds since epoch time is 1455235200. The software does all sorts of fancy shit with this number. It expects it to be a large number, and so it'll do stuff like division and shit. Anyway, if you set your time to Jan 1, 1970, that number is now 0. Well, what happens if you try to divide by 0? Fucking crash.
And it gets worse. When you take Timezones into account, that number might actually be a negative, which could fuck things up further.
TL;DR: The boot code doesn't sanitize/check the time function input properly.
Because their programmers are fucking morons. Did you know that elements in the Mac OSX UI are basically just Adobe PDFs? Transparency effects lag like fucking shit on Retina Macs.
Watch the Keynote for Mac OSX 10.0 to see for yourself, they haven't changed the UI renderer in over 17 years.
I'll never understand what the people who design this shit are thinking.
>how should we measure time
>let's just pick a date
reminds me of japanese videogame developers
>how should we measure time?
>off the system clock?
>fuck that, base it on the rendering framerate!
The clock might not be constant though, also because the framerate is relatively slow it gives the programmer plenty of time to let gameplay code complete before the next frame goes out.
It's not some random date.
Shamelessly stolen from Stackexchange:
>Early versions of unix measured system time in 1/60 s intervals. This meant that a 32-bit unsigned integer could only represent a span of time less than 829 days. For this reason, the time represented by the number 0 (called the epoch) had to be set in the very recent past. As this was in the early 1970s, the epoch was set to 1971-1-1.
>Later, the system time was changed to increment every second, which increased the span of time that could be represented by a 32-bit unsigned integer to around 136 years. As it was no longer so important to squeeze every second out of the counter, the epoch was rounded down to the nearest decade, thus becoming 1970-1-1. One must assume that this was considered a bit neater than 1971-1-1.
>Note that a 32-bit signed integer using 1970-1-1 as its epoch can represent dates up to 2038-1-19, on which date it will wrap around to 1901-12-13.
>how should we measure time
>let's pick the date a fictional character was resurrected
Point is, there is no good reference point unless you want to choose an eclipse or some other significant event.
I can understand how lots of people would/will fall for this, made me wonder for a second until I realized that this would cause data issues with shit on the phone and I wouldn't even bother for the useless novelty.
Also, I had a couple of grim years working for them and know that certain features will not work as intended if you don't have automatic date set even if you manually set it correctly.
Get ready for devices to be even more closed to users thanks to shit like this, I don't even blame the haters, I blame the idiots who let this sort of critical vulnerability open.
>That would be a tad bit retarded because the number would be fucking massive.
With 64bit UNIX time, you could count from the start of the universe and it still wouldn't even be 1% completed today.
No need to feel bad
These retards should get the punishment for buying Apple, and being tech illiterate.
Just using a Facebook doesn't make you tech literate, and these people will experience it firsthand
>These retards should get the punishment for buying Apple, and being tech illiterate.
meh, not everyone -buys- apple. my dad used to have an iPhone because it was a gift. and we used to use apple products back in the beige plastic era. he wasn't to know. then he got some official software update that literally burnt out the phone's wifi and hopped right back off that train. i bet he'd have 'fallen' for this
Still would have been too expensive back when Unix's timekeeping was finalised.
Right, and in mobile devices in like 2013? So okay lets break compatibility with everything just so we can count the time from the birth of """""our lord""""""
Even so I'm sure that counts from 1970 as well, there's just no reason to count from the year 0 other to satisfy some churchy people.
Great argument. Yes I do and so does the rest of the industry clearly.
Nvm, there were only 50 thousand other threads about this on /g/
So hold on for a second. Why the fuck would you use a signed integer for that? Instead of squeezing out double the representable time with a uint?
>Thinking you need an x bit processor to be able to use an x bit variable
This is the kind of people posting on /g/. Suddenly all the terrible purchasing advice and tinfoil hat threads makes sense.
>somethings doesnt working
>its just a meme guys, dont worry about it
AFAIK, it's just a super old piece of software that is the foundation for a lot of stuff. Fixing it properly would break a lot of stupid shit so people just patch it independently when they integrate it into their own system and hope nothing else breaks. You can see how that works out.
Because that's not how UNIX time works. If they used a different time system they could easily do that, but why rewrite software when existing free software can do the job?
This happened to me last night. I was stupid and totally fell for that picture. I went this morning to the nearest Apple product service store. It was hard to explain and one of the guys there did laugh at me. On top of that, they noticed my iPhone 6 was bent, so I can forget the warranty and have to buy a new phone. Luckily there was a guy who probably knew about this or he was just smart and removed the battery and put it back in. Works now but lesson learned.
Which means that the software works just fine. You're not getting the point.
Why are you assuming that a company like apple would not cut corners in software development? Why rewrite an existing system just to fix one bug? Writing software and fixing bugs is expensive and time consuming. It is wrong of them to leave a bug like that unpatched if they knew about it but you are making way too many assumptions on their part.
I'm not defending them, I just see where they are coming from.
Besides, some guy in software development probably mentioned this to his boss and his boss told him not to fix it because something else needed to be worked on instead.
Yes, iPhone 6 phones because the quality of the aluminium isn't as good as in the new phones. Especially when you keep it in your pocket while you sit it's guaranteed it will bent.
How do you plan to let it run down? Rtc modules have small power usage. You may try to run it down by putting a resistor between chargerw ports, but it may not work and thats not a thing average user would do
>32 bit UNIX time will last us ~60 years more
That's IPv4-apologisist-tier. The real solution is to do what OpenBSD did and use 64 Bit.
As to why it is signed, maybe to report errors in C API.
The alleged problem is that some variables on boot get wrong values, if your timezone isn't UTC this will set the unix time to a negative number which somehow fucks up booting.
Some people yesterday said it works to let the battery run down, but it requires leaving it in the boot loop for hours and then power it up again a few times.
Others reported that waiting for the number of hours between you and UTC (e.g. 5 hours for EST) would correctly advance the time to a positive number after which it boots again.
That's about all there's to it, now please stop making duplicate threads on this
So this breaks only iphones in the western hemisphere?
kek, fucking implying
Why is it when Applefags are confronted with a fault they recoil in horror like this? This isn't even damage control it's getting in the foetal position with fingers in your ears.
look, it may shock you to know but people with JOBS (no pun intended) can afford to buy a new iphone if they want.
I mean I didn't break mine but if I did it would have just given me an excuse to go from 6 to 6s.
And if I had a 6s I'd just wait for a 7.
Android losers can't wrap their heads around this because they're NEETs who depend on their mommy to buy them their cheapo phones.
This isn't damage control cause I'm literally laughing my ass of non-ironically that you losers would even bother with this stuff instead of trying to get your tiny microdicks wet.
I mean I know you've abandoned that prospect because god knows no one wants you but you should at least try to lose some fat, gawd...
I've done it on my old iPhone 5s and replacing the SIM Card worked since the time changed in order to connect to cellular towers (still have AT&T)
No need to go to the fagstore to get it fixed.
the top half of this comment is correct, but people that has a lot of money typically didn't obtain it by wasting a lot of it.
If my phone broke I would literally just visit a store and buy a new phone the same day, but I've held onto my Samsung S4 due to the fact that I bought a big ass battery that lasts 3 days, and is way more practical for wasting time at when I'm at work.
smdh desu senpai
>you have to remove the battery which means seeing apple support
Everyone with enough brain can figure out how to open a iPhone. That,and guides on that can be found on Google.
Apple users are no less scum than Apple itself
>32-bit iOS devices will not be affected by this issue
Everything is ruined after Steve Jobs died.
Utc is not a time zone is a standard you fucking cretin
> using frog time
If you are part of the great honorable British Empire you should use the term Zulu time or BST depending on the season
Well you see, transistors aren't smart enough to know what time it is without it being set someway some how. You would have very few options outside of doing it with a battery.
1.) Have a time synchronization server that every iphone device connects to every x units of time to check what time it is.
(this would be expensive, and could even be not as accurate as a battery)
2.) Use the bsd system with the base time
(not necessarily bad if your devs aren't shit)
tl;dr they should have used a watch battery or something
You fucking retard do you know what timezones are? You set the time to jan. 1 in your tinezone obviously, which is about 7 hours before utc if you are american. As internally the os stores utc time it goes negative
I'm gonna see if people are this retarded
>Why rewrite an existing system just to fix one bug? Writing software and fixing bugs is expensive and time consuming.
Yeah I mean it's not like people are paying some shit like $900 per phone or something...
>Our senior tech analyst has confirmed the discovery of an exciting Easter Egg on iPhone devices,
>senior tech analyst
> We’ve contacted Apple to see if it plans to roll out an update to fix the issue and will update if we hear back.
"That's about all there's to it"
"That's about all the information available that you might want to know about it"
I don't even have an iPhone, it's like hostility has become a sport on /g/
>1.) Have a time synchronization server that every iphone device connects to every x units of time to check what time it is.
>(this would be expensive, and could even be not as accurate as a battery)
Doesn't iPhone sync date with carrier and NTP server as default, but for this you need disable that feature.
doesn't matter, a simple google search would have brought up the bug details. pictures on facebook should not be taken as true until you verify it yourself.
this isn't just a problem contained within tech, people share pictures with wild statistics and other people believe it with no question.
Can someone explain to me why the whole phone shits itself if the date is set to a certain date and not just the calender and clock?
Why would the OS, the main processor and the ram care about the date?
Someone on my feed posted a picture and I was thinking of doing it but went like "no, I've seen this shit before. I've participated in the creation of this shit before. I don't know how this will fuck anything up, but it's nefarious."
But holy shit, people just don't learn
I once bricked an Android lollipop tablet by turning off/on in the middle of an app uninstall. Couldn't even get into recovery mode, thing was turbofucked. No root needed.
Fixed by connecting over fastboot and manually clearing the user data/cache (aka factory reset).
This kind of reminds me of Z2K when all the original Zune owners had their Zune's bricked for a day on New Years. It was a leap year and the calendar didn't take that into account or whatever. You had to let the battery drain.
>the C language didn't have unsigned integers.
so what if we use the device manufacturing date as a reference point instead of the unix epoch
There were "consumer targeted" DEC Alpha based PC's running NT4 in the late 90's based on the Alpha 21164PC processor. I remember reading an article on it 'cause back then I was really heavy into CGI stuff and having an Alpha or SGI machine was a dream instead of the dual Pentium Pro IBM PC365 box I had.
>Richard Stallman // February 12, 2016 at 3:54 PM // Reply
>Why do people say it bricks iPhones? I love this theme, been using it for 2 days straight, someone help get out of it, it’s so good!
holy fuckin shit
see you all in hell FUCKERS
Back in the days when having a quad CPU mobo meant you were godlike. Too bad there was no software powerful enough to actually take advantage of it back then. Unless you count POVRAY.
Shit, the dual PPro200 w/128Mb of RAM I had made me the defacto computer god in my circles.
Had a Digital Pictures Oxygen 102 in it for a while, then copped a Diamond FireGL 2000 which I kept in it until I sold it in 2004.
The Unsigned keyword was introduced in 1978
Unix time was established in 1970 .
doens't take a genius to figure out they had to use a Signed INT to store time.
>This will compile on any C compiler.
do you know the difference between
it's like a location based twitter.
you see posts near you, and people see your shit near you.
but you can also yikyak using fake location data and emulator. and they log everything, so don't post anything sensitive, ever. (duh)
>C/C++ is a format to save image data in
most /g/ thing I've read today
no one said they should use C/C++ for everything, but your reading comprehension takes this whole board to a whole new level
it's a apple product. every error is a "may as well buy another one" bricked because that is the business strategy. You need to set aside about $1000 per year for apple products if you want to be part of the ecosystem. If something breaks or if there is a new version and they make the old versions slower.
you might remove the battery to fix it, but even professionals often puncture batteries on iphones when they try to remove it. And I mean people who sucessfully have removed the battery hundreds of times might still quite often puncture the battery and make it blow up. It needs to be done with a fire extinguisher and in a well ventilated area.
Lol you dumb fag, as long as you know logic gates you don't need to follow any guides from the internet out anything, you can deduce everything yourself. If you need guides for something that simple, you have 0 learning capacity
Is it even possible to fix it? Recovery mode and itunes reset or something like that?
Is this a real site or just a troll one? Haven't heard of it.
If it's real then top fucking kek
>which increased the span of time that could be represented by a 32-bit unsigned integer to around 136 years.
>2038 - 1970 = 68 years
I'm back and the goyim know
I opened it to see if someone in my area had done it yet and found this gem.
The span would be from the minimum to the maximum. If the int is unsigned, 1970 would be the minimum. Since that sentence referred to a signed int, 1970 was right in the middle instead, because of how signed ints work
>not having used a computer long enough to know what kind of retarded fuckery can happen if your time is set correctly
this is the second time I've seen this meme repeated on /g/
the alpha was never a consumer product, it was never intended to be a consumer product, the closest thing it ever had to a "consumer" targeted device was the multia, which was built to be a shitty lobotomized workstation for large networked offices. both the alpha and windows NT as a whole were garbage for home users who were mostly still running their shitty 16-bit DOS kludges from the late '80s, something that combo would have only done excruciatingly slower than if you spent several thousand less on a cheap pentium-75 or 486dx2/66
>dual Pentium Pro IBM PC365 box I had
that must have been some shit, I still have a dual 512K PPro HP Vectra but I really want a 365, they look so nice.
I know there are a lot of NAND logic chips out there but I wanted to go even more minimalistic than that.
It was good learning experience if anything, I inhaled a lot of solder fumes but finally mastered soldering. I first made a half adder accidentally, then scraped that circuit and made a full adder.
I made individual xor gates and then put them together in the circuit. After that it was pretty straightforward. It could only add 2 numbers as long as their sum was less than 63, or 6 bits because I fell short on parts kek
For a highschool project, it was more than enough.
This dude was just bragging about his new iPhone case too.
>can't make this shit up
Cool, you were a dick on Facebook for no reason.
And now everyone wants a copy of the picture to do the same?
What the fuck happened to /g/...
Is it really that surprising that Applefags are the most retarded collective in tech?
I mean, even Alienwarefags are superior to Applefags. At least their computers can play video games and won't burn the house down because they have proper airflow. The money they waste at least enables full functionality unlike Applefags.
What's the point of trying to pain /g/ as something it never was knowing that there is still plenty of the old /g/ audience here from before your new ass appeared?
Are you not even aware of the stupidity of your action?
What did you guys do, I told a friend to give it a go blindly thinking he wouldn't fall for it.
Legit website, trying the theme after updating.
>At least their computers can play video games and won't burn the house down
Pretty sure Apple doesn't make any computer intended for gaming.
Might sound crazy to you, but some people use computers for things other than playing video games.