yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ieatabiscuit:
It's being addressed. Its an issue with upstream CM. You'll also notice issues rebooting to recovery from the reboot menu. Its a great ROM, but itnis still in beta after all. As for the Bluetooth mouse, it again falls on upstream to add in the code for some devices. It doesn't work with my pebble, or some fitness bands either. Everything has it's trade off, but its fun to tinker with things.
[Nook HD, HD+ Android Development] js290:
Just upgraded to 20150803-ovation and using terminal does not work for me. Trying to run "reboot recovery" I get permission denied. And, I also cannot su using the terminal.

I tried the same thing with adb shell, which does get root access, but "reboot recovery" simply reboots the device and not into recovery.
[Nook HD, HD+ Android Development] TBueno:
Always grateful

Maybe I'm too enthusiastic but ovation-0803 seems to be a noticeable performance improvement from previous non-experimental builds, especially regarding UX tasks such as app switching.

I'd say we've transitioned from a device that became surprisingly useful considering it's price, lack of manufacturer support etc etc to a tablet that performs pretty decently, period.

AMaces should set a donation link, I'm sure some of us would like to buy him a beer. And I hope the redundant reports of bugs and occasional complaints don't turn him down...
[Nook HD, HD+ Android Development] ieatabiscuit:
I agree, he busts major butt, as for the price of my ovation, I found mine sitting with 3 others on a clearance rack at Target for $50 a pop. As you can imagine, thet milked $200 from me that day. As for manufacturer support, I think they just wanted a good laugh, and it back fired. Here's to stubborn relentlessness and beer for [MENTION=4473900]amaces[/MENTION]!
[Nook HD, HD+ Android Development] Tschumi:
I...I paid full price. At launch. Plus shipping and import charges. I stupid.
[Nook HD, HD+ Android Development] ieatabiscuit:
I got lucky. Turned out that they didn't even have those in the system. They got found in the back room, and somebody just put them out there. Pure luck nothing more.
[Nook HD, HD+ Android Development] echoedge:
$100. Craigslist add. Nearly brand new. Reeked the smell of cigarettes for weeks.
[Nook HD, HD+ Android Development] mattyyey:
As said this was already explained to me. Thanks for the alternative module, however I use gb for more than 1 menu or I wouldn't bother at all.

[MENTION=4473900]amaces[/MENTION] gave a nice fuller explanation already. I'm still using gb. If I do encounter any problems I know where to start but my ovation is loving this rom!
[Nook HD, HD+ Android Development] Zippy Dufus:
Repository issues - cannot fetch?

Hello,

Has any DIY builders been having trouble syncing with the Cyanogenmod repositories lately?

I haven't been able to build this ROM since 08/02. Below is an example of many similar errors.

I'm wondering if I have done something bad to my build virtual machine except that my backup VM, which I haven't tampered with for some time, appears to have the same problem. However, my OmniROM VM is working OK.

Any ideas?

repo has been initialized in /home/android

warning: local_manifest.xml is deprecated; put local manifests in `/home/android/.repo/local_manifests` instead

fatal: Not a git repository: '/home/android/.repo/projects/hardware/samsung_slsi/exynos5.git'

fatal: Not a git repository: '/home/android/.repo/projects/hardware/samsung_slsi/exynos5.git'

error: Cannot fetch CyanogenMod/android_hardware_samsung_slsi_exynos5

warn: --force-broken, continuing to sync

== EDIT ==

Never mind. My local repo must be corrupt or the VM's filesystem is damaged. A copy of the VM which I shared with friend is still working fine.
[Nook HD, HD+ Android Development] bluecopper:
Has anyone else experienced increased phantom touches and worsening of the right edge responding to touch since installing 0803?
[Nook HD, HD+ Android Development] vinceweis:
Nothing unusual here.
[Nook HD, HD+ Android Development] keshabbhattarai126:
I am experienceing it too on my nook hd smoke grey version. Right edge touch sensitivity is almost dead and random touch is driving me insane.
[Nook HD, HD+ Android Development] sutty86:
My nook died on the the other day dwindled down past one percent now it won't turn on after being on charge all night,charger is making a funny noise on the wall each time I press the power button a battery icon and thunder show up, also tried reset by holding n button and power for 20secs,

Light is orange whilst plugged in.

