yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] pilotbob3:
Problem with keyboard in browsers- video flashes

Anyone else having problems while using browsers and entering websites using the keyboard?

Whenever the keyboard loads from the browser (either AOSP or Chrome), the display flashes on and off rapidly. Can hardly use the keyboard at all.

I tried loading the Google keyboard and using it versus AOSP, still same problem.

Any ideas?
[Nook HD, HD+ Android Development] amaces:
You're not alone; see message above yours ;)
[Nook HD, HD+ Android Development] Dread This Day:
Odd, on Hummingbird coming from a clean install this issue doesn't exist.
[Nook HD, HD+ Android Development] tebra:
Dirty flash on my hummingbird and don't have any bug with WiFi or keyboard. Thanks to hashcode
[Nook HD, HD+ Android Development] leapinlar:
Usually problems with the keyboard relates to the version of gapps you are using. Are you sure you are running the proper version?
[Nook HD, HD+ Android Development] pilotbob3:
Thanks for suggestion, that's probably it. I loaded the gapps-lp-20150211.signed.zip file from the link in the OP. It was suggested to load the newest gapps package. Maybe I'll try an older package.
[Nook HD, HD+ Android Development] norm883:
LP 2-17

Loaded new update (Ovation) clean install. Used the 2-11 gapps posted and no problem with wifi or keyboard.

Appears to be running really smooth.

norm883
[Nook HD, HD+ Android Development] amaces:
Ovation does have slightly different hardware (beyond the larger panel). It's also possible that my unit is somehow defective, and the new SGX/PVR binaries expose some sort of bug. I've had that happen with GPUs before.

Same visual glitches on my ovation after wiping everything but the external SD card.

P.S. I noticed a flurry of activity in the 3.4 OMAP branch; crossing fingers that [MENTION=4243514]Hashcode[/MENTION] brings an updated kernel in the near future.
[Nook HD, HD+ Android Development] king200:
I tried the Hangouts dialer and it worked. I did get a flash message that the camera wasn't working but the call was placed and seemed ok. There must be some code for the non existent camera in the build.
[Nook HD, HD+ Android Development] pilotbob3:
Got my fingers crossed to for an Ovation fix. Tried older gapps and same problem. Strange thing is that AOSP and Google keyboards work fine in other apps, but in the browsers resort to flashing screen. I did load Swiftkey and that works fine, so it's a short term fix, but I do like the Google keyboard.
[Nook HD, HD+ Android Development] Zippy Dufus:
Dailer still not working for me

Sadly, Hangouts Dialer is still not working for me. Both hashcode's and my own build still have the faint, sporadic, unintelligible sound.

I get the camera wasn't working message too but this is just a minor annoyance.

I've cleared the data and cache of both Hangouts and Dialer and rebooted but no luck. Then uninstalled/reinstalled Dialer. Hangouts won't let me uninstall but reverted to the "factory app" when I tried ... suspicious weirdness here.

I'll have to try a clean install.

Any other ideas?
[Nook HD, HD+ Android Development] verygreen:
Flashing screen is likely a manifest of gfx underflows. You'll see a telltale messages in dmesg if you adb shell in and then execute dmesg.

The occasional reboot also stems from there - underflows force the screen off and then on as the driver is reset and there is a race that triggers sometimes causing a panic - people also hit it at times when coming from sleep and such, but it's really rare, and in case of underflows the screen turns on and off fequently (hence the flashing) and the chances of hitting the race increase.

The underflows apparently happen because we are really driving the hardware (in case of ovation) at the performance edge due to huge screen resolution so the smallest mishap on the bus and we don't have enough data in the pipeline to feed to the gfx unit. I noticed that some units are more susceptible to it than others too - probably has to do with manufacturing quality variations.
[Nook HD, HD+ Android Development] Jon Lee:
I, too, believe that is the problem of lockups and reboots in KitKat (and later) ROMS. Our graphics blobs were designed for ICS. The fact they're even working at all on Lollipop is a minor miracle. Perhaps something to do with dropping 'WAITFORVSYNC' between 10.2 and 11?? Until better blobs are available (designed for the newer graphics frameworks), I don't believe CM11/12 will ever be 100%-ish stable.
[Nook HD, HD+ Android Development] amaces:
Thanks for all the good information. I won't hold my breath for better blobs given the state and age of the platform. I understand that we're sharing a common tree with acclaim and hummingbird now. Hopefully the ovation kernel will be tweaked to minimize these issue.

