Huh... interesting. Then why are we still talking about Error 53 today? I actually didn't know it had been "fixed" given the amount of time it still spends in the news.
I assume we are still talking about Error 53 more than a YEAR after a Fix because:
1. Apple Hate
2. Moneygrubbing Litigious Assholes
3. Willful Blindness by those trying to MISREPRESENT Error 53 for their own Porpoises
4. People don't HAVE to install an OS Update. Even one that fixes something...
I guess I don't understand why that's crazy. When I have something that works perfectly and does everything I need it to do, why is it forced into obsolescence and why am I forced to spend a bunch of money to 'upgrade' something that didn't need it?
If it works perfectly, You don't have to upgrade at all.
Also it means I have to throw away my Core Duo based macs. This is a bit why, after using macs and OSX for 15 years that I have walked away from them. I can't keep up with the pace that Apple has set for consumers.
Does it still run the Apps and OS installed on it?
Then why do you have to throw it away?
Besides, they said "High Sierra" will be the last macOS to run 32 bit apps "Without Compromises". That could simply mean that they won't be able to work with upcoming technologies, or take advantage of Memory over x GB, or something.
1. TRANSFER the ORIGINAL Home Button/Touch ID Sensor from the ORIGINAL Display assembly to the NEW Display Assembly. There are many tutorials available on HOW to do this, as well as the IMPORTANCE of doing so.
I do like how you capitalised all the words that become completely irrelevant when the ID sensor has failed. You know... one of the reasons you would take such a device to a repairer.
But that's why you're just a fake. The Real Tim Cook would put a lot more thought into user blaming.
Doesn't matter. We are ALL wrong.
It actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
By the way, BLOW ME for using Caps to Emphasize. As soon as Slashdot gets into the 20th (let alone 21st) Century and grows a Rich-Text Editor, I will continue to use the equally antiquated method of using CAPS TO EMPHASIZE.
besides, it could just revert back to asking the code onscreen. or letting you reset the device.
But it actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
Not out of context. It's an absolute. We went through this shit with cars a few years ago. The product is supposed to be owned not leased and the owner should be able to do anything legal they want to with the thing they own - including taking it to whatever mechanic or technician they want to.
But in this case, it actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
Everything I've read or heard about it is that it happens upon update. Louis Rossmann of Rossmann Group (3rd party Mac repair facility) and Jessa Jones of iPad Rehab (3rd party iPhone and iPad repair facility) are my primary sources on this. One iPhone/iPad repair neither of them will do is a home button replacement, after the first batch of such repairs on fingerprint-enabled devices resulted in Error 53 weeks after the repairs. Given that the phone must be shut down for the repair, a reboot is part of that process and the error would have been evident before the phones were returned to their owners if it happened after a reboot.
Ok, I understand.
But it actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
Sure, but why not do it as a single "News from WWDC" rather than posting, what is it now, six, seven, eight articles all on what seem like pretty minor announcements from Apple? Like these guys did, for example. The only thing in that whole pile of little tweaks and updates of any real significance was the HomePod, and even then it's just a catch-up to the Echo and Google Home.
Steve would have given them something to post about...
Oh, apparently, at least in the sound department, the HomePod is head and shoulders above everyone else. Hardly "just catch-up" when you fly past the others in the first stride...
But don't you see, it's got a 40% narrower bezel! You need to immediately throw out your current $1,500 iPad and buy a new $1,500 iPad that'll be replaced in six months with one that's exactly the same except for some minor cosmetic change, because Apple!
Me and the iPad 2 I am typing this on beg to differ.
The owner of a PC running Windows 10 S can buy an upgrade to Windows 10 Pro for $50. The owner of an iPad Pro has to pay about ten times that much for a Mac mini, even assuming he or she can use a keyboard and mouse from Goodwill and the living room TV as a monitor.
That's right; include The price of the hardware in one case, and not in the other.
I think the iMac Pro sounds good. I like the many cores etc. Since I am a video editing hobbyist, I sure can use them. I have a fully loaded 27" late 2013 iMac today which did cost me a small fortune. I have an extra cinema display attached to it and external RAID enclosure for more space and speed.
But I would really like a more modular machine. Right now I could use a better GPU for rendering. Of course the CPUs are maxed out too, but a new GPU would be great and could extend the life of the machine. I hate that I have to ditch a perfectly fine 27" monitor, well the entire machine just to upgrade. At least I got the better CPU and GPU.
Since I don't have a money tree in my garden, it becomes expensive.:D
Besides from OS X, it is mostly FCP X that keeps me on the Apple platform. Not having to tinker with hardware was also a part of it, but I guess that is why you pay the premium price. I thought about building a Hackingtosh as that would enable me to do small upgrades.
I guess I have to start saving up money to get a new machine next year.:)
You must be retarded to think disabling the phone only after doing an ios update is in any way a security measure.
Only thief who was even more stupid than you (quite the feat) would go to the trouble of swapping the sensor, and then instead of accessing all the juicy details, update and brick the phone.
Well, I do stand corrected (but not by you).
Apparently, this was a mistake, and has been fixed by Apple since February, 2016.
We go back and forth between agreeing and disagreeing with each other, so I hope I can get your attention with this.
You do realize that error 53 doesn't pop up until a software update after the repair, right? How does soft-bricking the phone with error 53 that stop someone from swapping the home button and gaining access?
It doesn't.
The new home button not being paired and, thereby, only functioning as a button and not a fingerprint scanner is what prevents a button swap from bypassing the security of the device. In fact, since you would have to unlock the phone to access the settings menu in the first place, there's little reason they can't give end users a "pair home button" option in system settings.
I thought that error 53 happened upon Restart. Are you sure about that?
1. TRANSFER the ORIGINAL Home Button/Touch ID Sensor from the ORIGINAL Display assembly to the NEW Display Assembly. There are many tutorials available on HOW to do this, as well as the IMPORTANCE of doing so.
So is that documented in the 'third-party repair' support documents that Apple publishes? Do they even publish any guidance to third-party repair operations? Or do they stonewall about everything and refuse to acknowledge that any third-party repair should be allowed?
It simply isn't enough to force third-party repair technicians to rely on YouTube videos about repair issues.
Slashdot is a nerd site, where we're the people who the first thing we do with new tech is take it apart to figure it out. You're not going to get away with expecting us to pray at the altar of the Company Store.
Show me one cellphone mfg. that publishers full repair manuals for 3rd parties (individuals) and offers OEM parts to same.
If the queue is long, the solution is for Apple to scale up the repair operation. Hire more technicians, have more repair functions going on concurrently.
That costs money, but they're charging money for services, so they should be spending it to deliver services.
I am not sure what the point of this is. There is no headphone jack to deliver analog audio. All new iPhones will have to deal bluetooth compression anyway. Maybe I am simply ignorant, but this seems like a "innovation" without a point.
AirPods, when paired to a device capable of AAC, use AAC, not that horrid CODEC that "Bluetooth Audio" uses.
Not quite lossless; but a damn sight better than what you are alleging.
Slashdot Mirror
Huh... interesting. Then why are we still talking about Error 53 today? I actually didn't know it had been "fixed" given the amount of time it still spends in the news.
I assume we are still talking about Error 53 more than a YEAR after a Fix because:
1. Apple Hate
2. Moneygrubbing Litigious Assholes
3. Willful Blindness by those trying to MISREPRESENT Error 53 for their own Porpoises
4. People don't HAVE to install an OS Update. Even one that fixes something...
And the reason to rip out support for 32-bit?
Testing.
Stability.
Memory Footprint.
There's 3 GOOD reasons for removing nearly-obsolete support.
I guess I don't understand why that's crazy. When I have something that works perfectly and does everything I need it to do, why is it forced into obsolescence and why am I forced to spend a bunch of money to 'upgrade' something that didn't need it?
If it works perfectly, You don't have to upgrade at all.
EXACTLY!
Also it means I have to throw away my Core Duo based macs. This is a bit why, after using macs and OSX for 15 years that I have walked away from them. I can't keep up with the pace that Apple has set for consumers.
Does it still run the Apps and OS installed on it?
Then why do you have to throw it away?
Besides, they said "High Sierra" will be the last macOS to run 32 bit apps "Without Compromises". That could simply mean that they won't be able to work with upcoming technologies, or take advantage of Memory over x GB, or something.
1. TRANSFER the ORIGINAL Home Button/Touch ID Sensor from the ORIGINAL Display assembly to the NEW Display Assembly. There are many tutorials available on HOW to do this, as well as the IMPORTANCE of doing so.
I do like how you capitalised all the words that become completely irrelevant when the ID sensor has failed. You know ... one of the reasons you would take such a device to a repairer.
But that's why you're just a fake. The Real Tim Cook would put a lot more thought into user blaming.
Doesn't matter. We are ALL wrong.
It actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
http://ifixit.org/blog/7924/er...
By the way, BLOW ME for using Caps to Emphasize. As soon as Slashdot gets into the 20th (let alone 21st) Century and grows a Rich-Text Editor, I will continue to use the equally antiquated method of using CAPS TO EMPHASIZE.
So, FOAD.
Using AAC over Bluetooth is a capability of the Bluetooth Advanced Audio Distribution Profile (A2DP) and not just limited to Apple devices.
Of course it's not well publicised so good luck telling which codec your Bluetooth devices are actually using.
I know it isn't "Just Apple". I don't think I ever said it was.
they reversed already
besides, it could just revert back to asking the code onscreen. or letting you reset the device.
But it actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
http://ifixit.org/blog/7924/er...
Not out of context. It's an absolute.
We went through this shit with cars a few years ago. The product is supposed to be owned not leased and the owner should be able to do anything legal they want to with the thing they own - including taking it to whatever mechanic or technician they want to.
But in this case, it actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
http://ifixit.org/blog/7924/er...
Everything I've read or heard about it is that it happens upon update. Louis Rossmann of Rossmann Group (3rd party Mac repair facility) and Jessa Jones of iPad Rehab (3rd party iPhone and iPad repair facility) are my primary sources on this. One iPhone/iPad repair neither of them will do is a home button replacement, after the first batch of such repairs on fingerprint-enabled devices resulted in Error 53 weeks after the repairs. Given that the phone must be shut down for the repair, a reboot is part of that process and the error would have been evident before the phones were returned to their owners if it happened after a reboot.
Ok, I understand.
But it actually seems that Apple accidentally left some Production Testing code in an iOS9 build, causing the Error 53.
They released a patched version of iOS 9 last February to both fix the problem, AND "unbrick" phones that had inadvertently been "caught" by the test-code.
http://ifixit.org/blog/7924/er...
It varies the SCAN rate of the DIGITIZER to optimize Pencil-Tracking.
It cranks it down to save batteries when you aren't "Pencilling".
My 2012 LG television has 120Hz refresh too.
Will Apple be adding 3D next? My TV came with four pair of glasses... but I've never opened those boxes.
I thought you liked Apple.
The 120 Hz refresh is for smooth Pencil use. They just provide different scan rates to optimize battery life.
di/dt, ya know...
Sure, but why not do it as a single "News from WWDC" rather than posting, what is it now, six, seven, eight articles all on what seem like pretty minor announcements from Apple? Like these guys did, for example. The only thing in that whole pile of little tweaks and updates of any real significance was the HomePod, and even then it's just a catch-up to the Echo and Google Home.
Steve would have given them something to post about...
Oh, apparently, at least in the sound department, the HomePod is head and shoulders above everyone else. Hardly "just catch-up" when you fly past the others in the first stride...
But don't you see, it's got a 40% narrower bezel! You need to immediately throw out your current $1,500 iPad and buy a new $1,500 iPad that'll be replaced in six months with one that's exactly the same except for some minor cosmetic change, because Apple!
Me and the iPad 2 I am typing this on beg to differ.
The owner of a PC running Windows 10 S can buy an upgrade to Windows 10 Pro for $50. The owner of an iPad Pro has to pay about ten times that much for a Mac mini, even assuming he or she can use a keyboard and mouse from Goodwill and the living room TV as a monitor.
That's right; include The price of the hardware in one case, and not in the other.
Nice try.
and but its from apple; Yuk.
Don't like it, then GO AWAY.
No he is not.
There is no 120Ghz content for tablet. So there is not practical reason for it.
On workstation, it's justified, because computer games, video editing, 3d programs, etc...
WTF ARE YOU TALKING ABOUT???
I think the iMac Pro sounds good. I like the many cores etc. Since I am a video editing hobbyist, I sure can use them. I have a fully loaded 27" late 2013 iMac today which did cost me a small fortune. I have an extra cinema display attached to it and external RAID enclosure for more space and speed.
But I would really like a more modular machine. Right now I could use a better GPU for rendering. Of course the CPUs are maxed out too, but a new GPU would be great and could extend the life of the machine.
I hate that I have to ditch a perfectly fine 27" monitor, well the entire machine just to upgrade. At least I got the better CPU and GPU.
Since I don't have a money tree in my garden, it becomes expensive. :D
Besides from OS X, it is mostly FCP X that keeps me on the Apple platform. Not having to tinker with hardware was also a part of it, but I guess that is why you pay the premium price. I thought about building a Hackingtosh as that would enable me to do small upgrades.
I guess I have to start saving up money to get a new machine next year. :)
The modular Mac Pro is still coming. Next year.
You must be retarded to think disabling the phone only after doing an ios update is in any way a security measure.
Only thief who was even more stupid than you (quite the feat) would go to the trouble of swapping the sensor, and then instead of accessing all the juicy details, update and brick the phone.
Well, I do stand corrected (but not by you).
Apparently, this was a mistake, and has been fixed by Apple since February, 2016.
https://techcrunch.com/2016/02...
We go back and forth between agreeing and disagreeing with each other, so I hope I can get your attention with this.
You do realize that error 53 doesn't pop up until a software update after the repair, right? How does soft-bricking the phone with error 53 that stop someone from swapping the home button and gaining access?
It doesn't.
The new home button not being paired and, thereby, only functioning as a button and not a fingerprint scanner is what prevents a button swap from bypassing the security of the device. In fact, since you would have to unlock the phone to access the settings menu in the first place, there's little reason they can't give end users a "pair home button" option in system settings.
I thought that error 53 happened upon Restart. Are you sure about that?
The ACs have gotten bad in the past week or so. One almost has to wonder if 4chan just recently discovered Slashdot.
They're ALWAYS bad; and they are a cancer upon Slashdot.
Seriously, like two dozen nearly-identical AC posts IN A ROW?!?
1. TRANSFER the ORIGINAL Home Button/Touch ID Sensor from the ORIGINAL Display assembly to the NEW Display Assembly. There are many tutorials available on HOW to do this, as well as the IMPORTANCE of doing so.
So is that documented in the 'third-party repair' support documents that Apple publishes? Do they even publish any guidance to third-party repair operations? Or do they stonewall about everything and refuse to acknowledge that any third-party repair should be allowed?
It simply isn't enough to force third-party repair technicians to rely on YouTube videos about repair issues.
Slashdot is a nerd site, where we're the people who the first thing we do with new tech is take it apart to figure it out. You're not going to get away with expecting us to pray at the altar of the Company Store.
Show me one cellphone mfg. that publishers full repair manuals for 3rd parties (individuals) and offers OEM parts to same.
That required step is well and truly "anti-third-party-repair".
If taken out of context, like you have.
If the queue is long, the solution is for Apple to scale up the repair operation. Hire more technicians, have more repair functions going on concurrently.
That costs money, but they're charging money for services, so they should be spending it to deliver services.
You can only scale things so far.
Yes.
Or I am.
Jobs left. They brought him back. That is one.
Jobs died. He is still dead. That is two.
So, there's at least two. I am not sure if we want to refine it further, but two is more than one. Hell, it's twice as many.
I guess you're technically correct.
But Apple us doing JUST fine this time; so...?
I am not sure what the point of this is. There is no headphone jack to deliver analog audio. All new iPhones will have to deal bluetooth compression anyway. Maybe I am simply ignorant, but this seems like a "innovation" without a point.
AirPods, when paired to a device capable of AAC, use AAC, not that horrid CODEC that "Bluetooth Audio" uses.
Not quite lossless; but a damn sight better than what you are alleging.