yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} JB and TPR roms

Adding on to post from earlier... Any of this telling of my high android system usage?
[Sprint Samsung Galaxy S III] mw86:
Re: [Team Kernelizers] {how to} JB and TPR roms

I am using the early Onite 45000mah battery i bought off amazon which had no NFC. They make one with NFC now pretty much same price.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] jcdominguez:
how bulky is your phone now. i know its advertise as slim. cant seem to find any pics of its bulkiness or lack thereof.
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

I'm using an Onite I bought a week ago. How do I check about the NFC?

Sent from my EVO using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
Re: [Team Kernelizers] {how to} JB and TPR roms

Hey guys ,

I'm running freegs3 v3 tw rom with ktoonsez latest kernel.

-Row scheduler with castle bravo tweaks.

-ktoonservative governor with castle bravo tweaks.

- deleted the freeza file in init.d

-undervolted extreme version in first post

-under clocked 96mhz and overclocked 1890mhz.

-manual screen brightness always set just enough to see.

-using ds battery saver pro on custom settings

-froze drm and Sprint optimizer

-kill media server apk

My android os, android system and media server look a bit high but I'm not sure if it is.

My battery doesnt seem very good. Here are some pics, please let me know what you think.
[Sprint Samsung Galaxy S III] daniel4653:
Re: [Team Kernelizers] {how to} JB and TPR roms

Did you delete 70tweak ?
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

Have you renamed the other files as well in the first and second post and they dont look that high that about normal really how long have you been running the rom?
[Sprint Samsung Galaxy S III] apexone4697:
settings wont stick

I need help. Been trying for 2 days to get the kernel settings to stick. Trying to run ktoonservative with the tweaks from first page. Every time I set them, I will turn screen off, then open up ktuner and they all revert back. Same thing when I try to use from toolbox. I've done the clear data from ktuner and restore settings. Nothing seems to work. Anyone have a sure method? Thanks guys
[Sprint Samsung Galaxy S III] Ragnar:
Re: [Team Kernelizers] {how to} JB and TPR roms

Did you set them on ktuner and selected to set immediately at boot then go into rom Toolbox and make sure you checked off set at boot?

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] steelers_exe:
I was having this exact problem earlier today, and after trying everything suggested, all it took was to backup settings in ktweaker, uncheck apply at boot in ktweaker and rom toolbox, restore settings in ktweaker (twice as suggested), change the value of one of the governor tweaks (i think i upped down threshold by one), apply scheduler tweaks mentioned here, then check apply at boot in both ktweaker and rom toolbox. worked for me.
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} JB and TPR roms

Is power Save Mode on?
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

And also what rom are you running n jpr only thing ask is dont double post buddy I mean dont post here n then post in another thread buddy we watch both thread very closely n most likely you will get a answer here before anywhere esle my team lives on this thead buddy im not flameing you or picking on ive told someone esle this too and it goes for everyone that reads this post plz if you post here just post here plz thats all I ask buddy like I said you probley a faster answer here anyways
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} JB and TPR roms

Sorry guy. Not trying to stir the pot or clog the threads. Just figured more chances for input. Didn't realize it would be considered double post. Thx for heads up. Every one has been great around here so far. The help has been terrific and atmosphere has been clean and refreshing.
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

How thats how I want it around here buddy no harm done my friend everybody n anybody is welcome here thats why I made this thread for the reason of answers and getting info on anything but its all good bro no worries buddy but on another note ur screenies looked good to me looked normal buddy
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
Re: [Team Kernelizers] {how to} JB and TPR roms

Yes I did

---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------

I Renamed all the files too. Been running this about a month? Whenever the v3 got released I was running it. But I recently did a restore a couple days ago.

I just got the random reboot while on YouTube . Everything was working ok the whole day and just now browsed YouTube for 10 min on Wi-Fi created the reboot.

Should I change the voltage to the safe version on op ? Does this seem to be the restart problem?
[Sprint Samsung Galaxy S III] apexone4697:
No
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

