yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] uries62:
Problem with wifi still

Is anyone else having problems with wifi? I still can't connect to an unprotected MAC authenticated network (its a roaming campus wifi). When I try to connect, it will find the ap, scan, try connect, and then revert back to scanning mode.

The only way I have found to get it to work is pushing the /system/etc/wifi directory from nookie froyo. Once I do this and reboot, wifi starts up immediately.

Also, I am running with a density of 180, maps works fine and reader is full screen. You need to remember to turn off compatibility in Spare Parts or the apps will never scale to arbitrary LCD_DENSITY values.
[Nook Color Android Development] Mikey:
Installing the latest version from this thread worked :)

http://xdaforums.com/showthread.php?t=865525
[Nook Color Android Development] Narfx:
Not here. Google reader *starts* in full-screen mode. But if I try to read a news item inside a feed it'll go to small-screen mode, compatibility mode disabled or not.
[Nook Color Android Development] rainmaker002:
I'm not sure if it's the same wifi problem I was having, but using Spare Parts and setting Wi-Fi policy to "never while plugged in" fixed all of my wi-fi problems, which were similar to what you've described.
[Nook Color Android Development] adma84:
don't have my NC in front of me but I thought Nightly 8 fixed the google reader issue (I saw in review.cyanogenmod.com that they set the density back to 160)
[Nook Color Android Development] subcypher:
Softkeys For Root Users works well too!
[Nook Color Android Development] Snyperx:
What is the key commands to get into the cyanogen mod recovery? Thanks.
[Nook Color Android Development] EpicFail236:
Check my sig for a mod that turns the volume keys into back and menu buttons. Usable as a decent workaround, if you dont turn your volume up and down all the time.
[Nook Color Android Development] philburkhardt:
Google Reader does that for me, no matter what I set my screen to. 160, 169, 169.33333, 180, 200 & 210.

I have been setting my screen to 210 since I got my nook. That's what I am going to stick with for now. I can read everything on my nook while holding it at a short distance. The Market and Maps work fine. I have had Maps 5.1 working the entire time I have been on CM7, and that has been since the first nightly.
[Nook Color Android Development] Calla969:
I know it has been mentioned a lot already, but I thought I was lucky. Not so, market has stopped showing "My Apps" and now it won't download anything. It just says "download unsuccessful". I haven't even been using it today, so no idea what triggered the change. I've tried all of the fixes I could find, but nothing has worked. Hopefully the Market will get completely fixed soon, it is pretty annoying. No big deal though, it's worth it to play with CM7. The NC runs great with it!
[Nook Color Android Development] Chahk:
I'm confused. Are you saying that for best results we shouldn't use the Ondemand governor with the latest nightly? Should we leave it on Performance?
[Nook Color Android Development] dalingrin:
No, I was explaining the changes I've made to get ondemand to work more efficiently on the Nook. Performance governor will always be fastest but at the cost of battery. In other words....keep using ondemand.
[Nook Color Android Development] Canadoc:
On an aside I am having wifi trouble on CM7 that I didnt on froyo.

My work wifi won't connect. Oddly if I copy the system/etc wifi files from froyo that are missing from CM7 the problem is fixed.

Also on wifi my slingplayer won't play but a few seconds and disconnect but if I tether via 3g (adhoc tether to my iphone) it seems to work fine....
[Nook Color Android Development] newellj79:
question about rom manager

With rom manager premium can u use the check for updates feature to upgrade nightlies and future versions of cm7. If not currently, at some point? I'm seriously considering buying the app and would like to know what some of the benefits are.
[Nook Color Android Development] dalingrin:
What files are missing? Softap should be the only thing missing and that wouldn't help, I wouldn't think.
[Nook Color Android Development] Canadoc:
within softap is a scripts folder which I added also there is a file tiwlan_drv.ko

which is absent. When added the scripts folder and this with repaire dpermissions and reboot I can then access my work wifi otherwise no go
[Nook Color Android Development] rvv2002:
So I installed the CM7 V8 build and everything was amazing. Running stable after OC. I inserted the SD card so that I could format it and it started flipping out saying "erase the card, format"...then again the same messages. I restarted the NC and then everything was gone (NC would not boot/black screen). Apparently I formatted the wrong thing from within the Settings option? Did I miss a key piece of information from within the posts?
[Nook Color Android Development] Divine_Madcat:
Like both of you, i am having the same issues; though at first it was even worse - it would hang on the boot. I have rest the voltages, verified the clockspeeds, set the bit depth to 16 bit, but it is still slugglish as allll get out..
[Nook Color Android Development] 12paq:
Hmmm.. I'm sure you guys are looking at this closely..

sounds like the CPU clock speed is stuck at a low setting..

Does cpuspy give any feedback?

I'm going to hold off.. need my Nook for a photo shoot today, thanks to USB host, lovin it!
[Nook Color Android Development] bigbob23:
It doesn't seem all that slow to me, Quadrant score of 2553 with highest clock at 1200 and conservative governor, 32 bit framebuffer off, 2437 with it on.

After running Angry Birds for a while, CPU Spy shows mainly 1200 MHz activity.
[Nook Color Android Development] Divine_Madcat:
Its not a case of "feeling" slow.. it s a case of Nenamark 1 going from 23 FPS to 10, and the shutdown screen taking 5 seconds (at times) to fully transition...
[Nook Color Android Development] bigbob23:
OK. I hadn't tried Nenamark 1 before. I get 13.5 but haven't seen the delay in screen turnoff (yet).
[Nook Color Android Development] Divine_Madcat:
It doesn't always do it, but before 132, it had never done it. Something is very wrong with this build....
[Nook Color Android Development] MrPib:
I'm also seeing the slow screen-off animation since running Netflix.
[Nook Color Android Development] newellj79:
please help

Because of a display defect b and n sent me a replacement NC today. I popped in my cwm boot card and tried to restore my backup. It errored when trying to format /data and aborted. My original NC was bought in January. Is there a chance the replacement is newer with different partition specs? If so how can I restore my backup from original nook to it. Thanks.
[Nook Color Android Development] bigbob23:
You probably got one of the newer models (blue dot on the box). You will need to repartition it, see http://xdaforums.com/showthread.php?t=1094371.
[Nook Color Android Development] dalingrin:
I'm noticing the same thing with N132. It looks like the new GPU drivers aren't doing well. Will probably switch back once I get home this afternoon.
[Nook Color Android Development] TheMainCat:
I am relived that others are seeing the lag with N132. I "flashed" it and wasn't sure what I was seeing was correct. I liked the really slow screen off animation (it reminded of the early days of TV with the clicker remote...not to date myself or anything), but the delay just between going from screen to screen was baffling. I also noticed that my HBO Go would FC consistently. For a sanity check, I went back to N128 and everything returned to normal.
[Nook Color Android Development] doncaruana:
Pardon my ignorance, but I assume that means that latest nightly = RC plus any new advances. So builds after 115 are essentially 7.1RC1+, right?
[Nook Color Android Development] sisterchick:
Here is my understanding - or at least what my simple mind grasps. :) Code changes are made just about every day by the Cyanogenmod team. These changes are reviewed and contributed to the repository if acceptable. Some are general and apply to all devices supported, some are for a specific device. There is build bot that is used on a host computer that kicks of a new build for each supported device from the repository nightly (or most nights.) These builds become Nightlies for the not faint of heart to try. After enough changes are made, the developers determine that a Stable or Release Candidate is in order for general use. So they pick a point out, make a build and call it RC or Stable. In this case, somewhere around 115, there was an RC released. But the stream keeps going and the builds keep going nightly, now up to 132 I think, moving toward the point where a build will be considered worthy of being called a Stable build.
[Nook Color Android Development] DizzyDen:
You have a very good "simple mind" ;)
[Nook Color Android Development] Phatdawg:
I went from MIUI to this nightly, did a clean install, and reinstalled all the apps cleanly as well. Basically a totally fresh install.

No lag problems. I did have a crash that it recognized from an issue with the theme, but otherwise, running smoothly.
[Nook Color Android Development] ganovim:
The cm7 contains the latest OC Kernel, but would this work on EMMC as well as SD ?

since in the past there were 2 seperated kernels for emmc and sd
[Nook Color Android Development] Divine_Madcat:
That is a bit of a misnomer. The actual kernels themselves were the same; what was different was the install scripts also contained in the zip, that put the kernel in the correct place depending on your installation.

