Is it being perceived that Apple was trying to hide what they did? I do agree they could've been a little more specific but doesn't exactly mean they were hiding anything.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Being Sued for 'Purposefully Slowing Down Older iPhone Models' [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
Is it being perceived that Apple was trying to hide what they did? I do agree they could've been a little more specific but doesn't exactly mean they were hiding anything.
Good, I hope Apple gets hit with a huge fine for this. Tired of their ********.
Doesn't throttling, in the way they implemented it, actually extend the window in which an older iPhone is functional? Is an unthrottled CPU but random crash user experience really preferred over a slower but reliable and functional experience?
Okay, yeah, I laid it on a little thick, there. Mea culpa. I'll be more objective.
I wasn't sure about TrueTone either, but I gave it a chance, and it's a great feature. Looking at a screen without TrueTone looks absolutely horrible to me now. Usefulness aside, your statement is incorrect. There's a whole step in the iPhone X setup flow that asks if you want to use TrueTone, and even shows you the difference with it on and off.
Most of the things your Note can do that iPhone can't (you might want to double-check that... iOS does more than it used to) are things that fall way outside the scope of what the masses want from their devices. Apple seeks to make the best device for everyone, which means that it may be more limited than what we'd like. However, as a developer, I've seen that they do try to extend the system's capabilities with each release, hoping to catch a few of us power users in their net, without confusing the mainstream.
Apple is fragmenting behavior to optimize them for their device classes. They will not exclude any supported devices from updates, and they will insure that the same patches, fixes, and features are present across the board. Devices will only become unsupported with age and exclusionary technologies (e.g.: 32-bit)
Apple does not give you access to the device filesystem. They simply provided a unified interface to the various file storage facilities (iCloud Drive, Dropbox, etc.). iOS provides other, more secure ways to get a file from your email to any other application. They may not be what a geek like us is used to, but they work.
It's not so much "geeky" as "something most users will never even think of doing". While a greater percentage of iOS users than Android users actually create content on their device, the majority of Apple's base would never want to make a ringtone.
I wasn't sure about TrueTone either, but I gave it a chance, and it's a great feature. Looking at a screen without TrueTone looks absolutely horrible to me now. Usefulness aside, your statement is incorrect. There's a whole step in the iPhone X setup flow that asks if you want to use TrueTone, and even shows you the difference with it on and off.
I wouldn't go so far as to say the A10 is the best. I can, however, state factually that iOS just makes better of whatever processor it has than Android does. If for no other reason, it comes down to the memory management used by its applications. Objective-C and Swift are automatic-reference-counted languages, and Java uses Garbage Collection. GC sucks on mobile devices, where you don't have a huge amount of RAM and unlimited power consumption.
Because it's reflexive of the real-world performance, which is what really matters, not specs.
User Experience professionals have to constantly remind themselves, "you are not your users." I've often said that the thing that bugs me most about Android devices is that they're in the hands of users who aren't savvy enough to keep them secure and working well. You and I are entirely capable of tweaking the crap out of a phone, maximizing it, protecting it from malware, etc., and we even like doing that kind of thing. But we're members of a tiny minority... we're a subset of a subset of a subset of users. The fact that we're posting here demonstrates that.
Most of the things your Note can do that iPhone can't (you might want to double-check that... iOS does more than it used to) are things that fall way outside the scope of what the masses want from their devices. Apple seeks to make the best device for everyone, which means that it may be more limited than what we'd like. However, as a developer, I've seen that they do try to extend the system's capabilities with each release, hoping to catch a few of us power users in their net, without confusing the mainstream.
I just bought an 8 and Apple already plans to throttle my phone, as well as the X. That tells me they already know these batteries won't hold up.
If there was a safety issue with these batteries there needs to be a recall of some sort. If you are out of warranty they need to at least allow batteries to be replaced at the users expense.
And last, the throttling needs to be reversed pure and simple. I personally do not support them throttling my phone for any reason. If my battery goes bad I will replace it, just give me a warning.
As to Apples intent here, only Apple can say so I won't speculate. This whole thing is just shameful if you ask me.
If there was a safety issue with these batteries there needs to be a recall of some sort. If you are out of warranty they need to at least allow batteries to be replaced at the users expense.
And last, the throttling needs to be reversed pure and simple. I personally do not support them throttling my phone for any reason. If my battery goes bad I will replace it, just give me a warning.
As to Apples intent here, only Apple can say so I won't speculate. This whole thing is just shameful if you ask me.
Apple did not confirm that they are lowering the processor clock frequency. Read their statement again.
They used the words "smooth out" not "slow down". There are lots of other things they could be doing, other than lowering processor clock frequency, to "smooth out" power use. The slow downs reported here could be due to something completely different.
I have not yet detected a slowing down of processor clock frequency on my old iPhone 5s, 6, or 6s devices. I'm an app developer. I know how to measure this stuff without using geekbench. I suspect the geekbench "CPU frequency" numbers are bogus. Something else is behind the slow downs reported.
One more thing...
I bet they will try to software fix this issue soon, with static variables for cpu clockspeed access.
And by kicking out all Benchmarking Apps of their AppStore.
I bet they will try to software fix this issue soon, with static variables for cpu clockspeed access.
And by kicking out all Benchmarking Apps of their AppStore.
oh yeah, me too, I totally did that
and if it werent for apple being such despicable and dirty tricksters my three-year-old phone would have been just as fast as this new one
They are just trying to save their asses with rhetoric.
My mom was complaining about her iPhone6 being unusable so bought a 30€ battery on amazon.
Before:
After installing the new battery:
That’s a double in performance!
She’s happy with her phone again
and probably hold her off for half a year (maybe even a year) to buying a new.
She would have bought a new one... Apple should have informed her about the faulty/degraded battery.
Before:
After installing the new battery:
That’s a double in performance!
She’s happy with her phone again
and probably hold her off for half a year (maybe even a year) to buying a new. She would have bought a new one... Apple should have informed her about the faulty/degraded battery.
It’s not a lazy solution. It’s corporate greed. It’s cheaper than recalling millions of phones to replace batteries. With the huge corporate tax cut, Apple can apply some of the savings to replace all iPhone batteries.
iWarnedYou! Go buy a OnePlus 5T......
Makes no difference. Anyone with Xcode can code, build, and run their own tests, count ARM asm instructions executed (if they know how), and time the results multiple different ways. And see if their measurements change over time, as the battery ages, or before-after OS updates, etc.
No, they're correcting the record. Every headline is sensational, and everything firewood said is factually accurate. iOS is not limiting CPU speed globally, it's preventing the processor from drawing too much voltage when it peaks, which doesn't happen very often in most actual usage, but happens constantly when running GeekBench.
[doublepost=1513985631][/doublepost]
I have a hard time believing that. I mean, you wouldn't have even tested it if it weren't for the headlines, and GeekBench scores have never been reflexive of real-world performance.
I'd be interested to see numbers for how many times GeekBench is being installed now, compared to a week ago.
Well, the Note 4's advantages were SD slot + removable battery + power user centric device. Apple used to mock the earlier Galaxy Note. Now, it's become so mainstream.
Note 8 offers better biometrics w/ an always on fp sensor, Iris scanner, and facial detection (an alright version). You have double the RAM, a better processor, dual cameras, a better S-Pen, water resistance, cleaner software, Samsung Pay, Bixby (not a feature to me, but to some it can be), bluetooth 5.0, HDR 10 display, and other software/hardware features. It is not worth $930 though.
iPhone 6 is much worse than the 8 and it's not even close. Double the RAM, water resistance, dual speakers, 4k capable camera (especially with 60 FPS on the 8), stereo audio speakers, bluetooth 5.0, Touch ID 2.0, better processor (A11 best on the market), better battery life, TrueTone display, better LCD panel, fast charging, wireless charging, front facing camera with flash, 3D Touch, Live Photos, Hey Siri, Taptic Engine, new color options, OIS in the camera, etc.
But 8 vs the X, it's just an OLED display, FaceID, extra GB RAM, no home button, better build quality, Animojis, true depth camera, 18:9 aspect ratio, dual OIS vertical rear cameras. Not worth the extra $300 plus tax for most.
Consumer spending habits and consumption habits can be mind-boggling. There are a lot of cost-conscious people out there, but e-waste is a huge concern. The weird thing is that phones contain so many rare-earth minerals in them that companies can take old phones and remove the materials to reuse or resell to another party at a later date. So the end user giving it up would end up losing out on the individual sums of the components on their own.
But at the same time, these companies' goals are profits first and foremost. CSR (corporate social responsibility) could be a tertiary goal or whatever lower ranked agenda it can be. Milton Friedman ignored CSR more than others as well. I rather not get on more of a tangent.
Apple is a great marketing company and its brand is remarkable considering the corporation was on life-support at one point.
Yes i know, i’m a dev, but then there wouldn’t exist this huge amount of users backing them up and being able to prove the fraud.
But it IS limiting globally. My IPhone 6 plus was nearly unusable before I replaced the battery. Simply skipping songs had a pause of 2-3s.
This will probably come down to examining the logic that governs when the throttling happens. Obviously if the logic is simply "throttle 20% at year 2, throttle 50% at year 3, throttle 75% at year 4", then Apple is definitely defrauding customers because that time based pattern can only be beneficial for selling more phones. Take the extreme case where an old iPhone 4 has never been opened, or perhaps activated but used only once, and then stored away without using battery. If a phone in near-new condition exhibits patterns of "battery saving throttling", then that makes no sense for the customer, and it is definitely defrauding by Apple.
I think a subpoena of the entire history of the iOS codebase is needed because most likely Apple said "oh crap, they found out about our scheme - quick, change the logic so it looks more like we were helping to save the battery life on these phones!"
I think a subpoena of the entire history of the iOS codebase is needed because most likely Apple said "oh crap, they found out about our scheme - quick, change the logic so it looks more like we were helping to save the battery life on these phones!"
Yeah, I'm with you on this. Whatever the outcome, I'm really hoping that it's not just settled out, and that the full technical details come to light. Given that iOS is already capable of measuring battery "health," it's probably not just a time-based thing, so getting some real insight into Apple's actual logic and decisioning would be fascinating. I don't think anyone's gonna get access to much— if any— actual code, but I definitely want to know more.
Yes, exactly. Jonny Ive's desire for seamless design has put Apple into a design hole. I know they want to have everything look clean and elegant, but this is proof that there are certain features that should never be excluded.
If it goes class action, I'm in.
I went into a cell phone repair store today and had them check the battery health of both my iP6s+ and my wife’s iP6s, and they registered 77% and 76%, respectively, not bad considering we’ve had them exactly 2 years now, even though her phone seems to be draining quicker than mine.