yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] jackgibbs:
...should I still be using fattire's local_manifest found here: http://pastebin.com/FrFJmVtJ ?
[Nook Color Android Development] crnkoj:
got this one https://paste.tinyw.in/index.php/view/50199795 from eyeballer (i believe) a few days ago. it compiles and works (its the .32 version though)
[Nook Color Android Development] krylon360:
Thats WAY old. Not sure where that one came from.

^^ Thats the one we are all running right now.
[Nook Color Android Development] jackgibbs:
haha. I knew it was old, but it was still the one connected to fat-tire's stepthrough in OP...I've sort've been keeping up with the necessary changes by running into a million errors, then using those errors to search the 3000 posts here for the solution. one step closer now, thanks!
[Nook Color Android Development] steven676:
Very, very, very likely that this is a corrupt filesystem -- this sounds exactly like the standard behavior of an ext* filesystem with errors=remount-ro. (Check your dmesg output -- you should see the filesystem errors noted in the log.) Back up your data (Titanium Backup, ClockworkMod or equivalent recovery) and reformat the card -- e2fsck is the best filesystem checker and repairer I've ever seen (and I've seen a lot of them), but even it doesn't work miracles.

If you keep getting the error even after having reformatted your card, you may need to consider the possibility that your SD card is failing.
[Nook Color Android Development] mateorod:
I just had this exact same thing happen with grouper. Now, that has a virtual sdcard, but still. It was the damndest thing.

I had pulled an entire sdcard partition from one device to my linux box and then pushed it wholesale onto a replacement device. Any folder that was overwritten (Download, Android etc.) became was read and execute only. That mean that downloads failed due to "storage full", no save state on games, all that stuff. su chmod did not affect those folders, rm in adb shell, adb mount and remount, nothing.

Since it is a Nexus, I just reflashed the factory image and all was well. I knew that would be a working solution, but was holding out hope that there would be an easier way.

So in the nook's case, like steven said, I would try a sdcard format. If it happens again, I bet he's right and your sdcard has just turned the corner.
[Nook Color Android Development] meteorrock:
Why are you running a fsck on a mounted filesystem? I sure hope you guys know what you are doing. I was told never to do that. http://serverfault.com/questions/29889/why-cant-you-fsck-a-mounted-partition

Check this thread here on using F3 guys. Its the linux version of H2testW. That is a safer option on checking those SD cards. http://oss.digirati.com.br/f3/
[Nook Color Android Development] crnkoj:
hmm so i have built the .32 version with the local_manifest.xml posted a few posts back and keep getting weird black screens randomly (never on cpu/gpu intensive tasks) and i get random lock ups without black screen sometimes when using tapatalk (for instance when i go to the pm tab of it). one more thing it seems with time from a reboot it keeps getting slower (as if there would be some sort of memory leak or such). Any ideas?
[Nook Color Android Development] eyeballer:
Known issues...
[Nook Color Android Development] cybertimber2007:
Thanks for the suggestions on the SD card everyone. Since others had reported similar problems (all apps suddently erroring until reboot) I wasn't sure if it was a 09/04 issue, but I'm going to try a different SD card and see if that any effect. I was planning to try that, but confirmations are nice.

Two things though:

/data doesn't have the errors=remount,ro option as far as I could see. I can check dmsg though. It seems most likely.

And metreorrok I didn't fsck on a mounted parition :)
[Nook Color Android Development] BobbyBest:
It seems like the LG Optimus Black (P970) has made some major improvements in their CM10 since it got is his first official CM10 nightly.

Is there anything SoC-related we could take from it? I guess from a YouTube clip and the fact that they released official builds, that they got the whole HA/HC thing working.
[Nook Color Android Development] meteorrock:
lol :) I was thinking you guys didn't, heheeee. Had to make sure though. ;)
[Nook Color Android Development] crnkoj:
can i do something to help diagnosing, testing, fixing these issues? ie logcats etc (sadly i dont have mad programming skills =/ )
[Nook Color Android Development] jschill31:
Hello all,

Well I am pleased to say that after a couple of months the current build allows me to get past boot-loops and into CM10. I am beyond excited, it has been since July 30th since the Fattire repo booted for me. I have tried numerous repos and builds since but this has always been the smoothest. Now that I am back in the game I must say this is pretty much ready guys.... The known black screen issues are a bummer but the positives way out way the negatives at this point. I also see that WiFi is surviving and I feel much stronger range than before. Is it time to give everyone a taste?