Anyway, yes, it should be just fine for SD (with one less thing to install); but, wait for nightly 133.. ;)
[Nook Color Android Development] Chrisnook:
I noticed the lag bigtime when playing a game also Video's on Youtube were very choppy , I went back to my backup and all is fine for now
[Nook Color Android Development] :
Yes and no. Yes that they are the same base, and no because 132+ all a LOT of new stuff (wifi/gpu/cpu? updates). But 132 is a bit...off right now, so hold off til greater minds dig in. Also from here on out the nightlies/stables will have the ability to OC built in, as well as 16 and 32 bit frame buffer (I went back to 16 even though 32 is checked by default, but still having weird performance issues...messing with governors now).
[Nook Color Android Development] Colchiro:
Make sure you have the latest version of recovery, 3.2.0.1, which is required by NC's partitioned with new scheme (blue dot). You can update your bootable sdcard w/o losing data by following the instructions here: update your bootable sdcard to 3.2.0.1.
[Nook Color Android Development] gullygossner:
I am seeing no difference lag wise with 132, improved quadrant as well. 2303
[Nook Color Android Development] Phatdawg:
Yup, I'm about 10 hours out with moderate use, haven't noticed any problems with hbo go netflix or angry birds.

Anything in particular I should stress test it with to see if I'm just not having the right content to see the lag?
[Nook Color Android Development] Ronin3178:
Here is my experience with 132,

http://xdaforums.com/showpost.php?p=15658983&postcount=3916

the only thing I have to aadd now is that wifi did take a little longer than normal (connect and go ffrom white to green)
[Nook Color Android Development] Divine_Madcat:
All i had to do to see the lag was turn it on. It was performing so bad, i didn't even TRY to use it. just opening the app drawer killed it..
[Nook Color Android Development] newellj79:
Does n e body know off the top of there head which gapps version gives you the video chat option? I got a replacement nook today and the icon is not showing up with 6/3 gapps.
[Nook Color Android Development] doncaruana:
Methinks this is a function of how much CPU tweaking you've done. I'll bet the people who aren't having issues aren't really seriously overclocking or pushing the limits at all. Just a guess, but maybe some folks could report what they are doing with the CPU?
[Nook Color Android Development] newellj79:
I think its pretty much a moot point because dal said he would be changing the gpu back.
[Nook Color Android Development] bonald:
I don't have any lag using the ondemand governor. With interactivex I am seeing the lag.

Fresh install, cleared cache and data.
[Nook Color Android Development] vtmike:
Could some people claiming no lag do a graphics benchmark. Neocore for example should be in the 30 fps ballpark if all is working well. Also a noticeably slower screen off animation is a symptom.

That's interesting about the governor. I was on interactivex when using n132. Didn't try ondemand because cpuspy looked normal.
[Nook Color Android Development] Phatdawg:
i downloaded it. I don't see a place for the fps.

Anyhow, no problems with it. Occasional stall, about once or twice a run, but nother than that seem pretty smooth.

On demand 1200 oc.
[Nook Color Android Development] TheAmazingDave:
I believe that's because ondemand will leave the CPU clock higher for a longer period than interactivex, which scales CPU closer with real time demand. (could be wrong there) Higher clocks mask the lagginess, I've noticed.
[Nook Color Android Development] Ronin3178:
Ok, tried Neocore both in 32bit and 16bit, interactivex and ondemand respectively, I got 13.9fps both times. I know I was getting closer to 29.9-30.x before. But that is the only place I have seen a problem with performance.

EDIT : Going to performance governor, scored 17.9 with 32bit.
[Nook Color Android Development] dalingrin:
The new drivers were causing performance problems for me. I verified by only changing the drivers and the performance increased.

Interestingly, I am having trouble getting real 32/24 bit color. My 32bit/16bit switch does work in Nook Color Tweaks as verified by SurfaceFlinger but the end result always looks 16 bit'ish. The same is true when using nightly 129 so I guess it has been a problem for a while now.
[Nook Color Android Development] vtmike:
I tried it out with ondemand and it does speed it up some due to it running at maximum clockspeed for more of the time. The lower fps shows there is an issue with the updated gpu files. Its very apparent when you do something as simple as turn the screen off.
[Nook Color Android Development] psychoace:
Someone suggested this earlier but change your minimum CPU speed to 600MHz and most problems will go away.

