yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
a bit about adb logcat

So for all you who don't know about "adb logcat" it's probably time we talked about it.

When android is running, it's generating all kinds of system messages. Ya see, programmers/developers can optionally output status information (or errors or debugging notes) in real-time to a system log, and Android itself sends all kinds of useful information out that way.

But if there's a running log going on at all times, how do you see it?

Well, if you're connected via adb (usb or whatever) try typing adb logcat . The output to your terminal window, which can be interrupted with ^C (control + C), is a real-time look at android's operation.

So let's say you're experiencing a boot loop and want to get an idea of what's going on "under the hood". It can't hurt to peek with adb logcat. Even if it just looks like gobbledygook, you can copy and paste the output (usually the errors will be obvious if you sit down and look-- stuff like "ERROR!!!!!" may appear) to a site like pastebin.com (although make sure that you're not pasting personal information such as local network addresses or anything sensitive, which occasionally will appear in the log). That way, you can show people the problem (via a link to pastebin.com) for further discussion/debugging/etc.

Anyway, from now on-- instead of just saying "Help! I'm bootlooping!", maybe say "Help! I'm bootlooping, and here's a link to the logcat!"

Why is it called "logcat"? Here's my guess. In Unix (and Linux), there's a command called "cat" (short for "concatenate files and print on the standard output" if you can believe it) that is used to view the contents of a file. So cat is kind of like a verb, in this context. You can try cat a-file-name.txt from the Terminal of any unix-like operating system (including Linux and OS X) and it'll spew out the file's contents to you. So "logcat" is I guess "spew out (cat) the contents of the log".

In other NC news, I think the non-working touchscreen on newer nook colors will be fixed with changes pushed today. Unless something is screwed up, that is. In which case it may not build or may not work. Or rabies.

Thanks to insz for patiently sitting with me on irc for hours, since I couldn't test this myself, not having a device with the new touchscreen.

Thanks also to keyodi for pushing some stuff as well today that fixes mounting on Windows and some general cleanup.

(Bonus Command!: If you're using Linux or OS X and want to view a file from the terminal, but don't like how cat filename.txt spews the contents at you nonstop, try using "more filename.txt" instead. I'll leave it to you to figure how it works.)
[Nook Color Android Development] speedfreak007:
How i changing the build.prop manually different from using an app? I want everything smaller, so which density do you think works fine with market? I've tried 140 and that force closes Trebuchet.
[Nook Color Android Development] JP12:
Since removing OneTimeInitializer I get random crashes where I have to manually reboot the device. Does anyone know more about this?
[Nook Color Android Development] anapospastos:
I just build from scratch including the latest commits from github and I can't boot in ics. My NC is into a reboot loop.
[Nook Color Android Development] fattire:
Logcat?

.
[Nook Color Android Development] anapospastos:
I can't take it. When I'm running adb logcat from terminal I don't get anything. I tried several times when NC boots but no light. Is this the right way to take a log during boot?
[Nook Color Android Development] rabshear:
I have this question as well. With CM7 on my NC I was able to make things bigger by editing the build.prop. There isn't a default ro.sf.lcd_density value in the build prop on this ROM. If I add one and set it to the same density as I had in CM7, it causes Trebuchet to crash. Is there any method to make things bigger on the screen for my aging eyes?
[Nook Color Android Development] numus:
Awesome.. Anyone going to work on a buildbot :)
[Nook Color Android Development] rgerrans:
In trying to troubleshoot another issue I noticed in my logcat file that the photo sync was running constantly and verified that when I looked at my sync settings, so you might want to see if you are experiencing the same issue.

-Ron
[Nook Color Android Development] HarleyChick:
I used Samiam's build on my sd card and I didn't have to do any resizing of the partitions or anything else for that matter. And it works wonderfully.
[Nook Color Android Development] rgerrans:
First off, thanks to everyone for all the hard work on this. So far loving CM9 on my Nook. The one key issue I have is that the Wall Street Journal Tablet app (I side loaded it on CM7) won't download new editions. I've attached a link to a logcat where I tried to download but unfortunately my programming skills/android knowledge isn't to the right level to figure out what might be happening (the App is WSJ). Anyone else see what might be causing the issue? It's the only thing keeping me from being able to run CM9 exclusively.

Logcat - http://dl.dropbox.com/u/19282063/logcat2.txt
[Nook Color Android Development] Midnitte:
Dalinger proposed donating to the EFF since in the long run they defend people like them being able to get CM7 on devices like the nook color. =p
[Nook Color Android Development] dalingrin:
Dalinger..thats a new one. =P
[Nook Color Android Development] :
Completely agree that they should spend more time deving than writing tutorials, however without how-to's and tutorials than everyone would have to start from scratch and the entire process would take forever...learning from others whether it be through videos, books, classes or tutorials will always make a better dev.
[Nook Color Android Development] joenathane:
That's only true to a point, if you just follow step by step guides, you're not a developer, you're more akin to something like a script-kiddie. One of the real keys to being an actual developer is being able to figure things out without someone holding your hand, like say when you don't have a proper driver and have to patch your existing one, or backport kernel features...

edit: wanted to add this point - There are quite a few out there that imagine that they are developers because they know how to compile CM, and they end up kanging CM, throwing a horrible skin on it, or some snake oil script and calling it "crappyusernameMod". That lazy approach isn't helpful to the community

/off topic
[Nook Color Android Development] fattire:
I'll try to have the tutorial thing up later tonight. Fwiw i find no better way to learn than to start up a wiki page on nookdevs and document things. Not only do you break down what you're learning into logical sections, you can use it for reference later. Oh and you help thousands of others as you learn together. People who know more than you correct your mistakes so you can learn from them too. A good example-- when i first built cm from source about a year ago, only linux instructions existed. i decided to try on the mac not knowing if it was possible but using the linux instructions as a reference and via trial and error tried different mac equivalents until i finally got it to work. I kept a "log" of all the steps in the wiki, so the results were the mac building instructions. Others who read it refined it and made further changes to keep it up to date. So i learned and maybe others benefited as well... and there have been many times ive gone back to old wiki pages -- essentially using them as my personal notepad-- to find old info...

Point is, i encourage eveeryone to use nookdevs or another wiki (like cm's) to collaborate and refine and collect info....

Oh and this whole post was tapped into nook ics at an Indian restaurant. :-)
[Nook Color Android Development] mgs526:
Wish I was savvy enough to build this. Anyone have a flashable zip?
[Nook Color Android Development] jalexishg:
Awesome job guys ! Feels great to know is almost there, thanks a lot for taking the time to do this for us !! Happy holiday's !!!

From my NS4G oICSv21
[Nook Color Android Development] iDidItAll4theNookie:
Source was dropped in mid-November. Less than a month's time and you guys have so much done already. The progress reports make the waiting easier, and it keeps the excitement alive. :)
[Nook Color Android Development] salsichad2:
Does anyone know what I'm doing wrong?

build/core/base_rules.mk:166: *** device/bn/encore/hwprops: MODULE.TARGET.EXECUTABLES.hwprops already defined by android_device_bn_encore/hwprops. Pare.

Thanks
[Nook Color Android Development] newellj79:
Seriously? I spend most all my free time reading up on this stuff. However, the help of other both here and at irc and step by step tutorials has been priceless. Sorry off topic. On topic, still syncing in home directory instead of system. I'm sttumped. Hopefully back on irc tonight. Maybe attention forth coming guide will help.
[Nook Color Android Development] dgozalie:
wow

well, you guys make me keep return here to see if the xmas comes early... who knows someone will drop the present and let us play ICS...keep it up, guys and i will keep check it couple times a day....

Donny
[Nook Color Android Development] cybertimber2007:
You'd know if there was one. You'd feel a rush of everyone going to one post or topic at the same time.

No released flashable zips yet... likely for good reason (unstable, dragons overhead, aliens and predators fighting on top of you, pikachu sick, etc). The devs know when the right time to release is.
[Nook Color Android Development] Midnitte:
That probably won't stop over people from making builds and releasing a zip though... =p
[Nook Color Android Development] xdp:
I would definitely give this a shot on my Nook if someone did a build. I gave up on my VM for doing CM builds when I heard about the hardware requirements for building ICS.
[Nook Color Android Development] brianf21:
Looks like you have two sources for the encore device. Did you try to integrate fattire's source into cm7 or cm9?
[Nook Color Android Development] fattire:
Yeah, why not...

Fine, fine.

update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip

md5: 85294ad91e2601beb737cf723b9fb9d6

(note this URL is likely to change)

Note: You are advised NOT to try to install this. This update.zip will **overwrite** as in erase whatever data you have on your emmc, so if you are trying this, you are advised to back it up first so you can recover. Install entirely at your own risk, and do a factory wipe first. This software is likely to be terrible and cause problems including permanent data loss, hair loss, and/or the destruction of your property and the death of your pets. You assume all risks involved in your use-- or even attempted use-- of this file. I disclaim any and all responsibility for your decision to try it.

*** Really. This build is buggy. It is a work-in-progress. It is only a snapshot of where things stand right now, and it's possible it'll never go further. ***

If you need assistance, you must rely on each other.

I am also releasing a first pass at a how-to-build walkthrough. It is available here:

walkthru (rough draft)

This doc will be updated and evolve with your input. It is meant to help people feel confident that they can build an operating system from scratch, and hopefully encourage them to participate, learn, and even make contributions.

You may be asking, where is the issue queue? There is no issue queue. You are on your own here.

For sure not working yet:

* sound

* video

* full 2d acceleration (esp on complex web pages)

* usb gadget (ie, mounting your sdcard to your computer)

* screenshots

* build system (to auto-create upgrade.zips)

* rotation is goofy

* bluetooth is pretty much untested (though it's been paired)

* some apps crash or go black

* the "open apps" softbutton doesn't work

* and much much more

These things may/may not be added at some point in the future. You should have no expectations that they will. Anyone who asks for an ETA for something or other gets collectively stoned by the crowd.

I'm sometimes on #nookcolor in freenode.

Thanks to keyodi, unforgiven512, arcee, toastfch, d0nk`, dalingrin, nemith, the rest of the cm team/TD, and anyone else who I've forgotten. We stand on the shoulders of giants.

Again, don't install this. And please don't "rom" this (as in change the font or background) and then ask for donations for your "hard work". This is a preview of a work in progress, not a final product, and it's not meant for people to use day-to-day. Don't be a ****. Thanks.
[Nook Color Android Development] dalingrin:
*Downloads fattire's release and renames it DalingrinMod then takes all credit
[Nook Color Android Development] jschill31:
That there is pretty funny...you just made my night!

Cheers
[Nook Color Android Development] fattire:
Oh yeah???? Well I'm going to change the bootanim on DalingrinMod and call it Nook2Kang and sell it on amazon.com for $35!!!!! :p
[Nook Color Android Development] Midnitte:
So it seems like you need people to test bluetooth then eh? =p

Any chance that will work with SD cards (in the future)?
[Nook Color Android Development] HarleyChick:
Where is your "latest" nightly? When I looked in your index, it shows the same file that I downloaded yesterday.

Nevermind - found it.
[Nook Color Android Development] johnny15:
Looks like the latest nightlys have dropped ~8MB from sneakpeak2 so, you are correct, you shouldn't need to do an partition resizing on an SD card right now (unless you want to drop both the nightly and gapps on at the same time).

Do we have any idea what's new in the latest builds (other than the fix for the NC's with the newer touchscreen)?
[Nook Color Android Development] Dj-Gutz:
If anyone is interested I managed to get NTFS working

use the attached zip to extract fuse.ko ( credits : fattire ) and put it in your sdcard like /sdcard/fuse.ko

than via adb/terminal emulator

insmod /sdcard/fuse.ko

then use a software like Drive Mount

It should work on internal storage too as far as I know , but haven't tested
[Nook Color Android Development] leapinlar:
I run an alternate launcher (ADWex). There is no setting in build.prop that changes the lcd density. But I have the app "lcd density changer". I experimented with it as I want the fonts and icons bigger, not smaller. I tried changing the density to 240 like I have on my Galaxy Tab. The app says the native density is 160 and it will allow me to change to 240. When it does, systemui.apk crashes. That is the app that displays the status bar at the bottom of the screen. And the effect on the screen is not what I would have expected. The icons are smaller, not larger. Ics must use a different mechanism to set up the screen font and icon sizing.

This is one of the things that is keeping me from jumping immediately to ics. I like the Galaxy Tab sizing. Fonts and icons are way too small on ics to suit me.
[Nook Color Android Development] Dj-Gutz:
Need help to investigate USB Audio problem ( which at first I thought was a buffer size issue )

I narrowed it down and the stuttering only happens when the screen is on

when I press the power and set it to sleep all of the artifacts are gone

Screen ON ( stuttering appears )

I/WindowManager( 1149): No lock screen!
D/SurfaceFlinger( 1065): Screen about to return, flinger = 0xf918
E/WifiStateMachine( 1149): set suspend optimizations failed!
E/AudioHardwareALSA( 1068): setParameters INVALID OPERATION

Screen OFF ( back to normal )

I/power ( 1149): *** set_screen_state 0
D/SurfaceFlinger( 1065): About to give-up screen, flinger = 0xf918
D/Sensors ( 1149): sensor activation called: handle=0, enabled=0****************
****************
E/AudioHardwareALSA( 1068): setParameters INVALID OPERATION

E/AudioHardwareALSA( 1068): setParameters INVALID OPERATION

sounds like the problem

how do I investigate further? where can I see what it's trying to set?

these logs obtained via logcat , I see nothing related on cat /proc/kmsg
[Nook Color Android Development] HacDan:
ro.sf.lcd_density=160 is the line in build.prop.

A 240 density will result in the phone layout being used in the operating system. There are no tablets with a DPI of 240 so you won't be able to make them that big.
[Nook Color Android Development] rabshear:
There is no line for that in the build.prop by default. There is in Gingerbread ROMs, but the line is missing in ICS. I built this last night, so I am running the latest. Correct me if I'm wrong, but it just isn't there.
[Nook Color Android Development] HacDan:
ro.sf.lcd_density=160 is what should be set. If you're looking for something different than that and still maintain the tablet UI, you'll need to use a different launcher as Trebuchet doesn't support anything but 160/240 at the moment, from what I cant tell anyway.

You can make the font size larger in the display settings.

160/240 are the only two that I know that work in the market. 240 will net you the phone UI however.

I already explained how to change the density manually. You won't be able to do it on the tablet.
[Nook Color Android Development] bigbob23:
I was still on sneakpeak1 but saw that the update size now fits the boot partition (I don't have a working Windows machine to use Easeus). When I installed the 20110112 nightly I got the reboot loop issue samiam had mentioned.

I installed 20110111 successfully and all looked well at that point. However, after I installed gapps (I tried both versions in samiam's repository) and rebooted, I don't see the icon in the upper right corner to access any apps.

How do I get to the apps?
[Nook Color Android Development] shumash:
Gapps Rename Issue

To install the gapps zip for ics, I had to rename the file from gapps-ics* to gapps-gb*. Any idea why? Do I have the wrong recovery image?
[Nook Color Android Development] webdroidmt:
If you're using verygreen's SD installer, I believe it specifically looks for "gapps-gb-xxx" in the filename to install. The current verygreen version would be 1.3.

Mike T
[Nook Color Android Development] boomn:
verygreen's installer? That's just because his installer is designed to only look for that file name, but nothing else about the installer makes it incompatible with ICS images
[Nook Color Android Development] liam.lah:
How old is the sneakpeak2.zip?

I spent all last night syncing the repos, the compile took hours on my ****ty old computer, and it didn't end up working.

Has anyone got an up to date build they can post?
[Nook Color Android Development] Samiam303:
Yeah, as mentioned above I'm hosting nightly builds. The most recent one may be suffering from the same problem your build was, but the one before it should work fine.
[Nook Color Android Development] webdroidmt:
Hi Sam,

So, for now we should be using the 20120111 zip? Also, which gapps do recommend, the small or v8? Thanks for your work on this, it's appreciated.

Mike T
[Nook Color Android Development] raenye:
Thanks, but sync is off altogether, and moreover WiFi is disabled so there's no network connectivity.
[Nook Color Android Development] Samiam303:
You can try the 20120112 zip if you'd like, but it may cause bootloops -- my nook is dead at the moment so I haven't been able to get a logcat to find out why that's been happening. The 20120111 zip however is fine. As for the gapps -- the V8 contains more apps (such as replacing the calendar and gallery with google versions), but it contains the OneTimeInitializer.apk which has caused problems for many people, so if you flash that one it may need to be removed through adb. The small zip is the same one with a number of apps, including the OneTimeInitializer, removed. It's really up to you which to use.

EDIT: If you do decide to use the small one, let me know if it works alright. I only zipped it up last night so I know it worked for me but I just want to be sure.
[Nook Color Android Development] webdroidmt:
Ok, thanks. If I use the small, I'll give you some feedback on it.

Mike T
[Nook Color Android Development] bigbob23:
I found that navigating on the SD card installation was causing me a lot of issues so I bit the bullet and did an installation of 20120111 and v8 gapps to eMMC using CWR.

The problem I had with accessing apps is now gone :)

I am still installing (automatically) a lot of the apps I had previously, but so far it all looks quite impressive!
[Nook Color Android Development] 12paq:
Hi Sam, thanks for hosting your builds!

Just a suggestion, and if Fattire is cool with it, maybe start a seperate thread for those who are *not compiling their own builds from source? Maybe a preview ICS general discussion thread? Then it would be just devs and code here and preview flashers on the new one?

No big deal to me either way, I'm nobody, just an idea. :)

Thanks again,

12
[Nook Color Android Development] webdroidmt:
I flashed the small gapps and everything seems to be currently working, both my gmail and calendar are synced up. I also d/l a few apps from market and all went well.

I did have to install sneakpeek 1 first and then flash your 20120111 zip to get up and running. Initially, I just tried flashing 20120111 but got bootloops. Does everyone have to install sneak 1 first, or is this just something with SD installs?

I'll try to give you some more feedback tomorrow after the rom runs and settles in. Thanks again.

Mike T
[Nook Color Android Development] racks11479:
12paq,

You're not a nobody! Everyone is somebody to someone else. :p

Off topic I know, but dang your photography is awesome!

-Racks
[Nook Color Android Development] dexx0008:
I also got boot loops attempting to flash 20120111.zip (or 20120112 for that matter) I will take a look tonight. I will try sneakpeek1 or 2 first, then try going to 20120111.zip.
[Nook Color Android Development] webdroidmt:
@dexx0008

Unless someone more knowledgeable than I says otherwise, I would do SP1 and not SP2, then Sam's build. I'm thinking that SP2 and Sam's build are predominantly the same, where SP1 has something that for some reason is different than either of those two???

I may be talking out of my a$$ on this but just a thought.

Mike T
[Nook Color Android Development] eyecrispy:
I tried to get to Samiam303 link in the post above but it's not working. Has this link changed? Can someone point me to an updated link?
[Nook Color Android Development] webdroidmt:
It has been moved here.

http://www.sphsolutions.net/android/

Mike T
[Nook Color Android Development] eyecrispy:
Very cool. Thanks! Are there any gotchas I need to know about? I'm on an older nightly of CM7 and haven't flashed it in awhile.
[Nook Color Android Development] bigbob23:
I flashed today over a very recent Mirage build of CM7 and it all went smoothly (I did a "wipe data/factory reset" and wiped the Dalvik cashe in ClockworkMod recovery before flashing the ICS ROM.

Most of my apps appear to be OK. I couldn't set up Aldiko for DRM content (for library books but was able to do so for the Kindle app).
[Nook Color Android Development] dexx0008:
Mike,

you are right. 2 didn't work. SP1 did, now trying to flash up. must have been one of those times when a nugget of truth slipped out... :)

I need to setup my machine for builds so i can hopefully pick more up and attempt to contribute. I've been benefitting from all these cm7/9 builds for a while. i'm afraid my old macbook core 2 duo 2.8ghz will take a while to build. only good news is work sprung for 8gb ram upgrade for it so that should arrive soon.
[Nook Color Android Development] Samiam303:
I've put all the little pointers I know about in a readme file that's hosted along with the nightlies. Check it out for an explanation of the different extra zips I've got hosted too.

As for the question of boot loops, it's been confirmed that the 20120112 build was just bad -- I'm rebuilding an up to date zip at the moment. However, I've never experienced any boot problems with any of my other zips, but then again I originally flashed a sneakpeek so maybe there's something to that theory? I don't know.
[Nook Color Android Development] iDidItAll4theNookie:
20120112.zip is giving me bootloops on emmc, too. I tried installing fullofbugs1 (installed and booted into it), then 20120112 and it went back to boot looping. I don't even get to the boot animation.