yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] pinguy1982:
Thanks, that did the trick.

For anyone that wants the script here it is:

#!/system/bin/sh
insmod /system/lib/modules/lzo_compress.ko
insmod /system/lib/modules/lzo_decompress.ko
insmod /system/lib/modules/zram.ko
# resetting zram
echo 1 > /sys/block/zram0/reset
# setting zram size to 154.8 MB/18.75% of total ram
echo 154837248 > /sys/block/zram0/disksize
# making zram swapable
mkswap /dev/block/zram0
# starting swap on zram
swapon /dev/block/zram0
# setting swappiness to 100
echo 100 > /proc/sys/vm/swappiness
echo 100 > /data/local/devil/swappiness
sysctl -w vm.swappiness=100

It is better to make smaller containers. This is how it is done in most Linux distros.

I will have a look into it and see whats the best way to implement it into Android.
[Nook HD, HD+ Android Development] PMikeP:
Synergy!
[Nook HD, HD+ Android Development] xflier:
I really love the 10.1 rom. Very stable, and still smooth. I just have a minor issue with the Browser. For sites like windows central.com, some images are not fully shown, they are partially blocked at the center area. Any input is appreciated. Thanks a lot for the great toms.
[Nook HD, HD+ Android Development] Monfro:
You are right: CM10.1 uses less ram than CM10.2, but it is still smooth.

I have less launcher redraw and it can keep apps open in background more often than CM10.2

Really a great work!

May I suggest also trying to build CM10 with yellow kernel?

Android 4.1 was faster than 4.2, and also needing less resources.
[Nook HD, HD+ Android Development] FirePsych:
10.1 is very smooth so far, but getting lots of redraws on browsers. Stock, Firefox and Dolphin.

Any of ideas?

More details: dirty flashed over 10.2. FDR via TWRP. Booted. Set up what I wanted. Reboot recovery. Flash 4.2.2 GAPPS. Wiped dalvik and cache. Reboot. Use tablet
[Nook HD, HD+ Android Development] FirePsych:
If you don't mess with gapps, what do you do for apps?
[Nook HD, HD+ Android Development] Jon Lee:
Likely the way that site is coded (same behavior in 10.2 BTW). Obviously their QC testing only included Internet Explorer compliance.
[Nook HD, HD+ Android Development] Jon Lee:
Anything I need from Google Play store I can have sent to my phone and pulled from there.

I keep a very minimal setup.
[Nook HD, HD+ Android Development] Jon Lee:
More than likely a 'factory reset' is required, which also wipes data.

(Something about titanium backup... or whateva).

Database issues between the two.
[Nook HD, HD+ Android Development] xflier:
Thanks a lot!
[Nook HD, HD+ Android Development] Jon Lee:
Here's a version of yellow, that has been updated to 3.0.72, to try.

ROM: http://www.mediafire.com/download/pyiep0h88b6wm2x/cm-10.2-20150603-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/grz1j5vh1xrva9j/cm-10.2-20150603-UNOFFICIAL-ovation.zip.md5sum

I don't know if I can really tell a difference (better or worse?). This version or the previous?

Kernel source: http://www.mediafire.com/download/vw819y087waoxfy/kernel-20150603.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
Installed it. Chrome crashed within minutes! Will keep testing & let you know.
[Nook HD, HD+ Android Development] PMikeP:
I went back to the old kernel. Chrome kept crashing/freezing/locking up my tablet on 3.0.72. My WAG is something to do w/ zRAM.

(I initially restored only /system & /data from nandroid, but found you have to restore /boot too.)
[Nook HD, HD+ Android Development] Jon Lee:
I probably should have said it, I do believe this last version requires a clean install to work properly.

(Factory reset).

I tried dirty flashing and ended up with 'black flashing' like I imagine firepsyche was describing with a dirty install of 10.1.

A factory reset cured that for me. I haven't had any major issues with it for a few days now. I held on to it for a couple of days, trying to discern any difference. I didn't really do it for 10.2, though. This is just my temporary test bed, ATM, as I'm already familiar with it. Needed the ipv6 sys path changes to move on to something different.

