• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root limited overclocking

I had my first full freeze today on JT's original 1.2GHz kernel, it happened as i woke my phone up and tried to hit 'messaging' (it started to open but just froze before it did.. i waited 10 minutes but it just stuck at that screen, unable to be powered off). I had to do a battery pull for the first time ever =(. I'm not sure if it was related to how long i had the phone on OR my settings in SetCPU. I followed saps's advice on 1200 max and 100 min, but perhaps the 100 min was my problem? The phone also displayed that it had 50% battery before the incident (it had been on for about 25 hours), but as soon as i battery pulled and booted it the battery was in the orange, at about 20%.

Since then I set the min to 200.. not sure if that's related though.
 
On a freaking side note, there's a 1.6GHz kernel now too if I'm reading correctly.

EDIT: with STANDARD voltage


............
 
zero_one said:
I had my first full freeze today on JT's original 1.2GHz kernel, it happened as i woke my phone up and tried to hit 'messaging' (it started to open but just froze before it did.. i waited 10 minutes but it just stuck at that screen, unable to be powered off). I had to do a battery pull for the first time ever =(. I'm not sure if it was related to how long i had the phone on OR my settings in SetCPU. I followed saps's advice on 1200 max and 100 min, but perhaps the 100 min was my problem? The phone also displayed that it had 50% battery before the incident (it had been on for about 25 hours), but as soon as i battery pulled and booted it the battery was in the orange, at about 20%.

Since then I set the min to 200.. not sure if that's related though.
Click to expand...

You know, I had an issue with freezing last night as well, same kernel. I wanted to put it to the test and was going through the NFS demo, and the second time I ran it the phone froze in the "sitting behind the starting line waiting to go" phase. Had to pull out the battery as well, although I was plugged in at the time so I can't comment on the usage.

SetCPU was set to 200/1200 Conservative.
 
Moonfire said:
You know, I had an issue with freezing last night as well, same kernel. I wanted to put it to the test and was going through the NFS demo, and the second time I ran it the phone froze in the "sitting behind the starting line waiting to go" phase. Had to pull out the battery as well, although I was plugged in at the time so I can't comment on the usage.

SetCPU was set to 200/1200 Conservative.
Click to expand...

Hmm.. sounds like its not related to the usage or the minimum setting then. A little disheartening, but it's more than probable (as was initially stated anyway) that there are a few quirks that still need tweaking. I only installed this yesterday, so I suppose I should wait for more long term testing.
 
Running at 1.4 GHZ here got a quadrant of 970+ without lag fix and feels very smooth and quick with no issues I will have to see how batter life is affected


edit: Games dont seem to like the new speed playing gangstar and Hawk freeze before getting past the menus. I thought it was the speed but i set it to 1400 min and max and am able to surf the web play with the app drawer or anything it is just the games that freeze up
 
Been testing for about 5 hours now with no problems and one freeze when I tried Quadrant for a third time in a row. A little more battery drain but hardly enough to get me back to stock or even a low voltage 1200. A 1600 is available but I'm unwilling to change how it is now. I like 1400 a lot.

dJQgB.png


jaLm0.png
 
zero_one said:
I had my first full freeze today on JT's original 1.2GHz kernel, it happened as i woke my phone up and tried to hit 'messaging' (it started to open but just froze before it did.. i waited 10 minutes but it just stuck at that screen, unable to be powered off). I had to do a battery pull for the first time ever =(. I'm not sure if it was related to how long i had the phone on OR my settings in SetCPU. I followed saps's advice on 1200 max and 100 min, but perhaps the 100 min was my problem? The phone also displayed that it had 50% battery before the incident (it had been on for about 25 hours), but as soon as i battery pulled and booted it the battery was in the orange, at about 20%.

Since then I set the min to 200.. not sure if that's related though.
Click to expand...
Yeah I dont know. 100min works fine for stock, but yeah many people end up at 200 it may or may not make a diff.
 
zero_one said:
On a freaking side note, there's a 1.6GHz kernel now too if I'm reading correctly.

EDIT: with STANDARD voltage


............
Click to expand...
My word Im gone a few hour and this pops up. 1.6Ghz was always considered the theoretical ceiling too; we hit it awfully fast
 
Moonfire said:
You know, I had an issue with freezing last night as well, same kernel. I wanted to put it to the test and was going through the NFS demo, and the second time I ran it the phone froze in the "sitting behind the starting line waiting to go" phase. Had to pull out the battery as well, although I was plugged in at the time so I can't comment on the usage.

SetCPU was set to 200/1200 Conservative.
Click to expand...

Freezing almost assuredly is due to lack of voltage. Its always tough to calculate or even guess how little/much voltage the cpu needs at any given speed. Usually dev's guess too low and you get lock-ups. Frustrating but its better than guessing too high I suppose

