yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] angelofmenoth:
When I reboot for any reason, I end up in a crazy set of boot loops for a long time, but if I leave it alone, I eventually come back to see that my tablet has finally booted properly. When it is up, its amazing (as expected), but the inability to reboot without losing 20+ minutes sucks.
[Nook HD, HD+ Android Development] PMikeP:
Even with Jon's fix?

Also, once it's running, you could drop the CPU speed back to 1500 GHz.
[Nook HD, HD+ Android Development] Jon Lee:
Observant. When I was working on the 'yellow kernel', I pulled pvr source, I assume, from the 10.1 branch. This source was incomplete/wrong version and I had to apply a patch to bring it up to the proper version. Even though the patch applied cleanly, the pvr had a bug in one of the files (a power file). I ended up replacing this file with the equivalent from an omap5 pvr source I had found (which I can't find anymore/isn't public anymore).

This power file has a "smooth" turn off effect, and very different from the screen squish effect of CM11's pvr source.

I used my/this pvr source for the first builds of liquidsmooth and slimkat (Actually switched it out because I prefer the smooth blank out).

But In the f2fs build of liquidsmooth, I used CM11's source (because I was playing with Tuna's pvr and it just sort of stayed).

I've noticed two things. CM11's source fixes a long standing random/occasional pvr memory manager issue I had been seeing but also introduces random/occasional "screen tearing".

FWIW.
[Nook HD, HD+ Android Development] PMikeP:
If, by screen tearing, you mean vertical color bars, I get those frequently during transitions. If you mean "rewind scrabble" (like on an old VCR), I've gotten that once. Like an oscillator (or, more likely, a PLL) loses lock.

I presume a future build of f2fs LS with a later CM11 "stable" Milestone source (hint, hint) will solve this problem. (Or an f2fs Yellow Kernel for CM11. I read that Lollipop has upgraded to 3.15. Will

that kernel play in KK?)
[Nook HD, HD+ Android Development] Jon Lee:
I suspect the 3.15 kernel bluetooth driver will have to be backported to our 3.0 kernel for us to have bluetooth on Lollipop. I don't know for sure yet. I'm in the middle of an aosp_ovation lollipop build, so I'll know for sure shortly.

Luckily, for us, someone has already done the hard work on that already.

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

As far as pvr's, I probably should do a diff between the two...
[Nook HD, HD+ Android Development] PMikeP:
Glad you're looking into it. No BT would be a deal breaker for me, since I use BT for GPS in the cockpit for aviation moving maps. (Although, frankly, unless L brings more performance to the table - which I'm guessing the later kernel will - I'm happy with your build of LS.)
[Nook HD, HD+ Android Development] PMikeP:
Does LS attenuate audio?

I've noticed my HD+ can't get as loud with LS as it could with CM 11. (By about 6 dB.) Is there anything in a build that affects this?
[Nook HD, HD+ Android Development] Jon Lee:
DL1_MEDIA_PLAYBACK_VOLUME found in device/bn/common/audio/audio_hw.c

I reduced it for several reasons. I felt that overdriving it to the extent that it was caused distortion, also because this rom includes Viper4Android, one can make up for it by enabling 'eXtra-Loud', and I didn't wan't anyone burning out their speaker. Mainly it was about audio quality though.

:D
[Nook HD, HD+ Android Development] PMikeP:
Hi Jon:

Thanks for the quick reply and for confirming (indirectly) that I'm not losing my mind when I notice these small differences from LS to CM 11.

