Database Users

[Q] SetCPU causes phone to freeze when used to underclock when screen is off

So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?

rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off

rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.

Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G

I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App

It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.

rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience

murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.

I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.

I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?

same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.

What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.

I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.

mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.

jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.

I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max

Froyo UI Response/Laginess

I (and several friends that I asked) noticed a mark increase in UI response (laginess) when coming out of sleep, opening app drawers, initializing the keyboards, scrolling between launcher screens, etc. Having random lags is annoying, but having 2-3 second lag spikes when using the keyboard is downright frustrating.
I know that lab benchmarks are way up with the new release, but frankly I don't care about those if my day-to-day functions suffer.
I first began to notice this when I made the stock upgrade to Froyo. 2 days ago, I flashed the EViO 1.5 ROM on my phone, and it seems to be 4x as bad. Paring down the window launcher helps marginally. ADW -> Sense -> Launcher Pro in order of most to least lag. I am currently using Launcher Pro just because it's responding a little better than the others.
In a somewhat related post, one of the developers offers that a lot of lag is due to aggressive garbage collection:
(unfortunately, I am not yet verified so I can't post the link)
I also wonder if the overhead from the JIT compiler or lack of proper memory caching isn't the culprit ... or perhaps this is to what the aggressive garbage collecting is referring.
Who else has noticed this? Can anyone offer up an explanation?
I would be willing to reflash to a new ROM if someone can suggest a custom ROM that they recommend as having faster normal UI response time.

Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag

DirtyShroomz said:
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
Click to expand...
Click to collapse
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.

None of these issues using Myn's 2.2 rls3 Rom and ziggys 11/5 kernel. I DON'T use setcpu. It can cause instability issues. Like the lag time in wake up. Some phones don't like 245mhz when sleep. Try boosting to 384 screen off. Also, overclocking can be beneficial but clocking too high can cause poor responsiveness. It can also affect benchmarking scores negatively if clocked to high. Try ziggys 11/5 kernel, its doesn't support overclocking, but it honestly feels like it is overclocked using this Rom/kernel combo
Sent from my DAMN Evo!!

lag what lag ? my 6.1 is lag free

moodebony said:
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
Click to expand...
Click to collapse
If your setcpu governer is set on something like conservative, it can defintely cause intermittant lag. get away from setcpu and use a havs kernel.

Currently mine is instant, no lag at all, but I had this problem about a week ago. I am running Fresh 3.4.0.1 with Netarchy's 4.2.1 cfs/havs kernel.
What caused my problem with lag was a lack of internal memory. I was down to about 64 MB of internal memory left and it would lag on wake or when exiting apps, and I noticed that it would often have to reload the UI whenever I exited an app. The fix was easy. I moved what apps I could to the SD card and used titanium Backup to remove a bunch of stuff that I do not use. Once available internal memory was over about 100 MB (134 MB is what it was when I was finished) the lag totally went away.

Problem Partially Solved!
SetCPU was indeed the main culprit. I was under the impression that overclocking too much would just cause instability. It seems that moving the ceiling from 1228.8mhz down to 1113.6mhz solved most of my new lag issues with the EViO ROM.
Indeed, upping the screen-off throttle-down from 245 to 386 also seems to have helped the wake-up lag time, though I'm still doing some more testing on this one.
Would I need to set all floor values up to 386 as well, or is that just for the screen off value? What scaling setting do you guys in setCPU? Conservative? Performance? On-Demand? Does anyone happen to know exactly what the differences are in the algorithms that they use?
So can anyone offer up an explanation as to why overclocking would result in lag? Is there some kind of hardware throttle-down that's happening? I had a catch for if the battery got too hot that would throttle back to normal speed, but I never seemed to reach it. Is there a known heat limit where the hardware automatically throttles down?
As for the seemingly normal, random Froyo lag spikes, I'll be monitoring that over the next few days.
Thanks again in advance for any information.

Odd problem across all ROMs I've installed

So, I've tried a number of major ROMs available for the Epic. ACE ROM, Midnight ROM, and now Bonsai 4.1.1.
I have a very odd issue with particular programs.
The programs are:
Backbreaker Football - gets stuck at loading screen
Chalk Ball - FCs after launching
Plants vs. Zombies - freezes at loading screen (only used this one on bonsai)
Doggcatcher - Works fine, except for when I try to switch between podcasts (listening to one after listening to another) it freezes. I close and re-open and it works fine again until I switch tracks
The first three are Amazon app purchases, so I could see a common issue, but Doggcatcher is a market purchase.
I thought it might be an SD card issue, but I've reformated twice now.
Any ideas?

I should also mention it worked for the first two days I had bonsai installed. Weird.....
Sent from my SPH-D700 using XDA Premium App

Did you have journaling on or off? If you had journaling off and you have a freeze, you have to pull the battery and data corruption starts and usually continues to get worse. Best thing to do until you find out what is causing freezes is to enable journaling for the ROM you are on or going to be on, do all wipes, reflash the ROM, then put these apps on fresh with no data (backup and restore from Titanium the app only if you can't redownload). If you are running a Overclocking or undervolting app, you may want to uninstall it until you resolve these issues.

kennyglass123 said:
Did you have journaling on or off? If you had journaling off and you have a freeze, you have to pull the battery and data corruption starts and usually continues to get worse. Best thing to do until you find out what is causing freezes is to enable journaling for the ROM you are on or going to be on, do all wipes, reflash the ROM, then put these apps on fresh with no data (backup and restore from Titanium the app only if you can't redownload). If you are running a Overclocking or undervolting app, you may want to uninstall it until you resolve these issues.
Click to expand...
Click to collapse
Kennyglass is right. It could very well be an Overclocking or Undervolting app. I can run at 1400 all day when messing with my phone but if I go to watch a movie or play a game, I have to back off of the overclock or it will freeze after a certain amount of time
Sent from my SPH-D700 using XDA Premium App

Thanks Kenny.
I was running Mighnight and ACE with journaling ON, so I don't think that was it. And I didn't use an UV or OC apps with Bonsai.
It's really puzzling as I now have Frankenstein installed and everything seems to be working fine.
Perhaps I just have a flakey phone?

lattiboy said:
Perhaps I just have a flakey phone?
Click to expand...
Click to collapse
this is a possibility itself. I've noticed a wide range of 'what these phones can do' that's not the same from one device to the next.. for example, when SRF 1.1.0 came out, lots of people had lots of problems flashing it, and others worked perfectly the first flash.. very strange why some phones like it while others didnt.
For over clocking, some phones will sscream along at 1.4 ghz, and others will puke at even 1.3 ... it's all a matter of what your phone will allow to play nicely with and what it just won't allow.

lattiboy said:
Thanks Kenny.
I was running Mighnight and ACE with journaling ON, so I don't think that was it. And I didn't use an UV or OC apps with Bonsai.
It's really puzzling as I now have Frankenstein installed and everything seems to be working fine.
Perhaps I just have a flakey phone?
Click to expand...
Click to collapse
It is possible. Bonsai OC's to 1120 and maybe even that is too much for your phone and causes a freeze here and there.

ARRRGGG!
Okay, everything was fine and dandy UNTIL I REBOOT. Frankenstein was working gloriously, and now these same apps are acting crazy.
Doesn't seem to matter what kernel or ROM I'm running.
Is this an EXT4 thing? I've had no FCs, so I don't think journaling is doing it either?
I'm running on the clean kernel now.
Ugh....
PS I've been able to run 1400 Mhz stable on Genocide, so it's not that either....

lattiboy said:
ARRRGGG!
Okay, everything was fine and dandy UNTIL I REBOOT. Frankenstein was working gloriously, and now these same apps are acting crazy.
Doesn't seem to matter what kernel or ROM I'm running.
Is this an EXT4 thing? I've had no FCs, so I don't think journaling is doing it either?
I'm running on the clean kernel now.
Ugh....
PS I've been able to run 1400 Mhz stable on Genocide, so it's not that either....
Click to expand...
Click to collapse
Are you sure you have journaling enabled.

(xoom 2) XOOM 2 10.1 Freezing & Reboots – A SOLUTION!

I just wanted to share with you my recent issue & solution to the XOOM 2 rebooting issue.
Now to give you an overview of my situation, I purchased the XOOM 2 10.1 UK back in January 2012.
I use it almost every single day. No surprises I was getting random screen freezing followed by reboots every single day. Most days twice!
Now I was hoping that when the update happen back around 2 months ago that it would solve this issue. It never.
In fact my freezing & reboots were happening more frequent.
Basically within 5-10 mins of using the Xoom2 it would reboot.
Some days I just wished I could throw the dam thing through the wall.
I rooted using Dan’s method. The only method. & tried various ways to solve the issue.
NOTHING worked.
In fact, I was convinced that my rooting & installing things that should not be there was making the reboots worse.
So I cleaned up my Xoom 2, went into recovery, wiped cache & cleaned data & rebooted.
This still did not work.
Then I tried task managers, cache cleaners & even paid for that system panel app that logs all apps & usage.
Nothing worked; I was still getting the reboots. Everyday.
So after looking over many Xoom 2 forums & with many issues and complaints about this issue, I was close to selling & getting an iPad.
I was convinced it was hardware.
Then I tried this way:
1. I rooted.
2. I installed ADW Launcher & made default.
3. I installed SetCPU
4. I installed Titanium Backup
5. I froze the stock ‘launcher’ – (whatever you do – do not un-install any app, you CANNOT update Xoom if you do)
6. I changed CPU from ‘hotplugmoto’ to ‘performance’ 1200min 1200max
(I know you might think this uses lots of battery but I found not)
7. Set up setCPU profile for ‘screen off’ I use ‘on demand / 300 to 600’
Battery over night on this setting did not go down by 1%
8. Rebooted.
After 4 days of constant use & trying so hard to get the Xoom to freeze & reboot – I can’t.
This method works.
I have surfed using ‘Firefox’ while using ‘Currents’ while using ‘Google+’ while downloading files and steaming music via ‘Google Music’. I have open every single app & been quickly switching between them all trying to over load the system.
Nothing will freeze or reboot my XOOM 2.
What I can get from this is that the Xoom 2 works perfectly.
With the high CPU set, it is so fluid and lag free. It works almost perfectly now. It also means the hardware is absolutely fine.
Maybe with newer firmware updates in the future this will be sorted naturally.
I makes me think something with the high CPU means a bug in the processing won’t make the Xoom freeze & reboot.
Until then this method works for me and I can’t see why it won’t work for you.
If you are having this issue I hope this helps.

I messaged you on the Motorola Forums, but I think they may take it down since they don't like talks about rooting.
But thanks for posting this, I will give it a shot.
When you changed to performance 1200 min/1200 max - I'm guessing you also checked set on boot? right?

Yes i ticked set on boot. Make sure you have a screen off profile otherwise it will be running at max all the time.
Hope it works for you.
Sent from my XOOM 2 using Tapatalk 2

Hi,
I froze some bloat before and uninstalled flash 10.3 cause flash streaming online videos didn't work 4 me (neither 10,3 or 11,x), then installed flash 10.2 and all starts to work ok but still 2 or 3 reboots for week.
Also seems that "memory booster" app helps when some apps starts to freeze and u can finish em and free some mem.
So now i'm trying setcpu and then i will do launcher trick
Thx a lot!

Vanpeebles, Did you switch launchers because you think it will help the reboots? or because of personal preference?

List of frozen apps
List of frozen apps 2 months ago without issues:
App used: Ultimate Backup
Amazon Kindle (I dont use it)
Citrix Receiver
Drippler Motorola DROID Xyboard 8.2
Drive
Fuze Meeting
Google+
GoToMeeting
Servicios de estadisticas de dispositivo ("Device statistics Services")
Twonky
Good luck everybody!
Now i'm not expecting ICS, this is working almost perfect. Let's see setcpu improve.

It does seem that the source of the freezing/reboots is the Motorola Launcher. Since I switched to Go Launcher HD I've definitely seen less freezes.

Hi
I switched launcher on personal preference but to be fair I have had no freezes now for 5 days
So I'm not messing now if it ain't broke.
The reason is I did this is I read 1 post on another forum that someone changed launcher &, this helped him.
So wether launcher or high cpu I'm not bothered
To finally have a working tablet is such a huge relief!
Sent from my GT-I9100 using Tapatalk 2

Thank Vanpeebles,
I did everything you said and now hoping for the best!
Either way, I'm loving ADWLauncher Ex..... sooo fast and snappy!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

Thanks my Xoom 2 is running great again!
Also add this warning. Do NOT remove the Launcher2 app if you do then your Xoom 2 will never boot again and the is no current way to fix this because of the locked bootloader.

luke.arran said:
Thanks my Xoom 2 is running great again!
Also add this warning. Do NOT remove the Launcher2 app if you do then your Xoom 2 will never boot again and the is no current way to fix this because of the locked bootloader.
Click to expand...
Click to collapse
That's my question, why do you even need to freeze the stock launcher if you've set adwlauncher as the default.. like what's the point of that step of freezing the stock launcher, it shouldn't impact performance.
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

big ach said:
That's my question, why do you even need to freeze the stock launcher if you've set adwlauncher as the default.. like what's the point of that step of freezing the stock launcher, it shouldn't impact performance.
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
Click to expand...
Click to collapse
No he is right, because the stock launcher takes a big bite out of your RAM around 100MB. And even if you do have another launcher running that stock launcher always seems to be in the background on my tablet.

luke.arran said:
No he is right, because the stock launcher takes a big bite out of your RAM around 100MB. And even if you do have another launcher running that stock launcher always seems to be in the background on my tablet.
Click to expand...
Click to collapse
Yeah but won't freezing the launcher (or changing its name to launcher2.apk.bak) cause problems if your tablet faces a failure and the adwlauncher crashes?
EDIT: I guess titanium backup unfreezes apps if you do a wipe so the best option is to freeze the stock launcher (NOT uninstall it and NOT rename it)
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

Over 1 week now and not 1 reboot.
I can't answer these questions on the launcher?
All I know is this works for me, I have had not 1 freeze or reboot, so the stock launcher can stay frozen.
(it may have absolutely nothing to do with it, but I really don't care)

Hi after several days over GO Laucher EX (or HD "Tablet version but less customizable") with Setcpu 1200 1200 performance and etc....
only 1 reboot when several web pages were opened on stock browser with flash videos etc.
I've noticed that now when apps stops to work it goes back to home instead of reboot except that time.
Almost no free ram and that's seems to be the clue..Stock launcher doesn´t free enought memory
And battery drains suddenly stopped.
Super happy man . More fluid launcher, more customizable, and also wifi starts to work better when comes back from sleeping
Thanks for not to give up!

Have to say... this solution seems to be working very well. I'm running set CPU in conjunction with auto memory manager set to "aggressive" and AdwLauncher Ex!
Using many apps that in the past would give me reboots, but now they are working flawlessly.
Thank you very much for this awesome contribution!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

I'm Xoom 1 user and also having annoying reboots you described here. Most of all it happens when watching movies or iptv in player.
But isn't setting cpu frequency to 1200min will force cpu run at 1200 not less all the time? It probably may overheat the cpu and sounds dangerous.

Neolo said:
I'm Xoom 1 user and also having annoying reboots you described here. Most of all it happens when watching movies or iptv in player.
But isn't setting cpu frequency to 1200min will force cpu run at 1200 not less all the time? It probably may overheat the cpu and sounds dangerous.
Click to expand...
Click to collapse
When its in use yes, but you also set a second profile to turn down the cpu to a lower value when the screen turns off so you don't drain battery and cause overheating!
So far - I'm running this method without any problems, no noticeable battery drain or extra heat in anyway!

big ach said:
When its in use yes, but you also set a second profile to turn down the cpu to a lower value when the screen turns off so you don't drain battery and cause overheating!
So far - I'm running this method without any problems, no noticeable battery drain or extra heat in anyway!
Click to expand...
Click to collapse
I'm currently running on stock kernel without ability to scale over 1000. Tried to set to performance governor only, but failed and got regular reboot during usage. Will try your method.
Seems to be it's operating system problem. Don't understand why motorola still didn't resolved it, including that fact that problem also present in first Xoom model.

Worked a bit around with your solutions and stabled on the following:
Stock launcher frozen;
SetCPU profiles:
Screen ON/unlocked: Governor OnDemand (1200-800) with Noop Scheduler
Screen OFF: Governor standard hotplug (800-300) with noop scheduler
It looks like moto_hotplug governor doesn't work quite well but I also noticed some glitches on systemui.apk. Whenever you turn your screen on and unlock doesn't show smooth you must turn off screen and try again... if you unlock with a laggy unlocker the whole system will be a mess.
With those setting I'm not having reboots, just some lags here and there; battey, however, lasts much less due to ondemand governor.

G2 D800 Lagging, running absurdly slow?

Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
But just recently, about a week ago, it just started lagging out and being very, very slow.
For example, if I'm watching a YT video through the app, if I rotate the screen, it takes maybe 5-8 seconds to actually rotate. Also, in a lot of circumstances where the keyboard has to pop up, it just freezes the app until the keyboard pops up maybe 10 seconds later.
It's also just laggier in general in most apps, scrolling through FB or Twitter freezes nearly every second when I'm scrolling. It's generally unresponsive and sometimes just freezes outright. It also acts this way on the homescreen, and in most everything else.
The most annoying part, however, is that sometimes the devices just doesn't turn on for sometimes up to 15 seconds after pushing the power button (and it usually just refuses to turn on when using my knock code).
The odd part, however, is that once it's actually in something like a game, it performs perfectly fine.
I've played a number of Cardboard games, as well as games like Nova 3, and it performs perfectly.
I've also ran multiple benchmarks (Geekbench, 3DMark, etc), and it scores around where it should.
Info about the device:
LG G2 D800
Stock Lollipop 5.0.2
Software Ver. D80030f
Kernel Ver. 3.4.0
Rooted
TWRP Recovery installed
XPosed Lollipop installed
G3 Tweaks installed, a number of tweaks applied
Everything else is stock (homescreen, etc)
What I've tried/checked:
Checked memory usage during "lag sessions", rarely dips below 300mb free
Changing minfree values through Rom Toolbox (tried every preset, as well as setting everything to the max to free as much as possible)
Rebooting (affects nothing)
Checked CPU speed with Rom Toolbox (is at max, and does achieve the max speed of 2265 MHz. Setting it to performance mode/setting the min speed to be 2265 MHz has no effect, but reduces battery time)
Changed default cache sizr (tried every preset from 128kb to 4096kb. With multiple benchmarks, the optimal value for r/w bounced between 512kb and 4096kb, currently on 4096)
Things I have not tried (that I am aware would possibly have an affect):
Changing anything in the kernel tweaks/build.prop
Completely wiping, reformatting, and reinstalling (I really would rather avoid this if possible, as it would take a while to get everything back to what it is now, and it was a pain to upgrade to Lollipop in the first place)
I am unaware of anything else I could try to fix it, which is why I'm here
So, does anyone know of any other solutions or things to try? This has made my phone very unreliable, even for phone calls and messages, which is a problem.
Thank you for your time and help!

Jtpetch said:
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
Click to expand...
Click to collapse
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.

iubjaved said:
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!

Jtpetch said:
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Click to expand...
Click to collapse
Hi,
Even you uninstalled bloatware, the apps you use daily could be running in background and taking all those rams. So whenever you play a game or dont use a certain app, just go to greenify and hibernate. Since you have xposed installed, you can do more than that such as u can stop sync , etc.
About the kernel, it has a ram management settings and cron task.
Ram management dont need to be altered. It has some preset profile so if you seek performance, just choose performance or if u need battery , select battery profile etc.
Cron task is useful because it will do alot of things automatically. For example, it will release ram at certain amount of time from the apps , it will restart google play service since that could be an issue , etc.
All you need to do is take a nandroid backup just to be safe. Then download Dorimanx Ota from playstore and it will detect ur device and show u which version of kernel is available. Then download that, go to recovery, flash it, and you will see three app installed : Synapse -- will give you all the details of ur setup including cpu speed, temp etc for monitoring purposes
Dorimanx settings - this is the main settings of the kernel. You will see a P icon on top, tap it and choose your desired profile.
Color management : It is as the title says, just leave it be.
Then use your device, check your ram and report back. Hopefully it will resolve your issue.

Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.

Jtpetch said:
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Click to expand...
Click to collapse
No worries, happy to help. I gave you advice based upon my experience using all those .
Feel free to post in XDA if you need any sort of help, you will find many that will give you insights and stuff to solve your issue.
GL :good: