Good tidbit of info, might explain some things. I make the assumption that it is actually the notification itself that is keeping the phone from sleeping and not simply that all led's are defaulted on. Correct?
I admit I'm confused by the report myself.
The phone is never dead, obviously - it can always receive an sms or a call.
Logic would suggest that the LED notification is sound asleep (there is such a thing as mode=sleep in any unix (read:Android)) and would therefore - logically - consume no resource until awoken.
And yet - someone at XDA who's studied it insists other.
If true, then there is some process that's not logical and is staying on whether notification(s) exist for signaling the LED or not.
Perhaps making the short answer to your question, yes.
Turn off all LED notifications.
In any case, I'm simply passing it on as unsubstantiated in hopes that it will help anyone with an always-on, battery-draining issue.
It goes back to the overall idea we had originally last week - that once clean, everything is dependent on checking the configuration and controlling it for best performance - not using tricks, using shared experience founded in what makes operational sense.
While writing this, I would also note that I just realized and remembered:
The configuration also automatically changes the display to auto-brightness. That's been shown in the past to be an automatic cpu-waster of no actual benefit to the user for our phones.
Turn off auto-brightness.
Another poster reported that his maps always launched and had cycles wasted on a background positioning attempt with an uncalibrated magnetic subsystem trying to act as compass.
I'd therefore also suggest maybe checking Maps to see if its running unintentially - either kill it or get the free Snaptic app called Compass and calibrate the magnetic sensor. (Personally, this last sounds out there - but at this point, I'm just trying to cover bases.)
Anyone with whtge8's problem should download perhaps SystemMonitor Lite, also free, Market and see if that sheds light on what process is really cpu-hogging. That app will also show a graph readout if a lot of network traffic is happening.
That's an especially bad sign if you think your all-quiet on the network.
There's also Android System Info by ElectricSheep, also free from the Market. Ironically, it's cpu-heavy - but - it will let you sort tasks by cpu or memory usage.
Either of those are infinitely better than looking at percentage of some overall process in the battery read-out.
A lot of people are convinced that Talk or Facebook isn't really running - one of the above tools might better tell the truth.
In whtge8's case, there's a runaway process that a factory reset didn't cure. Of the people suffering this, I'm only aware of two who were cured by a second reset. As his nerves are probably shot on this, I haven't pushed it, but for others, it's just a suggestion that I've hung out there.
We did have one case of a ##786# fix taking care of an uncontrolled handset. That accomplishes a factory reset and a reprovisioning and was done with a Sprint tech on the phone at the same time. Google shows that working for a few people just winging it - and sinking others who did it without benefit of tech support.
If you want to attempt that, I would recommend not calling Sprint - that takes hours.
Instead - mail a support form from your account at the online web site.
Your goal is to hit what we call Tier 3 support.
To do that in one shot, you have to be mega-succient, mega-polite and mega not-complaining.
Suggest as follows, reworded so it's not obviously boiler-plated:
"I have tried every normal good practice I can think of to manage my phone. I've performed a factory reset and still my phone dies quickly. I cannot even attempt to call support because something is eating the battery rapidly. I've read that some people are served with a ##786# reset but I would never attempt reaching into a service function on my own. How should I proceed?"
Paraphrase that, do not copy and paste. Do not tell them this is "reliable internet advice" - just state your case as succinctly and and as DISPASSIONATELY as possible.
At minimum, that approach saves you hours on-hold hoping for the best and at maximum it gets you something you never get by calling in:
A TRACKING NUMBER - it prevents you having to hear one thing from one tech and a second thing from another.
That's all I know how to advise on a runaway, battery-eating process at present. DO EXPECT them to ask you to run with nothing but stock apps.
If you hit Tier 3 - do NOT get clever, do NOT lie to them, do NOT pour your heart out over dissatifaction, do NOT exaggerate. Tier 3 support is always dead on - and it's always hard to come by. Mess with them and you'll get earmarked and they'll move on to some one they can help. The Tier 3 guys are often the ones missing meals with families trying to fix things. Be NICE.
Take that to the bank - it's how tiered support thinks and functions worldwide.
As to Pandora - we expected new codecs with 2.2 -
never would I expect a step backwards - but they did it.
Expect only chin-music on this from Sprint. Google screwed the pooch and Sprint has to take the calls. Maybe try for a billing concession for your trouble - but don't expect much. Sprint does not have a music service. In their mind they think you should be paying attention to Nascar or the NFL - and the last thing you want is to give them the idea that so many customers are so upset that in their next release, they should add some streaming bloatware on top of everything else.
I know this isn't much - but I really am trying my best to help.
Just because I'm not there right now - in no way implies that I haven't been there before and that I can't empathize with the plights.