I for one switched to Hacker's Keyboard to avoid these glitches; hard to look at with its Gingerbread roots, but it's growling on me in terms of functionality.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Move app to SD is not working. There is a option but it says not enough storage while I had abundant amount of storage. Kitkat had left support to SD but it is back on lollipop. Hope it will be fixed on future updates.
[Nook HD, HD+ Android Development] BehindTheMath:
Has anyone gotten Xposed to work with this ROM? I flashed it twice with CWM 6.0.4.6, and both times it got stuck at the boot animation.
[Nook HD, HD+ Android Development] CweeperHugz:
i got xposed to work on this rom. it was quite nice to have xposed available to me the day i first flashed lollipop. lol.
[Nook HD, HD+ Android Development] lothian:
...and what is the recommended "current recovery" (e.g., the recovery you use without issue on your NookHD+..? ...and what is the link to a viable download for that rev?
[Nook HD, HD+ Android Development] leapinlar:
Where is that abundant storage, on sdcard or ext-sdcard? Sdcard on the HD/HD+ is emulated and is actually part of internal storage that shares space with /data. So moving apps to sdcard actually gains you no more /data storage space. I think your issue is that move to SD tries to move to sdcard instead of ext-sdcard.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Abundant storage in both SD and ext SD. Since there was option in settings menu in app section of this rom that's why I am trying. Yes, I know it is emulated storage. Then SD swap would be the only option to gain more storage for apps if it would be available for lollipop rom. Thanks for your support.
[Nook HD, HD+ Android Development] leswgnr:
No root access for ES file explorer

Reported in the bug tracker. After an easy install I began to reinstall my apps. One of the first one I tried was ES file explorer. Turning on root in the app failed multiple times. I had to go into settings, change root access from adb and apps to none. The enable it for apps only. I then enabled root access inside ES. Changed the security settings back to allow both adb and apps and ES, and a subsequently enabled terminal app and ES have, and continue to have, root access.

I'll try TBU in awhile and see if that also eliminates the reported need for Chainfires SU.

So far works well. .... Minus the just experienced keyboard/screen issue which i will now upvote.

Much better than on my Kindle!

Update ..... Using the 2/17 build and current Titanium Backup, and changing the allow root settings as described above, a test backup and restore worked fine.
[Nook HD, HD+ Android Development] BehindTheMath:
Any idea what I might be doing wrong?
[Nook HD, HD+ Android Development] leswgnr:
I am also experiencing this with the AOSP browser and keyboard, but sporadically. (using the latest Gapps linked to in the OP on a clean Ovation install.)

Update... Always boots after flashing when editing a folder name on the homepage. SwiftKey, as another poster suggested, seems to work fine.
[Nook HD, HD+ Android Development] neutronjeff:
This build fixed my issue with the on-screen keyboard popping up while I was using my Bluetooth keyboard.
[Nook HD, HD+ Android Development] CweeperHugz:
i only installed the xposed framework app, and then flashed the zip from the recovery. it worked just fine for me, and xposed wasn't complaining at all. also, make sure you're using the version of the xposed framework that was linked in the post along with the zip. i'm pretty sure it doesn't work with the standard xposed framework app.
[Nook HD, HD+ Android Development] tebra:
Still have a small bug on last build: location by network don't works
[Nook HD, HD+ Android Development] Blenky:
Getting better

This is a very nice ROM - faster that CM11 but the bugs that persist are a deal breaker for me with the Ovation build. The following all listed in bug reports.

1) Allstream app cannot capture device so can't cast Spotify to my DLNA radio!!!

2) BBC iPlayer. With previous build playback and audio very jerky - now a black screen

3) Google Location does not work

4) Cannot cast screen to Chromecast

5) Chrome browser crashing

I will go back to CM11 and keep an eye on this board. Thanks for all the hard work.

To go back do I just do full wipe and reinstall CM11 and Gapps for CM11?
[Nook HD, HD+ Android Development] atlind01:
Screen mirroring for chromecast with CM12

Has anyone tried screen mirroring for chromecast with this version? I tried and it doesn't connect. I saw in other places they talk about a separete mirroring API that needs to be installed but couldn't find the link for that software?
[Nook HD, HD+ Android Development] extrem0:
Yes.

I tried and didn't work even with the 3rd party app.

Here's the link.

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
[Nook HD, HD+ Android Development] Tonto87:
I dirty flashed my Ovation from CM11 and everything's pretty much fine! :fingers-crossed:

