yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
Do you remember if latest AOSP was able to read you SD card? My exFAT cards are fine now, but NTFS support is not quite fully grafted onto AOSP (CM13 should be fine with its FUSE implementation).

To reiterate, Marshmallow has a new Storage API and apps need to be updated to take full advantage of it. Solid Explorer, for example, detects the external storage, but it still asks you to select the actual location, leveraging the built-in storage UI. That implies that even the big devs haven't quite decided how to deal with these changes; I'm only concerned with updating our device trees per official instructions here: https://source.android.com/devices/storage/config.html#android_6_0.

Nano-class GApps should work, and they leave enough free space in /system (at least on AOSP). The issue Chainfire brought up mainly affects Nexus/stock ROMs, usually packed to the gills; those 10-15 MBs that seem available in /system may be unusable, and attempting to use them can destroy the whole ext4 filesystem (under certain conditions).

We can fully control how much space remains available on the system partition, and when you have 20-30 MBs free, no need to worry about that issue.

P.S. Just curious, did you notice any dex2oat tombstones/heap corruption errors with this CM13 build?

The discussion about CM user and userdebug build templates applies to CM13 as well; the latter template happens to include CM's root solution. Since userdebug builds are the norm again (SELinux Permissive, ditto) SuperSU is not strictly needed anymore on CM. I still prefer it, and it's definitely the way to go on AOSP.

If it's the same generation of the same flavor ROM (i.e., successive CM13 builds), normal/dirty flashing should be OK. Sometimes, wiping caches might be needed, but only if issues pop up (much of the cache is regenerated anyway). With CM <-> AOSP switches, clean install is still needed, and if you're also installing GApps, that should happen right after wiping /data.

I hope that happened when you used the device a fair bit; it should be 80-90% deep sleep when you're using it intermittently and it sleeps overnight. Also, the CPU goes to 396 MHz much more quickly with the current zRAM driver, which is great temperature-wise (battery too).

Hopefully it's a user app because the sources you're building from are exactly what I have here. One other culprit may be a newer kernel EABI (5.2 or 6.0); there was discussion that even nominally stable GCC 5.2.x compiles kernels that are significantly worse battery-wise. The UBERTC dev was commenting on this recently: https://plus.google.com/+ChetKener/posts/9aimMRxLUWZ. He managed to improve the situation with his current 5.2+ toolchains, but others may still miss those patches.

Interesting, I'm tempted to give it a try at some point. Right now, CM12 needs some love too.
[Nook HD, HD+ Android Development] Zippy Dufus:
I went back to my build and it again rests at 800MHz. It may be a problem with my kludge with the blobs because there are two different sets in the working directory. Same file size but different checksums(??). I'm going to rebuild using the version in the bn directory and not the ti directory as I am doing now. AFAIK, I didn't start many apps other than the normal services for testing this behavior.

I've managed to build the Linaro GCC 5.2 2015.11 build chain from source and will soon see if I can build your ROM with it - just for fun! :cowboy:
[Nook HD, HD+ Android Development] belfastraven:
no dex2out tombstones In 2 days I have one from NYTimes (lib.so or webview) and one from Mediaserver.

I'll keep watching it...I'll check it first thing in the morning before I use it:

Thanks again for your answers (and your patience;).
[Nook HD, HD+ Android Development] andtron:
Hi amaces,

No problem at all and I know the MM is still work in progress, I just report the status with the sd card here to let people know.

Good job!
[Nook HD, HD+ Android Development] allrockedout:
Im retarded download link please?
[Nook HD, HD+ Android Development] digixmax:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918
[Nook HD, HD+ Android Development] allrockedout:
The shared file has been removed?
[Nook HD, HD+ Android Development] ajislav:
You must be on a mobile browser

Request desktop version.. Or use a PC
[Nook HD, HD+ Android Development] extrem0:
MM download folder: https://m.box.com/shared_item/https...ygh9vbaw7jjq08xr5evomvaw5ww/browse/3480156918

There's a new cm build from yesterday.
[Nook HD, HD+ Android Development] FirePsych:
Are you sure that's a CM build?

Looks like AOSP to me.

EDIT: Yes, that's a new CM build, but it's LP, not MM. That is, CM12 not CM13.
[Nook HD, HD+ Android Development] allrockedout:
Gapps not working?
[Nook HD, HD+ Android Development] FirePsych:
I've been using OpenGapps nano and pico without a problem.
[Nook HD, HD+ Android Development] vinceweis:
I also use nano Gapps with no problems.
[Nook HD, HD+ Android Development] allrockedout:
So i boot into twrp, i have the rom and gapps saved external sd. But when im in twrp i cant find the zips. I flashed cm12 a long time ago and forgot what im doing wrong?

