yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mrapollinax:
DOH

*headdesk*

File this under "Crap I knew this but didn't even think about it"

That said, no SOD issues for me, great work!
[Nook Color Android Development] That Baker Guy:
Im having a big problem guys, when my NC is on the wifi nothing else can connect, laptop, sgs3 or kf. they all time out. but as soon as i disconnect the nc it goes back to working just fine. im on the b2 build. my router is an older router set to g only. not really sure what is going on here.
[Nook Color Android Development] bigrat:
krylon:

Thanks for your work on this.

Regarding O/C - I am well aware you took out the options above 1000Mhz, and why you did so. I don't disagree. I simply wondered *where* those options are set, since setcpu can change them, but I didn't understand how. Are they compiled in? are they a function call of some sort? Would you like me to ask this question somewhere else?

Regarding the "dim/off" lockscreen. The screen is black, it doesn't wake up, the device isn't plugged in, and it's in b2. I'm just reporting it. In fact, I just reset the nook right now on it's second occurrence of this problem. Clearly, the device is doing *something* but the screen isn't coming back on after sleeping. What information can I get you guys so you can resolve this? Want me to wipe the device completely and re-flash?
[Nook Color Android Development] krylon360:
Not able to reproduce this issue. Ive got my NC, my GNEX, my laptop, my wifes E4G, my upstairs PC, my wifes NC, and my DS all connected to wifi, and everything is able to connect.
[Nook Color Android Development] That Baker Guy:
thats crazy, i have my macook, kf, sgs3 xbox etc on the wifi, soon as my nc connects to the internet everything goes down, while it is still able to load web pages and everything, ill try a clean wipe again.
[Nook Color Android Development] dparrothead1:
I have been in this from the first post and I have read each and every post. Alpha 1, I was experiencing SOD with the backlight coming on. Beta 1 was the same. Beta 2 is the same, but without the backlight coming on,,,,,just black screen. This happens each and every sleep mode.

I have tried dirty flashing. I have flashed from a complete wipe. I have flashed using the tablet zip by meteorod and without it.

Only thing that helps is Wakelock set on partial. You have my info using my screen name.

I do appreciate the teams hard work and other than the SOD, I really like this ROM. I wish I had the technical knowledge to be more helpful.

Edit: BTW, this happens with and without the charger cord attached.
[Nook Color Android Development] MrPib:
I don't remember what device was involved, but I recall seeing this problem mentioned elsewhere. It was fixed by replacing the router.

I think if it was a CM10 issue, more people would have it. And it's not like it's a problem that people wouldn't notice.
[Nook Color Android Development] boomn:
Was the MAC address issue fixed? Is the issue possibly related to that?
[Nook Color Android Development] RallyStyle2003:
I've had this happen before. Unfortunately there are incompatibility issues that come up with newer devices. When the router is still in its support cycle, the manuf will look into those problems and issue firmware updates to fix them. I'd suggest checking for new firmware or known issues with the manuf., then try resetting your router to default factory settings and see if it still happens. If that doesn't work, it's time for a new router.
[Nook Color Android Development] lollyjay:
I agree with you. Not a problem for most of us. I've been connected to at least a dozen routers with no problems.

QI0CM9787SV

12/11/2010

ES1.2

cyttsp
[Nook Color Android Development] majorpay:
*Probably* circumstantial, but this post reminded me that for the first time ever, my OBI202 went nuts and started cutting out. I also had more cutouts and hangs on Netflix on XB360 last night.

This does coincide with the upgrade, but for one thing, my Nook should have been sleeping during the phone call this morning.

Just thought I'd throw it out there. Likely nothing. Nook is still running well on B2, but performance has dropped a bit after stacking the launcher with apps (seems to be the case on all my Android devices).

