yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] legolee:
i agree, somewhat random. i try to reproduce the freezes but fail. I remember the freezes tend be occur when CPU is under heavy loading.
[Nook Color Android Development] Narfx:
You are :)
[Nook Color Android Development] Arbelzapf:
Is anyone able to help me with this? I just can't get it to work
[Nook Color Android Development] paleh0rse:
Anyone? Please? :)
[Nook Color Android Development] dalingrin:
I've no plans to put the IMEI hack in CM7.

We do plan to try to come up with a workable solution though.

I'm reuploading to a new host as we speak.
[Nook Color Android Development] ADude:
Sounds good to me.
[Nook Color Android Development] chadamir:
Dal, why do I get higher linpack scores on my droid 1 at a lower clock speed than I do on my nook at a higher one? It's the same cpu.
[Nook Color Android Development] legolee:
hey guys, seriously, benchmarks like quadrant score and linpack are just for reference only, it does not necessarily reflect the actual performance of the device.

and there are always some background process running when you perform the benckmark, so score does varies. if you want a great score for fun, always stick to performance governor with 1200min and 1200max.

I would say the actual performance of this .32 kernel beta 3.1 is so much better than any build+oc kernel of .29 !

p.s. still trying to reproduce the random system freezes problem. I think the problem is the CPU governor. looks like using smartass is more likely to have system freezes.
[Nook Color Android Development] scriptx:
People, worry less about benchmark scores and more about experience. I couldn't be happier with how my nook is currently running. I could care less to get into a penis-size fight with benchmark wars!
[Nook Color Android Development] Narfx:
Installed with the OC kernel, awesome performance, no problems detected =)
[Nook Color Android Development] dalingrin:
Link updated in OP. May the downloading commence.

What do you get? and at what clock speed?
[Nook Color Android Development] MedLine:
hey man you say some pretty smart things sometime

EDIT: btw where's hockey, is his Nook still dead?
[Nook Color Android Development] Arbelzapf:
Please guys, help me with this. Last time this happened, reflashing gapps worked. I tried gapps-gb-20110503-signed.zip and gapps-gb-20110307-signed.zip, none of these will bring be back to the account setup. Perhaps I'm just forgetting something embarassingly simple, but wiping cache, dalvik and system did not help so far.

What am I missing?

EDIT: Just to clarify: I have the old problem of not being able to access any google services. Market closes, Youtube complains, Calendar entries are missing and so on
[Nook Color Android Development] chadamir:
Linpack is supposed to be more objective. I'm actually curious for technical reasons, but thank you for the advice. I think that a 15-20 percent performance difference on a cpu test at the same clocks might show affected performance, don't you?

Dal, both are running at 1100 mhz on performance governor (though i have tried others and it makes little difference)

Both are at 1100 mhz and I think the droid 1 uses chevyno1's kernel on cm7. I get around 14.5-15.3. On the nook I get around 13.2-13.5

Edit: Also smartass governor seems to be returning lower scores and inaccurate results. On demand at 1200 mhz I get low 14s.
[Nook Color Android Development] ScottyNuttz:
Well you could try clearing all the caches and reinstalling CM7 from scratch, then installing the gapps again.
[Nook Color Android Development] legolee:
dal, i think i can reproduce the system freeze problem.

300/1200 smartass -- very often system freeze, need pressing power button for 7 seconds to restart

300/1200 performance -- seems to be most stable, still testing

300/1200 ondemand --was stable, but system freezes still happen quite often

To sum up, It usually freezes when using smartass/ondemand governor and cpu is under heavy loading. by the way, for scrolling speed, 300/1200 ondemand is noticeably smoother than 300/1200 smartass.

the freezes should have nothing to do with setcpu and seepu

I hope you will find the above info useful :)
[Nook Color Android Development] lyam23:
I'm not using the OC kernel and I've experienced freezing on conservative and interactive. :(
[Nook Color Android Development] Arbelzapf:
Already did that, but I'll just try again.

EDIT:

Nope....still out of luck

EDIT2: Why is it that I can't find any of the Google apps in system/apps after flashing? Shouldn't there be a Onetimeinitializer.apk, Googleservicesframework.apk and so on?

EDIT3: Woohoo it finally worked! As a last resort, I tried the internal recovery which has NEVER before worked on my device. So yet another huge thanks to dal. Now I can finally use Rom manager instead of my recovery sd card
[Nook Color Android Development] dalingrin:
Be sure to use the OC kernel thread to discuss issues with it.

I'll keep an eye out for the issue.
[Nook Color Android Development] MACLUIS1:
Unless Bluetooth range is fixed, I'm not flashing anything else.I'm totally happy with beta 3.1 and OC 1.2 smartass governor. Netflix, movie streams, CNN, Facebook, twitter, YouTube, etc. What can I ask for?. The hell with Quadrant scores!!!!!!!.LOL.
[Nook Color Android Development] dalingrin:
Did you mean ondemand? There is no interactive governor in 2.6.32
[Nook Color Android Development] chli:
Yeap lots of freezes here as well :(

I come from CM7 Nightly 68 and I flashed in CWR u-boot 1.2 / CM7 beta 3.1 / wiped cache and dalvic and rebooted.

I use the ondemand governor : 300 - 925 MHz

I'm about to test the OC kernel to see if its any better.

Edit : Seems that my problems are gone with OC Kernel, strange.

(tried smartass and ondemand 300 - 1200).

Edit 2 : Just crashed again.
[Nook Color Android Development] MedLine:
you forgot deep sleep
[Nook Color Android Development] lyam23:
Yes, my mistake. Typing from memory, there.
[Nook Color Android Development] poofyhairguy:
I am on vacation so I might have missed the bluetooth conversation, but am I the only one with triple the range?

My bluetooth GPS syncs at two feet (used to be six inches!) and works at 4-5 feet. My Retro Wiimote used to work at 4 feet, now works at 12+ (big as my hotel room). Also, bluetooth starts long after boot. Is bluetooth considered "fixed" except for mics?
[Nook Color Android Development] Divine_Madcat:
The does remind me - what is holding us back from getting BT Mics working, so we could do things like skype? The BT kernel drivers, or something in CM7?
[Nook Color Android Development] TJNooker:
So far so good...

I just finished getting my UI all back to normal after updating to 2.6.32 Beta 3.1 and the OC kernel. So far everything seems to be working as it should.

If it's of any use, here's how I updated to .32:

Previous Set-up:

2.6.29 Kernel

u-Boot 1.1

CM7 Nightly 70

OC Kernel 4/18C

Update Process:

- Flashed u-Boot 1.2 over top of old set-up

- Used TB to backup apps to Dropbox

- Made a CWR 3.0.2.8 bootable sdcard w/the appropriate files

- Wiped System, Wiped Data, Wiped Cache

- Flashed Beta 3.1, Flashed Gapps, Flashed OC Kernel

- Wiped Dalvik Cache (which miraculously didn't freeze)

- Rebooted

- Completed the mandatory Android set-up

- Downloaded TB & synced with Dropbox

- Used TB to restore missing apps w/data (no system apps or system data)

UPDATE: Sorry Mom! I fixed it. Can I go back outside now?
[Nook Color Android Development] ADude:
dalingrin has asked us to post all reports involving the OC kernel into the OC kernel thread - thanks.
[Nook Color Android Development] Divine_Madcat:
Oh mom, what would we ever do without you? :P
[Nook Color Android Development] spiicytuna:
Am I the only one who is no longer deep sleeping with beta 3.1? With beta 2 I was deep sleeping... I did the uboot, then the beta3.1, then the oc .32 kernel. How can I check what is keeping my nook awake?

Thanks!
[Nook Color Android Development] Arbelzapf:
I just experienced a reboot. After enabling Bluetooth, Wifi went off. When I tried to disable and enable it, the screen went black and it rebooted.
[Nook Color Android Development] moesasin:
mirrors!!

update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip

md5sum: cd6eb7032f612451d48ba444b772ba35

http://www.multiupload.com/TET8F3T6O6
http://hotfile.com/dl/117731149/6c22b25/update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip.html
http://www.megaupload.com/?d=PQPDGE5Z
http://depositfiles.com/en/files/hq7jyedxc
http://www.zshare.net/download/9011082698ef3d4b/
https://rapidshare.com/files/3727521269/update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip

PM me if you want me to delete them.
[Nook Color Android Development] Skilover:
OK, let me ask: How do I flash this? Do I flash it like a new nightly build, or is it a different process? For nighlies I install the new ROM on the sdcard and then use clockwork to boot up and install the zip on top of the existing ROM, only wiping cache. Once installed, how do I keep it updated? Thanks!
[Nook Color Android Development] chli:
This is a fantastic improvement. It's so much better than before.

Thank you.
[Nook Color Android Development] legolee:
if it is connected to the charger, it will not deep sleep.

Once unplug from the charge, turn off screen, then it deep sleep again :)

I am on beta 3.1 with oc kernel
[Nook Color Android Development] Animec:
EDIT: wrong thread

The touchscreen seems perfect now, thanks a million :) everything stable so far, no weirdness. 1.2 GHz with the smartass governor runs a little hot on my nook. This was occasionally the case with 1.3 GHz with performance gov on the .29 kernel, but is more constant for me with this latest kernel.
[Nook Color Android Development] ADude:
I prefer " Bad Cop ":
[Nook Color Android Development] :
Anyone else getting random pauses in playing local music on latest beta and oc? Streaming is fine.
[Nook Color Android Development] iDidItAll4theNookie:
gReader app is now working. :)
[Nook Color Android Development] spiicytuna:
Yes I know this. Been off the charger for hours... CPUspy shows deep sleep as an unused state.
[Nook Color Android Development] Ronin3178:
did you refresh cpuspy?
[Nook Color Android Development] Nburnes:
Shows it as a well used state for me.
[Nook Color Android Development] iDidItAll4theNookie:
Anyone else seeing their lockscreen running at phone-like resolution and not at full screen? Did I accidentally hit a setting? It wasn't doing that on the last beta.
[Nook Color Android Development] DeadlyDa:
As a quick FYI, I seem to be more fortunate. Gem Miner works fine for me. Running 3.1, OC'd to 1.2 w/SMARTASS governer.
[Nook Color Android Development] Ronin3178:
Yes, when I enabled it, it was at phone size.
[Nook Color Android Development] KitF:
Did you try clicking an article?