Update found cm13 zip flashed now saying unable to mount sdcard1
[Nook HD, HD+ Android Development] extrem0:
Sorry. Actually it's experimental folder and I forgot amaces went back to update cm12. The last cm13 build is from last week (13th).
[Nook HD, HD+ Android Development] BultoPaco:
I know a lot of people just blew by post #1434 from [MENTION=4141005]Lanchon[/MENTION] but this really will help you. I have used his Repit tool on both an Ovation and a Hummingbird and can load the latest LNOS ROM with Nano gapps. The tool allows you to increase the size of the system partition -- just make sure you read all the documentation. Once you have used Repit, you can install the ROM as usual. You will then need to use TWRP or Repit again to resize the system partition file (Repit documentation explains why) after you load the rom, then you can install gapps of at least nano size. Another benefit of Repit is you can also recover some emmc storage for the data partition.
[Nook HD, HD+ Android Development] pyoungworth:
Is there a way to fix the lines on the latest CM marshmallow build when rotating the screen? Everything else seems to be working flawlessly. Thanks for all the hard work and dedication you all put into these builds.
[Nook HD, HD+ Android Development] mmnspeed:
Tried a new build on ovation after a long time.The first device that I used Lineage OS on.Last I visited this page it was still Cyanogenmod.
[Nook HD, HD+ Android Development] Secretcow:
Thanks for the Lineage OS build :)!
[Nook HD, HD+ Android Development] pyoungworth:
When installing clean using the lineage ROM does it prompt to do a restore? I have tried the ROM a few times with Gapps pico and I am never prompted for an option to restore like I am on the previous cm 12 and 13.
[Nook HD, HD+ Android Development] digixmax:
Same here, I clean-flashed lnos_ovation-ota-NMF26Q.170104 and had to manually re-install all my apps.
[Nook HD, HD+ Android Development] NE0HP:
Does REPIT works on Ovation already running on CM11 or just on Stock rom? Asking because I wanted to upgrade my ovation from CM11 to LNOS Rom.
[Nook HD, HD+ Android Development] ieatabiscuit:
I haven't tried it personally, but from my understanding it isn't ROM specific at all. I haven't really bothered with it because I run pico GApps by default anyway, and change ROMs on my Ovation rather frequently. I'd be just adding more steps in if I used REPIT every time I wanted to tinker on my Ovation.
[Nook HD, HD+ Android Development] BultoPaco:
I agree REPIT is not ROM dependent. I flash new builds frequently also and maximizing the system partition size takes less than a minute in TWRP. Well worth it for the memory utilization benefit IMHO.
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm going to give this a shot. I've gotten my fingers into every other aspect of my ovation, including hardware. [MENTION=5403958]BultoPaco[/MENTION], if my ovation explodes, you're buying the sympathy beer for me right?
[Nook HD, HD+ Android Development] BultoPaco:
Sure, no problem brother. Lanchon claims no device has ever been bricked by REPIT and lnos is running great on both of my Nooks post REPIT application.
[Nook HD, HD+ Android Development] ieatabiscuit:
How's YouTube and/or YouTube kids run on yours? I've been having trouble with both (my daughter has an ovation also). I'm thinking maybe the extra space can be used as swap to supplement the low RAM, and maybe fix the issue of videos not playing.
[Nook HD, HD+ Android Development] ieatabiscuit:
Thanks for the inspiration. Everything worked just as advertised. Now I have nano and a little more white room. Time to see what I was missing out on.
[Nook HD, HD+ Android Development] i9000usersa:
I'm sorry if this has already been discussed or if this is the wrong place to ask. I looked around and couldn't find the information. I came across a nook hd, and I am considering either putting nougat on it or selling it, and I was wondering, if I flash nougat, is there a way to return to completely stock including recovery and everything else?
[Nook HD, HD+ Android Development] ieatabiscuit:
Yes, you would basically flash it like any other ROM, and the image you flash will have the recovery and all included. Then you're all stock. If you use REPIT, I don't know if you can do that, but I know that if you haven't changed partition sizes with REPIT you certainly can. Check for the images in [MENTION=349198]leapinlar[/MENTION]'s threads.
[Nook HD, HD+ Android Development] NE0HP:
TWRP 3.0.3.0(experimental) and REPIT

