yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] TBueno:
BToolkit

I don't know about you, but bluetooth in my ovation/CM13 grew increasingly finicky, until it became simply inoperative.

After some forum browsing and app trial and error, I found BToolkit. UX is eclair vintage, but it does the job: i can now connect and disconnect my keyboard, mouse and, surprisingly, my Tracks Air headset whenever I please.

Funny how reliable BT is and probably always was, CM's interface just seems unable to tap into it properly.
[Nook HD, HD+ Android Development] dxxvi:
How to have ssh installed in Android?

I used CM on my nook hd+ before and I had ssh in the terminal emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm). Now I switch to AOSP and don't have ssh in terminal emulator anymore. Does anybody know how to have it?

Thanks.

---------- Post added at 04:31 AM ---------- Previous post was at 04:28 AM ----------

I second that bluetooth in CM13 is really unreliable. I had to remove the bluetooth device and link it again every time I want to connect. However I haven't tried BToolkit yet but switched to a corded headphone.
[Nook HD, HD+ Android Development] KenBradshaw:
Just a question, Installed the Marshmallow Android to my Nook HD+ and trying to play from it to the HDTV via HDMI Cable. Doesn't work or I missed a setting somewhere. From my reviews on this issue many reported last good CM-Android for anyone was using the KitKat Version? Is there something I missed?
[Nook HD, HD+ Android Development] sasmith-129:
HDMI works for me on my Nook HD+ (ovation) using an older MM build: cm_ovation-ota-MMB29T.160127

It stopped working for me on some subsequent build (not sure which one) but I kept a TWRP backup of this build for when I need to use HDMI (typically when travelling).

You should still be able to find this build in the obsolete folder. Good luck!
[Nook HD, HD+ Android Development] lmacmil:
About ready to give up on CM13 and go back to CM11 snapshot. Behavior seems to get stranger every day. I'll tap an icon and get an all black or all white screen and it will sit there for 10, 20 or 30 seconds. Sometimes I have to pull up the open programs list, close it and start again. Just too many lags and pauses. While I can appreciate the effort that went into this, for me, it isn't ready for prime time. Oh well...
[Nook HD, HD+ Android Development] ajislav:
What version are you on?

Have you tried factory reset (possibly with data restore using an app like Titanium Backup)?

Does the issue persist after reboot?
[Nook HD, HD+ Android Development] lmacmil:
I am on the MOB30J.160530 CM build. Have not tried a factory reset yet. I don't reboot very often but I will try that next and then the factory reset if rebooting doesn't help. Thanks.
[Nook HD, HD+ Android Development] lmacmil:
The reboot seemed to help but still seeing long app loading times. I stared at a blank white screen for 18 seconds before the NY Times opened.

Sent from my Nook HD running CM13 (Android 6.0.1)
[Nook HD, HD+ Android Development] snoozer854:
I am currently running the aosp_hummingbird-ota-MOB30D.160423 since probably the 1st of May on my Nook HD & it has been running flawlessly.

Bluetooth, WiFi all working fine. Even some weird battery issues that I have had off & on for quite a while are gone.

I gave up on the CM 13 versions a while back to many issues. aosp version seems to fit my needs

I am pretty much sticking to this release.

"If it ain't broke don't fix it"

Thank you amaces for keeping my old Nook running.
[Nook HD, HD+ Android Development] TBueno:
Try making some room in internal storage. This used to be an issue for me in older ROMs.
[Nook HD, HD+ Android Development] lmacmil:
Good to know. I may try that before giving up on MM. Thanks.

[/COLOR]

I got internal storage down to 66% full from 80%. We'll see what happens. Thanks.

Sent from my Nook HD running CM13 (Android 6.0.1)
[Nook HD, HD+ Android Development] TBueno:
Judging from the comments under this article, I'd guess the app itself is to blame.
[Nook HD, HD+ Android Development] hajkan:
Installed aosp on ovation and getting "unfortunately the process com.android.phone" has stopped. not sure what to issue is but how do I pass that pop up?
[Nook HD, HD+ Android Development] MrPuddington:
Gapps Install Issue

Hello

I am trying a fresh install of CM13 on my Nook HD+, and I just couldn't manage to get gapps to installed. There were many error messages of different kinds for the different gapps packages.

But in the end this worked:

1. Install trwp-3.0.1-0-ovation.zip

2. In TRWP, wipe art cache, data, cache, system

3. Install cm_ovation-ota-MOB30J.160530.zip

4. Install open_gapps-arm-6.0-pico-20160729.zip

5. Reboot

