yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ieatabiscuit:
I generally go for TK Pico GApps. It's literally just the play store, and they do a decent job keeping it up to date. Like I said, CM GApps is not bad, it's clean, and complete. I just like to have less unused features, and to be able to install/uninstall the rest as I want. I haven't tried most of the others though, the TK GApps has me pretty happy. Also, for heating issues, it gets hotter when using it while plugged in, but that's because of the power management hardware being in that same region with the processor. You'll have a thermal resistor getting toasty, and a processor getting toasty too. The fun is doubled if you are doing something that drains a lot of battery so then you are charging almost as fast as you are consuming. That gets it nice and hot, and there's not really anything to be done there aside from setting it down to let it do it's thing. As for the heat from the processor, [MENTION=4473900]amaces[/MENTION] is doing what he can for good reason, but I doubt there is much to be done, reason being that there is no real heat shielding in the case, so you are exposed to it more. Not so much that it is over hot, but that the heat can bleed into other components, and that you can feel it more than with other more shielded devices. The inside of an ovation is pretty barren, and simple. There's not much room for anything more than what is in there.
[Nook HD, HD+ Android Development] TeutonJon78:
There is also the nice new Open Gapps. Which is a little nicer in concept than TK Apps, since it's all being done on Github, and doesn't really on 1-2 people that might leave if/when they lose interest again.
[Nook HD, HD+ Android Development] Zippy Dufus:
Thanks - opengapps

Thanks for bringing it to our attention! http://opengapps.org/

I haven't tried it yet but will for next build. (And maybe even try to build it myself.)
[Nook HD, HD+ Android Development] FirePsych:
I believe I'm currently using Open Gapps and have had no problems.

I say "believe" because I went through about a week when my Nook HD+ was having issues and I was trying to isolate the problem. I was trying different GAPPS packages.
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm running it now, so far as I can tell, it's he same as I usually use, but more up to date, and easier to find with support for kk ROMs. I'll likely make this my default gapps now.
[Nook HD, HD+ Android Development] moviepoppo:
Thank you!

I have no clue of programming and have been a troll here first taking verygreens ROM for Nook HD+ plus a few years back and now your ROM for my daughters hummingbird. Awesome work and thanks for contributing to the universe ;)
[Nook HD, HD+ Android Development] bluecopper:
Thankjs guys i'll surely be checking this out.
[Nook HD, HD+ Android Development] granny smith:
I am using the HD. Do I have to use TWRP to get GAPPs to run? I have CWM 6.0.4.6 and ever since the 8/3 build I have been unable to get the GAPPs to run after I install them in CWM. After my HD loads from flashing installing them, I get a whole bunch of errors like "Unfortunately, Google Play store has stopped" or "AOSP keyboard has stopped" etc. The tablet is unusable because the errors keep popping up as soon as I dismiss them. I'm doing a clean install and wiping the system, data, cache and dalvik cache every time. I have used opengapps, TKgapps, Paranoid Gapps. I want to use only the Pico Gapps. Is my problem the recovery I'm using or is it because I'm not using the full GAPPs file? Or both?
[Nook HD, HD+ Android Development] twiztid_:
I think CWM is just showing its age. Try installing twrp, might need to wipe and install just cm then install flashify and flash the twrp recovery image. After that, you should be able to install gapps without any problems.
[Nook HD, HD+ Android Development] aoleary:
SD Card image with TWRP instead of CWM

Hi all.

Is it possible to have TWRP on the sd-card image instead of CWM?

I have the reboot into recovery issue, so I tried to install the latest version via CWM, but I get bootloops..

Thx
[Nook HD, HD+ Android Development] twiztid_:
Using the 8/16 build, Power off works, and fully shuts down my HD+, but Reboot to recovery is not working.

I can't get ADB working, from what I've read I need a newer ADB client (newer than the one in LeapinLar's thread apparently) that will work on Android 4.4.2/.4 and newer. Haven't had a lot of time lately to look, so I'd be appreciative if someone could link me, but I'll try to make some time if not.
[Nook HD, HD+ Android Development] neutronjeff:
Sorry for the boob question, but if I'm doing a full wipe to install 0816 from TWRP 2.8.7.1 on Ovation, do I need to do any special formatting?
[Nook HD, HD+ Android Development] amaces:
I think the new builds yesterday are a better compromise between heat and smoothness. Each batch since August 3rd has had a slightly different combination of certain build flags, but now that I researched some more, some of these newer flags were unneeded or detrimental.

You should use the built-in bug reporter here, even after we have official builds. Same eyes watching things on JIRA, and on this thread ;) Now, we've discussed this couple of times, and as you discovered yourself, the lack of BT audio input is not due to the BT stack, but rather to missing hooks in our new LP audio HAL. We'll figure this out eventually; otherwise, the keyboard/HID profile should work, unless you have a very fancy proprietary one.

