yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] andtron:
I tried the 1029 6.0 and have no luck.

It booted looping at the android animation for over 45 minutes. And if I tried to boot it into recovery, it will struck at the twr main page and then the device would just reboot itself. Luckily I have an sd card to restore.
[Nook HD, HD+ Android Development] Monfro:
On Ovation it is the same: 10/29 is far better than 11/01.

Graphics problems on 11/01: the screen shows some green lines sometimes and it feels laggier.

Maybe is better we speak of Marshmallow in the other thread.
[Nook HD, HD+ Android Development] amaces:
Sunsetting CM12

Clearly, Marshmallow is the focus now ;) but I'm trying to keep track of Lollipop/CM12.1 issues here, at least till the 6.0 builds are usable enough. Otherwise, all MM-related replies will happen on the new thread, soonish.

Many potential reasons, but most likely connected to memory management. As of now, the composer code is pretty much the same as in CM11, ditto the proprietary blobs, while memory management is most heavily changed in the current CM12.1 kernels. If things are the same on Marshmallow, there's chance (albeit small) I can look into it once porting settles down.

It needs coarse location information, which we have, but also some sort of kernel/GPU interface to control the perceived color temperature of the rendered images, and that no OMAP4 device has or ever will.

Nothing missing, but SELinux was switched to Enforcing, and you're the first one mentioning this issue. While the fix is simple, it's problematic to apply it now since I switched to the Marshmallow codebase (not enough space to keep LP around). It works on the early MM builds because those are Permissive for now.

No need to track down another copy of USBHostSwitcher; it was disabled in the early CM12.0 builds, but I've been baking it in for a while now.

Glad you're around, verygreen; yup, his is definitely a SELinux denial, discovered only now.

You certainly can (look into the wm size/density commands), but I doubt it will change things drastically. The lags are usually on the order of a few hundred milliseconds, and if major ones happen, they shouldn't last more than a few seconds.

Once you enable USB host mode, NTFS should be fine in CM12, I think. Basically, there are two separate issues: USB mode, and filesystem support. Unfortunately, it seems that host mode cannot be enabled on the current CM12 builds for reasons discussed above. On the experimental Marshmallow builds, it's the opposite: USBHostSwitcher should work, but NTFS is probably unsupported on AOSP…

It's a complicated issue that we discussed a few times on the thread, and the fact that battery life fluctuates monthly seems to point to upstream CM, although I also made kernel changes recently. At the very least, you'd need to look at deep sleep statistics (with Trickster MOD, for example); based on your use, it should be above 85-90%. If that's much worse, use something like BetterBatteryStats to collect more in-depth battery, wakelock statistics; it may very well be an app behaving badly. Provided that you make a /data backup, an easy way to determine whether these ROMs or user apps are responsible is to do a clean install, and choose a new device profile in the SetupWizard (if you use GApps, that is). Of course, if the battery has aged or degraded, nothing will help.
[Nook HD, HD+ Android Development] sasmith-129:
Thanks amaces. As long as you're still tracking 12.1 issues, I'd like to note a video issue I noticed in the 10/18 build that wasn't present in 10/12. I mentioned it in post 1215 but, in summary, the game Temple Run 2 doesn't render graphics properly with 10/18.

It's difficult to characterize the issue as the display is constantly changing. I initially thought portions of the screen were rendered in the wrong place but it might be that not all of the screen updates are occurring (i.e. still seeing portions of the last "scene"). It's significant enough of an issue to make the game unplayable.

Thanks!
[Nook HD, HD+ Android Development] digixmax:
I am having problems with two apps on 12.1:

My Bidder Auction, which just crashes/closes upon start-up.

Hulu, which would play the commercial preceding a TV episode, then closes right afterward.
[Nook HD, HD+ Android Development] digixmax:
MyBidderAuction works again after the app's newest update today.

Still no dice on Hulu.
[Nook HD, HD+ Android Development] amaces:
Yeah, there was no reason for a regular app to suddenly stop working; AOSP 5.1 had some changes in recent releases, which forced Xposed to adapt as well. About Hulu, I'm not sure that it ever worked on our CM12 builds. I've had issues with HBO GO and PBS Video as well, so it may be a DRM issue, or something related to our codec support again.

