yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] PeteInSequim:
CM-12.1 is approximating a dead end since there is much more interest in CM-13 (Marshmallow). I have not re-written the instructions for Marshmallow, but did add a few hints at the beginning of the first post in this topic. Using the mentioned tools from [MENTION=5672278]belfastraven[/MENTION] it is now easy to make a bootable microSD card that boots directly to TWRP. The procedure is otherwise the same as described for CM-12.1 except with different download files. So now the whole Marshmallow installation can be done in only 4 easy steps instead of the previous 5.

And remember, the instructions are based on the unofficial releases given to us by [MENTION=4473900]amaces[/MENTION], not any Nook-specific releases from Cyanogenmod proper.

Hundreds of apps? Maybe you should divide the bunch among several Nooks; they're really inexpensive on eBay these days.
[Nook HD, HD+ Android Development] lmacmil:
I just flashed CM13 on my HD using your instructions, Belfastraven's recovery and the latest unofficial releases from Amaces. It went smoothly. It was my first experience with TWRP and I liked it. Going to do my wife's HD+ next. Hers is still on 10.2.1 and is getting pretty sluggish.
[Nook HD, HD+ Android Development] Harvick_29:
I flashed 12.1 a few days ago. Seems to be working fine except for the fact I can't power off. If I select power off it'll just reboot. Any suggestions???
[Nook HD, HD+ Android Development] PeteInSequim:
This is a very common problem that has been reported for Nooks and other devices. It even happens on my Intel NUC5i5RYH desktop. For Nooks, it has been reported for Lollipop, Marshmallow, and also earlier versions.

There are at least two bright people investigating this, and I have it on good recent authority that a fix is near. Meanwhile, when you turn off your Nook be prepared to press and hold the power button if an unexpected restart occurs. Sometimes you just have to choke it to death.
[Nook HD, HD+ Android Development] Harvick_29:
interesting! thanks for the reply!
[Nook HD, HD+ Android Development] rjolbrich:
Memory Management for CM12.1

Hello,

I'm a little behind the times as I just installed cm 12.1 on my Nook HD+. I'm running into

available RAM problems with my Nook HD+.

First, I've tried reducing the number of apps that start at boot, either through the Boot Manager app

or by turning off "run at startup" in the app's info. Boot Manager does not list all of my apps, and

turning off "run at startup" is not present as an option in many app info's.

Also, many apps seem to magically reclaim RAM after being shut down by a task manager.

I have a few questions.

What are the best apps available for boot management? Are there better ones than Boot Manager?

Does the RAM reclaiming happen irregardless of the task killer?

What are the memory management "secrets" of Lollipop (or Marshmallow)?

Do I have to live with fewer apps on my Nook HD+?

Is there a good source that describes memory management for Android?

Thanks
[Nook HD, HD+ Android Development] rjolbrich:
Greenify is the solution

THE Solution: Greenify. Amazingly simple hibernation app.

Who needs freeze apps.

Thank you
[Nook HD, HD+ Android Development] SamiRobo:
How to download?

please tell me how to download CM12.1 Rom, I can't find any link or file in thread or Shared folder, please help me.
[Nook HD, HD+ Android Development] digixmax:
See https://notredame.app.box.com/s/26a...e&sortDirection=desc&pageSize=20&pageNumber=5.
[Nook HD, HD+ Android Development] adamj02090830:
Please check the link's access level. I can't access it.
[Nook HD, HD+ Android Development] starbright_:
A minor issue observed in 0502:

The "Energy Save" button in upper bar just does nothing (as it seems). At least I can't observe same behaviour as under Settings/Battery/Save Energy.

(I do have non-english version, so sorry if translation is not correct)
[Nook HD, HD+ Android Development] jdjohn:
Anyone else having issues with APM? 'Power Off' seems to do a reboot every time for me.

This is coming along great, though!
[Nook HD, HD+ Android Development] extrem0:
This issue was reported many times. I also don't know if it was supposed to be fixed, but I think it's considered a minor issue.
[Nook HD, HD+ Android Development] techdudepro:
That has happened to me many times, even with CM 11. It hasn't done it as much since the 0502 CM 12.1(.1) build...
[Nook HD, HD+ Android Development] Jon Lee:
I think you are onto something with that patch. I wouldn't be too hasty in abandoning it.

I added it to the "Yellow Kernel", and it fixed my graphics glitches as well.

I also would have a reboot every time the display went to sleep/suspended.

To fix this I removed the code from the suspend side, and altered the placement in the enable side to be after the "if" statement, like so:

