yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
I know CM has made some questionable changes in the past, but this one seems incredibly excessive. The CPU page was the default/first page, but there were a bunch of different information pages there: Battery, Memory, Dalvik, Voltage, and Advanced settings, Time in state, wakelocks, General info, disk info.

And according to that, they "nuked" the whole menu to get rid of the "archaic" CPU code. Sure a lot of this information is visible elsewhere, but this menu gave you more detailed view than even some 3rd party apps give. I've only just recently found the page, but there's a few apps I could have skipped using and instead used the info from that if I had known about it...

Anyway, this is a bit offtopic, so...

I happened to see a new keyboard in the side bar that looks good: http://xdaforums.com/android/apps-games/app-clavis-keyboard-pc-tablet-keyboard-t3149500/

I'll give it a shot today and see if it still has the flickering, or if it's a viable replacement for our issues. The layout looks good, so here's hoping!

From what ive tested, the flickering is gone. it roes have some short coming, but seems VERY new and I think with some polish it will be an excellent keyboard.
[Nook HD, HD+ Android Development] amaces:
TWRP Official Now

Official TWRP images are live now for hummingbird and ovation; found out via Android Police ;)

http://www.androidpolice.com/2015/0...ne-2-lg-optimus-g-pro-bn-nook-hd-and-nook-hd/
[Nook HD, HD+ Android Development] neutronjeff:
Sweet. You guys are awesome.
[Nook HD, HD+ Android Development] TeutonJon78:
So, other than theme, are there any differences between omniROM/your version of TWRP and the official one?
[Nook HD, HD+ Android Development] belfastraven:
Great! I assume that the current TWRP live version is the same as your OFFICIAL version in the experimental folder? Thanks for supporting us with TWRP up until now.
[Nook HD, HD+ Android Development] amaces:
Well, for one, my recoveries use the same customized kernel as the ROMs. Although, most of those kernel changes don't really affect TWRP, except maybe the touchscreen tweak. By the way, you can (almost) replicate the newer theme on official TWRP by searching for the latest experimental (landscape) ZIP in this thread.

I assumed so, but the checksums are different… Nothing changed in the official repos, so I'm assuming it's another Jenkins run.

P.S. New experimental ovation build, with a bunch of interesting kernel additions, and everything rebased on top of 3.0.72 (testing stability).
[Nook HD, HD+ Android Development] bluecopper:
On the current build the Phantom touches have drank to booster juice. The regular remedy of locking and unlocking doesn't work. It even persists after restart of force power off. Installed swift keys and have had one case so far of the screen flickering and restarting after turning the tablet landscape. I have also had the screen going go haywire with distorted colored lines when switching between apps or switching from an app to home screen
[Nook HD, HD+ Android Development] lixxus:
Hi all,

firstly thanks to the developer for this build. I just wanted to ask ive got the hummingbird and noticed it is no longer part of dev tree.

i bought this device hoping to get a lot more android builds to come but it seems the oviaton is more focused on.
[Nook HD, HD+ Android Development] amaces:
Pretty odd… I've been using this exact build, and didn't run into any new bugs. For my use, it actually seems an improvement, but I will wait for more reports before deciding on the latest changes.

Please rephrase ;) If you're asking whether hummingbird is supported to the same extent, and its images are current, then yes, and yes. Many of the core changes are inherited by both devices, and I've kept the hummingbird tree in sync with ovation's… Of course, all this information is available in the OP, my GitHub repos. etc, but why bother reading right?
[Nook HD, HD+ Android Development] bluecopper:
Its not really new problems, just that in some builds the phantom touch isnt as prominent as well as the flickering and restarting. In this build it is very prominent to the point of frustration. I will however do a full wipe tonight wipe i get home from work and see how it behaves and update.
[Nook HD, HD+ Android Development] tebra:
I'm on 20150706 hummingbird build and phantom touches seem the same for me. Maybe a little better with 260 custom DPI.
[Nook HD, HD+ Android Development] lixxus:
sorry i meant officially by cyanogemod as cm11 was.

but thank you for all your hardwork and effort
[Nook HD, HD+ Android Development] twiztid_:
Neither Hummingbird, nor Ovation have an official CM12 build. This is as close as its going to be for a while until some issues get worked out.