Cheers
[Nook HD, HD+ Android Development] belfastraven:
The light being orange and the battery icon showing up make me think that the nook is actually trying to charge..... If the charger is making noise at the outlet, I'd try a different outlet (or a different charger--the unit that plugs into the wall may be bad) or you could try charging using a USB port. What version of software are you running ? Was the dwindling down below one percent happening while you were running something?
[Nook HD, HD+ Android Development] amaces:
Can you pair any BT peripheral? The conclusion from last time we discussed BT connectivity was that most things at least pair, basic profiles work well, and even some fancy ones. Audio input (i.e., BT mic) fails, but that's due to our current audio HAL, so no fault with the BT stack itself. It just happens that I ordered a BT mouse recently, and will be able to test this profile soon. Otherwise, we've been discussing power off/reboot to recovery issues ad nauseam; it's being investigated.

Noticeably better performance with the August 3rd builds is probably placebo ;) although being forced to clean cache does make things snappier. My focus was on what I perceived as slightly higher CPU utilization/overheating, and although things feel better to me now, still unsure whether my changes or the weather had bigger impact… Such is life with short testing cycles.

But yeah, I've always had a soft spot for this crazy tablet, and am still impressed with TI's OMAP platform. It's a shame they gave up on its development and exited the mobile chipset business, especially when Tegra and MediaTek are happily chugging along… Otherwise, the donation stuff would involve too many ethical issues, so no point dealing with that internal conflict ;)

Same here, well same price, sans cigarette smell ;)

Sounds like you figured out what was broken locally, and I will add that your custom/additional XML (devices.xml?) should live in the .repo/local_manifests folder.

He was asking specifically about touch changes with the August 3rd build; are these sensitivity issues happening suddenly to you as well?

But yeah, [MENTION=4698765]bluecopper[/MENTION], all recent changes have been relatively minor and unrelated… can't think of anything impacting touchscreen. I do know that most heat generation happens in the lower right quadrant (on the HD+, at least), and touchscreen sensitivity depends a lot on temperature. Also, if you keep using the device while very/unevenly hot, there's a risk of permanent damage to the touchscreen controller.

Did you let it die like that, or it suddenly discharged on its own? Either way, if the meter is correct and the true charge dipped below 1-2%, you may need a battery replacement. If it's just the controller acting up, or if the battery chemistry is still reversible, you need to let it charge turned off for a few hours, or maybe overnight. Only then, unplug it and attempt to power on. Of course, weird charger noises are additional concerns, and either way, I'd do this whole charging thing in a spot that won't catch fire easily, just in case the battery decides to explode ;)
[Nook HD, HD+ Android Development] ieatabiscuit:
Try this, its my go-to for so many issues, and seems to prove its self timelessly. Here it is, ready? Pull the SD card, and try turning it on without it in there. Worst that it would do is not make any difference, or make you buy a new SD card. Either way, simple test that costs nothing. I know, the SD card has nothing to do with your issue, but I'd bet a beer that it will boot with the card removed, and again will not when its reinstalled.
[Nook HD, HD+ Android Development] Seraph08:
I love this ROM.
[Nook HD, HD+ Android Development] jt61:
here's my quick 0803 Ovation report:

* wiped cache and Dalvik cache prior to installing

* reboot to recovery works

* shutdown (and stay shut down) works

* not seeing phantom touch issues reported by bluecopper

* still seeing the "battery apparently drops suddenly from 70-80% to 1%, but it's not real because when plugged in shoots back to where it was" issue I've reported before - probably the same thing reported by sutty86, and probably a bad battery

* bluetooth connection to speaker works

* have to hit power button twice to wake up - this has actually been happening for a while (not new to 0803)

* regularly see "process system is not responding" with options to report, wait, etc.

* have seen a couple of spontaneous reboots
[Nook HD, HD+ Android Development] dk1keith:
Great Rom. Thanks for all the hard work. Does Cast Screen work with this rom? if so what version.

thanks
[Nook HD, HD+ Android Development] echoedge:
Strange, I haven't noticed any of those issues on mine.
[Nook HD, HD+ Android Development] techdudepro:
Thanks so much [MENTION=4473900]amaces[/MENTION]!!! I noticed that the stock keyboard was also fixed in recent builds. Before I couldn't use the "swype" feature... now I can. And the Antutu benchmarks are impressive! I have the best performance I have had with my Nook HD. Way better than CM 11. The benchmarks prove it. And THANKS AGAIN SOOOOO MUCH FOR ALL OF YOUR AMAZING HARD WORK. I am REALLY impressed that you have made these Nooks amazing!

