yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] webdroidmt:
You did it right. I did a total clean install of the Liquid rom with the newly "implanted" CM11 kernel. I wouldn't mess around with the partitions, dangerous territory. :laugh:

There's possibly some "hook" that Yellow is looking for that is not contained in CM11.

After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error. With the ease of making nandroid backups, stuff like this is always worth a try when it's something you want or need. :D I'm thrilled that it works the other way, as I do use "Ok Google" a lot on all my devices and this Liquid rom runs nicely on the Nook.

In addition, with the introduction of Lollipop, Google has revamped GN and it's even better to use than before.

Mike T
[Nook HD, HD+ Android Development] PMikeP:
Good to know I'm not alone then. Oh well, it was a promising experiment.

(Last night I tried experimenting (hacking) to get zRAM to point to a swap file on /cache. Not really a LS thing, but I might write about it later.)
[Nook HD, HD+ Android Development] vimesxda:
I tried installing this today and it ran really nice and smoothly, but it doesnt seem to have the full HD+ screen resolution. Seemed more like 720p than 1080, large fonts and icons, just a lower resolution. Am I missing a setting or is it not working at full resolution?
[Nook HD, HD+ Android Development] Jon Lee:
There's two ways of changing this to your preference. The first is to go into settings/liquidsmooth/interface/custom density

The second is go into settings/liquidsmooth/performance/[open left panel], go down to Build.prop mods/Change LCD density.

The second method is probably better but will require a reboot to activate changes.
[Nook HD, HD+ Android Development] vimesxda:
Cheers for quick response. I did check the density in custom density setting and the slider was up to 320 which was seemingly as high as it went. I didn't check the LCD density though in performance. Are you sure this will have the correct resolution? I just want to be sure because I just went back to cm11 again and I don't want to have to factory reset again if the resolution will be same as before. Thanks for help.
[Nook HD, HD+ Android Development] Jon Lee:
See Post #7, Page #1.

(IE. Try 240)

;)

Btw, if you just want to wait, I'll be posting a new version tonight or tomorrow.
[Nook HD, HD+ Android Development] PMikeP:
Hi Jon. Is there a way you can put in the hook (or whatever is needed) to make your kernel play in CM11, so that we don't get the "com.android.phone has stopped" error?

Your OC kernel is nice and even faster than a simple 1600/1500 ratio speed increase would predict, and, for me, the best of both worlds would be to run CM 11 with your kernel.
[Nook HD, HD+ Android Development] vimesxda:
Thanks for help on DPI. I was under the impression that higher density is better picture quality thought , so I'm confused as to why lowering it appears to make the images sharper? Is it making thr resolution higher but quality lower?

Also I re installed today and titanium backup is telling me the device is not rooted, I've also noticed some apps I had before now say they aren't suitable with this device on Google store.
[Nook HD, HD+ Android Development] Arbelzapf:
It's not that simple. The resolution stays the same, of course. Everything's still rendered in FHD. The DPI setting basically just enables android to tell how big an element will appear on screen.

You see, when you just say "make it 50 pixels wide" you have no idea how large that actually is. There are countless screen sizes with countless resolutions out there. 50 pixels on a 1024* tablet is a lot bigger than on a 1920* phone. That's where DPI come in, because of you know how many DPI the display has, you can actually know how big the element will appear when rendering it. Thus, you can trick android into rendering stuff bigger by increasing that value.

But it's not directly related to picture quality or output resolution.
[Nook HD, HD+ Android Development] vimesxda:
Thanks for explaining, pretty sure I get what you are saying. Just a note on the rom itself, I'm really pleased and impressed with it overall. It lives up to its name, very fast and smooth and very functional. I love that it has viper fx built in as the equaliser too.

Experiencing a big issue at the moment though and that is I cannot get Skype to work properly, which is a pretty vital part of my tablet for me. If I make a call it hangs up instantly, or if someone calls me, it rings once and stops. I had the same issue when I updated to nightly cm11 on very greens .I had to keep reverting back to before update. I really don't want to uninstall this ROM so does anyone have any ideas what's causing this? Could it be g apps related somehow?
[Nook HD, HD+ Android Development] rhyang:
I was wondering when someone might notice this :). Remove /system/lib/hw/camera.ovation.so, reboot and Skype will work.