Well, there you go; extreme heat is a terrible thing for many other reasons (e.g., permanent battery damage, accelerated chipset wear, etc). You gotta find ways to better cool the device… fans, AC, bags of ice? Still, that kind of erratic touchscreen behavior should never happen.

Thanks for the heads up; I definitely like idea of these GApps, but you gotta be careful when dirty flashing on top of another package. They typically have all sorts of clean-up scripts that may introduce conflicts. Also, last time I tried PA clones, all sorts of issues happened, and now I have a duplicate device in Play Store settings. Granted, this package looks more modern, and well maintained.

Of course, recovery/TWRP is just another highly customized Android distribution. It's not trivial though to update verygreen's SD card images… The internal layout hasn't changed since at least CM10, and the purpose of those external images is to bootstrap the eMMC (internal) ROM and recovery. I still think that old CWM is usable for simple image flashing, as described in the OP, so your bootloops are probably due to something else. Of course, I understand that unreliable reboot-to-recovery is a major problem, but I don't see fancy external SD TWRP images happening anytime soon…

Why not download the newly released official tools/SDK 23, extract the adb/fastboot binaries for your platform, and replace your current versions?

Boob question accepted ;) No need for special formatting, but switching /data and /cache to F2FS is highly recommended. Search this thread, and the previous CM12.0 stuff for more details.
[Nook HD, HD+ Android Development] Zippy Dufus:
Compiler question

I was going to ask if you have your repos up-to-date but I see that they appeared so.

However, I also see where you are playing with OpenWRT and the gcc 5.2 compiler. Just for fun, I tried to compile this ROM with gcc 5.1 and got an error "Fatal error: invalid -march= option: `armv7-a' ". Could you point me to where to look in Cyanogen to set the compiler options?

BTW, my 08/17 build appears to be the best yet! Thanks.

_______________________________________________

Off topic:

I once built a working OpenWRT ROM for this camera with gcc4.9 but the latest gcc5.1 build is too big this device :(

Being a hacker, my goal is to get a working gcc5.1 build for this ROM and then see if I can build the 5.1 or 5.2 toolchain itself and compile a working ROM. I've accomplished this for Linaro. :cowboy:

Again, this is just for fun. Any performance gains are not that appreciable.
[Nook HD, HD+ Android Development] TeutonJon78:
You'll want to be careful with that. Most GAPPS packages aren't compatible with each other.

Yeah, all of them recommend doing a full system wipe and usually a data wipe before switching packages.
[Nook HD, HD+ Android Development] swaaye:
Any chance of getting 1.5 GHz for Hummingbird somehow? It is a shame that the official CM rules get in the way of just letting this happen easily.
[Nook HD, HD+ Android Development] tebra:
I change the kernel governor to "performance" on my hummingbird and it much smoother now with small impact on battery
[Nook HD, HD+ Android Development] bluecopper:
The extreme heat was right after flash and the device wasn't even in its case.
[Nook HD, HD+ Android Development] srgibbs99:
Is there a "What works and what doesn't" summary for this ROM somewhere? I am thinking about upgrading from CM11, but I am wondering how "beta" this really is. Good for a daily driver on the HD+?
[Nook HD, HD+ Android Development] asakurato:
Deleted
[Nook HD, HD+ Android Development] TBueno:
From the top of my mind:

Doesn't work:

shutdown and reboot to recovery (for some users, but physical buttons combo still does the job)

screencasting (it's currently audio only)

pairing some specific bluetoooth gadgets

Works: everything else

If you're worried about usability and stability, this "beta" is better than any CM11 build I ever tried, you'll very likely be better off by upgrading.
[Nook HD, HD+ Android Development] king200:
My power button and battery use are strange.

If I turn the HD+ off completely while holding the power button and then plug into the charger, it boots up. If I turn off while attached to charger it stays off but no charging light. I believe it is charging. Charging while system is up appears to take longer and battery discharges faster.

A quasi observation that leads me to a theory. My power button was behaving with some normality until one time when I tried to software boot into bootloader. After that, I now have the most common, non functional power button. I created the EMMC very early on, when it first came out, with Verygreen image and formatted MicroSD card. This is recollection and that's fading but maybe someone can look into into it.
[Nook HD, HD+ Android Development] ieatabiscuit:
That's actually the norm. Nothing's wrong, but from my own observations, if there's no charging light, there's no charging. One would think that if it's plugged, it's charging, but they have deceived us with this logic.. It will try to turn on when you plug it, even if it's dead. If it's not dead, it boots, of it's dead, it will go to the charging icon screen. As for slower charging while running, that's because it's being used while charging. Best to turn the screen off, and let it charge over night. Also, there IS a setting in CM that allows you to disable the feature that turns the screen back on when you plug/unplug the device. There's also one that stops the N button from turning the screen on, which I like, but that's just me. Long story short, there's a lot of querks that a Nook has that seem screwy, that's because B&N made it that way. Most mobile devices are not really designed to be turned off so much anyway, it really puts it behind on updates, and they seem to universally HATE being fully discharged.
[Nook HD, HD+ Android Development] Zippy Dufus:
Build installation problems?

Hello,

Anybody having trouble building since 08/21?

I'm getting an error on my 08/21, 08/22 and 08/23 when I try to install them: E:Error executing updater binary in zip '{ROM file name}'

To debug:

I've upgraded to the latest TWRP v2.8.7.0 which didn't help.

Extracted and compared the updater binary from both 08/17 (last working) and 08/21 - same checksum.

Performed a complete wipe with reformatting the filesystems - no luck.

I got a similar error when I attempted to install the open-GAPPS-mini package. At least it had additional error messages about not enough space so I backed off to the open-GAPPS-micro package and it installed fine (with my last working 08/17 ROM).

So I'm suspicious that CM may have bloated up past a threshold but some of my older builds have much bigger ROM zip files.

Any ideas?

==//==

P.S. I noticed that in the open-GAPS the corporate Exchange email protocol has been moved from the default email app to the Gmail app. I'm not happy with that because when I attempted configure Yahoo mail in the Gmail app, Google wanted complete access to my Yahoo email so I will probably get double the amount of annoying advertising. "Don't be evil" :rolleyes:
[Nook HD, HD+ Android Development] wanderso:
I've got logs and I want to report a bug, but all I get when I try to use the built-in bug reporter is a blank pane in my browser window (I've tried Chrome, Firefox and IE, just to be sure). The feature request window seems to be working, but the bug reporter doesn't like me. How can I make friendly with it?
[Nook HD, HD+ Android Development] js290:
I usually do

adb bugreport > bugreport.out
[Nook HD, HD+ Android Development] swaaye:
Is there some new way to configure the Performance settings now that the omniscient CM leaders have decided that we don't need that page anymore?
[Nook HD, HD+ Android Development] amaces:
They basically ruined the ability of TWRP (or any other current recovery, except theirs) to flash CM12 ROMs after August 19th… Look at the recent commits in android_build and android_bootable_recovery. I'm not saying WTF, but they're cherry-picking major plumbing changes from the yet unreleased M/6.0… I suspect that a majority of people use TWRP, if they can, so I'm surprised this hasn't exploded yet.

Anyway, after spending the afternoon looking through these changes, I decided that updating TWRP with some of these M commits makes the most sense at this point, given the massive changes in upstream CM. Look through my recent changes in https://github.com/airend/android_bootable_recovery/commits/cm-12. These extra features are nice, but mostly irrelevant for us currently, although there's potential for a 30-40% reduction in ZIP size. Right now, I'm only concerned with updating our recoveries for continued CM12 compatibility; that updater binary error is gone, but I still need to make sure flashing happens properly.

In conclusion, another weekend with broken upstream things… I guess we were lucky with the 08/19 builds, generated right before all this craziness started ;)

Ugh, you're right, the DevDB bug reporter is completely broken right now, and I know it used to work back in January at least. Sometime, XDA features stop working (multi-quote?); not sure whether it's their breakage, or I did something unorthodox with the thread, but we'll figure it out.