I've tried and flashed REPIT (both REPIT Zip files) as instructed in [MENTION=4141005]Lanchon[/MENTION] 's this https://github.com/Lanchon/REPIT/issues/59 thread using [MENTION=4473900]amaces[/MENTION] experimental TWRP 3.0.3.0 on my Ovation running experimental LNOS but it failed with Error 1. I've flashed both REPIT files using official TWRP 3.0.2.0 running LNOS and it just works fine. So since this TWRP 3.0.3.0 is experimental, and as suggested by [MENTION=4141005]Lanchon[/MENTION] , I request [MENTION=4473900]amaces[/MENTION] to have a look at my conversations with [MENTION=4141005]Lanchon[/MENTION] here https://xdaforums.com/nook-hd/development/nook-hd-repit-enlarge-data-partitions-t3503615/page3 and do the needful to update TWRP so that people who are willing to enlarge /system and /data partition using REPIT can do it without getting any error!

Thank you
[Nook HD, HD+ Android Development] Lanchon:
thanks!

[MENTION=4473900]amaces[/MENTION], please read this post and the next one:

https://xdaforums.com/nook-hd/devel...enlarge-data-partitions-t3503615/post70858542

the relevant error is: {@: 2}: bad substitution

it seems like a shell problem. was busybox replaced by brain-dead toybox?

thank you so much!
[Nook HD, HD+ Android Development] i9000usersa:
Can anyone please comment on the idle battery life of this ROM? I left the stock ROM on it and over 24hrs it lost 3 percent. I assume LineageOS with Pico gapps will use more than that, but how much more? It would be good to not have to worry about charging everyday, or even every week if I leave it alone.
[Nook HD, HD+ Android Development] ieatabiscuit:
When I'm not messing with mine, I get well over a week without charging. I'm using AOSP, but they aren't that different. I haven't measured real world usage time, but I get enough out of it that I don't feel the need to really worry about it. Maybe someone else that has timed it better could elaborate a bit more.
[Nook HD, HD+ Android Development] neonleon29:
I'm going to give REPIT a shot but have a couple questions:

1) Is it recommended to wipe system and data partitions before performing REPIT?

2) Assuming all goes well with REPIT and I have the increased system and data memory, when would I be required to run REPIT again? Is it every time a new ROM is installed? I was thinking it was a one and done shot. Once the memory is increased, what would cause it to go back to its original size?

3) After running REPIT, is it necessary to resize the system partition after installing the ROM?

A) Install ROM

B) Resize system partition?

C) Install GApps