I hope that helps.
[Nook HD, HD+ Android Development] sasmith-129:
FWIW, I tested HDMI on subsequent builds and it continued to work on the 160208 and 160222 builds but no longer worked on the 160314 build.
[Nook HD, HD+ Android Development] rtarv321:
As several have mentioned, I am going back to CM11. I installed CM13 & Pico gapps. While the install worked ok, I only have 34mb of free system ram. Titanium BU will load & restore but I get an error message stating that there is not enough memory to backup any files. I have the Nook HD+ with 32g ram. I think the upgrade path in the future is limited due to only having 1g of system ram.
[Nook HD, HD+ Android Development] cjpicci:
Before you give up on Titanium Backup with cm13, I think there was a certain way to get it to work, had to select storage a certain way for Marshmallow. Sorry I can't remember the specifics right now, but I know I got it to work.
[Nook HD, HD+ Android Development] rtarv321:
Thank you for your advice. You are spot on. Although Titanium Backup was setup using my micro SD card, using the "auto detect" button, the card was not writable. I had to go into preferences,backup settings,backup folder location & click on "storage provider, document storage".then choose " use current folder". Once I did this the location changed to "external storage/titanium backup". Works great now. I have question. I performed a backup of recovery using TWRP. In the log I noticed that my data partitions were f2fs & system partitions were ex4. Does this sound correct? Thank you for your help!
[Nook HD, HD+ Android Development] vinceweis:
That sounds correct. The file systems can be changed in twrp but as I recall, the advice has been to use f2fs for data and cache which you must have done in twrp in the past.
[Nook HD, HD+ Android Development] jerry.tk:
I had the same problem with musb_autosuspend_wake_lock and rx_wake both on aosp and cm. What finally helped me was this:

- Go to extended WiFi settings and set "Wifi active in sleep mode" from "Always On" to "Charger Only"

No more kernel wakeups after that. Hope that helps!
[Nook HD, HD+ Android Development] sasmith-129:
Also, yes, the system partition should remain ext4.
[Nook HD, HD+ Android Development] rtarv321:
My data partition is f2fs, but the cache partition is ext4. If I change the cache partition to f2fs using TWRP, do I need to wipe all or just cache. Will I need to restore recovery file or will the other partitions remain the same? Thank you in advance for your help
[Nook HD, HD+ Android Development] sasmith-129:
Just change the cache partition to F2FS using TWRP and reboot. That should be it!
[Nook HD, HD+ Android Development] rtarv321:
Thank you, your advice worked great. Cache is now f2fs.
[Nook HD, HD+ Android Development] mafioso16:
Works flawlessly most of the times, but sometimes on AOSP the Wifi suddenly disconnects and just reconnects upon entering Wifi settings.

Also, would it be possible to modify the kernel for overclocking?

Best wishes, and thanks for sharing your great progress!
[Nook HD, HD+ Android Development] snovvman:
I tried both aosp_ovation-ota-MOB30M.160614 and cm_ovation-ota-MOB30J.160530 before settling on AOSP. On CM, I saw a weird WiFi issue where it does not reconnect coming out of sleep. I haven't seen the problem with AOSP. Thank you [MENTION=4473900]amaces[/MENTION] for sharing your work.

I saw that there is a newer 160708 AOSP version in the Experimental folder. Is it stable?
[Nook HD, HD+ Android Development] snovvman:
Duplicate, deleted.
[Nook HD, HD+ Android Development] rtarv321:
CM13 has been working great, but I was thinking of changing to AOSP to gain a little more ram. The tablet is mainly used by the grandkids for games. If I decide to change to AOSP, can I dirty flash the AOSP with TWRP. Will I need to flash with opengapps? Will I lose root & have to reroot. I have read where several of you have switched. Thank you in advance for all of the help!
[Nook HD, HD+ Android Development] mmnspeed:
Have been using the latest build of cm13 for over a month now.I'm amazed at how much better it is compared to the official cm11.I use the nook only for reading.I was having issues reading some formats and the loading times were very long.Everything works much better in cm13.I mostly use xodo reader and I found multitasking much better in this rom.Call it placebo effect,but I can't explain how I am able to use even chrome with this rom.Earlier it was unusable.Might be a new lighter build by google,I am not sure.I had decided last month that I will change my tablet,but since I use it only for reading,this rom seems to have deferred that decsion.Some bugs are there,but nothing that can be considered major.Thanks amaces for keeping this device alive.
[Nook HD, HD+ Android Development] Zippy Dufus:
Flash failed in CM13 build

Hello,

Has anyone tried to build cm13 lately?