I've tried out Jon Lee's SlimROM 5.1, and it seems he's got the flickering issue fixed (as well as the absence of a few other minor issues, like keyboard sounds ignoring the volume setting), so it seems the problems are fixable, and hopefully the fixes/settings are not too difficult to move over to CM. The black text on dark background on popup windows happens in Slim as well as CM as well, not sure where the source of the issue would be.

Super happy to see the work he's done, and excited for what he will do, but sadly I don't think I could use SlimROM due to the limited options under Settings.
[Nook HD, HD+ Android Development] bluecopper:
Can u guide me to that custom dpi let me see how that works on mine. Another thing, since moving from M12 the right edge of my screen rarely responds to touch. So Instagram most times I have to rotate to landscape to send messages in apps like email and such
[Nook HD, HD+ Android Development] twiztid_:
Settings -> Display & lights -> LCD Density -> 260.

It helped my nooks touch accuracy quite a bit.

Not sure if you mean moving from CM11 M(milestone)12 or CM12, but either way my right side touch is the same as it has been for as long as I've used it, on stock and CM10 til now.
[Nook HD, HD+ Android Development] Jon Lee:
It was the flashing green screen of death that mostly concerned me and that I set out to fix. I made some further improvement on Slim's graphics today just by enabling software sync (I had disabled it trying to get hardware sync up). This may help with what you describe. I would still like hardware sync. I'll put another test build and source up in a day or so.
[Nook HD, HD+ Android Development] citionecent:
D
[Nook HD, HD+ Android Development] bluecopper:
CM11 M12 is what I speak of. I was running that release for quite a while with only issue was a few phantom touches that would go away once I lock screen and reopen. Don't remember which nightly I installed and since then the right edge issue.

Density change didn't fix that error but will see how the Phantom touches go
[Nook HD, HD+ Android Development] ieatabiscuit:
Cm11 is phasing out, you'll see a new nightly about twice a month now. It's pretty much complete aside for translation updates. This thread is an effort to hammer out a cm12.1 build and we are the test monkeys. Basically, pick if you want slightly older but solid, or expiramental. I keep a backup of cm11 on hand, and roll a test run of this to satisfy my run m flashing addiction. [MENTION=4473900]amaces[/MENTION], does the official TWRP support f2fs? If not I'm keeping your home brewed 2.8.7 installed, it's been working perfectly for me.
[Nook HD, HD+ Android Development] amaces:
One of the goals with the experimental builds this week has been merging newer I/O schedulers, such as FIOPS, ROW, and eventually BFQ. The current experimental build is using ROW as default elevator with the standard 128 KB readahead (hummingbird may follow later today). Of course, during the couple of days spent figuring out what to backport, a few other interesting patches popped up, mainly related to unaligned access on ARM, and related optimizations. As usually, everything is on GitHub (the iosched branch, for now).

Definitely fixable, although still not trivial… It involves reverting much of the HAL changes in hardware/ti/omap4 to a CM11 state. [MENTION=5664601]Jon Lee[/MENTION] is definitely better with code ;) but I'll try to integrate these changes into the Git tree, at least temporarily. The long long term plan is still the jump to HWC 1.1/DDK 1.12…
[Nook HD, HD+ Android Development] keshabbhattarai126:
Mine also happened the same . Right edge of the screen doesnot respond to touch. I moved backed to cm11 and even stock rom but didn't fix.. I think now the touch sensors are damaged from hardware level.
[Nook HD, HD+ Android Development] Zippy Dufus:
Which of your repos/branches should I be using for the most stable build nowadays?

My current local manifest is below and I see activity in your android_kernel_bn_omap cm12 and iosched branches.

I'm getting reproducible flickers leading to a reboot when I use the Calendar widgit.

But, I am ecstatic with how well the Hangout Dialer now works!

Thanks.

echo '<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/bn/hummingbird" name="airend/android_device_bn_hummingbird" remote="github" revision="cm-12" />
<project path="device/bn/ovation" name="airend/android_device_bn_ovation" remote="github" revision="cm-12" />
<project path="device/bn/common" name="airend/android_device_bn_common" remote="github" revision="cm-12" />
<project path="kernel/bn/omap" name="airend/android_kernel_bn_omap" remote="github" revision="g-3.0" />
<project path="vendor/bn" name="TheMuppets/proprietary_vendor_bn" remote="github" revision="cm-12.1" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery-twrp" name="airend/android_bootable_recovery" remote="github" revision="cm-12" />
</manifest>' > $CROOT/.repo/local_manifest.xml
[Nook HD, HD+ Android Development] Jon Lee:
It should probably be said, so here's what I gather. Please correct me if I'm wrong.

