yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mw86:
I thought this out. If you want to be certain futher than that try the following. Simply set your settings back to your own. Next set max mhz to your max 1500mhz and run the app you mentioned you opened and crashed immediately. It shouldn't crash, run it and make sure it survives. Rinse and repeat. Set max to the next mhz down test same way. Do this on each frequency testing by setting the frequency you are trying to test as your max. If you have no issues on all frequencies then no matter what game, media, app or as much as you can do on phone wont one day surprise you with a crash.

To clarify what can be seen. Often either a reboot, a blank screen that requires holding power 4secs or battery pull to reboot, or Android message stating Android System or any other important service force closed or something.

The fact youve used it for awhile like this no issues is a good sign. We know the volts are being used. I tested on mine 700mV at 96mhz in about a minute or less a app or so closed and i was frozen the UI got messed up so i held power. All phones are different. Its likely your either at the needed mv on all mhz used or very close since you have not seen issues. Maybe if you find the time you can run each one like that and let the others know, who may find their phones handle low mv good could try yours. You could post if all worked fine or end up posting a revised one. In anycase your phone handles undervolt well.

Just out of curiosity was it Stability test or Antutu the app you tried first? In any case stock phone set up all of our handsets handle those two apps while being stable. I hope that helps you confirm even better :) thats how i tested often but usually i try even more than just the two but i found nothing else to be revealing as well as those two. Later i have to catch some zzzz

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] asaa:
edit:nvm
[Sprint Samsung Galaxy S III] clothednblack:
Lol, as I don't mind testing your ideas, that one is very time consuming and I just don't have it atm, maybe another time. I already know that it works and is doing what it's set to do. :)

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Its no problem i went over to the other thread and i see how they are running 1458@700mv and ill be tinkering on it myself over there. Nice undervolt in anycase.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
Bfq with tunings

echo 24 > /sys/block/mmcblk0/queue/iosched/quantum

echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle

echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_max

echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty
[Sprint Samsung Galaxy S III] freecharlesmanson:
As a general statement I believe this platform supports out of order processing so although the thread queue is still the same which is cfs (very complex can of worms) I'd recommend separate reading on that note when the cpu is given a operation that will take multiple iterations dependant on other iterations it may process some ahead of others to acellerate the whole operation rather than a linear queue for execution, this with the advances under full load seems to be suggest it will be sigficantly more efficient with multiple threads
[Sprint Samsung Galaxy S III] mjdavis871:
My eyeballs are spinning trying to figure out what all that meant.

Sent from my Eclipsed Galaxy SIII
[Sprint Samsung Galaxy S III] freecharlesmanson:
It's a simple and common processing variation, happened back in early x86 architecture http://www.anandtech.com/show/5559/...mance-preview-msm8960-adreno-225-benchmarks/2

This and many other articles confirm this and undoubtedly supports the fact in some circumstances it exceeding it's single thread efficiency
[Sprint Samsung Galaxy S III] mw86:
I am working on another variant of KTOONSERVATIVE tunables hoping to save more power still enabking core two often but often disabling it when load or mhz is dropping. I am finding core two races to idle no matter what the up thresholds get set to meaning core two activities it easily and even faster than core one races to max or near max frequency and back to idle even if it stays on or hotplugs back off and no matter what thresholds i set core two acts like that. So my last setup enables core two for longer and waits for core one to drop closer to idle and lower mhz before turning off. I found that helps keep mhz down but a small issue is core two is using higher mhz than core one longer and more often. So to take advice from someone here i have varied the setup from that now.

