yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Darrian:
Ok, so you were using the same recovery as me. Interestingly enough, though, when I booted into TWRP today I discovered that I am now somehow running 2.7.0.0. I don't know how that happened since I never flashed a newer recovery zip.
[Nook HD, HD+ Android Development] mr72:
What nightlies are you guys running? Are you using ART? How stable is it? Battery life?
[Nook HD, HD+ Android Development] rholm:
I'm running 03/27/2014. It's much smoother than 10.2. Most everything seems to work. I have had a few hot reboots while using chrome. They have seemed to have something to do with browsing. I'm not using Art. Battery life is great, might be better than 10.2. I was having problems with screen sensitivity in Feedly and lag. Had to restart 10.2 every few days.

I upgraded last weekend and am happy. However, I would like to see it a little more stable for browsing.

All in all, great work by verygreen!

Cheers,

Rich
[Nook HD, HD+ Android Development] TeutonJon78:
If you flashed Succulent's ROMs, he includes 2.7.0.0 in his builds.
[Nook HD, HD+ Android Development] ibilln:
Agree with this
[Nook HD, HD+ Android Development] razholio:
3/27 seems to be a magic build for many. I've got 3/26 which is just ok, but I cannot download 3/27 from CM 'cause it's rolled off the list. Would anyone be willing to post it to their dropbox or some such for us to grab? thanks.
[Nook HD, HD+ Android Development] mr72:
I had a major collection of problems with the 3/28 and finally rolled back to the 3/25. I think everything got broken with the 3/31.

I would like to think since a week has passed now the new build could have fixed problems with 3/31 but nothing in the change log seems to show much promise.

Would also be nice if we had some indication of whether there is testing or stability observations going on. Pretty much picking up nightlies is like taking random chances. You never know what you will wind up with. And sometimes you wind up with something hopelessly broken that can't be fixed with a downgrade.
[Nook HD, HD+ Android Development] Darrian:
Oh, ok, thanks.

Well, I'm running the 4/02 build now and it seems to be stable and I've not noticed any flickering whatsoever in the last day. I might stick with this one for quite a while, in case it gets broken again.
[Nook HD, HD+ Android Development] mr72:
Are you using ART?
[Nook HD, HD+ Android Development] Darrian:
No
[Nook HD, HD+ Android Development] PMikeP:
TWRP 2.7.0.0?

That is strange. Since malware doesn't make things better, I presume someone included a recovery in their ROM which automagically installs. (Succulent?)

I was over at the TWRP website this morning, checking to see if they had an official version of 2.7.0.0 for the HD+. They don't.

BTW, FWIW, when I booted TWRP after installing Succulent's 2.6.3.0.a version, it still paints as simply 2.6.3.0.

