yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] polymath257:
OK, just before the st_register failed message for bluetooth, there is a collection of messages of the sort

(stk) :ldisc installation timeout

(stk) :ldisc_install = 0

(stk) : timed out waiting for ldisc to be un-installed

This is repeated a few times with 0 and 1 in the second line alternating.

Such messages do not appear in cm-10.1.3.1. Furthermore, when I click on the slider turning on bluetooth in cm-10.1.3.1, I get messages like

(stc) : st_register(2)

(stc) : add_channel_to_table: id 2

and then the same with st_register(3). Nothing like these messages appear in cm-11.0

---------- Post added at 10:59 AM ---------- Previous post was at 10:15 AM ----------

OK, after a bit of Googling, I think I found the problem with Bluetooth. The erros I posted before are seen on PandaBoards and are also associated with bluetooth issues there (even preventing android from booting). There, the problem is that a program named uim is having troubles. Well, the dmesg on cm-11.0 has an interesting line:

<3>init: cannot find '/system/bin/uim-sysfs', disabling 'uim'

I did a search of /system/bin on cm-11.0 and there was no uim-sysfs file, but there was such a file in /syste/bin for cm-10.1.3.1.

Now the question is how to get uim made.
[Nook Color Android Development] fattire:
It's been a while, but this is related to the shared transport that the nooks use w/the wifi/bluetooth chipset (wl1271) where the kernel needs a userspace process (run in init.encore.rc line 240)...

See:

http://omappedia.org/wiki/TI_Shared_Transport_Description_and_Support

http://www.omappedia.org/wiki/Wilink_ST

http://omappedia.org/wiki/ST_migration

http://git.omapzoom.org/?p=platform...d5e5007c06d90b9fb55c509a57f9dfe8b2b32;hb=HEAD

Wish I had a little time to take a look-- maybe next week if you guys don't figure it out.
[Nook Color Android Development] polymath257:
I attempted to put a version of uim-sysfs from cm-10.1.3.1 into /system/bin for cm-11.0

For emmc, there wasn't enough space (surprise!)

For an SD card install, I was able to put it in and make it executable.

The Bluetooth specific error message is now gone.

However, the messages relating to the timeout of ldisc are still there.

It appears that st_register is now successful and add_channel_to_table runs on a few channels, but immediately there are messages for remove_channel_from_table.

The slider for bluetooth in settings slides over then automatically slides back to off. Other devices do not see the Nook.
[Nook Color Android Development] bowguy:
The a2dp package has changed a lot from 10.2 to 11. In addition a major merge was committed 6 hours ago:

https://github.com/CyanogenMod/andr...mmit/2d30e4a060e7d963234ce7a7c06367ea7891d121

Steven676's patch posted below did the trick. Bluetooth now working

Thanks!.
[Nook Color Android Development] steven676:
Okay, wow, yeah. I finally had a chance to check my own installation -- 444 MB including gapps. Clearly, even if it fits (barely) in its current state, that's not a sustainable situation ... We're going to have to think about ways of freeing up room, extending /system, or both.
[Nook Color Android Development] polymath257:
The problem is I only see 34M left on the internal card. Not much room to grow.
[Nook Color Android Development] steven676:
A preliminary patch to do surface dithering for 16-bit color displays on CM11 is here: https://gist.github.com/steven676/7957779

I'll try to find time to get that submitted upstream this weekend, though I can't make any promises. EDIT: This was submitted (slightly modified) as http://review.cyanogenmod.org/55864.

Aha -- the BoardConfig flag to enable building of the TI-specific Bluetooth components changed from under us in CM11. Fix committed -- I verified this works by performing a BT file transfer from a Galaxy Nexus.

You'll note that we build a libbt-vendor.so from hardware/ti/wpan as well as the uim userspace driver initializer -- that's why copying over uim-sysfs from an existing build isn't sufficient.

That's the 2.6.32 kernel used for CM7. CM10/10.1/10.2/11 for encore all build the kernel from the same source tree.

These messages are all noise -- they'll sometimes appear even on a working system, depending (I think) on the specific timing of when uim-sysfs runs.
[Nook Color Android Development] steven676:
Putting CM for encore on a diet

I landed a bunch of changes in the NookieDevs tree to try to reduce the install size, though I think all of these plus http://review.cyanogenmod.org/55888 are good for a few hundred KB at most. There's also a change to shed live wallpapers and a couple other packages in my tree, which saves about 10 MB, but you'll need to apply http://review.cyanogenmod.org/55911 (against vendor/cm) to build successfully. Please test -- I think everything we shed is truly unused, but it'd be better to find out otherwise sooner rather than later.

Beyond that, there are only a couple other "easy" wins that I can think of for reducing install footprint:

Reducing the number of ringtones and notification sounds installed. We'd need to make some adjustments to CM makefiles -- right now, even the "mini" config pulls in the entire package of sounds.

Eliminating the ext4 journal on /system, which should save about 8 MB. There's little point in having a journal on a filesystem that's almost always mounted read-only. I'm not clear how we want to do this, though -- ideally, we can pass the option at mkfs time, but it may work out to be easier to just use ext2 as the filesystem instead.

We'll have to see how bloated the "official" Google apps package for CM11 is going to be before deciding whether we need to make more drastic changes.
[Nook Color Android Development] bowguy:
My build as of 12/14/13 is working great on an SD install. Netflix working, YouTube working, BT etc. No issues so far. I have 504MB in /system and a du of the directory is at http://pastebin.com/BpgWqmL3 for reference.

I'll work on building the above changes and let you know.

Edit: Looks like /system is now down to 494M now. Performance looks the same so far.
[Nook Color Android Development] tdm:
Agree.

With the move to "lock" ro mounts in kk there is little reason for a journal on /system. There are ext4 features besides the journal but I very much doubt that any are all that compelling.
[Nook Color Android Development] weldawadyathink:
Was this locking of ro partitions ever backported to cm10.2?
[Nook Color Android Development] tdm:
Don't think so. But it wouldn't be hard to do. Why?
[Nook Color Android Development] bowguy:
SD or EMMC ? I think you ran out of room during install:

E/dalvikvm( 6961): dlopen("/system/lib/libwebp_android.so") failed: dlopen failed: "/system/lib/libwebp_android.so" is too small to be an ELF executable.

My version is:

-rw-r--r-- root root 181476 2013-12-10 16:36 libwebp_android.so
[Nook Color Android Development] polymath257:
Looks like you are right. it is an EMMC install.
[Nook Color Android Development] weldawadyathink:
I have been getting some trouble with that on my phone so I was wondering if it was ever backported. If not, then either the dev of the cm10.2 port for my phone did something weird, or its something else. Thanks.
[Nook Color Android Development] steven676:
It looks like your source tree is incomplete or corrupt -- I'd try deleting external/chromium_org/third_party/icu from your source tree entirely and then running repo sync again.
[Nook Color Android Development] fly32:
Thanks, that solved that error..
[Nook Color Android Development] That Baker Guy:
thanks for this, spent all night trying to run these commands while booted into the rom, took 2 seconds to do it in recovery...
[Nook Color Android Development] gravitysandwich:
I have the same problem too, and I have absolutley NO idea how to fix it (first time building from source). I tried editing the the roomservice.xml in [source directory]/.repo/local_manifests/roomservice.xml. But there was no roomservice.xml, so i just created my own,and put this in there:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="NookieDevs/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>

and I did the repo init. and repo sync step again. Then I tried doing the breakfast encore command and gave me the error. I read a few pages back on how to fix this, but for me, it wasn't clear. So please, if you know how to fix it, be clear for my n00bness. Thanks.
[Nook Color Android Development] bowguy:
Did you do this?

$ cd ~/android/system/vendor/cm

$ ./get-prebuilts

http://wiki.cyanogenmod.org/w/Build_for_encore
[Nook Color Android Development] gravitysandwich:
Yes, I did that.

Edit: I’m almost positive I didn't miss a step till the breakfast encore command. I did this whole process 3 times, and read the whole wiki at least 5 or 6 times
[Nook Color Android Development] bowguy:
Try this.
[Nook Color Android Development] gravitysandwich:
Okay, after a couple hours, I attempted, and failed, so many times. And know I'm more confused then ever. I could NOT get cm10.2 on my nook. So he said to run unzip-files.sh and point it to a current cm zip file. So i changed directory to /home/jack/android/system/device/bn/encore and I did:

sudo ./unzip-files.sh /home/jack/Downloads/cm-10.2-20131222-NIGHTLY-encore.zip

and came with a crapload of errors saying:

Archive: /home/jack/Downloads/cm-10.2-20131222-NIGHTLY-encore.zip

End-of-central-directory signature not found. Either this file is not

a zipfile, or it constitutes one disk of a multi-part archive. In the

latter case the central directory and zipfile comment will be found on

the last disk(s) of this archive.

unzip: cannot find zipfile directory in one of /home/jack/Downloads/cm-10.2-20131222-NIGHTLY-encore.zip or

/home/jack/Downloads/cm-10.2-20131222-NIGHTLY-encore.zip.zip, and cannot find /home/jack/Downloads/cm-10.2-20131222-NIGHTLY-encore.zip.ZIP, period.

Nevertheless, I attempted to fix this, and still same error. Soo I continued, because I saw a bn folder with a lock on the icon in /home/jack/android/system/vendor. and I thought it worked. I then ran

$ source build/envsetup.sh

$ breakfast encore

and it seemed like it worked.

The next step said to extract proprietary blobs. But didn't I already do that? so I skipped it, and turned on caching and started the build. then about a minute later, it stopped. I didn't see any errors or a PACKAGE COMPLETE sign. So now I'm wondering what I did bad. (probably alot of things)
[Nook Color Android Development] kingsteve032:
Where are you guys pulling the newest source code from?
[Nook Color Android Development] DizzyDen:
Try:

sudo ./unzip-files.sh ~/home/jack/Downloads/cm-10.2-20131222-NIGHTLY-encore.zip
[Nook Color Android Development] gravitysandwich:
Thanks, but I already figured that out out a couple days ago. I got the build working and flashed successfully on my nook. I also just had to add a couple lines to my roomservice.xml file.
[Nook Color Android Development] steven676:
Feedback on hwcomposer on CM11 please?

For those of you who are building CM11, could you please try a build with the sources I just pushed to my personal Github account:

https://github.com/steven676/android_device_bn_encore/tree/cm-11.0 (device/bn/encore)

https://github.com/steven676/ti-omap-encore-kernel3/tree/encore-omap3-3.0.y (kernel/bn/encore)

https://github.com/steven676/android_hardware_ti_omap3/tree/cm-11.0 (hardware/ti/omap3)

Assuming things don't blow up, you should end up with a hwcomposer-enabled build (check for /system/vendor/lib/hw/hwcomposer.omap3.so in the output to be sure). I'd be interested to hear your experiences with performance and stability on hwcomposer-enabled CM11 builds; assuming we can get the kinks worked out, I'd like to enable hwcomposer on the CM11 branch.

A bit of background: when we tried enabling hwcomposer on CM10.2, things didn't go so well. Interestingly, though, the bug/crash symptoms for hwcomposer-enabled CM10.2 on encore were nearly identical to the problems which all PowerVR devices runing AOSP 4.4 experience (and which seem to be mitigated in CM11), and I have yet to experience anything like that while playing with hwcomposer-enabled CM11 builds on encore.
[Nook Color Android Development] Zippy Dufus:
Please post your local_manifest.xml.
[Nook Color Android Development] andtron:
Hi guys,

I have decided to get into the building game, so far, by reading the "How to Build CyanogenMod for Nook Color", I get to the line:

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

Do I need to change it to cm-11.0 in order to build the 11?

TIA.
[Nook Color Android Development] fattire:
Yup.
[Nook Color Android Development] andtron:
Thanks fattire.

After creating and editing the roomservice.xml file as posted by others and I did the "repo sync" successfully.

But when I came to "breakfast encore", I got the following errors:

~/android/system$ breakfast encore

including vendor/cm/vendorsetup.sh

build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/bn/encore/cm.mk]]: "vendor/bn/encore/encore-vendor.mk" does not exist. Stop.

Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Traceback (most recent call last):

File "build/tools/roomservice.py", line 76, in <module>

result = json.loads(urllib.request.urlopen(githubreq).read().decode())

File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen

return _opener.open(url, data, timeout)

File "/usr/lib/python2.7/urllib2.py", line 410, in open

response = meth(req, response)

File "/usr/lib/python2.7/urllib2.py", line 523, in http_response

'http', request, response, code, msg, hdrs)

File "/usr/lib/python2.7/urllib2.py", line 448, in error

return self._call_chain(*args)

File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain

result = func(*args)

File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default

raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

urllib2.HTTPError: HTTP Error 403: Forbidden

build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/bn/encore/cm.mk]]: "vendor/bn/encore/encore-vendor.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_encore'

** Do you have the right repo manifest?

Anyone knows where the vendor/bn/encore/encore-vendor.mk file is created?

TIA.
[Nook Color Android Development] steven676:
extract-files.sh from an existing encore running a CM10+ build. That said, we should really nuke the change that causes breakfast to fail, because it also breaks some recovery builds and seems to be causing a lot more grief than it's saved. (Also, I should update/add a script to extract the proprietary blobs from an OTA package, which would be easier for a lot of people.)
[Nook Color Android Development] andtron:
Thanks, Steven.

It sound like a chicken-and-egg problem. I ran into this problem because I had never built the older version, hence extract-files.sh was never run before. After running it, the problem went away.

I am building it right now, not sure how far it will go :).

By the way, I am using the openjdk-6, should I use the oracle java 6?

TIA.
[Nook Color Android Development] bowguy:
I have always used openjdk-6 with no problems. A nasty warning message but then no problems.
[Nook Color Android Development] andtron:
After running for 5 minutes, my build stopped for the following error (I included the trail end of the msg):

:

:

target thumb C: vim <= external/vim/src/ui.c

external/vim/src/regexp.c: In function 'get_char_class':

external/vim/src/regexp.c:474:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

target thumb C: vim <= external/vim/src/undo.c

target thumb C: vim <= external/vim/src/version.c

target thumb C: vim <= external/vim/src/window.c

make: *** No rule to make target `vendor/bn/encore/proprietary/bin/pvrsrvinit', needed by `/home/hkhoo/android/system/out/target/product/encore/system/bin/pvrsrvinit'. Stop.

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

external/vim/src/tag.c: In function 'add_tag_field':

external/vim/src/tag.c:3765:10: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

external/vim/src/screen.c: In function 'win_redr_custom':

external/vim/src/screen.c:6079:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

external/vim/src/spell.c: In function 'put_sugtime':

external/vim/src/spell.c:7869:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

------------------

I found out that the vendor/bn/encore/proprietary/bin folder is empty, so I am wondering if I also need to do the "repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2" before I do the 11.0?

TIA
[Nook Color Android Development] steven676:
OpenJDK 6 falls into the "unsupported, but probably works" gray area; the history of OpenJDK 6 is complicated (see slide 4 of this 2011 FOSDEM presentation by Oracle's Joe Darcy for a visual), and while the implementation passes the official Java compatibility tests, it's definitely not the same thing as the official Sun JDK.

At some point (hopefully in the not-too-distant future??!?), the Android platform should formally move to Java 7 and this should go away as a problem -- the official Oracle JDK builds from the OpenJDK codebase since Java 7.
[Nook Color Android Development] bowguy:
This is working much better for me. Smoother and better graphics. It can handle complex web sites without crashing. Will soon be my daily OS

Thanks!
[Nook Color Android Development] xflier:
how to change roomservices.xml to use them? a noobie here. Thanks!
[Nook Color Android Development] andtron:
xflier, please look at this page: http://xdaforums.com/showthread.php?t=1370873&page=358

Posted by weldawadyathink (post #3572).
[Nook Color Android Development] xflier:
I did the changes mentioned at that page, and I was able to build CM 11.0 by myself. I was asking the changes needed to use Steven676's new sources for a hwcomposer-enabled build. Thanks though!

Edit: I figured it out by myself. I can tell browser experience is better now. Thanks!

Edit2: some interesting observations. I tried MX Player with HW+ or HW, and Netflix (1.8.1 version). the Video playing has some shakes or blinks, the video was not stable. However, if I check Disable HW Overlays in settings, the issue was gone. unfortunately, I have to check it every time I reboot the nook color. I will try a couple of more builds.
[Nook Color Android Development] afzalarsalan:
New repos for building

Is there any disadvantages to using steven676's repos for building from here on out other than the possibility of a broken build from being bleeding edge and untested?
[Nook Color Android Development] meteorrock:
I love bleeding edge development. <333 Great work nookie devs. omnonmomom kitkat :p

Build it and help us. Do you use netbeans? To help, check out my thread down in cyanogemon nook color on how to build and help the developers here if you do not know how. Here is a link. http://forum.cyanogenmod.com/topic/...to-learn-how-to-code/page__st__60#entry400694

You will need ubuntu and some android SDK tools for debugging. Testing falls on us too.
[Nook Color Android Development] afzalarsalan:
Lol I've already built it and am running it right now. Will probably edit the thread on how the build is after a couple hours. So far it seems pretty nice and smooth :laugh:
[Nook Color Android Development] polymath257:
I did the standard cm-11.0 build and it is currently on my emmc. I have a stock ROM on sdcard. I would like to make it possible for the cm11 to access the SDCARD partition of the sdcard, but there is no vold.fstab file under /etc. Any suggestions? Where is fstab done in the new cm11?
[Nook Color Android Development] leapinlar:
It is built into the init files and cannot be changed without modifying the build. But since you are building it you can change it. I believe it is in init.encore.rc.
[Nook Color Android Development] polymath257:
I think I found it. In fstab.encore, which is used in init.encore.rc. I assume that I change the 'auto' to '4' just as before?
[Nook Color Android Development] leapinlar:
Yes
[Nook Color Android Development] afzalarsalan:
There wouldn't by any chance be a way to expand the apps partition on the emmc to larger than 1GB. The 6 or so GB of "sdcard" storage is some what being wasted and I do remember that some newer nooks had the partition enlarged from the factory.
[Nook Color Android Development] leapinlar:
Yes, look at this thread:

http://xdaforums.com/showthread.php?t=1094371
[Nook Color Android Development] racks11479:
Wow.. KitKat on the nook color. The devs never seems to amaze me!!! Now... how do i build again??? ;)
[Nook Color Android Development] aqtrans:
I believe the wallpaper scrolling has to do with a lack of hardware acceleration, maybe some kind of fallback mode? I know I had the same thing going on with ICS on my Captivate in the early alphas before there was at least some hardware acceleration support.
[Nook Color Android Development] biohazrd51:
It does, however, it takes a second and stretches before it fixes itself. Nothing deal breaking in my opinion.

Annoyed Ornithoid
[Nook Color Android Development] alton987:
Opp any chance you can update thread title with version # and date so everyone can tell when a update is released.

Thanks
[Nook Color Android Development] JustisLewis:
Anyone else having ridiculously high Android OS battery usage? Mines at 66% after 19 hours. My Nook has lost almost 85% of its battery after just sitting on my desk.
[Nook Color Android Development] Ronin3178:
Did you adjust the wifi policy? I found it was set to never off, but when I changed to off with screen it had to be toggled an extra time to connect to a network.

Disgruntled aviators
[Nook Color Android Development] cybertimber2007:
I noticed that there is something keeping the system awake

Settings > Battery > Android OS > Keep Awake = around the amount of the system uptime. For me, it's exactly that value.

Guessing this is to prevent a SOD.

---------- Post added at 07:05 PM ---------- Previous post was at 06:38 PM ----------

Unfortunatley I don't... not anywhere that can handle that much load anyway.

I can. Well for those flashing CM7 and then this, they aren't wiping. But the biggest thing is that the install script checks /system/app for nfcgoogle.apk or something. The ICS gapps install script seems to install everything, and then run the install.sh script... which means it will have the nfc file every time.

BTW:

These gapps should be fine for everyone... meaning no NFC issues here or there from a straight ICS install.

GAPPS - RENAME TO gapps-gb-ics-4.0.1-small.zip when using verygreen

gapps-ics-4.0.1-small.zip

Now if I can just figure out how to remove 5.5mb more, you'll be able to fit both this and ICS on verygreens /boot.
[Nook Color Android Development] Homer_S_xda:
OT I would just like to say Ubuntu has jumped the shark. What the *&*$ is that shell they have gone to? The frakkin' thing is un-navigable. I could use Ubuntu not more than 6 months ago. Now, forget it!

Homer
[Nook Color Android Development] jschill31:
Hello,

Why bother, just use a program like "Partition Master" to extend the boot partition to around 200mb. Do this directly after writing Verygreens to the SD card and before flashing the rom. Then you have room enough for the full size Gapps and the rom on the boot partition and are ready to flash.

Cheers
[Nook Color Android Development] gotrubberducky:
I have the same problem, with WiFi on or off. The problem is that android os says "always on" for the total amount of time the device has been on. They had the same issue with the first few builds of ICS on the Fascinate, it was just recently updated and the android os always on is very low. My fascinate after 8 hours android os keep awake is only at 11 min