Related
Hi ,
yesterday night i dint plug my phone to charging because my battery was above 70 % so i thought its more than enough for next day but i woke up in noon and saw that my phone was on 11% so took a screenshot thought that posting it here might help me
thnx in advance
Try disabling Google now I heard that its a major battery drain to our crespo
Sent from my Crespo using xda premium
You need to describe your device configuration. Phonetype, Firmware, ....
Time for a clean install.
Sent from my Nexus S
nexususer said:
Hi ,
yesterday night i dint plug my phone to charging because my battery was above 70 % so i thought its more than enough for next day but i woke up in noon and saw that my phone was on 11% so took a screenshot thought that posting it here might help me
thnx in advance
Click to expand...
Click to collapse
Try Installing soju factory image from google. I did a clean install wiping dalvic chache as well and my battery is awsome since then and I never disable google now. See in the attached screenshot how flat battery consumption curve when I am not using it.
alien_x said:
Try Installing soju factory image from google. I did a clean install wiping dalvic chache as well and my battery is awsome since then and I never disable anything.
Click to expand...
Click to collapse
I did the samething after getting terrible battery life due to an AudioOut_2 wakelock that never let my phone idle, and the same thing still happens. I'm wondering if a hardware malfunction could cause screwy behavior like this.
Just do "proper clean install", it should help.
Agree with clean install. ROM and kernel choice have a lot to do with battery drain also.
Was this a one time thing or the norm for your phone? If a one time thing wouldn't worry too much but would still shop for ROMs and do a clean install.
I have started using Juice Defender and LUX and my battery life has increased exponentially its features should help any ROM kernel combo.
Sent from my Nexus S 4G
i had a problem with android os sucking the life out of my battery, all was ok for about a week after i installed jb but then my battery life sucked. rather than do a clean instal i turned off auto sync for a couple of days then switched it back on again, since then my battery life has been good and android os has hardly used up any battery. might be worth while trying this first
Yeah. Full wipe is a last resort. At least if you figure out what actually caused it, you can prevent it from happening. I remember my Nexus S had this weird bug where if I put the phone in air plan mode and didn't disable auto sync, the phone would never properly sleep. Never had that issue on any other phone.
Its sometimes ROM related....codename ROM I get high android is but not with androxide
Sent from my Nexus S using Tapatalk 2
alien_x said:
Try Installing soju factory image from google. I did a clean install wiping dalvic chache as well and my battery is awsome since then and I never disable google now. See in the attached screenshot how flat battery consumption curve when I am not using it.
Click to expand...
Click to collapse
You have network disabled... Off course it does not drain!
I cannot tell much about your device setup since not all the details were given, But even my Sprint Nexus S 4G had horrible battery issues. The stock gingerbread was a joke, then the stock ICS did improve to do a couple more hours. Now running an rooted JB and it seems to do 1day and 3 hours at this time.
alien_x said:
Try Installing soju factory image from google. I did a clean install wiping dalvic chache as well and my battery is awsome since then and I never disable google now. See in the attached screenshot how flat battery consumption curve when I am not using it.
Click to expand...
Click to collapse
i am using international nexus s superamoled version and my model number is i9010T so i cannot install soju i have to install sojua and i m on jelly bean right now
One Power Guard can help the system into a deep sleep,Reduce battery drain
downloaded from http://forum.xda-developers.com/showthread.php?t=1889740
One Power Guard, an AMAZING product, saves energy for your Android device under the all circumstances. It greatly enhances device performance, improves battery, and powers up standby time and battery life by optimizing system kernel and cpu, avoid phone overheating, shutting down useless programs, preventing from energy-consuming apps, initiating deep-sleep mode, adjusting Wifi parameters, optimizing charging parameters and pacing up setting change , etc.
Google Now
Turning off Google now is what fixed the battery drain for me. Tried other things but only this worked.
My i9020T was working fine using the stock 4.1 firmware. I started playing around with a few custom ROMs (all designed for my phone) with varying results. I eventually got to a point where every ROM I tried resulted in a phone that restarted suddenly several times a day and drained the battery quickly. I thought maybe that restoring apps using Titanium when going back and forth between 4.1 and 4.2 based ROMs might be the problem, so I wiped everything and did a system reset, then installed CM 10.1 and the Gapps and a handful of crucial apps that I downloaded fresh from the Play Store. The random resets seem to have disappeared but I am still having strange battery life issues. The battery seems to discharge at about the same rate as with the stock ROM until it gets to around 40%, then suddenly dies with no warning. It can only be restarted by plugging it into the charger, at which point it shows a 0% charge. It seems to charge back up to the 40%-50% mark extremely quickly, then gets to full charge at normal speed. I tried switching to my seldom-used backup battery, with the same results. I also tried reinstalling CM 10.1 and Gapps, along with the Marmite kernel, and got the same results but with a slightly longer period of time before it dies. Anyone have any ideas?
This happened to me once, not like your case, but I fix it with a app witch one I don't remember the name. What I know is that app just delete the battery.stat soo android generate a new one. Try to search on play store.
Buscador said:
My i9020T was working fine using the stock 4.1 firmware. I started playing around with a few custom ROMs (all designed for my phone) with varying results. I eventually got to a point where every ROM I tried resulted in a phone that restarted suddenly several times a day and drained the battery quickly. I thought maybe that restoring apps using Titanium when going back and forth between 4.1 and 4.2 based ROMs might be the problem, so I wiped everything and did a system reset, then installed CM 10.1 and the Gapps and a handful of crucial apps that I downloaded fresh from the Play Store. The random resets seem to have disappeared but I am still having strange battery life issues. The battery seems to discharge at about the same rate as with the stock ROM until it gets to around 40%, then suddenly dies with no warning. It can only be restarted by plugging it into the charger, at which point it shows a 0% charge. It seems to charge back up to the 40%-50% mark extremely quickly, then gets to full charge at normal speed. I tried switching to my seldom-used backup battery, with the same results. I also tried reinstalling CM 10.1 and Gapps, along with the Marmite kernel, and got the same results but with a slightly longer period of time before it dies. Anyone have any ideas?
Click to expand...
Click to collapse
samcortez said:
This happened to me once, not like your case, but I fix it with a app witch one I don't remember the name. What I know is that app just delete the battery.stat soo android generate a new one. Try to search on play store.
Click to expand...
Click to collapse
App name is battery calibration and here is the link for it https://play.google.com/store/apps/details?id=com.nema.batterycalibration
Hope it works :thumbup: good luck
Sent from my Nexus S using xda app-developers app
Thanks for the replies. The Battery Calibration app seemed like it had pretty much done the job the first day after I ran it--the battery lasted the whole day and made it down to about 10% before it suddenly died. However, on the second day (today) it went right back to the old behavior, dying in mid-afternoon shortly after the battery charge dropped below 40%. Any other ideas?
Howdy folks. I have a major problem with my t769, and was hoping someone could help me figure it out. This problem began quite some time ago and has gotten worse. My battery stopped accepting a full charge (according to the meter.)
I had been running PA (racing port) for quite a while without a problem. The problem may have cropped up due to charging the phone while off at some point. When the problem first appeared, it would only charge up to 98%. I chalked it up to the fact that some phones apparantly don't trickle charge (for battery longevity?). Then the phone would only get to ~90%, then 83%... etc.
I have tried all three kernels available to us, nothing changes. Tried several different basebands. Tried reinstalling PA, no dice. Tried changing roms. Currently on Provision rom. The battery will not charge beyond 48 percent.
My issue does not appear to be a faulty battery; I recently purchased a couple new batteries and they do the same thing. Even after charging with an external charger - the phone still misreports the battery capacity. This has the effect of reaching a battery level of 0% (according to the meter) long before the actual battery capacity is exhausted. Further to that end, the android battery stats are never automatically wiped since the phone's battery meter never actually reaches 100%. The android battery stats page currently shows 4days on battery. I suppose this is because I last manually wiped the battery stats or pulled the battery 4 days ago.
Some more odd tidbits...
When the phone's battery meter reports 0%, the phone will automatically shut off ONLY if the display is ON. If the phone reaches the 0% mark while the display is OFF, it will continue to run and sometimes readjust the battery meter in 4-5% increments. i.e. if I turn off the screen when it hits 1%, and turn back on the screen some time later and the meter will report 4%. Other times it seems it will not readjust the meter while the screen is off and will remain at 1%. When the phone reports 1%, the battery is still outputting at least 3.5v. From what I understand, most 3.7v lithium ion batteries have an approximate safe operating range of between 3.2v-4.2v.
Really odd:
It seems that once the battery is pulled, the meter will revert to 0% once the phone is booted regardless of what the meter showed before the battery pull. I have not done this in the last couple days but it has happened several times and appears to be a repeatable issue.
All of my problems could logically be caused by a battery miscalibration, save the last point.
I have tried several calibration apps in the market that don't seem to do anything. I recently stumbled on this huge thread:
http://forum.xda-developers.com/showthread.php?t=765609
I have not read through all 200+ pages but it seems this has worked for many people. Unfortunately, I've been unable to get it to report values with the lightningX2 or CM10 kernels though. It states that the CM kernel should be supported, so I don't understand why it doesn't want to spit out values.
Any help would be greatly appreciated. I've grown quite attached to this phone and would like to continue using it!
Charge your phone overnight. Reboot to recovery (leave the phone plugged in). In cwm navigate to the advanced menu. Then in that menu wipe battery stats. Then let your battery drain down as much as possible before charging it again.
That should fix it.
Sent from my SGH-T769 using xda app-developers app
Many thanks for the reply. I'm currently using TWRP and I dont believe there is a section to wipe the battery stats.
I have removed the batterystats bin manually once android has booted both when the battery is in a near-dead state and in a near-full state and neither seemed to change the meter level. Perhaps I will see a different result by removing this file through recovery before Android boots?
I may install CWM to give this a shot soon but from what I understand, and please correct me if I am mistaken, the removal of this file has no bearing on the actual battery calibration. It was said that this file only affects what is displayed in the android battery stats page. There does appear to be a lot of confusion and controversy across the forums regarding whether or not this file is indeed responsible for actual calibration between true battery capacity and the state of the battery meter.
Not sure if this is important but when charging the phone (while turned off) the bootloader charging animation seems to report a value that is consistant with what the booted meter reports. (i.e. the animation will show ~50% battery left when the meter inside android will report 48%)
anactoraaron said:
Charge your phone overnight. Reboot to recovery (leave the phone plugged in). In cwm navigate to the advanced menu. Then in that menu wipe battery stats. Then let your battery drain down as much as possible before charging it again.
That should fix it.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
kmem said:
Many thanks for the reply. I'm currently using TWRP and I dont believe there is a section to wipe the battery stats.
I have removed the batterystats bin manually once android has booted both when the battery is in a near-dead state and in a near-full state and neither seemed to change the meter level. Perhaps I will see a different result by removing this file through recovery before Android boots?
I may install CWM to give this a shot soon but from what I understand, and please correct me if I am mistaken, the removal of this file has no bearing on the actual battery calibration. It was said that this file only affects what is displayed in the android battery stats page. There does appear to be a lot of confusion and controversy across the forums regarding whether or not this file is indeed responsible for actual calibration between true battery capacity and the state of the battery meter.
Not sure if this is important but when charging the phone (while turned off) the bootloader charging animation seems to report a value that is consistant with what the booted meter reports. (i.e. the animation will show ~50% battery left when the meter inside android will report 48%)
Click to expand...
Click to collapse
Just out of curiosity, does this happen across all roms? Does it do it for stock as well? Maybe return to stock and check? I gave up on TWRP not because I didn't like the recovery, but it seemed to be... off... somehow... The 2.4 wouldn't restore backups (and would randomly reboot), and the 2.3.3 wouldn't reboot when plugged in (it would just power off). I also had some issues with my sd card with one of them (2.3.3 I think but not sure) on one of the JB roms and I lost all of my data. After going back to CWM 5.5.0.4 I haven't had any issues.
Both TWRP versions are built on the default CM10 kernel (correct me if I'm wrong here). I went back to stock about 2 weeks ago and am getting 4-5 days on battery life (light usage) where on ANY JB kernel the most I could get was a day and a half. Perhaps there's something missing/wrong with the JB kernel, and as such, TWRP isn't working properly because of it.
Perhaps the battery isn't getting read properly... have you tried cleaning the contacts with iso alcohol?
Sorry I couldn't be more help...:crying:
It happens for the two JB roms I have tried. I've not tried to return to stock yet but if you are getting 4-5 days of light usage that is incentive enough for me to give it a whirl! I never was able to squeeze more than about a day and a half out of a JB rom on my blaze either, even before these battery problems cropped up. I started using TWRP on my last phone mainly due to the fact that it can compress the backups but I've also become more accustomed it's UI. I think I'm currently using 2.4, but I vaguely remember both the SD issue and the power off instead of reboot issue you describe with the previous rev.
I can't speak to if the recoveries are built from CM. Now that you mention it, both JB roms that I have tried on the blaze show higher than normal battery usage by media and android system processes. Are you running a complete stock ICS or GB rom, or is it some debloated one? Can you tell me which one it is?
I've cleaned both the internal battery connector and micro usb connector to no avail. You have been a great deal of help, thanks again!
One other quick Q... After returning to stock, do you still have the black and white colored (powered off) charge animation? Ever since I rooted this thing, the power off charge animation starts up with the stock color (green filled battery) but quick flashes off and changes to the black and white one. Perhaps this is part of my problem, remanants of the stock bootloader mixed with the rooted one?
anactoraaron said:
Just out of curiosity, does this happen across all roms? Does it do it for stock as well? Maybe return to stock and check? I gave up on TWRP not because I didn't like the recovery, but it seemed to be... off... somehow... The 2.4 wouldn't restore backups (and would randomly reboot), and the 2.3.3 wouldn't reboot when plugged in (it would just power off). I also had some issues with my sd card with one of them (2.3.3 I think but not sure) on one of the JB roms and I lost all of my data. After going back to CWM 5.5.0.4 I haven't had any issues.
Both TWRP versions are built on the default CM10 kernel (correct me if I'm wrong here). I went back to stock about 2 weeks ago and am getting 4-5 days on battery life (light usage) where on ANY JB kernel the most I could get was a day and a half. Perhaps there's something missing/wrong with the JB kernel, and as such, TWRP isn't working properly because of it.
Perhaps the battery isn't getting read properly... have you tried cleaning the contacts with iso alcohol?
Sorry I couldn't be more help...:crying:
Click to expand...
Click to collapse
kmem said:
It happens for the two JB roms I have tried. I've not tried to return to stock yet but if you are getting 4-5 days of light usage that is incentive enough for me to give it a whirl! I never was able to squeeze more than about a day and a half out of a JB rom on my blaze either, even before these battery problems cropped up. I started using TWRP on my last phone mainly due to the fact that it can compress the backups but I've also become more accustomed it's UI. I think I'm currently using 2.4, but I vaguely remember both the SD issue and the power off instead of reboot issue you describe with the previous rev.
I can't speak to if the recoveries are built from CM. Now that you mention it, both JB roms that I have tried on the blaze show higher than normal battery usage by media and android system processes. Are you running a complete stock ICS or GB rom, or is it some debloated one? Can you tell me which one it is?
I've cleaned both the internal battery connector and micro usb connector to no avail. You have been a great deal of help, thanks again!
One other quick Q... After returning to stock, do you still have the black and white colored (powered off) charge animation? Ever since I rooted this thing, the power off charge animation starts up with the stock color (green filled battery) but quick flashes off and changes to the black and white one. Perhaps this is part of my problem, remanants of the stock bootloader mixed with the rooted one?
Click to expand...
Click to collapse
I'm running stock rooted uvmb1 (ics), which I've debloated and customized a bit (nothing special). Stock roms have the stock battery charging animation.
The battery drain is just one of those things I can't fully explain, as I have a few other devices running CM10 or 10.1 and they have great standby/light usage battery life
I am running mokee open source 4.4.2 roms and am constantly having trouble with battery.
It shows vague levels...i charge it from 10% onwards...and it gradually goes to 60% or so and then suddenly jumps to 100% showing battery is full.
The recovery sometimes shows the original level as 60%..but rom shows 100%.
Then the rom discharges at 1% per 2 minutes or so and i just cant get any backup as in reality it never gets fully charged. :-/
I have tried callibrating it after numerous factory resets via various playstore battery callibration apps.
I have wiped the system everytime i have flashed a rom.
I have tried discharging it and then charging it while ita off.
I have tried bump charging.
Still it gives 7-8 hours backup while people get 3-5 days of backup on idle mode.
On idle mode even..my tab loses 10-12% in 2-3 hours.
Tab is 7 months old so i think battery doesnt needs to be replaced or any hardware issue.
Can anyone...anyone please help me..?
Please Suggest any method other than the ones i have tried.
Thanks
Edit:
I have even tried Greenify to check the background apps..but in reality the battery goes down on even very light use such as messaging or checkin xda updates.
Anyone..?
This meight help if you are on P51XX : http://forum.xda-developers.com/showpost.php?p=50677996&postcount=788
Else:
Got into advanced wifi-settings and disable wifi to be on all the time, also disable networknotification if you don't need them.
Thanks but i have a P3100.
I have already disabled wifi when sleeping.
Running powersave and noop on 300-1008 mhz.
raamishmk said:
I am running mokee open source 4.4.2 roms and am constantly having trouble with battery.
It shows vague levels...i charge it from 10% onwards...and it gradually goes to 60% or so and then suddenly jumps to 100% showing battery is full.
The recovery sometimes shows the original level as 60%..but rom shows 100%.
Then the rom discharges at 1% per 2 minutes or so and i just cant get any backup as in reality it never gets fully charged. :-/
I have tried callibrating it after numerous factory resets via various playstore battery callibration apps.
I have wiped the system everytime i have flashed a rom.
I have tried discharging it and then charging it while ita off.
I have tried bump charging.
Still it gives 7-8 hours backup while people get 3-5 days of backup on idle mode.
On idle mode even..my tab loses 10-12% in 2-3 hours.
Tab is 7 months old so i think battery doesnt needs to be replaced or any hardware issue.
Can anyone...anyone please help me..?
Please Suggest any method other than the ones i have tried.
Thanks
Click to expand...
Click to collapse
Try flashing new kernel for your device.
Did you overclock the processor?
I once extended the preload with the help of a kernel., and when I restarted, cwm was unable to mount preload.
so I resetted the default settings of the kernel tweak app and den everything went fine like before.
Thanks for the reply.
I had once tried agni PureCM any rom kernel and i think that the issue was gone but i dont remember exactly and moreover i want to remain on stock mokee to get OTA.
People are gettin 3-5 days backup on stock.
I am running stock 300-1008 mhz on powersave and noop.
Also i just wiped preload once..could that be an issue.?
And wouldn't formattin the whole device and flashing the rom from scratch would reset the kernel settings to default..?
Here's a logcat if its of any use.
https://www.dropbox.com/s/ai1yxarc89frj0n/logcat.2014-03-03-08-16-39+0530.txt
raamishmk said:
Thanks for the reply.
I had once tried agni PureCM any rom kernel and i think that the issue was gone but i dont remember exactly and moreover i want to remain on stock mokee to get OTA.
People are gettin 3-5 days backup on stock.
I am running stock 300-1008 mhz on powersave and noop.
Also i just wiped preload once..could that be an issue.?
And wouldn't formattin the whole device and flashing the rom from scratch would reset the kernel settings to default..?
Here's a logcat if its of any use.
https://www.dropbox.com/s/ai1yxarc89frj0n/logcat.2014-03-03-08-16-39+0530.txt
Click to expand...
Click to collapse
I don't think wiping the preload will cause a battery issue.
Yes formatting the whole device should reset the kernel to its default settings.
Are you sure it is not a hardware problem?
Try to check it on any other similar device if you have.
Okay mate.
So i dont have any other tab 2...but my bro has it and he doesnt has this issue as far as i know.
But even i didnt have this issue until 2-3 weeks.
The only real culprit i can think is it might be the cable.
As yesterday pc gave me a code 43 error and i could not connect the tab howsoever i tried.
On 4.4.2 mokee..what should i do with such stats..?
Running greenify...and wifi sleep is enabled..completely formatted the tab and still this issue.
Since battery didnt dropped while it was on sleep..i dont think there is any hardware problem.
Any idea mates..?
@raamishmk same happens with mobile data turned off? can you tell me when it started?
Mobile data is always turned off mate..that stat is for sim network only.
And it started almost 3-4 weeks ago.
Also..i bought a new factory cable and the issue remains..so the faulty cable was not an issue.
Tab is 8 months old now..maybe the battery has possibly died..?
It's a battery issue.. Happen with me as well.. Replace ur battery under Warranty otherwise it will cost u 1600 INR rupees..
Sent from my GT-P3100 using Tapatalk
Well warranty is of 1 year so i can..
Thanks.
Does anyone else have the issue where android system is consuming 35+% of the battery? Looking at the stats it seems like one of the bundled services is keeping the radio on for 14/18hrs its been on.
Have the same isssue
Yeah, I'm having this issue too. Android System is consuming HUGE amounts of battery for me.
Thought I was the only one but glad that's not true! Still got good battery stats with the android system drain nonetheless.
Charged mine to full last night right before hitting the sack.
Woke up 7½ hours later and it had consumed 33% of the battery just sitting doing nothing bar getting email & polling (presumably) for Facebook updates.
And that was with Power Saving enabled. Bit disappointing, hoping when I disable auto-sync that it'll kill the drain.
There's lots of services running under Android Systems disable the ones u don't use, I have disabled some got better battery life, still testing some others...
The hardware on the phone is great, but touchwhiz drives me up the wall. I'll be happy if and when we get anything AOSP based, CM being the holy grail. Nice to know I'm not the only one getting this battery drain. I've disabled pretty much everything that's able to be disabled, as all I use is google services.
Same problem here.... Huge Android System battery drains.
I've played around with several things, and as of yet I haven't gotten it to stop other than turning off WiFi. Anyone found a fix?
Mine's more a combo of Android System and Google Services... both take up a majority of my usage... Services typically being a bit more.
Why are there two android systems? wtf...
Is there any way to reduce cell standby?
polaric said:
Does anyone else have the issue where android system is consuming 35+% of the battery? Looking at the stats it seems like one of the bundled services is keeping the radio on for 14/18hrs its been on.
Click to expand...
Click to collapse
Same sh*t here. Went to bed last night fully charged, and 7-8 hours later, wake up with 23% of my battery gone.
I'm starting to wonder if moving away from the Nexus line was a mistake. I started running again and the N6 was just too big to lug along with me, on arm or in a waste band, so I decided to try Samsung.
Just got my S6 and I noticed this right away. Last charge I had 2:42 of SOT and "Android Systems" used 47% of the battery. I was just watching Netflix and YouTube mostly. My overnight drain is also quite high, about 1% every 30-40 minutes of standby.
Is that normal for most S6 owners?
To all:
Turn off VoLTE, turn off WiFi calling, install CPU Spy, ensure your phone is going into deep sleep. If it isn't, flash the stock recovery with Flashify, wipe the cache with it, then flash TWRP back with Flashify.
Post your results.
Paradoxumical said:
To all:
Turn off VoLTE, turn off WiFi calling, install CPU Spy, ensure your phone is going into deep sleep. If it isn't, flash the stock recovery with Flashify, wipe the cache with it, then flash TWRP back with Flashify.
Post your results.
Click to expand...
Click to collapse
Is this only for people who already flashed TWRP? I'm stock rooted and seeing this.
km8j said:
Is this only for people who already flashed TWRP? I'm stock rooted and seeing this.
Click to expand...
Click to collapse
This is for everyone. If you haven't flash TWRP, then simply wipe the cache with stock recovery.
I just assumed most people would have TWRP flashed, my bad.
I am guessing that that this is an Android problem as the Galaxy S6 Edge has the same problem with battery drains.
Paradoxumical said:
To all:
Turn off VoLTE, turn off WiFi calling, install CPU Spy, ensure your phone is going into deep sleep. If it isn't, flash the stock recovery with Flashify, wipe the cache with it, then flash TWRP back with Flashify.
Post your results.
Click to expand...
Click to collapse
I'm not rooted and I don't plan on doing so. I'm not sure of any other options. I unplugged it last night an let it sleep. Android system used about 14% of the battery. And I lost 20% charge. Cpu run time was 38 minutes too. and I never even woke it up post unplugging it.
I believe this Battery Drain Issue is a Lollipop issue. Was haing it with my One Plus One, I fixed it by going into privacy Guard, and going to Google Play Services and not allowing it to stay awake, and start by itself.
Ill find the actual thread and post it, same issues happening with a lot of phones using lollipop
Battery drain on a new device = bad flash (very common on android devices, first run)
1 wipe the devices and start it again from factory problem should go away. (at least the excessive drain anyway)
2 Ensure you have updated the Samsung Services app (this was responsible for most if not all battery drain issues if you reset your device)
3. Turn the bloody Screen brightness down and turn off Adaptive display (way way way too much battery drain using them)
4. LTE off and Cell data off if you on wifi, your wasting battery power communicating with cell sites you arnt using, the weaker the signal the more power you will drain for no benefit
6. GPS / Loc data off unless you need it even then wifi / AGPS is usually more than accurate, remember GPS + poor sky visibility = more power used to get a loc.
5 NEVER measure battery life for the first 24 hours way too much stuff syncing and updating to measure with any accuracy.
I get a solid 2 days out of the S6 with mixed use and a screen on time of 2:30 could get that upto 3 hours but i have a hearthstone addiction
As mentioned above, I highly recommend wiping the cache, even when not rooted.
Also, worst comes to worse, i'd completely redo the phone from scratch via the Smart Switch software samsung provide.