This truly is a remarkable daily driver. I should probably note that I have had no more lockscreen SODs (so far) since applying the tablet mode hack.
[Nook Color Android Development] That Baker Guy:
i know its not a cm10 issue becuase both my sgs3 and kf are running that latest nightlies have been for a while. it is probably the router its an older model, but brand new also flashed with dd-wrt. ill keep watching it
[Nook Color Android Development] krylon360:
trust me, I'm sure if it was an issue with the rom, I would have heard about it long before now, due to I connect into my works wifi with my nc.. ;)
[Nook Color Android Development] dparrothead1:
Edit II: This is really weird...with the charger plugged in, it will wake using the "n" and the volume rocker....but NOT the power button??
[Nook Color Android Development] mrapollinax:
You could check the logs of your router. Look to see when the MAC of your Nook connects and see if it precedes the network behavior you are seeing. It really does sound like a router issue though, either a config or something firmware related. I have to look at some packet captures but I don't think that the NC is sending out any VLAN or TOS/DSCP values that could confuse as QoS settings on any SMB type wifi gear.
[Nook Color Android Development] bigrat:
Well, I've wiped the Nook clean (system/cache/factory) and installed b2 and gapps, so there shouldn't be any legacy crap of mine floating about.

I can confirm that if I just bump the power button to wake the nook up, I get a "dim" lockscreen, and often, the nook just goes back to sleep. If I want the nook to wake up, I often have to hold the power button long enough to get the reboot menu to show up. I strongly suspect I still have the "screen won't wake up" issue, or whatever we'd like to call it now.

I did not have this issue with b1. In fact, I don't think I had any trouble at all with b1.

EDIT: Waking the device with the "N" button does not trigger this issue, and works correctly. Only the power button wakeup triggers this issue.
[Nook Color Android Development] krylon360:
for those having the dim lockscreen issue,

just dbl tap power. that will wake it to life.

it's being looked into.
[Nook Color Android Development] samcoinc:
Or use the volume... Seems to work every time for every combination (pluged in, unplugged,.....)
[Nook Color Android Development] sisterchick:
Thank you, kind sir.

I doubt this helps at all, but just in case...I don't have the dim lockscreen issue on B2 UNLESS I set lockscreen to "none" in settings. That will trigger it every time. Turn the lockscreen back to "slide" and it goes away.
[Nook Color Android Development] dparrothead1:
What about those with a totally black screen??
[Nook Color Android Development] krylon360:
you seem to be the only one with it. Not a whole lot we can do for an isolated issue. Hard to troubleshoot since we cant reproduce.

Are you a SD install or EMMC?
[Nook Color Android Development] bigrat:
I had this too. I am an emmc install. What information should I collect if I reproduce? dmesg?
[Nook Color Android Development] dparrothead1:
EMMC always. I have never done an SD flash.

I guess if I'm the only one, then I will just have to live with it. If I want to keep this ROM. And I have had my NC rooted and running a ROM since 1.1 Autonooter. Was using your AOKP until you stopped supporting it.

Thanks, anyway.
[Nook Color Android Development] frankusb:
Unless I missed the dim lock screen, I've had it once. EMMC.

Frank
[Nook Color Android Development] FloydF:
Something appears to cause a problem with my network. With my nook and Squeezebox on the same ssid, the squeezebox cannot maintain a connection to the server. Unfortunetely it could be the squeezebox, server or the router.Server is an old (at least 7 years) toshiba laptop with atheros Wifi.

I have a mesh router that uses a firmware based on ddwrt or ROBIN I think. It has 2 ssids, changing to a different ssid from the player and server seems to fix the problem. Again, no idea why, but easy fix for me.
[Nook Color Android Development] naughticl:
Loving B2... but

B2 seems to be working great, but the screen sensitivity seems to be an issue. Is there no touch calibration process? Any other available adjustment?
[Nook Color Android Development] fattire:
I can't remember what this app did exactly; it was so long ago with another kernel and all that, but you can try it and see if it does anything.
[Nook Color Android Development] mateorod:
I have the same hardware as you. I have been running a test kernel with no problems, but installed beta2 to see if I had your issues. A couple of hours in, it seems like everything is running fine....what does your dmesg say?
[Nook Color Android Development] bornagainpenguin:
Are there any work arounds for the menu button on beta 2? I really want to stick with CM10 for the sheer performance improvement in games, but I read a lot on my NookColor too and one of my eReader uses the context menu to change chapters. I really don't want to have to go back to CM7 if I don't have to.

