yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] styles420:
Lowering the brightness can have a huge impact - try turning off auto and keeping it as low as you can (just turn it up a bit in bright environments like sunlight).

That's all I can think of at the moment. I don't know if there is much more that can help - the fact is that the screen will always be one of the biggest drains, even with the most efficient settings. But you might be surprised at how much of an impact lowering the brightness can have - hopefully that helps

Edit: it seems someone else types faster than I do, lol
[Sprint Samsung Galaxy S III] daniel4653:
I had something interesting happen I left my phone unplugged overnight . I fell asleep around 2 am and woke up at 6:30 am for some reason and I look at my phone and battery dropped from 48% to 2%. Idk what happen. In was to out of it to look at better battery stats that early in the morning.
[Sprint Samsung Galaxy S III] prboy1969:
Sounds like a Wakelock. Used to have that happen with FB on the Wife's OG EVO, after a new Rom was loaded.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] daniel4653:
Yeah but I haven't change anything since two days ago and this didn't happen the night before. I've been running the same Ron for over a week
[Sprint Samsung Galaxy S III] mcluvin1065:
yea i never have auto brightness on and i always have it at the dimmest...i even have super dimmer to lower it...its usually drops like 1 percent every 5 min.....
[Sprint Samsung Galaxy S III] styles420:
Then I will watch for any advice offered by others - your drain from the screen seems better than mine, lol. That might be about as good as it gets without sacrificing functionality :)
[Sprint Samsung Galaxy S III] mcluvin1065:
Yea i know like i literally turn everything i dont need off... Gps location services, data, auto brightness, the whole nine.... Seems like using it even 10 min drops like 3 or 4 percents... But then i saw another thread with 4 hours screen time with 67 percent left... So i thought i must be doing something wrong...
[Sprint Samsung Galaxy S III] prboy1969:
No new apps, or mods?

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] castle_bravo:
I'm shaping up another excellent run with row scheduler and after tonight I'm gonna be on noop for a while to test it, I know I said I'd do it earlier but I wanted to give it some time to settle before moving on. No new tweaks.

---------- Post added at 05:19 PM ---------- Previous post was at 05:11 PM ----------

Oh and guys, use lux auto brightness from the play store.

Set brightness to manual

Set brightness to lowest setting

Install lux auto brightness

Control your screen brightness with this app

Lets you go bright as hell to lower than lowest stock setting, I use it WAY low when I'm using it in the dark.

If you keep the screen just bright enough to see you will have noticeable improvement of screen on time
[Sprint Samsung Galaxy S III] daniel4653:
Nope. Idk wtf is going on. I lost 10% in 50 mins on idle. I'm at 54% right now with 30mins screen time. For bow i am going to install a different kernwl.
[Sprint Samsung Galaxy S III] mw86:
What does BBS say? Anything that was still running like MAPS or media server?

*?! # Guys added few changes. A lot of new material we have here is now in second post so keep checking post one and two occasionally.

Build prop

Min fling velocity now 4000 from 10,000

Systctrl

Vfs cache pressure now 100% from 85.

Added a few apps under apps and resources

-Lux auto Brightness

-build prop editor free by Jrummy for those without rom toolbox.

-swipe pad for easy fast way to get to developer options. Set the shortcut to nova activities - settings - developer options.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] daniel4653:
Yes media scanner. But to drop it so much ? I even have rescan media root installed Lol
[Sprint Samsung Galaxy S III] castle_bravo:
Media scanner or media server? They are different, media server for me seems to be more of an issue than scanner. In the second post there is a download link for kill media server. I swear by that app.

---------- Post added at 07:19 PM ---------- Previous post was at 06:46 PM ----------

Didn't realize that noop has no adjustments, silly me. Still gonna test it though.
[Sprint Samsung Galaxy S III] mw86:
Create localprop and force app in memory thanks nonato

- Go to terminal tyoe su hit enter

-Type all of the following and hit enter to add an app to local.prop and force it in memory. Nova Launcher would be as follows. If local.prop doesn't exist the command will create it.

echo sys.keep_app_1=com.teslacoilsw.launcher-1 >> /data/local.prop

-(Thanks nonato for posting this trick in Seeder thread.)

