[GPL]2.6.29.6 CFS Kernel V9 12/10/10

[bftb0]

Update on my test runs since this prior report.

Basically, I ran Tazz 2.0 + overflash of CFS2 - still using setCPU (XDA version v2.0.2) with similar profiles as before, but all of them set to the interactive governor, and none of them with minimum clock rates less than 245 Mhz. I was not using Autokiller, so the process trimmer should be defaulting to whatever the Tazz 2.0 ROM sets them to (I need to look those #s up).

I developed similar troubles as before around 9 hours after the boot-up. The phone comes out of a Screen Off condition, and appears to be normal - but over the course of 3-5 minutes, the UI becomes progressively slower to the point of unresponsiveness.

I'm going to go back to square one, and repeat the same trial (clean install of Tazz 2.0 + CM2) - but this time with no SetCPU (and no AutoKiller, as before). If it stays healthy for 24 hours, that will seem to implicate something about SetCPU v2.0.2 that doesn't play nice with the CFS2 kernel when the interactive governor is used.

bftb0


PS - are the "Time in state" numbers available in /proc somewhere (if I want to look at them without having SetCPU installed)?

 

[Hungry Man]

Why not just stick with demand? >_> I am and it's working just as well as it ever has.

 

[bftb0]

Why not just stick with demand? >_> I am and it's working just as well as it ever has.

Perhaps I was completely mistaken about this, but I though that the only governor which was affected by the CFS patches was the interactive governor? If that is the case, the non-CFS kernel would have the same behavior when "ondemand" is in effect as the CFS kernel - and that would beggar the question "why CFS at all?".

As I said, I might be misinformed; if so, give it to me good fer being wet behind the ears!

bftb0

 

[Hungry Man]

Well CFS is the scheduler, so I would think the CFS and the governor are too very seperate things that happen to work nicely together (though apparently not in this case.)

 

[Hungry Man]

Conap, do you have the chart for voltages/ speeds?

 

[bftb0]

Android Low Memory Killer disabled in CFS2 ... and CFS3

Awww f**k.

With the CFS2 kernel running, from a root shell (via adb):

sh-3.2# cat /proc/config.gz | gunzip -c | grep -i low_mem
# CONFIG_ANDROID_LOW_MEMORY_KILLER is not set

sh-3.2# sh-3.2# cat /sys/module/lowmemorykiller/parameters/minfree
cat: can't open '/sys/module/lowmemorykiller/parameters/minfree': No such file or directory

My recent troubles with CFS2 had nothing to do with setCPU - purely memory exhaustion. I sort of wondered why nothing would stick to the wall when AutoKiller threw some page values at it (I wrote it off as a Autokiller bug)

Any reason why the ANDROID low_memory killer was turned off for this kernel build?

I can't figure out why no-one else has experienced slow-downs or soft restarts - is everybody rebooting their phones every couple of hours?

Gonna roll back my Eris to a different ROM and roll into bed.

G'nite.


bftb0


PS CFS3 also seems to be compiled the same way.

 

[Hungry Man]

I'm using BFS V4... no issues, I went quite a while on V3 as well. Used CFS for a bit but I didn't notice it being any smoother/ more stable so I just went back to BFS, which is the same thing but with the modified scheduler.

I used setcpu and I do not ever use autotask killer, which has never worked well for me between my two eris's that I've had.

 

[bftb0]

I'm using BFS V4... no issues, I went quite a while on V3 as well. Used CFS for a bit but I didn't notice it being any smoother/ more stable so I just went back to BFS, which is the same thing but with the modified scheduler.

I used setcpu and I do not ever use autotask killer, which has never worked well for me between my two eris's that I've had.

Well, this is a thread about CFS kernels, I think.

I'll assume that you mean "Autokiller" rather than ATK, but that is beside the point anyway: the Android low_memory killer is built into every shipping Android kernel, and I suppose it has compiled in default values - but they are explicitly set in the boot ramdisk (in init.rc or init.desirec.rc or via default.prop). So, it is active in your kernel - the one you are using right now - whether or not you are using an app to tweak it.

When you leave it out completely, the free memory can run to 0 MB, all processes get blocked or start running at a crawl, and the Android process monitor running on top of the kernel just starts starts killing Dalvik VMs randomly as various watchdogs expire. Eventually, every dalvik process dies and you get a "restart" of the whole Android VM process management system. The kernel never panics - it just comes back to life when it gets unstuffed.

If you had run your phone with either of these kernels for more than 5 or 6 hours, you would certainly have experienced this problem. (Actually, all you need to do is start every app on your phone one at a time, and just hit the back button - if you want to see it happen more quickly)

bftb0

 

[Hungry Man]

Yeah I meant autokiller. And yes I know android comes with it's own stock settings for it =p

Like I said, I'm using it and there are no problems. It's possibly because I have Advanced Task Killer and once in a while I kill tasks... but either way I've been playing Zenonia/ GBA games and I have 80MB free on my ROM. I don't know what to tell you =p

 

[Hungry Man]

Perhaps it's just been soft rebooting and I haven't noticed =p haven't been paying attention lately.

Anyway, I suppose it has to be added in then?

 

[bftb0]

Yeah I meant autokiller. And yes I know android comes with it's own stock settings for it =p

Like I said, I'm using it and there are no problems. It's possibly because I have Advanced Task Killer and once in a while I kill tasks... but either way I've been playing Zenonia/ GBA games and I have 80MB free on my ROM. I don't know what to tell you =p

I think you previously said you abandoned CFS trials and are now using BFS. The android low memory autokiller seems to be (correctly) configured into the kernels in Conap/Decad3nce's BFS kernels (well, in BFS330 anyway - that's the only one I flashed to check).


