Database Users

Anyone else not able to clock over 1100?

After trying out all the 1200 and the 1250 kernels, my phone just doesnt like them while using setcpu. With Setcpu set at performance and maxed out at 1200 my phone will run for a little bit and then lock up. If I try to run a quadrant it will freeze up when the immage starts to walk up the steps to the blue room requiring a battery pull. I am currently running an 1100 kernel that is stable on my phone but would like to run 1200 or even higher as 2.2 comes out and newer kernels are released. Is anyone else having a problem running above 1100? I'm still within my 30 day window and could easly take it back and get another phone, but in reality there is nothing wrong with the one I have, I just want it to run faster (than intended) so would I be wrong in taking it back to get a new one that will run at 1200 or higher? Thanks.

You should be running in conservative mode in setcpu regardless of the kernel...should fix your problem...
Sent from my rooted 1.2 voodoo Fascinate

vecchioni27 said:
You should be running in conservative mode in setcpu regardless of the kernel...should fix your problem...
Sent from my rooted 1.2 voodoo Fascinate
Click to expand...
Click to collapse
Why is that? I always ran performance on my Incredible without a problem. Granted, I realize that this is a different phone/processor. Wouldn't Conservitive keep the processor from max performance?

No, it will rev up the processor when you need it. I don't know if this will stop your phone from freezing while it's being taxed hard @ 1200 though ie Quadrant
Some people can run 1250, some have to stick to stock speed. I think it's mostly luck.

I think its because of all the different hardware they put into this phone to pump it out. Ontop of that the kernel code was not complete that samsung released.
Sent from my SCH-I500 using XDA App

[Q] Cant Overclock???

Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??

mike21pr said:
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
Click to expand...
Click to collapse
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel

Freek91 said:
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Click to expand...
Click to collapse
im using faux right now. ill see if i can find another one thats good to try out
thnx

i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board

mike21pr said:
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
Click to expand...
Click to collapse
well like im sure you've seen or heard...all hardware is different
so while 1.8ghz maybe slow...going down to 1.5 maybe quick and the opposite maybe true for someone elses phone...they may just totally fly at 1.8 while they grind to a halt at 1.5
so keep messing with it and see what happens...change clock speeds...change up the governors...just dont OC it to 1.8 and think the phone will magicly hit a 4100 quadrant and not have any issues
worse case...flash a different kernel and see how it acts
also on that topic...you said you were running IG...did you run the stock kernel for any length of time? did you try and OC that one?

Random lockups

As per the title, I have started experiencing random system lockups since yesterday. I have had to perform two battery pulls and I'm starting to worry that my ext partition won't be so lucky next time...
I have no idea what is causing the lockups, though both have occurred while using Swype. Coincidence?
For now I'm going to set my system clock back to 600Mhz and use the default input method for a while and see if I still get lockups, at which point I will probably flash another ROM unless I can find a solution, which is where you guys (hopefully) come in. Is there anything else I can do to diagnose and/or solve the problem?
- Typed from my rooted HTC Legend -

It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version

Try interactive governor or flash latest kernel from the other thread.

TheGrammarFreak said:
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Click to expand...
Click to collapse
That's peculiar, as I've had the processor on 768Mhz for a while now and I've had no problems at all before now.
As for Swype... it could be. ;P
BlaY0 said:
Try interactive governor or flash latest kernel from the other thread.
Click to expand...
Click to collapse
I'll try that, but what exactly does each governor do?

segphault said:
I'll try that, but what exactly does each governor do?
Click to expand...
Click to collapse
It manages when the processor speeds up. It doesn;t run at 768MHz all the time, that's just the highest you allow. Ondemand scales the frequency up when it's needed, and lowers it again afterward. It seems to be a little bugged in our kernels though, and causes crashes.
Interactive does a similar thing, but without polling the CPU. It also ramps the frequency up a little more quickly. I use it, it makes the phone more responsive (IMO), and also eliminates the need for profiles in setCPU (to a degree)

Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.

segphault said:
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
Click to expand...
Click to collapse
You'd have to mess around with kernel source code. I wouldn't know where to begin, sorry

Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App

MaBlo said:
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
That did cross my mind but other users have reported success with it, so I figured I might as well give it some investigation.

I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows

TheGrammarFreak said:
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
Click to expand...
Click to collapse
Maybe not quite 19Mhz, then.
Perhaps we should do some testing to see how much processing power is needed to wake the phone quickly? Is there any way to test that?