My new one turns up threshold and up threshold hotplug at same time at as late a load as possible. Sample rate at minimum possible. Down threshold just a hair under up threshold so that if mhz are unnecessary it only takes 10ms to drop one bin to try to fit load better. I set down hotplug just a hait under that down threshold and it is doing good to turn off core two often almost anytime load drops fast and even better the mhz down threshold for atleast a split sec still follows mhz down a bin or a few before it triggers the down hotplug again. This as i am using it happens many times a second. Noticibly ive cut down on core two being on by about 1/2-2/3 the amount of time it was active on my previous setup. Benefits are still as Freecharlesmanson explained dual core often is benefit in even single thread loads and thats why i have two cores on anytime load raises and more mhz are needed. Every period after that load is a lot lower cpu drops out second core and starts process off mhz lowering until load is at target. With 2% frequency step and a min max of 96-2106mhz a 10k sample rate (10ms) can escalate from min to max in nearly 290ms just over a quarter of a second, which is plenty fast to go from idle to max speed, not much would need to be at max to stay in target threshold so most anything short term is met by a mhz and load drops and subsequently mhz back to idle all very quickly in 10ms steps. I have the thresholds up very high would even seem too high. Since sample rate is so low it seems to ramp up fast enough to not feel laggy unless you prefer to use performance governor performance should be very good. If load is excessive continually it will stay in upper mhz ranges and not hold back too much but the thresholds should keep unnecessary mhz use down.

Using screen off mhz at same as screen on is best in my opinion since lets say 96-384mhz finishes a task taking ahile minutes later and allowing full max it finishes in a few seconds on max speed. If a light undervolt is used on max speeds the use of those mhz should have a more efficient return to idle. 1200mv for a few seconds is less than 900mV for a few minutes unless its a constant drain.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] decimalman:
Since each core's frequency is independent, the kernel assigns each core its own governor. As far as I can tell, none of the currently available hotplugging governors account for this when collecting load information, which prevents them from seeing core 2's load when making hotplug decisions (but fixing this could break the way they adjust frequency).

I don't know of any tools that will let you easily play with core 2's settings, but they're available in sysfs if you're curious. By default, both governors are set to interactive, and changing the governor in KTweaker or similar only sets core 1's governor. If you disable mpdecision and change to a governor that doesn't hotplug (when core 2 is offline its settings disappear), you can explore and make changes in a terminal:

su
cd /sys/devices/system/cpu/cpu1
echo 1 >online
cd cpufreq
cat scaling_governor

Honestly, I wouldn't worry much about what governor is running since it doesn't make as dramatic a difference as you'd expect (you might be able to trim a couple percent power usage, but core 2 usually uses a fraction as much power as core 1 even under load). If you decide to change governors, it's a very bad idea to set a hotplugging governor on core 2. It'll cause core 2 to eventually try to turn itself off, causing a deadlock that requires a reboot (abyssplug might be immune to this since IIRC it schedules the shutdown on core 1, but I haven't tested).
[Sprint Samsung Galaxy S III] freecharlesmanson:
I'd ask for more evidence, I'm not saying your wrong. But it clearly states the secondary governor as ondemand in CPU1.also in that light now I could be wrong but the core frequency as far as I know is locked....where did you get the idea it wasn't? Even if it isn't the primary governor should still cause it to sync with core0 yes?

Ktoonsez very clearly told me that it does pool the second core. By what I can understand in the c file it does look at all available cpus
[Sprint Samsung Galaxy S III] decimalman:
I'm definitely wrong about things blowing up with hotplugging governors on core 2, so I retract that part of the post.

Play with trepn, userspace governor, and scaling_setspeed in cpu1/cpufreq. Core 2 is independently adjustable.

With two governor instances and two separate frequencies, no syncing is done between cores unless explicitly coded into the source. The C looks like both cores should be polled, but AFAICT policy->cpus will only be a single cpu. I think I tested this, but I'll recheck.

EDIT: Just checked. Unless ktoonsez is doing something sneaky that I'm not, policy->cpus will only be a single core.

EDIT: IIRC /system/etc/init.qcom.post_boot.sh sets interactive on most (all?) ROMs, regardless of what the kernel is set to.
[Sprint Samsung Galaxy S III] freecharlesmanson:
Unless I'm missing it in the source it there is a section around line 535 mentions for each cpu sampling each one in the same sample or jiffy as it says

So you are saying you can observabley show CPU1 doing something completely different then CPU0?
[Sprint Samsung Galaxy S III] fluk321:
Advice Taken better scores.

