The initial drop from 100, especially when browsing is normal...continue to monitor that after the drop to 90....should slow after that.
Did you take it off of charger, then start browsing?
What kernel are you using? I think you were/are on MikG??? If I remember correctly.

 

I have noticed the same on my phone, however after the initial drop off I have noticed the battery will climb back up maybe to 93 -94. Haven't really tracked it religiously but will pay attention to it going forward.

 

Again, if I remember correctly, you just flashed that kernel.
Let it settle in a couple more days before you condone or condemn it.
If its the sbc variety, and if it is similar to the Mason sbc kernel I run,
sbc will kick in about and hour or 2 after fully charged.
Then, when you take it off of charger, it will stay at 100% longer than a non sbc kernel would have it....follow?

 

You wiped cache and dalvik cache prior to flashing right?

 

Probably, did you flash the sbc version?

@G2435
Ditto Rx's question

 

I think you flashed the sbc nohavs version cuz that's the one I suggested.
Just let it run a couple days.
After a couple days do this.
Put on charger all night.
Wake up, rub sleepys out of eyes.
Go potty, brush teeth. Grab phone. Say hi to phone.
Unplug phone...should be at 100% battery.
Surf the internet for 5 minutes like you did before.
See how battery drains.

 

We are guides, not mods. But thats no biggie. I think it was Mikestoney that first mentioned that to you


Kernels take a few days to settle in. Your phone needs to reboot a few times and go through a few battery drains and charges in order for it to report the correct battery level. We call this "settling in"

You can use whatever scheduler you want. Honestly I'm a little rusty as to the difference and what is "better", but they all seem to work.

What I'm saying is Deadline is just fine.


Edit:

I merged this with your battery issues thread as it seems to be a continuation of what is said there. Its got a little of your SetCPU thread in it as well but we will keep it here

 

@g4235
o.k...so here are my thoughts about battery/kernels/roms etc.....
And bear in mind, I'm not a great writer and my thoughts kinda jump around.
If you have time to read, then click "show"
Again, these are just my thoughts...

Spoiler

Everyones phone reacts differently. You may ask, "How the fun can that be?" Trust me they are. My boss and I got our phones at the exact same time, same O.S., same version, same hboot, same everything yet they react differently to different roms and kernels. Don't ask me why but from what I have read on many forums/posts, that's the way it is and I/you/everyone just has to accept that.
So, my kernel and how I set governers/schedulers/cpu speeds/under/overclock WILL not be the same as my boss's phone.
As far as your battery savings, it boils down to our Evo's are not known for thier battery life...in short it sucks.
That's why great developers of roms and kernels have been extremely helpful in their efforts to help this issue.
That being said, and what Rx has stated, leave your kernel settle in for 3 or 4 days before saying, "well this sucks!"
I have only been at this whole rooting thing for only 8 months...I, by no means know everything and I am still learning. My phone hates being undervolted by very much...I've learned that. I find that the interactivex governer works well with my phone with no profiles set.
I believe it was one of Mizzou's posts that had statement about what affected battery life such as signal strength....if your phone is constantly searching for signal, guess what? Your battery life will suck.
Also, screen brightness, wakelocks, internet surfing, game playing, screen on time, music playing, gps/map usage, and some others I cannot think of at the moment.
I have used Juice Defender quite successfully to save battery..(found in the play store)...Some people say, "That app will not help"...well, it does for me.
I also use Battery Monitor Widget app to monitor my battery usage. Also found in play store.
Schelulers? I use deadline or noop. But again, that works for me.
Wakelocks---from my understanding, its when an app or process that doesn't get killed and runs in the background, sucking battery....I use Better Battery Stats to keep an eye on that. See this
Task killers....don't use them....Android does a great job of doing that itself.
I usually get 17+ hours of battery use. I dont surf the internet, I dont play music, I dont play games at all. My phone sits on my desk all day with very little usage because I am a mechanic. I'm dealing with vehicles and customers all day....my phone sleeps alot and probably dreams of being used more...yes, my phone is overkill for me but ya know what? I love playing with it in my spare time.

I know this is a long rant type story but I thought I'd share it. I have 45 minutes of driving to work one way to think about stuff like this. lol

Take it slow, read, and asking questions like you do is great! Thats how I learned and many others have learned. I didn't go to an Android school, I know a little about computers (very little), and you look at me and think, "what the fun does he know about android?" Well, some, but not as much as the people here at AF--
Rx, ocn, argedion, granite, mizzou, and alot more I am missing, and I have learned alot from these people.

So ends my little story as I have to start work now...........

 

The number one thing that's going to eat your battery is the screen. It takes a lot of juice to power that thing, and it takes even more juice when you have auto brightness turned on.

If you are indoors, manually slide the brightness as far down as it'll go and you can still see the screen. You can do this by going into settings, display, brightness. There should also be a setting for this in your quick settings pull down menu in mikg. I only have auto brightness on when I am outdoors.

If you have wifi at home, work, or school connect to it as often as you can. Wifi helps conceive battery tremendously.

Check your sync settings. Do you really need your emails as soon as you receive them? If not, you can save battery by syncing every 15 minutes, half hour, hour, 4 hours, day ect.

Go into Google Talk and sign out if you don't use it. Go into settings and Uncheck autostart. Better yet un install it if you don't use it.

Signal issues Mike talked about, so I think that about covers it

 

Tiamat is an AOSP kernel, it will not work.

 

If you want to try an AOSP ROM, you'll want decks reloaded and the mason kernel

 

Make a nandroid before flashing anything. That way if you dont like it its like you never tried anything else after you restore it.

You can always download the app called wireless tether for root users and use it as a hotspot. I've mentioned before you probably shouldnt use your hotspot with the ps3

Tiamat kernel had a great run, but its no longer the best AOSP kernel. Mason is the aosp king