yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] simon-edwards:
Sorry, that was my typing at 1am the other night. I meant to say Flixster not Netflix. Having read the previous post about NetFlix it must have stuck in my head.

Flixster won't let me view a stream or a download whilst rooted. Thanks for the suggestion, I'll try rootcloak and see if it works.

BTW I've seen more of those errors bouncing off a lockscreen login and straight back to the blank standy screen. This time with BBC Sport as the open app instead of the Nook app. It wasn't a screen timeout that sent it back to the lock screen this time, I simply closed the flap of the case (Poetic in case you were wondering). When I re-opened it the tablet wouldn't let me login again. My pin was accepted, but it kept closing back to locked-out and blank screen immediately. Sometimes I got a glimpse of the BBC Sport screen where I had stopped reading earlier before it folder down to the horizontal bar and locked me out. I could repeat dozens of times and no way was it letting me in. Changing to a different account, a restricted child account is the only other option on my tablet, gave the same result. Selecting the other user icon - back to locked-out. Swipe to unlock - back to locked-out. Select my own account again - back to locked out. Enter pin - back to locked out.

Rather annoying!

This time around it repeated after a soft re-boot. A hard start from powered-off cleared the issue.

Which leads me to another annoyance.

Does anyone else have trouble powering back up from cold? If I don't have a power cable connected it can take 5-10 minutes of pressing the power button for varying lengths of time before one of them works. With the power cable plugged in it boots 1st or 2nd attempt. Is this something anyone else had seen?

It means that if that lockout occurs when I have no power source around - I have to wait until I get home to re-start the tablet.

So, apart from these niggles M11 is fine for me, but when these niggles hit they are rather annoying.
[Nook HD, HD+ Android Development] jpisini:
When it bounces you back have you tried closing and reopening the cover? The Nook has a bug in the cover sensor and that is what it sounds like.
[Nook HD, HD+ Android Development] simon-edwards:
Yes, I did try that a couple of times. Accidentally rather than deliberately. As I moved from room to room to tend to cover the screen in case I drop it. Next time it happens I'll try flipping it open quite often.
[Nook HD, HD+ Android Development] wmuflyer:
Does it do the same lockup if its not in the case?
[Nook HD, HD+ Android Development] JanSpatschek:
Latest nightly doesn't boot for me. (11 Nov). Anyone else?
[Nook HD, HD+ Android Development] vinceweis:
It is working fine for me. If I recall from yesterday, I had a MD5 error on the first download and had to download a second time but I attributed that to hammering the WiFi with play store updates and browsing this forum all at the same time.
[Nook HD, HD+ Android Development] Technosquid:
I saw that the m12 snapshot was released. According to the leaked CM roadmap, that's supposed to be the final CM11 before they start migrating features to CM12 (Android 5.0.) I'm not really familiar with how the process works, but I imagine they'll just put out maintenance releases until can consider it stable. Is that right? If so, what's the typical timeframe from final snapshot to stable.
[Nook HD, HD+ Android Development] TBueno:
CM 11 is actually the first time they use the nightly-snapshot only releases system, so previous versions are not a safe reference for this.

I'm also curious about the naming scheme for post-M12 releases. I doubt they'll label anything "stable", though that would be nice for those who like to feel like playing it safe.

I still remember what a sweet surprise it was when 10.2.1 stable was released for our device. It had been a long while since it got a stable release, and 10.2.1 was a leap stability and performance-wise.

So folks are all excited right now about CM12 and android 5, but what I'm really looking forward to is stable, smooth around the edges, thoroughly patched CM11 "final" releases... by the way, anyone care to share first impressions on m12?
[Nook HD, HD+ Android Development] Technosquid:
My 32GB HD+ with CM11-M12 boots a full 15 seconds faster than my 16GB HD+ with CM11-M10. M12 seems faster with much smoother animations. Noticed the app switching graphical bug is still present. Still waiting for the changelog to be posted.
[Nook HD, HD+ Android Development] KenNashua:
Error going to CM11 M12

Just got back from a trip only to find my sound had stopped working. Expecting to have to do a warranty, I reflashed stock and found that my sound was fixed. Figured it was time to go to CM11, so booted from sd, flashed recovery, and then tried flashing M12:

Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-11-20141112-SNAPSHOT-M12-ovation.zip
(Status 7)
Installation aborted

