yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
I'll have to look into that... There's only a few apps I use between my phone and tablet, and half of them are either "sideloaded" (GMail) or just not updated anymore, so it hasn't been a real priority for me. Care to help me get started with a few links, or a tutorial?

Use to love Firefox... but it's just become so much slower and feels bogged down. The android version has some of the same issues as Chrome, but will admit it's more stable. However, both Chrome and Firefox for Android are FAR less stable than stock Browser. Maybe I'll give Firefox another go.
[Nook HD, HD+ Android Development] techdudepro:
You should use 1 Mobile Market. You can download the app store and use it as an awesome and near-perfect Google Play alternative. It has over a million apps, almost all from Google Play, even a few paid ones for free. But make sure to download an app that has a blue check mark (certifies that is is genuine) and a Google Play icon (verifies straight from Google Play; both "certifications" right under the app title). Highly recommend. I use this and stay out of Google's ecosystem (mostly) and it frees up some memory on my Nook since I don't have all of the Google apps running in the background (primarily Google Play Services).

P.S.-- to download the actual app store app, I had to open 1mobile.com in the android browser, iphone mode as the referrer to use the mobile site, otherwise it just downloads as a text file in the normal desktop website.
[Nook HD, HD+ Android Development] hajkan:
Hi

Could it be possible that the VPN is broken?

---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------

Try Lightning browser, it is available on Fdroid as well.
[Nook HD, HD+ Android Development] TeutonJon78:
It works just like any app store. https://f-droid.org/ They have the information there on how to add other repos for apps they don't support (which would really be up to the app developer).
[Nook HD, HD+ Android Development] TBueno:
Tried 0611-ovation and it feels very similar to 0607. Same smooth graphics, but "shutdown" now actually powers off the device.

