yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] dalingrin:
I believe, there is an app or some account sync that is causing your problems.

What is your wifi sleep policy? Never, is more likely to cause problems.

Are you signed into Latitude? If so, sign out.

If you wind up switching up builds and such you should really try to narrow down the app that is causing this.

After you reboot, let the system boot up completely then put it to sleep. Wait 15 seconds and grab the output of:

adb logcat -d > log.txt

adb shell dmesg > dmesg.txt

I would not bother switching to an old build. You should just update once my commits go through.
[Nook Color Android Development] paleh0rse:
Thanks for the quick reply, and for all you do.

Let's see...

-- wifi still set to off when screen off

-- don't use Latitude

-- account sync could be problem with one of the apps. I use Craigslist, gReader, and Friendcaster too, so any one of those could be screwing me up.

One correction: I'm now showing 40sec of deep sleep during last 20 min with screen off; and, for the first time all night, it didnt SOD! I guess those are good signs. I didn't make any changes, so I'm not sure why it's behaving right now. Perhaps it read my previous post and decided to prove me wrong! lol

Tell you what, ill postpone the log caps until after your commits hit and I upgrade again. At that point, ill put it through the paces and provide logs if the problems persist.

As always, I truly appreciate everything you've done for us! Your work is simply amazing... :)
[Nook Color Android Development] dalingrin:
I would wipe clean for the next nightly that has my commits. Don't restore your previous apps with Titanium Backup and see how the Nook behaves. It would be great to narrow this junk down.
[Nook Color Android Development] bradputt:
i made it a habit of calibrating my battery after every flashing.

since then i never have any SOD any more.

you should try it.
[Nook Color Android Development] Jimbo67:
When you say " calibrating my battery"--do you mean clearing battery stats in cwm? Just trying to make sure my brain is on the same page. ;)
[Nook Color Android Development] bradputt:
i use battery calibrator from the market, you won't have to boot into recovery.

but yeah it's basically the same thing.

https://market.android.com/details?id=com.nema.batterycalibration&feature=search_result
[Nook Color Android Development] lschroeder:
To change the boot loader from Loading to the Green logo I did something like this. From the OP get update-genimage-1.3.zip and place on the boot partition, use power off and select boot into recovery. Reboot again into 131. Place the nightly 131 and OC 06/30 kernel back in the boot petition again even though it is working. Again use power off in 131 to select Recovery. This time you will see peguin as it reinstalls 131 and OC 06/30. The difference is that now the boot loader will be changed to the Green logo and 132/133 should now work. Reboot, the Green logo instead of Loading should come up. I used the utility NookColorUMS to select the 1st partition, boot partition, to load directly without removing SDcard. NookColorUMS is a thread in this group of XDA.

The reinstall is necessary because the Green logo boot loader comes from your nightly install. When you see Loading it did not get installed because 1.3 needed to be reinstalled to make it work. Crazy, but that is how I fixed it, I think. Selecting Reboot into Recovery from 131 is how I get around the "n" timing method of getting into Recovery.
[Nook Color Android Development] Zenoran:
Lag gone with 134?
[Nook Color Android Development] newellj79:
On the commit page n134 is showing nothing new since n133. Either its a typo, or it hasn't been merged (fixed) yet.
[Nook Color Android Development] tootseroel:
Is there a better gtalk for the nook that is more finger friendly. The send button doesn't work without multiple taps. Maybe a honeycomb gtalk APk that will work?
[Nook Color Android Development] doncaruana:
Using Nenamark with build 131, I get 24fps (only overclocked to 1200, no voltage modifiers).

With build 134 I'm down to 8fps. So I'd say no, the lag isn't gone...
[Nook Color Android Development] Phatdawg:
The log page shows that the gpu change out to the old drivers has not occured yet. So until then expect, fps to be low, I imagine on neocore anyhow.

Other another important note.

Has anyone been noticing when there is a random crash or SOD, that the message you get is that the theme caused it to crash and that it is resorting back to the default theme (although the default theme was already the theme)?

Edit:

FYI

http://cm-nightlies.appspot.com/?device=encore

The next nightly will have the GPU drivers reverted.
[Nook Color Android Development] :
Pre nightly nightly?

Could one of you gentlemen with a build rig make a nightly w/the reverted GPU drivers? Of course when I need my NC to function well, I already installed the latest nightly :)
[Nook Color Android Development] rjsmith2007:
Just use an old nightly....
[Nook Color Android Development] :
WOW!!!!!