Cheers
[Nook Color Android Development] lekofraggle:
Hey all, I have been away a while and tried looking back but did not find an answer. Are we abandoning the 3.x kernel for a bit? I have continued to use it as a daily and with wake lock it tends to work well. However, I am excited to try the .32 kernel to see if I can get USB host working (I had trouble compiling the 3.x kernel separately and thus could not enable features).

To the poster above, yes it is close to ready, but we are not there yet. The lead devs will let us know when.

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] bytte:
The WiFi corruption I was suffering last month is now fixed.

I still don't have adb. I must be missing something. Build shows cm_encore,userdebug,release and adb is enabled in settings. Is there anything else that is needed? adb works OK with CM7.1.

When people talk about black screen issues, do they mean that the screen suddenly blanks and requires a reboot? I'm getting that, also sometimes it boot-loops (stays in the animation), while other times the animation completes in under 50 sec. Is it possible to get progress displayed, or is that the job of adb - if only it would cooperate?

Sent from my NookColor running CM10
[Nook Color Android Development] cybertimber2007:
CM9 SD card issues

SD card update: I changed cards and re-setup CM9 and things are ok so far. I've only been testing for ~12 hours though.

That said I'm worried that I'm going to corrupt the /data partion all over again because it keeps hard freezing, requiring a reset. What do I need to capture after a hard freeze? dmsg and kmsg?
[Nook Color Android Development] bytte:
Capture the output from dmesg.

Then power off, put the card in your computer and run fsck -n -f and capture the output and post it to pastebin if it says anything about errors. Adding -v may produce more info, but try without it first.

Sent from my Nook Color running CM10
[Nook Color Android Development] meteorrock:
Come check my thread down in cyanogenMod to get started. I tried to set up a guide for new developers and superusers on trying to help the developers up here as simply as possible. Tons of outside links and books to check over so make sure you have some time and commitment to get started. :) Here is the link. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
[Nook Color Android Development] tambourineman86:
Running logcat from adb would show you the progress, so yeah, I think adb is required.
[Nook Color Android Development] joeuser846:
CM10 Encore - ready?

IMHO, no. The blank screen hang happens way too often to release this into the wild just yet. My NC usually don't survive for more than ten minutes, often less. Is my experience unusual?

I'd prefer the devs stay focused on stability rather than slogging through dozens of "I got a blank screen hang" messages.
[Nook Color Android Development] krylon360:
finally got some free time coming up again, so I'll be looking into what is causing the blackscreen. From reports, it's only when loading certain apps...is this correct?

I've got some coding changes to do in the OGL loader, so hopefully that fixes it.
[Nook Color Android Development] cybertimber2007:
Not sure if this is helpful, but doesn't the encore use OMAP3?

https://plus.google.com/+CyanogenMod/posts/VQnMza8rVBK
[Nook Color Android Development] bytte:
Play store install ranks high amongst my failures.

Sent from my Nook Color running CM10
[Nook Color Android Development] jschill31:
Hello,

+1 on the Playstore also it happens at random when transitioning (starting or closing) apps as well as settings. It does not matter which launcher you are using. I have tried stock, Apex and Nova they all seem to do it. I have also played with different combinations of clock speeds as well as other settings. Nothing seems to affect it, always random with the exception that it always happens when the screen is changing from one image to a new one.

Cheers
[Nook Color Android Development] crnkoj:
For me it mostly seems to happen totally randomly. Sometimes it's when opening apps, sometimes when I'm in an app (like tapatalk) and it never happened to me at least until now in gpu intensive apps (ie games). I however saw a few times a hard lockup with the last picture on the screen while trying to access the pm tab in tapatalk (no blackscreen).
[Nook Color Android Development] cybertimber2007:
Crosspost - captured dmesg & last_kmsg after a hard freeze.

http://xdaforums.com/showpost.php?p=31981665&postcount=1115
[Nook Color Android Development] lekofraggle:
I built using the .32 kernel and here are my thoughts.

With wakelock I have not got a single black screen.

In addition, after three days of minimal use and no charging I have 67 percent battery charge

There was a bit of lag until I changed three things (at once, I am sure it was only one)