Actually if you use anything but performance you have to bump your CPU to 800MHz min in order for the turn off animation to perform correctly. If you leave it at 600MHz the app drawer will run silky smooth on any governor. If you set min to 300MHz then performance is the only way to not run into slow downs.
[Nook Color Android Development] dalingrin:
Reverting to previous GPU modules:

http://review.cyanogenmod.com/#change,6722
[Nook Color Android Development] TheAmazingDave:
will anything be done to fix the new drivers or will you just stick with what works?
[Nook Color Android Development] gunnerhk:
Thanks Dalingrin for all this awesomeness.

My user experience with 132 has been the best so far. I have it on ondemand, and the scrolling latency (the lag between the finger moving and the scrolling starting) seems to be the lowest so far, at least in pulse,xda app, and app drawer.

Scrolling seems smooth in both 16bit and 32 bit for me. Before 132, I got a slight hesitation and stutter in the scrolling, but it seems a lot of that has been smoothed out.

I pray it does not revert with the old drivers :D

I don't overclock and voltages at default.

I guess I'm lucky I don't get PBD, SOD, and wifi wonkiness. :p
[Nook Color Android Development] skwalas:
Hardware accelerated movies took a definite hit. Watching the same movies via software looked fine. I saw the same thing running quadrant: the 2d test showed the same fps I always see but the 3d tests were seriously laggy.

All other experiences have been just fine. I would be willing to bet those who've played with undervolting may be the ones experiencing the worst non-3d lag?
[Nook Color Android Development] darkamikaze:
mmm .. nightly 131 is giving me SOD.. 1 so far :o

would 132 fix that issue?

I just set wifi sleep policy to never.. hope it fixes it before i flash to 132.
[Nook Color Android Development] newellj79:
Please post the cm7 commit merge link (updates) . I lost it.
[Nook Color Android Development] ianPhillips1:
Wrong thread.oops
[Nook Color Android Development] ziggy34:
http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] everalm:
Nook Color freezes when using VMWare View client

Done a search, can't see this being brought up previously.

Currently running a Nook Color,

Android Version 2.3.4

Kernel Version 2.6.32.9

Mod Version CyanogenMod-7-06232011-NIGHTLY-encore

No problems with any apps UNTIL now.

Installed the VMware View (Tech preview) client, version 1.1 to access my company VDI.

This works on my Nexus One running a very aged CynaogenMod running Android 2.3.2

On the Nook it starts, it asks for the RSA ID and number, it authenticates and connect, asks for AD User ID, Domain and password, connects, opens up the initial "this is how to use finger gestures screen", I can close that, it starts to build the view then the Nook hard locks up. Total freeze, can't go back to the home page, can only be hard booted.

Tried 5 times, both on battery and plugged into the mains, tried two different WiFi connections both with and without encryption no difference.

Any ideas from the guru's...?
[Nook Color Android Development] newellj79:
Thanx.

10char
[Nook Color Android Development] newellj79:
Is n133 running better than 132. I didn't see the gpu driver changed back n the log but I'm at work and am rushing.
[Nook Color Android Development] joenathane:
The change hasn't been accepted & merged yet...
[Nook Color Android Development] fogbav:
short question to the professional freaks ... there is no Nook touch forum here ... so excuse me when i ask here :

How dificult would it be to transfer the knowledge on Nook Color to Nook Touch and develop a nook touch version of cynaogen ?

Isn't it the same board with nearly same hardware - only changes in display ?

greetings - fogbav
[Nook Color Android Development] Awats:
I tried both 132 and 133 and they hung at the loading screen. Backed down to 131 and it loads. I am wondering if it's related to the clock setting. Before 132, you had to load OC kernel after you installed but with 132+ OC is built in so it must try and boot with the faster clocks ... which it might not like.

Edit: I tried setting the clocks to 800Mhx before I installed B132 or 133 and they still hang up at the "loading" screen. I don't get what is happening.
[Nook Color Android Development] dalingrin:
Overclocks are not set until boot is complete for this reason.

Are you running on eMMC or SD card? Have you changed the bootloader from what comes with CM7?
[Nook Color Android Development] Awats:
I am running from SD. I've never done anything else so the Nook is stock. I am using the VG 1.3 loader for my image. I have been using it for quite a few builds now and haven't had to reimage the card. Nice to have all of my apps and data remain.

