3g data speeds slow when screen is off?! - Samsung Epic 4G Touch

This is something that i have noticed and have confirmed several times. Ill be downloading a rom ( as im currently doing at this moment) and i get a average of 1.6Mb/sec with the screen on. I turn it off the screen for 30seconds or so then back on amd my live data graph in System Panel shows it imediately reducing my data speeds to around. 5Mb/sec or 500kbps. As soon as my screen is back on my data speeds are right back to 1.6Mb/sec area. How could this be? Im just more curious than i am upset that my phone does this. Thanks in advance for insite some one may provide in regards to my question

bluefire808 said:
This is something that i have noticed and have confirmed several times. Ill be downloading a rom ( as im currently doing at this moment) and i get a average of 1.6Mb/sec with the screen on. I turn it off the screen for 30seconds or so then back on amd my live data graph in System Panel shows it imediately reducing my data speeds to around. 5Mb/sec or 500kbps. As soon as my screen is back on my data speeds are right back to 1.6Mb/sec area. How could this be? Im just more curious than i am upset that my phone does this. Thanks in advance for insite some one may provide in regards to my question
Click to expand...
Click to collapse
Are you using cpu scaling? Perhaps when you turn your screen off, it's forcing the CPU speed down to 200mhz and that is slowing down your connection transfer? Just a guess..

Euclid's Brother said:
Are you using cpu scaling? Perhaps when you turn your screen off, it's forcing the CPU speed down to 200mhz and that is slowing down your connection transfer? Just a guess..
Click to expand...
Click to collapse
How do i check what my screen off cpu state is? Im running Caulkin's 2.8 and i know his is 200mhz-600mhz screen off. But im using Rom Toolbox to keep my cpu max at 1ghz so maybe that is changing the screen off cpu mhz?

bluefire808 said:
How do i check what my screen off cpu state is? Im running Caulkin's 2.8 and i know his is 200mhz-600mhz screen off. But im using Rom Toolbox to keep my cpu max at 1ghz so maybe that is changing the screen off cpu mhz?
Click to expand...
Click to collapse
this is from calk's rom thread
"If SetCPU, Overclock Widget, Android Overclock or QuickClock Advanced Overclock are detected, the script is ignored, so it will not affect them"
it doesnt list rom toolbox, so i dont know where that falls. id ask. hope this helped!

stretchwookie said:
this is from calk's rom thread
"If SetCPU, Overclock Widget, Android Overclock or QuickClock Advanced Overclock are detected, the script is ignored, so it will not affect them"
it doesnt list rom toolbox, so i dont know where that falls. id ask. hope this helped!
Click to expand...
Click to collapse
Actually i have found out that rom toolbox doesnt over ride it. CAULKINS battery script always seems to take over as long as you dont check the box "apply on boot" i tuink im going to dive into Tegra app for my underclocking. Heard its great and i love the idea off a slow cpu clock of 800mhz and a higher 245mhz (i beleive) gpu clock. Best of both worlda. Smooth screen and extra battery so to low cpu clock

Related

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.

[Q] CM6.1 wake issue

So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Only thing anyone can probably suggest is turning up your min clock speed. What are your profiles set to?
My screen off is 245/368 just to give it that bit extra to guarantee no wakeup issues, not that I had any to begin with, better safe than wanting to throw her up the wall (I get annoyed easy).
bahmanxda said:
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Click to expand...
Click to collapse
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Possible explination posted here by rmk40:
http://forum.xda-developers.com/showthread.php?t=884237
dhkr123 said:
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Click to expand...
Click to collapse
Thanks
no i didnt make any customization its just CM6.1 although my max clock speed is at 1497 mhz
setCPU
Screen off max 368
min 245
and profiles for temp and battery as well
the wierd thing is it doesnt happen at all when im just waking the phone up it only happens when its ringing i am thinking its my CPU issue ,i dont think it handles overclocking well ,i couldnt go over 1.1ghz (it would freeze instantly) with virouos that was the main reason i switched im gonna play with with cpu profiles for a while and see if i can get it fixed.
btw i have never flashed any radio so im guessing its the stock one
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
bahmanxda said:
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
Click to expand...
Click to collapse
With my experience I've noticed the phone runs better, and lasts longer on a single charge WITHOUT setCPU profiles. Just my opinion
bahmanxda said:
although my max clock speed is at 1497 mhz
setCPU
Click to expand...
Click to collapse
And there you have it. Overclocking can do weird things.
dhkr123 said:
And there you have it. Overclocking can do weird things.
Click to expand...
Click to collapse
Fair enough
Sent from my HTC Vision using XDA App

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.

[Q] SetCPU and battery life - am I doing this right?

I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g

My Nexus not waking up?

basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Did you try wiping everything on the phone and starting fresh. Go in the Android Revolution thread and run the superwipe script and wipe again then reinstall everything see if that helps.
I didn't look at the logcats, too tedious.
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
clarkey1269 said:
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Click to expand...
Click to collapse
Does this happen on stock. This logcat is using franco's kernel, are you UV'ing? OC'ing? Smartreflex? I don't know if actually Francisco is using official stock voltages today, or is already uv'ing a little from source.
And I just finished going through your log, there's nothing useful there; you should be getting it while it happens, or better yet would be /proc/last_kmsg immediately after the reboot; Grab it like this, for example:
Code:
adb shell cat /proc/last_kmsg > last_kmsg_on_my_pc
Also, what you're experiencing is called Sleep of Death.
chopper the dog said:
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
Click to expand...
Click to collapse
also happens on ICS not just JB
full wipe is taken out with every flash or nightly update without fail.
even did a fresh start with locking and relocking the bootloader with no effect i still get the annoying wake
Are you using any app to control your min CPU voltage? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU voltage is too low...
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
bk201doesntexist said:
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
Click to expand...
Click to collapse
Sorry I meant to say voltage
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
cayte2 said:
Sorry I meant to say voltage
Click to expand...
Click to collapse
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
bk201doesntexist said:
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
Click to expand...
Click to collapse
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
clarkey1269 said:
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
Click to expand...
Click to collapse
Does it happen when using google's factory image?
Do you have Eugene cpu sleeper installed? I was having that happen to mine and I just uninstalled, wiped caches, fixed permissions and I haven't had a problem since.
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Does it happen when using google's factory image?
Click to expand...
Click to collapse
fresh instal of googles stock image and il report back

Categories

Resources