Tried repeating the process: stock, go through setup, reboot, factory reset, flash recovery, flash CM11, same issue.

Ideas?
[Nook HD, HD+ Android Development] :
Indeed. Worthy to be flashed. So smooth.... its a very noticeable improvement and that's with cm's trebuchet launcher. So cool.

Your not using the recovery for cm11 :)

http://xdaforums.com/showpost.php?p=49257227&postcount=78 This post tells it in reverse.
[Nook HD, HD+ Android Development] KenNashua:
Thanks! I did figure that out a long time after I should have gone to bed and should have figured it out....the new bootable SD was being finicky so I accidentally reflashed it to the older one.
[Nook HD, HD+ Android Development] blautens:
CM11 M12 - thumbs up

I would second the notion that CM11 M12 seems faster - I'm coming from CM11 M9. I can only speak to the apps I installed and tested last night, which are DishAnywhere, Plex (the Plex Pass version), MX Player Pro, Nine, ES Explorer, Google+, Keep, Dolphin Browser + Adobe Flash - all worked fine with quick but reasonable tests. I have not switched to ART, yet, though.

I went without GAPPS at first to poke around - everything looked good. But then I will say that when I installed GAPPS 2014-06-06 (signed) I had a problem I think I had before when I installed CM11 M9, where after a minute it would freeze for 2-10 seconds at a time, making even the login to Google very difficult. Just to be sure, I wiped, formatted, etc - reflashed the ROM and then reflashed the GAPPS - same symptoms.

I recall last time I saw this I froze a service, I think the Google Framework Service, and then went and updated almost any Google app and it would update that service, too, and I was ok. But this time I just hammered through, maybe rebooted a couple of times, but once I finally got my account logged in and got to the Google Play store and updated any Google app - the new service required notice popped up - and once it was installed - poof - no more freezing.

Since then - nothing unusual, no lagging, but to be fair, a fresh start (I always wipe everything I can including /data/media) always makes for a better experience than the old ROM with a million things added, right? :)

Headed for a very long airplane ride now - to me, the ultimate test for the tablet (short of adding my 3 year old son to the airplane ride, I guess).
[Nook HD, HD+ Android Development] Technosquid:
I was just wondering if anyone could tell me -- if I disable HW overlays in developer options in order to mitigate the screen flicker issue (when app switching, and using certain apps especially while charging) will this significantly effect my battery life? I'm using the tablet mostly for watching video. I see that with HW overlays disabled I'm still able to use MX Player's HW+ decoder for video, which does put my mind at ease. Thanks! :)
[Nook HD, HD+ Android Development] TBueno:
I've heard that it will impact battery life and temperature significantly (CPU would be doing all the work), although I've never used it long enough to confirm that.

What I can say is that it slows down transitions and animations to a crawl. I set all animations and transitions to 0.5x, so the lag is really very noticeable. I'll take the ugly but quick flickers over the lag any day.

In my experience, Play Store is the app most affected by the flicker issue, especially when updating or downloading new apps, so I just try to shop for apps when I'm unplugged. And when I plug it I just hit "update all" and let it do it's thing while I'm not looking.
[Nook HD, HD+ Android Development] ominousnimbus:
I wish I could say the same. I even did a wipe and clean install of M12, but UI performance is still the same laggy affair it's always been on my 32 GB ovation.