:D
[Nook HD, HD+ Android Development] PMikeP:
Okay, thanks. Perhaps it was more a video freeze then from dirty flash.

Too much work for me to do a Factory Reset for now. I'll wait if others report a compelling reason to update.
[Nook HD, HD+ Android Development] Jon Lee:
TBH, I don't think there is. The 3.0.31 version is probably as good as it's ever going to get. FWIW.

Although... I can't say 3.0.72 is any worse... or better.
[Nook HD, HD+ Android Development] PMikeP:
No complaints here w/ .31.

I googled and found that others who built .72 into the 10.2 ROM were getting big jumps in AnTuTu. Seemed too good to be true.

You could check your score to see if it jumped by a thousand, if you haven't already.
[Nook HD, HD+ Android Development] PMikeP:
Clock hung. Is that the last bug?
[Nook HD, HD+ Android Development] Jon Lee:
No. I have no idea what would cause that. The bug I was referring to was something about timedeventqueue out of awesome player... which I have not seen out of the .72 version, BTW. Also, I believe the .72 version made some ti rtc changes...

The .72 version has actually been very stable for me. About the benchmarks. Benchmarks on this kernel are all over the place and depend on planetary alignment more than anything. That said, I believe about a 100 point deduction (but may make up for it in other areas that can't be measured with benchmarks (like... touchscreen and networking).
[Nook HD, HD+ Android Development] PMikeP:
Okay, I did a clean install of the 3.0.72 ROM. (Takes me 2 hours.) Chrome is still a problem. Seems to have something to do with timing and the keyboard. So far, everything else is working okay. ROM seems even more responsive, if that's possible. Only Chrome causes hangs.

Update: Cleared davlik again to force the cache to update; updated Chrome to latest: reinstalled adaway. Chrome is seems okay again.
[Nook HD, HD+ Android Development] PMikeP:
Although Chrome had gotten better after my "tweaks" above, it still froze sometimes. So I've gone back to the previous kernel. I'll see if the problem follows Chrome or the kernel.
[Nook HD, HD+ Android Development] Jon Lee:
I was waiting for the trim questions. I'll take a look at it. Just looking at what I have for core.c and the Samsung patch, it wouldn't apply without difficulty.

That said, I don't have issue with running trim manually.

root@android:/ # su
root@android:/ # cd /sys/class/block/mmcblk0/device
root@android:/sys/class/block/mmcblk0/device # cat name
MBG4GA
root@android:/sys/class/block/mmcblk0/device # cat manfid
0x000015
root@android:/sys/class/block/mmcblk0/device # cut -b 19,20 cid
06
root@android:/sys/class/block/mmcblk0/device # cat date
10/2012
root@android:/sys/class/block/mmcblk0/device # fstrim -v /data
/data: 3583389696 bytes was trimmed
root@android:/sys/class/block/mmcblk0/device # fstrim -v /cache
/cache: 431607808 bytes was trimmed
root@android:/sys/class/block/mmcblk0/device #

If you have a device with the affected chip, you might want to steer clear from this for now.
[Nook HD, HD+ Android Development] swaaye:
I think I have a safe emmc chip but I figured it was something to bring up seeing how you are making such improvements to 10.1.3.

By the way your latest v6 kernel seems solid. Previous releases were rebooting occasionally on my HD+. This one has not.
[Nook HD, HD+ Android Development] Jon Lee:
Took a look at trim. I basically have the same mmc/core and trim_quirks code as the CM11 kernel. There's a few differences but I believe trim should operate the same between the two.

I did pull a few Power Management fixes from the CM11 kernel. Hopefully this will fix any sleep issues.

Also added two governors and changed the default governor and i/o scheduler as an attempt to improve battery life.

Here's kernel source:

http://www.mediafire.com/download/wxf4hpbotpv01v4/android_kernel_bn_omap-cm-10.1_v5.tar.gz

and flashable kernel update:

http://www.mediafire.com/download/6l6y8fn7w6zfa17/ovation-kernel-cm10.1.3_v7.zip

Should be getting real close to a finished product here.
[Nook HD, HD+ Android Development] swaaye:
v7 seems stable so far. I have not experienced any sleep issues either.

I am running with your defaults of hotplug and SIO as well.
[Nook HD, HD+ Android Development] Jon Lee:
Here's another one to try.

http://www.mediafire.com/download/eby8epybrutvhy6/ovation-kernel-cm10.1.3_v8.zip

1) Added two more governors. Would love some input on these, because I'll probably drop some and/or add a few more. Just experimenting. Hotplug could probably be tuned better. Abyssplug seems to be more aggressive (warmer?).