I started on the 11th Jan build and upgraded to the 17th Feb version yesterday. CM12 feels much smoother than the most recent CM11 builds, so I'm happy.

I did have to re-install some of the Google apps such as Drive, Calendar and Keep, but apart from that (which is probably related to the dirty flash), it seems fine. Also, I had an issue with the touch-screen going funny, but that was a problem with some earlier CM11 builds. Will have to watch if that bug shows up again.

Thank you Hashcode and Verygreen and to all those who've contributed. :good:
[Nook HD, HD+ Android Development] mr72:
Funny I had the opposite experience. Dirty flashed on CM11 M12, same path first Jan 11 then Feb 17 build, and the device was barely stable, horrifically slow and totally unusable. Finally got so frustrated I factory reset and reinstalled CM11. Mostly this CM12 build is screaming for overclocking on the Ovation. man, is that ever slow.
[Nook HD, HD+ Android Development] atlind01:
thks
[Nook HD, HD+ Android Development] twiztid_:
First off, I want to say THANK YOU to verygreen, leapinlar, Hashcode, Zippy Dufus, and everyone else who has a hand in bringing newer Android version to this device and any others.

It really cannot be said enough. Thank you all for your hard work and your time.

Now, with the latest build of Lollipop, I too am faced with this problem:

While I might not understand the technical details, I full understand that the Nook was never designed to run Android 5.x (or even 4.x for that matter).

But that doesn't really help me get why there is such a drastic change from no flickering with Hashcode's first, and both of Zippy Dufus' builds, to near constant flickering when the keyboard is open in Chrome (Does not seem to happen in the built-in Browser for me) with the one we have now.

Was I just 'lucky' that I never experience it, or have hardware that wasn't affected by it til now?

Is there a way to reduce this effect from happening in the Performance/Developer Options?

It's not fixed, but helped enough for me to log in and type this. Thanks!
[Nook HD, HD+ Android Development] extrem0:
I also felt like you did. I came back to cm11 because I need my nook daily. What we have to understand is that although this rom is already quite stable, it's still in alpha stage. We can't expect the best experience with it. Depending on each person usage, it can be (un)usable.

Also, it's known that hashcode and verygreen support other devices and have their lives so they'll probably improve this rom slowly.

I think android 5.1 will improve performance in older devices with less ram.

Try enabling "force GPU rendering" and/or "Disable HW overlay" in developer settings.
[Nook HD, HD+ Android Development] keshabbhattarai126:
In the latest build 02-17 power saving mode is not present in battery section of settings. In previous built it was there. I am on hummingbird. What about you guys? Is it there? The three dot menu in battery sections is no longer present.
[Nook HD, HD+ Android Development] weinerschnitzelboy:
Keyboard "fix"

I too had the glitchy keyboard problem. However I found that switching to Google Keyboard from the Play Store helps a lot. It looks nearly identical to the stock keyboard but is cleaner and does not glitch out the display.

It's more of a work around, but it gets the job done and preserves that stock look.
[Nook HD, HD+ Android Development] leswgnr:
I installed SwiftKey, a free keyboard from the play store, which has so far for me, eliminated any of these types of keyboard issues.
[Nook HD, HD+ Android Development] Hashcode:
I'm pretty sure keyboard issues are a CM bug atm. And hopefully they will be resolved soon.
[Nook HD, HD+ Android Development] Hashcode:
Re-overclocking comments: this is rarely the right fix for issues that we are seeing.

I think a "fairly" smooth ROM should be possible with more memory tweaks, perhaps a kernel update and graphics binaries update.

Normally, huge lags are due to memory clearing, mmc I/O issues and other non-cpu related items. And almost always experienced while using the launcher (IE games mostly run fine).
[Nook HD, HD+ Android Development] spd_rcr:
The wifi bug was a bit of a pita to clear up as the file manager kept hanging when trying to enable SU access. Eventually got that sorted, but I'm getting a ton of screen cutting-out & flickering when accessing the pull-down notifications.

Seems pretty zippy, but I'll probably roll back to CM 11 for now.

Thanks for working on this.:good:
[Nook HD, HD+ Android Development] keshabbhattarai126:
Other bugs are 1.Music playback in background while doing other stuff stutters. 2. Music list and gallery list duplicate all songs and videos. 3. After applying 3 or more themes theme engine fails to theme notification bar. 3. At first boot brightness is set to 100% and can't be lowered until it is locked and unlocked. 4.After battery is below 15% I.e. low battery; there comes notification to turn on power saving mode and turning it on makes battery 1% directly. I am on hummingbird and ready to explain all these glitches and bugs one by one. I hope it helps in the development.
[Nook HD, HD+ Android Development] ST Dog:
Add detailed reports of each to the bug tracker after verifying they are not already listed.

