[Q] Overclock on cm10 - Fascinate Q&A, Help & Troubleshooting

Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?

Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
You need a kernel that is capable of overclocking. If you look through the Development thread, you can find one to do so.

Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
youll wanna find the devil kernel in development

Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
download devil 1.6.1 for fascinate

Newest is 1.7.4 actually, get it from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/

Crawshayi said:
Newest is 1.7.4 actually, get it from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/
Click to expand...
Click to collapse
Yeah, but at the time I didn't realize he made a new folder for 1.7., so I looked but all I found was 1.6.1.. but at least, 1.6.1 won't screw your Rom if you have an old partition (current being nightly cm10)--I learned that the hard way.
Sent from my Nexus 7 using xda app-developers app

Actually 1.6.1 was for the newer partition layout I think the last one he made for the old one was 1.5.4 or something. Anyway, he just released 1.7.5 last night, grab it from http://rootaxbox.no-ip.org/derteufel/jellybean/175/ :good::good:

im using the 1.7.5 release on LagFree
i dont want to overclock it tho because idk if it would mess up my phone .

Crawshayi said:
Actually 1.6.1 was for the newer partition layout I think the last one he made for the old one was 1.5.4 or something. Anyway, he just released 1.7.5 last night, grab it from http://rootaxbox.no-ip.org/derteufel/jellybean/175/ :good::good:
Click to expand...
Click to collapse
[er, I kinda meant to say "if you have the new partition layout," not old..]
but well...... :S I was right and wrong, because the old partition layout [with /datadata] is technically the "old" layout [the one that everybody always had], until for some reason they decided to move it around, so that you only had 400MB for apps, which I quickly ran out of after restoring my TiBu apps...and then they finally came around and put /datdata back, so theoretically it's the "new" layout, but..well yeah, hopefully you know what I mean.

mvmacd said:
[er, I kinda meant to say "if you have the new partition layout," not old..]
but well...... :S I was right and wrong, because the old partition layout [with /datadata] is technically the "old" layout [the one that everybody always had], until for some reason they decided to move it around, so that you only had 400MB for apps, which I quickly ran out of after restoring my TiBu apps...and then they finally came around and put /datdata back, so theoretically it's the "new" layout, but..well yeah, hopefully you know what I mean.
Click to expand...
Click to collapse
The reason it was moved around and suddenly you only had around 400MB was because the Fassy has 2 chips, 1 is fast as hell and the other is slow. Problem was, the fast chip only had so much storage space, so that was the trade off, good performance but poor storage space. For the newest layout, Jt didn't simply just 'put back' /datadata, the new layout actually is a completely new arrangement that gives us the fast speed AND storage space. If you want to read about it go over to the CM10 thread on Rootzwiki, Jt explained what he did. What this means in practical terms is that we now have a device with good speed and storage space that can handle the newer Android OSes :good:

whats the worst that can happen if you overclock ?