static int omap_dss_driver_enable(struct omap_dss_device *dssdev)
{
int r;

r = dssdev->driver->enable_orig(dssdev);
if (!r && dssdev->state == OMAP_DSS_DISPLAY_ACTIVE)
blocking_notifier_call_chain(&dssdev->state_notifiers,
OMAP_DSS_DISPLAY_ACTIVE, dssdev);
omap_dss_request_high_bandwidth(&dssdev->dev);
return r;
}

After that, It's working very well here. Just wanted to say thanks for finding it.
[Nook HD, HD+ Android Development] TBueno:
Man, you guys are coding ninjas. You seem close to not just a stable CM 12.1 port to our devices but also to fixing their chronical reboot trigger-happiness.

Thank you very much.
[Nook HD, HD+ Android Development] amaces:
You mean the "Power Save" tile? You're saying that it switches successfully in Settings (e.g., orange bars), but not from the notification shade? If that's the case, definitely on CM12, which means it should be fixed quickly.

You know, I've been telling people that it never happened to me, yet it just did for the first time today. I'm going to chalk it up to CM12 changes ;) I will check.

Thanks for the heads up; pretty interesting that the order should make such a difference in this case. The old-style omap_dss_{request,reset}_bandwidth calls that were removed in commit dec6f32 (OMAPDSS: DSS: Relax L3 bus bandwidth constraint), were also placed before, and after, respectively. Oh well, so many little weird things with the OMAP 3.0 kernel that nothing is surprising anymore…

I'm really glad that it fixed your issues, though. No reboots for now, but the flickers are still present on CM12 after implementing your change. You're using [MENTION=3654172]verygreen[/MENTION]'s older tree on CM10.1, right? The .72 kernel has many OMAP changes, plus the switch to common HWC, PVR, etc. in hardware/ti/omap4 entailed significant changes as well. Maybe CM10 is less taxing with the overlays, so forcing HIGH_RES_TPUT every time completely avoids the underflows in your case.

I notice that Lollipop really tries to move everything to the HW composer; I never see EGL overlays anymore, which I guess would be great if the hardware would be a bit more capable. I could live with less than 32 bpp, even RGB565 would probably be OK, but couldn't figure out where to make the switch globally. But yeah, increasing/optimizing DSS bandwidth is probably the general direction to hammer.
[Nook HD, HD+ Android Development] Jon Lee:
I had very little graphical glitching anyway, mainly in the keyboard. That's sort of what kept me from keeping CM11, except I think that there the graphics issue would cause a hang (no last_kmsg, so kinda hard to diagnose).

Yes, I started out with an early version of Verygreen's kernel. It seemed to be the least "adulterated" (which can't be said anymore). Would love a 3.4... I think you got further with Hashcode's omap-p-android-3.4 branch than I did.
[Nook HD, HD+ Android Development] steavis00:
CM12 505 Rev - Power Management

The unlock screen seems to work OK. However, power mgmt is not good. Sleeping for 12 hours goes from 100% to 29% on battery. On 502 it went from 100% to 98% in same time.

So I guess some kind of background task running, but I forgot to look at battery use under settings before I re-installed 502 which still has waking from lock to unlock (as in needs a reboot) issues.

Thanks for spending time on this.
[Nook HD, HD+ Android Development] twiztid_:
Nevermind. Didn't see the post was about 05/05.
[Nook HD, HD+ Android Development] amaces:
Wait, you mean power management with that May 5th build in the experimental folder? If so, it's probably because of frequent self reboots in those twelve hours :(
[Nook HD, HD+ Android Development] steavis00:
I guess it must be. I didn't look at the battery use before I re-installed 502 (which I should've) but that makes sense.

The 502 build works fine for power use. Just that wake-up from lock requires a reboot.
[Nook HD, HD+ Android Development] amaces:
Wanna try the build currently in the experimental folder?
[Nook HD, HD+ Android Development] steavis00:
Sure, I appreciate what you're doing and anything I can do to help. I'll keep 502 as my golden for now.

---------- Post added at 09:54 PM ---------- Previous post was at 09:40 PM ----------

Sorry, I guess I should've said I'll keep 502 as my backup for now.:)http://cdn3.xda-developers.com/images/smilies/smile.gif
[Nook HD, HD+ Android Development] king200:
I'm running the 0508Exp. Booted into system with no glitches. No reboots and battery drain doesn't seem unusual.

First impression:

Better than 0502 build.

Screen is responsive to touch and animation effects are fast and smooth. I'm guessing that ram is being used better.

Screen flicker is not a problem that I've had.
[Nook HD, HD+ Android Development] steavis00:
508 Kernell