Do you bbs on your phone need to get that if you dont have it it can you if there is a rouge app or something of that nature
[Sprint Samsung Galaxy S III] clothednblack:
Re: [Team Kernelizers] {how to} JB and TPR roms

Kernels are carrier specific, right? Wonder why

Sent from planet CM10 on a Paranoid Unicorn named JellyBam!
[Sprint Samsung Galaxy S III] Ragnar:
Re: [Team Kernelizers] {how to} JB and TPR roms

No kernels are not always carrier specific. If you look at the Galaxy Nexus devices kernels can be used from any carrier across all.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
Re: [Team Kernelizers] {how to} JB and TPR roms

But not the sg3, I'm guessing, Koontz makes a kt747 version for me (us cellular) since his vzm doesn't work

Sent from planet CM10 on a Paranoid Unicorn named JellyBam!
[Sprint Samsung Galaxy S III] mbc663:
Re: [Team Kernelizers] {how to} JB and TPR roms

And this sir, Is how you brick your phone. Never flash a kernel not specific to your device. That's android 101, don't learn the hard way!
[Sprint Samsung Galaxy S III] Ragnar:
Re: [Team Kernelizers] {how to} JB and TPR roms

We are not talking devices we are talking carrier. I'm just explaining that not in all cases are kernel carrier specific. On the S3 yes your limited. But read what I said, if you look at the Galaxy Nexus devices if you have a kernel you can use it on Verizon, Sprint, Att, Tmobile any version of the Galaxy Nexus. So the belief that kernels are all carrier specific is not necessarily true. Now due to so much integrated by the carriers into the non aosp phones and Sammy, such as the S3 that true open source goes out the Window.

Transmitted with a portable device using Xparent Blue Tapatalk 2

---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------

CORRECT.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] apexone4697:
bbs?

Bbs?
[Sprint Samsung Galaxy S III] GTOJim:
Better Battery Stats.
[Sprint Samsung Galaxy S III] steelers_exe:
Better Battery Stats

Indispensable tool for determining what is keeping your phone from deep sleep or waking it from deep sleep.
[Sprint Samsung Galaxy S III] prboy1969:
Re: [Team Kernelizers] {how to} JB and TPR roms

One of the first apps I load after flashing.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

I would out the better battery stats link in the op but the dev says not to so I cant if you want it you have to search for on xda its free for xda memebers but none members have to pay on the play store
[Sprint Samsung Galaxy S III] mw86:
Re: [Team Kernelizers] {how to} JB and TPR roms

You could load this app temporarily and check. https://play.google.com/store/apps/details?id=com.promethylhosting.nfc.test

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

---------- Post added at 05:27 AM ---------- Previous post was at 05:22 AM ----------

The battery is about double the thickness of stock so it used an extended back plate and adds about as much weight as another stock battery would weigh. These phones have gotten so light and slim but large displays i have not noticed a lot of bulk more than likely because i am more comfortable with a thicker feel to the phone. I just use a basic protector on it. I just like having a bit extra battery than stock.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] dman918:
Anyone?
[Sprint Samsung Galaxy S III] Ragnar:
Re: [Team Kernelizers] {how to} JB and TPR roms

I never use JD is think it causes more damage than good. It's not only about kernel settings. Are you in a good signal area. Are you on wifi? Are you shutting of data? Are you freezing DRM? Are you using apps like Facebook? These are killers if you are then there's other things you need to do to shut down their behind the scenes processes.

EDIT: As stated on the post after mine, I shut Sync off all the time. Everything app syncs the moment you go into them so it doesn't matter, and I turn autovsync on like every 4 days just to update any contacts which may have changed. Now some people are freaks about this because they can't just check their email they feel they need to be notified.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] prboy1969:
Re: [Team Kernelizers] {how to} JB and TPR roms

Another thing to pay attention to is how often things sync. Noticed this made a huge difference on the wife's SGS3.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] jcdominguez:
Re: [Team Kernelizers] {how to} JB and TPR roms

