yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
Thanks, I got the issue sorted out.

Any time I went to run an APK to install, it was just saying "Failed" in MiXplorer. The real "issue" was related to the new way 8.1 handles 'unknown sources', and my old settings seemed to be causing an issue with the Package Installer. I had to manually choose "open with" and select the Package Installer, after that I was given the option to allow installs (launched) from MiXplorer, and things are working fine.
[Nook HD, HD+ Android Development] belfastraven:
Any logs required?

[MENTION=4473900]amaces[/MENTION],

Do you need anyogs from 8.1 roms? I have gotten a kernel warning from CPUFREQ.c, apparently, and logcat is getting TI OMAP PowerHAL : Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse . The file supposedly was marked system writable, but i just tried forcing that again, to see if it would help. I know its still early days with the rom, ..
[Nook HD, HD+ Android Development] zspeciman:
I don't know what I'm doing wrong. I have downloaded the Amazon_App.apk, but when I click on it in the built-in file manager in aosp, it doesn't do anything. how do you install anything without an installer?

Is adb the only method to do this? And is adb has to be done from a computer to an android or can it be done from within the tablet itself?
[Nook HD, HD+ Android Development] belfastraven:
try going to settings, storage, files, then locating the file you have downloaded (in downloads maybe?) and clicking on it there. That works for me. The installer is really there..it is built in to AOSP roms.
[Nook HD, HD+ Android Development] zspeciman:
Thank you, thank you, thank you. works great!!!
[Nook HD, HD+ Android Development] dkg666:
Anyone else is having WIFI problems on 8.1 experimental build ? How to fix them ?
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION], building CM 13 for ovation and hummingbird fails at 35 minutes. LineageOS 14.1 fails to sync. Any suggestions? Also fails to sync on CM 12.1. All of these are under your, github.com/airend/android tree. Thanks.

****EDIT****

The oreo branch also fails to sync.
[Nook HD, HD+ Android Development] belfastraven:
I just synced lineage14.1 with no issue, so you may want to try again now. I think perhaps the oreo repositories are not ready for building by us yet.

If you have problems building or syncing, you can pipe the build or sync output to a file by adding

&>somefile.txt

on the build or sync command, and you can often identify where the problem is. IN build logs, I always search for for FAIL or FAILED, for example and can normally find the problem program. Time to failure may not be all that helpful, since we all use different machines, so the build vary considerably with respect to time. Also I have found that sometimes it's a change in one's operating system that causes a building problem, so its often helpful to know what you are building on to help solve a problem. just FWIW
[Nook HD, HD+ Android Development] secretwolf98:
I will try again. After syncing finishes, how do I build it for ovation and hummingbird? Thanks.
[Nook HD, HD+ Android Development] belfastraven:
Not wanting to discourage yhour building, but is there any reason you can't use Amaces lineageOS builds? The latest are from July 13th I believe.--the location is given in the initial post of this thread.

I would build hummingbird:

export WITH_SU=true (to get root privileges)

source build/envsetup.sh

lunch lineage_hummingbird-userdebuig