D) Reboot
[Nook HD, HD+ Android Development] ieatabiscuit:
Yes. You would do exactly that. I install ROM, resize with TWRP, install Gapps, and reboot. The reason is that the room installs to system by copying is version of system, and that includes is version of free space. You resize back to what you changed it to after to correct this. As for going back to stock, I don't know. For me, it's no turning back, I only use stock for partition repairs, which I have learned are less needed than originally thought.
[Nook HD, HD+ Android Development] neutronjeff:
This Repit tool seems like a great thing. I'm feeling uncomfortable about the specific choices to put into the file name. The instructions say to look for the device specific settings. I don't see the ovation file? I'm willing to completely wipe. It would be great to see a recommended set of selections to load [MENTION=4473900]amaces[/MENTION] latest N builds. Thanks.
[Nook HD, HD+ Android Development] ieatabiscuit:
This is the linkto their DL page. You want the one for your device (Ovation, or Hummingbird) For my Ovation I renamed it to lanchon-repit-20170115-factory=32M-system=1G-cache=32M+wipe-data=max+wipe-ovation.zip. Before you flash REPIT, you have to DL This to get the partition it pulls the space from all set and ready. Once you have them, (I changed everything to ext4 at this point for ease of use for this) FIRST flash the Delete backup of stock zip as is, then flash REPIT using the sizes you choose. Going smaller than 32M for the factory, and cache partitions is overkill, and not suggested. Once you have that done, (I changed /Data back to f2fs here, but that's optional) install the ROM you want, then in TWRP run the tool to resize partitions BEFORE you install GApps. TWRP may fail to resize the first time, that's because the partitions aren't mounted that first time. Retry it, and then all will be fine. Then install GApps, reboot, and enjoy. I've used Yellow Kernel, Amaces MM builds, and Amaces M builds with no problem aside for Yellow not liking f2fs.
[Nook HD, HD+ Android Development] sammynoob:
Building aosp for nook

This is my first time compiling a rom for the nook hd. I keep on getting stuck at this part and the build ends.

If you have any experience with this

build WL12XX_MODULES
FAILED: WL12XX_MODULES
/bin/bash -c "(make clean -C hardware/ti/wlan/mac80211/compat_wl12xx ) && (make -j8 -C hardware/ti/wlan/mac80211/compat_wl12xx KERNELDIR=/home/temp/aosp/out/target/product/hummingbird/obj/KERNEL_OBJ KLIB=/home/temp/aosp/out/target/product/hummingbird/obj/KERNEL_OBJ	KLIB_BUILD=/home/temp/aosp/out/target/product/hummingbird/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=\" /home/temp/aosp/prebuilts/gcc/linux-x86/arm/arm-eabi-4.9/bin/arm-eabi-\" ) && (mv hardware/ti/wlan/mac80211/compat_wl12xx/{compat/compat,net/mac80211/mac80211,net/wireless/cfg80211,drivers/net/wireless/wl12xx/wl12xx,drivers/net/wireless/wl12xx/wl12xx_sdio}.ko /home/temp/aosp/out/target/product/hummingbird/system/lib/modules ) && (/home/temp/aosp/prebuilts/gcc/linux-x86/arm/arm-eabi-4.9/bin/arm-eabi-strip	--strip-unneeded /home/temp/aosp/out/target/product/hummingbird/system/lib/modules/{compat,cfg80211,mac80211,wl12xx,wl12xx_sdio}.ko )"
[Nook HD, HD+ Android Development] belfastraven:
What version of the rom are you building, and whose repositories are you using? There is really not enough information here in your message. There should have been error messages in your output explaining what the build system is "unhappy" about. Could you please say exactly what you did to start this build-- i.e. what repos you inited and synced. I assume you ran lunch aosp_humminbird-userdebug, but can't tell for which version of the rom. Have you piped the output of the make command to a file and looked for statements that have

:error in them?
[Nook HD, HD+ Android Development] sammynoob:
This is the only part after the failed wl12xx modules fails to build and I'm using amaces repo.

this appears multiple times before it stops.

make[6]: *** No rule to make target `.git/refs/tags', needed by `/home/temp/asop/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/version.h'. Stop.

and this shows up

/bin/sh: 1: [: -gt: argument expected
/bin/sh: 1: test: -eq: unexpected operator
/bin/sh: 1: test: -ge: unexpected operator

Like I said this is my first time building a rom. I tried building this on a mac but got more errors so Im currently using ubuntu 16.04 LTS x64. if it helps also thanks for your help Ive googled everywhere and no one else had my problem.
[Nook HD, HD+ Android Development] neutronjeff:
Are the lineage builds Android 7.1?
[Nook HD, HD+ Android Development] belfastraven:
Sometimes you will get that error if there is not a proper .git folder in the hardware/ti/wlan source directory. Check and make sure the .git directory is there. I'm not sure WHY there would be something wrong with it if you recently synced and build.

I was asking you to be a bit more specific; I'm sorry if I wasn't clear. When you did the repo init, what exactly did you enter?

e.g. repo init -u https://github.com/airend/android.git -b nougat would be for building the android AOSP nougat

branch.

then you would

repo sync

from the directory where you created the repo

source build/envsetup.sh

then lunch aosp_hummingbird-userdebug

I build on ubuntu 17.04 64 bit machine and would test for you if I knew exactly what you did.
[Nook HD, HD+ Android Development] ajislav:
I was able to compile LineageOS cm-13.0 branch against amaces' repositories (revision mm-13) . Screen casting works and there are no more graphical glitches when rotating device. I might try and backport/cherry-pick amaces' updates to the ng-14 revision back into the mm-13, but at the moment I am just happy the build finished (WITH_SU=true) and data got preserved (I dirty flashed).
[Nook HD, HD+ Android Development] aoleary:
Hi.

So the repit tool has to be flashed twice?

Once before flashing ROM and once after flashing ROM, but before flashing GAPPs. Did I read that right?
[Nook HD, HD+ Android Development] neutronjeff:
There are two different tools.
[Nook HD, HD+ Android Development] olin00:
Thanks for the LNOS Nougat rom, works perfectly on my HD+.

I also tried to compile and failed. I even installed clean install of xubuntu 14.04 to make sure the compilation issues are not specific to my xubuntu 16.04.

Anyway here is the compilation errors if anybody is interested:

system/core/libbacktrace/BacktraceOffline.cpp:722:21: error: no member named 'toString' in namespace 'llvm'

llvm::toString(binary_or_err.takeError()).c_str());

~~~~~~^

I fixed it to get past the error by removing llvm::toString and using the output function from the code block above. Compilation carried on then failed on this one:

error: unknown target triple 'renderscript32--linux-android', please use -triple or -arch

ninja: build stopped: subcommand failed.

make: *** [ninja_wrapper] Error 1

After a bit of searching I found out the prebuilt clang (presumably downloaded by one of the installation scripts) is too old, so I checked out the latest one from git and the build carried on to the point where it crashed on sigsegv while running one of the compiled tool that was run as a part of the build. Anyway I tried to resync, at that point the repo started to throw multiple errors saying 'too many requests, http error 429' (probably I resynced too many times ) , so I bailed out and downloaded your ROM...
[Nook HD, HD+ Android Development] ieatabiscuit:
There's 2 tools to use. To correct the size of /system being changed by the ROM, you can do REPIT again, or you can just use TWRP to resize it back to 1G.
[Nook HD, HD+ Android Development] ejstubbs:
I have successfully deployed the ideas and tools discussed in this thread to upgrade my Nook HD+ to Marshmallow - not something I'd ever thought likely to happen before. Kudos to all involved in creating the stuff that makes it all work.

I did have to use lanchon's REPIT tool, with the default settings as per the latest download, to get GApps nano installed, but apart from insisting on running from tmp (it took me a minute or two to work out how to do that) it was all good.

One question: on CM11 I used Lagfix to run fstrim nightly, and when it looked like it needed doing at other times. On CM13 it says it's not supported. Is there another way to achieve the same thing - or is it simply not needed now? (I would say that I haven't noticed the slowdowns that I used to get quite regularly before.)
[Nook HD, HD+ Android Development] acr123:
How exactly do you resize /system back to 1G using TWRP? I am curious . I've done it already with REPIT.

