Scotty Loveless, a former Apple Genius, has posted the best guide we’ve seen to solving iOS battery drain. Unlike many guides that tell you to turn off every feature, Loveless offers a more targeted approach, including instructions on how to test battery drain and specific suggestions that are likely to improve battery life. Two surprises: the Facebook app is a huge battery hog and quitting apps may hurt battery life. follow link
Mysteriously Moving Margins in Word
In Microsoft Word 2008 (and older versions), if you put your cursor in a paragraph and then move a tab or indent marker in the ruler, the change applies to just that paragraph. If your markers are closely spaced, you may have trouble grabbing the right one, and inadvertently work with tabs when you want to work with indents, or vice-versa. The solution is to hover your mouse over the marker until a yellow tooltip confirms which element you're about to drag.
I recently came to appreciate the importance of waiting for those tooltips: a document mysteriously reset its margins several times while I was under deadline pressure, causing a variety of problems. After several hours of puzzlement, I had my "doh!" moment: I had been dragging a margin marker when I thought I was dragging an indent marker.
When it comes to moving markers in the Word ruler, the moral of the story is always to hover, read, and only then drag.
The Ultimate Guide to iPhone Battery Drain
I could see that my wife's iPhone 4S was never sleeping (Usage and Standby times were equal). GREAT! I finally had a diagnosis of the problem.
How come this advice is not better known?
But, Apple offers no insight nor tools to help fix this.
Force quit every app - nope. Restarts - nope. Upgrade to iOS 7 - nope. More Restarts - nope. Turn off Location Services - nope. Turn off Background App Refresh - nope. More force quits - nope. Install Battery Performance Monitor apps - nope.
So now what?
Installing System Activity Monitor app helped, but the savings finally came from deleting an old Mail account which obviously was caught in a loop.
Surely Apple could give tools to identify issues like this earlier?