On the contrary.On the contrary that's better then what Apple did.
What was happening on iOS-
Phone battery is defective. Battery unable to provide required charge. Owner is unaware of this and doesn't know about coconut battery and these other apps. Phone seems sluggish and is showing stuttering.Owner goes to the store. The store app is set up in such a way that unless battery health gets below 80% it will show up as fine on Apple's diags. Battery checks out fine. Owner is fed up with the slowdown. Goes out and buys a new iPhone using trade-in.
What reportedly happens on Android(no citation of any company as of yet)-
Phone shuts down. Owner goes to the store, issue is recognised as that of the battery. Buys a new battery. Problem solved.
See how easy it is? Unfortunately for Tim Cook, the above results in 1 less sale which is why he didn't do that.
Also I am still not sure if they are cheating in that battery health setting app so that people do not buy that discounted battery. My iPhone 6 battery health is 82% on coconut battery. On iOS 12 the inbuilt settings app shows health at 91%. Judging by the battery life, coconut battery seems to be more accurate to me.
Here's what was happening on IOS:
Power management kicks in to keep the phone running if the battery can't supply the proper voltage. User notices it or not. User cares or not. Some users may persue this further and get conflicting information. Maybe user gets battery replace and perhaps user notices a difference or not. (This is first hand anecdotal information)
Here's what was happening on Android:
Phone shuts down pisses user off because user does not know what is going on. (Sample citation given above)
[doublepost=1535984581][/doublepost]
Guess you missed the sentence in the manual about "professional installation". That eliminates all of this folderol in trying to compare a cpu installation with the insertion of the s-pen that can break the phone. Gee, I wonder if professional installation should have been noted in the Galaxy manual.I glanced over the whole manual and I did not find a single page where it states that trying to insert the CPU wrong will damage it beyond repair. If it's stated in small fine print it might as well not be there. And this is only for the Intel CPUs where the pins are on the motherboard. With AMD the pins are on the CPU so it's even easier to bend one.
I bet you guys did not even bother to download the Note 5 manual and check out what was written in it. For your reference, this is the warning I am talking about
http://downloadcenter.samsung.com/c...N920V_Galaxy-Note5_EN_UM_LL_5.1_OGE_FINAL.pdf
Warning: Be sure to insert your S Pen with the nib pointed inward. Inserting the S Pen the wrong way can cause it to become stuck and can damage the pen and your phone.
What pray-tell does a keyboard have to do with anything. You can't legislate stupidity, but you can help mitigate the consequences of bad design decisions. Samsung did not do this. Fail.And just like how Apple can't find a way to fix people's stupidity, Samsung can't either. Samsung showed the users how the Spen is to be inserted in the illustration. You use a device how it is meant to be used in the manual. If you experiment with it, it's on you not Samsung.
The MacBook keyboard stops working if dust gets under it. Is there anything given in the manual?
Sure, I can ruin my phone by toggling the toggle the wrong way.No,it's a very good example as turning it off doesn't turn it off. The first switch on the planet which behaves like this.
Yep, the lines at the apple store must be out the door as apple is fixing broken phones for this one.Also don’t forget the auto brightness toggle. It isn’t located in display and brightness like it’s supposed to be. You have to dig inside a convoluted series of menus to find a simple toggle. An amateur will need a google search to find out where it is.
Now you are putting parameters about how benchmarks can be manipulated. What can be manipulated up, can be manipulated down.Benchmarks can only be manipulated upwards, not downwards. No company wants to make their product look bad. Geekbench showed the score being halved and it was not a manipulation on the part of Geekbench because Apple confirmed later that what Geekbench was showing was genuine.
Apple only gave a way to solve it after 30 lawsuits were filed against it.
You can't prove the correlation between a lawsuit and ios update, as you can't prove what was in the works in apple software development.
Last edited: