yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] galaxys3man30:
Honesty idk what happened really BBS was normal but the only I could figure was it was seeder 1.2.4 that I downloaded this morning so I wiped eveeything of seeder n uninstalled and let my phone sit for awhile and still the battery was draining like a stuck hog but still nothing showed that was normal on checking everything but idk what went wrong just going to see what happens tomorrow

Really the main reason is if you touch ur sceen a lot ur getting that boost everytime u touch it n yes it drains ur battery cuz its turning the cpu up everytime you touch the screen see like me I use my phone for everything its my computer I make post on here from all day long n any other time as well but if you dont use ur phone like I do it wont effect you as bad as it would me so thats why we say turn it off it just another way to save battery no matter how you use ur phone
[Sprint Samsung Galaxy S III] jcdominguez:
Do you have BetterBatteryStats installed. Might give us a better view as to why the battery drain. If you don't have it I can forward you the apk I got it from xda.

I unfortunately got rid of the seeder + script altogether. After heavy use and testing I found myself having odd battery drain issues and odd device heating issues and weird cpu readings and no noticeable improvement. It felt as if i was sacraficing battery life for a lagfree device but in reality the device was already lag free as is.

I'm back to my old setup and a seeder -free device and battery is great again. I'm doing more research on this matter until more is learned ill remain as is.

Disclaimer: I'm not suggesting seeder or messing with the entropy was causing the weird behavior but due to it happening after running the seeder trial I assumed it is related. More research is definitely needed on this matter.

__________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time
[Sprint Samsung Galaxy S III] bso44:
Gotcha.
[Sprint Samsung Galaxy S III] castle_bravo:
Running the row scheduler right now, I like that that it was written specifically for flash based storage devices. I'm bout to go to sleep now (yea I know what time it is but ya gotta work when ya gotta work right?) I'm still doing my reading up on it so I understand it better but I'm curious to see how it handles. I'll share what I find of course.

---------- Post added at 09:58 AM ---------- Previous post was at 09:23 AM ----------

I'm also UV by 30 now and no issues yet, got off touch wiz finally and running paranoid Android 4.1.2. Ktoonz kernel with my last settings, and now row scheduler. Just an update on my setup.and I'll be on here in a day or two to write about my experiences with row.
[Sprint Samsung Galaxy S III] jcdominguez:
Question already asked under http://xdaforums.com/showthread.php?p=36536136

Luckymoney refer to that forum or delete that post either or. Either way let's get your issue resolved minus the multiple postings

Let's try to avoid double posting.

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] galaxys3man30:
I was about to say the samething too dont double luckymoney our team follows both threads buddy just erase the post in one of the threads
[Sprint Samsung Galaxy S III] flak0:
Running ur settings with Read Over Write Scheduler as well. So far I'm noticing even less battery drain and increased responsiveness.
[Sprint Samsung Galaxy S III] mw86:
I endorsed row since the first kt747 kernel that had it. Tried zen with bad results and used row ever since. So snappy and doesnt starve write actions.

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

---------- Post added at 05:47 PM ---------- Previous post was at 05:46 PM ----------

Scren percent really hugh how bright was screen?

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] galaxys3man30:
I have to run my really high I have bad eye sight n cant lower the screen brightness or I want see anything and I work outside most of the time that makes its even worse lmao im just getting old
[Sprint Samsung Galaxy S III] bso44:
Where are you guys seeing these other scheduler settings like Zen and ROW? I don't see them in the Ktweaker settings.
[Sprint Samsung Galaxy S III] adamdelozier:
The 1/9 kernel
[Sprint Samsung Galaxy S III] xblackvalorx:
I really don't like seeder. It's like turning the idle up on your dirt bike. Sure it snaps to full r's faster but it's burning gas
[Sprint Samsung Galaxy S III] daniel4653:
Which of his tweaks ;)

I can't find castle bravos settings. Anyone care to lead me in the right direction ?
[Sprint Samsung Galaxy S III] galaxys3man30:
Yes this is true buddy I totally agree but on the other hand it just getting started n there may be something good to come from it in the furture but its just a waiting game for now the team well continue to test and do more testing until we see fit that seeder well do more good then bad for the people that follow this thread n my team advice on xda but until then its a do at your own risk as of now n before anyone post that link is dead I already know going to fix in a few mins the link got cut short some how when I put it there lastnight
[Sprint Samsung Galaxy S III] adamdelozier:
Here is his post a few days ago.

http://xdaforums.com/showthread.php?p=36446274
[Sprint Samsung Galaxy S III] mcluvin1065:
Ok so i finally found a rom with extremely good battery life. I know someone here told me that playing games on this set up will overheat the battery immensely. Is there anyway around this?
[Sprint Samsung Galaxy S III] daniel4653:
Thank you good sir!
[Sprint Samsung Galaxy S III] galaxys3man30:
Undervolting would help with that buddy just follow the chart in my op bud
[Sprint Samsung Galaxy S III] castle_bravo:
Or don't over clock to 2106. Find a spot in between
[Sprint Samsung Galaxy S III] rhodiggah:
Looking forward to your latest setup. I would also like to try AOKP (or AOSP) soon. Since acquiring this phone, I have been rocking TPR!

Sent from my SPH-L710 TPR_TW!
[Sprint Samsung Galaxy S III] mcluvin1065:
Yea my set up already has it heheh... Was curious... Overheating annoys me
[Sprint Samsung Galaxy S III] Ragnar:
I could never think of this overheating. You guys should play with my Galaxy Nexus just for an hour and you would freak out at how hot that gets, so hot you literally can't touch it. The S3 with the settings recommended in this thread runs so smooth and good and incredible battery life.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] galaxys3man30:
My epic got that hot all the time especially during a call always had to put down n turn the speaker on lol
[Sprint Samsung Galaxy S III] daniel4653:
Epic touch while tethering got to 130 Lol
[Sprint Samsung Galaxy S III] mcluvin1065:
Yea im using mw86 setting w/ undervolt settings.... I lose like 1 percent every 5 hours heheh
[Sprint Samsung Galaxy S III] galaxys3man30:
Wow ur os is high
[Sprint Samsung Galaxy S III] castle_bravo:
interested in technical reading?

Found this gem

http://lwn.net/Articles/509829/
[Sprint Samsung Galaxy S III] galaxys3man30:
Nice find bro
[Sprint Samsung Galaxy S III] xblackvalorx:
Something needs to be done about how bad battery life is in bad reception. And the heat :/
[Sprint Samsung Galaxy S III] galaxys3man30:
Best thing to do about bad battery in a bad reception is to turn data off or put in airplane mode that ur not looking for a signel all the time ur in bad reception n when r you heating up?
[Sprint Samsung Galaxy S III] galaxys3man30:
YEA BUDDY!!!!!!! Hit a 1000 thanks
[Sprint Samsung Galaxy S III] phibetabeast:
Can someone help me. I'm running the latest ktoonz kernel 1/9 everything I set my governors and settings when my screen goes off my phones freezes or goes to black screen and I have to battery pull. I run the script at boot. Rom toolbox at boot. 1296max, 96min. Am I doing something wrong?
[Sprint Samsung Galaxy S III] pberge:
If you are undervolting, try setting voltages back to normal levels. If that doesn't work, I would try increasing your minimum and screen off profile to at least 192.
[Sprint Samsung Galaxy S III] phibetabeast:
I froze system tuner pro that stopped the issue. I don't understand cause system tuner had the same settings as Rom toolbox and kt tweaker app?
[Sprint Samsung Galaxy S III] chrischoi:
Does Deep Sleep Battery Saver Pro actually do anything? Saw a couple people using it with the tweaks.
[Sprint Samsung Galaxy S III] galaxys3man30:
Dont know never used it
[Sprint Samsung Galaxy S III] chrischoi:
Figured it was something like Juice Defender. I find those apps not functional. Wah wah.

Thanks.
[Sprint Samsung Galaxy S III] mw86:
I stopped using Juice Defender in extreme and started only using toggles, i just turn data on absolutely when i need it now. I watched juice defender took 20-30 min of usage in a days to do what i can do in a second or so. So much agreed.

Those who sync a thousand emails a day and other background stuff could easily still benefit from JD though. I guess depends on usage.

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

---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------

Nice looks like you fonally got yourself a dependable set up now. Though android system is high it all looks good. All that means is likely you had a little less screen time that run and it makes android system seem high. Its just a illusion of percents. I have a feeling everything is going good there.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] adamdelozier:
I have always us JDU, and started using DS Pro the other day...much simpler, and lighter that JDU. Has worked well for me. Yesterdays stats on Free Gs3 with ktoonz kernel almost 5 hrs screen on and 1d 15 hrs total time. Switches WiFi and data off very efficiently if u ask me. Just my 2¢
[Sprint Samsung Galaxy S III] mw86:
On topic of seeder like Gman mentioned its early in its development and so is the subject its supposed to take care of. Could we have a few see if just using sysctl has no ill effect on battery.

So far reports here are seeder takes a lot of battery and the systctrl is as well. On my setup and Gtojim's we have not seen excess drain, since all set ups can be different, without a flood of posts feel fre to keep reporting your individual findings.

A recent adjusment to my systctrl i have to post. This one has all the same except this one should keep entropy full without seeder at all. Or you can adjust the one you have to the following values.

**** just spoke with a knowledgeable member of XDA and the best bet is have stock write up threshold of 128 this way any entropy in the entropy pool can actually fully be utilized by depleting and refilling as necessary as it seems locking it at 4096 isn't necessarily helpful and may not allow the entropy to actually be used as a possibility. So below has just been edited. And i am uploading the correct initd now. That user is Zeppelinrox.

read_wakeup_threshold to 1376

write_wakeup_threshold to 128

http://db.tt/NilQsqG6

Init.d for systctrl with the above set already

Here guys this one is without anything special for entropy the values related to it are set to default on this one

So read_wakeup_threshold 64

write_wakeup_threshold 128

And randomize_va_space 2

http://db.tt/rHcNuTfR

Build prop i use and has been tested on 4.1.1/4.1.2/4.2.1

Gtojim and I are running these without issues. Tested on freegs3, cm10.1, Paranoid android and PAKman

http://db.tt/q7S1s8yp

Directions same as other build props we have listed. Until we have an easy install script this is for advanced users only who already have experience editing build.prop. I will always suggest using rom toolbox to do so vs manually editing your build prop file. Do not add all of them in without checking if the value exists already. You don't want double lines that one says the line and true and the other false, its hard to say but one may override the other. THIS IS NOT A BUILD PROP IT IS A SIMPLE TEXT FILE WITH ALL THE ONES I USE. THE BUILD PROP ENTRY IS TO THE LEFT OF THE EQUAL SIGN AND THE VALUE USED IS TO THE RIGHT OF THE EQUAL SIGN. YOU MUST SEARCH AND REPLACE OR ADD THEM MANUALLY.

Edit: the above post has been edited with proper info and a new init.d file version.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] davelikestacos:
So I am trying to find QOSMGR and GSIFF_DEAMON on my GS3 L710 with KT747 and LiquidSmooth 4.2.1 Beta 2 but I cannot seem to find either file. Anyone else have this issue?
[Sprint Samsung Galaxy S III] mw86:
Sorry for the second reply in a row guys.

Made some edits to the above post.

I consulted an XDA member and likely better we setup the systctrl to what i uploaded above.

I included a initd for systctrl that does not have anything for entropy changed so users not wanting to try or use the controversial new tweaks can still benefit from a few sysctl values improved.

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

---------- Post added at 06:01 PM ---------- Previous post was at 05:49 PM ----------

Your done sir on 4.2.1 you just need to take care of mpdecision. That one is only necessary if using a governor woth hotplugging built in. Ill grab link to how to stop mpdecision on 4.2.1. Rename it to mpdecision.bak and you will need to edit a system file carefully. Ill post the link here:

Navigate like in this pic to system/etc

Open postbootsh

Go to line 223

(i use droidedit to edit the file it makes it easy to find line numbers)

Place cursor in front of mpdecision and insert a #. Save the file and exit and reboot. Thats all thats necessary to prevent stopping mpdecision from issuing errors over and over in logcat on Android AOSP 4.2.1.

*#*@ Credit goes to Decimalman thank you :)

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] bob2300nx:
I dont get how to get the CPU min/max to stick? I have tried setting the same settings in ROM toolbox but then when I reboot and open ktweeker it says the min/max dont match. Then when I open ROM toolbox it shows the wrong frequenceies 1512 max and 96 min. So I deselected the ROM toolbox apply on boot and still have the same problem. Any ideas?

I pretty much get this message everytime I close and reopen ktweaker, because of what rom toolbox said its almost like ktweaker isnt OCing correctly
[Sprint Samsung Galaxy S III] mw86:
Do you have freezas script in your /system/etc/init.d folder its starts with the number 70 in the name? It based on batte lowers your max frequency and will override ktweaker. If its there delete it or back it up to another location. Its currently the most common cause.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] GTOJim:
Just installed DS Pro and so far I liking it better than JDU, much easier to configure, seems to be working as advertised. JDU IMHO tries to do to much, offers many options the average user isn't going to need or use. DS Pro is easy to setup, in the very limited time I've been using it, it does everything I need. So far streaming audio seems to be working well. Cheaper to purchase which can be a good thing.
[Sprint Samsung Galaxy S III] mw86:
Great feedback GTOJim and adamdelozier. Feel free to share how you like to set it up.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] GTOJim:
DS Pro has 6 profiles, my streaming audio settings at bottom. When screen is off phone will be in deep sleep except noted below.

Gentle, wake up every 30 minutes for 1 minute

Strong, wake up every 45 minutes for 1 minute

Balanced, wake up every 1 hour for 1 minute

Aggressive, wake up every 2 hour for 1 minute

Example e-mail app can sync with settings above.

Slumber, and Custom, deep sleep when screen is off, Slumber stops running apps when battery is 10%

Custom has Deep sleep weekday and deep sleep weekend settings which can be set to user preference. Example wake up every 1 hour, also has night settings, which I set to match my sleeping hours, during this time always deep sleep.

For streaming audio

In settings, deep sleep, Stop Apps White List , I added my streaming audio apps so they will not be killed if running when screen is off. Be sure background data box is checked for streaming audio or downloading when screen if off.
[Sprint Samsung Galaxy S III] bob2300nx:
I found post-int which I tried renaming with .bak but that didn't seem to help also found enable-oc both in the etc folder. Post-int says Max 1512 but idk if enable-oc is suppose to override that

I tried manually editing the post-intended.sh but that didn't seem to work either

Edit: Since the edit didn't work I deleted the files and rebooted... They then were recreated but are as I left them after editing the speeds. Another thing I notice is after booting I see a message saying ktweaker settings applied but I have the same issue. Running a fresh install of the peoples rom
[Sprint Samsung Galaxy S III] GTOJim:
Leave those two alone, the trouble maker has 70 in it's name, it will conflict with KTweaker settings and override.

You can try mw86 I/O settings in post #310, it's helped some, not all, might be worth giving it a shot.

Sorry just read your original post, this wont help since your settings are changing.

I'm in the same boat, I'm using mw86 latest more aggressive battery saving settings and even though I'm using Rom Toolbox my settings are not sticking. After rebooting I go into KTweaker after every reboot because like you they change. To me it's not a big deal, if I was rebooting a couple of dozen times daily it might be a bother.
[Sprint Samsung Galaxy S III] castle_bravo:
Gto Jim I'm curious to hear what you think of ds pro, I might give it a try. Currently testing schedulers and I want to test em with out a program like that.
[Sprint Samsung Galaxy S III] mw86:
Can you put those files back just how they were? They need to be like they were they were both necessary.

Give us some background. Do you have any apps that say powersaver, is power saver enabled in settings which limits max speed, do you have other overclock apps please list if so, juice defender and anything similar can cause this, it has an options to control mhz so if possible list as much details as you can of the apps like that you may have and how you are setup. For extra help for us please. List Rom, kernel, gapps version (if on aosp), android version number etc.

So to clarify the only files in initd are postboot and enableoc.sh yes? Those are needed and belong there so we can rule that out. After changing those back to normal reboot.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] bob2300nx:
The issue isn't the annoyance of having to run ktweaker after booting, I am likely getting worse battery life because the settings aren't sticking 5 mins later even if I don't reboot.... It's like my phone is fighting with itself
[Sprint Samsung Galaxy S III] castle_bravo:
I had almost that exact same issue, I wound up having to clear ROM toolbox data and uninstallit. I set up ktweaker then reinstalled ROM toolbox, problem solved.
[Sprint Samsung Galaxy S III] mw86:
Understood yes thats what would happen if your min max keeps getting messed up and or your governor settings. Can you post any of the requested info to try to find the source of the reset. The general reset is from that 70 script for some, and the other is usually a rogue app. For Gtojim its due to up threshold, down_threshold and the hotplugs are not in the order the kernel likes. But sometimes the rom toolbox theory helps. For me on more than one android version and Ktoonsez kernel KT747 I don't get the reset as long as i mess with the thresholds and renter those menus making sure they are set correctly and do the backup then set rom toolbox reboot and mine does not reset. Some boots very rare my max is 1100mhz or around there a reboot my normal setup boots. For Gtojim it resets but early on he had it not resetting and eventually the issue comes back. Still not sure why. Ktoonsez may be able to give insight in his thread too. But if you can please let us know your full set up we may be able to figure out whats causing yours to reset.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] bob2300nx:
Ok I had trouble reediting the postboot (kept saying failed) so I reflashed ktweaker wiped cache/devalk, fixed permissions. Now it is the same as before. Yes postboot and enableoc are the only files in that folder. I had deep sleep installed earlier but have uninstalled it since. I kind of doubt it is the problem since I couldnt get the settings to stick before that. Last night when I couldnt get them to stick I decided to do a clean install of the peoples rom 3.08 and then installed the latest ktweaker/kernal. I have followed the directions in the OP, except renamed the mpdecision with .bak instead of a script. I then edited the voltage tables based on your settings and used your second set of gov settings found in the OP. I marked Rom toolbox as set on boot and also made ktweaker set immediatetly on boot. The voltage and gov settings seem to stick. Only problem is the CPU settings.

EDIT: I cant really think of any other apps that would change this other than the deep sleep one I uninstalled earlier. I did a fresh install last night but my SD card has been through 4-5 roms. That shouldnt cause a problem though right since its not part of system?

Regardless thanks for all your help let me know if you would like any other info

---------- Post added at 03:56 AM ---------- Previous post was at 03:52 AM ----------

BRB giving this a go.

EDIT: Ok uninstalled rom toolbox completely, did a restart and allowed phone to fully boot. Then opened KTweaker and all settings are sticking except CPU. It seems rom toolbox does not have any affect on my setup.
[Sprint Samsung Galaxy S III] GTOJim:
I like it, but haven't had it long enough to give a fair evaluation. The developer is quick in resolving any issues, right now the support is great.

I just had my phone freeze up in my car while listening to streaming audio, it's to early to say it's due to DS Pro. I recently stripped a bunch of stuff out of my device, so that might have something to do with it.

I'll update in a couple of days unless other people start offering experiences with it. Sorry I can't be of more help right now.
[Sprint Samsung Galaxy S III] mw86:
Gosh i guess give all of us a bit to think of other solutions. It shouldn't keep resetting your max speed and i am unsure as of yet whats causing it. At this point it doesn't seem like anything wrong on your setup. Is anyone else having the same issue on that rom and setup?

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] castle_bravo:
I did but I can't for the life of me remember how I fixed it. Thinking and looking now

---------- Post added at 10:43 PM ---------- Previous post was at 10:37 PM ----------

When going in to ktweaker it would show 2106 after giving me the min Max message. I would go in to ROM toolbox and it would show 1500. I would move the slider in ROM toolbox and it would dynamically and automatically change it right back to 1500. I thought clearing its cache and data, then uninstalling it did the trick. I'm going through the phone to try and remember if that was it.

---------- Post added at 11:04 PM ---------- Previous post was at 10:43 PM ----------

Bob2300, only thing I can think of, which I think you already mentioned, is do what I said about ROM toolbox, or any other program that had input to the cpu control (I reinstalled it since with no issues) then flash the kernel cleaner script and the same kt747 zip. Then see if the settings stick reinstall ROM toolbox. Thats all I got bud.