It's definitely not bad EMMC, as I've successfully enabled TRIM (which definitely made a difference). But on every AOSP ROM I've tried, the main system UI animations are simply unbearable... sometimes, it looks like I get a total of 3 frames out of an app's opening or closing animation with all scales set to 1.0x (as a result, I've just disabled animations for everyday use). And yet, within many apps, the graphics performance is absolutely fine. Seems like it almost has to be either a software bug, or somehow the EMMC performance on the /system partition is worse than /data?
[Nook HD, HD+ Android Development] PMikeP:
Goodbye KitKat. We hardly knew ye.

So, I noticed that the CM 11 change log has been slowing down a bit since L got going.

Then I got a wild idea: I changed the URI slightly, from www.cmxlog.com/11/ovation/ to cmxlog/12/ovation.

I was greeted with this message "CM12 is in progress. There are currently no official nightlies. CM12 commits are listed below" and a long list of commits.

Now, a logistical question: Should we stay on this thread to discuss CM 12? Or will someone start a new CM 12 thread?

P.S. I gotta wonder whether Hershey got any benefit out of the short Kit Kat run.
[Nook HD, HD+ Android Development] dealpapa1:
this thread is way too long. most likely we are going to start a new thread with cm12. :p can't wait
[Nook HD, HD+ Android Development] :
If verygreen is too busy, it could start out in this one then move to another or even something else. That's just as unknown as if/when it will be available unless one of the maintainers would care to comment on either.
[Nook HD, HD+ Android Development] ejstubbs:
Is it safe to install M12 using the Cyanogenmod update service within CM11? I imagine that 'best practice' is probably to start afresh, but I'm short of time at the moment for going through the reinitialisation process and reinstalling all my apps.

Also, would I need to install gapps from stratch if I didn't start from a wiped device?

My HD+ has been very laggy recently (and yes, I've run fstrim a number of times to no great effect) and I was hoping that M12 might help.
[Nook HD, HD+ Android Development] ajislav:
There is no need to start afresh (done m11->m12 myself). Gapps will survive..
[Nook HD, HD+ Android Development] Blenky:
Is CM12 lollipop? Is it available for the Nook HD+ already?
[Nook HD, HD+ Android Development] Tight Git:
CM12 is lollipop (but note that M12 is a version of CM11 Kitkat) but whether we will ever get CM12 for the Nook is questionable. Also don't ask for an ETA or the devs will get upset.
[Nook HD, HD+ Android Development] Blenky:
Thanks. No I would never ask for an ETA. I just live in hope!
[Nook HD, HD+ Android Development] DeanGibson:
Updates?

I really like this ROM (USB host mode support included in Notifications pull-down), and am happy with it (except sometimes requiring a Titanium Backup restore of WiFi settings). However, it appears a bit dated.

bokbokan's 8/5 SD-bootable update didn't support (as far as I could tell) USB host mode. Anyone know if his recent (11/23) version does?

Comments from anyone else who has compared both bokbokan and verygreen's variants would be helpful.
[Nook HD, HD+ Android Development] leapinlar:
Ask him in his thread. Obviously he still monitors it since he just posted a new version.
[Nook HD, HD+ Android Development] agantai:
nvm
[Nook HD, HD+ Android Development] DeanGibson:
Replaced Nook OS with CM11 on internal storage

OK, I liked this so much that I built a bootable Nook OS SDcard, and today I installed CM11-M12 on the internal storage. What I got was:

Much fast performance from using internal storage.

It seems like the WiFi connection irregularities are gone! Good, they were a nuisance.

I lost the internal "Force USB Host" mode notification tile. So, I installed "USBHostSwitcher.apk". Not a big deal, but I prefer it in the notification tiles. I recall reading that it had been taken out of recent CM builds. Anyone know why?
[Nook HD, HD+ Android Development] drmarble:
The developers at cyanogen decided to eliminate host mode from their base code. There are modifications to code outside the device specific code that verygreen has control over. I think that they are in frameworks somewhere. It is in the sdcard version because that isn't made from raw cm source but rather a personal build with a modified source tree.

I don't know why host mode was eliminated. I think it caused problems with some devices. Including the code so some developers could use it and others not have it was too much of a kludge. I'm afraid it has gone the way of the tablet interface and isn't coming back to straight cm builds.
[Nook HD, HD+ Android Development] DeanGibson:
USB host mode

Having seem some of the Linux source code source build options for this and that features, I can imagine that the CM code base probably has hundreds of build options. Each one can have compatibility issues with other options, making delivering a stable product (note that we do not yet have a CM-11 build labeled "STABLE") a nightmare.

One of the problems with a manual USB host mode feature, is that there is currently no way (eg, icon in the notification area) to see if the feature has been left "ON" (like you can with most of the other icons in the notification area). If you forget, leave the option "ON" & connect a charging cable, the device will not charge. The "USBHostSwitcher.apk" has the same issue -- no way (from looking at the home screen) to tell whether it is "ON" or "OFF".

Perhaps if the feature included that, it might have been accepted in the code base. I think verygreen asked for volunteers to improve the UI of USBHostSwitcher. I'm tempted but currently too lazy.
[Nook HD, HD+ Android Development] verygreen:
I just updated the sdcard build for ovation to current source release of CM (I've been meaning to do this periodically anyway as time permits. Glad people still use it).

cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
[Nook HD, HD+ Android Development] TBueno:
According to Cyanogen, we never will:

Don’t expect a build labelled ‘stable’. The ‘M’ builds have supplanted our need for such a release. This also means you will not being seeing ‘RC’ builds.​

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
[Nook HD, HD+ Android Development] DeanGibson:
What's in a word?

Download in progress ...

Then they should probably remove the selector "stable" at the left edge of the web pages for downloads ...
[Nook HD, HD+ Android Development] TBueno:
I'd guess the "stable" selector is still there for the sake of builds prior to the current naming scheme (CM10 or older).

p.s. being a stability freak myself, I kinda miss the fake psychological gratification provided by the old-fashioned labels :p
[Nook HD, HD+ Android Development] DeanGibson:
Bug in SDcard variant?

This new version still has the annoying bug that loses all the WiFi access points. Fortunately, they are trivially restored from a (a "yellow" one, not the "green" one) "Wi-Fi Access Points" backup in TitaniumBackup.

This bug is not in the official emmc variant.
[Nook HD, HD+ Android Development] verygreen:
How do you reproduce, I wonder? I see nothing of the sort.

Also the source is all 100% the same between and emmc and non-emmc, with the only difference being addition of usbhost quicksetting.
[Nook HD, HD+ Android Development] DeanGibson:
What's the difference?

Hmm, well I first installed bokbokan's SDcard-bootable 8/5 variant, and then decided to try your SDcard-bootable 8/17 variant. I don't recall if I had the issue with his variant (I think it did), but before I installed yours, I looked at your .ZIP file and noted:

format("ext4", "EMMC", "/dev/block/mmcblk1p2", "0", "/system");

I therefore assumed that any remnants of what he installed would be erased by the reformatting. However, I did not erase /data.

If you think that wiping /data might cure the problem, I would be happy to try that. I'm certainly proficient in reinstalling all my apps :)
[Nook HD, HD+ Android Development] verygreen:
Well, /data holds all settings, but I am not sure what setting would achieve the effect you describe.

It's just I don't really have any wifi problems other then if using soft-reboot option, both in emmc and sdcard install too (and I test both), so if emmc install works for you, there's no reason whatsoever for sdcard install not to work.
[Nook HD, HD+ Android Development] DeanGibson:
It may have been me ...

Well, with every other Android device I've owned, I've always been able to just modify (from a reference file on my PC) the wpa_supplicant.conf file to include all the WiFi access points I use, instead of having to enter them manually, one at a time.

When I did this with bokbokan's version, nothing happened (it ignored my changes), so I (ugh) entered them manually, and then saved them with TitaniumBackup. Even so, on a reboot, they would sometimes be gone again. However, a TitaniumBackup restore would (temporarily) fix it, so it was a minor annoyance. Then, I moved to your CM SDcard variant, but the problem remained.

However, I liked CM enough that a couple days ago I installed your variant on the internal memory, and this time I just did a restore of the yellow "WiFi Access Points". For the couple days I have been running that, I have had no problems.

So, just today I did a factory reset on the SDcard copy, followed by a yellow "Wi-Fi Access Points" restore. So far, after a couple reboots, WiFi settings seem to be retaining.

Edit (2014-12-07): The WiFi problem seems to be gone.
[Nook HD, HD+ Android Development] didopicha:
Mine has this bug too. After I leave the tablet for a while when I unlock it again the wi-fi has disconnected and I have to type in the password again. Sometimes I even have to reboot in order to connect.

I didn't make a clean install, could that be the reason?
[Nook HD, HD+ Android Development] metropolitans:
Problem with lock screen

I have an issue with the lock screen on both my HD+ and HD. When I enable the PIN lock, then do a full reboot, both devices boot directly into the home screen -- instead of presenting me with the lock screen and requiring me to enter a PIN. The lock screen and PIN work just fine after the screen goes to sleep, just not after a full reboot. Am I overlooking a setting somewhere?

I do not remember if it's always been this way since I started using CM11 builds or if it's just something recent. My HD is running M12 and my HD+ is running M10.

Is anyone else seeing this behavior? How do I get them to boot into the lock screen?
[Nook HD, HD+ Android Development] ajislav:
I can confirm this on HD+ with M12.

Moreover, browser does not open, until the screen is locked and unlocked..
[Nook HD, HD+ Android Development] digixmax:
My HD+ (currently running M12) has always rebooted into the pin-based lockscreen.
[Nook HD, HD+ Android Development] :
A quick search reveals this -> http://forum.cyanogenmod.org/topic/79516-solved-nightly-20130926-lock-screen-not-locking/

or this -> http://xdaforums.com/showthread.php?t=2456650

So its probably an app gone wrong (system or downloaded), an incorrect cm setting, or a cm feature gone wrong. ... I just can't narrow it down further [for you].
[Nook HD, HD+ Android Development] asakurato:
Just installed M12 over ancient CM11 build, with clean install. After reboot, it always goes to recovery. What did I do wrong and how can i fix it?

Never mind, fixed it myself.
[Nook HD, HD+ Android Development] asakurato:
Ok, everything installed good(M12), but everuthing is very slow, sometimes I get bkack screen when opening apps. Will it get better?

Sent from my C6603
[Nook HD, HD+ Android Development] metropolitans:
Thank you! The solution was in the first link. The lock screen quick settings tile was toggled to off on both my Nooks. Switched on, my lock screen now works as it should. Odd thing is, despite that setting, my lock screen was working most of the time -- unlike with the OP in that thread. It just wouldn't work after a reboot.

All is good now. So glad I don't have to reinstall, which is what I feared. Thanks again.
[Nook HD, HD+ Android Development] lancorp:
Where are the M builds?

Had a couple of Nook HD+'s that have been sitting on my shelf for a year with an old CWM 10.x on them, and thought I'd refresh with KitKat.

I'm not an expert at all, and followed the instructions on the first post here. Not knowing which ROM to use, I chose the latest nightly. It seems to be fine, although I haven't spent much time with it yet as I just flashed it.

I now read about "M" builds, but cannot find them. The official page I go to and chose OVATION only shows Nightlies. Where do I find the M builds, like M12 for the Nook HD+? Is it OK to flash M12 over the the nightly (12-12)?

Thanks.
[Nook HD, HD+ Android Development] vinceweis:
The M builds are in the same list as nightlies but in the column for type, they are labeled snapshot instead of nightly. I've read that it is not a good idea to flash M over nightlies. I run the nightlies without any issue.
[Nook HD, HD+ Android Development] lancorp:
Thanks for the info. I see that now, and even choosing SNAPSHOTS under the category shows them (I'm sure I tried that earlier and the list was blank, but who knows!).

Do you think it's OK to put a newer SNAPSHOT on top of an older nightly, then? I'm good with staying with 12-12 nightly, and when M13 comes out, I'd want to put M13 on.
[Nook HD, HD+ Android Development] vinceweis:
No problem putting a newer snapshot on. It's just a newer nightly without the most recent changes.
[Nook HD, HD+ Android Development] digixmax:
See http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations.
[Nook HD, HD+ Android Development] Darrian:
[MENTION=4190710]drmarble[/MENTION]: would you mind building and posting a new unofficial nightly with zram, please? Thanks.
[Nook HD, HD+ Android Development] ShapeShifter499:
I never got a answer on this so I'm reposting. Sorry for the weird video angle. Does anyone know why I get this "glitched dual headed android" bot logo while updating using the CM Auto Update?
[Nook HD, HD+ Android Development] xecutionkrk:
Using M12 since its release but recently realized flash videos will not render or flat out freeze youtube app. Than checked with my time warner tv app and it does the same when viewing from the app. However playing videos from my harddrive like avi, mpeg videos works just fine....:confused:
[Nook HD, HD+ Android Development] Technosquid:
I've been able to use flash video in dolphin and firefox on mine running m12. It's not great... one has very poor frame rates, and the other has audio that runs behind. I'm not sure which browser was which. I have noticed a little bit of weirdness in youtube app controls when in full screen... of course that's not a flash problem, since the youtube app, nor youtube in chrome for android uses flash. You were probably just using "flash videos" as a blanket term for any browser based video whether it's played with flash or not.
[Nook HD, HD+ Android Development] sean_nj:
Where is the option to change CM update download type?

Hi guys,

My Nook HD+ is running CM SNAPSHOT-M12-ovation. I tried to update to a new version, the nightly one. But the option to change update type is not there (CyanogenMod updates) any more. The only option there is check for updates. There used to be an option to change update type.

Do I miss something here?

Thanks,

Sean
[Nook HD, HD+ Android Development] TBueno:
That option isn't available anymore. They've decided to enforce the "no crossing streams" old warning.