To kinda get back on thread, I read that people update to CM 11 because they have problems with CM 10.2.1. I've been running 10.2.1 for a couple weeks now (I think) and it's been trouble free. In fact, I almost make myself dizzy scrolling in Dolphin browser, it's so fast. I can't believe Nook HD+ hardware is that different, unit to unit. I wonder what makes the difference? (FWIW, I'm running the micro (or mini) version of gapps, and have uninstalled a lot of junk and disabled a lot of services.)
[Nook HD, HD+ Android Development] Whyzor:
Just installed 4/3 nightly and DSP Manager, Themes Provider, and Phones keep crashing, I'm running ART. The dialog keeps popping up and can't proceed (Don't understand why Android can't just go on, instead it's like MS Windows, stops everything in the GUI & pops up a dialog where there's only 1 OK button and it doesn't do anything useful)

UPDATE: Had to do factory reset & 4/3 is working ok ONLY in dalvik. I wiped cache originally, and even recovery restore to older build broke when I wiped cache & switched to ART.
[Nook HD, HD+ Android Development] sz0pf1:
CM11-3/17 Working Well

Currently running the 327 build and have been for several days. It's been very stable and responsive. The only problem I've had with it is that on occasion, I have to reboot to re-establish my Wi-Fi service. Must of the time I would not have service in the morning after using bluetooth to play music at night. I programmed an auto reboot which mostly eliminated the problem. I wake up and I'm good to go. I'm running Davlik.
[Nook HD, HD+ Android Development] pgrunwald:
I have found 3/27 also very stable with the exception of location services. Both SkySafari and Redbox can't pick up a location. I'm running ART.
[Nook HD, HD+ Android Development] kiyo21:
Had a similar issue today when updating to the latest 4/5 nightly build. I am running cm11 with ART as well. I had nonstop crash errors pop up in dialog boxes and they wouldn't stop popping up. The launcher never loaded up. I had to turn off the nook, boot it into recovery and reflash an older built I was originally on (3/29 nightly). All is fine now, but it seems this newer built still isn't working well with ART enabled.

---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------

Okay. I took a look at the CyanogenMod subreddit and it seems that ART is currently broken on all newer builds since the 3/31 nightly. It seems one of the commits made for that built is causing the issue and it hasn't been fix yet.
[Nook HD, HD+ Android Development] Whyzor:
I've been back to using 4/3 build w/ Dalvik and haven't really noticed much difference from ART in terms of response or battery. I think I'll stick with Dalvik for now since the ART platform commits have stopped on CM11 since about Feb. Android AOSP has a lot of recent commits that's not being included in CM11 nightlies. This is still experimental and new commits are more important than a stable feature.

https://github.com/CyanogenMod/android_art/commits/cm-11.0

https://android.googlesource.com/platform/art/
[Nook HD, HD+ Android Development] rholm:
I've seen this too. The random reboots seem to have stopped when I disabled the animation options.

Cheers,

Rich
[Nook HD, HD+ Android Development] JanSpatschek:
Which animation options? In the developer section?
[Nook HD, HD+ Android Development] rholm:
Yes. Window, transitions, and animator.

Cheers,

Rich
[Nook HD, HD+ Android Development] JanSpatschek:
Will try that. My device is just weird. I flashed 3/27 and didn't have a single problem for a week. Then I tried out some other ROM, went back to 3/27 and got reboots.
[Nook HD, HD+ Android Development] kiyo21:
I just did the same thing. I switch back to dalvik and am running the latest 4/5 nightly with no errors or crashes as before.

One issue that still bugs me is the screen flickering that happens occasionally when charging the device. Are other people still experiencing this issue?
[Nook HD, HD+ Android Development] angelofmenoth:
I'm on 3/28 with no problems running ART. Dalvik seemed a touch laggy. Battery has been great. I sometimes get flickers when charging, but unplugging charger and plugging it back in seems to fix it easily enough.
[Nook HD, HD+ Android Development] mr72:
OK, anyone know how to get the ART fixed in the more current nightlies? ART really makes a big difference (for me) in responsiveness and battery life, which translates directly into usability. I'd prefer not to have to go back to Dalvik.
[Nook HD, HD+ Android Development] JimJ2Mz:
As of now, ART on the April builds are broken and won't be fixed until the correct commits are put in to ART. There's probabły no way to fix it other than reverting to a build from 3/29 and back. I don't have my 3/27 build anymore but if I did, I'd give it to you. Sorry.

And I did try 4/6 and right after I switched to ART, everything began dying.
[Nook HD, HD+ Android Development] mr72:
That really stinks. And also, what is more annoying is that there was nothing in the change log to indicate that they broke ART.
[Nook HD, HD+ Android Development] Jann F:
God damn stop complaining about ART already, it's a still experimental feature and not a BN Nook HD/HD+ thing!

I still get random flashes sometimes and my device got stuck and only showed screen flashing after the first night.

I hope the Bexus N kernel will soon work, so I can test official nightlys with this kernel and see if it's a CM11/10.2 kernel thing...
[Nook HD, HD+ Android Development] mr72:
It's a thing that's functional in AOSP on numerous platforms and broken uniquely in CM11 on the HD+ (and likely HD). It may very well be broken in CM11 on other platforms, maybe even all of them. But it's definitely something to talk about when discussing CM11 on HD+. Ordinary stuff that works in AOSP is expected to ordinarily work in CM.

Screen flashing is happening currently when the charger is plugged in and every build since the very first nightly has done this. There's plenty to fix in the HD+ CM11 build. My point is that we should at least have those things working that are not unique to the HD+ such as ART. As it is, we have not only unique HD+ problems like the screen flashing but also incompatibility with normal AOSP functionality.

It's beyond annoying to flash a new nightly only to discover the device won't boot due to a likely-known ART breakage. At the very least, this deserves a note in the CM change log. "fixed <some.code>; fix for Dalvik only, may break ART." These are regression bugs. Regression bugs must be top priority to fix.
[Nook HD, HD+ Android Development] JimJ2Mz:
Whoa whoa. Calm down. Yes we know ART is experimental and all that other good stuff, but it has shown improvement, both in official testing AND personal usage, so not being able to use it does stink. Besides, there have been TONS of commits to ART on the official Google thing, just that Cyanogemod hasn't taken in those commits for some reason (which could be linked to why ART is broken). But yeah. ART is nice.

As for the Bexus N Kernel, I too am waiting to test it. I'm interested in it. But for now, I've reverted to Succulent's CM11 as it is much more stable.
[Nook HD, HD+ Android Development] Jann F:
ART isn't even an official AOSP feature yet...

It's a experimental developer thing and it pisses off to read through the thread and half of the stuff is related to ART.

The flashing screen is not related to the charger, but it sterted with the first nightlys of CM11 and is persistent in the CM10.2.1 build that came after official CM11 nightlys as well.

I think it's related with the kernel, it also happens more often when I use apps that utilize overlays.
[Nook HD, HD+ Android Development] mr72:
ART is pretty much the primary improvement CM11 has over CM10.1. So IMHO, ART is CM11.
[Nook HD, HD+ Android Development] JanSpatschek:
True, this Kernel has some bugs. That should be

priority now. Succulent's Kernel doesn't have any of these bugs.
[Nook HD, HD+ Android Development] Jann F:
That's why I wonder how stable Bexus-N is, I'll maybe setup a build environment tomorrow to try and built a package.
[Nook HD, HD+ Android Development] gandalf_grey91:
I am having problems using the nightlies in that by the time it has been established one is stable it is usually no longer listed for download in the cyanogenmod download list. Is there a more comprehensive list of the nightlies going back further into the archive?
[Nook HD, HD+ Android Development] mr72:
What would be better is if we were to begin to get some stable builds. Those hang around for months.
[Nook HD, HD+ Android Development] mr72:
Adding to my "please fix ART" line of discussion, I have been running yesterday's nightly for a day now and I can tell you that with Dalvik it is far more laggy and less responsive than the 3/28 was with ART. While it's possible other things are causing the lag, I also noticed a major improvement just switching from Dalvik to ART on previous builds. Battery life is uniformly improved with ART as well.

This video makes the case brilliantly:

http://www.youtube.com/watch?v=a7KmLpszbJQ

And while I'm at it, here's a discussion that may shed some light on what broke ART.

http://www.reddit.com/r/cyanogenmod/comments/223fxg/psa_art_runtime_broken_since_3103_nightly/

I can confirm that at least for the 4/7 nightly, this workaround works to "fix" ART:

mount -o remount,rw /system

edit /system/build.prop, comment out or delete "dalvik.vm.heapminfree"

mount -o remount,ro /system

reboot

In the meantime I think I plan to do a little scripting to make this fix persist across CM updates along with my preferred key layout fixes.
[Nook HD, HD+ Android Development] xflier:
Thanks a lot! I rolled back to 4/6 nightly which is the best one for me. I used build.prop editor to remove the value of it, and switched to ATR. It works too. It is faster than dalvik. I think I will stay on 4/6 nightly for a while.
[Nook HD, HD+ Android Development] mr72:
I'm glad this works! FWIW if you get into a situation where the UI won't come up due to constant errors you can edit the build.prop, switch runtime and reboot from ADB which should be accessible even if the UI is hosed.
[Nook HD, HD+ Android Development] JimJ2Mz:
Kind of disappointed M5 wasn't built for ovation.

cm y u no build m5

But anyway. An RC build would be nice about now. Stable still seems far off (though I'd love a Stable build).
[Nook HD, HD+ Android Development] Whyzor:
This comparison video actually does NOT do a good job. Comparing most games is not good because they have code that are written natively for ARM processors, so doesn't make a difference in Dalvik or ART.

I really wanted to believe ART is faster & more battery efficient, but really not objectively seeing it there. I've read that ART does help keep 60 fps in most rendering because it has faster garbage collection, which happens more often in Dalvik and takes longer, thus causes the hiccups that users experience. But I just don't experience the difference myself on the HD+. Also knowing that CM is so far behind the latest patches going into AOSP ART, I'm ok with running Dalvik for now, or at least wait to try it again after this fix to the bootup errors (currently in review) to be approved into a future build:

http://review.cyanogenmod.org/#/c/62152/
[Nook HD, HD+ Android Development] LucaToo:
Horrendous problems since 31/03

Title says it all. Despite clearing data and going back to M4 - Nook now runs like a dog. Some apps (inc Comixology) now take so long to open that I am sat looking at a black screen wondering if the thing has crashed and after charging overnight I have error messages popping up left right and centre.

Dolphin never now seems to complete loading a web page.

31/03 fried my SD Card which is now unreadable on Nook or PC and I am wondering if it did any further damage.

I have got a complete backup from 10/01 - which I can't now recall if it is before or after loading CM11 for the first time. But I may try going back to that next as the Nook is currently nigh on unusable.

Previous nightlies up to 18/03 were running fast and smooth using ART or Dalvik.
[Nook HD, HD+ Android Development] Darrian:
I'm having no problems whatsoever on 4/9 except that it takes forever to boot up. That may have something to do with Greenify and all my Xposed modules though.
[Nook HD, HD+ Android Development] mr72:
The game play wasn't the point. All of the navigating, etc., the ART is clearly way faster. Only the installation of the game is slower on ART, and the gameplay is the same.

It illustrates perfectly well why ART is an improvement. The device just feels snappier when using it, because it is faster in routine tasks.

I read books and web sites on my HD+ most of the time. Dalvik or ART makes no difference looking at a page of a book. Switching tasks, it makes a huge difference. There's an amazing difference for example just switching to the browser, clicking in the URL space and how much time it takes to actually bring up the keyboard and become responsive. With Dalvik you'd swear it is broken or frozen. It is just abysmal. Nearly useless. With ART it just works exactly as you would expect a functional product to work.
[Nook HD, HD+ Android Development] Jann F:
Would you please start your own ART propaganda thread? :rolleyes:
[Nook HD, HD+ Android Development] mr72:
Yes, right as soon as you start your own "CM should not support all of KitKat" thread.

Please forgive me for trying to contribute something useful to this thread. ART is faster, and ART is broken (well, was yesterday) in CM11. Breaking something that makes the device faster and more usable is rarely considered a good thing. But you are entitled to your own opinion.
[Nook HD, HD+ Android Development] Sherip:
Hope someone can enlighten me what needed improvements have landed since the unofficial version of 1/18 of the OP. I'm still running the unofficial from a 16gb SD card with ART enabled. Its been very snappy and stable all the while excepting the rare occasional spontaneous reboot.

Sent from HD+ MAG2GA CM 11 from SD
[Nook HD, HD+ Android Development] bxlegend:
Let me explain something to you and everyone using ART, it is early beta code that is not yet fully ready even though it was released with KitKat. Cyanogen is not obligated to support beta features. So your constant complaining in this thread serves very little purpose. If you know a developer that supports the Ovation and likes to mess around with beta code, please go and ask them to fix your issues. If you can't find one, learn to build and code yourself using the handy guides here on XDA or the CM wiki. Just stop with all the talk about ART as nothing is going to change anytime soon.
[Nook HD, HD+ Android Development] TheDannemand:
I, for one, think that discussion of how ART is implemented in this ROM, DOES belong in this thread. It's a KitKat feature (even if still experimental) and CM11 is a KitKat ROM. Why would it not be discussed here? Particularly when the feature is broken.

That said, I wouldn't want the thread to be flooded with ART vs dalvik debate. I don't think excessive ART promotion belongs here, nor do posts that profess hate on ART and wish it to go away.

Of course that's just my opinion.

Edit: I wrote this post just as bxlegend was posting his. My comments were prompted by earlier posts in the thread.
[Nook HD, HD+ Android Development] mr72:
It may be "experimental" but it's not "beta". It's released. Period. Go buy a brand new Nexus 5 and you can turn on ART in fully-released, production product. It's "experimental" because, primarily, 3rd-party apps may not work with it fully. In fact, even some of Google's own apps don't work with it correctly, but the Android OS supports it fully.

CM are not obligated to support anything. But if they endeavor to create a KitKat ROM, then they should ordinarily include the normal features available in AOSP, which in this case includes ART and a million other things. Generally CM has supported all AOSP features as well as some unique CM features, at least in my observation having used CM builds almost exclusively for many years now.

Your "if you don't like it, build it yourself" is beyond ridiculous. The last thing we need is another special one-off ROM. It is more than worthwhile to encourage the CM team to include AOSP features and fixes. It's open-source for a reason. If it weren't for AOSP we'd not have CM anyway.

Used to be we had build threads on xda-developers where we could actually discuss bugs and the devs appreciated the feedback and had a desire to fix things. I think the CM11-Ovation devs probably do want to make their build better, and I have no indication that anyone is deliberately avoiding fixing things. I was trying to help out during the time between when a bug is discovered and when it can actually be fixed. More than one person uses ART, after all.
[Nook HD, HD+ Android Development] bxlegend:
Discussing how it is broken is pointless since Google is not fixing it in released versions of KitKat. Cyanogen code is based on released versions not beta or experimental.

---------- Post added at 11:44 AM ---------- Previous post was at 11:36 AM ----------

Google themselves said it is beta code even though it is available in current products. Some simple research would bring this to light for you. To make your own builds is not implying you release it on XDA. It's meant for you to configure the code to your liking to suit your needs. Once again, as I've stated before, the updates to ART are not in the release channel and most likely will not be until 4.3 is released.
[Nook HD, HD+ Android Development] sunami88:
Third time writing this post:

I will probably do the build.prop mod next time I upgrade (I'm currently running CM11 0118 - works great), but I wonder if this could have been done intentionally to stop people from using the "not even close to ready yet" ART.

Thoughts? I don't mean this in a malicious way, but perhaps there's some huge (not necessarily user-facing) bug with ART?
[Nook HD, HD+ Android Development] TheDannemand:
I was not referring to ART being broken in general (which I don't think it is, it's just being experimental). I was specifically referring to the situation where ART is working in CM11 for weeks and months, then stops working and causes the ROM to be unbootable, because a build.prop line was inadvertently added in a nightly. I cannot think of any reason why that can not be reported and discussed in this CM11 thread.

The only reason ART posting has escalated here, is because of attempts to suppress discussion of legitimate issues like that, thus prompting others to post in defense of ART. I think neither of those types of posts belong here (arguing for or against ART). But reports and discussion of a feature that exists in CM11 -- and worked, but then broke -- is completely legit.

Google included ART in KitKat so that app developers can begin to ensure compatibility for the day when ART becomes default. If ART (as delivered by Google/AOSP) is broken in CM11, app developers can no longer use it to test compatibility of their apps. I am sure Cyanogen wants to fix that too.
[Nook HD, HD+ Android Development] bxlegend:
The line that was added to the build.prop is nothing new to Android and only shows that Google has to do more testing with ART before it is ready for primetime. This is why it shouldn't be used by regular users until it is 100% stable.
[Nook HD, HD+ Android Development] TheDannemand:
Of course it needs more testing. So does the entire CM11. But it WAS working, then broke. Users reported it, then others complained that it is a forbidden feature that cannot be discussed. And here we are with too many posts about it (on which I agree).

When others discuss a CM11 feature that I don't use (of which many are still in beta) I don't tell them to stop posting about it just because it doesn't interest me.

Stop arguing against ART (since it isn't going away) and others still stop defending it.
[Nook HD, HD+ Android Development] BJohnM:
Honestly, is there anyone on this thread that doesn't think this thing has been run to ground as a point of discussion. I'm pretty sure, by now, that verygreen and all the other developers know it is an issue, and it will at some point get fixed. I doubt another three pages of arguing about whether or not it should be discussed on this thread is going to make much difference.

So please, out of respect for the rest of the community, let's give this one a rest. I'd suggest those that want to continue the argument do so using personal messages.

Thanks,
[Nook HD, HD+ Android Development] Jann F:
Can someone give me the needed proprietary files to compile cm?

I'd like to experiment with some own kernel builds, have set up my build environment, but can't get those files since setting up adb for our nook is a pain in the ass.

I'd like to track down the screen flickering issues, as I only get them on cm10.2 , but not on cm10.2m4.
[Nook HD, HD+ Android Development] JanSpatschek:
Awesome, I can't really help you with the files, but I just wanted to say that I appreciate your work.

Would be great if you could implement 8X8 Fuzz in that Kernel (http://review.cyanogenmod.org/#/c/54476/).