yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] angelofmenoth:
Easiest way to remove flickering is to disable overlays in developer options.
[Nook HD, HD+ Android Development] volpo222:
This setting does not persist between updates.

Is there anyway to make it persistent?

Thanks,

V
[Nook HD, HD+ Android Development] angelofmenoth:
I haven't found a way to make it stick between updates, but I remember to set the option again as soon as I see the first flicker. LOL
[Nook HD, HD+ Android Development] razholio:
this isn't gonna work for you unless the bluetooth device supports A2DP (bluetooth stereo audio). You can pair and even connect to a device that will not play back the 'media audio' from android because it only supports 'phone audio'. There are mono devices that do support this (bluant earpiece - mine is set to 'phone audio' only) but they are few and far between. Most commonly you will find bluetooth speakers that also serve as a speakerphone and will therefore support 'phone audio' in addition to 'media audio'. I recently played audio from google music on my nook HD+ running CM M8 through my stereo bluetooth speaker and it worked fine.
[Nook HD, HD+ Android Development] tomlang:
I'm still having no luck casting the screen. Casting from a chromecast aware application works well. I downgraded Google play services to 5.0.82, and rebooted both the nook hd+ and chromecast after running the mirror enabler with all three switches set. A few seconds after I try to cast screen to my chromecast, Google play services quits and it disconnects.

Any ideas?
[Nook HD, HD+ Android Development] PMikeP:
Wow, good answer! Thanks.
[Nook HD, HD+ Android Development] GMTN:
I've miracast Youtube from the Nook stock ROM before onto a setup box connected to the TV, not sure if that's what you mean.

I think I'm ready to make the jump from stock . If I completely bomb this, will I be able to use leapinlar's

emergency tips to reinstall to the stock ROM or am I better off trying the SD install first ?
[Nook HD, HD+ Android Development] RhinoNelson:
Restoring to stock

I have just used his thread to restore my HD+ to stock using an SD Card. In the process of flashing I got stuck in a recovery boot loop. His thread explained why it was happening and how to resolve it.
[Nook HD, HD+ Android Development] extrem0:
Flash this and try again.

http://d-h.st/Nmb

You can use official cm11 nightlies and flash this to get mirroring working. You'll still need that #Mirrorenabler App.
[Nook HD, HD+ Android Development] tomlang:
That was all that was needed, thank you so much.

I am now casting my SlingPlayer audio and video from the Nook hd+ on the cm11 08/02 build very nicely.

The lag time is minimal, but I notice the audio is slightly out of sync with the video, even on the Nook, while casting. Might be hardware limitations.
[Nook HD, HD+ Android Development] NishantM:
M9 is available for download.

http://download.cyanogenmod.org/get/jenkins/78497/cm-11-20140804-SNAPSHOT-M9-ovation.zip
[Nook HD, HD+ Android Development] andtron:
What are so special about the "M"s versions , are they the so called stable releases?

TIA
[Nook HD, HD+ Android Development] NishantM:
M or Milestone releases are considered more stable than nightlies . And you got an accidental thanks from me :P
[Nook HD, HD+ Android Development] leapinlar:
Read here:

http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items

And here:

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
[Nook HD, HD+ Android Development] gregs1213:
Currently running TWRP 2.3.3.0.. I tried to update it via flashable zip (both CWM and TWRP) and I keep getting:

E:Unable to mount '/boot'

E:Unable to mount '/bootdata'

I am currently running CM10.1 and wanted to upgrade it to CM11....
[Nook HD, HD+ Android Development] leapinlar:
Probably best to make a new bootable CWM. SD to flash the new internal recovery. Go to the Dummies guide linked in my signature to get the files.
[Nook HD, HD+ Android Development] digixmax:
Which flashable zip did you try to use?
[Nook HD, HD+ Android Development] Eric Karz:
.Any plans to make new goodies for extSD install ?

opps
[Nook HD, HD+ Android Development] leapinlar:
Please don't quote the entire first post. Please go back and edit your post to remove the quote.
[Nook HD, HD+ Android Development] rhyang:
Showing Photospheres in Google+

I started taking photospheres on my phone a little while ago, and was a bit annoyed that with CM11 on the HD+ (probably HD also) I could never view them in Google+; instead google services would FC. After looking at a few logs it appeared that G+ was trying to use the Android side of the Camera HAL to get camera properties, which was failing since there was no other side (no camera.ovation.so in /system/lib/hw). It didn't look like USE_CAMERA_STUB was actually doing anything.