To be clear, I never get past the loading screen on reboot after the zip file is expanded. I copy the zip file over to the SD card, reboot, get loading, count to 4, release the buttons, about 5-10 seconds later "loading" disappears but the backlight stays on, then around 60 seconds later the backlight goes off. I reboot again, wait for "loading" and the release buttons. Before, it would show loading for a few seconds, then the screen would go blank (backlight on) and then the CM7 dude would skate by and stop. On 132/133 "loading" just stays up.

I pulled the card and looked for the zip file and it's gone so it did expand. It's reboot into the new build that is giving me a problem.

I tried it all again and got the same results. I did stop both B132 and 133 after 5 minutes on the loading screens since I figured I was well past the normal boot time. I put 131 back on and it expanded and loaded fine.

Terry
[Nook Color Android Development] dalingrin:
This is because you are using the old u-boot bootloader. It cannot handle kernels that are larger than 3mb. I've modified the CM7 u-boot to use larger kernels but I didn't think about SD card installs not getting the updated bootloader.

I'll remove the optimizations and get the kernel back under 3mb so future releases will work for SD card users without replacing u-boot
[Nook Color Android Development] rhester72:
Oh, how I hope this was sarcasm.

Rodney
[Nook Color Android Development] Awats:
For anyone on SD card that runs into this, rename the u-boot on your SD card to something else, extract the u-boot from the build and copy it to the SD card.

The newest Nook Tweak still doesn't like the kernel for the display settings but I will figure that part out.
[Nook Color Android Development] dalingrin:
lol, it was not sarcasm.

I'm going to remove the optimization until I can get Verygreen to cherry-pick my u-boot changes and update his SD card installer.
[Nook Color Android Development] Awats:
Thanks Dalingrin. It's hard to tell with some people here.

I copied the u-boot over and got it going. If it gets changed for future builds, it will remove that step. I can't run the latest nook tweaks for the display settings but I am sure that will fall into place at some point.

Terry
[Nook Color Android Development] dalingrin:
Do you have the latest SD card installer?

Verygreen just told me that v1.3 automatically uses the u-boot from CM7
[Nook Color Android Development] Awats:
Yes, I've been using it for the last several builds. If it does, that's strange since the only thing that worked was moving the u-boot from the build to the card.
[Nook Color Android Development] dalingrin:
Definitely strange. Other folks have the new builds working on SD card.
[Nook Color Android Development] Awats:
I'll update the SD card again and see what happens. No sense in getting hung up on it if it's working for others.

Thanks again! At least I know what is happening.

How about the kernel issue for the display tweaks? It says I need a newer kernel. I thought 133 had the newer kernel (it seems to since the OC's are there.) OC 6/30 doesn't seem to satisfy it.
[Nook Color Android Development] dalingrin:
Display settings was an issue with my Nook Color Tweaks app. It should work with 1.4.2. The SD installer doesn't make all the symlinks that are in the normal CM7 update.zip.
[Nook Color Android Development] Awats:
That fixed it!

I'll leave you alone now. :)
[Nook Color Android Development] fattire:
So I just rebuilt the newest tree with the reverted older graphics drivers + a new TLS register patch from dal...

Good stuff.. nice 'n smooth. That video lag is gone. Assuming kmobs checks this in tonight I think the next nightly will be pretty good and the first "good" one with the OC kernel built-in.

(on the other hand I'm only clocked to 1225 or so... but still seems to be going alright)
[Nook Color Android Development] paleh0rse:
My status since upgrading to n132:

--SOD has returned with a vengeance...happens every time I turn screen off for more than five minutes. This actually started when I went from n106 to n118.

--No deep sleep at all reported in CPU spy. Again, started when I updated to n118, continues in n132.

--Graphic lag makes video unbearable with either 16 or 32bit. This one started with jump from n125 to n132.

Needless to say, mine is pretty much hosed... for now. Ill probably try a fresh wipe to 1.2 stock, then straight to n132 to see if these problems continue.

If that fails, ill probably revert to n106 until things get worked out, or I get inspired to try n150 or 160, etc.

N106 was 100% stable for me with the exception of a consistent PBD at 11%, so that will be my fallback....
[Nook Color Android Development] paleh0rse:
Anyone have a link to n106? I accidentally deleted my copy, and need to revert. None of the old pinks in the nightly repository are working for me... :(