Develop Bugs

New to SetCPU!

I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.

You need to update your PRL ...

twigums said:
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
Click to expand...
Click to collapse
I always leave my main profile at 245 mhz min and 998 mhz max (ondemand mode). Then, of course, you'll want a screen off profile, and as far as that goes, I've heard that 128 and 245 draw the same voltage, so I have mine set to 128 min, 245 max (powersave mode). Other than that I just have some low battery profiles and a temp one. I don't really get any lag with this setup, but I've heard some people do. If that's the case, and I'm only talking about lag when first turning on, just up the 245 to 384 or something and I'd make it ondemand.

do i need to check set on boot under the scaling option

twigums said:
do i need to check set on boot under the scaling option
Click to expand...
Click to collapse
No. I would leave it unchecked. This has been known to cause some issues.

grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
what kind of issues are you talking about? i've only heard and practice leaving it off when experimenting with overclocking (since it can put you in a boot loop). once you find a stable overclock speed, you can check it to start on boot so that you don't have to open setcpu every time you reboot if you decide to run it at that speed.
on-demand is a little less laggy (barely noticeable to me) but may consume more juice than conservative.
most kernels will step down to 245 when the screen is off so creating a profile to do that is redundant. you can verify this with the app android system info under the system tab > cpu.
having said that, i don't use setcpu unless i'm benchmarking and want to overclock.
kings #6 bfs kernel is awesome for battery life (default is conservative governor). it's what i use. give it a go when you've gotten a good feel on how kings #10 cfs is working out for you.

Here's what I would hit up..
set it to conservative. Conservative starts your phone at your minimum clock speed and works its way up, as opposed to on demand which starts at the highest and works its way down.
then for advanced i have sampling rate at 50000
Up threshold at 95% <- that's saying that when the workload hits 98%, crank up the processing speed
Down threshold at 70% <- when the load hits 70% turn it down
That stuff right there is agressive as hell, and when I say agressive, i mean...you probably won't ever hit your max frequency unless you are seriously doing some heavy lifting. The settings there are what I use to save up battery, you can get through a day easy with everything on (GPS, Wifi, sync, 3g, the works) and with your current usage, since its similar to mine (except that i also run beejive, skype and twitter at refresh rate of 5min).

grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
Yeah I think you've probably just seen that on some custom kernel pages. They only say not to do that because if you're testing battery life with say...HAVS, it could interfere w/o you realizing it. Set on boot just means you don't have to turn setCPU on everytime you reboot your phone.

just go set a profile on minimal mhz and on powersave mode if kerenal allows if not just use ondemand

My problem with the "Set on Boot" option is if you accidentally fat finger the slider past your stable clock with it checked, you're looking at boot loops and possibly having to restore from a backup to sort it out. SetCPU really needs the "Set on Boot" option grayed out and a "Lock Settings" option that must be checked before "Set on Boot" becomes accessible (unchecking "Lock Settings" would also uncheck "Set on Boot").
Another option would be a user defined field for max stable clock in the advanced settings that would limit the slider on the main tab. Either one should eliminate accidental boot loops.

SetCPU Gingerbread

Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.

In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).

You could try using cpu tuner instead. Gives you way more options.
CM 7

You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?

My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?

Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.

thanks bro, i OC'd to 1017 and there are no issues

ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.

martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.

KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.

[A] Galaxy Nexus power consumption

Ok .. so, seeing many questions w/o real answers regarding the power consumption of the GN under various circumstances, I decided to create some testing conditions and generate some data.
The original idea and requirement started on Franco's kernel development thread but as this topic might be of interest I decided to create its own thread.
Test conditions:
- device: Galaxy Nexus i9250 - GSM version
- rom: bigxie's rom
- kernel: Franco kernel
*************************
1. IDLE test
2. MP3 play test
3. DISPLAY test
4. CPU Power test
5. Still image test
6. MKV play
7. Additional Display, MP3 play, YouTube and TuneIN media streaming
*************************
If you have any suggestions of tests you would like to see, please drop me a PM so I can make a list and implement them (depending on my possibilities).
*** Original post was heavily modified due to inaccurate measurements. The replacement posts linked here are the ones that matter ***

