5706 Views 4 Replies Latest reply: Aug 19, 2010 12:11 PM by rahul.l
Double tapping home button will show you apps that are recently used or running. Not many run in background but depending on what you have installed, you may of installed one that does.
Also note that when checking mail if the server is slow or bogged down or your signal isn't good, it will take more time and processor to check mail thus more battery.
There are many factors to power usage so hard to pinpoint. Could just be the phone cranking up the power to talk to cell tower if the signal is low (strength can change over time during the day even in same spot).
You could also just have an app that has a memory leak and is running and shouldn't be. It is like a computer after all and no app is perfect.
If not running iOS4 then you don't have any multi tasking so the only things that can effect quick battery drain when not using it is the signal stuff (pumping up power for low signal), mail checking that takes longer than normal for variety of reasons, or an memory leak in some app thus a bug.
None of which you can fix yourself really unless you can narrow down some app that seems to kill off your battery often after you used it after a clean reboot.
I'm facing this same problem. My usage time and standby time are both at 1 hour 10 minutes right now even though my phone was in sleep mode for the past 30 minutes. I've noticed this issue since upgrading to OS 4 but i'm using a 3G so there is no multi-tasking on my device. I know it isn't a low signal issue because I have a very strong cell signal at home. It isn't the mail app either since the last updated time was over 45 minutes ago when I last checked my mail. The only solution I've found for this is a hard reset (home button+sleep/wake button held down for 10 seconds). I don't believe that iPhone apps are "like a computer" because all apps from the AppStore are first approved by Apple and any apps that run in the background/leak memory are supposed to be rejected. I was hoping that iOS 4.1 would fix this issue but seeing that you're running ver 3 this clearly isn't only an iOS 4 problem. Hopefully somebody at Apple will catch this post and be able to provide an answer because I've had no luck trying to isolate the problem so far!!