Not sure that the exact Performance settings in CM11 can be brought back (short of reverting to old unmaintained code), but I did see references to lighter performance "profiles"; will investigate soonish. Still, those settings were limited, and were removed for good reasons, so why not look into something like Trickster MOD?
[Nook HD, HD+ Android Development] ieatabiscuit:
I test drove their recovery on my phone, it's looking a lot like some CM version of a touch screen enabled CWM, and has little advanced functionality at a glance. I quickly reinstalled TWRP, but now I see why I couldn't get updates to work after the disappointing test run.
[Nook HD, HD+ Android Development] Zippy Dufus:
Let me know when you get a bootable TWRP image and I will be happy to try it.

I grabbed the the recovery.img from my 08/24 build and flashed it with dd. This resulted in booting to a black screen so I had to futz around around with preparing a bootable sdcard to dig myself of the mess :(
[Nook HD, HD+ Android Development] amaces:
The new recovery images are in experimental, although no guarantee about flashing things properly.
[Nook HD, HD+ Android Development] Zippy Dufus:
That's OK, I'm fearless (and stupid) and haven't hard-bricked a device yet. ;)
[Nook HD, HD+ Android Development] pastordl:
Installed and tried various things and everything seems ok so far. Did have to reset all settings. Boots fine. Only thing left to try is installing a post 8/19 ROM for Ovation. I'll be your huckleberry for trying that when next ROM is out.
[Nook HD, HD+ Android Development] belfastraven:
Hummingbird also working OK . Will try flashing when new rom is available.
[Nook HD, HD+ Android Development] swaaye:
Trickster looks good. Looks like there are other options as well.

Any chance of 1.5GHz for Hummingbird? I actually went back to a CM11 build by verygreen because his kernel has 1.5 GHz enabled. It's nice to have. I realize that the reason it's not currently included is again Cyanogenmod doctrine though.
[Nook HD, HD+ Android Development] Zippy Dufus:
[MENTION=4473900]amaces[/MENTION], I see that you have been working on the recovery. I tried to build last night and got some errors probably from syncing while you were updating your repos.

I'll be patiently waiting for you to finish.

Thanks for all your efforts!
[Nook HD, HD+ Android Development] amaces:
Yeah, I was working on the LZMA compression feature before I upload new (smaller) images. I'm up to 1.5 TB, 75% of my Box quota this month :(

Everything worked as of last night, but I have yet to push a small compilation fix in TWRP's libminzip. Otherwise, those recovery images in experimental don't need changes, so that's good. You need them for any build after August 19th, or you know, build your own after I sync everything in a few hours. As of now, the HDs are probably one of the few devices with updated/working TWRP ;)

True, I've been a busy beaver, trying to fix all the annoyances with my digital things… Anyway, did you only update GCC on the Linux host? You need a complete cross-compilation toolchain, ideally optimized for our ARM/Cortex-A9 CPU, to replace the one in prebuilts/gcc. It's not trivial, and the benefits may or may not be worth it, but here's a good resource: http://xdaforums.com/showthread.php?t=2098133. I was planning to test the differences once there's a Linaro GCC5 optimized for Cortex-A9, and our sources have stabilized.

With OpenWrt, switching to a newer GCC is easy since they already have all the hooks in the build environment. By the way, the size issue is not GCC5's fault; my MIPS/musl builds are actually smaller than with 4.8. You're likely pulling much newer (and definitely larger) kernel and package sources now, plus your libc implementation matters a lot, but if you carefully disable optional modules/features (e.g., ppp stuff, if not needed) at build time, it should still fit into 4M. One of my routers has very similar specs and chipset (rt305x), and everything works great.

It's not really upstream CM that prevents us; our kernel alone has almost a thousand extra commits, and although I'm always rebasing on upstream, I'm OK diverging when it matters. Still, overclocking the hummingbird kernel hasn't even been mentioned before, and I have always assumed the slightly slower clock rate is OK given the massive reduction is pixels. At least, I've been told things are running smoothly on the HD.

Now, the HD+ has pretty much the same chipset at stock 1.5 GHz, so it's likely OK to overclock hummingbird, although there may be good reasons for the manufacturer selecting 1.3 GHz (e.g., heat dissipation in a smaller package, different/lesser CPU binning, etc). If I implement this, it'll be 1.3 GHz default, with the ability to overclock on your own. You can either point me to pre-existing code, or I'll investigate whenever I remember next.

P.S. Checked again, and the Bug Reports feature doesn't work on other threads either, so it must be a XDA DDB outage. Hopefully, they'll fix it soon.
[Nook HD, HD+ Android Development] TBueno:
CM download pages now provide links to recovery images. It looks like they're really moving away from both CWM and TWRP.

By the way, has anyone ever tried the Cyanogen recovery on these devices?
[Nook HD, HD+ Android Development] swaaye:
Jon Lee had Ovation overclocked to 1600 MHz and he posted some code for that years ago. Verygreen had Hummingbird at 1500 MHz by default on some old kernels as well. I've actually been looking into this myself and have built CM12.1 for Hummingbird but I really don't know what I'm doing when it comes to working with the source and github.

I agree that 1300 MHz should be default. I'm not sure how much benefit there is to +200 MHz but it should at least speed up web page rendering a touch. On the old Verygreen kernels at 1500 MHz the device doesn't seem to get any warmer but I don't tend to keep it at full utilization for extended periods.

Here is a thread Jon made about overclocking 4470 for Ovation:

http://xdaforums.com/showthread.php?t=2627202
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=4473900]amaces[/MENTION], 8/26 hummingbird build installed with experimental TWRP so far runs fine. It still will not shut down or boot to recovery. Booting into recovery from the power menu now seems to hang the machine at a blank screen. I notice that this rom is SELinux Permissive. Was that on purpose :) ?