Unfortunately, Chrome still produces artifacts when scrolling specific pages (ie this one, Amaces' Box folder, nyt.com). Couldn't find experimental boot image in ovation folder anymore. Flashing it didn't solve artifacts in 0607 anyway.
[Nook HD, HD+ Android Development] TBueno:
Just tried it here. Motorola wired headset and SOL Bluetooth, just crackling. :crying:

---------- Post added at 08:16 PM ---------- Previous post was at 07:35 PM ----------

Tried that too. Artifacts, artifacts and artifacts (aaargh), even if HW overlays are disabled. Will settle for (the awesome) 0530, thanks a lot for all your effort and time!
[Nook HD, HD+ Android Development] bluecopper:
Yes i'm still having the phantom touches, even after flashing the boot image. I'm also having blanking out of screen which causes me to force a shut off. Other times the screen goes heywire with interference like distortion. Found something weird with instagram since moving from the M12 release. In the notification are, when i tap the image that was liked or commented on there is no response. However if i'm using facebook messenger and as you know by default the chathead minimizes to the edge of the screen (in portrait mode) icon responds to touch.
[Nook HD, HD+ Android Development] js290:
Which adb version do you recommend? The .deb package is 1.0.31. I know newer TWRP recovery requires at least 1.0.32 to sideload.
[Nook HD, HD+ Android Development] TBueno:
Heads-up: if you're going to edit pics or create collages in Google Photos, disable HW overlays first. It's a bad case of flickering and reboot.
[Nook HD, HD+ Android Development] jt61:
Earlier I said...

and later it was reported...

I'm trying the 0611 version now, and it did power off the first time I did it, but subsequent shudowns resulted in immediate reboots.

For me, 0611 seems like the best yet. I'm not seeing the phantom touches I saw with 0530 or the flashing and crash/reboots I saw with 0603 and 0607.

I don't expect the battery issues I reported earlier to be gone, but haven't been on battery long enough to see that yet.
[Nook HD, HD+ Android Development] amaces:
I sat down and tested a couple of different headsets, and indeed, everything audio capture seems broken. I had assumed that at least Bluetooth should be different since its audio processing takes different paths, but whenever I try to use it in Hangouts, it breaks the whole Bluetooth stack somehow. Oh well, at least we have more data points for whenever this is our last major bug :(

I didn't even think about ADB versions since I've never run into this particular problem; now that I checked, it's 1.0.32 here, which must be quite old, since I don't recall upgrading in at least a year. Do you have access to a different computer/setup, to check which side of the connection is faulty?

Not sure what to say… After reverting a few changes, the kernel should be the same as in 05/30. There were a few notable changes with some core CM12.1 frameworks during the past week (e.g., base, av), but nothing likely to cause more overlay issues/underflows. In my use, with my hardware variant, I don't see any difference between the 5/30 build, and the 06/11 one (hummingbird may be different).

I will look at the different commits on the couple of kernel branches I was working on, and hopefully the regular builds tomorrow will be more stable.
[Nook HD, HD+ Android Development] adagiov:
Million thanks! I have sucessfully installed CM12.1 in my NOOK HD. Flashify app is easy to use in installing TWRP.

Having installed the cm12.1, Xposed does not work in my NOOK HD.

I have read through all this threads, but none of them works.

Could you provide the link of Xposed, that can be used in NooK HD.

Thanks.
[Nook HD, HD+ Android Development] neutronjeff:
I don't think Xposed is 5.1 compatible. (Yet)
[Nook HD, HD+ Android Development] windoge89:
There's an unofficial version that you can get that works just fine. I have it on mine with this rom
[Nook HD, HD+ Android Development] neutronjeff:
Link?
[Nook HD, HD+ Android Development] windoge89:
http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979
[Nook HD, HD+ Android Development] TBueno:
Thanks for looking into this even though you can't reproduce it in your own device. Maybe bluecopper and me are part of an (unlucky) minority?

I'm happy enough with 0530, but I'll try your next build and maybe help figure this out. Anyway, it's nice that you're keeping 0530-ovation available in your Box folder, it might be referred to as an alternative for those with flicker/artifact issues under newer builds.

[update] still get artifacts in Chrome in 0515. Google Photos warning still holds.

---------- Post added at 04:54 PM ---------- Previous post was at 04:46 PM ----------

Out of curiosity: how sure are you that Ovation will be "promoted" to official CM12.1?
[Nook HD, HD+ Android Development] adagiov:
Thanks. Indeed I have tried this before, but it did not work in my NOOK HD. And It did work in my Sumsung Galaxy S4.

After installing xposed-sdk22-arm-20150514.zip , xposed shows incompatible.

I guess the xposed does not work in NOOK HD, but Amaces mentioned in post #316, that he is also using xposed. So, might there is a way to get the xposed work in NOOK HD CM12.1.
[Nook HD, HD+ Android Development] windoge89:
That's odd. It works on my nook HD fine...
[Nook HD, HD+ Android Development] adagiov:
Thank you! I will reinstall the lastest rom 0615, and try again.
[Nook HD, HD+ Android Development] windoge89:
You should probably correct the "last updated" section in the original post to today
[Nook HD, HD+ Android Development] js290:
Forgot my desktop has adb 1.0.32 from the Android SDK install, and it can connect. 1.0.31 is no good for Nook HDs. Will update the jira case.
[Nook HD, HD+ Android Development] amaces:
Artifacts/glitches/flickers definitely happen on many HD+s (maybe most?). We know the reason (insufficient, or bad bandwidth management, leading to dried up panel buffers), and to reiterate, it's been my main focus, alas with only mild success. I'm only saying that I cannot find a reason for the worsening that you mentioned compared to the 05/30 build. That probably means there were changes in upstream CM, which affect some people's use cases. I also don't have many expectations from my device; any task beyond basic media consumption, anything frustrating, I save it for a big boy tablet ;)

Not very sure… Rationally, I don't see why we'd be left out, given that very similar AMZ devices (bowser class, OMAP4460/70) just got switched on, some even more underpowered than ours (tate). Gut feeling, however, is that official maintainer interest for the HDs is on the wane… Not sure why, since the Nooks are way more developer friendly, and we don't have to deal with all that camera nonsense in Ducati. Frankly, once I got over the learning curve, set up all the right tools, and can make my own builds whenever something exciting happens, my interest in official nightlies has also diminished. In conclusion, short of arm twisting, I have no idea whether we'll ever get that official status, or when that might happen.

Not sure why you have those issues; there were rare reports about missing livdvm.so on the Xposed thread, but the proposed solutions didn't look quite right. Either way, never ran onto that on either CM12.1, or stock LP. Maybe uninstall the Xposed managing app, wipe /system, then reinstall ROM, the Xposed framework (ZIP), and finally the 3.0 alpha2 APK. Latest compiled version of the framework is from June 9th: http://xdaforums.com/showpost.php?p=61265321&postcount=2896.

Every version of Xposed has been working as expected on CM12; it's certain modules that can cause problems. Certainly, don't use modules that expect stock UI elements (e.g., many parts of GravityBox), but plumbing-type stuff like Amplify works well.
[Nook HD, HD+ Android Development] TBueno:
That's what I thought too, since a while ago you said you'd be reverting post-0530 kernel tweaks.

Don't get me wrong, I was in no way complaining about the software or the device itself... It's a small miracle to see it running the latest android version with very little trouble. My unit has been far more stable than it ever was with stock, CM10 or CM11 ROMs. I don't hold high expectations against it either, I'm actually glad to see it do so much more than I thought it could. Audio 'chromecasting' for instance is a big bonus, since some more recent devices can't even do that over custom ROMs.

I mentioned the Chrome artifacts hoping it could indicate something wrong, thinking maybe other users could see those rectangles in other apps. But it's obviously easy to workaround this glitch, there are so many browsers out there.

BTW specific glithes/crashes are usually something you can live with, I guess every device has them. Before your ROMs, though, my HD+ at least would periodically reboot for absolutely no apparent reason, in any scenario imaginable. And for me that's what makes people enjoy and trust their gadgets less and less. So thanks a lot again for making these tablets even more useful than they were meant to.

I'm pretty sure we're far better off with your builds than "official" CM ones. Frankly, since CM abandoned stable/milestone builds, I've noticed a big slowdown in bug fixes. I don't believe many devices are seeing development as active and effective as yours. Still, maybe some official code could shed some light over our main bug...
[Nook HD, HD+ Android Development] belfastraven:
Thanks, amaces for the 6/15 hummingbird build. Everything is running well for me. The google play and or newstand widgets which had gotten a bit flakey (they would disappear) after thr previous build are back to running normally. I appreciate your building for a device you don't even own. How much disk space does a build use? I had seen something about 80G a while back and wondered whether that was still the case?
[Nook HD, HD+ Android Development] adagiov:
Thanks. The problem has been solved through reinstall the ROM and Xposed. The reason why I fail to install Xposed might be that I did not uninstall the old incompatible Xposed and installed the new Xposed directly.

Thanks for your detailed intepretation.

Also Thank [MENTION=6610558]windoge89[/MENTION] for your information.
[Nook HD, HD+ Android Development] amaces:
Not something that I control directly… That date gets updated automatically after every change, but apparently not when you double click to change the thread title. I've already messed up by including a date in the initial thread title, so now it's part of the thread handle, despite my latter attempts to change it. Welcome to the wonderful world of DevDB…

I like civilized, well thought exchanges. Besides, progress is made of discontent, right ;) About Chrome, I think it tries much harder than the AOSP Browser to push rendering activities onto GPU, and our drivers+proprietary blobs were made for another era… Those tiling operations probably involve many assumptions about the pace and coordination of the various memory buses… I suspect that other browsers based on Chrome's engine (Opera?) suffer from those tiling artifacts on this hardware. We can't really ignore these issues since Android M further deprecates the AOSP WebView by opening up custom Chrome tabs for that purpose. On top of that, other rendering engines are even more sluggish and inefficient.