Dman

A few things. I find juice defender pretty good overall. however I find and others have experienced issues where it takes a long time or sometimes it never reconnects back to data or WiFi. For people experiencing this I recommend DS Battery Saver Pro I use it on slumberer mode and works very well. Connects back immediately.

As for settings. The Team Kernelizers forum suggest many many many adjustments and no two devices are the same. Mix and match see what works.

Try this.

Save your current kt settings. Name it whatever you like. I usually name it the average battery life i get with the setting. Example: 19hrs. This will help you go back to those settings automatically in case others don't work as best as your current setup.

Load default on kt. Switch over to mw86 settings found on first post. Switch over to bfq. Set min 96 max 1806 lock frequencies and enable oc. Make sure touch booster is disabled. Undervolt all by 25 (hit menu in voltage and subtract 25) to all. If on TW rename the appropriate files. Make sure mpdecision is disabled (I do this by adding .bak to mpdecision located system/bin) . Install CPU spy as well as BetterBatteryStats both of these two programs allows you to see what your phone is really doing under the hood and we can get a better idea of what needs to be adjusted. With CPU spy we want to see deep sleep when phone is sleeping and low MHz with light use. With BBS we want to see little or virtually no wakelocks.

If you have been flashing ROMs it may be time for a battery calibration you can find many free apps in store. Having a battery calibrated helps show a much more accurate depiction of your battery.

Run with these settings for a while see what you get. I recommend charging to 100% always...before applying new adjustments

Battery life all on its own is a science my friend.... and we are its scientist. Try different settings. Avoid UnderVoting no more than -30 across the board.

Pm me if you have ???

____________

Device: Sprint Galaxy S3

ROM: Slimbean Android 4.2

Kernel: Ktoonz 4.2

Current Battery: Testing for 4.2

Old Result: 23 hrs w/5hr screen time

"Extending android battery life through research, testing, and calibration."

Proud kernel scientist for Team Kernelizers!
[Sprint Samsung Galaxy S III] mcluvin1065:
Re: [Team Kernelizers] {how to} JB and TPR roms

If we run cm10, must we still edit all the files and what not? And are all the steps same after that?
[Sprint Samsung Galaxy S III] jcdominguez:
Re: [Team Kernelizers] {how to} JB and TPR roms

For cm10 only the mpdecision file and yes all the same

____________

Device: Sprint Galaxy S3

ROM: Slimbean Android 4.2

Kernel: Ktoonz 4.2

Current Battery: Testing for 4.2

Old Result: 23 hrs w/5hr screen time

"Extending android battery life through research, testing, and calibration."

Proud kernel scientist for Team Kernelizers!
[Sprint Samsung Galaxy S III] apexone4697:
im gunna try what you wrote. I an get the settings from ktuner to stick at boot. When i go back into ktuner say like 5 minutes later to check, it prompts me that my current governer is not the same as my saved governer. So i think it keeps reverting itself back.
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} JB and TPR roms

Thanks for feedback. Just never seen android os and system higher than Screen, let alone even close.
[Sprint Samsung Galaxy S III] dman918:
Thank you so much for your detailed response. I will try it this weekend and report back.
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} JB and TPR roms

I just came off of aosp and back to tw because of a few reasons but I noticed on tw that android system and os are almost always up around 20% but on aosp I don't think I saw them cross 10% once. Cell standby was always higher. Don't really know why but I have a theory.

Goin nuts on this gs3
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} JB and TPR roms

Thanks man. Good to know. Haven't done aosp on the s3 yet. Did alot on og evo, so that's where my experience comes from. Good to know it's normal for tw.
[Sprint Samsung Galaxy S III] apexone4697:
Question. I got the settings to stick in ktuner on boot. I will open ktuner right after boot and it dosent prompt me that anything is different. But then i will open ktuner like 5 min later and then it will throw a prompt that somethings different. Should i not open ktuner again after i boot? Does this throw off the settings? I would like to only use rom toolbox to keeo settings and just freeze ktuner.
[Sprint Samsung Galaxy S III] prboy1969:
Re: [Team Kernelizers] {how to} JB and TPR roms

