yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] steven676:
As of last night, the two trees are in sync, and my hardware/ti/omap3 tree is no longer needed -- the changes to the OMAP3 hwcomposer have been merged into CyanogenMod. (As drmarble points out, you need to use the encore-omap3-3.0.y branch of the kernel no matter which tree you're building from.)

As of now, the only thing you need to apply to your tree to get a working build is http://review.cyanogenmod.org/57290/ . Applying the squisher patches (1, 2) will reduce the size of your build by about 2.5 MB, but that shouldn't be necessary to get the build plus the latest "official" Google apps to fit now.

If anything's still broken at this point, please let us know!

The way to go is to create a new branch in your local repository that tracks the upstream branch, and then commit your changes to that branch. Try doing the following in your device/bn/encore directory ($ represents your command prompt, not something you type):

$ repo start cm-11.0-local .
[make whatever changes you like]
$ git commit -a

If you've made your changes already, try this instead:

$ git stash
$ repo start cm-11.0-local .
$ git stash pop
$ git commit -a

(You can of course name your local branch whatever you like -- replace "cm-11.0-local" with your preferred branch name.)

From now on, when you sync, repo will automatically rebase your local branch on top of the upstream changes. If your local changes collide with upstream, the rebase will stop and you'll be asked to resolve the conflict by hand.

If you ever decide that you don't want your local changes anymore, just do

$ repo abandon cm-11.0-local .
[Nook Color Android Development] polymath257:
Thanks! I am familiar with $ and # and even >.

(cut)

Just what I needed! Thanks again!
[Nook Color Android Development] steven676:
I've taken to always including that line whenever I use that convention, because otherwise someone will inevitably drive by weeks/months/years later and complain that it doesn't work when they paste the entire thing into their terminal ...
[Nook Color Android Development] drmarble:
Good news. http://review.cyanogenmod.org/#/c/57290/ has been merged! Thanks steven676.

You don't need to add it any longer. If you try, you will get a harmless error message that tells you it did nothing.

You can build just using the NookieDevs or steven676 repos.

I think we are ready to merge the changes and go official. But, that isn't up to me.

It would be nice to have squisher enabled again but it is buildable without it. I should check that gapps fit. That would be sort of a deal breaker.

I just checked, without squisher and using the cm recommended gapps from http://wiki.cyanogenmod.org/w/Google_Apps I have 26.6MB free. That is including an enlarged hosts file thanks to AdAware. This is on an eng build because i forgot to set back to userdebug but that should make little difference. There is plenty of space.
[Nook Color Android Development] fattire:
Stay tuned... steven676 just merged the nookiedevs cm-11.0 branch into a new cm-11.0 branch on cm mainline. Nightly 11.0 builds won't be generated until jenkins is set up, but this means that you can replace the nookiedevs development device branch from .repo/local_manifests/roomservice.xml with cyanogenmod's.

Remember, when the nightlies do come, for those who haven't been building/installing cm-11.0 to this point, you'll need to use a recent recovery to install it. So if you haven't installed a recovery lately, now might be a good time to do it :) (someone else post a link, I don't have one handy.)

Again, everyone thank steven676 :)
[Nook Color Android Development] dparrothead1:
Looking forward to the nightlies. Thanks for the heads up on the recovery. I think those of us that did not have the time or resources to build, are already using imafanof's CM 11 build. :D
[Nook Color Android Development] pmgnet:
I'm also looking forward to nightlies. But unfortunately, I've not been able to repo sync.

I've tried both the NookieDevs roomservice and Steven's roomservice and both give me the below in repo sync.

It's very frustrating because the error is very vague to me. I do have my sync folder on a mount but I built 10.x with no issues.

Fetching projects: 99% (441/445) Fetching project platform/external/chromium_org/v8
Fetching projects: 100% (445/445), done.
Traceback (most recent call last):
File "/media/AndroidBuild/android/system/.repo/repo/main.py", line 418, in <module>
_Main(sys.argv[1:])
File "/media/AndroidBuild/android/system/.repo/repo/main.py", line 394, in _Main
result = repo._Run(argv) or 0
File "/media/AndroidBuild/android/system/.repo/repo/main.py", line 142, in _Run
result = cmd.Execute(copts, cargs)
File "/media/AndroidBuild/android/system/.repo/repo/subcmds/sync.py", line 648, in Execute
if self.UpdateProjectList():
File "/media/AndroidBuild/android/system/.repo/repo/subcmds/sync.py", line 431, in UpdateProjectList
if project.IsDirty():
File "/media/AndroidBuild/android/system/.repo/repo/project.py", line 603, in IsDirty
'--refresh')
File "/media/AndroidBuild/android/system/.repo/repo/project.py", line 2274, in runner
p.stderr))
error.GitError: prebuilts/gcc/darwin-x86/mips/mipsel-linux-android-4.4.3 update-index: fatal: Not a git repository (or any parent up to mount parent /media)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[Nook Color Android Development] unibroker:
rebooting into recovery

I believe since kitkat whenever I select reboot into recovery I have to also hold down the "N" at the Cyanoboot splash screen to actually get into Recovery. Otherwise it will just reboot normally.
[Nook Color Android Development] Arbelzapf:
Is the patch for wpa_supplicant merged as well?
[Nook Color Android Development] polymath257:
I attempted a build last night using steven's repos. After the breakfast encore command, another line was put into my roomservice for the CyanogenMod kernel repo.

I was able to get a build, but the name of the resulting zip was cm-.zip. Nothing with UNOFFICIAL, encore, or anything else.

When I attempted to install using a previous cm11 recovery (that worked with previous builds), the install failed with a set-perm failure.

1) What should the roomservice file now contain?

2) Was the recovery changed so that we need to install a new recovery?

3) What's with the barren zip file name?
[Nook Color Android Development] unibroker:
I built successfully last night with roomservice

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_bn_encore" path="device/bn/encore" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_bn_encore" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y" />
</manifest>

Used the same recovery I've been using for the last month.
[Nook Color Android Development] pastordl:
Same here.
[Nook Color Android Development] rino757:
Could someone please send a built zip for cm11 my way?

I've already built it myself twice, but the first one was extremely slow, and my current build force closes on almost every user app.

On top of that, I'm trying to build LiquidSmooth for the Nook (which no one seems to want to help me with).

I just need something to get by with until I can build again, as my Nook is my only portable device.

Please!
[Nook Color Android Development] andtron:
My latest syn and bld were done on Friday, and right now, there are several annoying bugs as far as I am concerned.

(1) If you move the installed app to the sd card, then their shortcuts on the desktop or navigation bar won't persist after a reboot, and even if you don't, some shortcuts appear more than once,

(2) If you turn off the Google search bar, then you couldn't remove a shortcut because the Remove button won't appear anymore for you to drag to.

(3) The reboot is slow, and most time weather widget just simply struck and you would need to run the weather app first to 'boot' start it,

(4) It won't let you turn off the Location from the Power Control widget.

If you use the NC for daily use, I suggest you to use the earlier versions.

To pmgnet, I suspect your sync has some merge errors on some of the files.

Please add '>sync.log 2>&1' (don't include ') to your 'repo sync' command. once done, use an editor to inspect your sync.log file. See if there are any error, in particular the 'Merge' error.

To rino757, do you also install the required KK gapp?

To polymath, do you use the 6.0.4.5 recovery?
[Nook Color Android Development] rino757:
Yes, I did.

I've also been trying to downgrade to 4.3 but I don't know how to with the recovery I have installed. I keep getting errors trying to install older ROMs or recoveries.

Could you possibly link me or tell me which recovery I need that can flash over new CM11 one?
[Nook Color Android Development] unibroker:
(4) Location has to be enabled from Settings/Location and then you can turn it off from the power widget. (Edit) Sorry, I was referring to the control you pull down from the upper right (notification bar?). I stopped using the widget when I found that the pulldown does everything the widget did.

---------- Post added at 12:50 PM ---------- Previous post was at 12:42 PM ----------

I believe an earlier build of CM11.0 had the ability to enable this Security feature. Now under Settings/Security the last item is App Security but does nothing.
[Nook Color Android Development] andtron:
This is the recovery 6.0.4.5 I used: http://www.mediafire.com/?7g38kesrl3b0978

By the way, it is backwards compatible with 4.3 and early, so the recovery could be used when you decide to flash back and forth.

I have a brief instruction a few posts back on how to update the recovery.

---------- Post added at 04:48 PM ---------- Previous post was at 04:38 PM ----------

I prefer the widget because one click is all you need, no need to drill down extra pages. That is why they are called widgets :)

By the way, it works on the 4.3 and 4.2. In the case of kk, the status of the location should be in sync in both cases (widget and inside settings), but they are not. The wifi and sync on the same widget both work.
[Nook Color Android Development] steven676:
There's quite a bit of stuff busted upstream at the moment -- Bluetooth most notably. That's the downside to living on the edge :P

I don't think there's any work going on on the default launcher right now -- the new, "improved" Trebuchet should become the default launcher soon, and that's where work is going at the moment.

I don't think reboot is actually slower (in terms of wall-clock time) than previous versions -- the boot animation freezes at several points, though, which does give that impression.

Widgets are very slow to come up on slow devices because of 4.4's throttling of services that start on boot (in order to prevent the system from killing itself trying to start everything at once). There's probably something that can be done on that front (prioritizing user-visible stuff in the startup order, for instance), but it'll have to be done upstream.

This is probably because we don't have a GPS. I suspect we need to indicate to the Android framework that that's the case.
[Nook Color Android Development] rino757:
I flashed it, but I get

E:Error in /storage/sdcard1/MROM-10.1-20131003-encore.zip

(Status 7)

Installation aborted
[Nook Color Android Development] polymath257:
Yes, I do. The problem seems to be with the build. The recovery worked well for previous cm11 builds.

Another note: the build I am currently doing (sync'd this morning) had two errors in

/packages/apps/Settings/res/values-ca/cm_translations.xml

One was a parse error on line 63 (no brackets needed for the text)

Two were lack of \ before apotrophe's in line 668 (one for l'arrancada and one for d'error)
[Nook Color Android Development] steven676:
Sync again -- it appears the offending commit has been reverted. As long as CM doesn't do mandatory automatic build tests before allowing commits through to the repositories, we're going to get build breakages like this once in a while -- if you don't want to hunt down the breakage yourself, the usual procedure is to wait a few hours and then sync again. (Well, except for the days immediately following an upstream AOSP release -- the build breaks often enough then that it's frequently best to avoid syncing for a while once you hit source that works ...)
[Nook Color Android Development] polymath257:
I don't mind tracking them down. I'm just not sure what the protocol is for informing people.

---------- Post added at 06:10 PM ---------- Previous post was at 05:48 PM ----------

Newest build failed to install also. It also built with a name of "cm-.zip" and was 147.2 MB in size (as opposed to 184.3 MB for the 20140117 build).
[Nook Color Android Development] andtron:
hi, Steven,

Thanks for the explanations, much appreciated.

---------- Post added at 07:59 PM ---------- Previous post was at 07:10 PM ----------

Where did you get this error, inside CWR 6.0.4.5?

Inside the recovery 6.0.4.5 so far I only used it for backup and restore, not install to go back to older CM, so I am not sure if that is a problem to it.

Also MROM has a configuration difference in that after it booted up, its sd0 and sd1 ares wapped. I have a pos on how to swap them back:

http://xdaforums.com/showthread.php?t=1904129&page=32
[Nook Color Android Development] unibroker:
I just built again (within 24 hours of my first build) and the results of an ls -al are

185393655 Jan 25 00:24 cm-11-20140125-UNOFFICIAL-encore.zip

