Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There isn't going to be a recall until there is a determination of cause, and there won't be a recall at all if the numbers of affected customers is low, which is surely appears to be now. There will still be the option for replacement of affected iPhones under warranty.

The only issue that the customer might have to deal with is an affected iPhone that is past its standard warranty. If in fact Apple does not provide replacement, then there would be cause for a class action lawsuit which might include a recall.

So far, there isn't even much evidence that this is widespread, but just another internet "wildfire" driven by relative small numbers of anecdotal evidence.


Very well put.
 
Thanks Fatboy. Much appreciated.


Does anyone truly know if that app is safe? Trusting anything that doesn't come from the App Store is questionable. Even if it appears to do what it claims how does anyone know whatever other mischief it might be doing via the install process or within the app itself?
 
If you're worried do a backup, install and run the app to find out if you have TLC or MLC then restore full image with iTunes and restore backup.
 
First of all sorry for my english

I,ve been reading this theme, i have an 6+ 128gb with TLC memory, and apart of the comparison bet velocities I read on Internet the life of 1000 cycles instead the 10000 of the MLC, for a normal user in years what's means? Because I found sites that says less than 4 years and others says till 11 years, I think 4 years it's a very little time no?!
 
First of all sorry for my english

I,ve been reading this theme, i have an 6+ 128gb with TLC memory, and apart of the comparison bet velocities I read on Internet the life of 1000 cycles instead the 10000 of the MLC, for a normal user in years what's means? Because I found sites that says less than 4 years and others says till 11 years, I think 4 years it's a very little time no?!

Over time, NAND cells will fail, and these locations will be removed from use by the memory controller that will also level the use of all of the cells, but I would think that most users will never see any noticeable decrease in the size of the memory. Even a loss of 10% of the cells in 4 years wouldn't be much of an issue for iPhones with large amounts of storage. I would think that 8 GB devices would be more at risk as there is a higher proportion of storage devoted to iOS and required Apps; you would notice the decrease in available storage.

In truth, if you can accept three to four years of hard use out of a device with 90% of the storage remaining, as an example, there will be plenty of used devices available on the market at cheap prices that will probably have a great deal of life in them.

Most people will probably have upgraded before that occurs. It's not something that many people need to worry about.

EDIT: I have a friend still using an iPhone 1. She won't give it up until it fails. I think that she treasures that it was a gift, but also that it is sufficient for her needs.
 
Last edited:
Iphone 6+

Just a quick summary of the current community results.... really did not expect such variance!

Code:
Device ____	User ____	Write	Read
iPhone 6 128GB	eclipsevv	174	363
iPhone 6 64GB	kemal __ 	54	337
iPhone 6+ 128GB	TEMPA __	135	195
iPad Air2 64GB	nagypeter	161	932


Mine is: Storage Write/ 184MByte/Sec
Storage Read/ 349MByte/Sec

Memory is: Memory Write: 1037MByte/Sec
Memory Read: 1019MByte/Sec
 
I'd like to check, but should I trust installing apps outside of the Apple AppStore?

Has anyone checked that PGYER's code for malware?

I thought exactly the same - we've had 2 recent alerts about malware being distributed through unofficial channels and still people continue to do it.

Not a bad scenario if you want to infect loads of phones: Start a rumour about some phones containing inferior components and then release a malware ridden app that can check what's in the phone and wait for people to infect themselves. I'm not saying this is what has happened here, but it would certainly be a decent attack vector judging by comments in this thread!
 
I thought exactly the same - we've had 2 recent alerts about malware being distributed through unofficial channels and still people continue to do it.

Not a bad scenario if you want to infect loads of phones: Start a rumour about some phones containing inferior components and then release a malware ridden app that can check what's in the phone and wait for people to infect themselves. I'm not saying this is what has happened here, but it would certainly be a decent attack vector judging by comments in this thread!

After i used the tool i deleted it and done a backup to get a clean install again.
For all who have a 128GB Iphone 6 you can be sure to have TLC nand dont use the tool. And one more important thing. TLC NAND is 33% more compact. To get 128GB in a iphone 6 or 6 plus they use 8 nand blocks. Maybe they hade to use the more compact nand to achieve the thin factor. I dont think this was done because of the cost. All ipad Air 128GB use the TLC nand since one year and never we did hear the same complaints as now with the iphone 6. Did anyone with a iphone 6 with MLC nand test the speed with the benchmark tool available at the appstore?

----------

I wonder if the guys with MLC nand will have higher Write and read values.
If they could post there results i would be very thankfull.
 
[/COLOR]I wonder if the guys with MLC nand will have higher Write and read values.

If they could post there results i would be very thankfull.


Several people with the MLC NAND already posted their result in previous posts: MLC is much slower than TLC in write speed (around 40% speed), while read speed is essentially the same.
 