First pass - Lock/Unlock is OK. Battery drain and charging seems OK.

Will update battery drain and anything else later.

Thank you again for doing this.
[Nook HD, HD+ Android Development] ekimookh:
Hi guys

Any one running freely on this? Freely freezes my ovation just after launch. Been happening on every build including the 08 experimental build.

Thanks for keeping "the tablet that could" running
[Nook HD, HD+ Android Development] vaughnmr:
Runs fine on mine with the 02 build. I am having problems with deep sleep sometimes causing display corruption when waking up, though, and have to reboot.
[Nook HD, HD+ Android Development] ekimookh:
oh bugger ..... I guess it's just me
[Nook HD, HD+ Android Development] king200:
Are the Ovateion Experimental 0505 and 0510 build the same?
[Nook HD, HD+ Android Development] amaces:
Similar, but not identical; plenty of interesting changes in upstream CM, plus a couple of small changes in my local/device-specific repos. See the repostamp/repolist text files in the root of that Box folder.
[Nook HD, HD+ Android Development] belfastraven:
I'm running the 5/10 hummingbird build on two different hd's and both are running well. The 16G nook always has screen flashes when installing a new rom, but settles down after a few minutes and then gives no other problems.

In settings, sound, the notification sound slider is back (was missing from the last couple of builds) . Couldn't try hangouts or casting..

Subjectively, the new rom seems smoother.

thanks again, amaces.
[Nook HD, HD+ Android Development] steavis00:
508 Update - Batt drain OK

It holds the charge in sleep mode OK, so I think you have it fixed. Thank you.
[Nook HD, HD+ Android Development] pastordl:
First try.

Just recently purchased a recertified Nook HD+. Started with CM 11 and very pleased. Tried CM12.1 yesterday and once I found the developer root choice was able to run most apps with little or no problem. Only thing that won't run on 12.1 yet is the Xposed framework, still only on 12.0. Other than that a great build able to get 1080p streaming from various sources and all ran flawlessly. Hopefully you'll be able to get this to official status soon. I still have my Nook Color I got 4 years ago as a daily work horse, but for fine viewing and speed the HD+ is my tab of choice.
[Nook HD, HD+ Android Development] king200:
I haven't done the Nook Color but have done HD+ with CM and emmc early when Verygreen started it. It's incredible that the list of developers, not least of which is Amaces, have kept this device at the cutting edge of Android. If more people were aware, we'd be having more owners and downloaders of this rom.

I even learned a purpose of the hanging hole. Stick a chopstick through and it is a great stand at right height and viewing angle. https://bookclubs.barnesandnoble.com/thread/9236

Xposed for Lollipop http://xdaforums.com/showthread.php?t=3034811 should run. The list of working modules is limited https://docs.google.com/spreadsheets/d/tzOETyXeiUT5JSHgmL1NxLg/htmlview#gid=0 if you try, be able to disable from Recovery beforehand.
[Nook HD, HD+ Android Development] pastordl:
I did find a non supported Xposed zip for 12.1 (5.1) here: http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

It seems to work fine. A few Modules don't work yet but this makes CM 12.1 a full winner for me.
[Nook HD, HD+ Android Development] FirePsych:
--nevermind--

Nook HD+ doesn't have GPS. Duh!
[Nook HD, HD+ Android Development] steavis00:
510 Issue

Well, spoke a little too soon. Am getting the black-out after I do a screen unlock (right after I slide up). A reboot fixes it until it goes to sleep again. Charging is OK.

Am trying a couple of things to see if it makes a diff. Like leaving an open app and let it sleep.
[Nook HD, HD+ Android Development] dbrickg:
Just installed the 5/10 zip. Dirty flashed on top of 11.0. Cleared cache and dalvik cache. I haven't noticed a crash right after screen unlock. Here's my notes so far: seems a bit slower than 11.0. And I've had a few crashes, here and there. HDMI out seems to work sometimes, sometimes doesn't. Chromecast ... hmm, not so much. Maps doesn't find my location. But I'm happy enough with it that I'll keep running it for awhile, see if there are any other good or bad things to note. Thanks all for all the work.
[Nook HD, HD+ Android Development] sipart:
Regarding issues after screen unlock. This may not be practical for you but I disabled the lock screen and I don't get these issues (still get some other screen issues but this is a alpha/beta release). Cheers
[Nook HD, HD+ Android Development] McGiles:
Great job amaces - everything going fine for me except google voice commands now either don't work at all and I end up typing or it works sporadically. John
[Nook HD, HD+ Android Development] amaces:
Testing UKSM

