yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] meteorrock:
Keep going guys. I know how hard it is to debug kernels, I am trying to learn along with you guys. Keep working at it, I really appreciate all the work you guys do for us. I know you can get that JB stable for us. :cool:

Here you go guys I wanted to give you this.

Its dangerous to go alone,,,,,,,, you will need this :D
[Nook Color Android Development] joeuser846:
CM10 BSOD - logcat

Here is some debug info for those working on the BSOD.

logcat is here: http://pastebin.com/AFKQyuMv

dmesg is here: http://pastebin.com/QGjweXjs

CM10 ran for about 30 minutes of varied activity, app launches, web browsing. It finally died on the black screen after two attempts to launch Calculator which fail with "Unfortunately, Calculator has stopped."

My gapps is "gapps-jb-20120726-signed.zip"

The build was done today and consisted of:

make clean

repo sync

. build/envsetup.sh

brunch encore

I used this local.manifest:

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

<manifest>

<remote fetch="http://github.com/" name="gh" />

<remove-project name="CyanogenMod/android_hardware_ti_omap3" />

<remove-project name="CyanogenMod/android_hardware_ti_wlan" />

<remove-project name="CyanogenMod/android_frameworks_av" />

<remove-project name="CyanogenMod/android_frameworks_native" />

<project name="fat-tire/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean-2.6.32" />

<project name="keyodi/nook_kernel" path="kernel/bn/encore" remote="gh" revision="jb-kernel" />

<project name="NookieDevs/android_hardware_ti_omap3-compat" path="hardware/ti/omap3" remote="gh" revision="jellybean" />

<project name="NookieDevs/android_frameworks_av" path="frameworks/av" remote ="gh" revision="nc_jb" />

<project name="NookieDevs/android_frameworks_native" path="frameworks/native" remote ="gh" revision="jellybean" />

<project name="NookieDevs/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="gh" revision="jellybean-encore-2.6.32" />

<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />

</manifest>

Can I provide anything else to help?

Thanks.
[Nook Color Android Development] bytte:
My theory a few posts back was that fork was failing, but processes continue. When I have time I will put some none forking debug code in adb server so that we can get some more info back. If someone does that before me that's fine.
[Nook Color Android Development] joeuser846:
Answers to above questions:

1. Calculator does not run on my build - it always ends with "Unfortunately, ..."

2. That link is my whole dmesg captured on the NC with: dmesg>/sdcard/dmesg.txt

3. I should have also noted that the logcat was captured on the NC with : logcat -f /sdcard/logcat.txt

Does capturing on the device rather than USB tethered to ADB matter to the debug info?
[Nook Color Android Development] bytte:
Can you download a file with known contents (and md5) and then check that the hash of the downloaded file is correct. Ideally the file should be a reasonable size (10+ MB).

There was a time when this was failing for me - but it went away when we moved away from the v3 kernel. I assumed it was a wifi problem. I haven't updated recently so I don't know if the issue has resurfaced.
[Nook Color Android Development] steven676:
Sounds like upstream (CyanogenMod) broke the calculator, then. I wouldn't worry about it -- it'll get fixed.

No, not at all -- I believe (but have not verified) that "adb logcat" is equivalent to "adb shell logcat" -- namely, just running logcat on the device and sending the output to the computer.
[Nook Color Android Development] thorin:
Ah! I just realized that I changed my local_manifest.xml to the one that was posted recently and rebuilt, but I forgot to do a repo sync after my make clobber. That explains why I still have a 3.x kernel. Off to try again.

Thanks!
[Nook Color Android Development] eyeballer:
Well keyodi has done some great work (again!) with the 3.0 kernel over the past couple of days and it seems he's solved most of the power related issues. There's still a few bugs.. eg. the 'n' button won't wake from sleep (but hey.. the device does!).

This is the latest manifest to try to build with: http://pastebin.com/5BB07A82

You may need to rm -rf the device/kernel/hardware/ti folders before syncing the manifest to make sure it's gets updated. Also you'll need to do a full rebuild so "make clobber" before you brunch.

Wifi seems to work fine here.. resumes after sleep and i've been able to install large games from the play store.

Please report back.
[Nook Color Android Development] keyodi:
Keep in mind this is still a work in progress and there will most likely be some bugs, which I know you guys/gals will be posting and +1'ing once you find them :p

