Separate names with a comma.
Discussion in 'Droid Kernels' started by prime, Feb 22, 2011.
reprimed compcache isnt working?
Not correctly, the size gets multiplied by 100 because of the recent CM changes...no harm but not properly functional.
i hadnt noticed a slowdown. oh well
Test 2 is much smoother and hooray, compcache via cm settings works. I don't know what all the changes you made actually are, but they have made an improvement. Nice work.
Kernel speeds not dropping
I am running the newest test 2 on cm7 test 6 and overnight I left my phone plugged in charging and this morning I see that the kernel never clocks down below 550. When I look at setcpu history, overnight.the cpu never went below 550. Load values are all below 1. I have the min value at 250, ondemand govenor. Will check battery performance today and report back.
All kernels are set to a higher minimum speed while charging, its part of the charging daemons functionality...I don't like it either and plan on removing this "feature" when I get a chance.
That's what happpens normally whenever you have your phone plugged in regardless of kernel.
Thanks for the reply. I thought I had noticed the kernel clock lower while charging before, but I was probably mistaken.
Second test kernel works fine except for wifi, which errors out. Anyone else get this?
Edit: Never mind, just saw your twitter.
Hey prime did you say you were going to be releasing reprimed with that compcache fix today?
reprimed updated for compcache fix, simply re-download and reflash from same link
Sorry, perused this thread but didn't see the answer right away - what's the difference between reprimed and deprimed?