bftb0

 

[MJL99]

Dang. I think im having problems with this now too. I noticed this was helping with gps for a few and my gps was flaking out once in a while so I gave it a shot. It worked for fixing my gps. Then I rebooted in the morning. Everything went fine until it finished restarting. Once it loaded, before I even unlocked the screen, it rebooted itself. At that point it wouldnt go past the skateboard screen. Pulled battery and tried again, let it run for maybe 15 mins and still didnt get past it.

I pulled battery and rebooted to recovery. Figured I had to wipe things now so I tried just dalvik and got stuck at skateboards again. Next I wipe data and dalvik and it booted up. Went thru the setup process and once it got to sync my data the setup FCed and left me on a black screen with the notification bar only. One thing I noticed that was different tho wasafter letting it sit, once I woke the phone, I saw the screen said sprint which I never had before.

Finally after waiting for a while I decided it wasnt going to work and restored my working copy before flashing the cfs kernel. Now its working but im back to square one. Just wondering if I did something wrong when flashing this new kernel. I didnt wipe dalvik or anything, just booted to recovery and flashed it and it booted just fine. Running nonsensikal 5.3 blue.

 

[Decad3nce]

I think you previously said you abandoned CFS trials and are now using BFS. The android low memory autokiller seems to be (correctly) configured into the kernels in Conap/Decad3nce's BFS kernels (well, in BFS330 anyway - that's the only one I flashed to check).


bftb0

Must've been overlooked. I'll get conap on it. Sorry about that.

 

[swaggerwocky]

Running the CFS v3 with KaosFroyo V32 and setCPU @ interactive/768-245 and Autokiller set to Strict. It appears as though the CFS has broken Autokiller since 0 is displayed for all the memory limit fields. I'm around 39mb free memory at the moment. Other than that, everything is running smoothly and quick as ever.

 

[hallstevenson]

I've noticed low memory numbers also, especially when using a "heavy" app like Maps or Navigation. My phone got really, really sluggish and when I finally got ATK launched, it showed 14mb available memory. I've never seen it that low, even with the stock HTC kernel !

 

[macdroid14]

I've noticed low memory numbers also, especially when using a "heavy" app like Maps or Navigation. My phone got really, really sluggish and when I finally got ATK launched, it showed 14mb available memory. I've never seen it that low, even with the stock HTC kernel !

Me too. It's great that Navigation works now, but using memory intensive apps causes my Eris to lag. It took about 25 seconds for the "Google Maps Navigation Beta" logo to actually get to the app.

 

[Decad3nce]

K. If you guys can wait til conap comes on, it's really an easy fix; just something that was overlooked after I told him to do a make mrproper.

 

[eklipze]

K. If you guys can wait til conap comes on, it's really an easy fix; just something that was overlooked after I told him to do a make mrproper.

Thanks for jumping on this! I really love this cfs kernels buttery feel!

Again you guys rock my little phones world!

Sent from my FroyoEris using XDA App

 

[wilshyre]

I have 2 eris phones as my old lady lost hers a while back and insurance replaced it, and recently we found it.. so I have actually have 3 if you count hers. Anyway, one is not activated but I've been using it to test CFS and I agree, there is def something wrong with the minfreekiller.. first, autokiller gave me values of 0 all the way down the line. Thought maybe this was a bug so put in numbers for strict, as the default presets weren't working either. Try to set them but they still show 0 all the way down. So applied settings after manually putting them in and the app confirmed applied settings.. but they definitely weren't working. Withoit a manual task killer and killing apps at intervals, it simply goes Mega sluggish. BFS330 does not seem to have this prob. Loving it and BFS.

Sent from my Tazz Froyo 2.0 using XDA App

 

[ahjee]

It certainly doesn't kill any apps/procress. Autokiller and all like it won't work either, sorry to be redundant but other than it not doing that it works well, I'm mostly happy about it solving my gPs and now it gives me a reason to use the formly useless ATK and others a like, its helped using it actually once I tweaked the settings.


Sent from my FroyoEris using XDA App