No changes that would impact EGL rendering in recent memory… The fact that it doesn't force close, but keeps attempting to render frames, seems to point to an app bug. As above, it's possible that game doesn't play well with the changes made in the latter iterations of AOSP 5.1.1, but without actual logs, it's hard to tell. Did you find reports of similar bugs on other devices? Truthfully, if it's something that I can fix, it'll be on Marshmallow. It's fairly close to usable, and I don't have enough space to resurrect the CM12.1 repositories.
[Nook HD, HD+ Android Development] JohnnyMcG:
the downloads you provided

will not work at all i dont know why i tried on multiple web browsers and still failed download thanks in advance to op if you post different links
[Nook HD, HD+ Android Development] dbrickg:
I'm assuming you mean the notredame.app.box.com links? Very weird. I just tried downloading one of the files, and got it without any problem. I'm also assuming you mean the the download didn't work, not that the ROM wouldn't install
[Nook HD, HD+ Android Development] PeteInSequim:
Was it the open-gapps link that troubled you? Try http://opengapps.org/ and pick the one you want, such as ARM - 5.1 - pico. I think all the other links are still good.

Please let us all know how it goes for you.
[Nook HD, HD+ Android Development] MrPuddington:
Ready for daily use?

Some time ago I wondered whether CM12.1 is ready for daily use on the Nook HD+, so I installed it. Generally the experience was ok - there are some minor problems and annoyances. It is impressive to see such a recent version with the material look on such old hardware.

That being said, there is some stutter when switching tasks (1GB of RAM is really a bit low for Lollipop), and for some reason Minecraft is behaving strangely at times. So I am back to the latest CM11 nightly, which is not as pretty, but very solid.

And it seems that CM12.1 development has stopped, so I should try CM13 now?
[Nook HD, HD+ Android Development] Tschumi:
Marsmallow is even less stable at this point. The memory management is not up to par with the latest 12.1, even the launcher redraws every time I minimize an app. I'd say give 12.1 a try and imagine 13 being worse in every aspect.
[Nook HD, HD+ Android Development] phpmoli:
cannot set brightness - possible help to a fix?

Hello there,

I'm a first time commenter, hope i do it right.

My grandma has Nook HD+ which she used with an android 4.2 cyanogenmod rom from the past. So I updated it to cm-12.1-20151018-UNOFFICIAL-ovation.zip, but in the end, i got the same error some guy got in this forum: you cannot set the brightness, it was constantly at max (or near max, i would say).

I read here that it is the installed gapps and not the rom which causes this bug. I dont know which gapps i installed first (deleted it since). Anyway, i gave it a try, and reflashed the tablet. This time i flashed the OpenGApps, and in the first-bootup-wizard, i set up my wifi, logged in to google, and selected to restore my apps from google cloud. In the end i didnt wait until the restore process finished, and tried to set the brightness, it didnt work with OpenGApps too!

I was confident in what you said, that the rom does not have this bug, so i reflashed it again, this time without any gapps. The brightness was working ok. So how come, OpenGApps is bugged too? I know now how, because next time i reflashed the rom with OpenGApps but without connecting to a wifi, to google, to the cloud. The google cloud restore process downloaded that bugged setting and reapplied it to OpenGApps too!

I hope this info helps finding the bugged setting, and somehow make it fix in the rom itself regardless of the gapps installed.

TL;DR

if you installed a wrong gapps package and your brightness isnt working, restoring your apps and settings from the cloud will redownload and apply that unknown bugged setting to your flawless gapps too!
[Nook HD, HD+ Android Development] ajislav:
Did you format system before each flash? If not, try that.
[Nook HD, HD+ Android Development] phpmoli:
Hello ajislav, are you asking this from me? There was no quote, so i'm not sure.

If yes: of course i wiped everything before each flash. But i dont understand the question, as the whole story of my comment was how to flash the

right

way. But i am not a native english speaker, so sorry if i cant express myself.
[Nook HD, HD+ Android Development] Tschumi:
Problem booting up

It seems my battery run out and the device shut off. I connected it to the charger and after a while it started bootlooping, after being extremely sluggy/slow to reache the android logo.

Going into recovery I wiped everything but I had trouble formating Cache, resulting in the messege: E:/sbin/e2fsck -fp /dev/block/mmcblk0p9 - Process ended with error 4