YOU'RE A GENIUS!!!

\ sarcasm

If I wanted to do that, don't you think I would have done it?
[Nook Color Android Development] harpo1:
WOW WHAT AN ASS!!!

Go read his kernel thread and it explains how to revert back on the last couple pages.
[Nook Color Android Development] joenathane:
There is only one way to settle this!
[Nook Color Android Development] Phatdawg:
1) Dude, if you read the last couple pages, you already know it's been accepted for an update in an upcoming night...FURTHER (see next point).

2) In my post above yours, I BOLDED, that it's coming out in the next nightly.
[Nook Color Android Development] jacjar1:
HAAAA...good one Will ferrell bat fat now that is genius
[Nook Color Android Development] RASTAVIPER:
Can someone confirm that during charging, Nook doesnt sleep?

Also screen doesnt turn off, only fades out a bit.
[Nook Color Android Development] I Am Marino:
I know my Nook never sleeps while charging.

and to make the screen completely shut off usually while charging, I have to hit the power button.
[Nook Color Android Development] gudism:
Same as above here
[Nook Color Android Development] boxcar8028:
its needed for adb and data transfer.
[Nook Color Android Development] Character Zero:
Does this mean that its already checked in. Can I do a repo sync and build and have these changes, or is it anticipated they will be checked in before the next nightly?
[Nook Color Android Development] ianPhillips1:
Not sure if the changes are available until the build bot does its thing. Its getting about that time to spit out our nightly anyway.
[Nook Color Android Development] newellj79:
Yes, u can build and it will b included.
[Nook Color Android Development] henel321:
I'm in serious withdrawal .... Where's that nightly? Just look at that juicy change list and nothing today... :)

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] slider2828:
Its 12:36PM in the afternoon LOL.... its not even dark yet, when nightlies come out hahaha..... GO USA Women's
[Nook Color Android Development] TheMainCat:
Anyone know which kernel needs to be used to explore the bit depth feature in Dal's Nook Tools app? I am running the 6/30 kernel (and it looks like that aint it), but maybe the kernel it needs is in one of the latest nightlies. I may answer my own question when the N135'ish build comes out.
[Nook Color Android Development] Ronin3178:
Yes, right now only 132+ works with the bit depth portion.
[Nook Color Android Development] TheMainCat:
Thanks. That's what I thought. I tried N132 briefly, but with the lag I was experiencing, I backed it out without looking looking at the depth feature. I wil give it a go once the next better'er nightly comes out tonight.
[Nook Color Android Development] frankusb:
Will we get OMAP3: wlan: Fix memory access violation in wlan driver in the next nightly? Or does one of the pre built binaries cover this code?

And it looks like Bluetooth PAN is on it's way as well. Nice.

thanks,

Frank
[Nook Color Android Development] newellj79:
Can somebody point me in the right direction to learn how to build my own nightlies from the repo? I have a windows 7 machine.
[Nook Color Android Development] fattire:
Looks like it's time to ****can windows (or run linux in a VM).

Here are instructions.
[Nook Color Android Development] newellj79:
Thanx. I'm downloading the stuff to try and get ubuntu running on top of windows.
[Nook Color Android Development] TheAmazingDave:
Those instructions hosed my linux install. :-(

I was trying to install the required libraries but not all of them were available in the package managers. I tried to sideload them and it messed my system up. Any tips?

Edit: I'll post the offending files on my break.
[Nook Color Android Development] fattire:
Undo that middle thing.

Probably a good idea :)
[Nook Color Android Development] Bonnie_Raitt:
I've been installing CM7 on several friend's NC over the past few weeks. Usually install nightly and gapps, reboot and all is well. I did an installed of N134 on a virgin NC tonight and started getting FC almost immediately. It said something like "Force close of Android media Application"

I tried clearing cache, I deleted data and set back to defaults. Nothing seems to have helped. Any ideas?
[Nook Color Android Development] slider2828:
Usually that is indicative of a bad copy of flash.... So delete all partitions on the card and start again.... Also did he buy a good sdcard?
[Nook Color Android Development] TheAmazingDave:
libsdl1.2-dev

zliblg-dev

Sun-java6-jdk
[Nook Color Android Development] slider2828:
Damn is 135 nightly going to come up soon??? Hahhaha been waiting literally all day hahaha... refresh refresh refresh..
[Nook Color Android Development] fattire:
You didn't mention your distro, but here's what I have installed (ubuntu) FWIW:

Looks like the buildbots are going in slow motion.. I think there was a repo sync error having to do with a volume mounted read-only... so i guess they'll be working on it.. in the meanwhile, keep working on that build process :)
[Nook Color Android Development] Divine_Madcat:
You know, the build bots always find a way to die like that, right when there are fun changes waiting in the winds...
[Nook Color Android Development] ianPhillips1:
.......any second now:D
[Nook Color Android Development] bigbob23:
But they seem to work just fine when there are no changes in the queue (133->134). :D
[Nook Color Android Development] newellj79:
So true. This has prompted me to try and learn to build myself. Look for a new thread, dedicated to all the questions and problems I have trying to get it setup, soon. :)
[Nook Color Android Development] weiqj:
131 is good, 132-134 have lots of problems

BTW, how to overclock above 925MHz?
[Nook Color Android Development] Hindle1225:
http://xdaforums.com/showthread.php?t=925451
[Nook Color Android Development] ianPhillips1:
Boom goes the dynamite....... http://download.cyanogenmod.com/get/cm_encore_full-136.zip
[Nook Color Android Development] bigbob23:
I'm trying that also, but have run into a few stumbling blocks. I was running Linux in a VirtualBox VM on my Mac but hadn't allocated enough virtual disk space (there are a lot of files to install here!) so I am redoing it. If there was a way to only get the encore files, it would take much less space and download faster.
[Nook Color Android Development] bradputt:
Why did it jump to 136 ?
[Nook Color Android Development] slider2828:
[YOUTUBE]ahoidh-VmSw[/YOUTUBE]

Agreed!!!
[Nook Color Android Development] slider2828:
Too much coolness for 135 most likely.... I was up all night and there wasn't a build last night... such a sad life I live....

I found the link before for the changelogs.... but I can't find it now... sucks...

Can anyone post up the nightlies change log?
[Nook Color Android Development] EverythingNook:
is 136 still laggy?
[Nook Color Android Development] slider2828:
Last I read 135 reverted back to the old sgx graphics drivers... Thats why everyone's waiting for 135.... So it shouldn't be....
[Nook Color Android Development] boxcar8028:
so tempting to flash n136, but been holding at 128.

I know, chicken sh%#:D

is it safe yet?
[Nook Color Android Development] slider2828:
I flash 134 before.... its fine.... It includes dalingrin's kernel and some other stuff too..... I haven't seen anything unstable about it... Before I was at RC7.1...

I am not sure what you mean by safe? LOL....
[Nook Color Android Development] bradputt:
Well my nook didn't explode after I flash 136

do we need to flash the kernel now?

is it merged into the nightlies?
[Nook Color Android Development] slider2828:
Any noticeable lag? Whats your nenamark score? LOL.... My flash porn depends on it LOL................ :D
[Nook Color Android Development] ponyboy82:
I haven't tried myself yet, but Dal's OC kernel should be in the nightlies since 134 so you don't have to flash it separately.
[Nook Color Android Development] jacjar1:
First thing ill do once workday is over...hopefully laginess is gone 134 brought my nook to a crawl..
[Nook Color Android Development] boxcar8028:
hold off guys, a new one is coming.

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] doncaruana:
Why not use 136 that's out there right now? The next nightly will just have the two extra fixes below, so far.

Lockscreen default option

Added this for users to be able to return to default color.

Lockscreen landscape fix

Fixes the force close introduced by http://review.cyanogenmod.com/#change,6731
[Nook Color Android Development] ponyboy82:
Yeah, I think everyone's been eager to get 135/136 because there were some issues with the updates in 134 that should be fixed. Otherwise, there's always a new nightly around the corner.
[Nook Color Android Development] :
136 is fine. Back to non-laggy graphics and all. Built in OC'ing is fine. Ready for a new stable perhaps :D
[Nook Color Android Development] danvee:
Works fine on my SD card install....

BTW, is everyone else's NookColor starting to glow green and smoke too? :p
[Nook Color Android Development] ponyboy82:
using emmc... mine has gone plaid
[Nook Color Android Development] danvee:
Ahhhh...Spaceballs reference.....:p

But does it have Ludicrous Speed? Or is that going to be in N200?
[Nook Color Android Development] d0gan:
just installed 136 to the sd card. All my market downloads are failing for some reason. Anyone know why?
[Nook Color Android Development] boxcar8028:
alright, just flash n136. all seems to be okay, smooth and running great, so far so good:D