Ksm enabled

Force gpu

Purge assets.

Since doing that, the .32 is stable and reliable.

In addition, I have not gotten a single broken download or kernel panic from the market or in general.

Thanks all, this rocks.

Note, I am using the manifest posted a few pages back pointing to the .32 kernel.

The 3.x kernel is still faster, but this is amazing.

~Leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] bodi524:
How do you do the wake lock to prevent the black screen?
[Nook Color Android Development] lekofraggle:
Search for wakelock in the market. It is an app. Once installed, create a partial wake lock. You need to allow the notification icon or else the os will kill it. I also enable start at login which is under settings.

If you are on the 3.x kernel, this is a must.

~leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] lekofraggle:
I disabled ksm after repeated kernel panics and it seems currently smooth and stable.

I have an older nook, but it may be one of the 1.5 generation that a few people have talked about.

~Leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] bytte:
Power Management

A caution if you are installing CM10 to EMMC.

I believe there may be an issue with the new bootloader when dealing with a fully discharged battery. You risk not being able to recover!

Recommend that you have a CM7.1 bootable (ie one that has been fully installed) SD card available - just in case. Read on and I'll describe what happened.

The battery fully discharged overnight (left wifi adb running - not on charge). In the morning it was dead. Didn't respond to pressing the n button. Not certain that I long pressed the power button.

Applied power, stock lead/charger - light stayed Green, (no current drawn), not charging. Left it an hour - still not charging.

Replaced CM10 SDCard with CM7.1 SDcard.

Connected power and long pressed the power button. Charge light went yellow, charge rate went to 13 watts, charging graphic on the screen.

After less than a minute (while still displaying the charging graphic), disconnected the power, changed back to CM10 and reconnected power. It went straight into the bootloader, rather than charging.

Powered off, reverted to CM7.1, left to charge.

Concern.

I believe charging is controlled ONLY by software (bootloader / kernel). The bootloader should check early whether it needs to charge before it tries to boot. If there is not enough power in the battery to boot, it probably won't make it through the boot to the normal kernel charging code.

There appears to be a distinct possibility of effectively bricking your Nook if you don't have a 'charging aware' bootloader available.

(I'm also surprised that the power management doesn't shutdown when the battery is dangerously low. Is something else broken?)
[Nook Color Android Development] nemith:
Since the nook will look for a bootloader from the SD card there is NO CHANCE of bricking your nook. Although this is a serious bug, no need to dramatize it.

You are correct the charging mode is done via the bootloader (uboot) so it seems there may be some logic missing to go into charge mode. It is also possible that it took a while for the batter to get enough charge to attempt to try the bootloader and go into charge mode. The LED on the cable is controlled from uboot as well.

Power from charger will allow the Nook to search for a bootloader and if there is one that will charge then it will charge. You can ALWAYS pop in a SDcard with an older bootloader. IT can CM 7, a recovery rom, or one with nothing more than the stock bootloader on it. Bricking isn't possible.

I do have some questions to help out with troubleshooting:

1. The bootloader you have with CM7.1 on the SDCard. Does it have a menu? or just the CM logo?

2. How do you know PM didn't work? Batteries can still drain even though there is no load. Go charge your nook, throw it in a drawer for a month and tell me if it works (mine doesn't)

I happen to have a dead NookColor in my drawer. I'll see if I can bug our resident bootloader guy: fattire for some testing
[Nook Color Android Development] fattire:
Well no changes were made to the charging code at all. And if I'm not mistaken, the battery will charge even if u-boot is wiped completely-- it's a hardware thing, I think.

The charging code in the bootloader basically makes sure that you have adequate power (15% or so) before it starts up, and if not will display a graphic telling you to plug in. And here's why: depending on what the last thing you were doing was when you ran out of juice, there may be an instruction sitting there saying "the next time the Nook boots, flash this .zip file". In the stock firmware, it might be doing an system update, or it could have detected corruption (say, by having too many unsuccessful boots in a row) and is doing a full re-install of the system software. If you're using cyanogenmod or another ROM, you may have left an order to clockworkmod or TWRP2 recovery to reboot and install the latest version of your firmware.

Either way, it would be really bad if you started your boot with such a "reflash" instruction, then it started flashing and ran out of power halfway through, leaving whatever it was flashing in a partially-done, inconsistent state.

U-boot/cyanoboot therefore does a check to see how much battery power you have when you start, and if it's not sufficient, it shows you a graphic and then makes you wait until you've got about enough that your emergency flash, if you have one, can go through. When you have enough power, it starts up. Incidentally, the code for the battery logic I'm describing is here starting around line 521. Even if you're not a programmer or anything you can scan through it, read the comments, and maybe get an idea of what's happening.

If you don't have enough power even to load u-boot, like if your battery is dead-dead, it should charge (orange light on the usb) until u-boot is able to load.
[Nook Color Android Development] freonchill:
sorry if this is a little "off topic", but it appears that TI is no longer supporting the omap3 processor

news release

http://www.reuters.com/article/2012/09/25/texasinstruments-wireless-idUSL1E8KP5FN20120925?irpc=932

i wonder if this means that they will no longer release any code or if they will give us a complete code dump.

though i do find it ironic that this comes so quickly after amazon releases their newest kindle fires with an omap processor
[Nook Color Android Development] bytte:
I have added the word 'effectively' to my caution so it now reads:

There appears to be a distinct possibility of effectively bricking your Nook if you don't have a 'charging aware' bootloader available.

I stand by that statement. That is certainly how it felt!

I don't disagree with anything fattire said about the design, except I don't think charging is a hardware thing (well it is, but it is controlled by software rather than firmware). Regarding the description of the code, that was my understanding and expectation, though I didn't know the exact values etc. Unfortunately, it just didn't happen that way on the day (bug).

My CM7.1 loaded does not have a menu AFAIAA.

Could someone point me to the source code for the original to compare against the new (which I really like).

Let me stress the main points of my observation:

The NC was not doing anything unusual when it died other than perhaps running WiFi with an open TCP connection and whatever Wifi adb (downloaded app - the one one with red / green bugs - I'll dig out the name when I have more time) .

With the CM10 SDcard:

The light remained green for an hour.

There was no charging current flowing into the NC (the digital power meter monitoring the supply to the transformer supplying the NC charger remained static at 2 watts - the value it shows when the NC is disconnected).

After CM7.1 had given it a small boost:

The CM10 bootloader went into menu / booting mode until I forced it to power-off.

At no time did I see the charging graphic from the CM10 bootloader.

With the CM7.1 SDcard:

The LED went amber almost immediately.

I did see the charging graphic (both times)

The power meter showed 13 watts.

We will get to the bottom of this - I'm not complaining - just trying to inform.
[Nook Color Android Development] cybertimber2007:
I'm not sure if they would drop software support so quickly. They did just help the CM team with OMAP3 (a link I posted a couple of days ago)
[Nook Color Android Development] bytte:
What is the config and / or make command line that you are using when building for the NC?

Thanks
[Nook Color Android Development] fattire:
For Cyanoboot? it's something like this:

$ make ARCH=arm CROSS_COMPILE=/home/fattire/Development/arm-2010q1/bin/arm-none-linux-gnueabi- omap3621_evt1a_defconfig

$ make ARCH=arm CROSS_COMPILE=/home/fattire/Development/arm-2010q1/bin/arm-none-linux-gnueabi-

the defconfig is from memory, but I think it's that.. just type "omap3621_ev" and hit the tab button and I think it'll autocomplete if that's not it.

also make sure CROSS_COMPILE points to wherever your cross compiler is, obviously :)
[Nook Color Android Development] bytte:
Bilding U-boot.bin

I download the souce code, and the current version of Code Sourcery_G++Lite (which is what I assumed you are using), issued the above commands, generated a binary

-rwxr-xr-x 1 root root 341964 Sep 30 00:13 u-boot.bin

-rwxr-xr-x 1 root root 341712 Sep 23 15:28 u-boot-orig.bin

but it doesn't boot. Nothing to see on the screen. I believe it was doing something, as I had to force it to power off before I could boot with a different SD card.

Any ideas?

Where do the printfs goto?

Thanks
[Nook Color Android Development] keyodi:
try using: make ARCH=arm CROSS_COMPILE=~/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

*path to your jb source
[Nook Color Android Development] bytte:
Building u-boot.bin

I started out using my 32-bit Linaro build chain but that failed at the final link (ld) stage. Downloading the 12-09 Linaro didn't help. The errors were to do with globals.