Today's builds are a bit more experimental; UKSM replaces KSM, and is enabled by default. The configuration interface is pretty similar to KSM; this page describes how to tune the UKSM parameters, or disable it altogether. We'll see if memory management is even marginally improved after this.
[Nook HD, HD+ Android Development] DarkStarr:
Dunno how it compares to earlier builds but it runs very smoothly. I came of of KK which was lagging like crazy, did a wipe then wiped the system partition for good measure. Works great. Very nice.
[Nook HD, HD+ Android Development] belfastraven:
The 5/17 is working fine on my nook HD's, but I am not sure what a good test would be to establish whether memory management is improved. I have run with the uksm enabled and un-enabled but don't "feel" any difference. I will occasionally have my NYT app freeze and have to soft reboot to fix what I assume is a memory issue, but wonder if there is some benchmark that could be run after using a set set of apps for a period of time. Would the multi-tasking test from Antutu be of any use?

Any ideas?
[Nook HD, HD+ Android Development] pastordl:
The 5/17 experimental with uksm does seem smoother and more stable.
[Nook HD, HD+ Android Development] nicko07:
I have tried to keep abreast of development and comments on Amaces thread and also Hashcode's and would like to add some feedback, I have installed and fully wiped a few times now, lately using Amaces 100515 and base-line gaps. In common with others, I initially experienced unexpected screen flashing and sudden re-boots. I disabled HW Overlays and this helped, but my Nook became sluggish. I noticed that when creating a folder for icons and trying to rename with the keyboard, the screen would flash wildly and then the Nook would re-boot. As an experiment, I randomly downloaded an alternative keyboard, in my case Fleksy (I have no association) and replaced the default in settings. I did not disable HW Overlays, just left everything as normal. Since then and for the past 48 hours, I have not had one screen problem or re-boot and the Nook is consistently fast. I did have problems with the default lock screen in that it looped twice for unlocking and I replaced this with another pin lock app, and that problem has gone. I still have the minor and documented re-boot on power-off problem, but not a big issue. I mention all this as, in may case, the default keyboard appeared to be the problem source that somehow affected the screen, triggered sudden re-boots and slowed performance. I’ve read that disabling HW Overlays is a solution for some, but not a preference and I now have no need to do so. I run quite a few movie and video apps, but not games. Might be useful or not and I just wanted to mention. I am really enjoying my Nook now and please keep up the excellent work!
[Nook HD, HD+ Android Development] steavis00:
517 Build Issues

Thank you again for your efforts. Two items:

1) Bluetooth takes forever to pair if at all

2) Netflix works but fast forward doesn't. YouTube is fine.

Didn't notice if these happened on earlier versions, sorry.
[Nook HD, HD+ Android Development] amaces:
When I do dumpsys meminfo, my ovation's RAM status is rarely "normal" during normal use; it usually sits at "low", and often "critical". At that point, SwiftKey keeps reloading, and Chrome is barely usable, so I was looking for an improved KSM-like solution that would reclaim some of the 100-150 MB lost RAM, without killing the CPU. I was hoping that UKSM is that solution, alas I only see drawbacks, and no apparent benefit after a couple of days of use. I didn't give up on the idea, especially that I found a third iteration of this feature in the form of PKSM. I will leave [UP]KSM compiled in, but disabled by default, so people can turn it on (and tune it) using the sysfs interface, like KSM worked before now.

Yep, replacing the default AOSP/Google Keyboard is my preferred solution as well (for now, at least). It's a shame as it really is the better keyboard when it works. Anyway, we've discussed different options on the previous CM12.0 thread, but it's still very puzzling there should be these differences. When I looked into the kind of HW acceleration and number of overlays used by various keyboards (dumpsys SurfaceFlinger), there didn't seem to be any major differences, unless they force different color depths in HWC (e.g., 8888 vs. 565, etc). Either way, the display driver should not fail in these horrible ways just because we're requesting more bandwidth. The DSS system in the OMAP 3.0 kernel must be flawed in a major way that nobody could fix completely for three years now :( Everyone using KK/LP on the OMAP44xx platform (and their grandma) has been rooting for a 3.4 kernel…

Those sound like CM12.1 issues, and it's been a while since I checked those features, but you could try the current ovation build in the experimental folder, which I like better than the weekend one.
[Nook HD, HD+ Android Development] steavis00:
519 Update

Works great. Netflix is OK and Bluetooth pairs.