2) Memory manager (mm) changes... much improved I/O benchmark score.

Edit: Here's the source for this in case anyone wants to add it to their own project:

http://www.mediafire.com/download/ejj0lovbtd5co1q/android_kernel_bn_omap-cm-10.1_v6.tar.gz

Speaking of, I don't own a hummingbird device, so I can't really do any development for it, but if someone wanted to, they would do well to take a look at the overclock and voltage settings used in the AGNI kernel from the link given earlier in this thread....
[Nook HD, HD+ Android Development] swaaye:
It seems solid.

Regarding governors... I can't really tell a performance difference between them, but the governors that disable the second CPU when idle sound practical. Ondemandq only disables the second core when the screen is off, I suppose because someone thinks it improves performance if the CPUs are always awake when you're using the device.
[Nook HD, HD+ Android Development] swaaye:
I just had some strange things occur.

-browser screen corrupted and only a small square in the center was still working. I had to force close it.

-a few mins later the tablet locked up while browsing and I had to power it off by holding the power button.

-upon booting up, the cyanogenmod setup wizard ran as if this was a fresh install. Some app settings were lost. So it seems I suffered some data loss. I've never seen this before..

Maybe it's related to abyssplug. I will try a different governor.
[Nook HD, HD+ Android Development] swaaye:
Nook rebooted on Hotplug this time. Maybe the instability is caused by the memory manager changes? I've reverted to the v7 kernel.
[Nook HD, HD+ Android Development] swaaye:
Another crazy reply to myself!

Kernel v7 rebooted in the browser today. Hotplug governor and SIO scheduler. Trying Savagezen governor to see if hotplugging is unstable.
[Nook HD, HD+ Android Development] Jon Lee:
What I think is that the M3 ducati cores are clocked too aggressively for some devices. The reason I say that is 416 was unstable for me and so was 410. 405 was obviously the cutting edge for stability for me. I haven't had a single reboot or any other issue since OC6. I also had a two week uptime on OC7 before I rebooted manually. I'm still running v8 without problems. That said, I do know that between v7 and v8 a wipe of cache/dalvik cache (and really, preferably, even /data.. although I didn't) would be more important than normal.

I believe with my next one, I will return the M3 core clocks back down to stock 384 just to prove it. This will save on battery and heat anyway. (Plus I want to try out the wheatly governor).

Oh! Also you might want to go into settings/Developer options and check 'Force GPU rendering'. This makes a huge difference on 2D rendering.

Edit: Well I couldn't bring myself to return them back to stock. But here's one where the M3 cores are clocked at 396. Should be an improvement.

http://www.mediafire.com/download/gynni0g3sgsgfj8/ovation-kernel-cm10.1.3_v9.zip
[Nook HD, HD+ Android Development] swaaye:
I hadn't wiped the Dalvik cache between v6-v8 kernels so I did that and have been running with v8 again. Savagedzen gov and SIO sched. If it reboots again I will install the v9 kernel...
[Nook HD, HD+ Android Development] swaaye:
I just discovered that the VPN tunnel module isn't built with your kernel? I thought that I had been using VPN with your kernel but I can't connect with v6-v9. Catlog says the tun device isn't available.
[Nook HD, HD+ Android Development] Jon Lee:
Details were hidden in Post#10 here:

http://xdaforums.com/showthread.php?t=2627202

But anyway, here's the link to the extra modules pack:

http://mediafire.com/download/670pzf1r2lu1dy8/extra_modules_ovation_cm10.1.3.tar.gz

Most VPN clients can be setup to insmod the tun.ko automatically for you, so that shouldn't be a problem.

You will have to adb push it or transfer with a sdcard and set permissions. Sorry for the inconvenience, but it was mainly for security reasons that it wasn't built directly into the kernel.
[Nook HD, HD+ Android Development] swaaye:
There isn't a tun.ko included in that archive. I tried tunnel4.ko but that didn't work.

Also, I did have another reboot. I was using Abyssplug on v9 kernel with a fresh install / wipe and was installing lots of apps at the time. I'm back to thinking it is related to hotplugging somehow. I've switched to Wheatley to test.
[Nook HD, HD+ Android Development] Jon Lee:
I'm going to be out running errands today so I won't be around to be much help.

I believe tun.ko may be built into the kernel but you will need to insmod some other kernel helper modules.

To get an idea of what's missing, etc, the kernel configuration can be found in /proc/config.gz. (I'm thinking ipip.ko, tunnel4.ko and some of the xfrm modules will need to be insmod). I'm willing to work with you on this or perhaps build the required modules into the next kernel (everything you need should be in the module pack though). The stock kernel had everything including the kitchen sink built into networking. I prefer a minimalistic approach generally.

