A) That doesn't work, if you read the rest of the thread you'd know why.
B) Why would I? 10.9.2 fixes the issues 100%.
I really hope 10.9.2 comes around quickly
this is really getting on my nerves
Interesting reading this. Since upgrading to mavericks on my MBP my battery has gone to s&*t. I upgraded to 10.9.2 today to see if it fixed it. Interestingly if I open activity monitor and then close the lid for a few minutes. Then open it. I see good old kernal_task at the top running at 100% + cpu. That doesn't sound very fixed to me
This change happened as soon as I did the upgrade to mavericks.
You can't measure the performance immediately after installing the new OS. It's got housekeeping chores to do. Let a day go by and it will be fine.
The battery percentage indicator started to count down like a timer after the upgrade(of course exaggerating, but say i get 1% drop every 30-45 secs or so), and this has been the case for the last 7 days since I did the upgrade.
You can find out which apps are using the most energy by checking under the battery icon in the menu bar. And Activity Monitor's energy tab will give you a more detailed picture.
That doesn't help either because I don't have any applications running, except the operating system itself.
However I checked the running processes, kernel seems to be the most active one, which makes sense. Nothing unusual.
Nothing has changed in the past week that I had Mavericks installed on my laptop. The impact on the battery life has been huge for me, and many others on this topic and on bunch of other forums out there.
The only way to avoid/fix this problem, is going back to the previous operating system, being Snow Leopard in my case. I had no such problems with it. Will wait for Apple to fix this issue with Mavericks before trying to upgrade, if they ever do of course...
Is the kernel reporting high CPU usage?
No, I don't have any applications reporting high cpu usage. All I can say kernel being the most active. No applications running. Fresh installation of the OS, fresh restart. I would think this to be normal, but I could be wrong.