Thanks again.
[Nook HD, HD+ Android Development] amaces:
Glad the resync helped; I did notice a flood of commits Sunday afternoon, just I had started building the weekend images. Since those were not the greatest builds, and I was still working on adding PKSM (ported from a patch for K3.6), I've uploaded new experimental ZIPs. To test out if PKSM does better with memory pressure and CPU, you'd need to enable it with echo 1 > /sys/kernel/mm/pksm/run. In the future, depending on feedback, we may go back to UKSM, or legacy KSM, but always disabled by default.
[General Questions and Answers] adamgraver:
Hi. Does anyone know of a way of including H+ UI support for the stock 4.3 ROM? Presently, it just shows as "H" all the time. Thanks!
[Galaxy S6 Edge Accessories] iconeo:
Does anyone have any suggestions for a waterproof case?

Thanks.
[Galaxy S6 Edge Accessories] beda_boy:
f they become available, I would look for a Lifeproof or Seidio

I've had Seidio Obex before for my S3 and it really worked great, submersible up to 6ft :)
[Galaxy S6 Edge Accessories] nappent:
No idea how good but here is one...

Emarket Durable Shockproof Waterproof Cover Case Pouch For Samsung Galaxy S6 Edge G9250 Green Color by emarket http://www.amazon.com/dp/B00UJ8JWJ8/ref=cm_sw_r_udp_awd_Xlmkvb0692J33
[Galaxy S6 Edge Accessories] kyoungs3:
6 meters for 3 hours? $10.99? Yeah, I'm probably going to pass testing that one out, haha. Hopefully lifeproof comes out with something for the edge. I really don't think it should be hard for then to create a screen protector-less version (nüd?) since it's just a rubber o ring pressed against the glass (the curve shouldn't be hard to account for), and they have the whole reputation based on reliability thing going for them?
[Galaxy S6 Edge Accessories] Lisayeang:
Eonfine waterproof case or Comeproof
[Galaxy S6 Edge Accessories] chrissmith2016:
I and my girl friend are those accustomed to using cell phone case adequately protecting devices from normal scratches, dents and dings.

Googling how to pick a phone case preferred,I found a pretty useful blog at blog.onu-mall filled with tons of useful publications including how to pick the quality phone case, tracking the blog,i was surprised by a online shop with huge collections of various affordable amazing Samsung galaxy S6 edge case at onu-mall.com/catalog/samsung-accessories/galaxy-s6-edge-case-cover/, i bought a really unique LOVEMEI 3 In 1 pattern aluminum and silicone shockproof snowproof waterproof case for Samsung Galaxy S6 Edge Plus at onu-mall.com/lovemei-3-in-1-pattern-aluminum-and-silicone-shockproof-snowproof-waterproof-case-for-samsung-galaxy-s6-edge-plus-white.html for my gf,she is so satisfied with the stylish, lightweight aluminum + silicone + tempered glass case with inner tempered glass inside for powerful waterproof function and with card slots to put your cash and cards in and with flip stand to watch movies etc conveniently,i am so happy making she surprising and would like to share the online store named ONU-MALL ONLINE STORE
[T-Mobile Samsung Galaxy S6] libuser:
I am pretty confident that is the issue but I thought I should check with you all first.

Seems that Verizon's unlocked SG6 does not support band 4 which is the 4g band of tmobile, and naturally I cannot get 4g. Everything else works flawlessly but I cannot get 4g at all. Using my SG5 I get 4g no problem but not with the SG6.

Can anyone confirm that this is the case before I return it to Verizon? I just got it today and thought it was an amazing piece of technology but I might have to return it now...

tia
[T-Mobile Samsung Galaxy S6] wund3rground:
Why didn't you just get a T-Mobile version? Try going into the service menu *#2263# and go band selection and see if you can do it there.
[T-Mobile Samsung Galaxy S6] mocsab:
I found this article that may help explain why Verizon's phone will not work on TMobile Network;

http://www.pcmag.com/article2/0,2817,2407896,00.asp

For what it's worth, I did a GOOGLE search and found this and several other articles about the difference between CDMA and GSM phones..(from what i understand, TMOBILE is GSM and Verizon and SPrint use CDMA)

I do hope you figure somehting out... GOOD LUCK
[T-Mobile Samsung Galaxy S6] jblazea50:
Were you able to get LTE/4G on T-Mobile using Verizon S6? From the specs list, it says Verizon's S6 support band 13 and band 4. Band 4 is what T-Mobile uses for LTE.

I'm curious to find out because I am looking to purchase the Verizon S6 and use it on T-Mobile.

TIA
[T-Mobile Samsung Galaxy S6] Synyster06Gates:
T-Mobile also uses band 2 LTE in some areas- something worth looking at.
[Verizon Samsung Galaxy S6] kregstrong:
Anyone know if there will be a way to get the google dialer with phone number lookup on the gs6??