AndroidGee209 said:
whats the worst that can happen if you overclock ?
Click to expand...
Click to collapse
Short term: Glitchy behavior (freezing/crashing/etc) and random reboots (this is more likely if you're doing Live OC versus just bumping up your CPU MHz)
Long term: Shortened device lifetime due to component stress; in other words if you plan to use your phone for a very long time don't overclock
Not all phones react the same way to overclocking, you might not get the same results as others are. For example, a lot of people seem to have good luck with 110% Live OC, however I can only get 105% on my phone before it becomes unstable.

Crawshayi said:
The reason it was moved around and suddenly you only had around 400MB was because the Fassy has 2 chips, 1 is fast as hell and the other is slow. Problem was, the fast chip only had so much storage space, so that was the trade off, good performance but poor storage space. For the newest layout, Jt didn't simply just 'put back' /datadata, the new layout actually is a completely new arrangement that gives us the fast speed AND storage space. If you want to read about it go over to the CM10 thread on Rootzwiki, Jt explained what he did. What this means in practical terms is that we now have a device with good speed and storage space that can handle the newer Android OSes :good:
Click to expand...
Click to collapse
Exactly
AndroidGee209 said:
whats the worst that can happen if you overclock ?
Click to expand...
Click to collapse
You remember that Mayan end of the World thing...
Crawshayi said:
Short term: Glitchy behavior (freezing/crashing/etc) and random reboots (this is more likely if you're doing Live OC versus just bumping up your CPU MHz)
Long term: Shortened device lifetime due to component stress; in other words if you plan to use your phone for a very long time don't overclock
Not all phones react the same way to overclocking, you might not get the same results as others are. For example, a lot of people seem to have good luck with 110% Live OC, however I can only get 105% on my phone before it becomes unstable.
Click to expand...
Click to collapse
Again, exactly...
Yep I accidently at my OC too high once and I got an immediate reboot, setting itself back to std
Sent from my swagger

Related

SetCPU and the X0

Now that the X10 is rooted, anyone install SetCPU yet. And if so is it fully functional?
Yeah, it's working fine for me.
Fuzalert2k said:
Yeah, it's working fine for me.
Click to expand...
Click to collapse
And you can change ur signature now
Fuzalert2k said:
Yeah, it's working fine for me.
Click to expand...
Click to collapse
Ok, good, I'll buy it now and get back to yaz...
Fuzalert2k said:
Yeah, it's working fine for me.
Click to expand...
Click to collapse
Oh... did you manage to overclock, if so, what was the highest stable overclock?
RodneyBR said:
Ok, good, I'll buy it now and get back to yaz...
Click to expand...
Click to collapse
No dude, don't buy it! it's free for XDA users.
RodneyBR said:
Oh... did you manage to overclock, if so, what was the highest stable overclock?
Click to expand...
Click to collapse
No, it won't let me go higher than 993 mhz
if decrease the clock speed to the max of 600mhz,will it save more power?
yeah tried as well and the max is 993mhz. weird
(unless i'm missing something, I never used setcpu before)
I use OverclockWidget for my wife's X10.
Off screen frequency : 250~384
On screen frequence : 576~1000Mhz
it work like charm !
but your not going over 1000mhz? not overclocking
Mod. edit: not dev related, moved to general
Fuzalert2k said:
No dude, don't buy it! it's free for XDA users.
Click to expand...
Click to collapse
It's free, really. How does that work?
czw2002cn said:
if decrease the clock speed to the max of 600mhz,will it save more power?
Click to expand...
Click to collapse
Well, I just leave it set to "ondemand", so that way it will automatically adjust the speed as needed (Max: 998MHz, Min: 245MHz). My max is 998MHz.
what firmware we can use? which is highly recommended? R2BA026?
SetCpu and more, can we use Juice defender to increase autonomy
RodneyBR said:
Well, I just leave it set to "ondemand", so that way it will automatically adjust the speed as needed (Max: 998MHz, Min: 245MHz). My max is 998MHz.
Click to expand...
Click to collapse
you know the phone does that anyway right?
I don't speak French so I can't comment on that but I've been using SetCPU since the 020 root and it SEEMS to work alright. Sometimes when I open it, it says something about failing but then it works OK.
I'm currently on R2BA026 rooted and it works for me. I also use JuiceDefender but to be honest I'm getting more and more convinced that's not helping any more. JuicePlotter in particular is struggling and keeps stalling, with gaps in the graph frequently, not sure why but that's not relevant to this thread so I'll leave that.
But I do NOT use it to overclock and would not recommend that! For a start, it would cane the battery. Rather, I use it to "throttle" the CPU speed. I think that's what most of us use it for. E.g. when the screen is off, it stops the CPU working too hard (and thus saves battery). Also when power is running low, CPU is throttled to save it. By throttled I mean "restricted to 245Mhz".
It's free to XDA members because the dev kindly put it up here somewhere for download - if you're looking for "how that works" on the Market, stop now because that's not how it works! The Market doesn't give you a discount for being on XDA.
Just search for it on here, or wait for someone who has used it to point you in the right direction. I'd search for it for you but I'm about to head out.
Ungruntled said:
I don't speak French so I can't comment on that but I've been using SetCPU since the 020 root and it SEEMS to work alright. Sometimes when I open it, it says something about failing but then it works OK.
I'm currently on R2BA026 rooted and it works for me. I also use JuiceDefender but to be honest I'm getting more and more convinced that's not helping any more. JuicePlotter in particular is struggling and keeps stalling, with gaps in the graph frequently, not sure why but that's not relevant to this thread so I'll leave that.
But I do NOT use it to overclock and would not recommend that! For a start, it would cane the battery. Rather, I use it to "throttle" the CPU speed. I think that's what most of us use it for. E.g. when the screen is off, it stops the CPU working too hard (and thus saves battery). Also when power is running low, CPU is throttled to save it. By throttled I mean "restricted to 245Mhz".
It's free to XDA members because the dev kindly put it up here somewhere for download - if you're looking for "how that works" on the Market, stop now because that's not how it works! The Market doesn't give you a discount for being on XDA.
Just search for it on here, or wait for someone who has used it to point you in the right direction. I'd search for it for you but I'm about to head out.
Click to expand...
Click to collapse
we cant overclock anyway until there is a custom kernel. and you get bet your arse that when there is one, ill be overclocking to the max zoooom
I've used SetCPU for a few weeks and now I've been using my X10 without SetCPU for a few weeks and I've noticed zero difference in power consumption.
I'm guessing Android does a fine job itself at downclocking the CPU when it doesn't have to do heavy tasks.
Cinner said:
I've used SetCPU for a few weeks and now I've been using my X10 without SetCPU for a few weeks and I've noticed zero difference in power consumption.
I'm guessing Android does a fine job itself at downclocking the CPU when it doesn't have to do heavy tasks.
Click to expand...
Click to collapse
Same here. i just uninstalled it and my phone is also more stable.

setcpu?

Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
xsalientx said:
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
Click to expand...
Click to collapse
setcpu is the only and the best overclocking app. If u want to be able to overclock ur phone us have to flash jt1134s 1.2ghz voodoo kernel then use can use setcpu to overclock to 1.2ghz!
sent from my fascinate rooted and ocl'd to 1.2ghz with voodoo
xsalientx said:
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
Click to expand...
Click to collapse
SetCPU is the most popular one. You'll need root to even use SetCPU. And you'll need CWM to flash the OC Kernels. If you dont OC SetCPU is pointless
On that note.
SetCPU must be ran on conservative and with no profiles and no load on boot.
If you do reboot your phone, mine reverts back to 800, so I need to manually change it to 1200.
Do u have to set both min & Max to 1200???
no just the max
Sent from my LV-Voodoo Fascinate using XDA App
saps said:
SetCPU is the most popular one. You'll need root to even use SetCPU. And you'll need CWM to flash the OC Kernels. If you dont OC SetCPU is pointless
Click to expand...
Click to collapse
Not pointless. You can always underclock to spare your battery life
Sent from my SCH-I500 using XDA App
jt1134 said:
Not pointless. You can always underclock to spare your battery life
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes, of course you are right. Actually the other day I forgot to slide sliders up from 800 to 1200 and I was getting really good battery life for like 2 hours my % only dropped 1% and I was like wow.
Im just pleased as punch that there are OC/UV kernels out, its the best of both worlds.
Actually my battery life is above average it seems; either that or my usage is below average so Im not draining it as much. I'd gladly mildly overvolt to something like 1350mV if it meant I'd be rock solid stable at say 1.4Ghz
BTW, jt I heard you might be getting out the kernel speed chase after these 1.2Ghz's? Just don't feel like chasing 1.3 or 1.4?
I am running Dirrk's D012 LV 1200 Kernel with SetCPU
Luckily, the LV runs EXTREMELY smooth on my phone..
So smooth, that for the past day now I have been able to run with "set on boot" and constant restarts on my phone..and with Profiles for Screen Off, Temp (probably wont get there), and Charging. I can say that I have had no problems with my profiles and set on boot. Then again, I don't want to contribute to hurting anyone's phone
Just thought I'd let everyone know how my phone (and potentially others) can seem to handle profiles and set on boot.
johnz1 said:
I am running Dirrk's D012 LV 1200 Kernel with SetCPU
Luckily, the LV runs EXTREMELY smooth on my phone..
So smooth, that for the past day now I have been able to run with "set on boot" and constant restarts on my phone..and with Profiles for Screen Off, Temp (probably wont get there), and Charging. I can say that I have had no problems with my profiles and set on boot. Then again, I don't want to contribute to hurting anyone's phone
Just thought I'd let everyone know how my phone (and potentially others) can seem to handle profiles and set on boot.
Click to expand...
Click to collapse
No problems with set on boot here either. I keep it on.
so how do i use setcpu/what are the steps i need to take?
xsalientx said:
so how do i use setcpu/what are the steps i need to take?
Click to expand...
Click to collapse
Install it, tell it to auto detect, set the max where you want, leave the min at 100, and then leave it alone.
Sent from my SCH-I500 using XDA App
I was hoping to get some help. I have installed jt's 1200 voodoo kernal, and I can't seem to get Setcpu to clock at 1200. It still says that the max is 800, however, on the slide it is only giving me the option to goto 528. Bellow are my facts, any help would be great!
Facts:
1. flashed jt's overclocked voodoo use clockwork, but did it through "install ROM from sd card". I am not sure if this is correct, but it seems to be running voodoo.
2. I have no idea how I need to have Setcpu set up.
I feel like I am blindfolded and I am trying to wack at a pinata.
thanks.
Edit: never mind...even a blind folded monkey hits the pinata every now and then

[Q] G Tab wont overclock

I dont know if anyone is having this problem but on pretty much any rom/bootloader combination my tablet will only run at stock speeds and if the rom is overclocked on first boot my tablet just wont boot at all, I know some processors are slower than others but is it really likely that mine maxes at 1 GHZ? If i use setcpu to OC when a rom is running smoothly it will run fine for about 1-2 minutes or until i needs a lot of cpu then it just freezes. Any ideas to fix this, or just help understanding what is going on would be appreciated. My CDMA hero overclocks just fine and crashes instantly if i go too far unlike the tablet.
I know that this will sound like a stupid question, but are you certain that you've loaded a kernel that allows for overclocking?
what rom/kernel combinations have you tried?
Calkulin Clemsyn combo is what I'm using, and the overclocking appears to be working fine with Clemsyn's kernel.
Try CPU master from market. The free version works fine. Should do what your looking for. I have the paid version of Set CPU and it has never worked on gtab for me.
Mantara said:
Try CPU master from market. The free version works fine. Should do what your looking for. I have the paid version of Set CPU and it has never worked on gtab for me.
Click to expand...
Click to collapse
Well, I'm surprised no one before me has tried to make this clear yet. Pershoot's kernels are written for setcpu. Clemsyn's kernels are written for cpu master. Make sure you use the right cpu app.
TJEvans said:
I know that this will sound like a stupid question, but are you certain that you've loaded a kernel that allows for overclocking?
what rom/kernel combinations have you tried?
Calkulin Clemsyn combo is what I'm using, and the overclocking appears to be working fine with Clemsyn's kernel.
Click to expand...
Click to collapse
Ive tried pershoot and clemsyn neither work though pershoot is more stable
Mantara said:
Try CPU master from market. The free version works fine. Should do what your looking for. I have the paid version of Set CPU and it has never worked on gtab for me.
Click to expand...
Click to collapse
Im installing that now, hopefully it works, it should, ive only tried setcpu to this point.
EDIT: nope, it still locks up, maybe my tablet just wont go that fast?
whodatxevg said:
Im installing that now, hopefully it works, it should, ive only tried setcpu to this point.
EDIT: nope, it still locks up, maybe my tablet just wont go that fast?
Click to expand...
Click to collapse
Not all chips can be overclocked to the extreme. A few can't handle it at all. Try some small increases at first to see if your chip can handle it.
I've also had some luck with finicky chips using PimpMyCPU with Celmsyn's kernel since it allows you to set specific speed and voltage combinations (Not sure if CPU Master allows that... never used it). So you might give that a try.
whodatxevg said:
I dont know if anyone is having this problem but on pretty much any rom/bootloader combination my tablet will only run at stock speeds and if the rom is overclocked on first boot my tablet just wont boot at all, I know some processors are slower than others but is it really likely that mine maxes at 1 GHZ? If i use setcpu to OC when a rom is running smoothly it will run fine for about 1-2 minutes or until i needs a lot of cpu then it just freezes. Any ideas to fix this, or just help understanding what is going on would be appreciated. My CDMA hero overclocks just fine and crashes instantly if i go too far unlike the tablet.
Click to expand...
Click to collapse
me to Calkulin Clemsyn combo is what I'm using, and the overclocking appears to be working fine with Clemsyn's kernel. from 1k to 1.5 k and works great and I am using CPU master also
Are you clearing davlik cash between each kernel switch?
goodintentions said:
Well, I'm surprised no one before me has tried to make this clear yet. Pershoot's kernels are written for setcpu. Clemsyn's kernels are written for cpu master. Make sure you use the right cpu app.
Click to expand...
Click to collapse
Only his latest kernels have worked with it. Setcpu didn't get on there end of the process until late may-ish, I believe, when they finally supported tegra2. Still CPU master works with pershoots kernels too. Its basically a re-branded copy of setcpu anyway.
No matter what combo of app/kernel/rom it wont go to 1200 and not lock so im just thinking its one of the slower tegras, which sucks but oh well
goodintentions said:
Well, I'm surprised no one before me has tried to make this clear yet. Pershoot's kernels are written for setcpu. Clemsyn's kernels are written for cpu master. Make sure you use the right cpu app.
Click to expand...
Click to collapse
WHAT?! How have I never read that! Thanks GI.
brettdwagner said:
WHAT?! How have I never read that! Thanks GI.
Click to expand...
Click to collapse
That's just it. It's not written anywhere before I wrote it. It's like masturbation. It's not really written anywhere for a 12 year old to learn about. Eventually, they all figure it out on their own... or they become the 40 yr old virgin.
Not positive it will work but for desktops, back when I overclocked religiously, instability could be helped by raising voltages. But it might increase heat which also leads to more instability. Lucky for us, tegra 2 is low voltage.

[Q] Phone freezing after flashing 2.3.6 rom

A couple weeks ago, I flashed the stock 2.3.6 rom using Mobile Odin Pro to retain root. Immediately afterward, I used CWM to flash Entropy's DD kernel. Then I did some undervolting with SetCPU. These are the voltages I have set right now:
1200 - 1175mv
1000 - 1100mv
800 - 1050mv
500 - 950mv
200 - 850mv
They're well within the suggested minimums from several threads.
Anyway, my phone has been freezing about once a day since then. It always happens the same way: the screen and capacitive buttons become unresponsive, and after a few seconds the phone reboots. Could the undervolting be causing it? Is there something else you guys can think of that might be causing it?
EDIT: Also, every time this happens, I lose quite a bit of battery charge. Like, if my battery was at 50% before the reboot, it'll be somewhere around 10% afterwards. Is that normal? I've attached a screenshot.
raptor102888 said:
A couple weeks ago, I flashed the stock 2.3.6 rom using Mobile Odin Pro to retain root. Immediately afterward, I used CWM to flash Entropy's DD kernel. Then I did some undervolting with SetCPU. These are the voltages I have set right now:
1200 - 1175mv
1000 - 1100mv
800 - 1050mv
500 - 950mv
200 - 850
They're well within the suggested minimums from several threads.
Anyway, my phone has been freezing about once a day since then. It always happens the same way: the screen and capacitive buttons become unresponsive, and after a few seconds the phone reboots. Could the undervolting be causing it? Is there something else you guys can think of that might be causing it?
Click to expand...
Click to collapse
Have you set the voltages back to stock for a few days and seen if the freezing stops? That would be the first thing I would try Not all chips can handle the oc/uv
yoderk said:
Have you set the voltages back to stock for a few days and seen if the freezing stops? That would be the first thing I would try Not all chips can handle the oc/uv
Click to expand...
Click to collapse
What do you mean about not all chips being able to handle it? Do you mean there is variation among different i777 devices? Or variation among different types of phones? Because the latter is obvious...
raptor102888 said:
What do you mean about not all chips being able to handle it? Do you mean there is variation among different i777 devices? Or variation among different types of phones? Because the latter is obvious...
Click to expand...
Click to collapse
WHY DO YOU THINK THE DEVICE WASN'T SOLD WITH THESE VOLTAGES? What part of "every device is different" didn't you understand? What part of:
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING OR UNDERVOLTING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC/UV in BIG GIANT RED LETTERS in one of the first four posts of my kernel thread didn't you understand?
I have ZERO tolerance for someone who flashes **** and clearly didn't even bother reading ANY part of the thread.
raptor102888 said:
What do you mean about not all chips being able to handle it? Do you mean there is variation among different i777 devices? Or variation among different types of phones? Because the latter is obvious...
Click to expand...
Click to collapse
Well if you would read a little (as entropy clearly stated) not all chips are the same, some can handle oc/uv and some can't. Seems like you are one of the ones that can't.
Sent from my SAMSUNG-SGH-I777 using xda premium
Wow, ok. I understood the risks to undervolting, and I realize I'll probably have to stop doing it. I was just hoping that this problem could be from some other cause so I wouldn't have to.
By the way, I read your entire thread, all 109 pages of it, before I flashed.
Sorry for being a noob guys. Go ahead and close this thread I guess.
Sent from my SAMSUNG-SGH-I777 using xda premium
You know, its posts like this that make Entropy rage and not want to help members or post his awesome kernels.
I think we should make some stipulations that users cant download attachments until they hit 25 posts, that way they have been around long enough to know how to read and search.

[Q] lulzactive cpu problem

I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2

Categories

Resources