but even with 32bit and surface dithering enable I still see banding in the start up screen in the xda app. videos looks about the same. market downloads just fine. cm7 emmc

kernel: 2.6.32.9erik@myhost#129

32 bit enable: neo core 25.9 fps, quadrant 2601

16 bit enable: neo core 29.9 fps, quadrant 2619
[Nook Color Android Development] Awats:
Running B136 on SD. Everything is working including the market.
[Nook Color Android Development] newellj79:
[Nc cm7QUOTE=bigbob23;15763696]I'm trying that also, but have run into a few stumbling blocks. I was running Linux in a VirtualBox VM on my Mac but hadn't allocated enough virtual disk space (there are a lot of files to install here!) so I am redoing it. If there was a way to only get the encore files, it would take much less space and download faster.[/QUOTE]

Same here. Only setup a 5gb partition for Ubuntu. By the time I installed the first thing in the setup guide (jdk) I had 1.1 TB left. Can anybody recommended a good size for setting up a vm build environment for NC cm7?
[Nook Color Android Development] ianPhillips1:
All is well emmc oc'ed at 1275. Netflix, market, animations and few games with no issues.
[Nook Color Android Development] doncaruana:
Actually, I notice that my nenamark scores dipped a little bit. I'm not doing a bunch of tweaking - I just OC to 1200 and that's it. With 131, my score is 23.5, but with 136 it dipped to 21.5.

I have 2 8GB Sandisk class 4's that I go back and forth with on these so it's fairly apples-to-apples.

Have no idea if that even makes sense, but I figured I'd report it...
[Nook Color Android Development] dexx0008:
did you test the speeds of the cards? i have numerous sd cards of same class and size, they don't always report the same speed. Even the same sd card will slow down on multiple concurrent tests as it heats up a bit. just some observations i've run across.
[Nook Color Android Development] crandy2:
Problems with 136

Flashed 136 from rom manager. Cleared Dalvick, then rebooted into recovery and wiped cache and Dalvick, ran fix permissions.Left the kernel settings at 300/800/Conservative. Didn't change any of the voltage settings.

No matter what I do, when I tap the power button to turn the screen off, it turns off, but won't turn back on. I also disabled screen off and screen on animations. I guess this is SOD, not sure. I've flashed a lot of nightlys, this is the first time I have had this happen. There is a last_kmsg, if this is still needed, I can post it.

The only way I can get it back is the power + N button for a few seconds, followed by the power button to restart it.

It runs fine when it is up, but I guess I will have to go back to N128, this is a deal killer for me.

Anyone know of anything else I can try?
[Nook Color Android Development] bigbob23:
Same here. Only setup a 5gb partition for Ubuntu. By the time I installed the first thing in the setup guide (jdk) I had 1.1 TB left. Can anybody recommended a good size for setting up a vm build environment for NC cm7?[/QUOTE]

I had a 8 GB partition, but had a lot of stuff already installed. I redid it with a 35 GB partition and it stalled after installing over 5 GB (it appears to be almost finished). I'm going to stop the process and rsync again (hopefully it won't start over).
[Nook Color Android Development] doncaruana:
Well, I took a backup of the card before I updated it. I just rewrote that backup on the card and I go back to 23.6 or 23.7 (consistently - same as the other card, still on 131)

Updated the same card I updated before with 136 again and get the same 21.5fps in nenamark. Don't know why, but there's definitely a "downgrade" there. Not sweating it, just reporting it...
[Nook Color Android Development] newellj79:
I had a 8 GB partition, but had a lot of stuff already installed. I redid it with a 35 GB partition and it stalled after installing over 5 GB (it appears to be almost finished). I'm going to stop the process and rsync again (hopefully it won't start over).[/QUOTE]

I just rebuilt my vm with 20gb. Will install jdk soon. The try to figure out eclipse and sdk. Let me know how it works out for u.
[Nook Color Android Development] bigbob23:
I don't know what eclipse is, so didn't worry about that. I finally got everything installed (it took a L*O*N*G time!) and am compiling now (which also takes quite a while). My internet connection is ~4 Mb/s and I'm running Ubuntu 11.04 (32 bit) in VirtualBox on a 2.1 GHz Mac Mini) Currently it is using 13.8 GB so 20 should be fine.
[Nook Color Android Development] jacjar1:
flashed 136 to my Nook running off of SD...much better results than with previous 13X builds. so far so good OC to 1200. Dont do anything real fancy but I think I am getting closer to going back to CM7 on EMMC...
[Nook Color Android Development] newellj79:
Thank u sir. Don't be surprised if I pm u with a question or to down the road.
[Nook Color Android Development] bigbob23:
I'll be happy to share my limited knowledge :D