I took Freecharlesmason's suggestions on Ktoon governor tweaks and IO settings and it's been working out fine for me, on my Sprint SGSIII. Somehow UV doesnt work and that or something kills antutu benchmark from running. I cant figure that out.

I seem to only be able to run Antutu with the settings from page 1 at 1.5 mhz, I dont know what happened but after initial test it FC before the benchmark runs, but scores better it seems at 96 - 1512 mhz range.
[Sprint Samsung Galaxy S III] decimalman:
Sampling is scheduled for the same time across all processors, but core 1's governor instance doesn't actually communicate with core 2's. Their cpufreq_policy and cpu_dbs_info_s data structures are separate (although dbs_tuners_ins is shared across all instances of the governor), and they don't explicitly communicate.

Yes, I can show the two cores doing completely different things. This is a good thing, and should allow for better power savings if taken advantage of. Qualcomm calls this aSMP, and it's one of the selling points of the S4 SoC. Google it.
[Sprint Samsung Galaxy S III] mw86:
Ive been watching activity a lot and will continue to.

Current tunings still being worked on (turns core 2 on same as frequency up, drops frequency and hotplug at same time)

I think media scanner was running so higher load but you get the idea.

Last setup (turns core 2 on early before raising frequency and then drops frequency first then drops core 2 once at idle not before)

Not all at once but monitoring tools i use cool tool, trepn profiler, Perfmon, micro cpu monitor, cpu spy/spy plus, Android Tuner (fuller version of System Tuner)

One thing freecharlesmanson i can't get mpdecion disabled its always running still how do i turn it off im not sure if what i typed in terminal was right? It should show in the running process list using developer option to see cpu usage right?

Edit: made a small adjustment to the threshold slightly and this is the new set up i am working on like the first pic above.

Its really working good to drop first core to lower mhz under load while dual core is calculating when it would be beneficial and cutting out when starting to idle. You see the graphs are much smoother especially core one and core two you see is turning off plenty more but still as much a benefit over my last set up. I feel its going to get best of both worlds. Still need time to see how it does longer.

Three more pics. When trepn is off its running 96mhz.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
I think it should be just

Stop mpdecision

Sense inserting it into a script I never have seen then behaviors again or CPU time accumulated so I'll go with it's gone
[Sprint Samsung Galaxy S III] mw86:
Wow huge difference i see now. The other night it never worked. I couldn't get it to work still until i entered all of that in lower case. Thanks now i can actually tune this and know what is happening.

Btw freecharlesmanson anything in 4.2 android that would be newer than aosp linux? Would going to 4.2 be most optimized android right now? Core 2 is acting more like it should for how i have it set now. Thanks again

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
You have been very busy :D would love some more fine tuning on mine, where do I start? I guess back a page or so ;)

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] freecharlesmanson:
Android 4.2 is very incremental but they added tip top features like daydream. I really don't see underlying performance being hugely different. Not from anything I heard. I'm sure it will be alittle better
[Sprint Samsung Galaxy S III] fluk321:
which settings you use?

I just want to know what settings are everyone tinkering with, i cant find where ppl say mpdecision is and cant get 96-2106 mhz to run without apps force closing.
[Sprint Samsung Galaxy S III] clothednblack:
96 at screen off, that's what mine idles at

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] GTOJim:
I can't help with the settings that are people are using in this thread, but there is another thread that has some settings I have used that work well for me and some others. I'm conservative, OC to 1728mhz even though phone seems stable at 2106mhz.

http://xdaforums.com/showthread.php?t=1963153

It's quite possible your phone won't overclock to 2106mhz and be stable. If you want to overclock first try a slight overclock for a few days and see if things are stable. If stable bump up the speed a little repeating the process.