Oh, the space requirements keep increasing, even more so from KitKat to Lollipop. As of now, I see about 120 GB tied into repo+out+ccache just for two devices. The incremental cost for additional 32-bit build is somewhere around 30 GB (21 GB + 9 GB ccache), and probably 40+ GB for 64-bit devices.
[Nook HD, HD+ Android Development] windoge89:
Ah ok. Thank you very much for your work. I appreciate that someone ported cm12.1 instead of the official cm11
[Nook HD, HD+ Android Development] js290:
Any tips on installing the NOOK:Read eBooks & Magzines app? Play store says it's incompatible with the device, both hummingbird and ovation. I'm running the 20150615 build, BTW.

Apparently, there's a way to do it by modifying the build.prop:
[Nook HD, HD+ Android Development] leapinlar:
You can get the app here and install it yourself:

http://xdaforums.com/showthread.php?t=3050405
[Nook HD, HD+ Android Development] js290:
Thanks for the tip! Is there a way to install an apk such that it does not get wiped on a factory reset? I guess gapps gets installed in /system such that it requires a full format to wipe rather than a simple factory reset.
[Nook HD, HD+ Android Development] amaces:
It's crappy that B&N is still doing that… Whatever business reasoning they had initially, it's definitely not worth it now. Anyway, messing with the device name, even temporary, on individual basis, is not a good solution. Sideloading, and in particular, [MENTION=349198]leapinlar[/MENTION]'s suggestion, would be the way to go.