Found resize hidden under wipe section.

Al
[Nook HD, HD+ Android Development] ieatabiscuit:
Wipe > Advanced Wipe > check System > Repair or Change File System > Resize File System > Slide to confirm

The first time after I first ran REPIT this method gave an error (I assume due to partitions being/not being mounted). Do it again, and the issue is cleared, and the partition is expanded properly.

We should take this conversation into the proper thread so this one isn't filled with unrelated talk, and so [MENTION=4141005]Lanchon[/MENTION] gets the recognition for this in his own thread.
[Nook HD, HD+ Android Development] acr123:
problems with latest TWRP for Nook HD+

When selecting reboot into recovery after pushing volume button to access the menu, the Nook first turns off. Then pushing volume button again it reboots into recovery. Also, I have expanded /system to 1 GB and gotten a little extra data space by using REPIT. Is this the way this should now work or is there something else I need to do.

Previously it booted directly into recovery w/o turning the Nook off first.

Thanks,

Al
[Nook HD, HD+ Android Development] belfastraven:
I think this commit would fix your build error : https://github.com/airend/android_build/commit/9bb553a0fc5d853f50f6332ba74f99b08bd2d3fc
[Nook HD, HD+ Android Development] ejstubbs:
Choppy audio with cm_ovation-ota-MOB31K.161125

Everything seems to be working fine with Marshmallow on my Nook HD+ except for this problem with the audio. It will play music OK first time of asking but stopping/pausing playback and then resuming the audio is choppy. I pause music playback and play a video instead I also get choppy audio, although the video looks fine. Using MX Player, if I switch from HW to SW decoding and back again it seems to fix the audio. The problem seems to go away if I stop using the tablet for a while.

Any clues to what's going on and/or how to fix this? I can't find any other references to this problem so maybe it is just me...
[Nook HD, HD+ Android Development] i9000usersa:
First of all, thanks to the devs for this amazing ROM. Everything seems to be working well, except battery drain.

Apologies if this has already been discussed. If so, please just point me to the answer.

I have some bad battery drain compared to stock. I installed better battery stats and it tells me that there is a kernel wakelock musb_autosuspend_wakelock and rx_wlan wakelock. Any idea how I can solve these? The battery drains at about 3-4% per hour doing nothing and connected to wifi. On stock it drained about 3% over 24 hours or more.

Also, not sure if it's related but on the system battery usage screen it shows that cellular network signal is active all the time with a red bar, which is strange because this is a wifi tablet.

I'm on hummingbird 170104.

Any help would be much appreciated.
[Nook HD, HD+ Android Development] digixmax:
Have you tried turning off WiFi when not using the tablet?