yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] krylon360:
keyodi fixed the audio issue in the codec. he had me test the file in my new build tonight, but had to run before he could push it, so I pushed it up to the kernel.

Lets just say...WOW..the Nook is LOUD!

Thanks Keyodi
[Nook Color Android Development] cpkroboth:
Yippeee.. I got it the Repo Sync working. Thank you to those who replied.

Well it ended up not being a network issue. Lets just say having the .Repo directory in the Home folder, with the local_manifest.xml, will cause you many hours of frustration. I put the laptop away for Saturday and most of Sunday, and looked again last night and found that I had created the folder and file in the wrong spot.

Deleted that folder and contents. Recreated the local_manifest.xml in the correct spot, just started the repo sync about 5 minutes ago.

P.S. I am learning just enough to be dangerous. Not sure if a good or bad thing.
[Nook Color Android Development] jschill31:
Cool, just never watched my screen before while building...a lot of stuff goes by and amazingly a lot of warning messages.

Cheers
[Nook Color Android Development] krylon360:
if someone wants to test out bt tethering on CM10, add this to your build. built it with my build a few minutes ago.

Not sure if my stock sprint SGS2 blocks BT tethering, or if it's still not working.

goes into /system/bin/

http://krylon360.com/file_host/sk4g/uim-sysfs
[Nook Color Android Development] newellj79:
Is anybody else still having issues with the touchscreen not working? I switched from building it myself to trying andbot because I could not get the touchscreen to work. Built with andbot last night and still no stinking touchscreen! Grrrrr.
[Nook Color Android Development] keyodi:
dmesg log?
[Nook Color Android Development] jromney:
This is a new message as I build tonight....