*!? #@ more added to second post to much to list

-the above

-CM tips

-AOSP tips

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] bso44:
I've been using castle_bravo's I/O and Governor tweaks since yesterday and so far so good. Try this:

- I/O Scheduler tweaks on ROW:

- Governor tweaks on Ktoonservative:

- Voltages listed in post #1

- Max: 1809 Mhz, Min: 192 Mhz

- Touch Booster disabled

- Screen Off Profile Mhz: 192 Mhz

- Screen Off Profile Gov: Same as selected governor (Ktoonservative)

- Swipe 2 wake: Enable ONLY while plugged in
[Sprint Samsung Galaxy S III] mw86:
My current voltage table below the table in OP that was just recently mentioned. (adding to post two right now also)

2106mhz: 1290 mV

1998mhz: 1260 mV

1890mhz: 1225 mV

1809mhz: 1200 mV

1728mhz: 1175 mV

1674mhz: 1160 mV

1512mhz: 1150 mV

1458mhz: 1145 mV

1404mhz: 1140 mV

1350mhz: 1135 mV

1296mhz: 1125 mV

1242mhz: 1110 mV

1188mhz: 1100 mV

1134mhz: 1085 mV

1080mhz: 1075 mV

1026mhz: 1035 mV

972mhz: 1025 mV

918mhz: 1010 mV

864mhz: 1000 mV

810mhz: 985 mV

756mhz: 975 mV

702mhz: 935 mV

648mhz: 925 mV

594mhz: 910 mV

540mhz: 900 mV

486mhz: 885 mV

384mhz: 880 mV

192mhz: 875 mV

144mhz: 870 mV

96mhz: 865 mV

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] bso44:
How long have you been running these voltages?
[Sprint Samsung Galaxy S III] mw86:
Since November i think. A few users are on this now as i posted these in pics maybe 5-7 pages ago can't remember. If anyone mentioned being on a voltage table lower than in OP and its working fine for them but a few need the one from OP this is the one that was reffered to.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] bso44:
Gotcha...thank you sir.
[Sprint Samsung Galaxy S III] daniel4653:
Looks like its the ROM. I've installed agats and its still thee same problem. So I take its the ROM or some setting somewhere. So I am going to factory reset my phone. I'll be back in about an hour or so.
[Sprint Samsung Galaxy S III] styles420:
You said that the battery drain started unexpectedly, without having made any changes? Sounds like your assumption that it could be the rom is based entirely on a misunderstanding - if the problem was with the rom, then it would have existed from the first install.

If nothing was changed on your phone, then there is a slight chance of hardware failure, but it is much more likely that something external changed - how is your signal strength? If it has been a little weaker than usual, then there is a good chance that there is a network problem or tower maintenance in your area. A weak signal can potentially drain your battery faster than keeping the screen on at full brightness. And if that is your problem, then it won't matter if you do a full wipe and reinstall, switch roms, or buy a completely different phone - you'll still have horrible drain until the network issue is resolved. Using airplane mode or turning off data when not in use will mitigate the problem in the mean time.
[Sprint Samsung Galaxy S III] bso44:
Which ROM are you using?
[Sprint Samsung Galaxy S III] dman918:
Thanks clankfu and mw86. I incorporated both recommended settings in the last couple posts and we'll see how it goes. :)
[Sprint Samsung Galaxy S III] mcluvin1065:
im not understanding how lux auto brightness is diffrent from the stock auto brightness feature besides a few extra features? wouldnt battery life drain be the same?
[Sprint Samsung Galaxy S III] daniel4653:
I had 4-6 bars when the draining started and I always have less than 100 ping and speeds from .7-1.8 Mbps so it is not the signal. And I'll see if its a hardware now that I wiped my phone and went back to stock
[Sprint Samsung Galaxy S III] steelers_exe:
Haven't used it personally, but from what I've read it's usefulness lies in the fact that with it you can drop the brightness level below the lowest the system allows you to. You have to set auto brightness within that app to off as well though.
[Sprint Samsung Galaxy S III] mw86:
Yes that is correct. The app is so useful you can have lux on auto and just set the brightness you like based on the current light the light sensor is detecting. Or manually make presets based on light sensor readings and what brightness may work good for the ambient light. Maybe a few of us can collaborate sometime on a very basic preset which you can restore on your phones and use the same settings we do. But it would take a few users and we could make the settings the average of all of them. So not too dark for some and to bright for others.