From what I understand my cache might be corrupted. Any ideas if there is anything I can do to fix it?
[Nook HD, HD+ Android Development] ajislav:
Hi phpmoli,

Yes I was responding to your post.

It was just a hypothesis that the problematic setting was actually on your /system partition and not in the cloud.

Your experience indicates there is indeed something wrong that's stored in the cloud. Could it be a user app setting or do you think it is related to a system app?
[Nook HD, HD+ Android Development] pavlos46:
Ελα καλημέρα,

This a problem that I also have in my data partition, when I try to format from the twrp main page, nevertheless you could try going into advanced selecting cache and then change type. Even if you select the same type as the one you are already on TWRP will correctly format this partition and allow you to load rom. If you try to format from wipe main page again it will crash again, so no real solution just a workaround.

Pavlos
[Nook HD, HD+ Android Development] Tschumi:
Καλημέρα στα Γιάννενα και ευχαριστώ.

Formated everything (cache, system, data) with the way you proposed and installed the latest nightly. Still lags for a minute in the cyanoboot logo and bootloops after a few minutes being stuck in the android smiley face. Am I missing something?
[Nook HD, HD+ Android Development] pavlos46:
I am afraid some more expert with twrp than me should jump in, in my and your case I also get fc and keyboard dropping, there has to be something we can do to format the problematic partition, I am gonna try loading stock recovery and going back to stock if it fixes anything although i strongly doubt it.

Pavlos
[Nook HD, HD+ Android Development] Tschumi:
Ι Think the problem in my device also affects data and system. It took a loooong time to format these.
[Nook HD, HD+ Android Development] pavlos46:
Managed to load stock recovery and go back to stock, but still feels unstable.
[Nook HD, HD+ Android Development] extrem0:
I think you guys got a nook with bad Emmc. It'll fail soon or later and you won't be able to use your tablet anymore. There was a time when trim was enable on kit Kat and some nooks got damaged. There are many Nexus 7 2012 affected too.

Look: http://xdaforums.com/showthread.php?t=2575993
[Nook HD, HD+ Android Development] Tschumi:
Ι am starting to think the same, even though I had checked when the first bricks happened and my emmc wasn't among the faulty ones.

Anyway, I will try to flash a stock recovery and if that doesn't work I will create a bootable sd 10.1 card.
[Nook HD, HD+ Android Development] pavlos46:
Whipped boot partition and everything else, flashed from SD the boot partition fix and plain stock ROM, let it boot and then did a factory wipe only and loaded cm11. Seems to be working great so far.

Only problem is with aosp keyboard that sometimes drops by itself, not fc.

Pavlos

PS. Wouldn't though suggest anyone to wipe their boot partition, but I was desperate.
[Nook HD, HD+ Android Development] Tschumi:
I am way beyond desperate. My entire emmc seems to be set as read-only. I can't seem to push any files, adb crashes, twrp is non functional. I managed to run cm 10 from the sdcard but it's very buggy. Trying now to see if cm 11 runs better.
[Nook HD, HD+ Android Development] Tschumi:
Update, finally some light.

I found Verygreens "noemmc" Cm10 rom. The recovery and the rom don't touch the internal storage at all and it runs very well. I wish I could run a newer version but, at this point I am just waiting for a new tablet.
[Nook HD, HD+ Android Development] amaces:
From a fellow ESL speaker, you're doing fine ;)

As you discovered, Google backs up many system settings nowadays, and probably most of them on Marshmallow. When we last discussed the brightness issue, the conclusion was that one should avoid restoring from an older device backup when these persistent bugs happen. Thus, after wiping local storage properly, you just need to select new device in the GApps setup wizard.

Not a good sign at all… Assuming the underlying eMMC is still OK, that points to messed up partition boundaries.

Just curious, what do you mean by TWRP being non-functional? Can you boot into it and list external storage content? The way CM12.1 is setup, it securely remembers the fingerprint of all ADB clients connected, and TWRP verifies this information. Once you wipe everything, TWRP will not allow regular ADB connections anymore, although sideloading should still work. Assuming that's why you cannot push files in recovery, it can be fixed easily. Of course, things are kaput if the eMMC hardware is somehow broken.

