i use the charger that comes with the phone and when i plug it into anything but the one outlet that works...which is actually an extension cord everything is fine. but when i plug it into my computer or any other outlet in my house it connects and starts charging and then after a min or less it disconnects and tells me to plug it into a charger.
based on some additional research and some advice from xda forums, the battery burn seems to have something in particular to do with sd card usage in lollipop, or especially having installed some apps to the sd card (which I have in kitkat).. I wonder if the folks who report having no issues are NOT using sd cards? I tried moving the apps back to the main device, but it seems like it still uses some aspect of the sd card for now and thus I remain still having excess battery usage unless I attempt to factory reset (which I am still refraining from, as that is not really clear whether it will 100% improve the problem anyhow). I will attempt to experiment with safe mode for an extended period and see if there's any improvement (although it doesn't seem really a fair test since most of my apps will not be available in that mode).
I have a micro sd card but do not put apps on it, only pictures and music.
My battery today with moderate usage has used 17% in just over 7 hours.
Haven't really disabled anything or done anything out of the ordinary like I used to have to do on my S4 just to make it through a day.
Just curious (if you are running Gsam at least, since built in battery usage doesn't show you everything) if you see unified daemon using much battery, mine only shows 4s of cpu and 0.1% but I have seen elsewhere that that process was killing other samsung devices (S5 for instance) but a few chimed in with older Note models with the same report.
Update - I tried removing the sd card for a few days, but it made no noticeable difference in battery usage performance. Overall battery usage is still noticeably worse than KitKat. Based on all the reports about poor S6 battery life, I suspect it is just a Lollipop issue in general!
It isn't globally an issue though, I know of many including my own that have upgraded to Lollipop and have had no issues after the first few days in fact mine has improved in battery life since Lollipop. Have you tried running it in safe mode for a while to see how the battery does? If in safe mode it operates significantly better then there is an app that isn't Lollipop happy.
testing in safe mode for a couple of hours
- battery usage is somewhat better, but not dramatically so
- safe mode isn't very useful (as most apps aren't available), nor safe (as some non-internal apps come up anyhow via notification - can't access them directly from the home screen, but can bring them to the front by clicking the notification and then switch back via the app switcher)
- most apps aren't running, so it's not really a very interesting test anyhow. the main point still being that we never had any battery issues under kitkat even with all apps running.
It is an interesting test because running in safe mode proves that it isn't lollipop directly it is an application that is causing the problem, usually when this happens especially when it is only select phones it comes down to an application that isn't behaving correctly under lollipop, an app that you are using that others aren't using.
Also apps being up to date doesn't matter if the app maker(s) haven't updated the apps for lollipop, sometimes it takes days, weeks or even months for that to happen.