185393886 Jan 25 16:54 cm-11-20140126-UNOFFICIAL-encore.zip

. The January 25th build was following a "make clean" and the Jan 26th was not.

---------- Post added at 05:40 PM ---------- Previous post was at 05:05 PM ----------

BTW, I found I had to go in and remove our crc7 patch before my build would complete.
[Nook Color Android Development] fattire:
Who amongst you wishes to make a contribution?! WHO, I ASK?!

in encore.mk:

frameworks/native/data/etc/android.hardware.location.gps.xml:system/etc/permissions/android.hardware.location.gps.xml \

change the above to not include gps. Just say:

frameworks/native/data/etc/android.hardware.location.xml:system/etc/permissions/android.hardware.location.xml \

Someone build it and let me know :)
[Nook Color Android Development] hwong96:
Five hours into the build and I get the following error:

Copying: /home/hubert/android/system/out/target/common/obj/JAVA_LIBRARIES/webviewchromium_intermediates/emma_out/lib/classes-jarjar.jar

Jar check: /home/hubert/android/system/out/target/common/obj/JAVA_LIBRARIES/webviewchromium_intermediates/jar_check_ok

collect2: error: ld returned 1 exit status

make: *** [/home/hubert/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/libart_intermediates/LINKED/libart.so] Error 1

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

hubert@hubert-Qosmio-F55:~/android/system$

Any ideas what went wrong? Repo int, repo sync, etc all went ok.
[Nook Color Android Development] unibroker:
Same behavior as before your requested change. BTW, my pulldown (Quick Settings Panel) from the top right edge of the screen supercedes the action of this widget. While I can't turn off location from the widget, when I pulldown from the right top edge of my screen and press location it not only turns off location here but also the widget. This was the action prior to your requested edit.
[Nook Color Android Development] andtron:
It means the ld didn't find libraries needed for your application.

The possible reasons: bug in the application code or you didn't install (improperly installed) some libraries.

Is this the very first time you do the build? try to update your java library.

Also try cd to the /home/hubert/android/system/out/target/common/obj/JAVA_LIBRARIES/webviewchromium_intermediates/emma_out/lib or the mentioned folders to see if your are missing those jar or so files.
[Nook Color Android Development] fattire:
Was this a make clobber build?
[Nook Color Android Development] unibroker:
No. I did a make clean build on Friday if that matters. I will start one now and report back. (edit) I just reread your post on make clobber/clean.
[Nook Color Android Development] hwong96:
First time building CM11 . I've built CM10, 10.1 with no problems previously.
[Nook Color Android Development] polymath257:
Well, I completely removed by repo, did repo init again from scratch, etc and then built the cm11. This now installed just fine.

This leads to a few questions, though.

1) I was also building for other devices (vivow) in other directories that were initialized using repo init --reference. Is it possible that these other

builds 'confused' the build for encore?

2) If that is what happened, is there a suggested way to build for more than one device on the same machine? is the --reference flag on repo

to be avoided in this case?

3) How can I determine when two devices can be built from the same working directory or not?

---------- Post added at 04:02 PM ---------- Previous post was at 03:41 PM ----------

I found this happened when I reduced the amount of RAM allocated to my virtual mchine. If I only have 4GB, the loader crashes. If I have 6GB, it does fine.

YMMV
[Nook Color Android Development] pmgnet:
so close to build?!

Finally just wiped and started all over. Building for 148 minutes and got: http://pastebin.com/4MF8J7Q1

Any ideas?

Trying another 'brunch encore' now.

---

That didn't help. Same error.
[Nook Color Android Development] unibroker:
My make clobber just finished. I can turn location off and on depending on how I answer the Location Consent to data collection popup which appears right after I turn location on. If I "disagree", I can turn location off. If I answer "agree", I can't turn it off.
[Nook Color Android Development] steven676:
In theory, if that happens, that would be a bug in the device/ tree for that device. In practice, I don't know how well-tested that is; that said, I build AOSP for crespo and maguro out of the same source tree without problems. (If you had changes elsewhere in the source tree for that device -- for example, modifications in frameworks/native or frameworks/av -- that's a different story, though that shouldn't cause the build system to get so confused it doesn't know how to name the output.)