Just a guess but its almost like this.

100% 2milliwatts

50 1.5

25 1.25

0 1

-25 . 9

-50 . 8

-75 . 5

-90 . 3

Not at all based on facts but the idea is our amoled displays at max is equal or greater than the draw of dual core 2.1Ghz @ 1350mv on or qualcomm S4's that is if you guys joining us are on GS3 stateside.

Ill try to dig out info on actual power draw of some of our hardware components. Would be useful to keep in mind actually. Ill try to find where i read that last.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] styles420:
Damn, I was hoping it would be the signal strength, since that would mean there was nothing wrong with your phone. I feel like I neglected other possibilities in my previous explanation, so I'm racking my brain to come up with something to try. I really hope it isn't hardware issues - this is definitely a time where I'd be thrilled to be wrong, lol

Did you make any changes within the week before the problem popped up? Maybe a new app or tweak? It usually shouldn't take that long for a problem to become evident after a change, but it can happen... If you can think of anything at all that changed, let us know - it might spur some new ideas...
[Sprint Samsung Galaxy S III] daniel4653:
I'm thinking I night of changed a file with ".bak" when I shouldn't have done so. Lol. That's why I just ended up wiping out my phone. :) I'll report by tomorrow afternoon to see if my battery life is back to what it was.

---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------

Thanks for trying to help
[Sprint Samsung Galaxy S III] styles420:
Renaming the wrong file certainly could cause your problem (or others, like force closes), and wiping the phone is definitely the easiest way to undo the mistake. So it sounds like you're doing the right things - I hope we get to hear some good news from it soon :)
[Sprint Samsung Galaxy S III] mw86:
Guys how am I doing? I am not a pro so I hope this all has been proving to be useful. I hope my efforts have been acceptable. Any additions, subtractions or feedback on the tweaks and the compilation in post two of this thread? I am new to Android as of six months so I am glad to even be here with such an amazing team and just as amazing user base. You guys keep being investigative by nature and it shows everytime you give each other advice. There are no bad questions in general. Thankfully everyone coming here for help has genuinely wanted it and we have had no trolls etc. Keep up the great work team. We the Team and I feel we are all equal here. Thanks for everything Kernelizers.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] clothednblack:
Flashed JellyBam today, it's moded out the wazoo in stock form (its CM10/AOKP/Paranoid mixed) it has more buildprop files than I have seen in a long time, gonna be awhile before I get this one dialed in.

Sent from planet CM10 on a Paranoid Unicorn named JellyBam!
[Sprint Samsung Galaxy S III] bso44:
Can't say enough about the jobs you guys are doing in this thread.

---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------

Which phone did you have before making the jump to Android btw?
[Sprint Samsung Galaxy S III] mw86:
Thank you its all happened so fast. I was on a Windows Phone HTC Arrive on Windows Phone 7 later 7.5 before the amazing Galaxy leap to well the S3. I was looking for a good professional interface and was on BlackBerry before that where I had been looking for the same. I know I made the right choice new convert here... Android fan for life ftw! :)

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] awillis111:
NOW JUST A DOGGONE MINUTE...I troll here quite a bit...but I ain't a jackass like you find in other threads. Instead of "don't feed the troll" warnings, we need "don't be a jackass" bannings.

GREAT WORK BY ALL!!!

Sent from my EVO using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] bso44:
And why exactly is this directed at me?
[Sprint Samsung Galaxy S III] awillis111:
Sorry. That's not what I meant to quote. I was trying to quote the same thing you quoted by mw86. It wasn't pointed at anybody in particular.
[Sprint Samsung Galaxy S III] bso44:
Gotcha...I was a little confused by that. No worries.
[Sprint Samsung Galaxy S III] mw86:
Lol I understand lol I completely forgot trolling isn't bad its the ones looking to work up angered responses from others. We have none of that here thankfully and to prevent it here we go. Its now official... "don't be a jackass" is now a bi-law of the Kernelizer thread. I love it awillis, thanks. Feel free to jump in more often. So far I am loving your input lol.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] styles420:
We see you trollin'...

