Hi, i have searched the forums, but haven't been able to find an answer, simply put i don't believe my xoom is overclocking. I have been testing it with an app called neocore, but have tried quadrant as well. It doesn't matter if i am at 1000 or 1700 Neocore always says that my xoom runs at between 34-36 fps, which is the same as when it was bonestock, quadrant is the same. No change in animation speed or results no matter what i have set the clock too. I currently have eos nightly 77 for 4g on my xoom, I was using the stock kernel that came with the rom, and recently downloaded the.3.0.5 tiamat overclock kernel, which after flashing think it was the same(I am a noob). I was originally trying to use android overclock to adjust my settings, now have completely uninstalled it and using eos's settings, no change. What am i doing wrong, or have missed?
Thanks for any help you can give me
For increased smoothness in animation, etc, I believe it is the overclocked gpu that helps as opposed to the cpu. Not all the eos kernels are overclocked. Quadrant score appears to be meaningless. Believe me, the eos kernels permit overclocking. What governor are you using? Is your setting stable?
I have it currently at interactive, after you mentioned the governer, i put it to performance and ran the neocore benchmark to see what would happen, 38.2. Well if it requires a gpu overclock that would make sense that i am not noticing a difference with the apps i am using. But raises another question,what is a overclocked cpu good for? More apps running at once? My overclock is ALLOT more stable with 77, i was previously on 74. Before it would get glitchy allot more often, and random reboots on anything above 1000. 1400 and i was having to watch the temperature, 1500 seemed to work the best, but still got random reboots (still better than what I got on honeycomb. I still get glitches here and there on 77, but still have yet to get a.random reboot.
Unrelated to my topic, thank you so much for your guide to rooting and romming, i had read a couple others and hemmed and hawed about whether to do it, even though my mouth watered about the benefits, your guide made me clap my hands together and say "let's do this"
I went back over the kernel I downloaded and flashed, it is the team tiamat overclocked gpu 3.0.5 kernel that was realeased 2/19/2012... sorry, this stuff is new to me so I am learning as i go along
Draxin said:
I went back over the kernel I downloaded and flashed, it is the team tiamat overclocked gpu 3.0.5 kernel that was realeased 2/19/2012... sorry, this stuff is new to me so I am learning as i go along
Click to expand...
Click to collapse
No problem...the EOS nightlies are on a newer kernel, but I think the lastest don't have oc gpus.
Related
Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.
Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon
I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
What the heck? I keep hitting edit but it keeps quoting =( please delete.
sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!
Blah please delete.
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.
Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.
Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.
I've never had success overclocking my cappy. I've tried multiple kernels all with no luck. I just applied the platypus kernel on cm7 and have tried multiple settings and have yet to have a crash. Any thoughts or anyone else have any success stories?
I've been lucky to have been able to overclock up to 1.4 GHz, but anything after that my phone would just freeze and crash.
One thing to remember is that all phones react differently to different setups and because one phone can do it does not mean another phone can.
Sent from 234 Elm Street
most sgs phones have no issues at 1200 but there seems to be stability issues in undervolt kernels that different phones may or may not have difficulty working with. above 1200 some phones can some cant, many will see 1300 with slight instability and others will go all the way up to 1500 and never have an issue. micro processors are built on structures that are just a few nanometers and it is imposible to make them preform exactly the same, a nanometer or 2 on a particular semiconductor can make all the difference. it is not untill you get down to molecular sizes that you can assure identical structures. that is still years in the future.
the cm7 kernels use differnent cpu drivers and and governor settings. different developers have different tequniques so you have have found a more stable kernel.
1200 works good for everyday use for me but when I hit the 1300 range its all downhill from there.....but honestly in my opinion there is really no reason to run that fast other then for scores! I run mine around 800 honestly!
Tegrak Overclock is a neat app that lets you go up to 1.3GHz on just about any kernel I believe since I was using it on the stock Froyo kernel until I recently changed to speedmod. I haven't tried kernels created for O/Cing yet though.
Back in the days of Froyo 1.5ghz was easy for me, never had any freezes or reboots. Right now Im Running Mosaic 2 with ExistZ 0.1.6 kernel at 1.2ghz and its never given me any problems either. Maybe Im just lucky. I guess just keep trying different things man. Hopefully CM7 works out for you.
Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez
I have the same issues and have been wondering the same thing.
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?
watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
yellowfuse said:
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
Click to expand...
Click to collapse
Were you using Glitch before, or some other custom kernel? I didn't think cyanogen's stock kernel supported overclock. If you install a new nightly you have to reinstall your overclocking kernel.
I have been using cyanogenmod only. I never purposefully installed a custom kernel then the rom. Just used Odin to root/clockwork and so forth. Never heard of Glitch. Through out all of my custom rom experiences with the captivate I have been able to use the sys. settings or osmonitor to overclock to a max of 1.3ghz. I have tried miui or whatever its called for about five minutes. other than that just cm6/7, then updated to cm9. in the past whatever kernel i had, stayed in effect, i guess.
I will do a search for custom kernels for cm9 on captivate.
I havent seen any yet, but who knows. I am used to simply stunning roms and the moto droid one. That was great! SS/chevy~ would always have links to the latest kernels avail. for the current builds etc. Good job too.
SO... the search continues.
*Mystery: If I cant even change cpu settings in osmonitor (up or down), yet it lets me enable root mode, what does that mean? The greyed out overclocking area in perfomance settings (up or down)???
I need to learn more"!"
As mentioned, glitch kernel b6 is a great ics kernel. Flash over CM9 and install nstools from the market to control all the kernel settings such as oc/uv, voltages etc etc.
Sent from my glitched ICS Captivate using XDA App
The options are greyed out because the stock kernel currently doesn't support overclocking. Glitch is awesome, and Semaphore kernel is pretty nice too.
Sent from my CM9 ICS i897 Captivate
IcyGlitch for OC, and Semaphore for 400MB mem.
Well Glitch has 387 MB of free RAM
both kernels are good
I want my 13 MB! They are unused so occupying them is unforgivable. IcyGlitch is solid kernel, and I hope 400MB will be added.
b-eock said:
Well Glitch has 387 MB of free RAM
Click to expand...
Click to collapse
I recently flashed CROMI-X, and I'm loving it so far; huge improvement over stock, thanks to all involved! A quick question, though: I've been running the Quadrant benchmark, and averaging around 4400. That's a big improvement over stock, but seems quite a bit lower than any scores I see posted here; could I have messed anything up during the install, missed an important setting, ticked the wrong box, anything like that?
zarquon7 said:
I recently flashed CROMI-X, and I'm loving it so far; huge improvement over stock, thanks to all involved! A quick question, though: I've been running the Quadrant benchmark, and averaging around 4400. That's a big improvement over stock, but seems quite a bit lower than any scores I see posted here; could I have messed anything up during the install, missed an important setting, ticked the wrong box, anything like that?
Click to expand...
Click to collapse
A couple of questions here:
What Kernel did you install?
What speed do you have your CPU set at? (Assuming you installed one of the overclock kernels)
pastorbob62 said:
A couple of questions here:
What Kernel did you install?
What speed do you have your CPU set at? (Assuming you installed one of the overclock kernels)
Click to expand...
Click to collapse
_that's kernel, v4, so, no overclock...
zarquon7 said:
_that's kernel, v4, so, no overclock...
Click to expand...
Click to collapse
Yeah, if you don't have overclocking, you won't reach the benchmark results posted.
But then it is all about usability, so if you are happy, no reason to chance damaging your device by overclocking.
Sent from my TF300T using Tapatalk
zarquon7 said:
_that's kernel, v4, so, no overclock...
Click to expand...
Click to collapse
If you are content with the functionality then stick with that. But if you are experiencing lag and sluggish performance then an oc'ed kernel is the only option you have to give it a boost.
I ran CROMi-X with Hundsbauh's kernel for a year, updating with each new version. I never experienced any problems while running oc'ed and the performance was great. Hundsbauh's includes an app where you can tweak the clock speeds for both the CPU and the GPU. e.g. I set my Balanced Mode to 1500 Mhz / 484Mhz and ran that way most of the time with no issues. It was a nice balance between performance and battery life.
That said, each device is different and your results may vary, but you should be safe using CROMi-X with Hundsbauh's kernel set to a reasonable overclock. It won't let you go higher than 1700 Mhz / 520 Mhz.
pastorbob62 said:
If you are content with the functionality then stick with that. But if you are experiencing lag and sluggish performance then an oc'ed kernel is the only option you have to give it a boost.
I ran CROMi-X with Hundsbauh's kernel for a year, updating with each new version. I never experienced any problems while running oc'ed and the performance was great. Hundsbauh's includes an app where you can tweak the clock speeds for both the CPU and the GPU. e.g. I set my Balanced Mode to 1500 Mhz / 484Mhz and ran that way most of the time with no issues. It was a nice balance between performance and battery life.
That said, each device is different and your results may vary, but you should be safe using CROMi-X with Hundsbauh's kernel set to a reasonable overclock. It won't let you go higher than 1700 Mhz / 520 Mhz.
Click to expand...
Click to collapse
After my original post, I tried switching to _that v7, and saw a nice bump in performance, though I'm not sure exactly what it's overclocking it to; I may try Hundsbuah's kernel, I like the idea of tweaking the speeds myself. I had been under the impression that _that's was a bit more stable, but it seems many people use Hundsbuah's without issues.