when i use 729 or above my Cpu stops working and its Reboot automaticaly any way to fix
Unfortunately you can't fix it. The overclock ability of the cpu is different in each phone. Some x8 can run on 800+ MHz, some can't reach frequencies over 700MHz. Basically the SoC (the cpu, gpu, dsp and some other device) contains millions of transistors, but the whole chip is only ONE small piece of silicium, the transistors made by litographic and other complex (and expensive) procedures. The overclock ability depends on the material quality (damages in the silicium structure), soldering quality between the core and the casing, etc. So, no existing rules to the overclock, if you lucky you can reach high frequencies, if you unlucky you can't overclock.
Note: under the manufacturing procedure the chips get a selection after testing, the highest quality 7x27 chips marked and sold as 7x27T with default 800MHz.
There is an app in the market called No Frills CPU Control: https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU
It will automatically change your CPU frequencies during boot to save your phone from hard bricking.
Anyway CPU gets overheated by overclocking as more amount of power comes in to it than what is required. So as a long term effect your CPU will die out and also your Battery too. So I would say to use a faster rom and dont overclock the CPU to very high frequencies.
paulebe525 said:
when i use 729 or above my Cpu stops working and its Reboot automaticaly any way to fix
Click to expand...
Click to collapse
You are using stock kernel?
Overclocking more than 729 is not possible for stock kernel...
Use "set CPU" application & remember to uncheck "set on boot "option
# I couldnt over more than 729 in stock kernel but now with nAa kernel in can overclock up to 787 mhz
sent using" ultimate - ics - standard"
I Overclocked to 748 MHz on stock kernel....
Without any problem
sent from my W8 using client-server technology
governer also matters, I always use smartassv2
As someone wise already stated, better using something like FroyoPro which is blazing fast compared to any GB rom instead of overclocking.
I can do more with FroyoPro than anyone running GB, ICS or JB roms.
It's just simple - lighter code takes less cpu cycles therefore it is quicker.
GB, ICS and JB roms really are a waste of time once you've tried FroyoPro.
The other roms are really only good for proof of concept - not for everyday usage.
mujeeb999 said:
governer also matters, I always use smartassv2
Click to expand...
Click to collapse
I use
ondemand [email protected] [email protected] & using CPU under volt too
not very smooth but I don't care about smoothness
CtrlAltDelIrl said:
As someone wise already stated, better using something like FroyoPro which is blazing fast compared to any GB rom instead of overclocking.
I can do more with FroyoPro than anyone running GB, ICS or JB roms.
It's just simple - lighter code takes less cpu cycles therefore it is quicker.
GB, ICS and JB roms really are a waste of time once you've tried FroyoPro.
The other roms are really only good for proof of concept - not for everyday usage.
Click to expand...
Click to collapse
I tried it , it's not that much good:/ plus it have so many bugs with alfs kernel.(brightness bug for example)
I compared it with iXperia 8s rom before, froyopro is better @ one of 3d tests(just 2 fps better)
Other test were like iXpera & minicm7
Remember it's froyo & they are ginger ,they can run newer apps .
My opinion iXperia is our best rom till now
sent using" ultimate - ics - standard"
I use over 800 on CPU with smartassv2 with baa kernel
Sent from my E15i using xda app-developers app
senci00 said:
I use over 800 on CPU with smartassv2 with baa kernel
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
baa kernel , what the....?
Sent from my E15i using xda app-developers app
Mockingbird said:
baa kernel , what the....?
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
He means nAa kernel
Dictionary has changed the word , but wait why nAa is not in dictionary? It's super popular
sent using" ultimate - ics - standard"
CtrlAltDelIrl said:
As someone wise already stated, better using something like FroyoPro which is blazing fast compared to any GB rom instead of overclocking.
I can do more with FroyoPro than anyone running GB, ICS or JB roms.
It's just simple - lighter code takes less cpu cycles therefore it is quicker.
GB, ICS and JB roms really are a waste of time once you've tried FroyoPro.
The other roms are really only good for proof of concept - not for everyday usage.
Click to expand...
Click to collapse
I don't like the UI..otherwise I tried it and it sure was great.
Sent from my E15i using xda app-developers app
..
paulebe525 said:
when i use 729 or above my Cpu stops working and its Reboot automaticaly any way to fix
Click to expand...
Click to collapse
It also depends on the kernel you are using..Alfs is better in this aspect..but too much overclocking is not recommended.
if you are using custom kernel ,under CPU settings, select the frequencies you desire and do NOT select "Set on boot" . Even if your phone gets rebooted due to overclocking the default values will be applied at boot. This way you can avoid problems.
My X8 supports upto 787MHZ on nAa .
Hit thanks if i helped.
Just out of curiosity so upto how much can i overclock my awesome x8??
So far i've been to 729MHZ
Bunny2rock said:
Just out of curiosity so upto how much can i overclock my awesome x8??
So far i've been to 729MHZ
Click to expand...
Click to collapse
It depends on the kernel you are using..some people here overlocked @800Mhz successfully while my X8 got settled only at 787Mhz. Try yourself.
its nAa N is next to B ;-D
At 787hz doesn't restart
Mine work at 787 hz smoothly,,,,it restarts rearly...remember to have an app advanced task killer ...and set its setting to auto kill after screen turns off..Also set it to crazy kill....
Hope it will help you....
If I helped you,,,,don't forget to press thanks button..:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
please read 2nd post by pilu. that's the best explanation. it's a hardware limitation, and it does NOT depend on the kernel.
[cAs]
Partially depends from the kernel too. The cpu clock is not only a simple value: xyz mhz. In the kernel this is a little bit complicated (pll frequencies, dividers, multipliers, voltage level, etc). Different kernels use different frequency tables, the results can be different, this the developer choice who can set different bus speeds (axi, ahb), base pll, voltage to every clock speed. You only see the frequencies in the different kernels, what is same, but the same speed maybe generated with different method.
So, the cpu overclock ability is 90% hardware limitation and 10% other things. Usually if you reach your own max speed with a kernel, the probability of higher speed with another kernel is small, the typical difference is nothing more than +/- 1 multiplier (+/- 19,2 mhz).
Sent from my E15i using xda app-developers app
What kind of success/failure are people having with overclocking and undervolting?
I'm doing this through ROM Toolbox Pro. Is there a better way? I'm a n00b with some of this stuff.
I have the phone overclocked to 1200mhz and all cpu levels are undervolted by 100mV.
Im doing so to get more performance, and better battery life. Just wondering what settings everyone else is using.
Also I'm using CM 10.1, with the BlueMint Theme.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.
DR650SE said:
Just wondering what settings everyone else is using.
Click to expand...
Click to collapse
Every phone has different limits. It's just like PC overclocking, no two CPU/MB/RAM combos are exactly the same. In general most of Captivates will handle 1200 step OC with default voltages. Not too many will handle 120% live OC though. It doesn't matter what tool you use to OC. All tools try to play with the same kernel settings. In my experience UV saves very little battery but increases significantly the chances to get stability issues. This is why I never play with UV. My particular phone can do 1400 step OC or 1200 live OC with 1350mV. I run it on 1200 step OC @ default. Also, keep in mind that different ROMs/kernels give different OC results.
RE: undervolt
I agree with Val D that undervolting will not show any significant benefits. Overvolting has helped me with stability while overclocking. I use the free Voltage Control app for voltages, or the free NStools app. Rom Toolbox is a great app too- I use it for many other things- stick with what works for you. Currently I am running at 1200Mhz step, at 120% Live OverClock to get CPU up to 1440Mhz, and ARM voltage of 1350mV at that 1200Mhz step. Rock solid. Battery life suffers a bit, but I run this way for gaming. Day-to-day regular usage I just set to 1400Mhz step and no Live OC, default voltages. I have run fine in the past at 1500Mhz, no Live OC. Overclocking the CPU tends to make my phone a bit snappier and more responsive. A big battery drain that affects my phone is an app such as Gmail running in the background, or leaving wifi enabled when not in use. Setting the phone to Airplane mode has been a big battery helper too (I do not make any voice calls on this phone anymore). Governor and scheduler setting can also have a big effect on battery life. I searched for this post I made a while back that linked to two great articles on studies of battery life and voltages, and ended up reading through them again:
http://forum.xda-developers.com/showpost.php?p=28141250&postcount=1194
Great information. Edit: just figured out how to link articles in my signature.
Thanks guys. I know each one over clocks differently. Just looking for some rough outlines. Thanks for the links. I'll be reading up on those. I have extensive computer over clocking experience, but on e phone its a whole new ball game. Basically trying to make this phone last longer.
I'll have to learn what live OCing is vs step OCing.
Thanks again!
Sent from my GT-P3113 using Tapatalk HD
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
PxGold said:
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
Click to expand...
Click to collapse
Awesome. Didn't even realize that as there. I've been using ROM Toolbox to OC to 1200MHz.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.
overclocking to 1200 mhz will made any difference ?
Klitoni said:
overclocking to 1200 mhz will made any difference ?
Click to expand...
Click to collapse
I really didn't notice much of a difference in speed or responsiveness using CM 10.1.
Hi guys!! I was thinking about opening a thread where everyone can specify what's the better kernel setup, according to her/his own necessities, and share that configuration with all p880 community. Also, it can be submitted the relationship between the kernel and the ROM an user is running on the device, to compare performances and make each other more conscious about kernel tweaking. I think it's better to open it in general section, so everyone can write, without being scared by submitting something not related to developing.
This thread won't to be in any way a substitute of the "Battery life!" thread, so if anyone wants to post specifical results or screenshots about battery duration, please post them here:
http://forum.xda-developers.com/showthread.php?t=2478514
Said that, the idea is to post a message like this:
KERNEL: name of the kernel you are using
ROM: the name of the ROM you are running
SETTINGS: the kind of settings you applied to your kernel (example: Governor=interactive, Scheduler=Sio, Multicore Power Saving=2,CPUquiet=balanced, LP Core uV=-15 mV, MPU uC=+20, and so on)
GOOD: the benefits you experienced with your configuration (the more specific possible)
BAD: the badness you experienced with your configuration
Of course, if the thread begins to grow up, is recommended to read everything before posting a configuration too much similar to another which have been posted yet.
If you think this is a good idea, press thanks, if you want, and let's begin posting, otherwise report it to moderators, like @laufersteppenwolf, and they will close this thread as soon as possible
If someone like @JoinTheRealms is interested to, I'd appreciate very much to create a section dedicated to the scripts, as a second post of the thread, maintained and refreshed by the author.. Let me know, and take your own space here, if you think it's good for you!
So, I'm starting posting my own last configurations:
1)
KERNEL: iodak v9.95
ROM: Beanstalk 4.4.2
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=370 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-30 mV all frequencies, MPU uV=-75 mV all frequencies
GOOD: this configuration improve battery life, without decreasing overall smoothness - suggested to the users who don't mainly use the phone for hard gaming and want to find a compromise between battery durability and overall performance
BAD: some little lags, here and there, randomly happen - I suggest to apply underclock, before changing cpu freq voltage, because this configuration is good for 1300 Mhz undercloked device, but it may cause system freezes on some cpu variants, if you set cpu clock up to 1600-1700 Mhz (tested)
2)
KERNEL: iodak v10
ROM: Beanstalk 4.4.4
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=620 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-100 mV all frequencies, MPU uV=-100 mV all frequencies
This configuration is very battery friendly, more than the last one I was using on iodak v9.95. Nothing is slowing down, btw
@JoinTheRealms reserve a post to yourself, if you liked my idea to dedicate some space to scripts explaining
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Saved!
Lol, I'm using almost the same config.
Kernel: Iodak 9.9.5
Rom: Beanstalk 4.4.2
Settings: I haven't changed anything
Good: Very fluid and stable
Bad: battery life, Antutu 3D test score
Sent from my LG-P880 using xda app-developers app
Kernel: 9.95
Rom: CM11 official
Settings: Max Frequency 1150 Mhz Cpu governor:interactive
mpu undervolt -100 on every freq (cpu variant 2, some hangs while waking the smartphone and I need to tap on the screen sometimes, if I press the power button the device won't wake up anymore until I restart it).
Congestion: westwood
Cpu quiet: runnable
Cpu max screen off freq: 475 Mhz
Good: less heat, more battery life, smooth experience
Bad: If I put 1300 Mhz as max freq the battery life will decrease.. And without 1300 Mhz as max freq I feel like cutting this smartphone's cpu potential.
Still bad battery life even with these tweaks, still disappointed, but so far this is my best configuration with Cm11 official.
peppethustra said:
@JoinTheRealms reserve a post to yourself, if you liked my idea to dedicate some space to scripts explaining
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The scripts i posted earlier, really shouldn't be take too seriously, mainly because they are written for ubuntu and require input. But when i get some time ill modify my post and give some examples of init.d scripts, or more specifically, the commands inside them. That should be somewhat more helpful i guess
JoinTheRealms said:
The scripts i posted earlier, really shouldn't be take too seriously, mainly because they are written for ubuntu and require input. But when i get some time ill modify my post and give some examples of init.d scripts, or more specifically, the commands inside them. That should be somewhat more helpful i guess
Click to expand...
Click to collapse
Take the time you need, the thread seems beginning to live, so we'll read your post for sure, when you will bring it to evolution!
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Kernel: Optimus Play v2.53
Rom: CM11 official
Settings: Max frequency 1200 Mhz (sometimes I tried to put it at 1100 Mhz or even lower, 1000 Mhz, resulting in better battery life)
Congestion: cubic (since there's no westwood implementation in this kernel)
Cpu quiet: not implemented (I think it's put on runnable or balanced as standard)
Cpu governor: interactive
Multi-core battery saving: 1
Gpu frequency scaling: on
Good: awesome perfomances, the games and all the apps are very smooth and compared to the earlier configuration with iodak v9.95, this is very much better, but be aware that I'm trying to have perfomances and battery life balanced, and on iodak v9.95 I undervolted the cpu of -100mv resulting in some cases of hangs and crashes. Battery life is still good, but a bit worse than the iodak configuration.
Bad: Battery life's not very good, it goes harder on deep sleep when the display's off, iodak v9.95 is the best with deep sleep; in fact it takes a while before entering that state, it usually stays on low frequencies but it still consumes the battery.
An other aspect I noticed is that even when the smartphone is on charge, when I'm using it, it doesn't charge much, if ever it looses energy, which is explained by the very good performances of this kernel.
A small bug present in this kernel, and not in iodak, you usually need to double press the power button to wake the smartphone, but it's much better than risking to have your smartphone crashed while waking it up.
Overall: A very good kernel for performances, I don't know if it's the best but it's very good, battery life's "good" if not using the smartphone, otherwise it drains quite fast, I think faster than the undervolted configuration with iodak.
If you're looking for smoothness with games and apps I'd suggest this kernel, if you prefer battery life I'd suggest iodak more, but I remind you the hang problems on it if you decide to undervolt up to -100mv.
I tested both kernels with the same Rom and apps and use more or less, so I'm quite positive it's a good test.
I hope it helps and you can give us tips or suggestions to improve this smartphone's battery life, without losing perfomance. I think this is the thread's goal.
and yeah, every LG Optimus 4x hd possessor's dream is to have a good battery life so well, let's help each other and get the best out from this device, it's not **** yet in my opinion, it just really has a bad battery usage.
@KrisJoe Very good review! I hope many people will follow your example..comparing user's kernel usage and customizations is the better way to help everyone to find the needed configuration, and to let them make whatever they want, with their phone, on the best possible way
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
I just noticed something going back at iodak v9.95 to try peppe's configuration; on iodak v9.95 the temperature of the cpu is higher, there's a difference of at least 20° C more or less. Problem was that I went back to iodak because charging with optimus play v2.53 was a pain since instead of charging it wasn't. (Of course I mean while in use)
With iodak charging is flawless (I activated the fast charge option, which isn't present in Optimus Play).
Is it because of the fast charging option that's making the difference?
I'n trying the cpu undervolted by -75mv MPU and -30mv LPU, and it seems a bit laggier than the optimus play one, I can feel the difference just typing with the keyboard on the browser, but it's charging despite me using the smartphone.
What do you think it's the cause of the slow charge in optimus? And maybe more important thing, how is it possible that the cpu has a 20° C of difference between optimus and iodak but I keep the same frequency? I even undervolted with iodak, and in theory it should be the opposite situation, with iodak having lower temperature.
KrisJoe said:
I just noticed something going back at iodak v9.95 to try peppe's configuration; on iodak v9.95 the temperature of the cpu is higher, there's a difference of at least 20° C more or less. Problem was that I went back to iodak because charging with optimus play v2.53 was a pain since instead of charging it wasn't. (Of course I mean while in use)
With iodak charging is flawless (I activated the fast charge option, which isn't present in Optimus Play).
Is it because of the fast charging option that's making the difference?
I'n trying the cpu undervolted by -75mv MPU and -30mv LPU, and it seems a bit laggier than the optimus play one, I can feel the difference just typing with the keyboard on the browser, but it's charging despite me using the smartphone.
What do you think it's the cause of the slow charge in optimus? And maybe more important thing, how is it possible that the cpu has a 20° C of difference between optimus and iodak but I keep the same frequency? I even undervolted with iodak, and in theory it should be the opposite situation, with iodak having lower temperature.
Click to expand...
Click to collapse
So, talking about charging, on iodak's kernel you have to consider two situations: if you are charging through USB port, you may experiment slow charging and battery consumption even while charging, if you use the phone in the meanwhile (so, using fast charge solves the problem, but it is recommended to do not use it too many often, if you want your battery to have a longer life)..the problem doesn't exist if you charge the phone through AC adapter, so the phone should charge at a normal speed, even if you use it, whit no fast charge necessity.
Talking about my configuration, yes, you may have some little lags, here and there, 'cause this is a battery saving configuration, more than a gaming performance one..
Finally, temperature: maybe the difference between the kernels is due to a different overall cpu voltage, or the temperature is not really precisely shown, honestly I don' t know for sure
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
I'm using the ac adapter and with optimus play charging was a bit hard and slower than with iodak. With -75mv it seems I don't have problems with waking up the smartphone and it seems a bit smoother, maybe a placebo effect, but I think that it could be the limit of undervolting with variant 2 cpus.
Now that I didn't use the smartphone for while the temperature is lower (49-51° C), the high temperature was due to the 1500 Mhz used at the beginning because I deleted cache and dalvik before installing iodak again (to avoid problems). Let's see how it behaves in these days, but I'm a bit confident iodak's config is better for battery saving, even though with antutu benchmark I did 13000 with iodak and, and 12800 with optimus play (with battery saving and performance balanced). It may be a wrong test but I still wanted to give it a try.
Yep, I tried to uV MPU frequencies at -100 mV, and it freezed my phone, after some seconds or minutes..so, I also think CPU variant 0x2 has this uV limit..maybe it's possible to uV a bit more single frequencies, without causing freezes, but I had not the time to try to individually uV any single frequency
Sent from my ME301T - Beanstalk 4.4.2 - Geass Kernel - using xda app-developers app
I was thinking that we should specify what runtime we're using, if Dalvik or ART because I actually felt some differencies. What about you? Do you feel any difference with using one or an other? Sorry for the off topic, but I thought we could talk about the runtime also since we'll looking for the best performance/battery life.
O.T.: Don't activate ART Runtime on the latest cm nightly (3rd of April 2014), it will force close some apps like uicall, dialer, ecc. I had to return to dalvik by installing an older version in which ART was working... quite unconvenient.
This is the best thread ever guys.
I am using iodak 9.95 in Zaiben RC8.
Max 1000 mzh, interactive, no undervolting, Multi core savings 2
The only bad thing is that if i want to wake a the device it doesn't wakes for the first time and I have to press twice the power button.
KrisJoe said:
I was thinking that we should specify what runtime we're using, if Dalvik or ART because I actually felt some differencies. What about you? Do you feel any difference with using one or an other? Sorry for the off topic, but I thought we could talk about the runtime also since we'll looking for the best performance/battery life.
O.T.: Don't activate ART Runtime on the latest cm nightly (3rd of April 2014), it will force close some apps like uicall, dialer, ecc. I had to return to dalvik by installing an older version in which ART was working... quite unconvenient.
Click to expand...
Click to collapse
Yes, everyone is free to talk about ART or Dalvik, of course, it's related to Rom customization, using or not using it! Personally, I'm not using ART, considering it's on an early, experimental stage, and I have no time to switch between the two runtimes, if something should go wrong with ART (I need this phone as my really daily driver, and I haven't too much time to experiment, ATM).. But every single accurate review, also explaining how runtimes work, with a specifical kernel and a specifical Rom, is appreciated here!
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
XxXDarknessXxX said:
This is the best thread ever guys.
I am using iodak 9.95 in Zaiben RC8.
Max 1000 mzh, interactive, no undervolting, Multi core savings 2
The only bad thing is that if i want to wake a the device it doesn't wakes for the first time and I have to press twice the power button.
Click to expand...
Click to collapse
Try multicore powersaving=1, and a little undervolt, you should have benefits in terms of smoothness, without losing battery
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
KERNEL: Iodak 9.5 (I know 9.95 is newest but I prefer 9.5 as I think it's performance/battery ratio is better.)
ROM: CM 03/30 nightly
SETTINGS(variant1): CPU max: 1500 lowest freq.: 620 screen off max: 475. GPU freq max: 564 mhz
MPU undervolted by -122 mV and LP core undervolted by -10mV but lowest freq. voltage is on default and max freq is on 1230 mV due to 564 mhz GPU freq. ART enabled and Multicore powersaving is set to 2.
GOOD: A lot smoother than 9.95 and with these undervolting I've done, it can survive heavy gaming without throttling.I can say this setup is the best for gaming if you've got variant 1.
BAD: Battery life is a bit worse compared to stock kernel.But with ART enabled it's difficult to notice the difference.Plus if you underclock to 1300 mhz your phone will still be smooth while giving you better battery life.
ottomanhero said:
KERNEL: Iodak 9.5 (I know 9.95 is newest but I prefer 9.5 as I think it's performance/battery ratio is better.)
ROM: CM 03/30 nightly
SETTINGS(variant1): CPU max: 1500 lowest freq.: 620 screen off max: 475. GPU freq max: 564 mhz
MPU undervolted by -122 mV and LP core undervolted by -10mV but lowest freq. voltage is on default and max freq is on 1230 mV due to 564 mhz GPU freq. ART enabled and Multicore powersaving is set to 2.
GOOD: A lot smoother than 9.95 and with these undervolting I've done, it can survive heavy gaming without throttling.I can say this setup is the best for gaming if you've got variant 1.
BAD: Battery life is a bit worse compared to stock kernel.But with ART enabled it's difficult to notice the difference.Plus if you underclock to 1300 mhz your phone will still be smooth while giving you better battery life.
Click to expand...
Click to collapse
I have double press to wake bug with iodak 9.5 how did you solve it ?
CrazyWinner said:
I have double press to wake bug with iodak 9.5 how did you solve it ?
Click to expand...
Click to collapse
I use volume rocker to wake the phone up as a workaround.Easy to reach it with your midfinger once you have the phone in your hand.Plus you get to press the power button less, extending it's life.
Edit : Incase you didn't know official CM and most of the custom ROMs have volume rocker wake option in settings > button or under some other category.
After flashing this kernel my gaming performance has been very bad. I am getting alot of lag. And cant even play
egren58 said:
After flashing this kernel my gaming performance has been very bad. I am getting alot of lag. And cant even play
Click to expand...
Click to collapse
Did you flash over stock or custom kernel?
k.s.deviate said:
Did you flash over stock or custom kernel?
Click to expand...
Click to collapse
Stock kernel and stock rom.
Wasn't open beta by chance was it?
k.s.deviate said:
Wasn't open beta by chance was it?
Click to expand...
Click to collapse
I am not on open beta. I am on the official 7.1.1 release
Custom kernels for the OP3T purposely underclocks the CPU to the same frequencies as the SD820 due to stability reasons. The stock kernel allows for the CPU to achieve higher frequencies and then throttles it down to prevent crashes. There is likely slightly reduced performance in custom kernels compared to the stock kernel, though I don't think it should result in noticeable lag. Are you sure your ElementalX kernel isn't set to power saving mode? Maybe try to set it to performance to test it out, or change the CPU governors.
You can change cpu speeds in the aroma installer when installing through twrp. There are several options I usually just use the default and still get great performance for scrubbing including games. You can also change cpu speeds with the elemental x kernel manager app from the play store costs about 2 or 3 dollars definitely worth it cause it will also update the kernel for you.
Anova's Origin said:
Custom kernels for the OP3T purposely underclocks the CPU to the same frequencies as the SD820 due to stability reasons. The stock kernel allows for the CPU to achieve higher frequencies and then throttles it down to prevent crashes. There is likely slightly reduced performance in custom kernels compared to the stock kernel, though I don't think it should result in noticeable lag. Are you sure your ElementalX kernel isn't set to power saving mode? Maybe try to set it to performance to test it out, or change the CPU governors.
Click to expand...
Click to collapse
ElementalX doesn't underclock the cpu.