MattyEss wrote:
[...]
BTW Thankyou Mods for deleteling all the inane posts that were in the last page or two of this thread
You should note that this includes your post of yesterday. I guess the moderators cut the apple in two so to speak - and some "users" must have leveraged lots of efforts to achieve such a limited result. Many of my posts remain, yet unfortunately not the huge one summarizing my contribution - my bad it contained some superfluous flaming elements - but intellectually honest people know about my contribution, have acknowledged it, and I feel entirely vindicated in that respect. I'm always supportive of moderation decision making though, as I don't set the rules in here. But neither do you or pals!!!
That being said, in terms of support, well, some questions remain for me. One I can't answer is what type of usage one can get in terms of word processing with a full charge i.e. plain typing of text within an app. Someone made a joke on that yesterday but in the end I find it's an interesting question - especially since some people compare a smartphone to a computer and an important function of a computer is word processing.
Also I note people always come back to the idea of "phantom usage". It's important to remember that this shouldn't be confused with "standby drain" i.e. 0.5% per hour - which can become more in low coverage situations(which cannot always be controlled by the user, even within the same location) - nor with definition based "usage" which includes background processing such as auto-checking of mail - so this can also extend to normal background polling for network centric apps. In summary someone having mail push/pull and network centric apps with notifications and such will always have usage "without touching the phone" (and most likely which would be added on top of the 0.5%) - yet this is not phantom usage, which should cover everything else i.e. out of spec. You can't have your cake and eat it. I think Apple should allow an option for log based notifications i.e. trapping of events like crashes that generate a visible notification as how can someone debug apps when he has 200 of them without removing them all and starting from scratch? Even that cannot be conclusive because an app can behave well at first and bug afterwards and also there is no account for possible app interaction. This is another way of saying that the Apple "experience" shouldn't hinder support.
Another question also remains in terms of charge cycles. Whether this is required only of a new device or whether this is required each time an OS update is applied. In the first case scenario, I think it's time Apple installs batteries and charges/discharges them at the factory level as to "burn them in" so to speak. In the second case, well, that means this variable is always relevant after a patch and posters should be constantly reminded of that...