EDIT: I'm aware that the context menu has been fixed upstream, and will be released as part of what will become Beta 3, I'm just asking if there are workarounds to hold me over until the official release. Editing to clarify this now before someone accuses me of not reading the thread.
[Nook Color Android Development] dparrothead1:
I know how to pull that up, but I don't have sufficient knowledge to read it. Should I be looking for some error in particular?
[Nook Color Android Development] afzalarsalan:
Just post it and I'm sure someone will help you out. Its completely anonymous so that shouldn't be a concern.
[Nook Color Android Development] vettejock99:
Let screen time out. Go grab a coffee. Come back, and no Burton will prompt device to resume. Power button must be held to force a hard reset. Happens here, and I believe there are other valid reports but whatever, you are the dev so I am prepared to be wrong.
[Nook Color Android Development] majorpay:
I have seen it. Not a true SOD in my case though (backlit screen lights up, although black). Holding power for a bit pulls up the context menu. Clicking anywhere on the screen wakes it up long enough to get in (most of the time). Ever since I flashed the tablet hack, it's appeared to have been "better" about this. Also, as someone else pointed out, if you set the volume button to wake the device, that also appears to fix the problem.

It's like the lockscreen goes missing or something. I'm actually curious if a lock app would fix that.
[Nook Color Android Development] andtron:
As some have reported using the volume up-down buttons instead of the power button will solve the screen dim issue.

This is how I do it, in Settings->Display->(Volume Rocker Wake), turn it on.

Now when you nook is asleep, instead of using the power button, click either volume udown will wake it up.
[Nook Color Android Development] sisterchick:
Workaround: Go to settings/system/hardware keys and turn on display overflow menu. That will give you 3dots in apps. Put a shortcut to settings on your desktop and you should be good for now.
[Nook Color Android Development] vettejock99:
yeah I get that too, but as you noted it is a different issue. I think setting the lockscreen back to slide fixed that though.

UPDATE - putting the lockscreen back didn't fix the dimmed screen upon resume after all, at least not here.
[Nook Color Android Development] pastordl:
Looked in Settings - System (under interface) - nothing listed for Hardware

Looked in Setting - System - Again no hardware keys
[Nook Color Android Development] bytte:
Krylon360

Please take moment to look over the above dmesg - I hope you will agree something bad was happening.

HTH
[Nook Color Android Development] That Baker Guy:
i had a guy pm me earlier about having the same wifi issues as me. not sure if we have the same router or not, but its atleast another report, im not crazy right?
[Nook Color Android Development] nookle:
I also have the wifi problem. Didn't happen with the CM9 rom I had on earlier. Soon as I put CM10 on it did it. My laptop's wifi connection would drop to 5 Mbps. Drove me nuts for awhile, as I was transferring large files from my laptop to my server and the transfer speed was like 200 KBps. Turned the wifi off on the nook and my connection shot back up to 65 Mbps.

If it makes any difference I have a D-Link DAP-2553 Wireless Access Point. And I am actually running the build from 10-26-12, before the beta releases.

Oh, and Krylon and the rest who have worked on this, you are all gods among men. Fantastic work. I was thinking about getting a new tablet, but this has given new life to the old nook. Thanks!
[Nook Color Android Development] barkerdogg:
Ditto that. This is exactly what is happening to my nook. At first it started out happening occasionally but it happens pretty much every time it goes to sleep now. Double tapping the power button has no effect neither does using the volume key. The only solution is to long press the power key to reboot.

Suddenly my calendar has also started force closing. Is anyone else also seeing this? Wasn't happening before.

Good work anyway devs. Looking forward to beta 3.
[Nook Color Android Development] bluepen61:
The Devs have done well at building JB to work on the NookColor! Thank you to all who are programing this rom.

So here is my observations after nearly 2 days on B2:

My NC, ES 1.2, build 10/28/10, and the ccyt thingy which is written down on my journal at work.

Installed B2 over B1; B1 was a clean wiple/format install after Alpha.

Dual boot on EMMC, B2 in primary, B&N/MN in alternate.

The Oh the NC Wakes to a Black Back Lit Screen started occuring slightly 24 hours after the install and use of B2.

I charge every night, night 1 it charged ok. Last night I charged to 89%, the charger cable was yellow, and after a minute or so of use, the battery meter read 100% with the yellow cable remaining yellow. I powered-down the NC and booted to B&N / MN 5.8.20 and the battery level read 99%. Powered-down again and the meter read same in B2. Used it for about 45 minutes in B2 and the battery declined to 94%. Performance is set to INTERACTIVE. It has been charging for about 45 minutes, reads 100% but still yello cable. And now it seems to wake up on power button tap
[Nook Color Android Development] bornagainpenguin:
I'm not seeing hardware keys listed as an option either.
[Nook Color Android Development] lollyjay:
It is in my system. Don't know why it's not in all.

QI0CM9787SV

12/11/2010

ES1.2

cyttsp
[Nook Color Android Development] bluepen61:
The ONWBBLS issue does not occur when I am listening to music using the Pandora app. It fully wakes up using the power button, and after unlocking the NC, it appears to bring you back to the screen it slept on. I tested both Pandora and the Homescreen. And this was through auto-sleep and not a forced sleep from pressing the power button. And it works when forced to sleep.

This is probably why I did not experience it during the daytime yesterday while listening to music.

Thinking back, it might not have been a problem when listing with Apollo music player app... And I just verified the same results as with Pandora. Maybe this might help the devs.
[Nook Color Android Development] lollyjay:
Didn't find other posts on this. No matter what I set my home screen grid size, it remains at 6x6. Anyone else with the same problem? BTW using trebuchet.

QI0CM9787SV

12/11/2010

ES1.2

cyttsp

CM10 Beta 2, Trebuchet, Tablet b1
[Nook Color Android Development] lasereyes:
Nook causing problems for Wireless

I've been having this same problem too (with CM10 B2). When I have my Nook on, my laptop's wireless starts cutting out, but as soon as I turn off the nook, everything goes back to normal. I didn't have this problem with any other ROM, and this didn't happen in CM10 A1. I have no idea why this would happen though...
[Nook Color Android Development] grayfoxmg1:
:Warning Ignorance ahead:

Could it be that, our nooks (when acquiring an IP address) take the one the applies to our routers, thus making a conflict. And some how that conflict resolves itself with having the Nook access the internet and barring everyone else from it.
[Nook Color Android Development] Nooter:
I noticed this yesterday, as well. Not an isolated case!
[Nook Color Android Development] lollyjay:
OK. Can confirm that my NookColor also interferes with my Mac notebook's wifi speed when connected. Just by working the connect / disconnect, I can see the effect on speed of running the same process on my Mac.

QI0CM9787SV

12/11/2010

ES1.2

cyttsp

CM10 Beta 2, Trebuchet, Tablet Update-b1
[Nook Color Android Development] samcoinc:
To test you could set the ip address of the nook manually.
[Nook Color Android Development] nookle:
I found a setting in the advanced wifi settings that seems a bit odd. Not sure if it is the culprit of the wifi strangeness. There is a wifi region code setting, and it seems to be permanantly set to 'Europe.' I click the radio button for 'United States' and it seems to take, but when I go to my home screen then back into the wifi advanced settings it is back on 'Europe.'

Is this normal? Or is this a bug?
[Nook Color Android Development] lasereyes:
I just tried that. It made no difference. I don't think it's an IP issue.
[Nook Color Android Development] grayfoxmg1:
same here, sorry for wasting everyone's time
[Nook Color Android Development] lollyjay:
Just tried to set from Europe to USA and it goes back to Europe on mine too.

QI0CM9787SV

12/11/2010

ES1.2

cyttsp

CM10 Beta 2, Trebuchet, Tablet Update-b1
[Nook Color Android Development] bytte:
Sounds like it is a bug, but it shouldn't be a problem. It should only affect what channels the wifi will work on. The router controls the channel it uses, the Nook finds the router on that channel. (Europe has more channels than the US IFIRC).
[Nook Color Android Development] bytte:
Sounds like it is a bug, but it shouldn't be a problem. It should only affect what channels the wifi will work on. The router controls the channel it uses, the Nook finds the router on that channel. (Europe has more channels than the US IFIRC).

Suggestion:

Could someone who is suffering this problem do some diagnosis.

Ideally you will have:

Some spare time

A second android device on which you will install and run Wifi Analyzer by FARPROC (from Play)

A wifi capable laptop running Linux with Wireshark installed (it would probably help if you have used wireshark before).

Suggested reading: www.willhackforsushi.com/books/377_eth_2e_06.pdf

An awareness of the law in your country regarding monitoring wifi. You will be intending to capture your own traffic, but you may well capture your neighbor's traffic also. That may or may not be legal - you need to know.