Also if/when anyone experiences a reboot, it will help greatly for debugging purposes to pastebin the contents of /proc/last_kmsg to share here. This will give me something to work with.

I have some idea of some the things I will be working on next.

I successfully ported i2c from linux-3.8, should see this in the next release. Testing ATM, but I'm hoping it improves the behavior of the touchscreen driver. Seems to be doing good. There's a gic_timer_interrupt omap patch I would like to incorporate. I also plan on working on the ion memory manager and the tiler as time permits.
[Nook HD, HD+ Android Development] swaaye:
I looked at the config.gz output as you suggested but I don't know how to figure out dependencies from it. I suppose the ideal thing is just to build tunnel support into the kernel anyway. I'm not sure how to automate insmod commands on Android. rc.local isn't active for example...

And next time I get a reboot I will post logs. I am back to your defaults of abyssplug and row now to test.

--edit

OK it rebooted in the browser. I don't see last_kmsg but got a huge dmesg log and I think it shows the reboot near the end.
[Nook HD, HD+ Android Development] Jon Lee:
Ok, that's not a kernel reboot/issue per-se. It is the android kernel Out Of Memory (oom) killer doing what it's supposed to do. When I did the two week uptime test it happened to me two or three times. It does appear that you lose half the apps in the app drawer (because trebuchet is killed and restarted). If you go home/recent apps/clear recent apps/home/app drawer, you'll get them back and everything will be good for another few days (I say a few days, it probably happens less to me because I have less apps installed).

I do have a potential fix for it... largely untested.

http://www.mediafire.com/download/bmcgi8hliacn5ak/ovation-kernel-cm10.1.3_v10.zip

root@android:/ # echo 60000000 > /sys/block/zram0/disksize
root@android:/ # mkswap /dev/block/zram0
Setting up swapspace version 1, size = 59998208 bytes
root@android:/ # swapon /dev/block/zram0
root@android:/ # cat /proc/meminfo

Anyway the above kernel was configured for VPN. The ksm, zram/zcache options also reduce benchmarks slightly. No major changes to kernel source.

Edit:

I guess you will also need:

echo 1 > /sys/kernel/mm/ksm/run

I may have to add a kernel boot parameter to enable cleancache. I'll mess with it later.

You can extract the 60ZRM file to /system/etc/init.d and give it rwxr-xr-x permissions and zram should be configured upon reboot.

test with a cat /proc/meminfo, you should see some swap mem.
[Nook HD, HD+ Android Development] :
Great kernel!

Just wanted to say thanks for this exceptional kernel. CM10.1 is fast and stable alone, with this OC'd kernel combined, I would say this is the best setup to date for the Nook HD+
[Nook HD, HD+ Android Development] swaaye:
I think you must be seeing another problem because when I say it reboots I mean it goes from, for example, the browser to the boot animation. :)