Long version: this is a camera stub I added to the CM11 device tree a while back so could i view photospheres in Google+. I noticed recently that it now causes Skype to barf. Not sure which app is more brain dead ...
[Nook HD, HD+ Android Development] vimesxda:
Ah thanks a lot! Been looking around for various solutions and I thought it was going to be one of those problems that's never fixed. So glad there's a solution and such a simple one at that. ROM is still running very nicely. I've noticed its running quite hot though and battery is draining a little faster than my cm 11 I think. I am running viperfx at super high audio so I don't know if that could be causing a lot of CPU heat. It didn't seem to before but I was using an older version of app then.
[Nook HD, HD+ Android Development] vimesxda:
Damn actually this doesn't seem to be working. Just tried a call and same problem. Deleted and rebooted file like said. I guess maybe an older version of Skype might work but I'm not really sure where is considered a trustworthy place to download old apks.
[Nook HD, HD+ Android Development] rhyang:
Well, that's annoying. Try getting a log (catlog from the play store works for me) and upload it somewhere .. there might be telltale signs of whatever the problem is.

If you get a chance, try the same experiment with CM11 (I just tried this with my slimkat and Skype works.) I submitted a change to CM gerrit to remove the camera stub about an hour ago. If you find that removing the file makes Skype work on CM11, then that kind of points to another problem.
[Nook HD, HD+ Android Development] vimesxda:
Where would I upload that log to? Im happy to if its helpful. I'd like to run that test with cm11 too and will if it will really help out but I actually wanted to fix this problem so I could avoid wiping everything and reinstalling cm. I'll try though if nothing else comes up.
[Nook HD, HD+ Android Development] rhyang:
So, as background try googling "android logcat" -- that should tell you something about what we're looking for. There is also a similar utility for kernel messages called "kmsg". There are various apps to read these logs (I like dmesglog). You can upload the log(s) to anywhere you like as long as it's publicly readable: google drive or pastebin to name a few. It would probably also work to zip it up and attach it to a post here. Show a little resourcefulness :)

As for CM11, it's time to get familar with the backup/restore functionality of whatever recovery you have installed. Back up your current boot, system, and data partitions (nice to be able to do this with a microSD on these devices). Wipe cache and dalvik. Then flash CM11 (or whatver it is you are testing) & reboot. Try it out, kick the tires, experiment. Then to get back to your backup, reboot into recovery again and restore those partitions you backed up. Remember to wipe cache & dalvik again. When you reboot it will be like you never changed anything.

The nice thing about this is that you can back up the state of your tablet as many times as you like: you are only limited by your microSD storage. Cheers and good luck :)
[Nook HD, HD+ Android Development] vimesxda:
Thanks for the explanations and helpful advice. believe it or not I do have some resourcefulness lol, I was mainly asking about where is the appropriate forum or website to post the log as you said about uploading the logs to anywhere and i wasn't quite sure what you meant.

Made a backup of my system like you said from recovery, which worked very smoothly. Downloaded log cat and I recorded whilst making a call on liquid smooth now Ill go do the same on cm11 and update this post with the logs when done.

*update*

Ok just finished making logs and it seems that the latest nightly of cm11 skype is working fine now, so i couldn't get a log of the bug on there. If needed Ill install the version that wasnt working and make a log of that, but here I've uploaded logs of the liquidsmooth skype that isn't working and the cm11 that is. Just used the first free uploader I found. http://www.filedropper.com/skypelogs
[Nook HD, HD+ Android Development] rhyang:
Awesome. Just to be clear, when it worked on cm11, it was after you removed /system/lib/hw/camera.ovation.so, correct ? My commit to cm11 to do this has not yet been merged (verygreen is verybusy :))
[Nook HD, HD+ Android Development] vimesxda:
Hmm I didn't remove camera ovation on very greens cm11 no. I installed one of the older versions linked in the start of the thread and it works in that, which is what I ran the logcat in. But then normally when I update to latest nightly Skype crashes, same as liquidsmooth, this time I updated to latest nightly and it seems to be fixed. I can try making a log on the nightly that was crashing if needs be, I presume its the same error as liquidsmooth though.
[Nook HD, HD+ Android Development] rhyang:
Very interesting. I looked at the logs, and indeed the camera stub-related error is nowhere to be found on LS. That it now works on cm11 implies something in the cm11 framework has changed, fixing the Skype problem. If we can figure out what that is, then we can have photospheres AND Skype !

Thanks for helping investigate this :)