The safest way is to have completely independent copies of the source tree for each device -- that's a huge waste of disk space, though.

I'm not 100% sure, but this is a guess: check for files named Android.mk in each directory of the device source, and look for something like https://github.com/CyanogenMod/android_device_bn_encore/blob/cm-11.0/Android.mk#L29 in them. The entire contents of the file (except comments) should be guarded by a check like that to prevent anything from that directory from affecting builds for other devices. (This isn't foolproof -- for example, if the Android.mk unconditionally includes other makefiles, but all of those files' contents are guarded so that they only affect builds for that device, that would work too.)
[Nook Color Android Development] andtron:
Yup, same here after the build today.

However it doesn't respond on the location change via the pulldown, but ok from the regular setting menu.

---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------

Just a wild guess, did you install the python?
[Nook Color Android Development] polymath257:
There are some changes in hardware/qcom in chilly's vivow source. Could that have been the problem?

Would I need an independent source tree for such?

---------- Post added at 08:13 PM ---------- Previous post was at 08:09 PM ----------

I can change the location settings from the Settings menu. If I *agree* to the location consent, I can turn location off and on via the status bar. On the other hand, if I *disagree*, I can turn *off* the location from the status bar, but the bar doesn't show the change (Settings menu does). Once it is off, however, I cannot turn it on again.
[Nook Color Android Development] pmgnet:
Yes, and thanks. Python is there. What made you think from this that python wasn't present? Someone on IRC said my python version was good and latest.

I ran 'brunch encore' again and got this: http://pastebin.com/4MF8J7Q1
[Nook Color Android Development] andtron:
The wild guess was due to the errors had been related to the .py files.

Sorry it didn't help.
[Nook Color Android Development] unibroker:
Successfully built yesterday now repo sync error

At the end of today's repo sync I get the following:

Traceback (most recent call last):
File "/home/jim/.repo/repo/main.py", line 418, in <module>
_Main(sys.argv[1:])
File "/home/jim/.repo/repo/main.py", line 394, in _Main
result = repo._Run(argv) or 0
File "/home/jim/.repo/repo/main.py", line 142, in _Run
result = cmd.Execute(copts, cargs)
File "/home/jim/.repo/repo/subcmds/sync.py", line 657, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/jim/.repo/repo/project.py", line 1106, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/jim/.repo/repo/project.py", line 2074, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/jim/.repo/repo/project.py", line 2227, in rev_list
p.stderr))
error.GitError: CyanogenMod/android_bionic rev-list (u'^53f15d0325feeaf7e58dc79fce4ddf55e0a64b7a', 'HEAD', '--'): fatal: bad object HEAD

I believe someone else recently stated having a "py error" so maybe there is something up with the repo? I'll try repo sync again later tonight.

Edit: user error (in wrong directory).
[Nook Color Android Development] steven676:
A few notes ...

Official CM11 nightly build generation was turned on this morning, so we should have nightly builds just as soon as the autobuilders get around to making some. (Based on the build logs for the past few days and where we slot into the (alphabetical) build order, I'd guess that's going to be around 4 AM tomorrow UTC-8 time, but that's just a guess and is subject to change anyway.)

As such, the ban on binary builds of Android 4.4/CM11 is lifted (yes, you can go and race the CM autobuilders if you really want ...).

Disk space really shouldn't be a problem again for a while after this patch to remove ~30 MB of Latin IME spelling correction dictionaries from the "mini" build was merged. I think the goal is to provide a dictionary downloader, but if you really need one of these dictionaries now, grab it from https://github.com/CyanogenMod/andr...s/packages/inputmethods/LatinIME/java/res/raw and follow the instructions in this commit message.