Misquotin'...

And we're sure that you're been flashin' dirty...

:p
[Sprint Samsung Galaxy S III] mw86:
You just caught him flashing dirty. SNAP!

You guys are so much fun. Its starting to sound like the TPR thead. Keep it up lol. Dont make me bust out some of Naddict's post pics.

LOUD NOISES! I DON'T KNOW WHY WE ARE ALL YELLING.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] awillis111:
Flashing dirty is ok

Riding dirty, not so much
[Sprint Samsung Galaxy S III] bob2300nx:
Your doing a great job bro. I know there have been a few but which governer tweeks are your favorite? Do you mess with the I/O settings (I havent been since it doesnt seem to be sticking).

I am using your voltages but started to see rare bootloops. So I increased 20mV across the board the problem has gone away. Just FYI that they can still be too low for some people.
[Sprint Samsung Galaxy S III] GTOJim:
When experimenting with voltages and over clocking, to be safe it's best not to apply settings at boot until sure things are working ok. Thanks for sharing, hopefully others will learn from your experience.
[Sprint Samsung Galaxy S III] bob2300nx:
I guess I phrased that wrong. It would crash with some apps (randomly) and restart. It seemed odd since I thought if it didnt crash with benchmarks I was in the clear. Guess my processor doesnt like too low of a voltage.
[Sprint Samsung Galaxy S III] FlowingAway:
Guys thank you for the recommendation of the Lux Auto Brightness app. I've always thought the lowest setting on the GS3 wasn't low enough.

However, when Lux is active I have noticed a drop in performance, namely when playing games. I play Bike Race (addictive) and the framerate drops quite a bit when Lux is running. There is an option on Lux to disable itself when certain apps are running, but I really wanted to be able to play my game while also having a really low brightness. Is there any recommendations you guys might have?
[Sprint Samsung Galaxy S III] pberge:
I haven't noticed a performance hit with Lux, but it was one of the first apps installed on my phone, so I don't have much of a baseline comparison without it.

One thing to keep in mind about Lux is that the sub-zero brightness levels are achieved by overlaying a semi-transparent dark layer over whatever is being displayed on your screen. Try lowing the brightness way down and taking a screenshot. I suppose that drawing this layer could have an impact on performance as well. To test this, change to 1% (or just above your backlight zero point setting) brightness and see if your frame rate increases again.

The other thing to look at is the auto modes. If you are using one of the auto adjustment modes, especially dynamic, it can consume a fair amount of CPU time. Try setting to manual, or adjust on wake only and see if that makes a difference.
[Sprint Samsung Galaxy S III] FlowingAway:
pberge,

Thank you for your reply. I was using manual mode and indeed, as soon as I go into the sub-zero range, the game's framerate drops a bit. The game is still playable, but it's enough to bug me. Looks I'll just have to set an exception so when that app fires up, lux will be disabled. No big deal.

Another thought just hit me. If using Lux can affect performance like that, does that make it counter-intuitive to the cause? Yes, the screen isn't as bright, but it's using more CPU to do so. Or is the screen brightness such a battery killer that we still come out saving battery?
[Sprint Samsung Galaxy S III] galaxys3man30:
Brightness is one of the biggest battery killer's it will be the number one killer over anything esle so lux will slow the drain but not stop the drain completely but not causeing a high cpu useing thou
[Sprint Samsung Galaxy S III] mw86:
Exactly see if lux drains a lot on cpu or battery it would show in upper list of battery drain and it doesn't. Going from ics, to all three versions of jelly bean i have seen the lag. You may see it less or non existent if you add the build prop and use the Hwoverlay and force gpu rendering. The issue could be when the cpu is used to create the overlay not the gpu. Checking Hwoverlay means the gpu calculates even the framework and composition on screen and force gpu rendering forces gpu to be used on anything Hwoverlay option may not cover. On touchwiz though playing a video with Hwoverlay on it can pause upon first playback and its been noted one must touch the screen for it to comeback.