From the initial post

Also, what build did you use?
[Nook HD, HD+ Android Development] patstar5:
Hello, how stable is this rom? I havn't really been using my nook hd+, usually use my phone all the time but I have it with cm 11 rooted. Compared to it, how stable is it?
[Nook HD, HD+ Android Development] neutronjeff:
I think the Feb17 build is great. I see complaints of screen and keyboard issues, but I did a complete internal wipe before loading and it runs smoothly for me. Note: I did have to reflash it to get WiFi to start up.
[Nook HD, HD+ Android Development] Dread This Day:
[MENTION=4243514]Hashcode[/MENTION], [MENTION=3654172]verygreen[/MENTION], Hummingbird 02/17 build is pretty solid. I use mine A LOT, and I'm really impressed. I have no new issues to report, but I do have a solution/request to fix screen casting.

Can you add audio.r_submix.default to

the product_packages in the device.mk file?

EXAMPLE: http://review.teameos.org/#/c/389/

This will make screen casting work for us. :)

Thanks for all of your hard work, nice ROM overall.
[Nook HD, HD+ Android Development] Hashcode:
I'll try and test this tomorrow. I can't believe I forgot to add this. It's a well-known fix.

Thanks for bringing it up.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Music playback stuttering in homescreen was actually not a bug. I turned off "OK GOOGLE" detection on Nova launcher. And now it works fine. Rest of bug is still persistant. I don't know what sort of thing is used to track bug.
[Nook HD, HD+ Android Development] ST Dog:
Go to the bug reporter page I linked in my last reply to you (also in the 1st post of this thread).

Please list each as a separate issue.
[Nook HD, HD+ Android Development] sjavvaji:
Same with GEL...Turning OK Google detection off solved all my audio stuttering problems.
[Nook HD, HD+ Android Development] dougperx:
Was on CM11 and did a wipe and this ROM is working really really well. I think faster and smoother than CM11 IMHO. I couldn't move apps to SD card but I think I saw that was already reported. Is there anywhere to donate to the devs?
[Nook HD, HD+ Android Development] lentm:
I tried to install this rom on f2fs, and keeps saying it failed to mount: omap_hsmmc

and system unmounts itself and reformat to ext4.

My nook hd+ works okay with the other f2fs roms. weird...
[Nook HD, HD+ Android Development] verygreen:
Actually we alreay have it, it's just in device/bn/common/common.mk:

# Audio Support
PRODUCT_PACKAGES += \
libaudioutils \
Music \
tinyplay \
tinymix \
tinycap \
audio_policy.default \
audio.a2dp.default \
audio.usb.default \
audio.r_submix.default

it's been there since August of 2014.
[Nook HD, HD+ Android Development] mhunt13:
Battery percentage?