Edit: I ran a quick test with cm11 28-Oct nightly, and Skype definitely does not work with the camera stub present; removing it and rebooting seemed to make Skype work. So we're back at square one. I might try LS later and see for myself ...

Another thing to try is looking at liquudsmooth threads for other devices; wonder if they are having trouble running Skype or if it's just us. BTW I have never seen the rei visa or us bank apps work on ovation, in cm11 or slim. Wells Fargo app works on cm11 but not slim. Have been scratching my head about how to fix for a while ...
[Nook HD, HD+ Android Development] vimesxda:
No problem :). Turns out I was wrong about cm11 like You had happen to you too.. Well its odd because yesterday when I tested it, I rang the test call on skype, and i got through to the voice speaking and then I hung up. I'm pretty sure at one point the voice talked for 10 or 20 seconds but I cant be sure. Thing is I used skype last night and my calls connected but then instantly hung up. I called the test again and it got through and heard a couple of words and it hung up again. Now I'm not sure if i was just hanging up before it had chance to on its own yesterday or not, but its definitely not working so Ive had to go back to early cm11s again. I took another log just in case it helps http://www.filedropper.com/skypebugcm11 .

I've looked at some other liquid smooth threads and I read something about fixing it, I cant remember what now but it didn't work for me. I did read someone said that stopping certain apps made it work, because another app was sharing the mic or something like that. Maybe something running is using the mic and causing a conflict? Whatever it is i cant find anything that works at the moment .Annoying because Liquid smooth works so nicely apart from that. Ill keep with verygreen's cm11 for now, but keep up to date with this thread and do some more tests if it helps fix it.
[Nook HD, HD+ Android Development] rhyang:
So did you delete the file I mentioned earlier or not ? No worries if this is confusing; just be honest and save everyone's time .. Later can make you a flashable zip for use in recovery.
[Nook HD, HD+ Android Development] vimesxda:
Ah I forgot about deleting that file on cm11. Yeah I'll backup and try cm11 whilst deleting that file and see if it works. I didn't think of it because i was trying to fix the liquid smooth not the cm and it just wasn't on my mind when I was trying the cm11.

Ah installed now and deleted camera stub on cm11 and is working fine. Finally something actually went right. Now just to get working on liquid.
[Nook HD, HD+ Android Development] Jon Lee:
Alright, here it is. LiquidSmooth F2FS ***ONLY*** build.

ROM:

http://www.mediafire.com/download/s7gis87skzl68u6/LS-KK-v3.2-2014-10-30-ovation.zip

MD5:

http://www.mediafire.com/download/9eyuyy72f8d3fb7/LS-KK-v3.2-2014-10-30-ovation.zip.md5sum

Requirements:

To avoid confusion with incompatible recovery versions, Install and use THIS RECOVERY:

http://www.mediafire.com/download/33f8skzaxwk00u6/OVATION-TWRP-20140729-recovery-F2FS.zip

This is the only recovery I have used and tested this with and that I know to work.

Do an 'Advanced Wipe' and individually go through and convert system, data, and cache to F2FS. If you're already using an F2FS system, then still do a complete wipe of system, data, and cache. This is mandatory.

Changes:

1) Exchanged CM11's Bluetooth stack out for Omni-4.4's. (less audio dropouts)

2) Removed Camera stub from build.

3) Added live wallpapers & zram.

4) Kernel and defconfig changes.

5) Compiled with 'Link Time Optimizations, LTO'