The HardwareComposer Hashcode used in (this) cm lollipop was originally for the omap4430 kindle fire 2/otter, probably ICS.

The kernel was modified to emulate omap4430 graphics in order to use it. (Something to do with locking the GPU clock to 233mhz??). The PVR is also compiled at platform_version=4.0 for the api to match this hardware level.

I can understand why this was done as a stepping stone, as it was probably the easiest and fastest for him. (And also provides cross platform compatability for easiest maintenance).

The problem therein is that the omap4430 has a davinci chip for hardware video decoding (which I think works better BTW), But does not have the gc320 blitter/bltsville capability that ours does. Therefore his HWC is lacking blitter support. This provides hardware 2d acceleration, which is needed for our high pixel count.

Whew.

The "other" HWC we've been using in the past (cm 10/11), I guess is an original Jellybean version to match our ducati that someone at ti was so gracious to "leak". The big advantage... blitter. (Different clock structure as well, a conversation on the pros and cons of such would be interesting). The single GPU variant actually does benchmark better than our dual GPU variant (Separate IPU/DSP sides. IPU is used for camera, which we don't use). But if we ever switch to a newer ducati, we can have a SMP RTOS/sysbios....

But what I'm trying to say is that in this case, it's actually an " upgrade".

Like I said, if anyone wants to correct me... but that's how I understand it.
[Nook HD, HD+ Android Development] belfastraven:
6/12 hummingbird is working very well. Anything in particular you want tested?
[Nook HD, HD+ Android Development] amaces:
I don't know about stability, but feature-wise, the iosched kernel branch is currently the most complete. Sometimes, I remember to make the current branch default ;) You probably noticed… I rebase and modify history a lot, which would be a big no-no with normal shared repositories, but these are straight copies, and I like to keep the trees relatively free of cruft.

This is great information; thanks! I didn't look into some of this background history, and this provides enough motivation to work with the CM11 HWC. I only remembered that the UI fluidity was not as good in CM11, but maybe there were other reasons, and I'd certainly be OK with the trade-off.