I see Viper4Android in the list of system apps (under ALL), but I don't see it in the App drawer nor have I found it in any Setting. So I don't know how to open it, to enable "eXtra-Loud." Got any hints? (I vaguely recall DSPManager being an option in Preferences with the built in audio player in CM 11, but I don't recall if the settings for DSP persisted to my preferred audio player.)

I can't find a file audio_hw.c in my system to modify (let alone a directory named "device,") so I'm guessing that's a file for building the LS image that only true geeks know how to do. But since I'm only a user/hacker who can barely use Linux . . .
[Nook HD, HD+ Android Development] Jon Lee:
<settings><LiquidSmooth><Equalizer>

<Enable Viper4Android, etc>

If I ever get a functional Lollipop build, I will force 48khz pcm sampling in the kernel...twl6040.c (Actually already have, just waiting for a build to put it in).
[Nook HD, HD+ Android Development] PMikeP:
Thanks Jon. I feel kinda stupid not finding Viper4Android on my own. One would think it would have been under Sound, but it appears the LS folks put all the LS speciality stuff under LiquidSmooth. (Which presumes users already know what distiguishes LS from stock Android.)

Volume is fine now with eXtra-Loud.
[Nook HD, HD+ Android Development] kokercey:
I am having a difficult time downloading this rom from Mediafire. Has anyone else had a difficult time. I have tried Firefox, Chrome, and IE all with no luck. When the download link is clicked will reload back to the download link. Twice it has loaded a capcha (sic) which when submited returns me to the download link. Any thoughts anyone.
[Nook HD, HD+ Android Development] PMikeP:
I've noticed that with some of these file share sites, there are numerous ads that are disguised as download buttons. IIRC, it took me a few false starts to download Jon's ROM. Since he's a developer, perhaps he qualifies for - and can get - an xda hosted site, as drmarble did for his zram variation of CM 11?
[Nook HD, HD+ Android Development] kokercey:
Thanks Mike for your quick responce. I wiil keep trying. I have had problems with mediafire in the past. I have been on cm11 builds sence succulent stopped building and have not been real happy so i will try this one of Jon's and compare, Thats if i can get it downloaded.
[Nook HD, HD+ Android Development] sarthakkapoor25:
Maybe a dumb question,but i am getting bootloops on both LS and SK.Tried full wipe but still doesnt work.Had to go back to succullents CM build.
[Nook HD, HD+ Android Development] kokercey:
What recovery are you running. When i changed from succullent's builds i had to change recoveries due to boot loops
[Nook HD, HD+ Android Development] JeauxAdam:
Change to what recovery?

Sent from my Nook HD+
[Nook HD, HD+ Android Development] sarthakkapoor25:
Tried both CWM and TWRP.
[Nook HD, HD+ Android Development] kokercey:
I switched from Succulent's TWRP 2.7.1 to CWM 6.0.4..5b and it has been working for all my Rom's. The only advise i can add is full wipe with /system format and install using CWM 6.0.4.5b

So far this Liquidsmooth build has been good for me. I will keep it for another week before deciding if it is the one for me.
[Nook HD, HD+ Android Development] PMikeP:
But if you don't use the special TWRP recovery for this LS ROM, then you can't use f2fs, which is one of the major benefits of this ROM.

You can use that recovery to convert back to ext4 if you don't stay with this ROM. And I expect (but don't know) that it will work with other ROMs too., since it's based on a later TWRP.
[Nook HD, HD+ Android Development] Reed-Sternberg:
Yeah, I'm in the exact same situation. F2FS is sooooo much better, I can't believe this is the same tablet. but the bootloops after every reboot is just too much. I also made the change in fix-mac.sh, and reverted the overclock at no avail. any suggestions folks?

at a side note, I think when the wifi is connected to my router, it breaks the connection somehow! my other devices lose connection. I find this really weird. can anyone else confirm this?
[Nook HD, HD+ Android Development] PMikeP:
FWIW, I do not get any bootloops with Jon's f2fs build of LS nor does wifi break my router connection. I've been running this build since the day (night?) it came out on a Nook HD+ CPO 16 Gb unit.

I'm still running 1.6 GHz and no fix-mac.sh. I run Hotplug governor. Maybe try that and tell Kernel Tweaker to set it at boot.
[Nook HD, HD+ Android Development] JeauxAdam:
One more question. I see there was discussion about being able to bounce back to a "normal" ext4 ROM using the F2FS TWRP recovery if needed. How would a person go about doing so if need be?

I doubt it will be necessary as I am confident in the devs abilities and as long as this version of LS has pie control and works with Netflix I'm good to go. I don't do a lot of gaming or heavy usage so my requirements a minimal.

Thank you all for being so helpful.
[Nook HD, HD+ Android Development] mcord11758:
I went back to another rom and still have this recovery. Just advanced wipe converted system, data, cache to ext4 then flashed o other rom
[Nook HD, HD+ Android Development] JeauxAdam:
That would make sense. Just wanted to be sure I wasn't forgetting something. Thank you sir.

Sent from my Nexus 5
[Nook HD, HD+ Android Development] Jon Lee:
Also if you make a TWRP backup of the rom you currently have onto external SD, you can restore it without having to convert filesystems. I have three or four roms on backup and it only takes a few minutes top to restore them.