*** Forcing "make installclean"...
*** rm -rf out/target/product/encore/data/* out/target/product/encore/data-qemu/* out/target/product/encore/userdata-qemu.img out/host/linux-x86/obj/NOTICE_FILES out/host/linux-x86/sdk out/target/product/encore/*.img out/target/product/encore/*.txt out/target/product/encore/*.xlb out/target/product/encore/*.zip out/target/product/encore/data out/target/product/encore/obj/APPS out/target/product/encore/obj/NOTICE_FILES out/target/product/encore/obj/PACKAGING out/target/product/encore/recovery out/target/product/encore/root out/target/product/encore/system out/target/product/encore/dex_bootjars out/target/product/encore/obj/JAVA_LIBRARIES out/target/product/encore/obj/FAKE
*** Done with the cleaning, now starting the real build.
[Nook Color Android Development] nukedukem:
I was pleasantly surprised to return to the nook forum and find development on a JB rom. Is the current state of development bootable? All I've done is sync the new JB source and add a nook local manifest I found a few pages back. My first build resulted in nothing but a black screen so I was just wondering if the current state of this rom is bootable so that I can know if the problem is on my end or not and start to troubleshoot. Nice work fellas!
[Nook Color Android Development] BobbyBest:
There's a vid flying around in the thread by one of the devs how he's playing YT HQ with sound, so yes this ROM can boot.
[Nook Color Android Development] ionz:
Hey guys,

First off thanks for all the hard work put into these builds. Its fun seeing major changes within a 2 week span :p and seeing the commits on github.

I did run into the wake lock issue on in the jb builds I made but it seems to better now (I have to do more testing though).

But with the wake lock, I have wifi issue of it working the first time around then randomly failing and doesn't recover

:/ I want debug it or at least try to but dmesg doesn't seem to have any useful info. Any tools or logs I should look into?

Thanks

PS: You guys dragged me out off lurking for over 3yrs! Lol, my first post!
[Nook Color Android Development] krylon360:
Reboot into recovery then reboot back to the system. You'll have working wifi. Odd I know, but it works.
[Nook Color Android Development] lekofraggle:
Ionz and anyone else who has sleep working,

How did you fix wakelock? I am good until I leave my nook asleep too long. Then I get SOD.

At which point I cannot pull a log.

(At least not yet).

I am using wakelock set to partial. I also have the wifi set to turn off on screen off with green power.

Other than that my builds are insanely stable and quite zippy :)

~leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] jschill31:
Hello,

If you are using Wakelock you should leave wifi on with screen off. I think you will have better results. This way the wifi does not need to re-connect.

Cheers
[Nook Color Android Development] nukedukem:
I can't seem to make a bootable build. Can anyone help me? The OP is regarding CM9 but I found a tut by fattire for CM10 about 20 pages back or so. I've been following the tut and 3 builds later I'm still getting a black screen on boot. Is there a source for the most up to date info on building CM10? I think I'm missing some key info such as replacing the kernel or adding some patches perhaps? I realize I'm being vague about my technical difficulties, I'm just wondering if there is more to it than just the CM10 tutorial by fattire? It would appear from the tut I'm reading that syncing the CM repo and adding the custom local manifest is sufficient but I've seen numerous patches scattered throughout the thread and I haven't been following these developments so I don't know if they have been submitted yet.
[Nook Color Android Development] ionz:
._O

wth?

It works and I'm grateful....but where's the logic in that lol?

Is the build messing with bootloader in some way?

---------- Post added at 04:19 PM ---------- Previous post was at 04:03 PM ----------

Actually I didn't do anything; I figured there was a commit was made for it....or somebody had inadvertently fix it..

All I did was a repo sync and make clean and build yesterday. (cm-10-20120815-UNOFFICIAL-encore.zip

EDIT:

I feel like I'm speaking too soon...I gonna play with it more..

Wasn't sure if make clean was necessary but my other builds (I think it was Aug 10th) had this issue of launching any app and causing the nook to reboot (kernel panic maybe?).
[Nook Color Android Development] ioos:
I'm trying to build CM10 and getting some errors. I've set it up twice and even re-downloaded the source, but after entering "brunch encore" it errors out with:

host C: libicuuc <= external/icu4c/common/utrace.c
ERROR: could not open directory /home/ioos/projects/android/build-nook/out/target/product/encore/obj/KERNEL_OBJ/../../system/usr/lib/modules/99.98.3.0.8+: No such file or directory
FATAL: could not search modules: No such file or directory
make[2]: *** [_modinst_post] Error 1
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/ioos/projects/android/build-nook/kernel/bn/encore'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
external/icu4c/common/utrace.c: In function 'outputPtrBytes':
external/icu4c/common/utrace.c:147:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

This is on 64-bit Arch Linux. I'm using the local_manifest.xml file linked to in the CM10 build guide. Any guidance would be appreciated.
[Nook Color Android Development] tomsawyer14:
Did you do the step that copies files from your Nook? I may be wrong but that seems like a possibility.

Step 4:

Next, install the proprietary files per the original instructions and run the ./setup-makefiles.sh script in android/system/device/bn/encore.
[Nook Color Android Development] lekofraggle:
Ioos,

I think you need to run ./get-prebuilts after a repo sync each time you build.

Everyone who helped me with SOD. I think I may have fixed it. I did not keep the icon in the status bar and I think the os killed wake lock. Now it has been working for 4 hours with no issue.

~leko

Transcribed by my pet Android
[Nook Color Android Development] ioos:
Hey guys thanks for the suggestions. I just ran each of these commands (from their appropriate directory) without any errors.

$ repo sync -j9
$ ./extract-files.sh
$ ./setup-makefiles.sh
$ ./get-prebuilts
$ . build/envsetup.sh

But "brunch encore" still ends with the same error. If I just try "lunch" then choose "cm_encore-userdebug" it fails immediately with the message "Dependencies file not found, bailing out." I've read earlier in the thread that that message can be ignored, but in this case it doesn't get past it so I thought it might be relevant.
[Nook Color Android Development] fattire:
Hmm, I'm wondering if the dependencies in question have to do with apt-get packages (or linux packages, speaking more generally) that you don't have installed... are you sure you have all the build tools and everything?

If you scroll up over the dependencies not found, does it give you a clue about which dependency is missing?
[Nook Color Android Development] mateorod:
You can build with that error, despite its ominous sound. I have been getting it forever. Any build errors you may get later are not necessarily related.

When I get the message, it is at the beginning of the build, which then eventually goes about its business of compiling.
[Nook Color Android Development] eyeballer:
This. The dependencies error relates to the CM build system, specifically "room service" - when you lunch for a device that you do not have the device/kernel repo for it will try to get it for you from the cm github. However, we're supplying manually (via the local manifest). If it won't let you lunch for encore, close your shell session and start a new one. Then it should find the relevant repo and the build will continue.
[Nook Color Android Development] ioos:
Installed all of the dependecies for building Android listed on the Arch Linux wiki. The only one I'm not sure about from the CM build wiki is "libesd0-dev". I don't know what package that is in Arch Linux. I opened a new shell and ran it and got this output.
[Nook Color Android Development] mateorod:
It ain't exactly like at the bed and breakfast. First you have lunch, then brunch. Or bacon, but let's keep it simple.

Enter

brunch encore

You can find libesd0-dev if you run sudo apt-get install libesd0-dev, it will recommend a package for you. I have had to install it when I was using the mkboot binaries on a machine that hadn't built source. But I think you may be alright, that is used on binaries you are going to end up compiling for yourself as the build progresses.
[Nook Color Android Development] ioos:
I understand that there is a difference between "lunch" and "brunch". I don't know how they're different, which is why I was showing that they failed in different ways.

I'm not using a debian based distro, so I don't have the apt-get command. I'm using Arch Linux, which doesn't seem to have a package with that name. I am using [testing], so is it possible that something is too new? Like maybe glibc? I'm really grasping at straws here.
[Nook Color Android Development] mateorod:
Lunch adds your device to the source tree. Brunch commences the build.

just type

brunch encore

Worry about libesd0 when and if it becomes a problem. It should not come to that. If it does, try pacman, I guess.
[Nook Color Android Development] sirrkitt:
I don't think it'd be that big of a worry. Build without it

The library it is complaining about is for esd aka enlightenment sound daemon if I remember correctly.

It's just a deprecated sound system that used to run on top of Alsa. I don't think Android uses it and it's probably got more to do with the emulator or something (just did a quick search for "Android esd" on google and that's all I could see)

If you're using Arch, I'd suggest installing yaourt and maybe searching the aur for a libesd package (it may even be on normal pacman repos)

I also don't recommend running Arch Testing for your build system unless you really have a need for bleeding-edge and likely less-stable packaged. Arch is rolling-release and already a lot more up-to-date than most other Linuxes. If you're having troubles with Arch and/or can't figure it out, I'd recommend starting out with Debian and then work your way toward Arch.

:)
[Nook Color Android Development] lekofraggle:
So, I am a teacher and use my nook a lot in the classroom. Now that the summer is almost over, I think I need more stability to move through the year.

I enjoy the speed of jb and do not want to lose that. So, can I build with 2.xx kernel

I need my nook to boot consistently it currently takes 3 or more times after a wipe

I need fewer kernel panics

Ac charging

USB host.

I thank you for all your hard work, but I tried to solve all these issues to no avail.

Sorry if this post is out of place and demanding or curt. I spent 5 hours just wading through bootloops after a kernel panic. My logs are not helping.

Leko

Transcribed by my pet Android
[Nook Color Android Development] jschill31:
Leko,

Sounds like your Nook is exactly what mine does. We should try to figure out what is different on our versions that the kernel hates. Whatever it is it started in early August for me. You and I seem to be the only ones with this issue. My guess is a slight variation with our digitizers. We seem to have screens that are not original but also not the new version. Mine was a B stock unit from BN, how about yours?
[Nook Color Android Development] lekofraggle:
Jschill,

Thank you for the level headed reply. It has been rough dealings with my nook this weekend.

I agree. There is a chance that mine is also b stock. I bought it shortly after release, but got it swapped out after a snafu with the sd card(note to self, they only go in one way and the store clerks do not know how to remove them when backwards).

Anyway, so it was a warranty replacement.

Any advice as to how to catch a logcat after the system crashes or while it boots?

Two pieces of evidence to back up your theory.

-when it boots the boot animation stalls. This is true even when I changed to nexus 7 style which worked until early August.

-sometimes after a boot, the touch screen is extra sensitive in some ways and input only works in the bottom left corner of a button. A few successful reboots fixes this.

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] jschill31:
Leko,

I only was able to get a logcat once...and it stalled so it never got to the point of fail. I have tried more than 20 times on several different clean builds since the beginning of August and never get a logcat to generate. I too have changed out boot animations to no avail. With the stock boot animation i get one revolution of the arrow then it locks up and fails. After several attemts to boot it will finally boot into recovery. I am usinging TWRP 2.2 as my recovery and have considered trying Clockwork again but have not. Which recovery are you using? I highly doubt that it has anything to do with our issue but would give me another reference not to try. I strongly beilieve that there is something in the kernel that does not like our version of Nook. This would also explain why we can't pull a logcat. I beleive I first reported this issue back at the end of July or beginning of August but it was just happening to me at that time. If you scroll back several pages you will find where I posted the bootloop issue. I kinda moved on chalking it up as my Nook kinda dying...

Cheers
[Nook Color Android Development] lekofraggle:
Jschill,

I use Twrp2.2 on an sd card.

I can boot and when it doesn't panic, I can do most of what I need.

However, recovering from a kernel panic is painful.

After the boot ani. Stall, it moves in a choppy manner to the next few frames, then it stoops and I get a boot.

But, if it needs to rebuild cache or dalvik, it shuts down (true black screen no backlight) before it finishes.

I was using Nova as a launcher, but got a crash just now with trebuchet.

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] jschill31:
Hmmm, maybe it is worth trying Clockwork again? I wonder if for some reason we are not getting a complete wipe using 2.2? I highly doubt it but you never know. I am traveling but maybe when I get home tonight I will give it a try. Might be worth getting some additional feedback from other Nook users who are not having any issues flashing and booting newer builds which recovery they are using....

Cheers
[Nook Color Android Development] lekofraggle:
Jschill,

Thank you. Great point. I did just get a log of the ui crashing. I noticed some wiered stuff with tasker so I froze it. I will continue to work on this.

Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] fattire:
Wiki for progress....

Here's a wiki on some progress for anyone interested.. Using it to keep track of how things are going, so please don't change anything unless you have something to contribute.

CM10 for NookColor WIP Wiki
[Nook Color Android Development] cybertimber2007:
@fattire @krylon360

The Netflix issue affects all CM10 according to Cyanogen.

https://twitter.com/cyanogen/status/236714029899468800

https://twitter.com/cyanogen/status/236733963509592064

Edit: Except: https://twitter.com/Paullie_Vicious/status/236861464445591552
[Nook Color Android Development] krylon360:
Tbh I wouldn't trust what PV says. Took him months to find the code for the AOKP swagger toggle and then said the toggle was broke because it didn't do anything. Lol

I know Steve has been trying to debug the Netflix issue which is why I'm not to worried about it right now.
[Nook Color Android Development] cybertimber2007:
Just wanted to make a note of it since I saw it on the wiki.
[Nook Color Android Development] tomsawyer14:
I wanted to try that patch mentioned in the wiki for the wakelock issue but I'm not quite sure how to convince git to use it. Still trying to learn how to use it.
[Nook Color Android Development] jschill31:
Hello,

Thank you for this. Is everything merged into the repo except GL acceleration for UI or are there other manual insertions? It is driving me nuts that I can no longer boot and get stuck in loopsville. I wonder if there is something I missed that I need to manually change on my end. Still not able to get a logcat before my Nook locks up but only on my CM10 builds.

Cheers
[Nook Color Android Development] lekofraggle:
At the moment, the big change on the wiki is using steven676's wifi drivers. Here is a quick tut on how to add it.

Full disclosure, I have not yet tried this with steven676's git, but adding this to your local_manifest should get the new wifi drivers.

It goes before the /manifest and do not allow any blank lines (I heard that can mess things up).

In the same vain as the classic fishing cliche, here is how you figure it out...

The project name is the path on git. It is in blue on the top of the git page (and also in the http or git copy line)

The path is where the download goes in your build environment. This is the root folder of all the folders and files which repo will replace. Fat tire gave us this one, but if you did not know, search your build for the folders which will be replaced. Know that everything in the path folder will be removed and the files on git will take its place (this is where my git fell apart).

If the repo is on github, use remote="gh" this is a variable you defined in your local_manifest

The revision is the branch of the files you are grabbing. You can see this on the git page under branch.

So, that is it.

Please let me know if I got this wrong.

~Leko

Edit: though I have not yet built with it, it does sync. Just be sure to add the " /" before the final bracket (if you copy and paste, you are ll set. You also want to remove fat tire's hardware/ti/wlan git. You cannot have two gits syncing to the same folder.

Edit 2: I had build issues after syncing. There seem to be some files missing.
[Nook Color Android Development] riverzhou:
we can get sgx vendor files from ti offical website:

http://www.ti.com/tool/androidsdk-sitara

http://software-dl.ti.com/dsps/dsps...Android_ICS_4_0_3_DevKit_3_0_0/index_FDS.html

http://software-dl.ti.com/dsps/dsps...0_3_DevKit_3_0_0/exports/beagleboardXM.tar.gz

beagleboardXM's SoC is omap3530 , renamed to AM37x .
[Nook Color Android Development] krylon360:
The version has to match what we are using inside of our pvr source in the kernel, otherwise, you get a black screen. Hence we aren't sure if we are allowed to redistribute them or not. We know rowboat is, but not sure if they have a license to or not.
[Nook Color Android Development] unknown_world:
Hell with license if we can't use it directly write instruction or write a script to get libs.
[Nook Color Android Development] lekofraggle:
hey all,

When I try to use Krylon's git referred to in the wiki, I get the following error...

build/core/base_rules.mk:171: *** hardware/ti/omap3/liboverlay: MODULE.TARGET.SHARED_LIBRARIES.overlay.omap3 already defined by device/bn/encore/liboverlay. Stop.

I tried to put the git in hardware/ti/omap3-compat first with the same error.

Do I have to edit the mk file in liboverlay (or delete the whole folder)? Or, am I missing something else?

~Leko
[Nook Color Android Development] fattire:
The wiki mentions deleting the folder from the device. That should do it.
[Nook Color Android Development] lekofraggle:
Doh. I am sorry I missed that. Thank you.

Transcribed by my pet Android
[Nook Color Android Development] chilre:
Thanks for the wiki. This finally forced me to take the plunge in compiling CM10. I was successfully able to compile and run with the default configuration. However, I am unable to boot when using Krylon's git with the OMX changes.

The wiki mentions to remove the liboverlay directory and to add hwcomposer.omap3 to device.mk. Where / how exactly do I do that?

I tried adding it to the PRODUCT_PACKAGES variable in device.mk. While I am able to compile successfully, the nook is unable to boot. I am also unable to get a logcat, so have no idea what is going wrong. Am I correct in assuming that the kernel fails to load? Any idea what I might be missing?

Regarding using the omapzoom's wlan drivers, from what I have been able to understand, the new compat-wifi drivers have split the code into a core module and chipset specific modules. So when using the omapzoom drivers, the location of wl12xx.ko has changed, while the wlcore* files are not present. I have currently modified the location of the wl12xx.ko file, and added the wl12xx_sdio.ko file (as replacement for the wlcore_sdio.ko file). Have I missed out anything else, or is this enough?

thanks again to all the devs for their work on the NC.
[Nook Color Android Development] fattire:
I think eyeballer was having a problem booting as well... not sure what the deal is at the moment. Sorry it's not booting yet, but congrats on taking the plunge.. you'll get it soon enough, no doubt.

As for the wifi modules... are you using the "standard" one I set up or sluo's more experimental ones?

Incidentally, if anyone here has a nexus 7, I put together some instructions for that tablet.
[Nook Color Android Development] chilre:
I am using sluo's modules. (leko had mentioned that some files were missing during the build, which was due to the location change of the .ko files)

I haven't been able to test these wifi modules yet, since i made this change along withthe change to use OMX from krylon's repo.

Also, is logcat the only way to get the bootup logs? or is there any other way one can debug?

btw, I am installing CM10 on sd. Guess this shouldn't be a problem.