Reason for this thread is for general discussion about the Blissful kernel, and what settings users are having the best experiences with the kernel. Please limit thread discussion to only the kernel and not about BlissPop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
General Features
CPU OC/UC 35MHZ/2899MHZ
CPU OV/UV
GPU OC/UC 110MHZ/700MHZ
MSM LIMITER
POWER-EFFICIENT WORKQUEUES
INTELLITHERMAL
FAUXSOUND
WAKE GESTURES
USB FASTCHARGE
UKSM
CPU GOVERNORS
DARKNESS
BARRY_ALLEN
ALUCARD
ZZMOOVE
WHEATLEY
SMARTMAX
POWERSAVE
NIGHTMARE
LULZACTIVEINTERACTIVE
INTELLIACTIVE
IMPULSE
HYPER
HELLSACTIVE
ELEMENTALX
DESPAIR
DANCEDANCE
CONSERVATIVE
BLU_ACTIVE
PERFORMANCE
LIONHEART
BIOSHOCK
HOTPLUGS
INTELLIPLUG
BRICKED HOTPLUG
ALUCARD HOTPLUG
MAKO HOTPLUG
I/O SCHEDULERS
NOOP
DEADLINE
ROW
SIOPLUS
SIO
CFQ
BFQ
FIOPS
ZEN
TCP CONGESTION CONTROL
HTCP
RENO
BIC
CDG
CUBIC
WESTWOOD
HIGHSPEED
HYBLA
VEGAS
VENO
SCALABLE
LP
YEAH
ILLINOIS
Kernel Source
https://github.com/TeamBliss-Devices/blissful_shamu_kernel
Contributors
apophis9283, pimpmaneaton
Reserved
Reserved if needed
Reserved
I use Barry Allen governor with Mako hotplug.. Max frequency 2649 minimum 35.. Been getting decent battery life with this setup. Keep up the good work fellas.
Sent from my Nexus 6 using Tapatalk
JohnnyMontana_ said:
I use Barry Allen governor with Mako hotplug.. Max frequency 2649 minimum 35.. Been getting decent battery life with this setup. Keep up the good work fellas.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I use Nightmare, uc'd to 23mhz and oc'd to 2899. Using alucard hot plug. bfq i/o scheduler.gpu is u/c to 110mhz and oc'd to 700mhz and msm-adreno-tz gpu governor. Highspeed for tcp congestion control.
apophis9283 said:
I use Nightmare, uc'd to 23mhz and oc'd to 2899. Using alucard hot plug. bfq i/o scheduler.gpu is u/c to 110mhz and oc'd to 700mhz and msm-adreno-tz gpu governor. Highspeed for tcp congestion control.
Click to expand...
Click to collapse
Nice.. Could you guys maybe link a wiki in the OP about the governors and such for users to reference? Would be nice to be able to quickly get an explanation of what all the different features do. Just a suggestion not a must have.
http://androidmodguide.blogspot.com/p/blog-page.html?m=1
This is a good one.. Thanks to whoever made it.
Sent from my Nexus 6 using Tapatalk
apophis9283 said:
I use Nightmare, uc'd to 23mhz and oc'd to 2899. Using alucard hot plug. bfq i/o scheduler.gpu is u/c to 110mhz and oc'd to 700mhz and msm-adreno-tz gpu governor. Highspeed for tcp congestion control.
Click to expand...
Click to collapse
Any settings specific for the alucard hotplug? Or just the default?
Sends like the biggest art is setting the hotplug ie especially mako
jcrompton said:
Any settings specific for the alucard hotplug? Or just the default?
Sends like the biggest art is setting the hotplug ie especially mako
Click to expand...
Click to collapse
I switched to alucard governor and plug. Everything default and running beautifully
apophis9283 said:
I switched to alucard governor and plug. Everything default and running beautifully
Click to expand...
Click to collapse
I think after about 20 hours with this setup I'd say that it seems to have improved screen off battery usage and it really is snappy with typing and key entry and system navigation. May have increased screen on drain just a bit.
Not sure if due to setup but Tapatalk has a bit of a stutter with scrolling
Related
Just curious guys, what do you have your Glacier running on for overclock? I'm running CM7 if it makes a difference.
Sorry I'm such a noob with android, I'm just wondering what people are running. Also does it affect the battery?
Sent from my HTC Glacier using XDA App
Runing my phone at 768.
[sent via Cyanogen powered Android]
High 13000 low 264 smartass gov
Sent from my HTC Glacier using XDA Premium App
Im overclocked at 1.1 ghz max & 245 min smartass... Battery life great & speed FAST lol... The higher u go less battery life u'll have....
Permrooted S=off-MyTouch 4g-White
Eng-0.85.2007
Clockwork Recovery-3.0.2.4
Rom-RoyalGinger v1.4.1(Gingerbread baked just right : } )
for everyday use I run mine at 1113/245 (default for faux's kernels) with smartass governor. only time I take mine any higher is for showing off/crushing someone's spirit (usually Evo and Galaxy S fanboys).
neidlinger : how well does your's run at 768, do you see much lag?
RavenWulf said:
for everyday use I run mine at 1113/245 (default for faux's kernels) with smartass governor. only time I take mine any higher is for showing off/crushing someone's spirit (usually Evo and Galaxy S fanboys).
neidlinger : how well does your's run at 768, do you see much lag?
Click to expand...
Click to collapse
i also run at 768 its perfect for moderate use(texting, Music)
RavenWulf said:
neidlinger : how well does your's run at 768, do you see much lag?
Click to expand...
Click to collapse
Nope non at all. In fact it still blows a coworkers iPhone 4 on most day to day task. And another co-worker has a DroidX and was shocked when I told him it was underclocked
[sent via Cyanogen powered Android]
I'll have to give it a run for a few days then and see how it stands up to my usage, mostly calls, texting and wi-fi tethering my netbook when I park my rig for the day.
thanks for the heads up on how well y'all are doing on underclock, are you guys running a "stock" volt or low volt kernel?
didn't mean to thread-jack but figured I get as much info as I can while everyone seems to be in such good moods
I run 1305 max, 245 min at 100% and 1075 max, 245 min at 50% with 245 max, 245 min on screen off.
Sent from my HTC Glacier using XDA Premium App
On CM7 using faux123's low-voltage kernel, 1.2 GHz max / 245 MHz min, smartass governor. Battery life is awesome.
EDIT: On CM6 I was using SetCPU on min 245 / max 1209 with the following profiles, in order from highest to lowest priority:
Code:
SCREEN OFF
min 245 / max 368
BATTERY TEMP > 120F
min 245 / max 768
CHARGING
min 245 / max 1305
BATTERY PERCENT < 21%
min 245 / max 1024
BATTERY PERCENT < 41%
min 245 / max 768
Of course, CM7 does not need SetCPU.
1017 Max / 245 min
Plugged in 1209 Max / 245 min
768 245 smart ass
Sent from my HTC Glacier using XDA App
I'm running 'stock' 1.1, smartass, in CM7. I setup a profile to scale back (786 I believe) once the battery gets low. My battery life is excellent.
I am running 1.459, I think max and 378 or close min. Stock rom with faux sense kernal. Battery life is really good and I get 2000+ on quadrant.
Sent from my HTC Glacier using XDA Premium App
jdkoren said:
Of course, CM7 does not need SetCPU.
Click to expand...
Click to collapse
sorry for the noob question, but "why not"? I'm running CM 7.0.3 and in the performance settings I can only specify one set of CPU speeds, not different profiles like in setCPU ...
1017 max 122 min
Govenor Superbad
Demonspeed kernel 2.6.35.14 INSANITY v6 CM7+
awesome kernel amazing battery life superbad so smooth!! lol
I have one of my MT4g's running @:
Max=1708
Min=1017
Set on boot = off (Just in case)
I haven't had any issues and it runs so amazingly smooth.
demonSPEED INSANITY v6 on MIUI 1.8.19, 1209/122 superbad. great battery life and performance, 20+ hours on a full charge
1.4GHz Max/122Mhz Min, on MIUI, I may go for 1.5GHz, on miui these clock speeds are just insane, just plain overkill
1017/122-Superbad gov.
Seeing great battery life.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok so it is very hard to find dedicated threads to this and I think the more of us trying this and reporting back to one thread, the more successful we will be in achieving great battery life or performance (i do it for battery life)
Here's what i have found to work well today, just some simple adjustments but my battery didn't drop a single percent for about 1.5 hours of very light use(still great tho).
MAIN TAB
Setting the Scaling to: Conservative
Max: 1000MHz
Min: 100MHz
PROFILES TAB (i only have one profile set):
Screen off - Max: 400 (don't go lower, your phone wont wakeup)- Min: 100- conservative - Priority 50
ADVANCED TAB(minimal changes, but i feel they have helped a bit):
Sampling Rate: 20000
Up Thresh: 80
Down Thresh: 25
Ignore Nice: 0
Freq Step: 20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These may not be the best settings as we will play guess n check, but thats the reason of this thread, lets figure these things out.
You need root permission's for this, correct?
driftnut56 said:
You need root permission's for this, correct?
Click to expand...
Click to collapse
yessir you do
You should look into the smartass governor if you want to look for screen off frequencies. SetCPU only wastes CPU cycles for you to do this when a kernel can do it. Of course, I believe the end result is that you're still saving more battery, so at least it's a step forward
I'm overclocking 1.2 ghz. Switching between interactive and conservative.
Conservative has better battery life, but interactive is a bit snappier.
I'm new to the setcpu thing; gathered bits and pieces here and there to try and find the perfect settings.
Great thread though, hopefully people will post so we can take full advantage of this beast!
BTW, Tried to post screenshots, but I need more forum activity.
Had no success with conservative myself it allows the clock to step down to 100 eventhough I have the minimum at 200. The smart ass works like a charm no more lock screen lag
Sent from my Nexus S 4G using Tapatalk
teddybrukshut said:
I'm overclocking 1.2 ghz. Switching between interactive and conservative.
Conservative has better battery life, but interactive is a bit snappier.
I'm new to the setcpu thing; gathered bits and pieces here and there to try and find the perfect settings.
Great thread though, hopefully people will post so we can take full advantage of this beast!
BTW, Tried to post screenshots, but I need more forum activity.
Click to expand...
Click to collapse
Hi. I am new to over clocking with SetCPU. How did you get it to go over the 1000 max? I don't understand all of the other settings enough to feel brave enough to change them other than the first tab.
Thanks
ArizonaLoco said:
Hi. I am new to over clocking with SetCPU. How did you get it to go over the 1000 max? I don't understand all of the other settings enough to feel brave enough to change them other than the first tab.
Thanks
Click to expand...
Click to collapse
You have to flash a custom kernel (i recommend netarchy's kernel), then when you open setcpu, you can "autodetected recommended settings". You will then see the ability to overclock.
itsallsubliminal said:
Ok so it is very hard to find dedicated threads to this and I think the more of us trying this and reporting back to one thread, the more successful we will be in achieving great battery life or performance (i do it for battery life)
Here's what i have found to work well today, just some simple adjustments but my battery didn't drop a single percent for about 1.5 hours of very light use(still great tho).
MAIN TAB
Setting the Scaling to: Conservative
Max: 1000MHz
Min: 100MHz
PROFILES TAB (i only have one profile set):
Screen off - Max: 400 (don't go lower, your phone wont wakeup)- Min: 100- conservative - Priority 50
ADVANCED TAB(minimal changes, but i feel they have helped a bit):
Sampling Rate: 20000
Up Thresh: 80
Down Thresh: 25
Ignore Nice: 0
Freq Step: 20
These may not be the best settings as we will play guess n check, but thats the reason of this thread, lets figure these things out.
Click to expand...
Click to collapse
i used following profiles and UV settings...
still looking into it though...
http://caleb1783.tistory.com/196
I'm not using setcpu. It causes launcher pro to freak out for me. Installed CPU master and all is perfect. Running matr1x 7.5 @1.3 jiggawatts with the smartass v2 governer. Also I'm on gpa17 at the moment.
sent from my Touchwiz'd Nexus S 4g
What is the default CPU min/max frequencies and the governor being used? (on stock kernel)
My guess is that the max is 1512 and min is 384. But I'm really not sure what governor is used by default.
Anyone know?
Ondemand
Sent from my Nexus 4 using XDA Premium HD app
Defaults are as follows:
MIN: 1026MHz
MAX: 1512MHz
CPU govenor: ONDEMAND
xandr00 said:
Defaults are as follows:
MIN: 1026MHz
MAX: 1512MHz
CPU govenor: ONDEMAND
Click to expand...
Click to collapse
The default minimum is 1026??? Are you sure? Why would it be set to keep running so high? I heard that it doesn't fall from 1026 to 384 easily until 5-6 seconds have passed...but if 1026 is the minimum..then, smh
Is the default I/O CFQ?
Max - 1512
Min - 384 (CPU Apps don't show it correctly)
Govenor - Ondemand
I/O - Noop
Harry GT-S5830 said:
Max - 1512
Min - 384 (CPU Apps don't show it correctly)
Govenor - Ondemand
I/O - Noop
Click to expand...
Click to collapse
The fact that CPU apps don't show the minimum frequency properly, and the fact that it hangs on 1026 for a few seconds before dropping to 384...do you think that indicates a problem?
I don't know if the minimum is actually 1026 or not but I know for a fact that when you TOUCH the screen, it does ramp up to 1026. So that can be a explanation why battery life isn't as good in reviews.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zephiK said:
I don't know if the minimum is actually 1026 or not but I know for a fact that when you TOUCH the screen, it does ramp up to 1026. So that can be a explanation why battery life isn't as good in reviews.
Click to expand...
Click to collapse
I remember with my i9300, as soon as you touched the screen, it would ramp up to 800mhz. It has to do with project butter. It does keep everything running smooth, at the cost of battery life.
K Rich said:
I remember with my i9300, as soon as you touched the screen, it would ramp up to 800mhz. It has to do with project butter. It does keep everything running smooth, at the cost of battery life.
Click to expand...
Click to collapse
never heard such of a thing on the galaxy nexus (might of been present but no one ever mentioned it so im not sure how GN reacts to that). first time ive heard of it.
battery life has been nothing but exceptional for me on N4 and GN. didnt notice a difference between 4.1 and 4.0.x for battery life. it stayed the same or slightly gotten better.
i recommend using franco kernel though
zephiK said:
never heard such of a thing on the galaxy nexus (might of been present but no one ever mentioned it so im not sure how GN reacts to that). first time ive heard of it.
battery life has been nothing but exceptional for me on N4 and GN. didnt notice a difference between 4.1 and 4.0.x for battery life. it stayed the same or slightly gotten better.
i recommend using franco kernel though
Click to expand...
Click to collapse
I agree completely, battery life has been great. Just letting others know what might be the cause for "bad" battery life from past experiences
This thread is for posting and discussing ones kernel settings.
TIP 1#
To prevent random reboots, turn the the default undervolting off in options and tick set on boot (sorry can't provide screenshot right now)
Dont know if its the best way to configure it but heres mine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AndreAkaNick said:
Dont know if its the best way to configure it but heres mine.
Click to expand...
Click to collapse
What ROM/Theme u are using ?
pedromms86 said:
What ROM/Theme u are using ?
Click to expand...
Click to collapse
CM11, MIUI6 Theme and Xposed Flat Style Module for the status bar.
Aronuser said:
TIP 1#
To prevent random reboots, turn the the default undervolting off in options and tick set on boot (sorry can't provide screenshot right now)
Click to expand...
Click to collapse
This does nothing. The Random Reboot problem is a problem with the kernel itself.
If anyone have problems with F4k kernel just use stock cyanogenmod kernel.
iFlasher said:
This does nothing. The Random Reboot problem is a problem with the kernel itself.
If anyone have problems with F4k kernel just use stock cyanogenmod kernel.
Click to expand...
Click to collapse
well i remember that i had random reboots and i disabled that, so it stopped. i thought maybe the chips data became buggy because of low voltage
I'm using smartmax with fiops , 182-1458 mhz very battery friendly. Any other good settings ?
Ursurobertt said:
I'm using smartmax with fiops , 182-1458 mhz very battery friendly. Any other good settings ?
Click to expand...
Click to collapse
i use fiops too cause it's improved for flash drives and i've freq from 162-810 mhz it's still smooth enough for messaging and browsing and maximum battery saving i think. i also have multi core power saving at "on" cause i think it's useful
AndreAkaNick said:
Dont know if its the best way to configure it but heres mine.
Click to expand...
Click to collapse
Wht app is this
Sent from my unknown using XDA Free mobile app
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
Aronuser said:
i use fiops too cause it's improved for flash drives and i've freq from 162-810 mhz it's still smooth enough for messaging and browsing and maximum battery saving i think. i also have multi core power saving at "on" cause i think it's useful
Click to expand...
Click to collapse
If you're like me who likes to game n also save battery life,
Max: 1Ghz
Min: 162mhz
Governor: Smartmax
I/O: FIOPS
I too switched Multicore power saving. Ran Asphalt 8 in Very low graphics (since i find special effects to be annoying) and it works smooth. Very minor stutter.
Sent from my unknown using XDA Free mobile app
TiTAN-O-One said:
Wht app is this
Sent from my unknown using XDA Free mobile app
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
If you're like me who likes to game n also save battery life,
Max: 1Ghz
Min: 162mhz
Governor: Smartmax
I/O: FIOPS
I too switched Multicore power saving. Ran Asphalt 8 in Very low graphics (since i find special effects to be annoying) and it works smooth. Very minor stutter.
Sent from my unknown using XDA Free mobile app
Click to expand...
Click to collapse
Faux123 Kernel Enhancement Pro ?
I typically set min CPU freq to 162 and max to 1458 with Wheatley Governor.
I/O:Fiops
Disable MPDecision, and enable msm-hotplug
Hyst value 4/threshold-722.
Entropy read_1024 write_2048
Post your best score on Antutu you got till on your Nexus 7 2013!
Let's see who can beat the current score![emoji1]
Mine is 32212!
It was obtained with Simple AOSP(5.0.2)+Glitch Kernel(AOSP) at 1.7Ghz OC CPU and GPU at 500MHz and was preety smooth too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock rooted 5.0.2 with Glitch Kernel r307 @ CPU 2000 mhz and GPU627 mhz. Not bad at all .
pk-sanja said:
Stock rooted 5.0.2 with Glitch Kernel r307 @ CPU 2000 mhz and GPU627 mhz. Not bad at all .
Click to expand...
Click to collapse
I lost!
You are the man!
What the heck over clock that is!
Any performance glitch in real life on that setup?
AnkeshReborn said:
I lost!
You are the man!
What the heck over clock that is!
Any performance glitch in real life on that setup?
Click to expand...
Click to collapse
It's quit stable in real life usage but with higher battery draining . Next time i would like to try with 2,1ghz vor 2,2ghz.
pk-sanja said:
It's quit stable in real life usage but with higher battery draining . Next time i would like to try with 2,1ghz vor 2,2ghz.
Click to expand...
Click to collapse
Let me know!
I managed to get a score of 31958. Running cm12 with the glitch kernel. Overclocked to 1890 ghz. No quite as fast as you but close
---------- Post added at 04:12 PM ---------- Previous post was at 03:59 PM ----------
Overclocked to 1944 ghz and got a score of 32058. Nearly
AnkeshReborn said:
Let me know!
Click to expand...
Click to collapse
So new Update!
Setup: CPU 2,1Ghz, GPU 600mhz, Lbus OC Glitchy.
Impressive but it doesn't scale good any more.
Wow that's high. Don't think I can beat that
andyskelly said:
Wow that's high. Don't think I can beat that
Click to expand...
Click to collapse
Pk sanja beated me,I cri!
pk-sanja said:
So new Update!
Setup: CPU 2,1Ghz, GPU 600mhz, Lbus OC Glitchy.
Impressive but it doesn't scale good any more.
Click to expand...
Click to collapse
Can you post the latest ones with your kernel settings again and a screeny too of 34k!
•Hit thanks if I helped you..
AnkeshReborn said:
Can you post the latest ones with your kernel settings again and a screeny too of 34k!
•Hit thanks if I helped you..
Click to expand...
Click to collapse
Sure
My DD
ROM: Latest GROGGS88 AOSP ROM
Kernel: Glitch r320 with 1,7Ghz 1050mV, GPU 600mhz with -150mV, OC-BUS glitchy and everything else off.
pk-sanja said:
Sure
My DD
ROM: Latest GROGGS88 AOSP ROM
Kernel: Glitch r320 with 1,7Ghz, GPU 600mhz, OC-BUS glitchy and everything else off.
View attachment 3211817
Click to expand...
Click to collapse
No Undervolt?
•Hit thanks if I helped you..
AnkeshReborn said:
No Undervolt?
•Hit thanks if I helped you..
Click to expand...
Click to collapse
Of course undervolt, i forgot, i will edit my post .
Sorry to revive this thread but i was surprised with improved performance.
In Antutu:
47542 (Configuration 24/7)
51961 (Configuration only to Benchmark...cpu min 1500mhz)
I have red numbers in my second test... why? Fail?
I use CM13 + Glitch r520
1998MHz max/81MHz min/Intellidemand/gpu 600MHz/noop
Thanks to all devs in XDA, without them our devices would not be the same.
Edit: 53295 in Configuration 24/7 but with Interactive governor.
Chrisis25 said:
Sorry to revive this thread but i was surprised with improved performance.
In Antutu:
47542 (Configuration 24/7)
51961 (Configuration only to Benchmark...cpu min 1500mhz)
I have red numbers in my second test... why? Fail?
I use CM13 + Glitch r520
1998MHz max/81MHz min/Intellidemand/gpu 600MHz/noop
Thanks to all devs in XDA, without them our devices would not be the same.
Edit: 53295 in Configuration 24/7 but with Interactive governor.
Click to expand...
Click to collapse
I'd like to try your setup with CPU 1998MHz max/81MHz min/Intellidemand/noop & gpu 600MHz. What is your undervolt for CPU and GPU (-mV value) ? Do you use any other options for mpdecision, etc. ?
idCyber said:
I'd like to try your setup with CPU 1998MHz max/81MHz min/Intellidemand/noop & gpu 600MHz. What is your undervolt for CPU and GPU (-mV value) ? Do you use any other options for mpdecision, etc. ?
Click to expand...
Click to collapse
Config at your own risk!!
I use:
Rom: CM13 nightly 27-08
Kernel: Glitch r520
Kernel Auditor:
Freq Max: 1998
Freq Min: 81
Governor: Interactive
Undervolt: No :crying:
Intelliplug: ON
Profile: Balanced
Hysteresis Value: 6
CPU treshold: 720
CPU max screen off freq.: 810
MSM Hotplug: ON
Debug Mask: OFF
Maximum CPU Online: 4
Minimum CPU Online: 1
Maximum CPU Screen Off: 2
CPU Boosted: 4
Down Lock Duration: 500
Boost Lock Duration: 2500
Update Rate: 10
History size: 10
Offline load: 0
Fast Lane Load: 400
Suspend Defer Time: 10ms
IO is Busy: ON
WARNING! Thermal options
Intellithermal: ON
Core Control: ON
CPU Throttle Temp.: 69 :angel:
Frequency Throttle Temp: 60
Poll: 250ms
Thermal limit Low: 1
Termal Limit High: 26
GPU: 600mhz
Governor: ondemand
I/O scheduler: noop
Read ahead: 2048
I/O Stats: ON
RQ Affinity: 1
Dynamic Fsync: ON
Gentle fair sleepers: off
arch power: off
ufff! hahahah