So I added a stub camera solely for showing photospheres on G+ :) Here's an unofficial build of CM11 which is otherwise the same content as the 9-August nightly : (please do a backup first)

http://rhysw.com/CM11/cm-11-20140810-UNOFFICIAL-ovation.zip
http://rhysw.com/CM11/cm-11-20140810-UNOFFICIAL-ovation.zip.md5sum

The commits are in these two forked repos : (cm-11.0 branch)

https://github.com/roberthyang/android_device_bn_common
https://github.com/roberthyang/android_device_bn_ovation

This creates camera.ovation.so in /system/lib/hw. I tested it out with other camera-using apps like Facebook and Flickr, and it looks like no harm was done. Please check it out if you like, and let me know if there are any glaring problems (a log would help; I like CatLog from the play store, but there are others). If the code doesn't look too horrendous I'll try and submit the changes to CM. Enjoy !
[Nook HD, HD+ Android Development] YevOmega:
Can someone running CM11 M9 please run the Quadrant and Antutu benchmarks right after a reboot and post the scores that you get? If that's too much work, then at least just Quadrant. Thanks!
[Nook HD, HD+ Android Development] andtron:
I am running Aug-09 build, don't think it is going to make any difference:

Antutu - 13531

Quadrant - 4098
[Nook HD, HD+ Android Development] YevOmega:
Thanks a lot. Pinguy's Tweaked Xperia ROM seems to indeed be the best option. Time to get it.
[Nook HD, HD+ Android Development] tomlang:
Quadrant score on my 8-9 build is 3018

According to Quadrant, 10.1 is faster. Maybe so, maybe not in real world use. Personally, I'm staying on cm11. I like KitKat's ability to cast screen and it is definitely fast and smooth enough for me.
[Nook HD, HD+ Android Development] danj88:
Jumping from CM 10.1 to CM 11 M9:

Very responsive and smooth experience. However, the battery seems to drain quite a bit more than with 10.1. Additionally, the Nook has gone into standby mode quite a few times since I upgraded. It seems to go into standby mode with certain screen input or movement of the tablet but I have yet to pinpoint the exact trigger.
[Nook HD, HD+ Android Development] PMikeP:
Is there an easy way to enable zRAM?

I like CM11, but as andr0idfreak has observed, its aggressive memory management negatively affects "multitasking." For example, my aviation moving map application is always being shut down and has to restart if I go browsing on the net for more than a few minutes. Whereas, with CM 10.2.1, which had zRAM as an option, I didn't have that problem.

Even tho the developer of zram settings says zRAM is "a thing of the past," my understanding is that KitKat was supposed to support zRAM out of the box. Succulent's CM11 has it.

So, is there an easy way to enable zRAM in CM11? By easy, I mean, not having to recompile a kernel. (I can only do simple things, like modify scripts, etc.)

Why is zRAM suddenly undesirable?

Did the CM devs intentionally leave the zRAM enable option out of the ovation build? Or is it something that the installer sniffs, and if you have more than 512 MB of RAM, it doesn't install? Our HD+'s are a strange animal, with some of our RAM dedicated to graphics, leaving us only 782 MB. I'd like it to think it had a little more.

I searched the file system for zram* and found a zram.ko file, FWIW.

When I try using Zram Settings to enable zRAM in CM11, it says "zRAM enabled," but running the command "free" in Terminal doesn't show any swap in use.
[Nook HD, HD+ Android Development] leapinlar:
Isn't there a setting in developer options to adjust how aggressive the background kill is? I know there is on older CM. Maybe that would make it less likely to kill your aviation app.
[Nook HD, HD+ Android Development] ajislav:
PMikeP: David Marble has some zram patches ready... http://review.cyanogenmod.org/#/q/owner:drmarble1%40gmail.com,n,z

Not sure if or when will be merged..
[Nook HD, HD+ Android Development] PMikeP:
There is a "Background process limit" under Apps in Developer Options on CM11. Mine is set to "standard."

I don't know how many "standard" is. The highest manual option is "at most 4."

I've set it manually to the max of 4 while composing this post and it seems that causes the app to shut down every time I move away from it.

So I'm back to thinking is that it's not the number of background apps running that's limiting me per se, but the RAM the aviation app is using. (121 MB.) It's fairly graphically intensive, as you can imagine, showing weather radar, lightning, clouds etc. on a high res chart.

---------- Post added at 04:52 AM ---------- Previous post was at 04:43 AM ----------

