Monday, April 2, 2012

Test Feedback Needed: Experimental Kernel saves 7MB RAM

Update 4/7/2012: Due to code review we have decided to go with a more conservative 1.5MB RAM savings for the upcoming CM9 beta2.  We will further investigate for later releases if it is 100% safe to further reduce the RAM usage by reverting triple buffering to the video decoder double buffering behavior used in gingerbread.

noobnl found a simple hack that reduces the kernel framebuffer memory, giving 7MB to userspace on Epic 4G.  We need your help to test this kernel and report any changes in behavior that you see.

There *has* to be a drawback to this, perhaps in a very rare corner case.  If you find a failure case, please verify it by doing the reproducer on the previous kernel, then again on this kernel.

Download
This experimental kernel works with both CM9 beta1 and the experimental CM9 beta1-test-4.0.4 and contains the following changes since CM9 beta1's kernel.
  • mdnie enabled.
  • tun enabled for VPN users.
  • Kernel framebuffer memory reduced by 7MB.
Please report any changes that you see here or in this Google+ thread.  Thanks!

17 comments:

  1. Everything looking good
    Seem to get better signal on wifi and data. Even seem to get better battery life! Overall good work

    ReplyDelete
  2. I could see the battery life gain being possible with less ram, but framebuffer changes affecting signal?

    ReplyDelete
    Replies
    1. No. Battery life has nothing to do with less RAM. This was a myth created early on due to people repeating bad information.

      Delete
    2. This comment has been removed by the author.

      Delete
    3. Warren, why would you explicitly put aside time to post a comment like this?

      Does a thrashing desktop system not [increasingly and eventually likely-cyclically] spend more resources shuttling data back and forth to the HDD?

      Does my Android mobile not repeatedly kill and relaunch Poweramp (in the bg), launching 30+ second SD card rescan & resyncs each time, when it's dancing below [and above] its memory limits.

      Ray offered only the mildest squeak of acceptance that battery life improvement might be a "possibility".

      If you thought memory was generally uncorrelated, but recognized there could be instances where it could affect battery, I would expect you to simply ignore the comment at the very most. Is there something you know that I don't that warrants explicitly squashing an already mild statement and authoritatively stating that the two have "nothing" to with each other? As a young but seemingly exceedingly experienced developer, your word carries a lot of strength around here.

      Delete
    4. I notice he explicitly did not take the time to answer you... :p now THAT carries a lot of strength. XD

      Delete
  3. flashed on test build and everything works great. only thing i noticed was after flashing it automaticly rebooted instead of staying in cwm. it flashed ok first try just wasnt expecting reboot. going on 3 hours now and very smooth and only 10 percent drop with medium use, gps and wifi on, and couple reboots(intenional) while setting up.

    ReplyDelete
    Replies
    1. Flashed the temporary kernel? That doesn't install, it reboots into the temporary kernel. If you reboot it goes back to your previous kernel. That is why it is temporary.

      Delete
    2. yes the temp kernel. didnt even think about that when i rebooted. checked in settings and did revert back. now that i have test build setup the way i want i reflashed and confirmed running experimental kernel. still no problems but i will charge up and test some more without rebooting. report back later.

      Delete
    3. after testing more only had one problem. camera would open then force close after a few seconds. rebooted and camera was functioning properly again. reflashed experimental kernel again and this time camera working no problems.dont think this is related to kernel but thought i would mention anyways. all other apps and functions that i use work with no problems.

      Delete
  4. Hello Warren,

    I've flashed the temp kernel; for me it seems to run slower than the kernel included with b1. As I am testing I am documenting in this google spreadsheet document, you can look at it here:
    https://docs.google.com/spreadsheet/ccc?key=0AsDFupwiCOXydEF0OU5mZDY1T0RKOXdMcTBKbXE1VEE

    ReplyDelete
  5. I am running the temp kernel and I do find the response a lot faster then the regular kernel on beta 1. I do not notice any color difference tho lol, the color scheme looks the same to me with or with out mdnie enabled.

    I see apps like Google plus, xda premium and the stock browser open much quicker then before.

    ReplyDelete
  6. I agree i just flashed it and noticed right away that it seems noticeably quicker let you know if i come across anything

    ReplyDelete
  7. Runs good but the only thing is the quality got very horrible and worst thats the only thing i found with it

    ReplyDelete
  8. Everything is working good with the test kernal running with the 4.04 test build. One thing i've noticed is sometimes the on screen keyboard will come up when its not supposed to. Happened last in the Play store while reading reviews of an app. Keep up the good work, Thanks

    ReplyDelete
  9. Tonight I went back to 4.04 without this kernal.I was getting random battery reading and occasional freezing of the lock screen. Hope this helps. Thanks again

    ReplyDelete
  10. Responding to your 4/7 update, I have been running this since it came out and have experienced NO issues. Everything is quick, everything is stable, everything is great. 4.0.4 test build(my notification toggles do not work. I'm attributing that to the ROM not the kernel). I'm going to miss this 5.5MB of RAM.

    ReplyDelete