I follow the steps in the OP. Then reboot. After reboot I open KTweaker. It usually prompts me about at least one thing. Then I click yes. Open up the general settings, and uncheck Lock Frequencies. Then recheck it, and back out. Then everything sticks.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] mw86:
Re: [Team Kernelizers] {how to} JB and TPR roms

A user here suggested in addition make sure each threshold all four are set at least one number apart as i also found this to be true in helping keep governor resetting.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] apexone4697:
will try. thanks.
[Sprint Samsung Galaxy S III] mw86:
Re: [Team Kernelizers] {how to} JB and TPR roms

Those on Ktoonservative 4.2.1 with jumpy cpu behavior try enabling yoyo cpu load with a 1 and enabling ignore nice load with a 1 which should help the jumping of mhz so often. Next just raise sample rate just a bit maybe 15-20k (30-50k if really bad jumping still) and throw in a sampling down rate of 2-4 low if you have a high sample rate.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

Do these look right?
[Sprint Samsung Galaxy S III] daniel4653:
Re: [Team Kernelizers] {how to} JB and TPR roms

Yup. Let us know how it works out for you ?
[Sprint Samsung Galaxy S III] bso44:
I believe what all those battery calibration apps do is simply delete the batterystats.bin file. An actual Android dev at Google debunked that it has any real effect on the accuracy of your battery.

https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
Re: [Team Kernelizers] {how to} JB and TPR roms

My phone freezes only when I was on you tube for a while and random rebooted. Is the under volting a bit too much?I just got lux to try improve the life of the battery . Any other suggestions? Castle, have you found better specs for the row scheduler?

Thanks in advance

Steven
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

Will do after a few days. This on a clean install of slimbean rc1. So, I'll give it a few days to settle.
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} JB and TPR roms

Nah I haven't messed with row since I last write about it, I have been using noop. I think maybe the rp read quantum could be brought down to 75 with good results though.

Goin nuts on this gs3
[Sprint Samsung Galaxy S III] clothednblack:
Re: [Team Kernelizers] {how to} JB and TPR roms

Anybody know (dev) iGio90?

I'm trying to get a hold of him.

Sorry for the off topic.

Sent from planet CM10 on a Paranoid Unicorn named JellyBam!
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} JB and TPR roms

This is going to be a write up of my experiences using the three schedulers which are row, noop, and bfq. This is all on a stock battery with the Bfq tweaks here and my own row tweaks I posted on here with battery conscience governor tweaks (not extremely conservative though) and strict radio usage.

Let's be honest, there aren't HUGE differences in how the phone feels using different schedulers. But there are some differences.

For example, overnight drain.

Leaving the phone alone for 8 hours overnight with WiFi, data, gps, Bluetooth, etc etc all these radios off. Same Rom stable, no new apps, no new setups, same wakelocks (basically exactly the same) proved interesting differences.

Bfq saw no change in battery life at all. Go to bed with 100% battery, wake up 8 hour later with 100% battery.

Noop saw 3-4% every time

Row saw 8-10% every time

Weird seeing as the phone should be in deep sleep and not doing anything.

Another thing I noticed is response from screen off. With row the phone is very responsive with very little "lag" bfq was a little laggy occasionally, while noop was mostly laggy a lot of the time.

Phone feel with what I consider normal our moderate use.

Row was sick, no lag or stuttering and very good response. Bfq was a bit better than noop in this area but for certain things it lacked. These two went back and forth for me, I really don't know which one performance wise was better, where one was bad the other was good and vice versa.

Phone response with heavy load I.e. games.

With bfq, after only a little while the phone would get real hot and the game would stutter and crash, every time for the test. Noop would have a little lag to start or load but once in game wouldn't have a problem like above. Row had now issues and was smooth as glass. Battery drain was similar for all schedulers.

Now for numbers!

Light use;