Why exactly did you decide not to run tests with wifi and 3G/2G, like grabbing and playing a youtube video?

That was the plan but seeing that I don't have enough resolution for this run, I decided to keep the test as simple as possible.
In few hours I'll do a more detailed run, with 1mA reasolution and I'll include online media too, as well as wifi versus 3g power comparison. It looks like a long friday night for me
// sent from my green robot //

ro_explorer said:
It looks like a long friday night for me
Click to expand...
Click to collapse
Haha! Well... I'm already looking forward to those higher res tests... don't forget to include 3G vs 2G as well, because I'm really not sure if there is much of a difference since you take so much longer to load... oh, maybe not a late friday but an early saturday?

thanks for doing these tests, its a great idea and cant wait for more results.

Yes. Thanks. Definitely need more.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

Thank you for support guys .
I've managed to build the new test circuit. I can now read the current with 1mA steps.
As a first set of measurements with the new setup - idle power .
Kernel and rom - see first post.
HotPlug function is a feature of Franco's kernel to turn off CPU 1 while phone is in sleep mode (in case some of you are wondering). It is supposed to be a feature to save power while phone is idle.
Voltage constant at 3.9V over all set.
1. AIRPLANE MODE - any governor, both 350-1200 and 700-1200 frequency range:
1.1. HotPlug OFF - 3 mA steady
1.2. HotPlug ON - 3/4 mA - the multimeter was unable to choose a value
So .. in airplane mode, the standby power is between 11.7 - 15.6 mW
2. 3G mode,WiFi - OFF, interactive governor
2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
2.2. Freq: 700-1200, HotPlug - OFF - 4/5-8 mA
2.3. Freq: 350-1200, HotPlug - ON - 4-8 mA
2.4. Freq: 700-1200, HotPlug - ON - 4-7 mA
3. 3G mode,WiFi - OFF, conservative governor
3.1. Freq: 350-1200, HotPlug - OFF - 3-8 mA
3.2. Freq: 700-1200, HotPlug - OFF - 3-8 mA
3.3. Freq: 350-1200, HotPlug - ON - 3-7 mA
3.4. Freq: 700-1200, HotPlug - ON - 3-6/7mA
4. 3G mode,WiFi - ON, conservative governor
4.1 - 5GHz WiFi
4.1.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
4.1.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA
4.1.3. Freq: 350-1200, HotPlug - ON - 4-7/8 mA
4.1.4. Freq: 700-1200, HotPlug - ON - 4-6/7 mA
4.2 - 2.4 GHz WiFi
4.2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
4.2.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA
4.2.3. Freq: 350-1200, HotPlug - ON - 4/5-8 mA
4.2.4. Freq: 700-1200, HotPlug - ON - 4/5-8 mA
When NOT in airplane mode, my phone has data and sync ON, and (over night at least) only Google services are being synced - gmail, g+, gtalk.
The measurement with data on/off, sync on/off are identical to the data on, sync on, when there is no activity that is. So, the the only way the phone will consume more power when data/sync is on is exactly when an event is being synced .. the rest of the time the radio being idle, identical with data/sync off.
Conclusion regarding IDLE (in my case at least): best power saving while phone idle is with WiFi off while screen off (or on only when plugged), conservative governor, 700-1200 freq. range and HotPlug - ON. Of course these values are experimental and are specific to my device but the numbers are looking reasonable.
I did not take any video of the above measurements because it was really boring .. put device at sleep and wait for it to really sleep (about 2 minutes for each test). But I'm attaching a photo of the test bench .
... to be continued with awake tests with video capture also ...

Awesome work!
I can think of one more scenario that's worth testing: when the screen is off but there is a wakelock keeping the CPU awake. This would give us a baseline of CPU awake but screen off, which would tell us exactly how much juice is going to the screen and CPU when the device is on.

Would MP3 play in background meet your expectations?