Good luck
[Sprint Samsung Galaxy S III] clothednblack:
Exactly what he said, all phones run different. This runs perfectly for me, and under volted everything

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Best answer other than all phones are different is start with no undervolt. Next let us know what rom you are on maybe the force close is rom or app related if no undervolt is used. Next try a small undervolt maybe - 10mv on all step in ktweaker working try for 25mv still working go by only 5mv more at a time. Whwn you see issue go back to last stable and add 10mv back and call it good. For 1998/2106mhz the only frequencies i recomend setting even if no others at - 25mv less minimum and preferred - 50mv. So 2106mhz 1300mv instead of 1350mv but better yet is 1290mv and same for 1998mhz drop - 50--60mv

Paranoid Galaxy S3 on Tapatalk 2

---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------

If you're looking to do anything in particular what might that be?

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
It's always about battery life and smooth performance :)

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Exactly and true for all of us. Only a few care about battery life before all else. Those usually always use a low max mgz because under steady load it tends to draw less power than the faster mhz... Its a toss up though because depending if not gone too far faster mhz finish workload faster making it hard to discern if one or the other saved more power.

Are you still adjusting i think is what i am asking. Im working on an improvement on my governor tunables myself im posting them tommorow. Many people are also using freecharlesmanson tunables with great results too.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
The only thing I haven't messed with is the i/O scheduler adjustments, everything else is tinkered :D

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Many are using bfq with all the latency adjust for platter hds disabled wirth a one or zero it runs fast.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] fluk321:
These setting work for me!

Im running Pacman Rom v.18 96-1809mhz bfq IO with Freecharlesmasons settings and rom running smooth good benchmarks, mflops range from 133 to 156, touchwiz i get 275 to 335.
[Sprint Samsung Galaxy S III] mw86:
Yeah touchwiz is scoring higher in linpack and Quadrant bench and Antutu is scoring higher on AOSP. Chainfire java is higher on Touchwiz. Vellamo is scoring higher on AOSP. Seems to depend on what is being tested. Also since aosp isnt running any slower at same speed its either touchwiz is scoring too high a score or aosp is scoring to low a linpack but in anycase the actual handling should be the same at the same frequencies. Touchwiz has a more optimized vm but aosp has newer linux built underneath. Both are good.

I have used Paranoid since dawn of time lol now i just loaded PACman or whichever and i am in love lol. AOKP and PA what more could we want.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] Logix:
I want more commits problem with pac is it dosent have the newest nightlys and some stuff is still borked and the ril is not that good from that build
[Sprint Samsung Galaxy S III] mw86:
I came from the latest Pa Kbizzle updates and it took a bit to set up but i am having no probs. I haven't used any bluetooth stuff but Kbizzles temporary release for sprint in the pac thread works great. I haven't used the latest nightlys ive been on latest PA since PA was posted here first for sprint by Kbizzle. Cool either way.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] fluk321:
I'll be looking forward to those settings. I believe it was one of your post those peaked my interested in this area, and I've been tuning my governor since then. It opened up a whole new area for me in terms of playing with my SGSIII, wish I would of knew these things when I had mu OG EVO 4g.
[Sprint Samsung Galaxy S III] mw86:
Guys continue to follow this thread but now go here to check latest tunings all in one post. Galaxyman did us the honors of combining much of our discussions here. So stop in for the current set up and friendly advice on basic tweaks.

http://xdaforums.com/showthread.php?p=35101228

Here is our other discussion thread too.

http://xdaforums.com/showthread.php?p=35112065

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] newworld:
Awe, now I know what it all means. Was clueless before. Appreciate the explanation.
[Sprint Samsung Galaxy S III] mrgodai:
i noticed setting up_threshold_hotplug to 100 and down_threshold_hotplug to 98 (99 wont stick) pretty much turn the 2nd core off.

performance remained the same for me and now my phone is very cool to the touch as if it's off. testing battery now.
[Sprint Samsung Galaxy S III] mw86:
Actually once core two shuts off it doesnt matter what you had hotplug down at as in even 11 would shut it off moment it became idle. Yes i mentioned in these threads that hotplug 100 disables core two as long as mpdecision is turned off as you could see core two for microseconds flash on. 99 hotplug up keeps hotplug functionality and thats what i use so core two comes on at the heaviest load i can have it turn on at.

Theres no prob if you plan to use your phone in single core just know under heavy use it will get more done with less work or energy in two core on heavy processes. If you plan to browse and use phone lightly its a great idea to keep phone cool and save a lot of energy. As long as you find it doesn't bog down on what you do thats a good viable solution to extend battery life and lower the total heat of phone.

Cool idea if thats how you use your phone.

Id like a second governor programmed to that id set it to screen off and use Ktoonservative on my settings for screen on.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
Yep I'm doing 80up hotplug no ill effects seen so far.....
[Sprint Samsung Galaxy S III] totestotes:
Does ktoonservative allow deep sleep?

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

Another question, does enabling auto hotplug for non hotplugged govs in ktweaker affect ktoonservative in any way?
[Sprint Samsung Galaxy S III] mw86:
Yes ktoonsez kernel allows deep sleep.

Only enable auto hotplugging on governors with no hot plugging logic built in. Governors with hotplugging Ktoonsez disabled the effect even if autohotplug is checked as they should not be used together. So do not use auo hotplug option on for example Ktoonservative governor.
[Sprint Samsung Galaxy S III] totestotes:
Okay. Thanks for clearing it up for me. I'm really enjoying this kernel!
[Sprint Samsung Galaxy S III] Near_07:
Galaxy note 4 (question)

hello guys i am using Ultimate kernel and i found Ktoonservative governor here, i just want to ask if bellow my settings is ok? or it is not ok? i also apply some of the advice in this thread, i just also want to know if ktoonservative and ConservativeX is a good partner? i also heard that:

"In my test ktoonservative governor is not battery friendly altough some cores sometimes stop. But it has very good performance. (Geekbench test = 4500) I think cores restart consumes much battery than steady works" - is this true?

Note 4 exynos has 8 cores what i like about this governor is some cores will stopped and thought to be a good battery saver.
[Galaxy Y GT-S5360 General] Fallen_Knight:
can anyone please decompile this apk and compress to zip and upload here...

i cant decompile cause apk manager quits whhen i try to decompile it...

this is ucweb moded for free internet in the Philippines using globe network

UCBrowser7.2 Globe MGC

its working fast...can anyone try to find where is the edited server??
[Galaxy Y GT-S5360 General] Mohamed.Anwar:
Here you go :

http://www.mediafire.com/?m538c19yw778ye5

Press Thanks
[Galaxy Y GT-S5360 General] Fallen_Knight:
oh man..you just extracted it..please decopile not extract...
[Galaxy Y GT-S5360 General] sasuketobi:
http://db.tt/SAdyYzhS

There you go

Tapatalk on Evo-x 2.1 @ SGY
[Galaxy Y GT-S5360 General] Fallen_Knight:
Please decompile this also....cant find a way to decompile it on my netbook...

download and decompile thhen uplload me
[Galaxy Y GT-S5360 General] anasdcool71:
Dude, this is a forum to learn. This is not a place where everyone will do the work for you. Use apktool to decompile.

System.out.println("Sent from my SGY");
[Galaxy Y GT-S5360 General] Fallen_Knight:
im not just a noob..i know how to decompile but this apk is giving me head ache cause when i try to decompile it. it just closes apktool or apk manager. it seems like my netbook aint powerful. i have my desktop but my ram stick is fried so im askin for help..can you help? xda is a forum of sharing and helping
[Galaxy Y GT-S5360 General] Crackion:
So didn`t you got it the decompiled yet??
[Galaxy Y GT-S5360 General] Fallen_Knight:
not yet. can you help? unlike the other one commented but did nothing..
[Galaxy Y GT-S5360 General] anasdcool71:
Don't be so ungrateful. Alright, i'm decompiling for you and giving you the decompiled folder, for once. The folder is in a zip file.

Get the files here.

But remember this :-
[Galaxy Y GT-S5360 General] Fallen_Knight:
ok thank you...finally...but remember this dont judge a man to be a fool because one day youll also be judge as a fool..adios my friend...
[Galaxy Y GT-S5360 General] -CALIBAN666-:
Youre good member with great heart bro.

MANY GREEEEETZ!!!