sidenote: have you covered the stagefright vulnerability in the latest builds? Thanks
[Nook HD, HD+ Android Development] amaces:
They've been making changes to the libc/bionic assembler code today, so new builds tomorrow, after these low level optimizations settle down.

I assume so; CM says they were fixed about two weeks ago: https://plus.google.com/+CyanogenMod/posts/7iuX21Tz7n8.

The AOSP keyboard was probably fixed upstream; Google's swipe was always working, I think. Of course, both were triggering those GPU underflows/flickering/reboots till recently. Otherwise, you probably know my opinion on synthetic benchmarks ;)

Aww, you got some searching to do ;) But no, screen casting is a tricky one with LP HALs. Chromecast streaming in apps is a different beast, and that works well.
[Nook HD, HD+ Android Development] twiztid_:
I haven't noticed the swipe (Gesture Typing) not working, but if for some reason it does stop, I would bet that it is likely due to a missing (or possibly mis-matched) file.

Copy (or rename, I've tested and it works) /system/lib/libjni_latinime.so to libjni_latinimegoogle.so, reboot and swiping should work again.

Not sure why it needs the file, possibly due to when the AOSP version of the file didn't have Gesture Typing code and references to it were never added for/relocated to libjni_latinime.so. Without the "google" file, swiping doesn't work even if it's enabled, however it seems everything will work and the keyboard will use the "google" file just fine if the "standard" libjni_latinime.so is not found.
[Nook HD, HD+ Android Development] techdudepro:
Wow, thanks that worked slick. I just tried doing what you said with gapps. (flashing gapps googlifys everything, assumed it would do what you suggested and it worked) Thanks, my mistake:o
[Nook HD, HD+ Android Development] twiztid_:
Glad it worked, I always use the smallest gapps I can, so I've never seen it in the package before (don't like the Google version of stock keyboard).
[Nook HD, HD+ Android Development] windoge89:
Sometimes when I unlock it, it will relock itself. Then it will refuse to turn back on for a little, then when it does, It can be successfully unlocked. Don't know why this happens and I think it happened with CM11 too.
[Nook HD, HD+ Android Development] TeutonJon78:
Are you using a smart case with a magnetic cover? If so, that just something that happens and has happened. Usually just flicking the cover against the tablet once or twice will leave it an awake state.
[Nook HD, HD+ Android Development] windoge89:
I do. I'll try that. Thanks
[Nook HD, HD+ Android Development] KMCO:
Affter install CM12.1 for Nook HD/HD+ [2015-08-10], my Nook HD+ cannot turn on wifi, help me, pls. Thank a lot!
[Nook HD, HD+ Android Development] FirePsych:
Did you reboot?
[Nook HD, HD+ Android Development] ieatabiscuit:
Are you using a case with a magnetic cover? If yes, then it's a common thing that has been around since forever. All you do then is close it, and reopen it, and in time, you'll learn the pattern to appease the Nook gods. If not, then again, as always, try things with the SD card removed, it makes any random weird thing you can imagine happen if it's got its foot out the door.

I vow that one day, I will have said to remove the SD card to every XDA member at least twice, and nobody will have weird things happen ever again!! (saddly, my natural lifespan will have long expired before this happens, but I'm trying.)
[Nook HD, HD+ Android Development] amaces:
Feedback on Aug. 3rd -> 10th

With the 08/10 builds, I'm interested in subjective feedback; does the device feel more sluggish, do things work as well as during the past couple of weeks, etc. The device does feel cooler, and the CPU does seem to ramp down a bit faster, which is good. Yes, synthetic benchmark results/changes are good too for this one ;)

Which build did you have before? Is this the first build with SELinux Enforcing that you installed?
[Nook HD, HD+ Android Development] jaydeedid:
Can an app mess up shutdown?

*I used TWRP to wipe everything before installing 0810 Ovation.

Shutdown worked until I installed several apps. I suspected other apps but it wasn't until I uninstalled GMail that shutdown worked again. I reinstalled GMail and again my HD+ wouldn't stay shutdown. I uninstalled the app again and again shutdown worked. It's probably anecdotal but I wanted to mention it for those who are experiencing issues still.

Reboot to recovery is still not working for me though. Perhaps I'll try uninstalling other apps to see if that works again.
[Nook HD, HD+ Android Development] belfastraven:
On Hummingbird, with 8/10 ,shutdown worked a couple of times, then stopped working. Reboot recovery still not working. could really use both of those features now, since I just broke my dominant hand wrist..:) I've often thought shutdown/recovery may have to do with what we are running on each tablet, since some people seem not to have a problem. For 8/3 though, I did wipe system, cache and data, and neither feature worked before the installation of gapps or any other apps.