make otapackage -jN &>filename.txt. (You replace the N with the number of that depends on how many core sand threads per core you have on your CPU. I believe -j4 is the default if you don't specify anything. the &>filename.txt will put the build output in a file)

For ovation you would substitute "ovation" forf the "hummingbird". You should do a

make clean

between builds, I think.

. If you haven't built before, be aware that you need a reasonable amount of memory to build, also. It used to be at least 8G, but it may be more now.

There are actually many different ways to build, various places to put output, etc.

If you are new to building roms in general. YOu might want to use the prebuilt ones and spend a little time looking at various build instructions from the internet. I apologize: I am out of time to respond now. I'm sure someone else will jump in if you need further assistance.
[Nook HD, HD+ Android Development] secretwolf98:
Syncing went fine. Compiling is going now. I want to compile, because I never did it before, I think it would be nice to try it out.
[Nook HD, HD+ Android Development] secretwolf98:
Help! I am getting errors.
[Nook HD, HD+ Android Development] belfastraven:
What is the cpu of the device you are building on. Your build is going very very very slow. Perhaps the build is not defaulting to -j4 like I though. IF you have two cores on your cpu try -j4 one the makeotapackage command. If you have 4 cores try -j8... I know that if the system was actually running single threaded it will not build sometimes.

P.S. the build may still fail about a third of the way through. It did for me just now. I believe there is currently an selinux context mismatch problem. I have alerted amaces through the github repository.
[Nook HD, HD+ Android Development] secretwolf98:
I did another repo sync. I will do another make after. If continues for errors. I will wait until fixed. Can you alert me please, once it is fixed? Thanks.

The computer has 2 cores. I have been doing, -j4
[Nook HD, HD+ Android Development] belfastraven:
I just sunced and build successfully. I am still concerned that there is something in your build "environment" that is causing you build problems. It looks like you are building on an external device, which should be ok unless it it running out of room or too slow..

I am assuming you have installed all the necessary software for the build (compilers, java, etc.--usually if you haven't the build will complain ) the current out file just indicates that the build is being killed here:

build/core/ninja.mk:166: recipe for target '/media/secretwolf98/ExtDrive/JL/CM/sources/cm14/out/build-lineage_ovation.ninja' failed

but not why.

Perhaps one of the other builders will see this and help figure out the problem is you continue to be unsuccessful. If this does succeed based on the amount of time it took to get this far, the build will run for hours...
[Nook HD, HD+ Android Development] secretwolf98:
The drive has 590GB left of space. But once I do, make otapackage -j4 &>filename.txt, I do, brunch ovation, and the errors happen. Am I supposed to do brunch or do something else? After I do the make thing, I don't see any flashable zips in my directory. Thanks.

PS. I am in school right now, so, once I get back, I will do, repo sync, and try compiling my way, if there is any steps I am doing wrong or forgetting, I will do those.
[Nook HD, HD+ Android Development] belfastraven:
If the make otapackage command succeeds, you will find in your output directory "youroutputdirectory"/target/product/ovation/lineage_ovation...... .zip

you do not need to "brunch". , just the three commands I gave you. The filename.txt file you originally included showed that the make otapackage command failed. That zip file you need for installation is the otapackage.
[Nook HD, HD+ Android Development] secretwolf98:
How do I fix this, so I can get the zip, successfully? And, when I do the make command, it stays blank with the command for like a hour, and then it ends without a error. The errors in the filename.txt that I provided, is from doing, brunch ovation.
[Nook HD, HD+ Android Development] belfastraven:
If you have &>filename.txt on the

make otapackage command, the output will be piped to the filename.txt file. Check that file when you get the text prompt back on your system. you should be able to tell how far the build has gotten and where it is failing, if it is failing. A successful build might give yuou a file of 60,000 lines, by the way. But you should get information which will help you debug. Since I just built today, I'm pretty sure there is nothing wrong with the repositories now, and those three lines I gave you are what I normally use to build.
[Nook HD, HD+ Android Development] drmarble:
I always use:

lunch lineageos_ovation-userdebug

mka -j4 bacon 2>&1 | tee make.log

or just:

brunch ovation 2>&1 | tee make.log

The output appears both in the file and on the screen thanks to the 'tee' command.

the flashable zip should be in out/target/product/ovation/<something>.zip

good luck.
[Nook HD, HD+ Android Development] secretwolf98:
Ok, thank you. I will give this a try.
[Nook HD, HD+ Android Development] secretwolf98:
HELP! I am getting errors when I try to build for,

Acclaim - LineageOS 13 (Android 6.0.1 M)​

&

Ovation - LineageOS 14.1 (Android 7.1.2 N)​
[Nook HD, HD+ Android Development] Zippy Dufus:
[FONT="Courier New"][SIZE="1"]#!/bin/sh

export CROOT=/home/android
export LOGFILE=$CROOT/Logs/sync_build_nookhd+.cm14.$(date +'%y%m%d-%H%M').log
export LANG="" # [url]https://bbs.archlinux.org/viewtopic.php?id=201281[/url]

printf "Program: %s\nPID: %s\nDate: %s\n " "$0" "$$" "$(date)" > /tmp/BUILD-IN-PROGRESS

time {
# set -x

STARTDATE=$(date +%s)
echo "Start time: $(date)"

export JAVA_HOME=/usr/lib/jvm/java-openjdk
export JAVA_OPTS="-Xms2G -Xmx4G -XX:MaxPermSize=512M -XX:-UseGCOverheadLimit"
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"

export WITH_SU=true # Baked-in Lineage su support

java -version

export USE_CCACHE=1

cd $CROOT

# Clear any local manifests
rm -fr $CROOT/.repo/local_manifest.xml $CROOT/.repo/local_manifests/*
mkdir -p $CROOT/.repo/local_manifests

# initialize repo
repo init -u git://github.com/airend/android.git -b cm-14

repo sync -j1 --force-sync
repo_status=$?
if [ $repo_status -ne 0 ]; then
echo "repo sync failed[$repo_status]"
exit 1
fi

source build/envsetup.sh

lunch lineage_ovation-userdebug

mka -j3 bacon

ENDDATE=$(date +%s)
echo "Time elapsed: $(date -u -d "0 $ENDDATE seconds - $STARTDATE seconds" +"%H:%M:%S")"

sync
} 2>&1 | tee -a $LOGFILE

rm -f /tmp/BUILD-IN-PROGRESS[/SIZE][/FONT]
[Nook HD, HD+ Android Development] belfastraven:
If you read your own log files, you will see that the builds are failing for the same reason .Fex is complaining about locale definitions (look at the last couple of lines of each file).

before running your other commands, export LC_ALL=C. I believe that will fix things for you.
[Nook HD, HD+ Android Development] twisteroid:
I dug out my Nook HD+, wiped everything, and flashed TWRP 3.2.3 and AOSP 8.1.0 from the experimental section without installing gapps. I couldn't believe how much faster the tablet runs now! All the lag was gone, although gapps was probably to blame for that. And for the first few times powering off the tablet, it actually stays off!

However, I then had file system corruption in /data, and "Repair File System" in TWRP can't fix it. I thought the cause was F2FS, so I formatted both data and cache to ext4, and now the tablet won't stay off anymore. :crying:

Could it really be that using a certain file system for data and cache helps the tablet staying off? Or is it something else I'm missing?

Also, the "reboot" option in power menu always reboots into recovery :confused:
[Nook HD, HD+ Android Development] secretwolf98:
I gave this a try. It took 11 hours before it failed. Any suggestions or/and help, please?

PS. XDA won't let me upload the log, it is 100KB more than it can handle.

Link to error: https://www.androidfilehost.com/?fid=1322778262904006206
[Nook HD, HD+ Android Development] Zippy Dufus:
I can't see any errors in your output. You must have filtered out stderr.

Go to the end of your real log and search backwards (case insensitive) for "error" to find out what stopped the build.

If it got as far as it did, then I suspect the "jack server". Are you setting the ANDROID_JACK_VM_ARGS appropriately for you machine? Set it to a value less that is available memory in your machine. Perhaps your machine doesn't have enough RAM to build android.

Also, I suggest that you run a rm -rf /media/secretwolf98/ExtDrive/JL/CM/sources/cm14/* to clear out your build directory so a pristine copy of all the source code is checked out of your local git repository. (This way you can fork the provided script to build other devices by removing artifacts from a prior build.) However, check first to running ls -l /media/secretwolf98/ExtDrive/JL/CM/sources/cm14/* to be sure that your don't pick up the hidden .repo directory which contains around 20GB of downloaded android source code! The /* is very important to prevent this!.

Good luck.
[Nook HD, HD+ Android Development] secretwolf98:
My laptop has 2GB of RAM. I didn't filter anything out, it was all the terminal, that would let me select.
[Nook HD, HD+ Android Development] belfastraven:
Wait you say that the laptop has 2G ram? Are you building on the laptop? Building Android requires more memory than that..if you look up "building android" ram requirements on the web, you will see that people will say 4G is minimum, some 8G. Or are you building on a different machine, I don't understand. You have seemingly gotten about halfway through the build--i see that by comparing my outptut lines to yours.

So if a build succeeds, it will probably run close to 24 hours......

I have a reasonably fast 8 core processor and lots of ram, and I can build in 20 minutes or so. I think many people can build in a coiuple of hours. Can you use a different computer to do this?
[Nook HD, HD+ Android Development] secretwolf98:
I don't have any other computers that has more than 2GB RAM.

Could you do me a favor and sync the LineageOS 13 source code, do source build/envsetup.sh, lunch lineage_acclaim-userdebug

I know it will give a error message (This should download all of the required files from the LineageOS github). So then, go to, device/bn/acclaim. Delete all of those files, open a terminal for the whole LineageOS 13 source code directory... Then do, git clone git://github.com/secretwolf98/android_device_bn_acclaim.git -b cm-13.0 device/bn/acclaim

After completed, do... export WITH_SU=true

source build/envsetup.sh

lunch lineage_acclaim-userdebug

Then do what ever after/before that to get a successful build... After you get the flashable zip, could you PM me on XDA with the zip, please? I will test it on my device. Thank you, if you can.
[Nook HD, HD+ Android Development] Zippy Dufus:
Yup, 2GB is a little "light".

Having said that, I am composing this reply on an 8yr 2GB laptop (Acer Aspire 5516) which was the cheapest of the cheap. I removed the bloated Windoze Vista (which barely ran) and it has been running Fedora Linux ever since. I even managed to once compile the Chromium browser (Google Chrome development/testing) on it but this took a better part of a week to build!

Lately, after much searching I found another 2GB used memory chip for $10 at an independent (aka a nondescript store in a sketchy strip mall) computer store which buys/sells used computers as well as unlocks smartphones. It took 3 trips to store to find a chip that will work and on the final trip, I took the laptop into the store and tried a dozen chips until I found one that worked. You may want to research the memory configuration of you laptop and do the same. However, if you have a two slot mobo with two 1GB chips, it is probably not workwhile to to spend the money to upgrade.

What you should try:

Prepare my script so you can easily run it from the command line

export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx1G"

repo sync -j1 --force-sync

mka -j1 bacon

Boot your machine in init 3 mode (no graphics to save memory) so only the command line is available. Google how to do this if you do not know.

Fire up the build and hope that you have something within a week!

Good luck and don't give up!
[Nook HD, HD+ Android Development] secretwolf98:
I feel so sorry for your computer. I had a old Dell Studio 1537 laptop (dark blue) that had Windows Vista, brand new from Best Buy... Was junk out of the box. The hard drive failed in the summer of 2015.
[Nook HD, HD+ Android Development] drmarble:
I had a few problems recently which might be related to the new TWRP and/or aosp_ovation-8.1.0-20180904.zip.

I formatted system and data and flashed the zip. It worked fine, wifi was buggy but I didn't notice any other problems. I decided to go back to lineage14.1 for a while and restored my backup. It also worked fine. Then a new build (09-14) appears. I reboot to recovery to install it and my troubles ensued.

TWRP didn't finish starting. Just the splash screen. I could log into an adb shell and saw that it was stuck scanning /data. There was a broken file in the cache for an app. Any efforts at rebooting fail. I assume it was the contents of /bootdata/BCB. I was going to "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088" to clear it but I tried booting an old install sdcard with cwm on it. cwm wouldn't let me mount my f2fs formatted /data but it did clear BCB so I was able to reboot to system. I released a large sigh of relief. I go in and clear the cache for the offending app. To be safe I copy the contents of /sdcard to my pc. Everything seems to work fine.

I was wrong. I reboot to recovery and it gets stuck in the same fashion. Even the same cache files even though I had cleared them out. I dd'ed an older 3.0.1 TWRP into /recovery, reboot and get the same errors. The old twrp has the same problems. I pop in the ancient sdcard and reboot to cwm. From there I reformat /data & /data/media and reboot to older twrp. From there I change the file system for /data to ext4. I restored my backup and everything is now working fine with an old fashioned ext4 file system instead of f2fs. I even adb pushed the saved contents of /sdcard. It seems to be working fine. I ran "e2fsck -fpcv /dev/block/mmcblk0p10" expecting there to be bad blocks. There weren't any. I just had a sudden glich in the file system with no obvious cause.

I have no idea what screwed up my file system. It is all better now. I plan to try out the new build soon. I know how to fix things if it goes bad again. I am glad I had the old cwm around so I could easily erase /data. I am not sure that dd would work when the file system was being probed by twrp. I'm curious if anyone else has had similar damaged file systems from trying the 8.1 zip and 3.4 based TWRP.

Still in all, amaces, amazing work. Thanks for keeping the omap4 processor relevant.
[Nook HD, HD+ Android Development] belfastraven:
I don't think that trying to sync either the Lineagos github branch for cm-13.0 or amaces repository will actually give one a buildable set of files for lneageOS 13. One can build AOSP from amaces repository but not Lineage 13, as far as I can tell. The problem isn't with the device files, more that the vendor propritary files are not included in the build instructions. Unfortunately, I don't have time to look at this more in the next few days. If you need an acclaim cm marsmallow rom, someone here might have one already that they could send you, or be able to help you further.
[Nook HD, HD+ Android Development] jernyx:
I've had similar problems with the two recent builds and the data partition with an f2fs file system. I've formatted and reinstalled several times now. I'll try reformatting /data as ext4 and reporting back.
[Nook HD, HD+ Android Development] secretwolf98:
Why can't anyone build from the LineageOS source code? Could you look into this when you have time?
[Nook HD, HD+ Android Development] asksmity:
I may be late to the party, but I took some time and did a lot of testing.

Here is what I did to get 8.1 and Gapps Pico running.

Used repit to size my system to 2gb (may not be needed, but i did it anyway)

Wipe system via advanced wipe

Install 8.1 and magisk

Go to wipe -> advanced wipe -> select system and then resize file system

System should show around 88mb remaining with total size of around 661mb

Select resize file system and run twice. first time it errors, second it runs.

Back to the advanced wipe screen, select system and repair again. verify your size now shows 2019mb (or whatever you have it truly sized to)

Install gapps

Reboot to rom

Edit: This was using the HD+ Ovation
[Nook HD, HD+ Android Development] ajislav:
+1, my ovation runs very smooth, will report back after more than 1 day of usage.
[Nook HD, HD+ Android Development] jernyx:
Previously the file system has stopped my device from functioning within a matter of hours but it's been working fine since my last post with all the same apps I was trying to run. All I did was change /data to ext4 (previously f2fs which worked fine on older builds as far as I could tell) from the latest TWRP then wipe and do a clean install of the latest build. I also ran the same e2fsck command that drmarble ran, no bad blocks. It seems the Oreo builds may not work with f2fs for some reason. I'm not knowledgeable enough to figure out why.

I suspect it also may have something to do with the apps I was installing. I got an error either while booting the OS or TWRP which indicated a problem specifically with a file that twitch had in the cache. But I hadn't tested or investigated this further before switching to ext4.
[Nook HD, HD+ Android Development] michealm1979:
How do I update my TWRP? I would love to run Oreo, but no matter how I try to update TWRP, I get softbricked and have to boot from my sd and replace CWM, only TWRP I have a flashable zip for is twrp-3.0.1-0-ovation.zip.
[Nook HD, HD+ Android Development] asksmity:
TWRP has a "flash image" option. You can use the images in amaces folder (either ovation or experimental). So if you can get to any version of TWRP, you could do it that way. Not sure if CWM has that option, but they may.

If there is an underlying issue like partition layout or something, not sure.
[Nook HD, HD+ Android Development] michealm1979:
Thanks for the reply. I'm used to doing it on a phone, and just flashing the ZIP, and being done with it.
[Nook HD, HD+ Android Development] zspeciman:
I finally took the big step into REPIT, using e.mote guide https://xdaforums.com/showpost.php?p=71387219&postcount=1722 and it works!!! I was able to install gapps pico which I couldn't do previously. Before I started, I had to make sure that my data and cache was on ext4 and not f2fs (I believe that is a necessary step), also at step 6, "Select resize file system and run twice. first time it errors, second it runs" (quoted from asksmity) And finally I was able to root via addonsu-14.1-arm.zip This process while looked quite challenging wasn't that bad and worked out much better than I expected. I'm glad to see that you can enable battery percentage in options in aosp Oreo, that was missing in aosp Nougat. The only problem I noticed is that when you touch an app and you are giving the option to remove or uninstall, those two options are blurred into gibberish characters. The function still works, but you can't tell if you're removing from the screen or uninstalling the app. Otherwise, its exciting to see Oreo on this aging device.
[Nook HD, HD+ Android Development] mikeataol:
I didn't see any quick and easy instructions for repit, so I fell back on steps I already knew how to do to enlarge system partition

created a how to here: https://xdaforums.com/nook-hd/help/nook-hd-ovation-repit-alternative-t3844912

I used opengapps nano on 2 Ovations and its fine (other than the random bugs in the rom being described in various posts)
[Nook HD, HD+ Android Development] zspeciman:
its nice to see there is another option besides REPIT, thanks for the guide [MENTION=5561010]mikeataol[/MENTION]. I stayed away from REPIT because it looked complicated, no matter how many times I've read it. But it wasn't that bad, just few steps using the guide I linked earlier. Not much to it, just following steps. One question that I have: Next time I factory reset, for a fresh install, do I have to repeat REPIT or do these new partition size stay the same?
[Nook HD, HD+ Android Development] mikeataol:
once you've gone to TWRP and an aftermarket rom, factory reset wouldn't do any changes to partitions.

So no, the partition layout should stay the same with a large /system.