zero_one said:
Hmm.. sounds like its not related to the usage or the minimum setting then. A little disheartening, but it's more than probable (as was initially stated anyway) that there are a few quirks that still need tweaking. I only installed this yesterday, so I suppose I should wait for more long term testing.
Click to expand...
I do think its valuable to remember that these kernals were not actually indeeded for release as early as they were. But one they were out the dev's have been scrambling to try and make them stable.
On day 3 [2.5] of jt's 1.2 and my only issue is worse battery life. Have yet to have a single freeze lock up. Very tempted by the 1.4 though
 
erasmogjr said:
Running at 1.4 GHZ here got a quadrant of 970+ without lag fix and feels very smooth and quick with no issues I will have to see how batter life is affected


edit: Games dont seem to like the new speed playing gangstar and Hawk freeze before getting past the menus. I thought it was the speed but i set it to 1400 min and max and am able to surf the web play with the app drawer or anything it is just the games that freeze up
Click to expand...
Hmm that sounds a bit low actually on Quadrant. I hit 978 with 1.2 [no lag fix]
As aforementioned, I think the issues everyone is having is lack of voltage its why non intensive functions are fine but cpu intensive functions sometimes lock up. So to the dev's:
we need more power
StarTrek_Scotty.jpg
 
Gitykins said:
Been testing for about 5 hours now with no problems and one freeze when I tried Quadrant for a third time in a row. A little more battery drain but hardly enough to get me back to stock or even a low voltage 1200. A 1600 is available but I'm unwilling to change how it is now. I like 1400 a lot.
Click to expand...
Lovely simply lovely. Did you happen to try the 1.2 as well? Im wondering how the battery compares if you did? I do actually notice a difference, in terms of JT's 1.2 being worse than original stock.

Also anyone know when Dirrk says standard does he mean factory default? I'm also trying to get his numbers for his low voltage settings
 
Yeah, I used 1.2 and I noticed a significant difference between that and stock, but the jump from 1.2 to 1.4 hardly changed it at all. Maybe it's because I haven't tested it thoroughly and I've only been using it for about 6 hours, but I think that 1.2 is just basically a waste of time if the pattern I'm seeing with 1.4 continues.

And I think Dirrk's SV kernels are default (1350 mV?) and LV is under 1250 (1200 maybe, almost unsafe)

As you can see, I don't like the looks of the seriously run down voltages. I think stock voltage or maybe 50 below that is just fine for default clock, and stock should be good for almost any OC.
 
saps said:
Lovely simply lovely. Did you happen to try the 1.2 as well? Im wondering how the battery compares if you did? I do actually notice a difference, in terms of JT's 1.2 being worse than original stock.

Also anyone know when Dirrk says standard does he mean factory default? I'm also trying to get his numbers for his low voltage settings
Click to expand...

yes I believe standard is factory default.
 
OK good stuff. The cpu default max is 1300mV. So Im wondering if 1300mV is all thats powering both the 1.4 and the 1.6. Thats a tad hard for me to imagine. I know JT's 1.2Kernal goes up to 1325mV and that was rock stable for me. Im almost expecting 1.4 and 1.6 to need 1350 or 1375 to run stably and thats fine with me.
Equally true I know the Sprint Epic crew has a 1250mV 1.2Kernal who's battery life exceeds the stock 1Ghz.
I guess like anything we dont know till we try.

BTW, and this is for all. You guys are NOT doing Set on Boot right? While this does add the slight inconvenince of going into SetCPU to re-autodetect and re-slide the slider. If you get locks with 1.4 or 1.6 it also wont keep you trapped there since the kernals by default I think either boot at 800Mhz or 1Ghz
 
zero_one said:
yes I believe standard is factory default.
Click to expand...
See that almost doesn't make sense. I'm all for using as little voltage as needed. But equally true if JT pumps 1325mV for 1.2Ghz and is stable what is Dirrk thinking giving just 1300mV for 1.4Ghz :confused:. Voltage always has to go up with OCing you need more juice.

I see Dirrk has just pulled down his 1.4 and 1.6 Kernals [right as I was going to grab the 1.4 :mad:] but this is no doubt for tweaking and probably/hopefully a small incremental voltage bump up
 
Gitykins said:
1400standardmv.zip

Maybe because it's effed up, I wasn't noticing any battery change.

He says not to install it though, so maybe flash it and check it out but don't leave it going?
Click to expand...
This is Dirrks that just got pulled off right? Thanks. I love seeing you guys here and at xda...at the same time...just like me...gotta love tabs:D
 
Had my second complete freeze and battery pull last night as I tried to access a message from the lock screen. Went back to stock kernel.
 
You must log in or register to reply here.
Back
Top Bottom