I'm getting the following errors when I try to flash the ROM which appeared to build OK. I tried in two successive days.

My last build on 07/08 reinstalled OK.

Any ideas?

I:Set page: 'flash_confirm'

I:Set page: 'flash_zip'

I:Set page: 'flash_zip'

Installing '/external_sd/Software/cm-13.0-20160807-UNOFFICIAL-ovation.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts

I:Legacy property environment initialized.

Target: Android/cm_ovation/ovation:6.0.1/MOB30Z/52adbc5e4f:userdebug/test-keys

minzip: Extracted 3 file(s)

mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory

about to run program [/tmp/install/bin/backuptool.sh] with 2 args

run_program: child exited with status 127

about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args

unmount of /system failed; no such volume

performing update

open "/dev/block/bootdevice/by-name/system" failed: No such file or directory

script aborted: system partition has unexpected contents after OTA update

Patching system image unconditionally...

Verifying the updated system image...

system partition has unexpected contents after OTA update

I:Legacy property environment disabled.

E:Error executing updater binary in zip '/external_sd/Software/cm-13.0-20160807-UNOFFICIAL-ovation.zip'

Error flashing zip '/external_sd/Software/cm-13.0-20160807-UNOFFICIAL-ovation.zip'

Updating partition details...

I: Data backup size is 2136MB, free: 6911MB.

I:Set page: 'flash_done'

​
[Nook HD, HD+ Android Development] belfastraven:
I am running a cm13 build that I built after syncing on Friday evening. I had gotten a couple of errors the day before and did get

system partition has unexpected contents after OTA update

but not the other errors you have: I did notice though that after trying to do the install that that the recovery TWRP 3.02 seemed not to be able to properly mount various partitions. I had been messing around with testing various tool chains (kernel was built with UBER 7--live dangerously :) ) and thought maybe that was the problem. I did an absolutely clean install with the system I built Friday night (using the default toolchains) --I fomatted data and wiped everything except for my external SD card, and then installed the rom and lastest pico opengapps. I haven't tried to build today.

FWIW
[Nook HD, HD+ Android Development] lmacmil:
I've noticed the wifi connection drops while in sleep mode. I have to manually reconnect more often than not. Did not have this problem with CM11.

Sent from my Nook HD running CM13 (Android 6.0.1)
[Nook HD, HD+ Android Development] objw:
Icons disappearing and wi-fi disconnected on reboot/power off

I was wondering if there are any fixes or settings for two issues I am having on reboot and power off/on.

I just installed cm_hummingbird-ota-MOB30J.160530 and open_gapps-arm-6.0-pico-20160804.

Everything installed fairly easily and without major problems (little issues with gapps being too large, but used pico and installed fine).

One issue that I am having is some of the shortcut icons I create on the "desktop" disappear on reboot and power off/on.

I am pretty sure it i the same ones disappearing. Same thing happens when I made them again x 2.

The other issue is the wi-fi is not connected on reboot and power off/on.

To start it I hit the wi-fi icon (from the top right drop down) and it connects and seems to work fine after that (...until restart&power off/on).

The icons problem is more of a pain then the wi-fi, but any help on either or both would be appreciated, Thanks.
[Nook HD, HD+ Android Development] Zippy Dufus:
All's well!

Got a good build! Must have been a hiccup when syncing for my previous unsuccessful build. I saw one of the common BN project repos updated for this build.

The new Updating Apps startup dialogue in interesting!

Cheers!
[Nook HD, HD+ Android Development] belfastraven:
Yes--its much more useful than seeing App 1, App 2, etc., I wish we had had it a couple of years ago when cm occasionally did get stuck compiling something:)

Here's the commit if you haven't already found it.

https://github.com/CyanogenMod/android_frameworks_base/commit/59350eaf491df7cac496a38443e9d3fb8b715137