After two hours it is still compiling. Sort of reminds me of compiling a Linux kernel on a 20 MHz 386 back in 1994. I have another machine on which I plan to install native Ubuntu which should be quicker.

Edit: It took a bit over 4 hours to compile and create the zip file. "df" showed about 17.5 GB was used. I installed it and get the boot loader Cyanogen image, but it goes into a loop at that point :(

Oh well, it was an educational exercise in any case.
[Nook Color Android Development] TheMainCat:
Flashed N136 and the "lag" is gone!. Unfortunately I am seeing the same FC with HBO Go that I did with every other N13x build. Anyone else seeing this?
[Nook Color Android Development] doncaruana:
I'm still curious if anyone else has done any definitive benchmarking. I got 23.6 on nenamark with n131 and get 21.5 with n136 (vs 7.5 with n134). I know it's not much, but it doesn't seem like a simple revert of the gpu drivers would cause the score to go down.
[Nook Color Android Development] paleh0rse:
Did you do the following? (Using titanium backup)

--wipe HBO go app data

--uninstall HBO go

--reinstall HBO go (app only)

--re-run dizzy's IMEI generator

All of those steps are required each and every time you upgrade to a new cm7 nightly.
[Nook Color Android Development] darkamikaze:
anyone know how to fix the lockscreen when it looks smaller than the whole screen?

shame on me.. should have searched.

Spare Parts >click-unclick compatibility mode > reboot
[Nook Color Android Development] skwalas:
Its called random variability. A single measurement in each case is not definitive. Do the test several time over the course of a few days (NOT back to back) under each condition and then decide whether a difference was really observed.

Your friendly statistician
[Nook Color Android Development] TheMainCat:
Yup. Learned that lesson a bit ago. Weird stuff. FC's everytime I try to login. The usual behavior (if you don't do the above steps) is that the app just hangs. This is a different animal and like I said, I only see this with the N13x Roms. On N128 or earlier Roms the app runs great.
[Nook Color Android Development] slider2828:
What clock speed are you running? I only get 16fps on Nenamark1.... wth...
[Nook Color Android Development] fattire:
A few notes.

Number one: CONGRATULATIONS! Finishing the build is a big deal, even if it doesn't exactly work yet. That's to figure out. But bask in the glow of a successful build.

Number two: If you built the right thing (encore, right?), and the build finished, and the zip flashed, I'm guessing the issue is something like you not clearing the cache or something. Unless you did a lot of hackery to get it going in the first place... You might take a look at the logcat to see what it's getting hung up on and wipe all the caches and previous systems and everything...

Numero tres: on the build time-- 4 hours is excessive. On my MBP it would take 2.5. (It now takes under 20 minutes on my thinkpad!) You don't have to build in ubuntu-- you know you can build on os x too, right?
[Nook Color Android Development] quepaso:
Running 136 from a fresh wipe/install to EMMC. Nanamark1 does 23-23.2 fps. OC'd to 1.2. I did get a SOD earlier, but i forgot to switch the governer to InteractiveX. It was on conservative when it happened. Im going to try and reproduce the error.

edit - Ive been trying for a while now and SOD wont happen, since i switched to the interactivex governer its been fine. Deep sleep comes on every time and everything works flawlessly. Great stuff. Amazing work to CM7 team and dalingrin.
[Nook Color Android Development] Taosaur:
136 is running smooth for me. Nenamark1 score of 20.5, OCed to 1300 on InteractiveX gov.
[Nook Color Android Development] doncaruana:
Thanks for the input. Here's what I did.

Ran nenamark on 2 identical SD Cards with n131 on them several different times over several different days. I always get 23.6 or 23.7.

Then I've run it on n136, restored that card back to n131, and then back to n136. And I ran it again just now and actually it's anywhere from 20.9 to 21.5. But not one single time I have run it with n136 has it topped 21.5.

I don't think this is a matter of random variability - it's far too consistent on both builds.

I am running OC'd to 1200 and the conservative governor, no voltage or stepping tweaks.

So far, the few reported numbers seem low by comparison. Maybe it makes sense to one of the devs...
[Nook Color Android Development] khaytsus:
No. Simply rebooting fixes the lockscreen, it defaults to the lower res one until it knows better.