help pls, i hv updated to version 3.0 since 18/6 & was running smoothly. since yest i realize my batt drain very quickly, it is also a bit sluggish while using it. this morning when i charge the batt & after 3 hrs of charging, it was only half full so i decided to do backup restoration. as the restoration was in process the the battery level drop drastically at the same time. now after i hv fully restored and reboot my iphone, the battery level is down at critical level. As anyone encounter similar issue... pls help, tq

well... i must say mine is a little different case, i think 2 days ago when i hv downloaded few software's updates, all of a sudden the batt drain unusually fast. Same time I hv prob charging the batt, for half a day I only managed to charge a quarter of the batt indicator however, some thing strange when I removed the SIM card, it charge normally but when I insert back my SIM the batt drain quickly again. As I have to work, I don't have much time to diagnose without the sim & see if it drain the same rate as wit the sim inserted. sigh... I wanted to do a reset of all contents but notice it takes more then 2 hrs to do it, i decided to skip that for now (no time)

I'm actually currently in china since 17/6 & i'm using china mobile sim on my iphone whn i'm here but still it doesn't add up cuz it was running without prob, all these happen 2 days ago. I'm on maxis plan, bought it when it launch. I tried using maxis sim just now & its the same batt drain fast. i'm erasing all content now & see what happen... will update with u guys....

... I have finished erasing all content & installing all data & software's back into place. tested playing with games for awhile & so far so good, batt remain at full... also tried switching between both msia & china SIM cards, works fine.
now i pray it stays that way... thanks a lot guys

sigh... my battery is still draining abnormally fast & worst I have problem charging my phone. It doesn't charge normally without removing my sim card... by googling around i notice indeed thr r a number of similar cases. hope apple will address this issue soon...