Perhaps I'll try building with the new uber tool chains again--(7 for kernel and 5.3 for the rest of the rom). I've been trying to figure out the HDMI issues as well as the power-off issues but not having much luck. :(
[Nook HD, HD+ Android Development] crudepasta:
Lost Data Partition

I decided to try and upgrade my CM12.1 to the latest, and something went awry. The install of TWRP 3.0.1-0 went OK, as did cm_ovation-ota-MOB30J.160530. However after I installed pico Gapps, it locked up. Using the recovery SD, TWRP ends up in a boot loop, but I can boot into CWM and get adb access. It seems that the data partition somehow got corrupted (it cannot be mounted). Is there any way to recover the data partition from adb?

Thanks
[Nook HD, HD+ Android Development] Zippy Dufus:
I've only been able to successfully compile the kernel with my 5.2 and 5.3 Linaro toolchains. The entire 5.2 ROM builds but won't install and the 5.3 toolchain has weird assembly language compile errors that I have no clue on how to resolve.

Regardless, the Geekbench3 results are consistently better for the 5.3 kernel than for the 4.9 default (445/825 versus 440/815), not that this is noticeable.

Also, this ROM is the best EVER for this device. Kudos [MENTION=4473900]amaces[/MENTION] !
[Nook HD, HD+ Android Development] belfastraven:
Can you boot the internal recovery (TWRP )? (I mean holding the power and nook keys for 4 seconds or so) If you can, see if you can mount data. I'm not sure that CWM will mount data or cache if they are formatted to f2fs, which might be your problem there. If recovery is apple to mount the partitions, I would suggest doing a factory reset, and then installing the rom and pico gapps immediately, one after the other. There could be something wrong a particular gapps, I guess, what was the date of the one you were using?
[Nook HD, HD+ Android Development] crudepasta:
After things went awry, if I try to boot into TWRP (either the one I installed on eMMC or off an SD card), the TWRP screen comes up but stays locked for about 30 seconds, then the nook reboots. It goes to TWRP and repeats the boot loop regardless of whether I am holding the "n" or not on boot. However, I can successfully boot into CWM off the recovery SD if I select that as opposed to TWRP.
[Nook HD, HD+ Android Development] belfastraven:
if you can run adb shell, you can try to fsck.f2fs the data partition

f2fs.fsck /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata

for an f2gs partition, or by using e2fsck if it was formatted as ext4. There might be a problem with f2fs.fsck not being available in CWM. If that is the case, I think you would have to format data, to clean up the partition. I believe that should work from the device, or from adb shell:

recovery --wipe_data

I hope you have a backup of anything crucial...
[Nook HD, HD+ Android Development] flieswithhawks:
I have been running CM11 monthly builds on this device for some time and it has always seemed clunky/slow with most operations. I only use this device as an e-reader with Moon Reader Pro and it would not render many PDFs very well or sometimes would cause the tablet to freeze and the app to crash if the PDF had a lot of images on a page. This was very frustrating and I was going to look elsewhere for a decent e-reader until I found this ROM, and lemme say I'm glad I didn't buy another device.

The May 30 build on my Nook HD is absolutely solid so far and has breathed new life into this device. I don't use Gapps or even Wi-Fi as I really only read eBooks/PDFs offline. Nova launcher is much more responsive and everything opens much quicker and overall it feels much smoother than KitKat.

I also play a homebrew Magic the Gathering clone called Wagic (from www.wololo.net) and some of the images for the cards are high resolution. This game does not lag at all now and is a lot more enjoyable because of this.

Thanks so much to the dev for this build as it finally seems my Nook HD is "humming" away at it's true potential. I'll be looking forward to future builds.:)
[Nook HD, HD+ Android Development] hv6478:
I used the CM May 31 file with the most recent version of pico gapps, installed at the same time but, very importantly, wiped dalvik cache, data and cache AFTER both flashed, BEFORE rebooting system. After the boot screen was done, 92 apps optimized successfully then I got through the startup wizard with 0 errors, running like a champ! Best this thing has ever been.

Thank you for the work!