I'm running the last unofficial CM12, and all is well -- except I cannot find the setting to change the battery icon or display percentage in the notifications area at top right of screen. Where is that setting?? Thanks,...
[Nook HD, HD+ Android Development] dbrickg:
Dunno about this cm12 for nook hd, but on my phone it's in Settings / Status bar. But I suppose you already knew that and looked there
[Nook HD, HD+ Android Development] mhunt13:
[MENTION=4490141]dbrickg[/MENTION] -- right you are! I looked so hard, just missed it. Duh!
[Nook HD, HD+ Android Development] mr72:
Well, I decided that I didn't give it the proper chance. I backed up my CM11 and then did a clean install of CM12 starting with the 2/17 build rather than upgrading the way I did before. I haven't completely rebuilt the tablet yet and no news so far on battery life (which was, frankly, not very good with CM11) but the extreme slowness is gone. This is actually quite usable. Might even be faster than my CM11, but I haven't installed all of my apps yet.
[Nook HD, HD+ Android Development] agantai:
i have NOOK HD 7" Tablet,i just installed this CM12.0 & although i have only been using it for about 20 minutes i already love it,the tablet feels like a 2015 model. Thanks very much for bringing the awesome LP to the good old Nook HD. :good:
[Nook HD, HD+ Android Development] aoleary:
I find this quite quick also, and doesnt have the random screen flickering of other ROMs. Overall I am very happy with it :)
[Nook HD, HD+ Android Development] Sherip:
Is there an sdcard version of this ROM for Ovation?
[Nook HD, HD+ Android Development] Dread This Day:
No.
[Nook HD, HD+ Android Development] asakurato:
There is too much flickering in every app and frequent reboots because of that in latest build :( Guess I'll go to previous one.

Sent from my C6603
[Nook HD, HD+ Android Development] extrem0:
Anyone experiencing bootlooping on ovation when turning it on with sdcard inserted? I can insert it later without bootlooping. Maybe my sdcard is damaged.
[Nook HD, HD+ Android Development] trenty12:
Getting lots of flickering and reboots on the download in OP (latest I believe).

One noticeable one is when i pull down the top right corner to view toggles. Always flickers and then reboots
[Nook HD, HD+ Android Development] king200:
I don't see flickering. On occasion, Firefox will flicker on a webpage, but in the landscape mode only. I don't run any special settings but I do use the Nova launcher instead of the included one. I have an HD+32 and HD+ 16 and don't see the problem in either.
[Nook HD, HD+ Android Development] vinceweis:
Yes, I get the same thing. When pulling down to see notifications or toggles, it often flickers and will reboot if I don't close the pull down right away. Tried multiple wipes and installs, launcher 3 and Nova, but have not tracked it down specifically enough to report as a problem. My latest attempt was a nandroid restore of cm11 which works great for me, then a dirty flash of cm12. So far, it has been much better but did get some flicker this morning.
[Nook HD, HD+ Android Development] asakurato:
Flickering always happens for me when I pull down notifications on landscape mod. Also, it is flickering when I use Facebook app or messenger or some graphic heave stuff, like youtube.
[Nook HD, HD+ Android Development] vinceweis:
Interesting. I am almost always in landscape mode. Will try in portrait next time it happens. Thanks.
[Nook HD, HD+ Android Development] N!ghty:
I can confirm, that when pulling down the notification bar in landscape, 1 flicker occurs followed by a reboot.

Also, when using the "search bar" in the recent apps menu, I get a flicker, too. No chance of recovery to my knowledge. Seems like the video driver crashes or something...

Btw: which governor and scheduler do u guys use?
[Nook HD, HD+ Android Development] kaidynamite:
yes i'm getting this as well. The boot animation gets slower and slower and it finally just reboots again. i went to the twrp file manager and deleted the bootanimation file and it booted but then system crashed as soon as i booted and i wasnt able to mount the sd card either.

in any case i reflashed the rom and it boots fine without the sd card. it boots fine with the sd card too sometimes. idk its random
[Nook HD, HD+ Android Development] asakurato:
I use default ones.

Sent from my C6603
[Nook HD, HD+ Android Development] Tonto87:
Is TRIM working okay on this ROM?

I mention it because after the Play Store updates several apps, the device seems much slower. This also seemed to be the case with the last few CM11 builds.
[Nook HD, HD+ Android Development] amaces:
One solution is to "Disable HW overlays" in Developer Options till this bug (see buffer underflow here) is fixed (which may be never). It's far from ideal, making the interface choppier, but the device is still fairly usable.

The kernel definitely supports TRIM, which you can also check manually: fstrim -v /data (or /cache). Of course, it depends on the underlying filesystem as well (e.g., no support on F2FS, or exFAT).
[Nook HD, HD+ Android Development] vinceweis:
I tried your solution and it works great. Thanks for that advice. I don't really see any choppiness yet, but I am not that picky about it either. Sure beats flicker, reboot, or always having to be in portrait.
[Nook HD, HD+ Android Development] amaces:
Glad it worked. Just a heads up, that setting may revert to default upon reboot; I guess it's mostly intended for temporary debugging.
[Nook HD, HD+ Android Development] vinceweis:
Ok, thanks. I don't reboot often (unless it reboots itself ?) but I'll know how to control it now.
[Nook HD, HD+ Android Development] ghagiel:
FYI you can enable the HW overlay option permanently. I posted about it back when it was an issue on CM11:

http://xdaforums.com/nook-hd/general/fix-screen-flickering-cm11-m8-hd-t2836318

No idea if it works on Lollipop, tho. Haven't made the jump yet (too lazy to wipe and set everything up again).
[Nook HD, HD+ Android Development] keshabbhattarai126:
Any screen recording program working in this build ??

I am trying to record screen with rec. and it is unable to record, fails at last. Any recommendations?