It's enterprise-level Box hosting, which is very reliable. Are you sure it wasn't a temporary issue with your net provider?
[Nook HD, HD+ Android Development] Tschumi:
Non functional in the sense that I cannot apply any changes. The version number stays at 2.8.7.3 even though I tried to flash an older version over it, or even cwm to got back to stock, as Pavlos did above. It's as if the whole emmc became somehow read-only. The external storage is shown and I can "install" or "restore" backups or zips, but using Adb it's not possible to sideload anything, and the file manager (on the Advanced tab) cannot copy files from the Sd to the internal storage (the opposite works though).

Repairing/changing file system for the affected partition is also impossible, as everything stays ext4, despite the process shown as completed.

Any help would be appreciated.
[Nook HD, HD+ Android Development] pavlos46:
How about booting from an SD CWM and flashing stock recovery, (should be able to flash recovery) and doing the 8 failed boot sequence....

Pavlos, psI am actually back on CM12.1.
[Nook HD, HD+ Android Development] amaces:
Well, the current CM12.1 ROMs will not even flash with anything less than TWRP 2.8.7.3 (my incremental tagging, official version is 2.8.7.0). I'm assuming you have attempted the recovery procedure described in the OP, i.e., boot off verygreen's external recovery image, then either flash the latest TWRP ZIP (as of now, 2.8.7.4), or extract the raw image therein to write it manually. When the eMMC partitions are this damaged, you need to use external tools (either your SD card ROM, but preferably recovery) to wipe/fix them. Once the internal TWRP is in good shape, you can attempt to reinstall everything. Otherwise, internal storage is probably OK since you can at least boot TWRP, but other parts are seriously corrupted.
[Nook HD, HD+ Android Development] SCWells72:
Did you ever resolve this? I updated my kids' HDs and am seeing the same thing. I'd prefer to avoid clean flash if possible, so I figured I'd check before burning time on that.
[Nook HD, HD+ Android Development] dononeil:
What's the latest build of CM12.1, is it still 10-18-15? I don't see anything else posted to the box site.

Thanks!
[Nook HD, HD+ Android Development] long2ski:
Sorry to say, I had to wipe and reflash. No problems since except seemingly random screen flicker (green pixelation) that a reboot seems to fix. I believe amaces has moved on to marshmallow so we might get that once all the bugs get worked out on it. (Thanks Amaces!) 12.1 is great though.
[Nook HD, HD+ Android Development] SCWells72:
Thanks. Well, last night I went ahead and did a clean flash of the 10/18 build on both my kids' HDs after taking a TiBu of their apps. I used the latest 5.1.1 gapps from the Cyanogenmod site. It didn't go very well.

First, the AOSP keyboard FCed non-stop. I took a snapshot of the Google Keyboard from the Play Store from one of my other devices and added it, disabling the AOSP keyboard. That took care of that issue.

Then when I tried to restore the apps using TiBu, many of the ones from the Amazon App Store wouldn't restore. When I looked into it a bit more, they wouldn't even install directly from the App Store. No useful diagnostics...just "Install Failed." That wasn't the case with the earlier build of CM12(.1?) that I had installed on there previously.

I'm past the first issue obviously, but the second concerns me. I've accrued quite a few kids' apps from the Amazon App Store's free-app-of-the-day over the years. I could certainly replace them from the Google Play Store, but the fact that they simply won't install makes me wonder if I'm just going to run into other issues.

Any ideas on why this might be happening and whether I can remedy it easily? If not, I'm not opposed to dropping back to an earlier, more stable daily driver for my kids' tablets. I'm more interested in stability than in being on the latest-and-greatest.

Thanks in advance for any guidance!

---------- Post added at 10:37 AM ---------- Previous post was at 10:33 AM ----------

Yeah, this looks like the same thing I'm seeing. Did you ever find any resolution for this issue?

UPDATE: Okay, I figured out why it's happening. The app is trying to install to the external SD card and is failing because it's read-only. I tried using one of the "make SD card writable" apps to address that, but it still fails. For the moment I've changed the "Apps" setting to say that all apps should be installed on internal storage instead of letting the system decide and things that were failing are installing now. I would like to be able to install on/move to external SD since this is a 16GB Nook HD, but I'll get the apps restored and then deal with that.
[Nook HD, HD+ Android Development] chuimk:
Yes I did:

Hope it works for you too.
[Nook HD, HD+ Android Development] SCWells72:
Thanks for following up. Yes, I discovered that same thing about 30 minutes after I posted the question and managed to get my kids' tablets going quite well.

I guess the follow-on question would be whether there's any way to move apps to the SD card under this ROM, though. The "Move to SD Card" button is available and enabled when I look at the application info for some of these apps, but when I tap it, it says the destination isn't writable. Does anyone know how to get this working? Thanks again!
[Nook HD, HD+ Android Development] herges:
I posted this issue a while back but unfortunately no solution has been posted so far http://xdaforums.com/nook-hd/help/to-sd-card-app-storage-space-t3197172.
[Nook HD, HD+ Android Development] SCWells72:
Thanks for the update. That's a bummer. I'm constantly bumping up against the storage limit on my kids' tablets and was hoping that the 32GB uSD cards I picked up for them would help with that. I'm not opposed to going back to a previous ROM if that might help. My kids don't need the latest-and-greatest, just something stable and (to make my life easier) something that can actually use an installed uSD card. Does anyone know if this works under CM11?
[Nook HD, HD+ Android Development] amaces:
Marshmallow has native adopted storage support, which I enabled in the experimental builds. It's supposed to extend system storage transparently, merging eMMC and external SD into one pool. No idea how well it works, but it's there, and the current AOSP builds are pretty usable.
[Nook HD, HD+ Android Development] TeutonJon78:
I know most of the work has shifted to MM, but since this is still the stable line, are there going to be any more builds with the monthly security updates?
[Nook HD, HD+ Android Development] amaces:
Yes, Lollipop/CM12 is still more usable than current MM builds, and I'd like to refresh the stable builds at some point. It's a bit complicated since I had to wipe CM12 stuff, in order to make room for both AOSP and CM13 ROMs. Of course, the sources are not lost, but I've been hesitating to bring CM12 back since it means: a) wiping CM13 for now, b) doing so temporarily, and all this takes many hours to sort out/check/build/etc. I should do it though… for the holidays ;)
[Nook HD, HD+ Android Development] long2ski:
Is anyone else getting more lag? My ovation build 10/18 is not up to what it used to do. I have greenify, rebooted of course, tried wiping dalvik, but no difference. Any suggestions?
[Nook HD, HD+ Android Development] Tonto87:
I'm been scouring the Nook HD forums after a long absence because of this. I'm still on CM 10.2 but it seems that the latest Google Play update (6.0.5) and maybe a simultaneous Play Services update has made my Nook almost unusable. Not sure whether to try a CM12 or MM/CM13 ROM, as I now have nothing to lose.
[Nook HD, HD+ Android Development] amaces:
Try the Marshmallow builds (make sure to also flash the updated kernel if on AOSP); you'd need to wipe everything anyway, and these experimental builds are way better than “almost unusable” ;) I'm suggesting this because I plan to work on CM12 later in the week, so you might as well test these in the meantime.
[Nook HD, HD+ Android Development] TheDannemand:
I am in a similar situation as Tonto87 with my wife's Ovation: It's been on CM10.2 since forever, and is still usable -- albeit slow and in dire need of a TRIM. I've been watching your threads and your work on Marshmallow (CM13 and AOSP) as well as this CM12.1. You and [MENTION=4243514]Hashcode[/MENTION] and [MENTION=3654172]verygreen[/MENTION] are nothing short of heroes for what you are doing to keep these Nooks running. It is very much appreciated!

I assume you're looking to port the recent kernel improvements from Marshmallow to CM12.1 (correct me if I am wrong). With Marshmallow still being quite new, would you say I am better off going with one of your next CM12.1 releases as far as general stability goes? Again, this is for my wife. She is a very patient user, but I don't have the time to update her Nook very often.

Thanks a TON for everything you're doing.
[Nook HD, HD+ Android Development] mmnspeed:
Any links for downloading gapps for cm13?

Edit:Got it..had the correct gapps,but have to install them before first boot for proper permissions..
[Nook HD, HD+ Android Development] Tonto87:
I'm tempted! Although after a few reboots my CM 10.2 has improved in responsiveness.

I did try one of the very early CM12 builds when you first released it, but it was a tad sluggish. Would you say it's improved in smoothness since then?