Noop I just recently went 38 hours on a charge, 4 hours screen time and could've went longer.

Bfq was giving me 34 hours with 5 hours screen time.

Row was getting me 26 with 4 hours screen time.

Moderate use;

Noop would get me 28 hours with 4.5 hours

Bfq would get me similar

Row would get me 23 hours 4 hours screen time

Heavy use;

All numbers here very similar but row would give me lag free smooth operation while Bfq I would rate 2nd here and noop last.

My final words and opinions:

Row is our performance scheduler

Bfq is our balanced

Noop is our battery saver

I prefer a battery saving governor setting using row because of phone feel and I can still get 4 to 5 hours screen time on a 20 hour cycle but if I know I won't be around a charger for a while I'm going to throw Noop on it.

Bfq and Noop are VERY similar but I prefer bfq even though it's not optimized for solid states because of initial loads, but if you care more about current performance over initial loads go with Noop.

I hope I didn't get to redundant on here (writing this watching the hockey game so I'm half not paying attention)

Goin nuts on this gs3
[Sprint Samsung Galaxy S III] xblackvalorx:
Re: [Team Kernelizers] {how to} JB and TPR roms

Voltages can go far lower on aosp roms. I'm running 825@96mhz-1120@1512mhz so far perfectly stable on aokp and liquidsmooth. Going to keep pushing them down.

My phone will not run the extra low voltage table on any TW roms.

Just a little note for those of you feeling adventurous.
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

No sir I dont buddy
[Sprint Samsung Galaxy S III] docnas:
I just wanted to post a long term report of how my phone has been since I updated my rom to FreeGS3 to 3.0 and did a majority of the tweaks talked about here with an eye to battery saving but with just enough performance that its not laggy.

My average battery life according to GSam Battery life is 21hr:52m. In actual usage I rarely have any problems with charge, Unless im in a very low reception area like in the basement or such areas when my phone eats thru my battery like its nothing.

I can easily get 4-5 hrs of screen time with 1-2 hrs of calls on a single charge running the whole day with email being pushed same with a voicemail app I have installed (hullomail).

In regards to performance Im preety happy, yes I can overclock it but I think for most needs its more than fast enough so I keep it normal BUT I have undervolted my CPU by a large amount. I m guessing I got lucky and got a CPU from a good batch as I have lowered my voltages by a significant amount and have absolutely no problems. At 96Mhz voltage is 800mv and at 1512 Mhz the voltage is 1050mv. I could probably squeeze some more juice out of the middle voltage values but eh I think its enough.

My IO schedualer is BFQ and i didnt change the settings. My governer is ktoonservative using governer tweaks slighly modified from the ones given in the OP.

Ime attaching screenshots of my CPUSpy stats to give an idea about its stability and how its really staying at lower cpu speeds unless really needed.
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

This maybe OT. But, which of the build.prop tweaks are supposed to stop screen flicker. Is lpa.decode=false the only one?
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

Lol nothing isb off topic here buddy n I think thats the only one mw86 can answer that better then I can not to good with build props
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

I know how to change them. As far as what they do, it's all Greek to me
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

Yea im the sameway bro i can change them n all but just know what they do im clueless lmao
[Sprint Samsung Galaxy S III] steelers_exe:
It may not be exactly what youre looking for, but the built-in build.prop editor in rom toolbox gives a brief description of a good chunk of them. You could check it out and see if it helps.
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

RTB did make it much easier. Thanks for the tip. Think I found what needed to changed.

lpa.decode=false

persist.hwc.mdpcomp.enable=false

debug.composition.type=gpu

debug.mdpcomp.maxlayer=2

So far (about 3 hrs), no screen flicker.
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} JB and TPR roms

Damn bro great work buddy glad you got it working
[Sprint Samsung Galaxy S III] awillis111:
Re: [Team Kernelizers] {how to} JB and TPR roms

Amazing what you can learn by SEARCHING

Sent from my Nexus 7 using Xparent Blue Tapatalk 2