Yup, installing/moving it to /system is definitely possible, either manually, via ADB, or with specialized apps - Titanium was able to do it, if I recall correctly. While a system app will be available after wiping /data, keep in mind that every ROM update cleans /system, and only brings back things that have addon.d backup support, which most GApps packages have.
[Nook HD, HD+ Android Development] wanderso:
Bluetooth broken in CM12.1?

Amaces,

I looked at your DevDB stuff, which is totally kernel related. And as I have said elsewhere, the stability of your Ovation kernel is excellent - the flashing screen problem is gone, after untold generations of software. Congratulations!

The Bluetooth problem may not be kernel related, as I have seen issues reported with CM12.1 on other platforms. And it is not just audio-related. On my Ovation running the 0615 build, my Azio Bluetooth keyboard pairs just fine (as does my Plantronics M1100 earset) but no data comes through.

Since this may not be a kernel problem, is there somewhere, say at Cyanogenmod, that this can be reported as a bug in the more general CM environment?

Thanks for the great work on the Ovation!

wanders
[Nook HD, HD+ Android Development] king200:
Raccoon v3.5 - An apk downloader for Google Play http://xdaforums.com/showpost.php?p=53147630&postcount=1

Very useful for apps. Sometimes good for restrictions by country too.
[Nook HD, HD+ Android Development] faxmachineanthem:
First, I want to echo everyone else's thoughts and say thanks for all the hard work. My HD+ is running smoother and faster than it ever has, with no noticeable bugs. (I'm running the 5/30.) I recently started running greenify with the xposed options enabled and that seems to sped things up even more.

The only downer versus CM11 has been battery life. I'd estimate I'm only getting ~60% of the screen time that I was getting with CM11. Has anyone else felt that way? Have newer builds improved vs the 5/30 or are they likely to improve in the future?

Thanks again for the truly great work.
[Nook HD, HD+ Android Development] amaces:
SELinux Permissive->Enforcing

Heads up, Hashcode has re-enabled enforcing mode in kernel/sepolicy for al his AMZ devices. Since that's a pretty good idea (default in AOSP, forces better written sepolicy, etc), I mirrored his changes, and am testing for inclusion in the next full builds. Xposed/most modules will still work, and hopefully, there won't be any major problems.

If you want to test these changes in advance, I've uploaded new kernel images in the respective device folders (Settings > About tablet > SELinux status should say Enforcing afterwards). As always, source changes are synced to my GitHub repos.

I wouldn't put the blame squarely on CM12 just yet… It's only certain BT profiles that don't work on the HDs; unidirectional music streaming (A2DP) works fine. It's the headset profile that breaks the BT stack somehow, which means that BT digital input ends up processed through the same buggy software as built-in mic or wired headset. There are many layers where the audio capture breakage could occur; I've been looking into three: AudioPolicy, HW driver glue, and the OMAP kernel/ABE sound API. CM's AudioPolicy kit is probably mostly OK (otherwise you'd have all those broken phones), but I am looking into any mismatches in our Nook-specific code.

For bug reporting, there's always jira.cyanogenmod.org, although given that the HDs are not officially supported beyond CM11, your report will likely be ignored.

Definitely agree that battery life took a hit compared to CM11, however it doesn't feel like 40% lower. Truthfully, I haven't tested it properly, given that I'm often flashing test images, but I would think that major kernel issues would show up during sleep. So far, just looking at the graphs/coarse stats, the HD+ seems to sleep as well as before, with about 80% in deep sleep with my usage.

Screen time/active use is noticeably lower as you discovered, and I'm not sure whether our kernel, CM12, or AOSP is to blame more.

Kernel-wise, we do know that: 1. we're pushing the various memory buses and the video system to the limit, plus the GPU is often lit-up in the higher performance states, and 2. the zRAM/LZ4 trade-off, with constant compression/decompression happening on large chunks of memory must keep the CPU awake much longer. Anyway, seeing how other devices behave on Lollipop, I still suspect that more blame is on stock code+CM12, which is good, since improvements are more likely. Android M is definitely good news for battery life.
[Nook HD, HD+ Android Development] wanderso:
Thanks, big time, for the attention to this. Love the work you are doing.

wanders
[Nook HD, HD+ Android Development] belfastraven:
'm running the SE Linux Enforcing boot image on Hummingbird. No problems so far with my normal apps--NYT, Kindle, Google Newstand, chrome-beta, as you would expect . Perhaps the AMZ devices are going to nightlies; my understanding was that for that to happen, SELinux had to be Enforcing.

thanks again.
[Nook HD, HD+ Android Development] danrb40:
Kernel installed and working fine here! Many thanks for your hard work!
[Nook HD, HD+ Android Development] amaces:
Huh, I didn't know about SELinux Enforcing being a stringent requirement, but you might be right. The bulk of those AMZ changes happened just before jem & tate were sent to nightlies. I'll try to push the sepolicy stuff to CM12 upstream as well.
[Nook HD, HD+ Android Development] king200:
Experimenting with different rom, where changing selinux was necessary, used app, "[APP]SELinuxModeChanger" http://xdaforums.com/showpost.php?p=47397991&postcount=1

I would guess it might work here too.
[Nook HD, HD+ Android Development] amaces:
Mostly Good Things…

Turns out that SELinux Enforcing is a bigger headache than anticipated… It only became apparent with a full build that it breaks Wi-Fi (and BT) because fix-mac.sh is trying to remount /system to write the initial wl12xx calibration data. With a simple boot image, that calibration data wasn't wiped, so I happily ignored those SELinux denials. It'll be fixed eventually (SuperSU, other devices modify system files in Enforcing), but we'll have to keep Permissive mode for now.

Otherwise, good news: Hashcode will focus on the HDs next, so official nightlies are in the cards, and will happen fairly soon™ :)