I haven't seen the Trebuchet problem. I am using Holo Launcher HD. Fast, simple and has gesture support.

Thanks much for integrating VPN TUN support. It is working well.
[Nook HD, HD+ Android Development] Jon Lee:
I'm unhappy with two things about v10.

1) touchscreen

2) runs hot

To address this I reverted the i2c/touchscreen fixes to the way they were before (actually used v6 source, lost wheatley governor, GPU back up to 405). I think maybe smartreflex v3 doesn't adjust voltages properly, so I reverted back to v1.5. I'm not sure if VPN options were making my device work harder and run hotter, so I removed those. (It would be best to module-rize these anyway.. maybe one day)

http://www.mediafire.com/download/d6438zdfj0hpn7e/ovation-kernel-cm10.1.3_v11.zip

I have ksm working. You will have to enable it manually by echoing 1 to run (the init script won't do it.. permissions?)

root@android:/ # cd /sys/kernel/mm/ksm
root@android:/sys/kernel/mm/ksm # ls
full_scans
pages_shared
pages_sharing
pages_to_scan
pages_unshared
pages_volatile
run
sleep_millisecs
root@android:/sys/kernel/mm/ksm # cat full_scans
23
root@android:/sys/kernel/mm/ksm # cat pages_shared
633
root@android:/sys/kernel/mm/ksm # cat pages_sharing
6248
root@android:/sys/kernel/mm/ksm # cat pages_to_scan
256
root@android:/sys/kernel/mm/ksm # cat pages_unshared
19755
root@android:/sys/kernel/mm/ksm # cat pages_volatile
31404

I have no real way to test long term memory performance, but I'm hoping this will work.

root@android:/sys/kernel/mm/ksm # cat /proc/meminfo
MemTotal: 782100 kB
MemFree: 9064 kB
Buffers: 6784 kB
Cached: 456204 kB
SwapCached: 68 kB
Active: 131628 kB
Inactive: 448172 kB
Active(anon): 40508 kB
Inactive(anon): 77016 kB
Active(file): 91120 kB
Inactive(file): 371156 kB
Unevictable: 396 kB
Mlocked: 0 kB
HighTotal: 18048 kB
HighFree: 148 kB
LowTotal: 764052 kB
LowFree: 8916 kB
SwapTotal: 61436 kB
SwapFree: 61224 kB
Dirty: 1260 kB
Writeback: 0 kB
AnonPages: 117180 kB
Mapped: 172120 kB
Shmem: 280 kB
Slab: 17304 kB
SReclaimable: 6900 kB
SUnreclaim: 10404 kB
KernelStack: 3448 kB
PageTables: 5536 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 452484 kB
Committed_AS: 2916996 kB
VmallocTotal: 122880 kB
VmallocUsed: 70168 kB
VmallocChunk: 17348 kB
[Nook HD, HD+ Android Development] dk1keith:
which post has the install instructions. It isn't a simple flash from recovery is it? can't seem to find the step by step install instruction.

thanks
[Nook HD, HD+ Android Development] FirePsych:
I think the kernel is part of the ROM, so you just flash that.
[Nook HD, HD+ Android Development] dk1keith:
Right. But where is the latest rom with the kernel? and do you simply do a factory reset data and cache in recovery? I am using the latest CM recovery not TWRP.

thanks

---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------

Can I flash this one in CM recovery or do I have to use TWRP. Been wanting to try this one but not sure which to use. This is the rom and kernel correct.

Thanks
[Nook HD, HD+ Android Development] FirePsych:
I think most of us are using TWRP.

You will want to do a full wipe if you're coming from a different rom.
[Nook HD, HD+ Android Development] FirePsych:
Hello,

Still running the latest 10.1.3 ROM.

Generally runs great, having a few problems though;

I'm being prompted to update Maps and YouTube but I get an error that says I need a new / updated SDK. No idea where to find that.

Also, Calendar isn't syncing. I've checked permissions and security settings and tries Google Calendar, but no luck. That usually fixes that problem.

I'm thinking both issues are related to my GAPPS package, but I'm having a heck of a time finding 4.2.2 GAPPS other than a full package and I really don't want a full package.

Thoughts?

PROBLEM SOLVED

I used 4.2.2 GAPPS from here http://www.teamandroid.com/gapps/

That solved my update problem.

Turns out, and I don't know why, Calendar sync on my phone was turned off. That fixed my second problem.

All good now.
[Nook HD, HD+ Android Development] pinguy1982:
Gapps are built into this tweaked version of 10.1.3 Yellow ROM.

http://xdaforums.com/nook-hd/development/nook-hd-tweaked-yellow-kernel-4-3-1-rom-t3110130
[Nook HD, HD+ Android Development] xflier:
I am using YourZGappsXS, which works for me. You can search for it in the forum.
[Nook HD, HD+ Android Development] FirePsych:
Is that your ROM or Jon Lee's ROM?
[Nook HD, HD+ Android Development] pinguy1982:
It's Jon Lee's ROM. All I did was OptiPNG, Zipped the apks and patched services.jar with "Ultimate Jar Power Tools" to improve multitasking. Also stripped out the libs in the apks and added them to system/libs.

Added my little tweaks to it. Replaced the launcher with the Google Now launcher. I added the Lollipop keyboard and the Sony Walkman music player with the UPNP/DLNA Media Server. Also added a custom sound engine that will greatly improve the sound quality.

MX Player is included and has working AC3 sound using a custom Arm v7-Neon codec.

There is a load of extra fonts added and I built in a modified version of flash that has Hulu support..

KSM and zRAM are enabled by default with custom values.

zRAM size is set to 154.8 MB/18.75% of total RAM and KSM pages_to_scan to 1536 and sleep_millisecs to 6000 reducing CPU cycles and saving battery power.
[Nook HD, HD+ Android Development] PMikeP:
I read about your similar Carbon ROM in another thread of yours. There was something abt having to run an Optimzer. (Run SuperJars or the Power Tool or something.) Do we have to do that with this one? Or is it ready to go out of the box?
[Nook HD, HD+ Android Development] pinguy1982:
Ready to go out of the BOX. You don't have to do anything. OptiPNG etc. is the list of things I did to the ROM.
[Nook HD, HD+ Android Development] PMikeP:
Thanks for the quick reply. Am downloading now to try. Dumb question: Jon's builds are abt 170Mb. Your's is 340. I know you said you've got GAPPs on yours, but a stripped down GAPPs version in this thread is only 18Mb w/ Lollipop keyboard. I polietly ask, why the 2x difference? (Perhaps you've already answered by way of your list of mods. If so, please disregard. I might be making a noob mistake of equating ROM download size with running ROM size in memory.)
[Nook HD, HD+ Android Development] pinguy1982:
This is mainly due to the added fonts (I added a lot) and the Sony framework files to get the Walkman and UPNP/DLNA Media Server apps working.

Also the gapps are up-to-date, so they are larger. For an example:

GmsCore = 20MB

GoogleTTS = 10.7 MB

QuickSearchBox = 39.8 MB

Google Now Launcher = 11.9 MB

LatinIME (keyboard) = 19.0 MB

EDIT#

As for memory usage. This version will use less then the default "Yellow kernel" ROM because I have OptiPNGed the apks and framework-res.apk and added my optimizing tricks to it.

I am willing to bet it benchmarks higher then the default "Yellow kernel" 10.1.3 ROM even with the added Gapps.

Jon Lee has done a fantastic job with this ROM. Without his work I wouldn't be able work from it. OptiPNGing takes hours to do but does lower the memory foot print. Because it takes hours to do is why many devs don't do it.

All I have done is taken the fantastic work Jon Lee has done and added my optimizing tricks to it. All the hard work was done by Jon Lee. Optimizing a working ROM is easy if you have the time and know how to do it.

DOWNLOAD​