Wow - that's exactly what I'm hoping for! Thanks!
[Nook HD, HD+ Android Development] mr72:
Have any of you successfully used a stereo bluetooth device with an HD+ and CM11? I have a Sony SBH20B that works brilliantly with my phone (Samsung Rugby Pro) and my laptop (MacBook Air) but my HD+ simply does not see it. The HD+ does see my phone and my Roku and I can talk to it from my laptop, so I know BT is working in general.

Quick googling and scanning hits shows maybe CM11 has some A2DP & ACRCP bugs... My headset supports HFP v1.6, A2DP 1.2, AVRCP v1.4 and HSP v1.2.

Ideas?
[Nook HD, HD+ Android Development] rhyang:
I'm sure there are still some Bluetooth issues in cm11, but I've been using a stereo headset with it -- a kinivo bth240, and occasionally a homespot NFC stereo adapter (not sure of the model number, but it's the one on amazon). Things have gotten better.

Make sure your headphones can accommodate more than two pairings at a time. The kinivos can handle 5 and the home spot 8, but I also have a couple headsets that can only remember 2 at a time.
[Nook HD, HD+ Android Development] mr72:
The HD+ doesn't even see the headset as visible, when it is not paired with any other device. It's just like it totally can't see this type of BT device.
[Nook HD, HD+ Android Development] rhyang:
Googled your BT device manual -- it apparently can only remember at most two pairings (has both a single and dual mode, a little unusual). As far as visibility, remember to click "Search for devices" in the bluetooth settings if the HD+ doesn't see the device at first (there is an adjustable search timeout, 2 minutes default I think). Might be informative to get a logcat while pairing ?
[Nook HD, HD+ Android Development] rhyang:
I was curious about these, so I ran an unofficial build with them :

http://rhysw.com/CM11/cm-11-20140815-UNOFFICIAL-ovation.zip
http://rhysw.com/CM11/cm-11-20140815-UNOFFICIAL-ovation.zip.md5sum

Should be mostly the same as the 14-August nightly + a few commits. The tablet seems to work ok so far, though I'm not exactly sure what to look for in terms of performance changes.
[Nook HD, HD+ Android Development] mr72:
Yes of course I did the "search for devices", it fails to find it. There's no pairing, since it doesn't even SEE it. I'll take a look at logcat.

I haven't read the manual on the headset... are you suggesting that once it's paired with two devices it will never again be visible on BT?
[Nook HD, HD+ Android Development] drmarble:
I'm not sure what the zram really accomplishes. I've checked that it really does work. I just don't run so many apps that I need it. Having the zram allows running apps to be swapped to disk rather than being closed. This makes restarting them faster as they only need to be reloaded from disk rather than reopened.

Thanks for testing it. Let me know if it causes any problems. I will put verygreen on as a reviewer so he can merge it but I wanted others to test it first.
[Nook HD, HD+ Android Development] PMikeP:
Excellent! And thanks! (I wish I knew how to do this stuff myself - but at my age, it's not in my future.)

I did a dirty install of your unofficial ROM over a recent CM 11 nightly. (Nevertheless, it rebuild the apps on first boot. Running ART.)

zRAM is running, although the enable/disable option isn't found under "Performance" > "Memory Management" as it is in CM 10.2.1. (Nor can I select the amount of RAM to set aside.)

Running the command "free" in Terminal shows a Swap of 131,068 MB.

Interestingly, the app zRAM Settings doesn't see that zRAM is enabled. I haven't played with zRAM Settings yet to see if its VM settings affect this implementation of zRAM.

As I expected, what zRAM buys me is more "performance" in the sense that my aviation moving map doesn't have to restart as often. (And unlike when my browser shuts down, the moving map goes through an initialization process, asking me questions.)

I can kinda see zRAM working when I switch back to my aviation moving map, in that there's a slight pause for the map to start playing. Like coming out of standby in Windows.

KitKat still seems too aggressive in closing apps after a certain amount of unused time (that's my sense, anyway) - but zRAM helps me a lot. (Is there a way to adjust LMK minfree in KitKat?)

I'd assign myself even more RAM for zRAM if I could, for tuning purposes. I have 400 MB set on my Galaxy Tab 2, and I can run three aviation moving map apps with that in flight without restarts!

---------- Post added at 04:13 AM ---------- Previous post was at 04:08 AM ----------

Thanks for bringing zRAM to CM 11! I don't run that many apps either, but apparently the ones I run are high memory consumption. As you said, zRAM allows them to run without being closed. I would rather have the option of using zRAM and being able to disable it, then not having it all.

I've been running this unofficial build for a few hours now. Only one SOD so far, but that's not unusual and since I'm running a differently nightly now, I can't say that something else didn't cause the SOD.
[Nook HD, HD+ Android Development] procter:
Can we uppgrade the recovery with PhilZ? I'm on this CM11 emmc Rom.
[Nook HD, HD+ Android Development] Odenknight:
No sound on HDMI out latest nightly

[EDIT]

Disregard. After further testing, determined that there was a possible anomaly with the upgrade on that specific HD+ device. Re-flashed, and all is well. Keeping initial entry in case someone else runs into said anomaly.

Is anyone else having any sound output issues on the latest nightly? Video works great, just no audio.

thanks.
[Nook HD, HD+ Android Development] drmarble:
KitKat has zram build in. You just have to enable it in the kernel, fstab and init files. You cannot adjust it except by editing the files while building. I guess one could edit the fstab.ovation file and then reboot. That would give you the ability to increase or decrease the zram. Zram apps for pre KitKat no longer work with zram. I'll look into editing that file and post results if it works.

I have set it up with only 128M zram. Perhaps I should double it to 256M. The 128 is really more appropriate to a 512M device like the nook color. This should make it more useful. I will look around other cm devices and see how much zram they use.

Thanks for the feedback.

---------- Post added at 01:20 PM ---------- Previous post was at 12:34 PM ----------

I tried editing fstab.ovation. It doesn't work. It reloads it with the original version when rebooting. You can't change zram size at run time. Actually, you can open the installation zip file and edit the fstab.ovation file. Just change the amount of space allocated at the end of the last line (try doubling it). Then you can flash that modified zip file. I can't help you with doing this editing in windows. It is easy in linux. You don't want to unzip the file but just edit it in the zip file and save the changes. The zip file is just stored and not compressed and windows sometimes has trouble doing this.

I looked at other cm devices. Some of the amazon devices use the same 128M zram that we use. Encore (nook color) uses 100M but it only has 512M ram. I think we should stick with 128M.

I use the app Zram status from the play store to check on zram usage.
[Nook HD, HD+ Android Development] PMikeP:
I was just logging in to report that!

Okay, I'll hack around to see if I can modify the install zip. I'll use a Mint live distro if push comes to shove. (I think 7-zip will do it in Windows.)

For me, 256 MB swap will work better, especially since the HD+ is RAM challenged at 782 MB.

If I have success modifying the install file, I'll try 512 MB of swap too. In the Galaxy Tab 2 forum, the dev there says that zRAM compression is very fast. The implication seems to be that there's no down side to having too large a swap when it's implemented electronically. (As opposed to slow spinning hard drives.)

I'll let you know how a large swap plays.

Thanks again!

---------- Post added at 09:19 PM ---------- Previous post was at 08:48 PM ----------

Boy, I hate to show my ignorance - I upzipped the installation file using 7-zip but I cannot find an fstab file.

There's something in a context file about fstab being in a build file, but I can't find the build file either.

Please, what am I missing?
[Nook HD, HD+ Android Development] leapinlar:
The fstab.ovation file is not in the zip, it is in the boot files. That is why it changes on each boot. You can either change the boot file (not easy) or you might try a script file to dynamically modify it at boot.
[Nook HD, HD+ Android Development] drmarble:
You are right. It is not in the zip file. The fstab.ovation file is in the boot.img. It does have to be edited at compile time. I wasn't thinking straight when I suggested editing the zip. Opening up the boot.img, editing and repacking sounds too hard to me. I'd rather just rebuild. I'll do a build with 256M zram and put it somewhere. I am not sure just what size to use. As I said, the amazon cm devices use 128M like my patch. I couldn't find other devices using it but I didn't look very hard. I expect there would be little demand for 512M. I can build with that size too.

Sorry to have sown disinformation. Thanks for the correction.
[Nook HD, HD+ Android Development] drmarble:
I built three roms with different Zram sizes, 128, 256 and 512, and uploaded them to my box.com account. I am testing the 512M one now.

Test them out and let us know how they work and what the best size is. I can change the size for the patch I have submitted to cm. I just don't know what the best size is.

These roms should be easy to flash directly over any cm-11 nightly. No need to wipe or anything like that. It might be hard to flash back to a previous milestone release.

128M: https://app.box.com/s/a34tq556jdzmm9gkb60c MD5sum: 2bd21b53fe1b82a3e1a47ef4a86c5167

256M: https://app.box.com/s/ypo4drg38xurlfe7smif MD5sum: 89e29d9c13cd195dbec1dff29c9b44f8

512M: https://app.box.com/s/foilxf9d9sym7tm2cxud MD5sum: e6a2400af87215b2d1ccc560d2d3fc4c

I hope I don't hit my box.com upload limit with these like I did with my touch fuzz kernels. If anyone wants to mirror these, feel free.
[Nook HD, HD+ Android Development] PMikeP:
Thanks again!

I too downloaded the 512MB one and am testing it now.

So far, so good. I can run about 10 "tabs" in Lucid Browser (about 286 MB in RAM) and run my aviation app and not lose either to a forced shut down.

Times might be just a tad slower on app launch (but it takes about six seconds anyway with ART to launch my aviation map), but once launched, everything is fine.

Since you consider this swap size as the worst case, please, is there some app or in-house command I should run that monitors the OS for arcane performance info (page faults, etc.) that would give you the hard data you need to make a final decision on swap size?

For example, I'm noticing that even tho the total swap size is 512 MB, I only use about 60 MB of that. ("Free" command in Terminal.) I suspect that's due to a "swapiness" setting. Is there a way that I can monitor swap usage to report to you?

What, specifically, should I be looking for that would indicate the swap is too big? (How would I know if all the extra swapping required more use of TRIM?)
[Nook HD, HD+ Android Development] andtron:
Thanks for the zram builds by drmarble.

After spending few hours using the 256 version, I have decided it is not for me.

Overall, I personally feel the response is pretty sluggish. I mostly use my device for web browsing, downloading file

, ebook reading. Most app startups are slow, e.g. using fxmanager to copy folders, occasionally it would pause for 5-10 seconds before continue. These situations don't happen with other regular builds.

Pmike's applications are different, so your mileage might differ.

Thanks again.
[Nook HD, HD+ Android Development] verygreen:
Well, I am experiencing severe lack of time for quite a while as you might have noticed.

None of my Nook plans really got any time too :(

The most I can do ATM is just a rebuild of current CM11 repo, I guess:

It probably has way too many changes since January to be able to list them here.

cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip

I am holding high hopes on sluo's work for unified sdcard/emmc builds for nooks so that people would be able to use a single build in both capacities.
[Nook HD, HD+ Android Development] razholio:
You guys sure it works that way? I read up on zram a while back and it was described as creating a compressed ram disk (hence the boot time config for size) and then putting swap on that. The eMMC is not used for swap at all. The result is more ram at the expense of speed as you have the zlib hit as well as paging to the swap. The performance hit on paging to eMMC would be intolerable...
[Nook HD, HD+ Android Development] PMikeP:
Yes, I believe you're correct. Sloppy terminology on my part. I tend to call all internal memory "eMMC," but that's incorrect. eMMC is the non-volatile flash storage (which we call ROM on the Nook HD home page in this forum?) and RAM is volatile RAM.
[Nook HD, HD+ Android Development] Yegort:
I gotta say verygreen, the nook is the stablest device I have running cm11. What you have done is incredible! It actually has been stable for months and I've been running ART too.

P.s. I hope we get android L :P
[Nook HD, HD+ Android Development] PMikeP:
I've settled at 128 MB zRAM

I started out trying 512 MB of zRAM swap, but never got more than 10% usage of the swap space. (per zram status.)

It must be something hard coded in KitKat, that the memory manager just doesn't want to keep apps in memory. (Or maybe something the way ART works.)

So I dropped down to 128 MB swap. The most usage I've seen there is 60% usage. And that's after tweaking

vm.min_free_kbtyes to 2500 and

vm.oom_kill_allocating_task = 1

with sysctl edit.

Interestingly, the most compression I've seen is approx 40%.

I'm not smart enough to do the math, but if only 50% of the 128MB is used (64 MB), and only 50% compression at that (implies 128 MB total), does that mean that we're better off just letting the 128 MB of RAM be RAM?
[Nook HD, HD+ Android Development] razholio:
It's been far too long for me to remember specifics, but that seemed to be the conclusion of folks looking into this back in the 10.1 or 10.2 days.
[Nook HD, HD+ Android Development] YevOmega:
Can someone please run benchmarks for Verygreen's latest build right after booting? TIA!
[Nook HD, HD+ Android Development] mmoalem:
Hi all. I'm running succulent July rom.was wondering if it's worth updating to recent nighties... Anyone who can shed some light?

Cheers
[Nook HD, HD+ Android Development] Yegort:
using todays nighlty...

ART

antutu:13864

quadrant:4005

Dalvik

antutu:13847

quadrant:3013

these scores are best of 3 runs