reboot reecovery works from terminal. Will try flashify, etc tomorrow

As of 4/27 a.m. , Reboot to recovery works from terminal, flasify, AND power menu,

Power off works from power menu and from recovery.

Chrome beta keeps stopping, regular native browser is fine.
[Nook HD, HD+ Android Development] Zippy Dufus:
Almost!

My build almost completed but had an issue near the end. I'm wondering if I am missing a development library on my virtual build machine?

[SIZE="2"]creating userdata.img...
Running: mkuserimg.sh -s /tmp/tmpmalzCq/data /tmp/tmpDnrFiR ext4 data 13824409600 -T 1440639794 /tmp/targetfiles-V5YEgL/BOOT/RAMDISK/file_contexts

++++ extrauserdata ++++

++++ cache ++++

done.
[33mPackage OTA:[0m /home/android/out/target/product/ovation/cm_ovation-ota-3ce89644f2.zip
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 1691, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 1587, in main
extra_option_handler=option_handler)
File "/home/android/build/tools/releasetools/common.py", line 738, in ParseOptions
if extra_option_handler is None or not extra_option_handler(o, a):
File "./build/tools/releasetools/ota_from_target_files", line 1560, in option_handler
from backports import lzma
[COLOR="Red"]ImportError: cannot import name lzma[/COLOR]
build/core/Makefile:1715: recipe for target '/home/android/out/target/product/ovation/cm_ovation-ota-3ce89644f2.zip' failed
make: *** [/home/android/out/target/product/ovation/cm_ovation-ota-3ce89644f2.zip] Error 1
+ local ret=2
++ date +%s
+ local end_time=1440659510
+ local tdiff=19950
+ local hours=5
+ local mins=32
+ local secs=30
+ echo[/SIZE]

I grabbed someone else's GCC5.1 build (arm-eabi and arm-linux-androideabi) from Github as a starting point. If I can get a working NookHD+ build, I will use this information as a starting point to build it myself. I monitor christopher83's thread as my cue to go to the Linaro site to get their latest source tarball and build it myself. Their 5.X release is a little slow in coming and I am looking for something to do. :cowboy:
[Nook HD, HD+ Android Development] dbrickg:
just dd'd the latest "experimental" ovation TWRP, 2.8.7.3 and am making a backup. As soon as that's done I'll try installing the cm-12.1-20150826 zip ....

ah, ok, backup is done. installing the 8/26 zip... done. rebooting... optimizing apps... and it's back! Hurray! Looks good so far....

Just looked at Settings / About tablet, and noticed that it says "SELinux status permissive". I thought we'd gotten to the "enforcing" stage. Sorry, I'm not keeping up very well. Too busy with my stupid phone.

Oh, hey, just tried rebooting to recovery, and it works!!! Yay!
[Nook HD, HD+ Android Development] swaaye:
I followed this

http://wiki.cyanogenmod.org/w/Build_for_hummingbird

And added TheMuppets repo for the proprietary blobs. Built first try.