Easy-peasy.
[Nook HD, HD+ Android Development] PMikeP:
Wait. Jon, I want to make sure I understand. Before switching to your f2fs LS ROM, I made a backup of my old CM11 ROM, which was on ext 4. Are you saying that I could simply tell TWRP to restore CM11 over the current f2fs file system and TWRP would automagically convert the f2fs partitions back to ext 4? And likewise, after I restored CM 11 on ext 4, I could go back and restore your f2fs LS ROM and TWRP would automagically convert the partitions back to f2fs?
[Nook HD, HD+ Android Development] Jon Lee:
Yes, it gives a warning (about incompatible filesystems), but otherwise works for me (without having to go through and convert). Try it!
[Nook HD, HD+ Android Development] PMikeP:
Thanks for the near real-time reply!

I wonder how it knows what format the image is in? (rhetorical) I thought an image was agnostic? Must be pretty smart.

I would have tried restoring an old CM 11 in ext 4 (although no reason to leave your f2fs LS build) but didn't want to hose a partition and brick my HD+.
[Nook HD, HD+ Android Development] Jon Lee:
I am convinced that 99% of supposed "bricks" (and I'm talking about the "corrupted emmc" variety) could be fixed.

If not with the ability of TWRP to do a real "format", then as long as fastboot can see the entire partition table....

As far as TWRP, I assume it does backup/restore with a type of .img, which carries the filesystem with it.
[Nook HD, HD+ Android Development] JeauxAdam:
Just installed the F2FS version a bit ago and it seems good so far. It seems to "forget" I'm using pie control sometimes so I disable/enable it and it's good. Had one random reboot which made it forget everything I set up but has been good since. I'm sure it just needs to "settle" for a bit.

Overall very nice. I like it. This old girl seems to have a bit more life in her now.

Sent from my Nexus 5
[Nook HD, HD+ Android Development] mcord11758:
I have to give this a shot again, first flash no matter what gapps I used I got bootloops. If I let it go for like ten minutes it would eventually boot but any reboot would go back into bootloops. Ran fine otherwise. If I did not install gapps there was no bootloops
[Nook HD, HD+ Android Development] JeauxAdam:
I used the nano version of the PA gapps that were linked somewhere in here. Don't know if that mattered. Other than the ROM forgetting I have the PA pie controls on, causing me to go into settings to disable and then enable it again, it's been pretty sweet.

I see there's an option to turn on ART but there's a warning that pops up stating Liquidsmooth doesn't support it. I'm a little sad but then I can use Xposed framework so it balances out. :)

Sent from my Nexus 5
[Nook HD, HD+ Android Development] PMikeP:
Lately I've been getting a message every now and then that the ui has stopped working. It forgets my wallpaper.

I don't know what changed, since I haven't changed anything since initial install. (Well, I did enable Viper4android.) It seems to happen when I've been using the tab for a long time. (More than an hour?)
[Nook HD, HD+ Android Development] Jon Lee:
Generally, the first thing to do for those types of problems is wipe cache and dalvik-cache and reboot and let it rebuild the cache. The majority of the time, that will take care of it.
[Nook HD, HD+ Android Development] PMikeP:
I wiped them last night. That seems to have stopped the TV color bars I was getting during transitions between apps.

But I got the message that the process "system.ui" stopped after reading a user's manual PDF for about an hour. My layman's guess is that it's some google process trying to run in the background.

I noticed that some new services have crept in on Play Services, presumably from updates to Play. I disabled those. We'll see how it goes.
[Nook HD, HD+ Android Development] PMikeP:
Yeah, it says that. But I've been running ART anyway for the past many weeks without incident.