Back on topic, I just had another lockup while using the interactive governor. This time I froze up while loading Fruit Ninja.
Now I'm at a total loss for what could be causing the lockups.
- Swyped from my rooted HTC Legend -

Seeing as nobody can seem to pin-point the problem, I'm moving to CM7 permanently as soon as it's released as stable.

overclocking

how do I overclock my vibrant safely without destroying it??

Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Try installing an overstock kernel, like Eugene373's Deadhorse Kernel, then you can download One Click Lag Fix from the market.

Just install a kernel that has oc capabilities and use set CPU to adjust the frequencies
Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA Premium App

I have overstock 2.2 with minimum at 400mhz and used spare parts to set windows to fast. This thing HAULS ASS!
Sent from my GT-I9000 using XDA App

If he asks how to install an OC kernal I'm reporting this thread to be closed.

LOL
Sent from my SGH-T959 using XDA App

after you have the oc kernel installed go into set cpu and set an audible alarm and for when your temp goes above 115 Fahrenheit, in that profile have it drop your clock speed down to 1000 or 800 to help your phone cool off before reactivating the full oc. Ive never had any problems with the cpu getting to hot oc'd to 1.2 thats not to say you wont.
Cheers

I don't think that overclocking and not destroying can be done at the same time.
Sent from my SGH-T959 using XDA App

Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Flash it, set clock speed with setcpu or voltage control, cross your fingers and hope for the best.
Sent from my SGH-T959 using XDA Premium App

All you need is a kernel that supports OC ie. (DoW, Tigersblood, Overstock, Dragon) you should be golden but double check compatibility with whatever ROM ur running.
I use "set cpu" to torque it up to 1.2(or whatever the kernel OC's to) Then i use "SystemPanel Lite" to check and make sure its actually OCing. In the system app it has a CPU Clock in the top right corner which monitors ur current cpu. When the system app opens it has a list of active applications i simply move the list up and down repeatedly really fast and watch the "CPU Clock" if it maxes out at 1.2 or whatever its good to go. I remember one time(cant remember what kernel)but set cpu showed 1.2 or 1.4 and even in system CPU info it showed OCed but if you did like i just described the CPU Clock never went above 1000Mhz. Like it was just showing as OC even tho it really wasn't it was really weird the clock would max out at 1000Mhz with dead space above it like it could go over but never would.
shreddintyres said:
after you have the oc kernel installed go into set cpu and set an audible alarm and for when your temp goes above 115 Fahrenheit, in that profile have it drop your clock speed down to 1000 or 800 to help your phone cool off before reactivating the full oc. Ive never had any problems with the cpu getting to hot oc'd to 1.2 thats not to say you wont.
Cheers
Click to expand...
Click to collapse
i never knew you could set audible alarms(guess i never really looked into it) thanks for that! running DoW221 OC to 1.4 i used to see my temps hit 120-130 it would freak me out! but never had any problems except for batt life avg 6-7hrs.
Personally my best OC ROM/kernel setup to this date has been MALICE[EDT]+Tigersblood(any release) everything works and great batt life for a OC kernel

Binary100100 said:
If he asks how to install an OC kernal I'm reporting this thread to be closed.
Click to expand...
Click to collapse
LOL
funny

Just make sure you backup before trying. Some Vibrants cannot handle overclocking (and there's no real way to know until you try). Mine is one of those, and if it can't handle it, an Odin to stock will be in your immediate future.

Overclocking ROMs heat issue?

I am going to be getting an Atrix in the next few days and will install the Aura ROM right off the bat, but im wandering, since it appears to use an OC'ing kernal, what effect will this have on heat and battery life? presumably negative, but how much so? i dont want another phone which heats up like mad, but i do like the look of the ROM. please help out an Android n00b
thanks

Just because it can overclock doesn't mean you have to. I use set cpu and keep mine undervolted and set to 1.1ghz. Idle around 30 celsius and when I game it gets up to 50 degrees.
Sent from my MB860 using xda premium

the atrix on stock 1.0 ghz gets REALLY hot so yea i would assume it would just get hotter MUCH hotter but you can get a setcpu and just set your processor down when you dont use it much or make profiles to automatically do it

great, so the rom just allows OCing, not forces it? thats good to know, thanks

ishamm said:
great, so the rom just allows OCing, not forces it? thats good to know, thanks
Click to expand...
Click to collapse
it will automatically clock itself to 1.3ghz, you'll need a program like SetCPU or PimpMyCPU to set it to not OC itself.
i suggest SetCPU myself, it can be found on the market. i prefer buying it over getting it for free here on XDA, we gotta support our devs right?