Lots of changes to a core system, so give it a day or so to test stability. Otherwise, experimenting with readahead size could be interesting (Trickster MOD can change it, for example, and I wouldn't go past 512 KB). But yeah, it's a significant improvement once the system settles.
[Nook HD, HD+ Android Development] amaces:
Yay for motivation, I guess… Today's experimental build for ovation is using the previous HWC/PVR, and indeed, the flickers are gone, alas the UI is not as smooth (basically the familiar CM11 behavior). I still wanted to hold onto most other improvements that came with the switch to hardware/ti/omap4, so I've implemented a BOARD_USE_CUSTOM_HWC flag, such that only the HAL is replaced, and pretty much all changes are confined to our device repos.

Had [MENTION=5664601]Jon Lee[/MENTION] not elaborated on the history of these changes, I would've continued dismissing the CM11 HAL… Now, this doesn't yet incorporate all his changes beyond the CM11 HWC/PVR; that attempt will follow soon, and I'm hoping it'll bring at least the level of smoothness we got accustomed to in the normal builds. As usually, all these are synced up on GitHub.

P.S. There's another quick test in experimental, which is even better (tagged HWC11ONLY).
[Nook HD, HD+ Android Development] twiztid_:
Just installed it, and am testing now. So nice not to have any flickering. I was getting an occasional reboot with the last build after the screen would flicker and go black.

I'm glad to hear the recent info boosted your interest, keep up the great work!
[Nook HD, HD+ Android Development] Jon Lee:
You were quick!

I've made some changes that will help greatly...

I will upload some updated source shortly.

Basically in omap4/BoardConfigCommon.mk make sure you have this:

#TARGET_HAS_WAITFORVSYNC := true
TARGET_RUNNING_WITHOUT_SYNC_FRAMEWORK := true

Use this pvr-source which has an updated config.

http://www.mediafire.com/download/etrzigl6ufn8aa6/pvr-source.tar.gz

In the kernel config:

CONFIG_SYNC=y
CONFIG_SW_SYNC=y
CONFIG_OMAP2_DSS_FAKE_VSYNC=y

So far this is the combination I've found to work best thus far.
[Nook HD, HD+ Android Development] andtron:
Hi Jon,

Where do I find the kernel config file?

TIA

Found it in android-base.cfg.
[Nook HD, HD+ Android Development] starbright_:
About my Wifi issues (Page 38): This happens with multiple AP, after 3 clean installs - so I'm sure it is located inside NookHD+. I am not i a special range of WiFi freq ... You are right, for a log it is to late (back to CM11) , but maybe I am back in some time.

But one question OT: Without TB - how do you backup/recover you data? TWRP does it only for the hole partition....
[Nook HD, HD+ Android Development] wolfhelm:
I'm going to take a risk and ask here if anyone has any reason why something wont work on the Nook HD+ with either CM 11, 12 or 12.1 installed when the device meets all the requirements to run it.

Skylanders Trap Team from the google play or amazon store does not appear to want to run properly on this device. Interestingly, this meets all of the hardware and software requirements that Trap Team would require including BTLE. I can get it to install and even download the additional obb files but once I run it, it closes, half the time without a message, the other time it just says it has stopped. In reading the log cat it appears that it is having opengl driver issues, and possibly something to do with java, I unfortunately dont know enough about this to troubleshoot further, but if someone has any insight I'd greatly appreciate it. I've purchased this game for my daughter and while you dont need the skylanders to try it from the app store, the purchase includes the portal and the first 2 characters. (Again, you can play/try it from the app store without any purchase at all). I know BTLE is functioning as this connects to my BTLE devices as it should in all versions of CM (though in CM 11 I had to patch it myself to enable the BT 4.0 libraries).
[Nook HD, HD+ Android Development] sutty86:
Can I flash this from cm11 without SD via cwm recovery
[Nook HD, HD+ Android Development] TBueno:
That's what I did, and I didn't even have to wipe, so all my settings, data and profiles were preserved.
[Nook HD, HD+ Android Development] sutty86:
Where's the files
[Nook HD, HD+ Android Development] ieatabiscuit:
He's got a link in the OP, it'll take you to all you could ever dream of.
[Nook HD, HD+ Android Development] fvicente:
I was able to "dirty" flash this over the stable CM11, I had some issues with gapps but reinstalling gapps and letting everything update in the background overnight took care of all the FCs.

One question, I know this has been beaten to death for CM 10 and 11, but is trim enabled on this kernel?
[Nook HD, HD+ Android Development] agantai:
guys i already have TWRP twrp-2.8.7.0 installed on my nook hd but i noticed twrp-2.8.7.1 image is available,how do i update ?

edit:

done it

i used https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
[Nook HD, HD+ Android Development] amaces:
No More Alphas ;)

We've reached beta, I think; ovation is ready, hummingbird should be done in less than an hour. These builds are still on the experimental side, but if things work as well as they do on my Nook, no point delaying further. All the good stuff is on GitHub, but I do need to follow up with a long post soon.
[Nook HD, HD+ Android Development] agantai:
thanks
[Nook HD, HD+ Android Development] TBueno:
0714-ovation: flickering is gone, ladies and gents!

Just checked Google Keyboard and Google Photos, can't get the device to flicker or crash.

I'ts time to celebrate, all hail master AMaces!

[IMG="It's happening! (yes, THAT gif)"]http://i.imgur.com/s5wUufo.gif[/IMG]
[Nook HD, HD+ Android Development] amaces:
Well, let's not forget [MENTION=5664601]Jon Lee[/MENTION]'s explanation that started this latest ball rolling. I tend to assume newer, shinier things are better, and glossed over the composer changes many times… At any rate, together with the scheduler changes before the weekend, plus some of the updated PVR build configuration, I think we have something that resembles a real tablet now. Certainly, my initial goal of Nexus 7 (grouper) level smoothness or better, has been achieved ;)
[Nook HD, HD+ Android Development] twiztid_:
Is 0714 faster than the experimental "HWC11ONLY" build?

Also, not to pester, but does this mean that official builds are happening sooner? Or is there still just as much work to do before then?
[Nook HD, HD+ Android Development] pastordl:
Thanks to Jon Lee's research and Amaces work we have the best build yet (7/14). Typing this in landscape using SwiftKey and not even a twitch. Netflix, Crackle and Youtube all smooth as silk. Seems a bit quicker in loading apps too. Checked out the TWRP 2.8.7.1 an it too is rock solid. Glad you kept the material landscape design. Awesome pieces of work. My old NookColor is getting less and less use. :good::highfive::victory::laugh:;)::cool:

Edit: Still running great. BT keyboard and Memorex speaker connect and run fine. Tried running large number of apps and switching back and forth, again no problems. Everything is rock solid.
[Nook HD, HD+ Android Development] skyhawk21:
Well haven't tried any newer builds past 7/6 but every 5 seconds using keyboard or drop down notification menu and you get screen flicker and turn off all the dam time. How is this so much more unstable than cm 12 unofficial first stable build? I never had screen flicker or turn off glitches ever with keyboard or notification drop down or with anything using screen.

If this has updated drivers why so many issues that make using this as a daily driver impossible????

---------- Post added at 07:06 AM ---------- Previous post was at 07:03 AM ----------

By the way I have nook HD+ ovation
[Nook HD, HD+ Android Development] TBueno:
Flickering has been fixed in the latest build.
[Nook HD, HD+ Android Development] dk1keith:
Maybe you should try the latest build.....the one your on is fairly old. Especially since it seems like a lot of your issues have been fixed in the current build
[Nook HD, HD+ Android Development] sutty86:
does anyone wanna point me in the direction to download latest build? looked everywhere!
[Nook HD, HD+ Android Development] FirePsych:
First paragraph of the OP. Where "here" is underlined. That's a hyperlink to the ROMs and TWRP.
[Nook HD, HD+ Android Development] andtron:
If you'd not already known, OP means First Page of this thread :).

And the here is https://notredame.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww
[Nook HD, HD+ Android Development] asakurato:
Is box.com down?
[Nook HD, HD+ Android Development] extrem0:
Kind of. I could browse up to ovation folder, but once I clicked to download it it got down. It's being like this for the last hour.

Now it's back.
[Nook HD, HD+ Android Development] vinceweis:
This new build is amaces-ing. No flicker, smooth, etc. Thank you so much for the endless hours of work.

I am having trouble with chrome beta closing, but regular chrome works fine. Probably on my end, not wiping everything well. This ROM seems so good, I'm almost looking forward to a complete wipe and starting from scratch.

Edit: my fault, chrome beta works fine.
[Nook HD, HD+ Android Development] tebra:
To mute sound keyboard. Go to settings -> input -> AOSP keyboard -> settings
[Nook HD, HD+ Android Development] ieatabiscuit:
This has been working really well on my HD+. After about a good week or so, I'll test it on my daughter's nook HD. Also, THANK YOU LOADS for twrp 2.8.6! That little jewel made my day!
[Nook HD, HD+ Android Development] ieatabiscuit:
I have noticed that the system takes up a lot of RAM where on my phone running 5.0.1 the system uses about a quarter as much. It's really bogging things down. Had to remove all but essential gapps. Anyone else have the same thing going on? If not for this, it's pretty nice with minimal issues so far.
[Nook HD, HD+ Android Development] amaces:
That 25% number can't be right. These days, I see at least 500-600 MB used (total) on stock Nexus 4/5/7, and what they label as System is comparable on Nook HD+ (screenshot attached). That being said, these devices are severely RAM constrained; LP on 1 GB would be OK on paper, if it weren't shared with the framebuffer. With full HD, I'm only left with ~750 MB, although zRAM and KSM makes that bearable. Still, in my experience, memory management is much improved compared to CM11, and generally, at least since ICS, you should let the system do its own cleanup. Manually killing background apps/services will make it worse.

Now, if you want to do a more in depth comparison, look at something like dumpsys meminfo; the summary at the bottom is pretty easy to read:

Total RAM: 796116 kB (status normal)
Free RAM: 193315 kB (227619 cached pss + -74836 cached kernel + 40532 free)
Used RAM: 502105 kB (356789 used pss + 145316 kernel)
Lost RAM: 100696 kB
ZRAM: 8500 kB physical used for 25516 kB in swap (131068 kB total swap)
KSM: 45672 kB saved from shared 6184 kB
193372 kB unshared; 228640 kB volatile
Tuning: 128 (large 402), oom 122880 kB, restore limit 40960 kB (high-end-gfx)
[Nook HD, HD+ Android Development] ieatabiscuit:
Two points I want to make in light of this.

1: Your response time and how thorough you are with your own ROM is amazing.

2: I'll reflash, and see if maybe I mucked something up, and do that check. I'll let you know how it turns out.

I really liked how it ran overall, so if I can manage this little hiccup, I'll be very happy.