Jon is the expert on whether LS supports ART any more than CM 11 says it does(n't).
[Nook HD, HD+ Android Development] Jon Lee:
Personally, if it were me, what I would do next is to use a terminal, cd /data/system, rm -rf *, reboot. This will wipe most of your settings, but will retain your apps. In fact I wish recovery had an option to wipe this, as I've had to use it before.
[Nook HD, HD+ Android Development] Jon Lee:
ART gave me reboots (I believe it was with the Browser). I ended up having to change back to Dalvik.

If I were still working on this build, I would end up upgrading ART to AOSP or Lollipop. I'm playing with other Lollipop builds ATM though.
[Nook HD, HD+ Android Development] JeauxAdam:
I'm totally fine with Dalvik. Its working great so far. Thanks for your continued efforts!

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] PMikeP:
Thanks! I did it. (It's taken me 3 hours to type all my custom settings back in and to make sure everything works for a flight tomorrow.) ) We'll see if this makes things better.

For those who don't know, you have to type "su" at the command prompt in Terminal before you type Jon's string to remove the files in /data/system.
[Nook HD, HD+ Android Development] PMikeP:
I couldn't get Play to update programs after I did the rm. This could have been my problem, since I've disabled a lot of services in Play. Or does Android lose track of what version of Play you're on? For example, I didn't have the option to uninstall updates.

I didn't have time to experiment more - I restored to where I was before the delete and then I selectively went in and deleted a few things from /data/system.

Actually, there's not much there. I don't understand why a delete there can make a difference.
[Nook HD, HD+ Android Development] Maltings:
No issue here either. F2fs + art + viper. No reboot, no issue.

I removed the stock browser, though, and use dolphin zero for everyday use.

Not really bothered with pie, I see it popping once on a while, so I must have activated it...

Also, not using any gapps, just a handful of APKs backed up earlier...
[Nook HD, HD+ Android Development] Maltings:
ART - browser

As per my post last night, you're right (from empirical testing): 1st thing I did after f2fs format and ROM installed, was removing stock browser, installing dolphin zero( pure browsing: no tabs, bookmarks, or anything), then set ART. I used it like that for about 2 weeks with no issue.

After I posted last high I installed another browser (dolphin HD)... Out of curiosity I rebooted... And it started a reboot loop,

I got lucky enough to have the few necessary seconds at boot to uninstall the new browser... No reboot since...
[Nook HD, HD+ Android Development] JeauxAdam:
I had a couple days of weirdness but everything seems to have "settled" since and have had no performance issues to speak of.

One annoyance that has remained is forgetting my pie control settings occasionally after rotating. It's easy enough to flip it off and then back on in settings but I thought it was worth noting. Otherwise it has been great!

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] PMikeP:
Yeah, I need to wean myself off of Play. That's the only reason I have GAPPS installed. Aside from the political reasons for not installing GAPPS, there sure are a lot of junk services that Google keeps adding. That keep trying to start.

This last version had about 20 more services for wear, games, kids, etc. I keep going in and disabling them with Disable Service. But the cleanest way to have a trouble free system, and the longest battery life, is to run clean.

P.S. Is there some trick for downloading .apk's off of Play on the web? When I first tried it, I kept getting a message about how my tablet wasn't compatible with the app, even tho I was using the account tied to my HD+ on Play. (Why is BB protecting me in the first place. But there I go on the political stuff. . . :) )
[Nook HD, HD+ Android Development] Maltings:
Going lean

Not that I'm aware of; also depends on which apps...

An alternative and less intrusive market app can help: say you use amazon market: install market, download and install apps, remove market...

I found a few reviews of alternate market, but as far as what I have seen, the most practical alternative is amazon.

Personally I use a lean 4 or 5 apps diet these days: 1 fat free browser, 1 game , 1 news reader, 1 file manager (ES's self updating btw), 1 media player.

As pretty much everything is available through a browser these days, and my phone can do wheather/email/social..., I can keep my tablet this way for now...

M.
[Nook HD, HD+ Android Development] Monfro:
There are some markets alternative to Google Play Store, like:

- Aptoide

- F-droid

- Amazon appstore

- Yandex.store

And probably others I don't remember.

Or websites like

www.apkmirror.com

Google apps needs Google services to works (available in Gapps packages), so it is not enough to download and install them.
[Nook HD, HD+ Android Development] Shermanballz:
Try this, it's called Raccoon:

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

Install on your desktop. You can sign in with your account and get all of your free AND paid apps. You can use a specific Android ID and still limit apps by device compatibility, but if you leave it blank it will generate a new id with no device restrictions. Download onto your computer, transfer to your device.

Worked well for me. Allowed me to install Hulu+ and I've had no issues.
[Nook HD, HD+ Android Development] PMikeP:
Hey, thanks for the heads up! I haven't had a chance to try it yet, but looks promising!
[Nook HD, HD+ Android Development] DSoundso:
Why don't you just install the pico gapps package?

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

I tried to go without store for some while but to be honest, it was annoying and over complicated if you still prefer some comfort using/installing/updating apps.

For me the pico package is a fine alternative not handing Google my whole device.
[Nook HD, HD+ Android Development] Maltings:
got it stable with art

I managed a stable ART Install that includes stock browser: some steps may be optional, but here is how I got to it

Step1: try that horrible cm11 temasek mod. yuk.

Step2:decide to come back to LS. Yay.

3. Format system/cache/data f2fs with twrp

4. Install ROM, reboot

5. In LS settings, remove stock browser ( I removed a few other, like calendar as well, but fear not: see next few steps)

6. Install my apps

7. Switch to ART and reboot

8. It should bootloop by now

9. Run the ROM install again

10. Tadaa. LS with f2fs, art, and no browser issue/fc/bootloop

I must say I haven't been as far as installing gapps...
[Nook HD, HD+ Android Development] PMikeP:
I haven't tried this yet (reqires java and I haven't gotten around to building a Windows VM w/ java). In the meantime, I found http://downloader-apk.com/.