P.S. TWRP flickers quite a bit after a while of being in recovery (or maybe after a specific wipe or something, can't tell). Never hinders any performance though, as it seems.
[Nook HD, HD+ Android Development] mckinsey01@gmail.com:
I have to say that the latest CM13 is working out nicely, the builtin browser isn't crashing and I've only had one small issue where it froze up. This one is a winner! I was just about to give up on my trusty hd+, glad I waited.
[Nook HD, HD+ Android Development] crudepasta:
Thank You!!! I booted into the legacy CWM, and recovery --wipe_data from adb shell did the trick. Apparently that command is different than the data wipe command available from the CWM GUI. I was able to then successfully boot into TWRP< reformat the data partition into f2fs and install the latest images.
[Nook HD, HD+ Android Development] Zippy Dufus:
A new build issue

Hello,

I have a new build issue which cropped up on my last two attempts. Below is from 08/15.

Any ideas?

...

...

target StaticExecutable: init (/home/android/out/target/product/ovation/obj/EXECUTABLES/init_intermediates/LINKED/init)

Install: /home/android/out/target/product/ovation/system/lib/libc++.so

target StaticExecutable: adbd (/home/android/out/target/product/ovation/obj/EXECUTABLES/adbd_intermediates/LINKED/adbd)

target StaticExecutable: healthd (/home/android/out/target/product/ovation/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd)

vendor/cm/charger/healthd_board_cm.cpp:335: error: undefined reference to 'gr_set_font(char const*)'

collect2: error: ld returned 1 exit status

build/core/executable_internal.mk:75: recipe for target '/home/android/out/target/product/ovation/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd' failed

make: *** [/home/android/out/target/product/ovation/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd] Error 1

make: *** Waiting for unfinished jobs....

make: Leaving directory '/home/android'

+ local ret=2

++ date +%s

+ local end_time=1471321166

+ local tdiff=11097

+ local hours=3

+ local mins=4

+ local secs=57

++ tput colors

+ local ncolors=256

+ '[' -n 256 ']'

+ '[' 256 -ge 8 ']'

+ color_failed='\e[0;31m'

+ color_success='\e[0;32m'

+ color_reset='\e[0m'

+ echo

+ '[' 2 -eq 0 ']'

+ printf '\e[0;31m#### make failed to build some targets '

#### make failed to build some targets + '[' 3 -gt 0 ']'

+ printf '(%02g:%02g:%02g (hh:mm:ss))' 3 4 57

(03:04:57 (hh:mm:ss))+ printf ' ####\e[0m\n\n'

####​
[Nook HD, HD+ Android Development] 32square:
[MENTION=4473900]amaces[/MENTION] Would it be possible to get a new precompiled build based on the 20160816 ZNH5Y snapshot?
[Nook HD, HD+ Android Development] Uldiniad:
Having trouble completing builds without errors again...

[MENTION=4473900]amaces[/MENTION] Might be worth checking what is causing this as it has been around for two days now. I have a very similar issue to that of [MENTION=5672278]belfastraven[/MENTION] and [MENTION=3651088]Zippy Dufus[/MENTION]. Any help is appreciated.

Symlink: /home/capedcrusader/android/system/out/target/product/ovation/recovery/root/sbin/losetup -> busybox

vendor/cm/charger/healthd_board_cm.cpp:335: error: undefined reference to 'gr_set_font(char const*)'

collect2: error: ld returned 1 exit status

make: *** [build/core/executable_internal.mk:75: /home/capedcrusader/android/system/out/target/product/ovation/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd] Error 1

make: *** Waiting for unfinished jobs....

Symlink: /home/capedcrusader/android/system/out/target/product/ovation/recovery/root/sbin/ls -> busybox

make: Leaving directory '/home/capedcrusader/android/system'
[Nook HD, HD+ Android Development] belfastraven:
As I mentioned to [MENTION=3651088]Zippy Dufus[/MENTION], I think there may be a problem with the location of the minui.h file that includes the original function definition. The make file shows that bootable/recovery should be added to the path for looking for include files, but I am wondering whether that file is not actually being used since we are actually compilling and linking recovery-twrp. I have copied the minui.h file from the bootable/recovery/minui directory into the vendor/cm/charger/ directory to see if that helps. If not, I try finding the proper file in the twrp recovery tree and changing the makefile to include that directory.
[Nook HD, HD+ Android Development] flieswithhawks:
Yes please. I 2nd this.
[Nook HD, HD+ Android Development] Zippy Dufus:
"Effective procrastination"

I haven't done any serious investigation yet as I usually wait a few days and try again.Obviously there was some recent tinkering upstream somewhere but I didn't see changes in [MENTION=4473900]amaces[/MENTION] repos that would account for this.

I've been busy building for my new Samsung Prime device and when I run into issues I build this device to verify that my build environment is OK.

I am concerned about the direction and support from Cyanogen because they apparently sacked their developers. :mad:

I'll try again in a few days.
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=7350242]Aelfwin1996[/MENTION], [MENTION=3651088]Zippy Dufus[/MENTION], copied to [MENTION=4473900]amaces[/MENTION]

To get latest cm builds to work, either

move the recovery-twrp folder out of the bootable folder

or

use one of the older, stable branches for

<project path="vendor/cm" name="CyanogenMod/android_vendor_cm" />

I built with cm-13.0-ZNH5Y and it was fine.

The latest builds are configured to use that gr_set_font function which is actually defined in the Recovery/minui/graphics.cpp file. We don't normally compile that file since we build with TWRP. I thought maybe we could point to some directory the twrp-recovery directory here

in vendor/cm/charger/Android.mk

LOCAL_C_INCLUDES := \

system/core/healthd \

bootable/recovery

but that function actually seems not to exist for twrp.

Not sure what the best longterm solution for this is.