Several people with the MLC NAND already posted their result in previous posts: MLC is much slower than TLC in write speed (around 40% speed), while read speed is essentially the same.

Oh i did not see the MLC results. But thanx for the information. So if its faster its nice, but what is with the lifespan? How many years would you guess it could be usefull? 4Years? 10 Years?
 
Oh i did not see the MLC results. But thanx for the information. So if its faster its nice, but what is with the lifespan? How many years would you guess it could be usefull? 4Years? 10 Years?

typically the P/E of a TLC nand is 1000 cycles, however consider, as a precaution, only 500 cycles and considering that each day we move (write & erase) 10GB of data (value too excessive for a smartphone - it's not a computer) in this case the lifespan of a 64GB iPhone will be (500X64) / 10 = 3200 days or 8.76 years.

As you see it is a false problem ..... let's enjoy our iPhone for what it is and not for how it is made,

Sorry for my English
 
Unless you restore your iPhone every 10 days, I'd say 10GB/day is definitely too much. iOS has no memory paging on disk, most of the time the phone will write new images/media or updated apps. TLC lifespan is definitely not an issue.
 
I have iPhone 6 64gb but mines is MLC. I guess I'm one of the lucky ones.
 
Last edited:
IPad Air 128GB

I have iPhone 6 64gb but mines is MLC. I'm guess I'm one of the lucky ones.

I just checked my ipad air it is MLC. Im very surprised. I was thinking it is TLC.
But my Ipad Air 2 is TLC. I wonder if this was the price to realize the thinn factor of the new ipad air 2 and iphone 6 plus.
 
Random write is the important stat (bottom graph) which can be up to 7 times as slow with TLC vs MLC:

41410_01_apple_iphone_6_storage_tested_with_mlc_and_tlc_nand.png
 
Unless you restore your iPhone every 10 days, I'd say 10GB/day is definitely too much. iOS has no memory paging on disk, most of the time the phone will write new images/media or updated apps. TLC lifespan is definitely not an issue.


Honestly, the phone will be obsolete LONG before the memory degrades.
 
Random write is the important stat (bottom graph) which can be up to 7 times as slow with TLC vs MLC:

Image

That would mean that a iPhone 6Plus with TLC nand is 7 times slower? Thats ********. I tested my ipad air 128gb with MLC against my iPad Air 2 with TLC . In each installation progress the ipad air 2 was much faster. Even if you compare a iphone 6 with TLC and one with MLC you wont find big diffrences.
I mean in real life scenarios.
 
Hey i have this odd issue and maybe it's TLC NAND related?
I have a Space Grey Iphone 6 128GB version with a TLC NAND equipped.
This is an new exchanged phone, the last one had the same problem..


It's like some sort of lag when the music application is on and it sounds kinda odd like a static crack/pop noise,
for half a second and then dissapears.
I find it's quite annoying with the heavy use of safari while my music is on and i hear the crack/pop while loading.
This especially happens often/randomly when the phone is trying to load large apps/websites.

Although the song continues playing but just with that half a second crack/pop delay..
If i leave the phone alone with the music app on and playing the songs then i experience no problems or whatsoever.

So i'm not quite sure what to do yet, maybe a new firmware can fix the issue?
I'm kind of clueless since i already tried 8.0.2, 8.1.1 and now 8.1 and still the same issue.
All in all with a backup restore and even multiple reset as factory and that goes the same for my exchanged Iphone.
And my phone is jailbroken, without jailbreak the problem still exist. 

And even tried to replicate it on my Iphone 5 with the same firmware and no problems.
Although i never had a problem with my Iphone 5.
 
Never had this problem, but for sure it cannot be NAND related. In the situation you describe, both Music and Safari are in RAM, there would be no need to read from NAND.
 
Never had this problem, but for sure it cannot be NAND related. In the situation you describe, both Music and Safari are in RAM, there would be no need to read from NAND.

So you say the TLC NAND is not responsible for any problems? Funny we never heard of such problems under the MLC nand. I think the TLC sucks big time. Wish my iPhone 6 plus and iPad Air 2 hade MLC :(
 
Never had this problem, but for sure it cannot be NAND related. In the situation you describe, both Music and Safari are in RAM, there would be no need to read from NAND.

Yes, i'm still not quite sure what the problem can be.
I litteraly tried everything i could and still this problem exist nonetheless.

I searched on google for this problem, but couldn't find something related or that people does have experienced it?
And even with this exchanged phone the problem is still there, which is kind of weird?

Although i'm a really heavy safari user so i tend to put the music app on while browsing,
and if this problem occurs so often it's really annoying.

I've been keeping an eye on it since the first time it happend, and it only happens when i try to load something big.
And this especially happens so often and randomly while loading a content-rich-websites and sometimes in opening/closing apps.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.