(See Post #3)

http://xdaforums.com/galaxy-nexus/verizon-develop/rom-fml-fork-life-06-05-2014-v2-t2427087

***Source***

Kernel:

http://www.mediafire.com/download/6ozqoglter8pa76/omap.tar.gz

Device:

http://www.mediafire.com/download/899s82mqs1txb89/device_bn_liquid.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
Woo-hoo! Is this the first impementation of f2fs for KK? (I presume you took trim out, or that it won't try to start?)

So, before I try it, does your Recovery allow me to format back to ext4?

And is it drmables version of zRam, or is it the standard compcache?
[Nook HD, HD+ Android Development] Jon Lee:
There's a decent conversation on the 'Yellow Kernel' thread about F2FS and trim (towards the end).

Yes, Rhyang's recovery will allow you to convert back to ext4. TWRP backup and restore feature works quite well across different filesystems btw.

Zram is of the zsmalloc variety (I believe the only nook kernel that has this).

Also, the kernel source is refusing to upload for me (I don't know why...It won't even start/stalls at 0%), so it will probably be tomorrow or the next day. :(
[Nook HD, HD+ Android Development] PMikeP:
Thanks. Found it about 2/3'rds way in.

So, did you enable the cleaning operation in this f2fs build or play it safe?
[Nook HD, HD+ Android Development] PMikeP:
I got it up and running.

Just to make sure, you don't want us converting Dalvik to f2fs? (Just /cache?)
[Nook HD, HD+ Android Development] Jon Lee:
Correct. Dalvik cache is actually covered under data.

and yes, cleaning operations are enabled by default.

(should still be safer than trim).

Btw eventually I might build a cm11 with compiler optimizations and yellow kernel. Somewhat strapped for time right now though.
[Nook HD, HD+ Android Development] PMikeP:
Initial observations on LS f2fs

I'm running Jon's f2fs build of LiquidSmooth, posted above.

My first observation is that, even tho a build running f2fs might not automatically give higher benchmark numbers, the system runs at least 10% faster anyway. (I see this with my Galaxy Tab 2 too.) I notice the speed increase the most when browsing the web. Even the LS boot animation of the slo-mo stream of water runs smoother. (No more stutters.)

On this particular build, I get 19480 (!) on AnTuTu after disabling the "safety" in Dynamic Fsync. That's my highest score yet. (Curiously, Dynamic Fsync doesn't affect file I/O scores. It's "Multitasking" that jumped from 3000 to 3800.) That is more of an increase from my best CM11 score than simple overclocking would predict. So perhaps LTO has done a lot to speed up the kernel?

I can't find a check box to enable KSM, nor a check box for purging bitmap assets (or whatever it's called) as you usually find the Memory Management sub category of Performance in CM. Didn't see them with Trickster Mod either. It could be buried somewhere in LS and I haven't found it. Presumably, they would make things even faster/more useable.

Jon says his build is running zsmalloc for zRam. I don't know how that compares to drmarble's 10 step implementation of LZO zRam. (Currently the steps are here, but if they get merged into CM 11, they will not be on his Gerrit page anymore.) I don't know how to test for differences between the two implementations. But I can say that the app zRam Status doesn't seem to report status accurately with either implementation. (When compared to "free" in Terminal.)

FWIW, Jon is running a 64K swap. drmarble is running 128K.

No crashes or fc's so far. (Although I've only been running it less than 24 hours so far.) Very promising.

Now that Jon (and rhyang?) have shown the way, I hope the CM11 folks will update their kernel to support f2fs soon. (Nothing against LS. It's just that CM 11 seems to have more bug squishers banging away at it.)
[Nook HD, HD+ Android Development] Shermanballz:
mixed results so far

Well this sounded pretty exciting. Haven't messed with f2fs before, but heard good things.

So first round went okay. Got rom installed, did my liquid gapps, restored some old apps...

Then I tried to install the lollipop keyboard. I had done this on two other devices as well as this one when I had SlimKat. No issues then. But this time when I rebooted I got a boot loop. Rebooted right at the lock screen.

So I tried wiping cache. Now it boot looped just before the lock screen

Tried reinstalling rom and gapps - boot loop at lock screen

tried wiping everything, reinstalled rom and gapps - boot loop at lock screen. But now it seemed to sit there until I touched the screen.... weird.

so I formatted system, dalvic, data, cache, internal. Converted system, data, and cache to ext2, then back to f2fs. Reinstalled rom - worked

Downloaded liquid gapps. Installed. Lockscreen boot loop.

Formatted everything, reinstalled rom, downloaded PA gapps - stock was too big to install.

Tried liquid gapps again - force closed.

Can anyone suggest an alternate gapps? The PA link from liquid downloads (in about tablet) had modular and mini for 4.3, but I didn't see for 4.4...
[Nook HD, HD+ Android Development] PMikeP:
Sorry to hear you're having so many problems - especially since mine is running fine. (I did end up going back and setting the conservative file I/O switch. It might be too fast without the safety on - I kept getting funky color-TV like bar test patterns flickering on my screen between transitions with the safety off.)

To answer your question, I am using PA GAPPS, specifically the Nano version. I also use gapps remover (on the same page) to remove a lot of google junk before it can install.

I read in the Liquidsmooth information that the ART runtime cache might not fit if you're using a large GAPPS. They suggest running Dalvik. (But I'm running ART and doing okay with my minimalistic GAPPS installation.)
[Nook HD, HD+ Android Development] PMikeP:
AOSP keyboard problem in LS?

I doubt this is a function of Jon's build of Liquid smooth. Rather, I think it's something in LS itself.

But, even tho I have Correction and Next word suggestion turned off, my keyboard still insists on correcting words for me sometimes. (For example, it put the space in Liquidsmooth!, above.)

Anyone else getting this?
[Nook HD, HD+ Android Development] PMikeP:
Multiple zRAM devices?

First, I'm finding that 60 MB of zRAM is not enough for my multitasking purposes. My aviation moving maps are constantly restarting after switching back to them.

Fortunately, it's easy enough to modify the 60ZRM text file in /ect/init.d to increase the swap size. I'm using 96 MB right now, that that works for me. Later, I might decrease that amount to find what the minimal zRAM is needed for my purposes. (And then add a 10% fudge factor to it.)

Next, I have come across people on the web who are saying that there should be as many block devices of zRAM running as there are cores in you CPU. This due to a bottle neck in zRAM in kenels 3.15 and lower.

In particular, from the gentoo wiki " . . . the recommended amount of devices for swap is 1 per cpu core for kernels prior to 3.15."

So, since Jon's LS build is running a 3.0.31 kernel, I tried enabling two block devices of zRAM (zram0 and zram1) using

modprobe zram num_devices=2

and the additional lines of code needed to initialize and instantiate zram1.

(Naturally, I divided the total swap size I wanted (96 MB) into two 48 MB swaps.)

But trying to run zram0 and zram1 didn't work. The "free" command in Terminal showed only one block working.

Maybe it's because this custom kernel was built to only supports one block? I say that because there's something in the gentoo wiki about configuring the kernel with the max number (M) of compressed RAM block device support.

I'm not smart enough to take this any further. Thoughts anyone? It might be interesting to try the two blocks for our dual core CPU to see if that's any faster.
[Nook HD, HD+ Android Development] Shermanballz:
Are you referring to the fsync option in the kernel tweaker? I checked that and I think it did make a difference, although I'm not totally without occasional boot issues. Thanks!

However I think you've got the right idea. I think I'm just taxing the system too much because my boot loops never happened consistently with my installs. Once it was after enabling greenify exposed settings. Another after installing a keyboard, and various other times. But the next time it would work and something else would screw it up. Only time it was consistent was when flashing liquid gapps or when flashing ANY gapps without first booting the ROM (is that typical with LS?). And now I've had a couple boot loops that were fixed by waiting a few minutes before booting or rebooting several times.

Very frustrating because when its working this ROM just FLIES! But I clearly don't want to troubleshoot this thing every day ;)

So... Got any ideas? Some kernel setting I can try tweaking? I'm no noob, but I really don't have much experience with kernel options.

Thanks!
[Nook HD, HD+ Android Development] Jon Lee:
When you have it up and running, try editing /system/bin/fix-mac.sh

(with Root Explorer or some other file manager) and add a

'wait 1' on the line immediately after 'busybox mount -o remount,rw /system'

and see if that doesn't fix your problem.

(Also be sure to use 4.4 gapps and not 4.3...)
[Nook HD, HD+ Android Development] PMikeP:
Yes.

The UI there is confusing. (At least to me.) There are two check buttons on the same line.

I am guessing that clicking the round checkbox (an oxymoron) enables Dynamic Fsync.

I think the "If enabled gives stock I/O and data integrity" check box is enabled, it either disables delayed writes and/or write caching.

I have mine set for Dynamic Fsync with the integrity check box checked. (With the safety off, I was getting massive screen flickers between transitions.)
[Nook HD, HD+ Android Development] Shermanballz:
Hehehe... Yeah, kinda weird

I was thinking that the small, boxy check box was choosing on or off and the round one was whether or not to apply that setting on start up.

Actually upon my first reboot it messed up again :( But I will try again. Thanks for the help, guys!
[Nook HD, HD+ Android Development] PMikeP:
Screen rotates on sleep

Not really a problem. More of an observation: When I'm in landscape and I put the tablet to sleep, the screen rotates to portrait as it goes to sleep.

It didn't do that in CM 11 (AFAIK) and I don't recall it rotating in the previous version of LS.

P.S. f2fs really flies! Difficult to imagine ever going back to ext4.