(Doesn't work for me)
[Nook Color Android Development] newellj79:
Edge of screen almost impossible for me tobuse in some areas. Best example, when signings into Netflix in portrait mode, keyboard comes up, I have to hit the number 1 and the @ symbol literally 30 times to get it to take once. Any suggestions? Aside from that I'm freaking loving this build! ...beta 3.1 @ 1.2ghz
[Nook Color Android Development] iDidItAll4theNookie:
Just tried an article on ars. Worked like it should, but faster than rooted 1.2 thanks to the 925 OC. I'm currently running on SD, to see if I'm ready to switch over.
[Nook Color Android Development] djlim4:
I thought the new build fixed this, but maybe you need to recalibrate the touchscreen?

http://xdaforums.com/showthread.php?t=972388&highlight=recalibration

there's a link to the nookdevs forum for the adb method and there's also a link there for a recalibration app. I've used the app, it was much easier than adb
[Nook Color Android Development] joenathane:
This thing flys with the OC kernel, much faster than .29

Great Job!
[Nook Color Android Development] seth.i.simmons:
Same here, I loved having a lockscreen when I was on the nightly's, but now when I enable it, it's a very small rectangle on the top of the screen, like a small phone screen. Any way I can fix this? If not, I can do without a lockscreen, but I really liked having one.
[Nook Color Android Development] newellj79:
Enable compatibility mode.
[Nook Color Android Development] chisleu:
I think you just have to reboot after turning it on? Maybe the fix wasn't brought over yet. I don't need a lockscreen.
[Nook Color Android Development] aludal:
Has video playback really improved (inline, Adobe Flash 10.3 like on:

-- clips of news.google.com

-- movies of youtube.com/movies

-- vimeo.com "HQ" clips

-- hulu and maybe hulu "HD" (above 480p)?

.29 was showing Neocore in 20...23 FPS area, OCed or not, what are Neocore marks for .32?

Last thing: after all that ext2-to-ext4 juggling, would it be correct way to "upgrade" using CWM 3.0.2.28 -- instead of 3.0.1.0?

Thank you, and thank you dalingrin: hopefully we'll see the

adequate

for Gingerbread 2.6.35 or 2.6.36 OMAP kernels working on NC very soon.
[Nook Color Android Development] ADude:
From what I have read, the best procedure is:

- Upgrade to 7.0.2 if you have not done so already, in order to get the latest ROM Manager.

- Use ROM Manager to upgrade CWM to 3.0.2.28 (takes like 20 seconds)

- Upgrade u-boot.bin to the one found in B&N's 1.2 update to Froyo (search this thread if you need more info on that)

- Then upgrade to the zip in the OP, wiping cache and dalvik-cache

- Let everything settle for ~5 minutes during the first running of .32

- Reboot
[Nook Color Android Development] celyst:
The fix for the tiny lockscreen is just to reboot. Goes back to full screen after that =).
[Nook Color Android Development] ADude:
news.google.com does not have its own material - it is just links to other sites, so do you mean NYTimes ? BBC ? Wall Street Journal ?

mobile.nytimes.com makes you go to a separate video section - I watched one and it was quite pixelated.

mobile bbc.co,uk is same. Their video section has a one minute world news. It was a lot clearer but low framerate for most of the minute - which may have been the long distance perhaps.
[Nook Color Android Development] joenathane:
inline video has always been great for me on .29 and still is with .32

give it a try yourself, come and join the dark side, we have cookies
[Nook Color Android Development] Divine_Madcat:
Ignore him.. he keeps spouting on about random crap that he knows nothing about, and it drives certain members here crazy (aka, a friendly dev who has done some amazing kernel work for us.......)
[Nook Color Android Development] aludal:
Thanks, Mr. ADude!

On video, I meant anything with Flash inline (like a Web page youtube.com where all news.google.com links marked with "YouTube" icon lead. The thing is, Adobe says 3rd time in the row that Flash 10.3 utilizes hardware acceleration (actually, HW rendering) -- at last. However, it takes Android 3.1 to see that...

In any case, youtube.com/movies can give you enough material to test. Just use stock Browser and try to watch your favourite old free movie for more than 15...25 minutes: to see whether any stuttering, A/V desync occurs, and hanging after 30...45 minutes.

Pixelation you mentioned might be because of inability to turn ON "hardware" in Flash 10.x Player -- even if it's still unable to use it.

Thanks for the "upgrading" procedure description: it's clear, must be put into the OP, but quite convoluted still. Hopefully, someone cooks th ROM out of it, LOL.
[Nook Color Android Development] ADude:
There was nothing weird about his post here, it seemed innocuous.

Devs are free to ignore whoever they like, but the some of the users who slam his posts can barely write a coherent sentence - I think perhaps they are put off by the highly technical details that he posts.
[Nook Color Android Development] ADude:
The B&N 1.2 update contained an Adobe 10.1 flash player apk that has hardware acceleration designed for the NOOKcolor. I currently don't have it installed, but could do so.
[Nook Color Android Development] Ronin3178:
Just got 30.1fps on Neocore, 3.1b, .32 OC 300/1200 Smartass

30.3fps 1200/1200 Performance
[Nook Color Android Development] seth.i.simmons:
Is this after enabling compatibility mode?? I haven't tried compatibility mode yet, we'll see if that fixes it. Weird thing is I didn't have to do that on any of the other roms (CM7, Phiremod, HC).
[Nook Color Android Development] Divine_Madcat:
Nothing wierd? You mean other than him asking the same damned question for the 50th time, despite dalingrin (and others) answering them. He is convinced that video is broken (wrong) and that it has something to do with the GPU (it doesn't, video is handled by the DSP).

Sorry, but his constant badgering gets REALLY old...
[Nook Color Android Development] aludal:
Thanks for all your care. 30.3 FPS is really outstanding result for NC. Hardware overlay/full OpenGL ES 2.0, when made available system-wide, should bring it to 50...55 FPS. Which is what Opera scrolling and YouTube app show already.

Any changes in ALSA/audio max level? I'm not asking about DRC, if it takes it.

To dalingrin: was the improved edges/corners screen sensitivity achieved by subtracting 5 peripheral pixels as before in CM7, or more elegant solution was found?
[Nook Color Android Development] chadamir:
Anyone have a problem where when using tablet tweaks the status bar just totally disappears.

Edit: Also, I'm not sure my battery reading is correct. Anyway I can check. It hasn't seemed to move.
[Nook Color Android Development] mkm1126:
Hi All! Firstly, thanks to the Dev's for such amazing work!! I'm continue to be impressed and excited by the development seen here.

Tonight I'm trying to flash the 3.1 experimental .32 rom. I think the mistake I may have made is upgrading my u-boot first to 1.2, but not sure. Here's my situation:

I flashed the new u-boot (btw, I was on the 7.0.2 rom with cwm 3.0.1.0), then rebooted. Everything came up fine, then I went to Rom Manager to upgrade to 3.0.2.28 CWM. In Rom Manager it showed me on 3.0.0.5 and did not give me any options to upgrade. I tried to reboot into recovery from Rom Manager and all I get is a black screen. So, I used my sd card to boot into 3.0.1.0 recovery, and reflashed the 3.0.1.0 recovery, then flashed the .32 rom. I removed the sd card and put in my normal sd card. All booted fine and I show I'm running the new rom (with the .32 kernal). I went to Rom Manager only to see it is still showing that I'm at 3.0.0.5 cwm. I tried to reboot recovery and I can no longer boot recovery from emmc, only from my sd card.

Can anyone help me figure out how to fix my cwm on my emmc?

Thanks!
[Nook Color Android Development] mooja:
So I've got a weird one. On my home wifi i cant seem to stay connected for more than about 45 seconds. it shows that i have full signal and it still reads i have an ip address, but i just cant access anything, but on other networks(i tried my network at work) it worked fine. works fine on the .29 kernels, and the issue happens on both beta 3.1 and the .32 oc kernel. i tried changing my encryption to a few different things on my home network(mostly just different wpa2 configs) with no change. i tried reflashing from scratch to beta 3.1 and no dice either. i tried all the different governors to no avail. what kind of logs should i gather for something like this?

and yes i made sure to flash the 1.2 uboot
[Nook Color Android Development] joenathane:
Have you tried opening ROM manager in CM and reflashing CWM?
[Nook Color Android Development] mkm1126:
I tried, but it wouldn't work, the only version it listed was 3.0.0.5 and it said there were no updates available. Strange, because I was on 3.0.1.0.

Edit:

I am going to try the recovery fix from here (will post back):

http://xdaforums.com/showthread.php?t=1024010
[Nook Color Android Development] stevemp:
Same thing happened to me. Wiped and started over. Followed ADude's instructions below and every thing worked fine. I had a backup so it was not a big deal.

From what I have read, the best procedure is:

- Upgrade to 7.0.2 if you have not done so already, in order to get the latest ROM Manager.

- Use ROM Manager to upgrade CWM to 3.0.2.28 (takes like 20 seconds)

- Upgrade u-boot.bin to the one found in B&N's 1.2 update to Froyo (search this thread if you need more info on that)

- Then upgrade to the zip in the OP, wiping cache and dalvik-cache

- Let everything settle for ~5 minutes during the first running of .32

- Reboot
[Nook Color Android Development] mkm1126:
Step 2 from the post linked above worked for me. After this step (because it restored the 1.1 u-boot, I simply flashed the 1.2 uboot. I can reboot into recovery using the recovery option in the power menu (great!!). Interestingly enough my Rom Manager still seems to be borked as it shows my current version of CWM as 3.0.0.5 still even though when I boot into recovery via power menu, it boots in 3.0.2.28. I'm not sure it really matters at this point now that we can reboot recovery from the power menu, but does anyone know what might be up with this?

Thanks!
[Nook Color Android Development] stevemp:
Have you tried wiping cache and dalvik-cache? Sometimes that fixes problems.
[Nook Color Android Development] mkm1126:
Yes, several times. What is the latest version of ROM Manager? I'm wondering if it's not getting updated when I flash a new rom? Is this possible? I don't want to hijack this thread with Rom Manager issues though. I will investigate a bit further tomorrow and if I can't get it corrected or find that it's really even an issue (again, I don't know that I'll even need to use Rom Manager now), I'll create a new thread in the general forum.

Thanks all! Time to get some sleep!
[Nook Color Android Development] lilgrass71:
Hi

I have the March build of gapps . Will that work.

I forgot where I can obtain the newer builds if that is required would anyone kindly point me in the right direction?

Thanks in advance!
[Nook Color Android Development] explorer-10:
is the latest beta okay to use or is it recommended for devs only at this point?
[Nook Color Android Development] Nburnes:
I would say it's fine to use.
[Nook Color Android Development] Arbelzapf:
Does the lockscreen need to be enabled for the sleep mode to work? I just looked at the battery after the first night with the new kernel and I certainly do not see the improvements it's supposed to bring. Went down from 96 to 86
[Nook Color Android Development] Narfx:
Smoother performance and better battery life than ever, reboot to recovery from power menu working, screen-off animation working... it's not fine, I'd say it's the best till now by a big margin :)
[Nook Color Android Development] furius:
Sorry for noob questions...

I m on 7.0.2 om emmc with CWM 3.0.2.8...

How can I check which is my uboot version?

Where can I find the uboot 1.2?

Can I flash this uboot as usual with cwm?

Thanks
[Nook Color Android Development] lschroeder:
What SD method are you using? I can not get verygreen's to work with beta2 and 3.1? It worked with the first two releases. If it worked not sure how to intall new OC kernels that allow 1200. I know 925 OC comes with the beta.

Anybody else using SD with current beta? Are you OC it?
[Nook Color Android Development] madguy2006:
Hello

Need some help:

I installed the ROM (beta 3) and then flashed the Google apps on top of it (gapps-gb-20110307-signed.zip ---> from CM).

I can find the Market icon, Google chat icon and Google search icon but NOT the Gmail icon.

Could somebody tell me what I should do to get the Gmail icon? Did I do something wrong?

Thanks in advance!
[Nook Color Android Development] derekr:
I'm randomly losing the status bar and the Tablet Tweaks buttons when coming out of sleep. Yesterday it came back after running a couple of apps, but this morning it was really gonzo, and I had to reboot to bring the status bar back.

I have never had this happen before this beta...