This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
My droid completely choked on your latest test kernel, with default speeds and vsels. Became so slow it was basically unusable. I tried several different governors with no change. Flashing back to test #19 fixed things.
My droid completely choked on your latest test kernel, with default speeds and vsels. Became so slow it was basically unusable. I tried several different governors with no change. Flashing back to test #19 fixed things.
Just a update to BFS and a MMC tweak, I haven't had a issue but the next update will have deadline along with CFQ for IO schedulers along with scripts to change them. Perhaps changing the IO scheduler will have an effect on the CPU scheduler performance on your device.
On my device CFQ rules the roost, deadline causes some noticeable lag.
Just a update to BFS and a MMC tweak, I haven't had a issue but the next update will have deadline along with CFQ for IO schedulers along with scripts to change them. Perhaps changing the IO scheduler will have an effect on the CPU scheduler performance on your device.
On my device CFQ rules the roost, deadline causes some noticeable lag.
I'd be interested in knowing, too, as I just rooted/cm'd/oc'd an old G1.
Except for the original battery not lasting a day the thing seems happy on CM6. It's only on wifi for now.
Likely a combination of the vsels and BFS, it is more CPU intensive as it gives processes that need ticks the most attention. Could you try bumping the vsels up about 5 on each slot?