My KE7 battery life is fine....
Since the first firmware I've had greatly varying battery lengths day-to-day. On my very first discharge to zero then full charge I got 21 hours of pretty heavy usage. Then, as I added more widgets and things that were syncing in the background I saw battery life drop. I have to say it has only once not lasted me until I got home.
Still, KE7 seems to be the best for me so far. After KE7 update I got a full day, around 12 hours on a charge with heavy usage (I could elaborate on usage but it would bore you and me alike).
Last night I did a factory reset and as I reinstalled apps and widgets etc I was consciously checking that I turned off unnecessary syncing on apps that don't need it.
Today, after around an hours of unplugging I saw it had dropped to 97% and wifisharing was around 30% at 13 minutes. I used the 'Force Stop' function to freeze it and since then it stopped gaining time and it's % decreased accordingly.
Later in the day I saw it had started again and was at 14 minutes so I force stopped it again. Thing is, I didn't do anything that used wifi, let alone wifi sharing....
Still as you can see in my screenshots after nearly 13 hours I'm still on 29% battery. I plugged it in for about 3 minutes to get some photos off, which accounts for the small blip at the end.
At the end of the day I think we are all going to have different battery experiences depending on the apps we have installed, the sync frequencies, how many email accounts we have syncing, the launcher we use (I notice my battery life got MUCH better when I started using Launcher Pro Plus...) and any number of factors.
While I would never discourage discussions about battery life, I would encourage everyone to keep it in perspective and understand that just because they get **** battery life after an update, it doesn't mean that firmware is buggy. It might be something else.
Having said all that, I seriously hope they get to the bottom of the wifi-sharing issue that has been endemic since release of this phone, and the Android OS issue which I believe is actually a symptom of a bug in 2.3.3 and has been reported as fixed in 2.3.4 for Nexus S and Nexus One users.
COME ON SAMMY! BRING ON 2.3.4!!!