yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] king200:
I tried open_gapps-arm-6.0-nano-20151106.zip with the dirty flash of 11/05 and it did not work well. I did wipe system before the install.

The setup wizard or something else ran and FC so I could not get anywhere. Perhaps if I used the pico version, it might have worked. I did not use on a clean install.
[Nook HD, HD+ Android Development] Monfro:
I confirm that deleting the line makes sound work again on Ovation too.

Last build seems smoother than previous.

You are improving this rom really fast, thank you!!

These Gapps(and also Banks) are working well:

https://www.androidfilehost.com/?w=files&flid=41043

Of course aosp keyboard and play services fc, until you give all permissions
[Nook HD, HD+ Android Development] hemeboy:
I installed the AOSP ROM successfully but no matter gapps version I used I get the "unfortunately setup wizard has stopped" fc problem; any suggestions, thanks
[Nook HD, HD+ Android Development] Monfro:
Try Gapps link I posted before.

AOSP keyboard and Play Services will FC on setup wizard, but you can ignore and go ahead until home screen appears.

Then select another keyboard you flashed before, give all permissions to Play Service and everything will work well.

With Titianium Backup I managed to restore all my apps: they are all working well except 2
[Nook HD, HD+ Android Development] hemeboy:
I used the Slim_zero_gapps.ALPHA.6.0.build.0.x-20151106 build. I am able to fix Play Services FC with giving all permissions but still have the "setup wizard has stopped" FC.
[Nook HD, HD+ Android Development] belfastraven:
The open gapps 6 versions specifically say that they require a kernel patch to avoid the force close problem, and give a link to the patch. I see that [MENTION=4473900]amaces[/MENTION] has put the open gapps nano zip in the experimental folder, so perhaps a future kernel will include the patch. As [MENTION=1876393]Monfro[/MENTION] had said, it is possible to get gapps going. (I have managed to get to the apps setting and disable the setup wizard, e.g.) I think everyone should read the op, though. It was originally requested that we test without gapps...
[Nook HD, HD+ Android Development] amaces:
GApps Fixed ;)

The GApps issues were pretty complicated indeed, and were fully fixed only this morning; try the fresh package I uploaded in experimental. The Open GApps site will probably have fixed packages tomorrow, or whenever they regenerate them.

Not sure that anyone else has fully fixed packages yet (beyond freshest Open GApps sources, that is). The permissions for Play Services were a minor issue compared to the other things that had to be updated. Either way, the AOSP keyboard doesn't crash anymore, but you may get a few FCs in the very beginning.