I wonder if it's a website running Raccoon? It finds my proprietary aviation moving map apk.
[Nook HD, HD+ Android Development] DSoundso:
I have a question. How do I stop this ROM from closing apps when my device goes in standby. Every time the screen goes off I need to start my PDF document or something else again because I am back at thee home screen. Is this unusual or a common feature?
[Nook HD, HD+ Android Development] twiztid_:
There is a setting under developer options that (I think) closes all apps when you sleep, near the bottom.

On lollipop its called "Don't keep activities", it may be the same on kit kat.
[Nook HD, HD+ Android Development] twiztid_:
With standard CM11 I have been having an issue with the keyboard flickering on/off and just flat out not working, mostly in chrome but on occasion in other apps. Updating to CM12 and dropping chrome has eliminated the issue completely.

Would this ROM (most likely) have the same issue, since its also based on kitkat? Or could some of the fixes/changes have solved this?

I would (and may) try for myself, but it would involve changing my recovery and I don't have the time to test it and then undo and reinstall everything for a few days.
[Nook HD, HD+ Android Development] PMikeP:
Jon has moved on to a Yellow kernel for CM 10.2.1. http://xdaforums.com/showpost.php?p=59112482&postcount=189

It's a hybrid ROM, half f2fs, half ext4.

I use Chrome and the stock keyboard. No flicker.

Before Jon moved on, I used to use this LS. But his latest is better. Haven't had to reboot for weeks.
[Nook HD, HD+ Android Development] toplist:
I have been using this rom for about a month now and am surprised by how good it is. I'm on the full ext4 version. I tried the f2fs version but got random reboots for some reason and reverted back to ext4 immediately.

I like to use the most updated rom and I jumped on lollipop wagon from its earliest days. I tried the initial rom from hashcode and then moved to amaces's rom. Kudos to both of them for bringing lollipop to ovation. However, I had problem with listening to music on the background while multitasking on lollipop rom. It might have been the notorious memory leak bug of lollipop. Since I listen to music from my sdcard while reading/browsing on the nook, I had to find a different rom. Then, I jumped to Jon's yellow kernel rom and I must say that is the smoothest rom I've used on ovation. It was jellybean and plain cyanogenmod. So, I wanted to try something else.

I found this LiquidSmooth Kitkat rom and am impressed by the performance of it. I've never run benchmark on any rom and from the everyday user experience, this rom is pretty close in smoothness to the yellow kernel rom. . I should mention that I've not flashed gapps on it and keeping my number of apps to minimal. For those of you who aren't aware, this rom has multiwindow besides other features (custom density, total blackout, built in adblocker, pie controls etc.). Jisoo's Carbon rom comes to mind when comparing the number of features/tweaks available on this rom. The only glitch I experience sometime is when jumping to an app from recent panel. But it doesn't lag app switching or compromise performance. This has been a perfect rom for me and I want to give a shout out to Jon for his wonderful work on our device. I'm looking forward to your SlimLP.
[Nook HD, HD+ Android Development] Nolfer:
I'm having issues with battery. The nook just dies when I leave it somewhere for more than one day. Fully charged. I have to re-charge it again. Is this a rom problem or am I probably on the verge of throwing my nook in the garbage bin?
[Nook HD, HD+ Android Development] ajislav:
Could be the Google Play Services which prevent the tablet from going to deep sleep. Check it using BetterBatteryStats and if indeed so then search for SystemUpdateService and possible workarounds.