Also, can someone check whether location works in Maps? If it doesn't, I think I fixed it; the more modern Play Services (GMS) location provider was missing from our device-specific overlays. Since GApps are used by a large majority of us, this was a no-brainer, but it'll help even if you stick to purely AOSP solutions (see https://f-droid.org/wiki/page/com.google.android.gms). New builds will be ready later tonight, hopefully.
[Nook HD, HD+ Android Development] Jon Lee:
fix-mac.sh runline could possibly be moved to recovery/postrecoveryboot.sh...
[Nook HD, HD+ Android Development] mhunt13:
I'm running your 0615 build on my HD+.

Just tried Maps, and it did find my current location, using Wi-Fi. I then turned on GPS, and again it found current location. So it worked either way, Wi-Fi or GPS.

I did install the Banks gapps 6-13-15 with your Rom, maybe I got the most current Play services location provider thru Banks???

Was running your 0530 build before, don't think Maps location worked, and I had used PaGapps with that.
[Nook HD, HD+ Android Development] amaces:
That would only run when booting into recovery, right? We need something to regenerate the calibration data in /system/etc/firmware/ti-connectivity/ after every ROM update. Either way, based on the trends/commits for other devices, recovery would also switch to Enforcing, so remounting/writing to system would be equally problematic. Still, I'm sure there's a magic combination of SELinux permissions without allowing labeledfs:filesystem remount to fix-mac.sh (that is prohibited by current upstream SELinux policies; kernel compilation aborts).

Interesting, I haven't checked in a while and didn't want to reinstall an old ROM for this. Maybe Maps is properly checking com.android.location.fused or com.google.android.location now. Or, maybe CM12 un-broke those older location providers. Otherwise, all Lollipop GApps packages should include the newer GMS providers. P.S. There's no proper GPS in any Nook, just a software stub, so it's all going through the coarse Wi-Fi location databases.
[Nook HD, HD+ Android Development] Jon Lee:
I believe when you power down or reboot out of recovery (which would work after flashing a ROM). There would still be an issue of insmoding the necessary Wi-Fi modules. It already remounts bootdata rw.
[Nook HD, HD+ Android Development] bluecopper:
Just installed the 06/15 with the SeLinux img and it broke my wifi too. Keeps saying "turning wifi on"
[Nook HD, HD+ Android Development] bluecopper:
Trying to install the SELinux mode changer but having issues. SuperSU telling me i need to update binary but it keeps failing. Any ideas? Really need to get the wifi working again
[Nook HD, HD+ Android Development] mhunt13:
You should be able to re-flash the 0615 Rom (don't use the boot img in the download ovation folder).

I'm using 0615 build on my HD+, no Wi-Fi issues......