My HD does't seem to be running an y cooler, but is runnig very smootly
[Nook HD, HD+ Android Development] TBueno:
Everything great so far on my HD+. I rarely play games and usually check Play Newsstand, task switcher, GPhotos and some other casual tasks for performance comparison between builds: 08-10 feels snappier than it's ever been in my experience. However, as you noted yourself, I'm not immune to some occasional placebo illusions...

It's been great to see my home screen surviving some quick browsing without the need to reload, memory management seems to be squeezing the ultimate most out of the device.

Browsing in Chrome, Firefox and stock browser is as good as it's been since the flickering fix breakthrough, so smooth I'm back with Chrome as my default. BTW, while showing some "heavy" webpages, Google Keyboard might refuse to stay up, switching to home screen then back again usually frees enough ram for it to stick, but I've had this like forever on this device, definitely not Cm12.1 related.

Considering the reboot/recovery fix is a minor annoyance, I'd say this ROM is in a very advanced beta stage :good:
[Nook HD, HD+ Android Development] drmarble:
Amaces:

I added you as a reviewer on: http://review.cyanogenmod.org/#/c/104543/

It might help with wifi connection. Michael Bestas just added me as a reviewer because of some of my past work on the Encore and Ovations and we worked together on some changes for the cm-11.0 release of the TI wifi stuff. I am not building cm-12.1 for anything so I cannot test this. I am sure that he would appreciate your testing this change out. They appreciate any comments. I know that putting in a delay helped with the HP tenderloin wifi connection.

Maybe I will break down and try cm-12.1 on ovation. It sounds like it is working pretty well. I still can't get it to boot on Encore but not many people care about that device anymore. It was really at its best on Gingerbread. I hope we can get a cm-12.1 release soon for the ovation and hummingbird since they are planning on stopping the cm-11.0 builds.

Thanks for all your work on this device. We wouldn't be making any progress without you.

Edit:

There are two additional patches for 44.1 kHz sound on omap4 devices. http://review.cyanogenmod.org/#/c/105565/ and preferably (according to the author) http://review.cyanogenmod.org/#/c/105582/

You might want to take a look at them.
[Nook HD, HD+ Android Development] lonecanislupus:
Everything seems to be going well. Its running on the same last build from July and is good for day to day use from what I've gathered from my girlfriend. The only complaint is that battery drains more quickly while sleeping than it did with the stock nook software, but she mentioned this when I first flashed CM11 before flashing your CM12.1 builds. Anyway, Fallout Shelter came out today and ovation hasn't had any issues with it. :)

P.S. Thanks. Has been my pseudonym since primary school haha
[Nook HD, HD+ Android Development] ieatabiscuit:
So far its been smooth sailing. Temperature has been noticeably less, and during those hot times, I can see that it cools down faster than before. My battery life has been on par with my usage, nothing to report there. Responsiveness has been far superior to CM11, and I have noticed little difference from older CM12.1 releases. I can power down now, but still can not reboot to recovery (which is not as important as stability and such to me, I can always just use the hardware method). I have not tried the Bluetooth gambit, as that is more upstream, and likely to fall short in some areas, CM has some wonky Bluetooth settings. In short, its as it's been, but cooler, and still better than official supported ROMs.
[Nook HD, HD+ Android Development] sasmith-129:
Same experience for me. I can confirm my MiniSuit BT keyboard seems to work with this latest build. I hadn't tried it on any of the earlier builds.
[Nook HD, HD+ Android Development] Jann F:
I have the issue that after a full wipe from CM11, installed via the latest TWRP, after setting up my google account, the setup assistant FC's and throws me back to language selection, so I am not able to exit the setup assistant.

I tried latest CM Gapps and Delta Gapps.

Solution is to do the first boot without gapps or only using f-Droid or Amazon.
[Nook HD, HD+ Android Development] king200:
Interesting to see what happens:

After flashing the rom and getting your setup failure, go into TWRP recovery and use the file manager to delete /system/priv-app/SetupWizard/SetupWizard.apk. You might also just rename it.

I've been using Euroshank (banks) Gapps http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nook HD, HD+ Android Development] evaporic:
You will need to unplug it from the tablet and plug it again for another hour. It may take a few tries every hour for it to get enough charge to boot

---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------

You could also try disabling the lockscreen
[Nook HD, HD+ Android Development] twiztid_:
Is the next build planned for the 17th? I'm on an older build (7/26) but I seem to have a terrible habit of upgrading about 6-12 hours before a new build comes out, so I want to wait this time around. Tablet is running smoothly, but browser issues have been getting worse lately (locks up and have to clear it from recents, then relaunch to unfreeze).

Speaking of, is there a way to download the compiled browser apk file? Or does it get compiled with the OS as you build it?
[Nook HD, HD+ Android Development] bluecopper:
So i flashed the latest build with the latest gapps from banks. The device had serious heat and phantom touch was on viagra. Can the gapps you use affect the behaviour of the device? I did have this behaviour with an older version of the banks gapps. I did another wipe and flash and as it came up, same behaviour. Downloading slim gapps now to try. Which other gapps you guys use?

Video of how my device was behaving https://mega.nz/#!zoV2nKxa!uhr375brq4PEV_GZHweCFhZYPHJFT9S48NtNpyX0-RQ
[Nook HD, HD+ Android Development] echoedge:
I cannot get video link to open, but I was having what sounds like a similar issue on my nook with a 07xx build. I explained it a few pages back as my screen going berserk, touches were met as swipes, was entirely out of its mind. For me this only occurred occasionally maybe a few times a week.

I upgraded to 0803 build (had to reflash gapps too was issue for me while upgrading -

gapps-lp-20150211-signed.zip)... and aside from shutdown issue this ROM has been working like a dream.. have had it for almost a couple weeks now and have not seen any phantom touches since. Also seems cooler while running extensive programs (though I never noticed heat on my nook to ever be an issue).
[Nook HD, HD+ Android Development] bluecopper:
I think I may have to do a full wipe now. Flashed current version and slim gapps and play services keep crashing. Reflected same thing. Flashed again with banks gapps and still having the error. Last night the touch issue seemed to be affecting twrp. The right buttons would activate and the swipe action wouldn't slide over. Can you provide link to the gapps you use?
[Nook HD, HD+ Android Development] echoedge:
Ya it kept on crashing for me to till I reflashed that gapps. I can't provide link bc its been on my SD card forever so I don't even know where I got it. Am sure if you just Google that exact filename you'll be brought to a link to download it right away
[Nook HD, HD+ Android Development] ieatabiscuit:
Did the great installation ceremony on my daughter's hummingbird recently. Paired anything I wanted with ease. I noticed the crashing with my tk pico gapps. Reflashed and loaded without gapps at all, then all worked well. After initial setup, I flashed same gapps, and all has been flawless. Also, been putting the Fallout Shelter app to hard work with my ovation, and I dare say that the 8/10 build has been taking it like a boss! Heating is indeed less prevalent, and cooling is faster. Battery life playing Fallout Shelter has been a couple hours nonstop. Now if we can just teach it to cook too...
[Nook HD, HD+ Android Development] bluecopper:
No i have never used that app before. When my device gets hot, its the back, bottom left. When it was behaving the way it was in the video, it was extremely hot.

---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------

Ok thnx much
[Nook HD, HD+ Android Development] bluecopper:
Anyone using the gapps provided on the CM site? Whats the experience with that?
[Nook HD, HD+ Android Development] ieatabiscuit:
I have before, it's not bad, but it's a rather complete gapps. My issue with a very complete gapps is that it has a lot of extra googly parts that I don't use that will be running by default, and using up resources that I could spend on other things that I would be using. It's about as close to a default setup as you will find, and it's usually pretty up to date also, so not bad at all, just those extra bits that don't get used would be my only complaint.
[Nook HD, HD+ Android Development] bluecopper:
I'm not sure why but I did a full wipe installing 0816 and banks 0815 and on start up there was no gapps apart from playstore that wouldn't open. Reflashed and same thing. Wiped again using the gapps from CM and that worked.