ro_explorer said:
Would MP3 play in background meet your expectations?
Click to expand...
Click to collapse
Wakelock but idle would be ideal I think, but actually an MP3 playing might be perfect if you can compare MP3 playing with the screen on in one of the previously tested states and MP3 playing with screen off. Then some simple subtraction should tell us everything we need to know.
I'd like to be able to calculate how much is used when the CPU is awake due to a wakelock, and how much power is saved by getting out of that wakelock ASAP to get back to power collapsed state. It might turn out that ideal screen off profile is 920 or even higher.

Good stuff. Glad someone is taking their time to collect this data.
Something to try: Loop a program to browse site content with white (light) heavy colors vs black (dark) heavy colors.

excellent info. if anyone's interested we did a similar test with the nexus one where we were able to use the actual resistor in the fuel gauge chip within the battery. so we did various testing scenarios, and that phone pulled very high currents. seems like our galaxy nexus is actually more efficient with some of those screen tests.
here's the link, prob boring though since it's not our shiney new GN.
http://forum.xda-developers.com/showthread.php?t=998544

This is my simple, yet efficient circuit (and quite precise I might say).
As you can see, the sense resistor is quite small not to interfere with normal operations and I think the 1% tolerance is making it perfect.

MP3 test
This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no
Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).
I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.
Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU
Values from this second test:
~0.62W consumption with screen ON, autobrightness, showing homescreen
~0.72W when mp3 is started (70% volume, headphones)
~0.155W with screen off/playing mp3
~0.05W with screen off, no mp3 play and a software waiting for input (in this case, poweramp's lockscreen)
~0.011W in standby - airplane mode.
The above values are with 350-1200MHz freq range, conservative gov.
The frequency CPUs have used during screen-off play was 350MHz. If I'm increasing the min. frequency to 700, the average consumption is increasing with an average of 2-3mA.

ro_explorer said:
This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no
Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).
I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.
Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU
Values from this second test:
~0.62W consumption with screen ON, autobrightness, showing homescreen
~0.72W when mp3 is started (70% volume, headphones)
~0.155W with screen off/playing mp3
~0.05W with screen off and a software waiting for input (in this case, poweramp's lockscreen)
~0.011W in standby - airplane mode.
Click to expand...
Click to collapse
Perfect. Thanks so much for taking the time to do this. I had been trying to come up with a semi-scientific way to measure some of this stuff and you just hit it out of the park with this.
Do you know what frequency the CPU was at when playing the MP3 with the screen off?

Display test
This is the hi-res (1mA) display test: http://www.youtube.com/watch?v=cqSQ5QE-4S0
Values (with device awake, of course):
- auto brightness, relative low light conditions, dark homescreen: 162mA / 3.87V = 0.14W
Maximum brightness:
- white screen: 380mA * 3.8V = 1.44W
- red screen: 287mA * 3.83V = 1.1W
- green screen: 295mA * 3.82V = 1.127W
- blue screen: 327mA * 3.81V = 1.246W
- gray screen (50%): 240mA * 3.84V = 0.92W
- black screen (but awake): 147mA * 3.87V = 0.57W

aron7awol said:
Do you know what frequency the CPU was at when playing the MP3 with the screen off?
Click to expand...
Click to collapse
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.

ro_explorer said:
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.
Click to expand...
Click to collapse
Thanks, my guess is that this CPU can play an mp3 at 350 MHz just fine

I've solved the mistery ... above post updated.
The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.

ro_explorer said:
I've solved the mistery ... above post updated.
The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.
Click to expand...
Click to collapse
Sorry to keep bothering you for more, but do you also know the CPU usage playing the mp3 at each frequency?
The final question I'd like to be able to answer is: Is getting to idle faster at the expense of using a higher frequency to get there beneficial?
I guess to answer that question we need to separate how much power the CPU uses at 100% CPU usage at 350 MHz, 700 MHz, 920 MHz, etc.

cpu going nuts for no reason

I'm on stock, rooted, s-off
my device is getting extremely hot during normal use.(i dont play games at all, just whatsapp, facebook, news etc..)
sync is off, auto brightness.no google location reporting and history, no google now or history.
and using bbs to see what is going on ,i have no wakelocks and looking at battery screen, screen on time and awake time are almost identical.so nothing is keeping my device awake.
but for some reason, when the device is idle, the cpu goes nuts!
i installed cpu status bar xposed module so i could monitor cpu on real time, and i see the device jumping allot from 300mhz to 960 and 1000+ for no reason.(without touching it, and no apps running).when i touch the screen it scales to maximum.
it drives me crazy because i dont understand why the cpu behave like that.there is no logical reason for cpu going to max when i'm typing text.
its unbearable, cause its getting really hot while i hold it.
i have tried various kernels(elementalx, skydragon, faux, ionx, hacker kernel, but all of them shows that behavior.
on my old i9100, i never got that behavior, ondemand governor was perfect and i could reach 4 hours of screen on time.with the m8, i can barley pass it , going for 4-5 hours, because its draing too fast.
any suggestions?
*EDIT*
tried a factory reset, and i just installed xposed with cpufreq status bar module, and the device is still going nuts.WTF?

Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.

thebobmannh said:
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
Click to expand...
Click to collapse
i know there are background process and apps, and i don't except the device to stay at 300mhz all the time, but its quite annoying to hold on to a device and feel its temperature rising to insane levels without doing anything fancy with it.just texting.and every touch ramp the cpu to the max frequency, its weird.and unnecessary.
i don't know if its normal behavior, as i mentioned, my old i9100(galaxy s2) would not act like this. and i could get 4 hours of screen on time, and here, i get 4-5 hours max.it dose not seem logical.
I'm not using lte of nfc or BT.my reception is full(both wifi and cell).
i just want to know if this a normal behavior? anyone else having this heat buildup on light use?

I have a similar problem there on M8S. I killed half the background tasks, disabled syncing, auto backups, and then I open FBreader(or any other app) at 30% brightness and all the cpu cores go to 50 degrees C, heat up my battery to 43 degrees C. It results in loss of 40% of battery charge in just an hour. With screen off my device usually consumes 1-2% an hour. Whatever I do, I have never seen at least one core sleeping, they always work at 600-900MHz.

Is my Note 4 defective?

I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius

bucs9115 said:
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
Click to expand...
Click to collapse
Okay, so I got rid of my Note 4 so this is off of memory (full-disclosure). My Note 4 always ran pretty hot when it had to do anything. When flashing ROMs I'd be lucky if the CPU was below 70 C and any time I'd be playing a GPU intensive game it would get too hot to touch. I never had a lot of issues with the battery temp being too high though despite this.
As far as solutions go:
1) Screen res might help.....but I would try my other suggestions first
2) I wouldn't recommend disabling cores, it just makes the other two have to work harder to accomplish the same tasks and may be worse overall.
3) Kernel adiutor will allow you to do two things: adjust thermal throttling and adjust max GPU/CPU frequencies. I always reduced the max GPU frequency on this phone to lower the temps and adjusted thermal throttling to 55 C. The only CPU adjustments I did were to make sure the CPU wasn't overclocked.
4) I know you said it wasn't a rouge app, but get a task viewer (this is a good one) just to make sure (I had Nova taking 25% CPU usage in the background because I restored it from TiBu).
I saw your post in the NSeven thread and decided to respond, but please in the future try not to post errors in other threads unless you have the issue in that ROM. It sounds like you might have the same issue in that ROM as well, but you didn't say so in your post.

Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?

bucs9115 said:
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
Click to expand...
Click to collapse
You're welcome, and no worries for the post . As for your third point it would be really helpful if you tell me what you're running.
Could you list: kernel, ROM, root method, Android version, and any kernel mods (govtuner, skynet, etc)?
Also, does the same thing happen when you set a GPU max frequency? Have you tried having the settings run on boot and then reboot the phone?

Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol

bucs9115 said:
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
Click to expand...
Click to collapse
Since you're replying to both threads I'll keep my responses to your other Q&A thread to make life easier .