Not a kernel patch, but a frameworks change is recommended (AOSP-only though). There was some confusion about the extent of these changes (plus, CM versus AOSP, see https://github.com/opengapps/opengapps/issues/159#issuecomment-154805982), and the Open GApps Wiki was just updated this morning.

I will prepare updated builds later today, but the GApps package in experimental should work with the ROMs in there.
[Nook HD, HD+ Android Development] hemeboy:
Thanks, now working including Google keyboard. Pinpoint location not working in Google Maps but this was a problem with early builds of KK and Lollipop.
[Nook HD, HD+ Android Development] Tschumi:
Am I the first to test the 8/11 version? Just some quick observations;

The home button works and wakes the device.

External storage gets mounted properly.

The keyboard no longer force closes.

Google services stop force closing after given permissions.

The provided google apps work fine.
[Nook HD, HD+ Android Development] belfastraven:
I have been running with the 11/08 hummingbird and 11/08 gapps from experimental for about 13 hours--. I have found the same as tshumi, except that

home button does not wake my HD (but it hasn't for at least a few months--perhaps other HD owners can weigh in here)

I have had a couple of reboots and "settings" has closed a few times.

I also have found that I've had to tinker with permissions at times, e.g. gmail would not by default let me attach files from some storage directories, but rather than reporting a permission problem would state that it couldn't attach an empty file. I'm not sure that even all of the google apps are marshmallow "friendly" yet.

From dmesg log: (happens a few times)

[ 94.214172] omap_cpu_thermal_manager:sensor 75400 avg sensor 71275 pcb

[ 94.221130] 61000, delta 10445 hot spot 85845

[ 94.226013] omap_cpu_thermal_manager: hot spot temp 85845 - going into monitor zone

[ 96.029724] omap_cpu_thermal_manager:sensor 69200 avg sensor 72615 pcb

[ 96.036773] 62000, delta 10806 hot spot 80006

[ 96.041870] omap_cpu_thermal_manager: hot spot temp 80006 - going into safe zone

In logcat I note several Fatal errors of the type "heap corruption detected by dlfree"-- usually seeming to have something to do with dex2oat .

[MENTION=4473900]amaces[/MENTION], I'm happy to send logs if you think I am seeing something different from you. You seem to be making great progress!
[Nook HD, HD+ Android Development] vertycall:
First impressions from marshmallow alfa on Nook HD+ :

Pros - fast, responsive, relative stable.

Cons- some random crashes - system UI has stopped, a few crashes with Kodi playing HD video, can't install super su, cant get VPN to work (probably due lack of permission)

Used latest nano gapps dated 10.11.2015 from OpenGapps and 11/08 Ovation.

As usually - amaCing work ! Thanks Andrei !!!
[Nook HD, HD+ Android Development] asakurato:
For supersu, use latest beta version
[Nook HD, HD+ Android Development] FirePsych:
For Setup Wizard FC, on MM alpha ROMs, I've done this on my Nook HD+ and Nexus 7-2012

In TWRP, Mount System

Then, go unto the System folder >Priv App > Setup Wizard

Delete that file.

Reboot
[Nook HD, HD+ Android Development] Mac Hosehead:
I made the leap from LP to Marshmallow on hummingbird. Installed Supersu and Gapps. My VPN service is working now. Looks nice so far, TYVM.

-MH
[Nook HD, HD+ Android Development] smileyint:
Hi

I noticed the auto rotate did not work though.

Cheers,

smileyint
[Nook HD, HD+ Android Development] Zippy Dufus:
Build help?

Hi [MENTION=4473900]amaces[/MENTION],

I'm having trouble building marshmallow with my script below.

Here is the error that I am getting. Do you see anything wrong with my script? Is the init correct (I tried both cm-13.0 and cm-12.1)? I did do the sync over the existing repo instead of deleting it. (BTW, my similar script for your cm-12.1 mysteriously errors out now but I'm now interested in building marshmallow.)

Also, I may not be understanding your guidance in post #15. Any ideas?

HOST_OS_EXTRA=Linux-4.2.6-300.fc23.x86_64-x86_64-with-fedora-23-Twenty_Three

HOST_BUILD_TYPE=release

BUILD_ID=LMY48Y

OUT_DIR=/home/android/out

============================================

Checking build tools versions...

"ebtables is disabled on this build"

find: 'dummy': No such file or directory

find: '../../../../../../external/hamcrest/src': No such file or directory

find: '../../../../../../external/junit/src/org': No such file or directory

find: '../../../../../../external/hamcrest/src': No such file or directory

build/core/base_rules.mk:154: *** platform_testing/tests/jank/webview: MODULE.TARGET.APPS.UbWebViewJankTests already defined by frameworks/webview/chromium/tests/UbWebViewJankTests. Stop.

make: Leaving directory '/home/android'

#### make failed to build some targets (04:30 (mm:ss)) ####

real	4m40.204s

user	1m9.630s

sys	1m26.421s​

My build script:

#!/bin/sh

export CROOT=/home/android

export LOGFILE=$CROOT/Logs/sync_build_nookhd+.M.$(date +'%y%m%d-%H%M').log

export LANG="" # https://bbs.archlinux.org/viewtopic.php?id=201281

echo $$ > /tmp/BUILD-IN-PROGRESS

time {

#set -x

export USE_CCACHE=1

java -version

cd $CROOT

# Set up local manifest

rm -rf $CROOT/.repo/local_manifests.xml

echo '

{paste in contents of https://raw.githubusercontent.com/airend/android/marsh/default.xml}

' > $CROOT/.repo/local_manifests.xml

# initialize repo

repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1

repo sync --force-sync

# repo sync

# hack to update get-prebuilts

cp -f $CROOT/bin/get-prebuilts $CROOT/vendor/cm/get-prebuilts

cd $CROOT/vendor/cm

./get-prebuilts

cd $CROOT

. build/envsetup.sh

breakfast cm_ovation-userdebug

time brunch cm_ovation-userdebug

sync

} 2>&1 | tee -a $LOGFILE

rm -f /tmp/BUILD-IN-PROGRESS
​
[Nook HD, HD+ Android Development] Monfro:
Thank you Amaces for explanation and new 15/11 build...Unfortunately I can't test it until tomorrow evening :(
[Nook HD, HD+ Android Development] uberchoc:
Okay I got Syslog and ran it. If you look through the logcat logs--I attached two here--you will find the issue around the 22:56 - 22:57 region, I believe. Also somewhere in 23:16, you should find it. I might be incorrect, please look through with more experienced eyes, I would very much appreciate it. Cheers.
[Nook HD, HD+ Android Development] KyJelly69:
Some crazy things are happening. I will leave it plugged in to charge then return later to find that it has turned off. I can verify that it was off by looking at battery stats where it shows a large gap. This has happened on other versions as well.

i attached a syslog too :)
[Nook HD, HD+ Android Development] Shadowpain:
In my nook (ovation) i noticed that this happens when i lower the brightness to zero and then close the screen . As long as i close it with at least 15%+ brightness there is no problem (wakes up normally)

It might be a coincidence though cause it only happened 2-3 times and i haven't tested it
[Nook HD, HD+ Android Development] highlandsun:
Thanks. I had it on apps+adb before. Setting it to apps-only worked. But how do I get adb working now? "adb devices" on my PC says the device is offline.

Never mind, I got it. My adb binary was too old, using a newer one works.
[Nook HD, HD+ Android Development] belfastraven:
see attached if you need more detail let me know.

thanks--it wasn't there last time I looked.

It's certainly easier to use this way :)
[Nook HD, HD+ Android Development] belfastraven:
[

In my experience, after installing the rom and finding that something can't get root, if I change the settings to "none", and then change the settings back to "apps & adb" everything will work. Perhaps changing the setting in any way is what causes the setting to be "noticed".
[Nook HD, HD+ Android Development] belfastraven:
Hopefully, [MENTION=4473900]amaces[/MENTION] will see this, also. One more question, though. What is your setting for "keep WiFi on while asleep" in the advanced WiFi settings?

Also , if you are using Syslog, you should check the "scrub potentially personal infomation from the logs " box.
[Nook HD, HD+ Android Development] uberchoc:
Thank you very much for your help.

Wi-Fi is always on during sleep. Also, I did check that box.
[Nook HD, HD+ Android Development] herges:
Hi All,

Both cards are not very old, the contacts are clean and the speed rating is U1 (according to this https://www.sdcard.org/developers/overview/speed_class/ this is equivalent to class 10 and there is only one faster class U3). In response to ieatabiscuit, I have since then gone back to CM 11 with the hack of swapping the sdcard and have not attempted CM 13 again but if you are still seeing this issue on the latest build then this is not addressed yet.

I have tested both cards using a phone and a card reader and both work without any faults so it is not faulty or too slow cards that are the issue here. I wonder if it is the UHS speed class that is causing this?

Is anybody using this Marshmallow feature successfully?

Many thanks,

herges
[Nook HD, HD+ Android Development] highlandsun:
I actually had to use pico, nano was too big too.
[Nook HD, HD+ Android Development] belfastraven:
When you plug it in, do you always see the amber led that indiicates that it is charging? When you go back to it is and it is turned off, what is the state of the battery?

I have found that when my nook was plugged in to a.c. and the power went off, it would start discharging . The same thing would happen if the wire connecting to the nook or at the wall were not seated quite right A couple of times I had to charge it for several hours before I could boot again. Unfortunately, once it reboots, you are getting fresh logs, which makes it hard to pick up an event after the fact.
[Nook HD, HD+ Android Development] KyJelly69:
I'm not sure the status of the LED. I will check if it happens again.
[Nook HD, HD+ Android Development] belfastraven:
These nooks are really very fussy about the sd cards, as [MENTION=6326205]ieatabiscuit[/MENTION] has said. Just because another reader reads the card doesn't mean the nook will be happy with it. That being said, I found a few places on the web suggesting that using the card as internal storage works much better if you

1. format card for internal storage. (Let it format, ignore "too slow" messages)

2. Select "move later"

3. Reboot .

After the reboot you can go back to settings, storage and specify that you want to move the apps.

I have done that, just as a test, with a SanDisk 16 G card (its either class 4 or 10, I forget which) and everything seems to be OK right now. I have run several apps

You might want to try reformatting the card in your pc or in the nook as external storage, and then going through the steps above... let us know what happens if you do.

P.S> it probably would be good to have a backup on another sdcard in case something goes wrong.
[Nook HD, HD+ Android Development] ieatabiscuit:
On another note, I have tried both the aosp, and latest version of the cm ROMs. Both seemed to work just fine for anything I could put them through. Ran along with Fallout 4, and Shelter fine. Played my movies fine, and even played nice with chrome. I honestly do not think it to be software related with the ROM, as it is seen in both, but the battery issue we skill love so much becomes very persistent. Upon reflashing back to official cm11, I have seen no sign of it. I have been pretty thorough with investigating the hardware, even put the battery it's self through the gambit of tests. My theory, given the finicky nature of the ovation, is that I may have something to do with partitioning. Between the software being poked at by [MENTION=4473900]amaces[/MENTION], and [MENTION=5672278]belfastraven[/MENTION], and my hardware testing, what else is left besides partitioning? Given that I can reproduce the problem on demand, as well as fix it, by way of flashing ROMs, and have become well versed in the touchy nature of my own nook's mentality, web l with proper instruction on the software troubleshooting, I'm willing to torture my device further if I can help solve this for others. I'm just not so well versed in the guts of the software.
[Nook HD, HD+ Android Development] belfastraven:
Really, [MENTION=4473900]amaces[/MENTION] is the only one here doing any software modifications--I am just a tester and someone trying to learn how everything works.(while not being TOO annoying) The battery issues that people see here may very well be "software" or more specifically, the way the software is interacting with the hardware.

I think anyone who has ever tried or read about the overclocking of pc cpu's to make them run faster realizes that if one provides more voltage to a chip and/or increases its clock speed , it will use more power. Sometimes when you modify software, especially in the kernel of our devices, to make everything run faster, the device can indeed use more battery. It is a matter of balancing our perceived smoothness and "zippiness" with battery usage. Maybe there is an EE or computer science person on this list who can explain this better.
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm talking about all-out faulty battery readings. For a time I thought I had a bad battery, and when I removed it to test it manually, the multimeter had shown that the battery was in perfect condition on all the leads that it had. It was about 75% charge then, but the nook was showing 1%... For 8 days straight. I managed to do a trick here and there to fix the issue, but it returns after a bit. Now I'm truing other things with ROMs as I did not see the issue on the stock ROM. After a factory reset from the stock ROM, I tried the official cm as a control, since it's more up to date than stock, and had ample time to mature. I saw no readings coming up like before. Thinking the issue solved, I tried these ROMs. After getting used to MM (not sure I care for the way my card is used as internal storage yet), I like how my ovation acts with the builds from here. Then the battery readings went screwy. I reflashed cm11, and they are gone (been over a week now). The fact that I have seen it on cm11 before makes m believe that it's not a ROM fault. I think it becomes more pronounced with several ROM flashings, and from that being done with several different ROMs. Since the ROM changes partitioning, and some unaccounted for space is in reality used for hardware information and not usually touched by a basic twrp cleansing, perhaps the changing of partition information over time corrupts that data, and with km being so different that it shows more prominently. I could be completely wrong, but if its not hardware, and can be so affected by software, but not so much to affect everyone on a ROM, maybe it is due to that circumstance. Mabensince [MENTION=4473900]amaces[/MENTION] has the most popular nook ROM so far, if that flaw can be tracked down, and at least a work around hammered out, it can keep the issue from popping up so much. Perhaps it could be a fix that twrp could handle, as I do not think its a ROM issue.
[Nook HD, HD+ Android Development] belfastraven:
AOSP build in experimental--hummingbird 160203

[MENTION=4473900]amaces[/MENTION] ,It seems to work fine. Temple Run II still runs :) however there is a small glitch in the navigation bar:

the home button still works, but its position has shifted to the left

See attached.

By the way; how to you get a screenshot on this rom--I ended up having to use my phone to capture a picture of the screen.....
[Nook HD, HD+ Android Development] amaces:
MXB48T/android-6.0.1_r16

The AOSP images in experimental are based on Pixel C code, somewhat divergent from the regular February update (android-6.0.1_r13) that is being merged into CM13. The most visible difference is the new tablet UI, with the split/uncentered Back, Home, and Recents.

Also, it was possible to complete screen casting support on AOSP; the tile in the notification shade is fully functional now/no need for other apps (e.g., MirrorEnabler, Chromecast). Apparently, something is still working differently in CM, but I'll look at it again with the next batch.

Although MXB48T is fully usable, it'll remain in experimental as I'm preparing regular MMB29U. Otherwise, CM13 builds will happen over the weekend, when the AOSP updates should be fully merged.

BTW, you can always select portable storage, which should be the default/normal mount option.

You are right about partitioning being different on CM11 versus CM12, which has slightly larger /system, and /data (CM13 makes no further changes there). Moreover, the transition from Dalvik to ART meant that /cache is used differently, and has different size requirements. It's possible that changing some of these boundaries destroys some temporary battery stats on the other partitions. It never happened to me, but I also don't recall ever going back to CM11. I don't recommend fully formatting all the other partitions (e.g., /rom, /bootdata, etc) since many files in there are hard to replace. However, some of the auto-generated battery files could be erased, which was all the rage on the older versions of Android, so maybe there's something about it on the web. I for one don't know for sure, having yet to encounter this issue.

Ha-ha, it was never my intent for the ROMs to become popular; that thin line between fun and chore is pretty blurry now. I just want my device to work properly, or as well as possible. The reboot upon power off issue, for example, has been hard to track down; the awesome [MENTION=6822220]PeteInSequim[/MENTION] has sent a hummingbird that exhibits it, so hopefully I can make progress there.

Right, the problem lies with my additional optimization flags, which are not used in these builds.

Google's tablet UI for the Pixel C, also described in the second paragraph here: http://arstechnica.com/gadgets/2015...es-an-android-tablets-core-problem-software/2.
[Nook HD, HD+ Android Development] ieatabiscuit:
[MENTION=4473900]amaces[/MENTION], if what you say turns out to be true, I have something to do this weekend. I'm going to go elbows deep in the partitioning on my ovation. See what combination of what positions to format to create or avoid the issue.
[Nook HD, HD+ Android Development] amaces:
I use screen casting to mean mirroring; regular Chromecasting never had issues. This is on AOSP; CM needs more work/testing.
[Nook HD, HD+ Android Development] acr123:
I'm confused. Chromecast for me has never worked with either CM12 or 13 when using the chromecast app to mirror the nook. to a TV. It works fine if I select an app such as Youtube or I use the chrome browser with the google cast extension to cast tabs to the TV.

Am I missing something or is there a setting I do not know about because for me the Chromecast has these mirroring issues..

Al
[Nook HD, HD+ Android Development] amaces:
Yes, it's a bit confusing, but I was pretty clear: the last four AOSP builds (two stable, two experimental, all in February) are fixed such that you can now mirror your screen simply by selecting the Chromecast device in the casting tile. There's no CM build that contains these fixes yet, and I'm not even sure that CM can be fixed in similar ways. The only way to test this feature right now is to flash one of the AOSP builds.
[Nook HD, HD+ Android Development] brenyoka:
Can I ask why the recent few builds are all >250MB in size, when just in December the size tended to be around 190, under 200 anyway? I can only fit the smallest opengapps package and I wonder if the little free space left after all the install would affect the performance negatively regardless of the otherwise pretty stable state of the build?

What is the main difference between the AOSP and CM builds? The former seems to be as small as the slightly older cm builds.

Thanks in advance.
[Nook HD, HD+ Android Development] DE-Nooker:
Hi [MENTION=4473900]amaces[/MENTION] and thanks for the ROMs. I did flash latest 160124 cm (+ open gapps nano) on my ovation and I had a problem with wifi connection drops. I then flashed latest AOSP build 160204 (+ open gapps nano) and I have same problem.

First connection to a WPA2 network works fine but then wifi connection gets lost. This also happens after reboot and it doesn't matter if the Nook is plugged to AC power source or not.

On AOSP, I am able to reconnect by just opening wifi settings. On CM, I need to tap the saved network and then tap connect. However, after a while wifi connection gets lost again on both builds.

Update: On AOSP, I also need to tap the saved network and then tap connect now. Just opening wifi settings doesn't work anymore.