Overall, the kernel looks good for an alpha release (only time will tell)...Good luck building!
[Nook Color Android Development] bitstra:
Hi keyodi & eyeballer & all other devs here,

thank you for all your work on the repos for CM10 on b&n nook color!

I've compiled CM10 with the actual kernel (synchd on 10-05-2012 (synchd repos with the latest manifest on: http://pastebin.com/5BB07A82)...

so far all works fine. I'm in testing the flashed cm10-05102012...

First bug I've found: seems to be the AC-Adapter-charging problem is back...

When Charging with wall-mount-AC-adapter (1500mA) the battery charging state is shown as CHARGING (USB).

thanx in advance

bitstra

Edit:

test-results:

1- AC charging works as USB-charging for the moment, when connected after boot (when connected before booting it's shown as AC-charging) oops.

- Wifi and sleep/idle works fine with wifi-off when sleep/screenlock

- sound works as it should

- accel.-sensors work fine

2- google now works fine with 'fake gps location' installed and activated

- trebuchet seems to hang sometimes in sleep mode/ with apex launcher all seems to be o.k.

3-CM updater forces close / deactivated it for now via Settings->apps->all->CM updater->deactivate

4-power off / reboot / reboot to recovery - they all work now correct - that's great too

I'm curious if this build can become an alpha release! (Why not?)
[Nook Color Android Development] lekofraggle:
Thank you everyone who helped improve the kernel. It is quite fast and smooth. However, I had a few issues which in my mind keep it from primetime.

-Kernel panics still happen frequently, and when they do, the only way out of them now is to wipe cache and dalvik (or one of the two. I wipe both out of habit). If you do not, it locks up during boot.

-I too have the ac charging issue

-Downloads still failed from the market or caused a kernel panic or both.

-There is a weird bug with the nook and hw acceleration which prevents some images to load. It affects any gallery app other than the standard as well as nook magazines and comics. The pages only show up after you zoom in. While this should not keep the rom off the shelf, I thought I would mention it.

I do not mean to belittle our progress, I just think we have some kinks yet to iron out.

~Leko

P.S. FWIW, my Nook may be of that odd vintage in which it exhibits more issues than some. Too new to be the first gen hardware, but too old to be the second.

P.P.S. I have not had adb working for about a month, so it is difficult for me to help troubleshoot. Sorry.

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

I did a clobber and built today using the new manifest which goes back to the 3. kernel... Once again I am not able to boot into CM10. I am not sure what the problem is but the 3.0 kernel just kills my Nook before it even gets to loading. The past couple of weeks using the 2. kernel have been fantastic since I am able to enjoy some CM10. The long and short of it must be that some Nooks do not like the newer kernel no matter what is done to it. At least with the 2. kernel everyone is able to use the OS. Is it not worth continuing to explore why the 2. kernel gives a black screen from time to time?

Just my opinion for what it is worth

Cheers
[Nook Color Android Development] bitstra:
continuation:

-5 sound becomes crappy and very loud after wakeup from sleep (internal speaker and earphones !)
[Nook Color Android Development] jamesh0317:
I built CM10 for the first time on 09302012 using fattire's quite simple instructions. Was smooth, fast, and everything worked as advertised- no new issues to report.

I just changed the local manifest per a few posts back, clobbered, synced, and brunched. All works just as well, and "about" shows the 3.0.8+ kernel, and version 10-20121006

The only difference is where it used to say "E 0" in the upper left of the Cyanogenboot screen (which I understand means that there were zero boot errors) it now says "emmc 01". I know what emmc is, but don't know why it replaced "e".

Does the "01" means that there was a boot error, and if so is there anything else I can report to help?
[Nook Color Android Development] eyeballer:
E on the old cyanoboot always stood for EMMC (meaning you're booting from EMMC not sdcard) - obviously not everyone understood that so now it's clearer :).

The number is a bootcount not error. So 01 means 1 boot attempt, perfectly normal afaik.
[Nook Color Android Development] steven676:
Not many people are using Mac OS X to build at the moment -- has anyone gotten this to work with OS X lately? Assuming your BoardConfig.mk is correct (compare https://github.com/fat-tire/android_device_bn_encore/blob/jellybean/BoardConfig.mk), I'd say it looks like the Mac OS X prebuilt toolchain is broken.
[Nook Color Android Development] hushpup131:
appreciation

Thanks for the E01 clarification
[Nook Color Android Development] alienbiker99:
i am also getting the build error on osx mtn. lion. it builds beyond the first error that thorin posted but still fails.

http://pastebin.com/zMWZS2vr
[Nook Color Android Development] narta:
Succesfully compiled and deployed CM10 but wifi is wacky (I am at arms length from my router and suddenly out of range)

I will continue to test the build and report anything else

Router: Thomson TG585 v8, TKIP+AES encryption
[Nook Color Android Development] bitstra:
I think, every one can see the 'out of range' message for his wifi-network entry. This is not a problem of our routers! It takes a longer time to let you connect. But when connected then it stays connected...

So you have to be patient at the first try to connect...

(May be, we can tweak this by wifi settings in build.prop - will try that later)

regards

bitstra
[Nook Color Android Development] bitstra:
BTW:

I have installed 'Wakelock' from playstore and set _Partial_Wakelock

to prevent problems after very, very long deep sleep...

Battery time in this case is about 24 hours...

regards

bitstra
[Nook Color Android Development] krylon360:
Wakelock isnt needed.
[Nook Color Android Development] eyeballer:
For those on OSX the workaround for now is to force using the older toolchain to build the kernel. You need to add this line to your boardconfig alongside the other kernel related defines: TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3

(You can see where it was removed from here: https://github.com/fat-tire/android_device_bn_encore/commit/be794b3e2cd7d6265ff4e567cb9afbfafb7a2d66 )

Of course this is a "hack" since it builds fine on linux as is- the real solution should be for someone with OSX to go look and see why gcc 4.6 causes the kernel to fail. Anyone done any research on it?
[Nook Color Android Development] crnkoj:
Which toolchain version is being used otherwise?
[Nook Color Android Development] HacDan:
If you don't have the time to set up a build environment, you don't have the time to test the builds. This 'excuse' is getting quite old.
[Nook Color Android Development] sellers86:
The default is GCC 4.6 I believe.
[Nook Color Android Development] alienbiker99:
I added the line to my board config but now i am getting an error when building wifi. http://pastebin.com/isTbC0hA

something is wrong with the osx toolchain?
[Nook Color Android Development] HacDan:
OS X Fixes, maybe?

Well, you can revert the BoardConfig change and give this a try if you're feeling adventurous.

Move on over in to kernel/bn/encore/arch/arm/mach-omap2/ and replace the Makefile in there, with this one: http://pastebin.com/zw6cGHHV

Please report back if it works or not if you or someone else gives it a shot.

Note: This is for OS X only, to help with the build errors.
[Nook Color Android Development] xdp:
I disagree, as I know setting up a VM/Ubuntu/SDK/build, and figuring out everything that goes wrong, will consume an entire night or several (I'm not just guessing, I went through this with CM7), but a pre-compiled build could be "tested" (played with) in just the few minutes a day I have to spare to play with the device.

But anyway, are these still the most up-to-date instructions, even for CM10 builds?
[Nook Color Android Development] DizzyDen:
try.. CM10 for NookColor Build Instructions
[Nook Color Android Development] narta:
Another option is using a VM and deploying andbot build environment. Just keep the local_manifest.xml up to date with the ones provided here and building is a piece of cake.
[Nook Color Android Development] krylon360:
well since you already went through it with cm7...then it's either already done, or you already know how to do it. :)

or just wait for us to post it.

these are the cm10 build instructions. Though, the local_manifest has changed.

https://docs.google.com/document/d/194wk4Tx0NyR7pIpFtBw76dltF7Igj0Uaquha5q1ZoDc/edit?pli=1
[Nook Color Android Development] thorin:
Additionally, the new local_manifest already includes the proprietary files, so no need to pull those.
[Nook Color Android Development] HacDan:
And I disagree with your interchange of testing and playing. People are building now to test and confirm things are working/not working. This requires feedback, not just 'a few minutes a day'. Your view on testing is a bit flawed, sir.
[Nook Color Android Development] xdp:
I'm in software development myself, I wasn't trying to equate the two terms, I was just pointing out that I only wanted to try it out of curiosity, not seriously test, which is why I felt that was something I could do in just a few minutes a day. But it's okay, I understand that the devs would rather be happier with the state of it before letting more folks try it out. I appreciate the fact that you value quality feedback.

Thanks guys for the updated links. I will definitely give it a try if a free Saturday opens up. I did CM7 builds on a different computer two years ago, and I remember having a number of headaches, so I figured I would practically be starting from scratch again now.

I'm interested in learning how the local_manifest and andbot makes things easier, will have to try to read up on that.
[Nook Color Android Development] alienbiker99:
I reverted the change and switched the make files. It went past the wifi building error but stopped and didnt give me a flashable zip. http://pastebin.com/WDzpxt72 Thanks for help guys I've been trying to build this in the background while I do work.
[Nook Color Android Development] lekofraggle:
Alienbiker,

I have an old santa rosa macbook pro and gave up on building in osx. What I did that worked well was go the vm route. It took a bit to dial in my setup, but now it builds well.

I run ubuntu 12.04 on fusion 4 (I already had vmware installed and virtualbox did not want to work without me uninstalling).

Parallels would build but networking and sync errors were a nightmare.

Good luck.

~Leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] Divine_Madcat:
Back on topic folks, please..

If you want CM10 for the nook, right now, you must build it. That is what our maintainers have requested, and I have no problem upholding that request. If you do not wish to setup a build environment, that is fine, but do not argue about it otherwise...
[Nook Color Android Development] HacDan:
Which kernel are you building? And I think you missed the error entirely with the pastebin. Gonna need the last 100 lines or so considering so much is built at once.
[Nook Color Android Development] thorin:
I noticed that in the most recent build, under performance -> processor the max cpu frequency is 1000MHz, but previous builds had it at 1200. Was this reduced on purpose, and what do I need to change in order to raise it back?

Also, has anyone else tried the true tablet UI patch (xdaforums.com/showthread.php?t=1780970)? It seems to work pretty nicely.
[Nook Color Android Development] jackgibbs:
has the random black screen been fixed? my girlfriend won't let me put this back on her nook until that goes away.
[Nook Color Android Development] mateorod:
I don't know if you are just asking about the tabletUI code edits, or an actual package, but you can add tabletUI to just about any ROM with the auto-patcher in my sig. Exact same code edits, i put the package together with barmullio. Unless the recent upgrade to 4.1.2 broke the patches, which is unlikely given their size, it will almost certainly work on the roms for this device.

Oh, and the max cpu was lowered in the kernel code to keep overclocking from being a factor in bug reports. You can expect it to return at some point in the future. If you really want it back, you can look at the github or run git log and checkout the previous commit. Or just write in those changes if git isn't your thing.

But you lose your right to report kernel bugs...
[Nook Color Android Development] alienbiker99:
I am building the default kernel. Using the latest local manifest that was posted a few pages back, haven't change anything.

here's a longer paste hopefully I copied the error this time http://pastebin.com/24cCTXft . I don't really have a reference on what to for or how to go about changing it if I find an error. I know i can set up a linux distro and have the source compiling in a small amount of time, but that's the easy way out now, I feel like I can get it building as there are many threads here on xda about building at least cm9 on osx. Thanks again.
[Nook Color Android Development] fattire:
make[1]: /sbin/modprobe: Command not found

You're running this on a mac, right? I don't know why it would be using modprobe, which is a command for adding modules to the linux kernel.

Let's see...

hardware/ti/wlan/mac80211/compat_wl12xx/Android.mk includes:

MODPROBE := /sbin/modprobe

and then it actually uses it... very odd. It shouldn't be building anything for x86 systems... this doesn't appear to be very smart about possibly running in OS X.

Quick workaround is to not have it build the wifi modules and use prebuilt ones. Try commenting out:

# TARGET_KERNEL_MODULES := WIFI_MODULES

and maybe

TARGET_MODULES_SOURCE := "hardware/ti/wlan/mac80211/compat_wl12xx"

in device/bn/encore/BoardConfig.mk

There is probably a smarter solution, but this is a quick one that hopefully keeps you building, although it may get stuck if it expects to find the modules it thinks you built... Regardless, you'll need to grab the modules manually for now.

We probably will want to figure out what to do if this is being built in darwin..
[Nook Color Android Development] narta:
I get errors syncing http://pastebin.com/HHD24NSM
[Nook Color Android Development] unknown_world:
all sync errors are your pc/network related or github.com related not a development bug. Let's keep this thread for devs to talk and

users to report bugs.

Now the big bug is charging code. With the latest code commit nook is not at all recognizing AC Charger not matter how you connect it always report it as a USB Charging.
[Nook Color Android Development] narta:
If I can't build how can I test and report? :mad:
[Nook Color Android Development] cybertimber2007:
What? This thread has been about three things: CM9, CM10, and building them yourself until public builds are made. If people weren't reporting building issues, we wouldn't know it was broken on OS X! So I'm fairly sure it's ok to ask for help if you are having trouble with building. Correct me if I'm wrong (@fattire, @eyeballer, @krylon360 @divine_madcat)
[Nook Color Android Development] krylon360:
Re-init. repo init -u git://github.com/CyanogenMod/android.git -b jellybean

then type reposync

(no space between repo and sync)

Wrong. He's trying to sync so he can build. Build == dev == what we asked for.

Part 2. It's still charges right? so not a "big bug"

You are correct
[Nook Color Android Development] eyeballer:
Updated manifest for those building at home. We're back using the CM frameworks/av, /native, /omap and /wlan now that our device configs are more inline with upstream CM.

http://pastebin.com/vuXbMz6D
[Nook Color Android Development] eyeballer:
It detects AC charger just fine if you plug it in when it's 1) off or, 2) on and awake. But it won't detect AC if it's sleeping and you plug in. So not too difficult to workaround right now - just hit power to wake then plug in.
[Nook Color Android Development] unknown_world:
Go it thankyou.

One more thing

libOMX.TI.720P.Decoder.so you added is not a lib file it's a html code.

libOMX.TI.720P.Decoder.so: HTML document, UTF-8 Unicode text, with very long lines
[Nook Color Android Development] eyeballer:
Well that's fun.. should be fixed now :)
[Nook Color Android Development] alienbiker99:
I kept the mach2 makefile change and added these to my BoardConfig.mk. I have a successful build on osx! just installed the zip on my nook and it seems that the wifi modules didnt get added as I cant turn on wifi. Thanks for the help guys. Not sure whats exactly wrong with the toolchain normally if anyone has an ideas im willing to try them our to see it if works.
[Nook Color Android Development] fattire:
Yup. You just need to get the wifi modules and you'll be good to go :) Congrats on getting it built on OS X... I don't think anyone else has recently...

The issue with OS X and the modules is that the Makefile is assuming you're using Linux... I don't think they were thinking this would be built on-the-fly as part of an android build :D For the longest time encore just used pre-built modules. It was a relatively recent decision to make it part of the build, as more source is always better than binaries... hence the issue. You can always modify your build environment to use the prebuilts-- or even better maybe there's a way to either fix the makefile or get it to auto-detect if the build is on darwin, and if so, just use the prebuilts :)

eyeballer, do you think the prebuilt should be updated to the device for those who need it?
[Nook Color Android Development] anapospastos:
Why I can't get the proprietary files from eyeballer's github?

repo sync -j4
Fetching projects: 100% (316/316), done.
fatal: reference is not a tree: a2f746c1f7a2c99fb770671a075a2f9b266cbc1f

vendor/bn/: leaving ics; does not track upstream
error: vendor/bn/: eyeballer/proprietary_vendor_bn checkout a2f746c1f7a2c99fb770671a075a2f9b266cbc1f

edit: nevermind, solved it by deleting the old proprietary files
[Nook Color Android Development] bitstra:
THANX!

synched today (10/12/2012) with this local manifest and got an unofficial CM 10 (JB 4.1.2 build JZ054K) - GREAT!

All works fine after flashing. AC-Charging behaves like eyeballer wrote...

If screen lock comes after time without activity, I get a blacksreen after deep sleep when I try to switch on. If switch off to screen lock with hardware button all seems to be o.k. (no blackscreen after sleep).

...but though so far the best build I've compiled (as allways here with ANDBOT on VM ubuntu system) in the last weeks.

regards

bitstra
[Nook Color Android Development] unknown_world:
Adding "USE_OPENGL_RENDERER := true" to BoardConfig.mk also gets you HWA Rendering
[Nook Color Android Development] bitstra:
AH! thanx, will give a try that tomorrow...
[Nook Color Android Development] alienbiker99:
awesome. I un # the lines below "# Wifi - we're building ourselves" in device/bn/encore/device.mk is this how i would manually use the modules?
[Nook Color Android Development] fattire:
Anyone building via OS X may also be interested in this thread on the official AOSP building group at google.
[Nook Color Android Development] jamesh0317:
~/android/system/device/bn/encore/BoardConfig.mk?