Before i used lux i had a plain app just called screen filter and free but since it used the same overlay i saw same lag rarely. The services themselves seem nit to take much cpu draw. For gaming i guess its not a good solution but hours of texting or reading webpages is a good scenario where lux would be very useful.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] styles420:
It's a gamble - while a dimmer screen will consume less battery, the processing required to run one more app will take more juice. The goal is to save me more juice from the screen than you lose from the extra app.

Edited... Damn auto correct ;)
[Sprint Samsung Galaxy S III] mw86:
You could try screen filter for the games and see if the same fps drop is seen.

https://play.google.com/store/apps/details?id=com.haxor

Free... But no services like lux. So not an alternative permanently but maybe just for the games. Again like i replied to Gman i think if you haven't try applying my build prop and using both Hwoverlay and force gpu rendering in developer options.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk

---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------

Good to know can you tell me if this is from my low voltage table in second post or the higher one in the first post? I recommended everyone try the first table and if no problems move to the second one, but it would be good to know which one you had problems with and adding 20mv fixed it?

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk

---------- Post added at 12:36 PM ---------- Previous post was at 12:28 PM ----------

The governor tuning for the most powersavings i was using on touchwiz and aosp builds. I am now back on 4.2.1 and on Kt747 kernel and Ktoonsez has worked hard to fix cpu load calculator on 4.2.1. So i was using the same tunings and am trying to adjust them for a similar effect since 4.2.1 handling improved by Ktoonsez fix but not fully yet as its more sensitive than the other builds.

So i started with my favorite which was the last governor presets i posted.

Up thresh 95

Down thresh 85

Up hotplug 99

Down Hotplug 94

Min 96

Max 2106mhz

sample rate 10,100

Frequency step 2

Thats the original i am trying to adjust for same effect on 4.2.1 so far more distance between thresholds are needed and a higher sample rate... Seems 4.1.1 /4.1.2 were more accurate and precise in that respect. Haven't finished yet.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] FlowingAway:
I've not tried your build prop. How do I go about that, and what all does it do?
[Sprint Samsung Galaxy S III] castle_bravo:
I don't think using lux is a gamble at all, mw86 hit it right, if that app was using a lot of juice it would say so in our battery feed in settings. I have noticed significant difference when not using lux and using it. When using lux I have much better battery life than when not using it.
[Sprint Samsung Galaxy S III] pberge:
I have been following this thread since the day I discovered it and the information in here has really helped me. I'm fairly new to Android myself (< 6 months) and the amount of fine tuning available can be very overwhelming when coming from a phone that pretty much forces you to do things the way they want.

The one piece of feedback I would like to give has nothing to do with the content, but the format that the information is presented in post two.

Because of the high resolution of the screen on the S3, the 720x1280 screenshots are huge and awkward when viewed on a regular computer monitor, taking up the full height of my 19" screen. Some of them have been resized, but most are original, which makes things look messy when scrolling through the list. I would like to suggest a standard size for these images, and I think half sized is reasonable. I took it upon myself to batch resize all of the images from post 2 to 360px wide and zipped them up, so feel free to use them if you feel it would be helpful.

I hope to be able to participate in this thread more actively in the future, but right now I'm getting some screen flicker and graphics artifacts when I use the kt747 kernel. Hopefully it will be resolved soon and I can get back to tweaking. For now, I will continue to read and gather information from this thread. Keep it up! :good:
[Sprint Samsung Galaxy S III] pberge:
I hope this isn't too far off topic, but I wanted to add one thing regarding image size on this forum in general, because I run into full sized screen shots all the time here. If you are using Chrome, install the Stylebot extension. Similar extensions are available for Firefox as well.

Once installed, you will see a little CSS button in your address bar.

Make sure you are browsing the xda forum.

Click the css button to open the stylebot window.

Now click the Edit CSS button on the bottom left and add the following code:

td.postContent img {max-width: 360px;}

Hit save and you're done.

You can change the width to fit whatever size works for your monitor.
[Sprint Samsung Galaxy S III] castle_bravo:
Since there is not much left to test and read about these I/o schedulers I'm going to start implementing the build prop tweaks. I can't seem to find any information on the Zen scheduler :/
[Sprint Samsung Galaxy S III] mw86:
Thanks for the feedback and resised pics it will take a bit but i am replacing them now. Thanks.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk