Even as a Mac enthusiast, I have steered clear of the iPhone. From not having Exchange server support early on to the high cost of the phone (initially) and AT&T service (continuously), it has not been worth the investment.
Until this past weekend.
It was time for me to finally upgrade my phone, and after trying out the Palm Pre (I was a Treo addict until 2 years ago), I quickly returned it and decided to wait it out for an iPhone.
I now understand all the hype, three years running, for this device. The user interface is amazing, it is very fast, and I'm surprised at how much this phone has enamored me.
Well, this "ga ga" feeling was starting to quickly fade, as I was finding myself with battery life of about 3 hours, without me making any calls. After days of searching and struggling (accompanied by some screaming at times), I finally figured out what was causing the battery drain, and the solution to fixing it.
So, listen up if you are in a Microsoft Exchange environment and are using Entourage on your Mac as a mail client, and are enabling Push on your iPhone.
Here's the scoop:
1. You probably know that Entourage doesn't delete meeting invitations even after you accept them. For the life of me, I don't know why it does this, but it seems completely useless to me.
2. As a result of #1, check to see if you have any of these things lying in your inbox. If you do, this will cause the iPhone to poll the Exchange server in Push mode every six seconds or so, and kill your battery quickly.
3. Delete all of the accepted meeting invites out of your inbox. I'd also empty the Deleted Items folder just to be sure.
4. Doing this will return the iPhone's Push with Exchange to be true Push instead of some weird hybrid Push/Pull.
5. Delete the account on the iPhone, do a hard reset, and then add the exchange account back on.
Now, I don't know technically why the iPhone does this when my Windows Mobile device didn't respond similarly, but I can tell you that by doing the above fix, my battery life is now back up to something like 16 hours as opposed to the prior 3.
Good luck!
Wednesday, June 24, 2009
Subscribe to:
Post Comments (Atom)
5 comments:
The theory is plausible, but deleting the invites from the inbox have not solved the problem for me. As a matter of fact, completely emptying the inbox and the deleted items did not help either. Same issue, so after 8 month of normal operation I have started experiencing rapid discharge with PUSH enabled. Changing the phone have not solved the problem. Please post any ideas you may have.
Here's the source article where I found the solution.
http://discussions.apple.com/thread.jspa?threadID=1696689&tstart=0
I also modified the post to include removing the account from the iPhone, doing a hard reset, then adding the account back in.
I was on the verge of giving up until I read about this. Indeed I had all these calendar invites in my inbox, and once I removed them and emptied my deleted items, battery life has been more than acceptable.
Oh, also, I forgot to mention that yesterday I conditioned the battery two times (drain fully then charge fully) using the wall charger. But I know for a fact that just doing the conditioning didn't help me.
It could very well be that there is something else wrong, and perhaps I should be getting more than 16-18 hours of standby battery life with wifi on and push on, but that amount of life is fine for me for now.
Thanks for sharing this information, Aaron.
Even though we all know over here that you've gone completely over to the business-side with a Blackberry Tour.
Nonetheless, I'll be posting this fixit on my own Blog.
Meanwhile, we're sticking with the Blackberry Curve 8900 for now. But, the newest iPhone is close. Very close. And, we've hacked our Curves into MacBerry's - http://briancork.wordpress.com/2009/06/09/the-macberry/.
And, AT&T is working very diligently to improve it's service - and, it's working. You will be able to read about my own recent adventures, and satisfaction, over that in the next week.
Cork
Well, one thing to keep in mind is that with 3.1 - which was also supposed to fix the battery issue - people are reporting even more battery issues. So, I still think this is an implementation thing with Push that Apple just hasn't figured out yet. I think they will - eventually. But until that day, I'll have to stay away.
Post a Comment