[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix! - Page 44

rpierce99 · #**431** (**permalink**) 03-12-2011, 06:11 PM

Quote:

Originally Posted by ndno

Note that when you overclock, it doesn't mean that it will always be at that overclocked speed; it will throttle between 122mhz and the OC speed, deeping on the work load; this is done on purpose for improving battery life, like a laptop. So if you OC to 600 or 700 mhz, chances are it can operate at 480mhz 50% of the times and you won't notice any difference between the 2 OC speeds. There's a utility called setcpu that allows you to have more control of this "throttling" or "scaling" action; you can find it somewhere on Xda for free; or pay $2 to get it on the market. For example if I use setcpu to set it to use a "performance" profile, I can force the cpu to operate at 700mhz all the time and actually get a score of 630 using quadrant. Then again, leaving it like this will kill my battery life quickly.

Sent from my FRX05-ized TP2

I'm pretty sure SetCPU support isn't in our kernel right now, I know ACL wanted to put it in for NAND but hasn't yet afaik.

**ndno** · #**432** (**permalink**) 03-12-2011, 06:23 PM

Quote:

Originally Posted by rpierce99

I'm pretty sure SetCPU support isn't in our kernel right now, I know ACL wanted to put it in for NAND but hasn't yet afaik.

Hmmm..., been using SetCpu for the last 2 days. Working great. I set the max OC speed (710Mhz) in STARTUP.TXT and used/configured SetCpu under FRX05 to customize the throttling range (I hate the low range 122Mhz-320Mhz, so I forced it to throttle between 480 and 710 and it works fine). I have a few profiles setup under SetCpu, including one in which it always operates at OC speed at the times, the main one operating between 480 and 710Mhz, one at 122Mhz when it goes to sleep, and so on. Working fine for me... I verified it's working by monitoring the kernel clock debugging logs here:

/sys/devices/system/cpu/cpu0/cpufreq

stckmojo · #**433** (**permalink**) 03-12-2011, 08:48 PM

I've messed with setcpu and the only thing I really find useful about it is making sure my phone is running at the oc I set inside the startup file.

It doesn't seem to have any control over what speed things are running.

Within the last few hours I've had a few instances where my phone didn't wake up on the first click. It always seems to on the 2nd though if thats the case.

**ndno** · #**434** (**permalink**) 03-13-2011, 01:27 AM

Well, I tried this new kernel today and I had many restarts to WinMo, a few without even noticing that it happened; by this, I meant I'd be in FRX05, left it alone, went to do something else and when I came back, WinMo is showing on the screen! I had probably 5 restarts today (3 of which I didn't even notice as described above). I'm not sure if it's my setup but I'm going back to the 3/1 version to see if I still get that many restarts.

**arrrghhh** · #**435** (**permalink**) 03-13-2011, 02:29 AM

Quote:

Originally Posted by ndno

Well, I tried this new kernel today and I had many restarts to WinMo, a few without even noticing that it happened; by this, I meant I'd be in FRX05, left it alone, went to do something else and when I came back, WinMo is showing on the screen! I had probably 5 restarts today (3 of which I didn't even notice as described above). I'm not sure if it's my setup but I'm going back to the 3/1 version to see if I still get that many restarts.

Oo, that's not good.

I was getting a lot of reboots to WinMo earlier, but that was on a special build I was testing for WisTilt2. Not just this kernel, but a lot of other changes.

I'll go back to this kernel and see if I get reboots on FRX05.

stckmojo · #**436** (**permalink**) 03-13-2011, 03:06 AM

well I have found something odd.

Ever since I updated the kernel package, my voice to text refuses to work. :P

It just sits for 15 seconds after I talk, then shuts itself off.

**fishingmedic** · #**437** (**permalink**) 03-13-2011, 10:37 AM

I've been running the newest kernel all day yesterday and overnight, no issues at all, no SOD's, sometimes gotta hit power a couple of times, but much better for me. As I type this I'm praying I didn't just curse myself though lol

**arrrghhh** · #**438** (**permalink**) 03-13-2011, 12:10 PM

Quote:

Originally Posted by arrrghhh

Oo, that's not good.

I was getting a lot of reboots to WinMo earlier, but that was on a special build I was testing for WisTilt2. Not just this kernel, but a lot of other changes.

I'll go back to this kernel and see if I get reboots on FRX05.

I have run this all night and no reboots to WinMo. Not sure what's causing it for you ndno, but it's not this kernel

.

lemeiux1 · #**439** (**permalink**) 03-13-2011, 01:21 PM

I've been running it for almost a full day now and I have to say I havent had any issues except the panel not coming on to show who is calling me in time to answer (but I've had that in different kernels as well, so no real change). I do however notice my battery was excellent! I went to a pub crawl yesteday starting at 11am and used my phone all day for texts and data and whatnot and when I plugged it in at about 1:30am last night I still had about 65% battery!

thanks guys

**ndno** · #**440** (**permalink**) 03-13-2011, 01:25 PM

Quote:

Originally Posted by arrrghhh

I have run this all night and no reboots to WinMo. Not sure what's causing it for you ndno, but it's not this kernel

.

Ok, I guess it must be my setup then. Gotta go figure what I recently configured; must be setcpu acting up, screwing the clock. Gonna try again without setcpu. Thanks.

Edit: OK, I removed the setcpu widget from the homescreen and it's been working fine now (4 hours without restarting). The setcpu widget shows me the current speed and profile it was using and apparently the realtime updating it was doing is causing some sluggishness and most likely the unstableness.

Sent from my FRX05-ized TP2