..../arm-eabi-ld: error: fs/ext2/libext2fs.a(ext2fs.o): unsupported reloc 1 against global symbol malloc (and lots of other symbols)

I didn't get any errors from the Sourcery build and the size looked reasonable.

The thought crossed my mind that I had downloaded the tarball of the source rather than doing the proper git stuff - would that make a difference - there was only the master branch (I'm a git novice).
[Nook Color Android Development] mateorod:
You are building the very-green repo U-boot, right? That has more branches than just master, although master branch has the latest commits. Try this walk-through, it for sure works. Just point the make commands at your sdk.

To get the source through git, install git on your machine. Then enter

git clone https://github.com/verygreen/u-boot-encore

In your directory of choice. Then you can edit locally all you want. git reset --hard will,restore it to the original state if your edits won't compile.
[Nook Color Android Development] bytte:
Sourcery 2009q1 compiles u-boot.bin

No - I am compiling the new Cyanoboot - see earlier discussion.

However, the link helped in that it gave me a link to the arm-2009q1-203-arm-none-linux-gnueabi tool chain (https://sourcery.mentor.com/GNUToolchain/release858?lite=arm) that works with our NC whereas the current release doesn't - I have no idea what is wrong.

(The current release compiles Cyanoboot but it doesn't run correctly - everything is fine with the 2009-q1 - however, it did require me to have an Xserver running before it would install)

Thanks

BLACK SCREEN

This may help in diagnosis.

I had wifi adb running when I was hit by a BSOD.

NC still answered pings and the established TCP connection to 5555 continued to work - so the running program was fine.

However, new adb commands failed which sounds like fork was failing:

Here is Wireshark output:

00000000 4f 50 45 4e 4d 00 00 00 00 00 00 00 07 00 00 00 OPENM... ........

00000010 52 02 00 00 b0 af ba b1 73 68 65 6c 6c 3a 00 R....... shell:.

00000000 4f 4b 41 59 0f 00 00 00 4d 00 00 00 00 00 00 00 OKAY.... M.......

00000010 00 00 00 00 b0 b4 be a6 ........

00000018 43 4c 53 45 00 00 00 00 4d 00 00 00 00 00 00 00 CLSE.... M.......

00000028 00 00 00 00 bc b3 ac ba​

........

0000001F 43 4c 53 45 00 00 00 00 0f 00 00 00 00 00 00 00 CLSE.... ........

0000002F 00 00 00 00 bc b3 ac ba ........

00000037 4f 50 45 4e 4f 00 00 00 00 00 00 00 2f 00 00 00 OPENO... ..../...

00000047 1f 0f 00 00 b0 af ba b1 73 68 65 6c 6c 3a 65 78 ........ shell:ex

00000057 70 6f 72 74 20 41 4e 44 52 4f 49 44 5f 4c 4f 47 port AND ROID_LOG

00000067 5f 54 41 47 53 3d 22 22 20 3b 20 65 78 65 63 20 _TAGS="" ; exec

00000077 6c 6f 67 63 61 74 00 logcat.

00000030 4f 4b 41 59 10 00 00 00 4f 00 00 00 00 00 00 00 OKAY.... O.......

00000040 00 00 00 00 b0 b4 be a6 ........

00000048 43 4c 53 45 00 00 00 00 4f 00 00 00 00 00 00 00 CLSE.... O.......

00000058 00 00 00 00 bc b3 ac ba​

........

0000007E 43 4c 53 45 00 00 00 00 10 00 00 00 00 00 00 00 CLSE.... ........

0000008E 00 00 00 00 bc b3 ac ba ........
[Nook Color Android Development] mateorod:
Just because i don't use the same words you do doesn't mean I am not paying attention. I am not spending my time just to flap my gums. Those repos are the same.

My point remains the same. You don't need to try all this tool-chain shenanigans. You have a tool chain in your build system that is more than capable of building Cyanoboot. This walk-thru is 100% applicable and accurate, with or without Code Sourcery.
[Nook Color Android Development] bytte:
Redacted
[Nook Color Android Development] mateorod:
I have built Cyanoboot separately,from source, over 200 times. But you go ahead and do it your way. I shouldn't have bothered.
[Nook Color Android Development] Divine_Madcat:
Both of you, knock it off. Lets keep this dev thread on track, and without fighting.. sheesh.