Wifi Analyzer will show you the channel and signal strength from your base station. You can record it as a graph. How does this vary when the Nook is on or off?

Does Wifi Analyzer work well when install on the Nook?

Set up and do some capture of your channel using wireshark on Linux. The suggested reading will walk you through the process. What do you see in terms of number of new connections, errors, throughput etc. What changes when the Nook is on or off. Is the nook behaving differently to your other hosts, when doing the same sort of work.

My guesses are that the Nook is either doing a lot of session initialisations or there are lots of collisions/errors.

When reporting back it would be useful to know what the security settings are for your channel (wifi Analyser, settings, show full securities).

Finally, I'm not going to able to fix the problem, but hopefully those that can will have more info than they have now.
[Nook Color Android Development] dparrothead1:
I would like to start off by assuring everyone that I am not insane!

I installed Beta 2 Wednesday night. All day Thur and Fri I had true SOD.

Last night I let put itself to sleep. I have not added nor deleted any apps. This afternoon I picked it up, hit the power button and the lock screen came on.....I almost dropped the Nook!!! And it still had 75% charge left.

Don't ask me to explain. I can't.:confused::D:)

Edit: would like to give a shout out to mjolner. He can't post in the dev section yet so he took time out to send me a pm with a fix suggestion. Members like this are what makes this forum so great!!!!!:thumbup:
[Nook Color Android Development] fattire:
To update on the screen recalibration thing, I got this today in PM:

Thanks svip!
[Nook Color Android Development] sisterchick:
Maybe it had something to do with the Tablet UI patch. I have a hardware key setting under settings/system.
[Nook Color Android Development] ahopper:
Yeah, the terminology was my fault; I have the earlier version (1G data/5G media). I was just trying to recall the labels on the storage activity. The sdcard itself works fine when mounted under Windows and if I revert to CM7.2, it's r/w, so pretty sure the card's OK. I must confess it's been a while since I've used this nook; I didn't recall it installing everything to the data partition, so I was wondering whether it was unable to install apps to sd due to the ro mount.
[Nook Color Android Development] krylon360:
ok I can confirm, SOD is still an issue.

Happened yesterday when I left work.

Wifi was on, and connected to my works wifi hotspot, but wasn't auth'd with it. (Needed to accept the security cert. when I got home, had an sod. Looking into if it was due to wifi hanging, or something else.

27 hrs on battery to, not bad.
[Nook Color Android Development] leapinlar:
Some apps do install to SD automatically if they can. If your card is ro, then they would install internally. That could explain why internal filled now and not before.

Did you try a different card in the Nook? I know sometimes cards can be read on the PC and not on the Nook. If others can be read, try reformatting the card with the SDFormatter program free on the web.
[Nook Color Android Development] bornagainpenguin:
I flashed the Phablet GUI restore for beta 1 and now have a context menu again. I didn't even look for the hardware keys setting, since this seems to work good enough.

Interestingly enough, now I am able to wake up the Nook with the n button again, and having some slowness and other issues with waking up from the power button. Occasionally I get the screen coming on (back light) but a black or blank screen. I wonder how many people reporting still being able to wake with the n button are running dirty installs?

NOTE: in recognition of the fact I am no longer running a stock install of beta 2 I will avoid making bug reports from here on in until I return to stock or install beta 3.
[Nook Color Android Development] jacjar1:
Beta 2

FWIW....I have found that if I disable WIFI before Nook sleeps of if I know it wont be used for some time, I do not get SOD. If I leave WIFI on I will get a black screen SOD every 5th or 6th time. For me i can live with it.
[Nook Color Android Development] EAK128:
There is an app in the market that does this pretty much, called nook screen recalibrate. And I just tried it and helped a lot. I had an older recalibration app that didn't do much, but this one definitely does.
[Nook Color Android Development] steven676:
For those having problems with their NC DoSing their wifi ...

If you're experiencing a problem where, with beta 1 or beta 2, your wifi network's performance is being degraded when your Nook Color's WLAN radio is on (if you're not sure, just try turning off wifi and seeing if the problem goes away) ... could you please try flashing the attached patch ZIP on top or your existing install and reporting whether the problems continue? (It's another update to the firmware for the wifi chip -- thanks to eyeballer for being the guinea pig on the firmware update.)