yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] I Am Marino:
I'm on 102 thinking I was immune from this SU issue but my SU is also messed up, it FC anytime I need to use it, although it's allowing me to use any apps I've previously allowed access to. Do I need to just update my SU? I'm not planning on flashing a new nightly until this batch of SU issues are fixed.
[Nook Color Android Development] Nburnes:
Try downloading su in Rom Manager. Under Download Rom > Extras > Superuser 2.3.6.3 efgh.

Then you will have to reboot to CWM and find it under clockworkmod > download > downloads.androidsu.com > superuser > Flash su-2.3.6.3-efgh-signed.zip.
[Nook Color Android Development] :
The verygreen sdcard image doesn't support CWM. Would this be something I could "fix" using Adb?
[Nook Color Android Development] Nburnes:
Install the .zip this way, straight from verygreens first post.

http://xdaforums.com/showthread.php?t=1000957

.zip is a .zip the world around mate.
[Nook Color Android Development] :
Tried this already. :)
[Nook Color Android Development] Nburnes:
Well I am out of ideas man. :(
[Nook Color Android Development] :
No worries. Thanks for trying to help. I'll probably just redo the image. Will just need to reinstall some apps since I haven't been keeping up on my backups. Oh well...the price you pay for messing with the nightlies. :D
[Nook Color Android Development] residentorca:
107 with 06/18/11 kernel running very smooth at 1.2 GHz. No SOD, deep sleep or wifi issues, and no FCs. Seems nearly perfect on mine; will be looking forward to testing USB host support. Thanks devs!
[Nook Color Android Development] vgupman:
Thanks man. Just what I was looking for.
[Nook Color Android Development] TDO:
Of course you can use CWM. Just use the right version.

I have posted an adopted version in the generic sd card image thread.
[Nook Color Android Development] oldman_58:
Constant SOD

I am getting SOD with n107 and 6/18 kernel.

As last_kmsg does not write on a locked up system, I am attaching a detailed send-log after reboot, probably not much good..

Is there something I can do to force a last_kmsg when system is locked?
[Nook Color Android Development] n0xx187:
Im also getting SOD with n107 and 6/18 kernel. and when I connect my BT apple magic mouse it freeze's my nook and I have to hard power off
[Nook Color Android Development] xdajunkman:
If your nook is locking up or freezing, then that is not a SOD. If it works fine, then either powers off by itself because of idle time or is powered off by you, then wont wake back up without long-pressing the power button and rebooting, THAT is a sleep of death. If your screen is still turned on but your device is unresponsive, that is a different problem.
[Nook Color Android Development] I Am Marino:
I noticed some people are mixing the two.

I, for sure, I have SOD issues at the moment.
[Nook Color Android Development] xdajunkman:
What are you currently running? As of your last post you were on nightly 102. I went to nightly 107 last night and used the crap out of my Nook last night trying to get it to lock or SOD. Have no SOD, FC, or lockups so far. I have not tried any BT connections or anything else fancy, however.
[Nook Color Android Development] chisleu:
BT Wiimotes are working for me. My BT keyboard died... POS Zoom brand keyboard.
[Nook Color Android Development] oldman_58:
I have asked the question before, if SOD really does "Lock" the system that only a hard boot can restore, there is no way to get a last_kmsg file,

I have to long press the power button for a count of 10 then restart.

I never have a last_kmsg file. So maybe a clearer explanation of SOD would assist us in determining the issue...

This is happening on 2 Nooks, a few nightlies ago only 1 was having that issue, now both seem to have the issue.
[Nook Color Android Development] ShutterPeep:
Went to 108 as I had the SoD even at 40% battery level with nightly 107. Monitoring now.
[Nook Color Android Development] I Am Marino:
I'm on 103 for sure, I got my nightlies mixed up, I was updating daily but I stopped here once my deep sleep returned, and with the issues people were having with SU beyond 103, I'm waiting for an all go on newer ones before I jump to a new one.

I haven't had SOD since last night sometime so a full day without it, holding my breath.
[Nook Color Android Development] DizzyDen:
Go to 108... the only version that had su left out was 106... all is well again in the CM7 world.
[Nook Color Android Development] ular_king:
I have SOD on 107 with latest OC kernel at 80% battery...have to plug in to power in order to turn on...
[Nook Color Android Development] oldman_58:
What you are describing is not SOD it sounds more like PBD, Premature Battery Death
[Nook Color Android Development] capnblackleg:
Can anyone tell me why I always end up losing deep sleep? I only seem to have it for the first charge after a new flash.

I could live with SODs and PBDs but losing deep sleep sucks.
[Nook Color Android Development] dalingrin:
Telling me your symptom without any additional information is pointless.

If you are going to post about a problem please

- give logs if possible(dmesg, last_kmsg, logcat)

- describe your usage leading up to the problem

- list some installed apps and widgets

The more info the better.

Saying, "my wifi doesn't work right," or, "I have SOD," does nothing to help your problem or anyone else's.
[Nook Color Android Development] dvdivx:
It seems the sleep problem would be pretty easy to spot if devs owned nooks. Just let it sit awhile not plugged into power and it will enter deep sleep. Once it does you have to restart it. That's on 105 w/ 6/18 OC Kernel. I'll try the next nightly (109) with and without the OC kernel to see if it does it again after a complete wipe with no apps installed other than market and Gmail. (from the 6/13 gapps)
[Nook Color Android Development] fattire:
Ooohhhhhh. I guess the devs should buy nooks then.
[Nook Color Android Development] dalingrin:
Nope. Never happened to me or anyone else working on the nook. This is why I'm harping about good bug reports. I can't fix a problem that I don't have unless I get good information from users that do.
[Nook Color Android Development] oldman_58:
Thank you both, that is what I needed to get you the info you may need.

With that said, I found in N108 that WiFi had been defaulted to always on, I set back to off when screen off about 10 hours ago no SOD so far, very light use.

Widgets running

Stocks

Mail (Android Mail)

Battery Left

Weather

Background programs:

cpuspy

Cache Cleaner

Not plugged into power last night battery remains 42% on both Nooks, not planning on charging until power drops below 10%

I am attaching 4 last_ksmg files for 2 Nooks, dates 6/16 and 6/21 Hope this helps.

=========================================

N108 6/18 kernel

After setting Wifi to screen off I am happy to report both Nooks are sleeping and remain at 41% battery left.... Not too shabby.
[Nook Color Android Development] DizzyDen:
Most of the dev's do own them... That's why they hang out in the nook forums. I have been as fortunate as they have in only ever having 1 SOD. Imagine tying to troubleshoot an issue you can't see or reproduce. Also remember all the combinations available noe... different uImages, kernels, run off EMMC or uSD... and you'll understand how complicated it can be bug tracking.
[Nook Color Android Development] n0c:
Oldman: where do you make that wifi setting??
[Nook Color Android Development] oldman_58:
Go to > Settings > Wireless & Networks > Wi-Fi Settings

Press the menu key

select Advanced

open Wi-Fi sleep policy

and select

When screen turns off

Are you are set.
[Nook Color Android Development] n0c:
Thanks. Interestingly mine was set to screen off. (N108) here, with 6/18 oc kern.
[Nook Color Android Development] 12paq:
On log reports..

Yeah, thanks old man (that sounds funny, I'm 47. Lol), reporting what your wifi sleep settings are, what nightly you're on and what kernel date you're using is important for devs too. While reading mutiple reports on sod I have often wondered if some don't even know were the wifi sleep policy is. It is quite hidden, I guess..
[Nook Color Android Development] capnblackleg:
That does help and I thank you for it. I guess I didn't bother with all that because I haven't seen anyone talking about this particular issue. There's no error or anything that jumps out at me that is the cause of it, unless something happens on the charger.

Anyways, if it happens again I'll post all the particulars, I was more interested to see if anyone else lost the ability to deep sleep. I flashed 108 last night and so far so good, but I'll use it this evening and see for sure.
[Nook Color Android Development] MedLine:
RIPOFF alert: looks suspiciously like viewsonic gtab running cm7 with tablet tweaks: http://biotx.net/products/wellaware/wellaware-ii
[Nook Color Android Development] 12paq:
No worries.

Not directed at any one post. :)
[Nook Color Android Development] boxcar8028:
yesterday I came home to find my nook had a SOD. the kind of SOD were I couldn't hear any beep beep from the speaker and had to reboot. I checked the battery stats to find that the nook was sleeping fine most of the day but at the end had a panic of some sort and had a sudden mass lost of battery life. see pic1. cm7 n107

last night before I went to sleep I turned off wifi and background data to see how the nook would sleep over night. see pic2. to my surprise I found that it did deep sleep all night. a first for my nook. cm7 n108

also, thank you 12paq, for the instructions on how to pull and find logs for the devs to check out. I believe most users do sincerely want to help in squashing bugs but do not know how. anyway, I did found a "last_ Kmsg" log in the proc folder. see last_kmsg

cm7 n108 6/18 OC kernel 300/600/800/1100/1200 conservative
[Nook Color Android Development] sinanju:
I don't get why that's a ripoff... Should they have built a tablet and OS from scratch? Perhaps they should mine the ore and refine the oil to build the components?

As long as they are complying with licenses, what's the problem?
[Nook Color Android Development] pmilford:
Wifi sleep screen off setting not sticking

HI,

I am on Nightly 107, 6/18 OC kernel.

When I set my Nook to 'sleep when screen turns off', then check the setting

a while later, it is set to sleep 'never'

Looking at battery use, it reports WiFi on most of the time.

I had seen something like this on N94, but I was getting many SOD, so I was

thinking the reboots may have been changing the setting.

Anyone else seeing the 'sleep when screen turns off' not sticking?

I'm guessing it is either a 'bug' in CM7 or one of my applications

over-riding the CM7 setting. The only other settings app that I am

using regularly is 'Quick settings', but there are many many applications

that update data in the background.

I am getting lots of deep sleep reported by CPUSpy and my current uptime is

42 hours with 22% battery life left.

Attached is "alogcat" output. I checked the wifi sleep state setting ("on

screen off") turned off the screen and waited a while (30 mins?) then

turned on screen, checked wifi sleep state, it was set to "never". I don't

understand the log well enough, but perhaps this is where the issue is??

"I/ActivityManager( 1110): Displayed com.android.settings/.wifi.AdvancedSettings: +532ms

W/asset ( 1178): deep redirect failure from 0x01030068 => 0x0a080004, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000

W/asset ( 1178): deep redirect failure from 0x01030067 => 0x0a080003, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000

W/asset ( 1178): deep redirect failure from 0x01030067 => 0x0a080003, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000"

Peter
[Nook Color Android Development] Divine_Madcat:
That; and didn't Mad say that the TT wasn't just for the nook, but for a few devices anyway? I didn't think this was news.....
[Nook Color Android Development] rhester72:
Well, in fairness, maybe they should stop Pandora before taking screenshots for commercial advertising *LOL*

Rodney
[Nook Color Android Development] chisleu:
Yes... Less "ripoff alert" and more "awesome alert"
[Nook Color Android Development] MedLine:
its ripoff in same way that paying $500 for 0.5ml of research enzymes or antibodies that cost $20 to produce is a ripoff. here they're taking a $300 device adding $5 worth of plastic and basically a $0.99 app and selling it for $1200, but never mentioning CM7 in process.

guess thats message here, CM7 = awesome.
[Nook Color Android Development] Awats:
To be fair, that $5 worth of plastics could take $100k in tools to make. But I am not looking to be fair right now.
[Nook Color Android Development] sinanju:
But they're adhering to licenses, so the problem is.... "I didn't think of that first"

Got it...
[Nook Color Android Development] sinanju:
licenses liabilities lawyers

accuracy accreditation anoraks
[Nook Color Android Development] Snyperx:
I am not sure if it is just me or the build. I am on build 110 and am unable to drag app icons on my scree. I also can not do a long touch to bring up the Wallpaper/widget menu. Any idea? I might have changed a setting some place and not realized it as well. Thanks.
[Nook Color Android Development] rhester72:
On 110 myself, no such issue here. Don't even know what you could do to cause that intentionally.

SD or eMMC? What launcher?

Rodney
[Nook Color Android Development] oldman_58:
Did you lock your desktop in CM settings?
[Nook Color Android Development] ziggy34:
from the home screen, press menu

See if lock desktop is there, might have to press the more option.
[Nook Color Android Development] Snyperx:
Yup, that was it. Thanks!!
[Nook Color Android Development] Minjin:
Does anyone know if the Google Reader issue will ever be fixed? CAN it be fixed? That's the only real issue I have with CM7. I've only had the fall asleep and never wake up issue once.
[Nook Color Android Development] dalingrin:
Because this is a bug in the app, there is nothing I can do.

I hate to always respond like this but have you tried other reader apps? Or better yet, have you tried the Google Reader mobile page? I personally find the mobile page better than ANY app. For me, having the ability to open full articles in a background tab and not having to switch apps just to read an article is enough to use the mobile website over any app.

If you insist on an app then you should really try D7 Google Reader.

In my experience the official Google Reader app is not nearly as good as the mobile website. Perhaps my usage style is different than most users.
[Nook Color Android Development] domin8:
You should try greader, or pulse if you like a little eye candy now that you can import Google reader sources
[Nook Color Android Development] wumpus11:
I use LCD Density changer to dynamically switch from 161 to 160 specifically for Google Reader. For a working market, I change it back.
[Nook Color Android Development] paleh0rse:
+1 for gReader.
[Nook Color Android Development] Miltani:
Just upgraded to nightlies 108, I realized I have a problem when i put my nook into standby. Upon resuming my nook, my wifi doesn't connect back automatically. I have to off and on it again for it to appear. Is this a bug? I thought that it was solved many nightlies ago?
[Nook Color Android Development] Awats:
I've noticed since builds in 80s that the wifi comes back on by itself after about 20 seconds. I figured that's is normal.
[Nook Color Android Development] Hindle1225:
I second that!
[Nook Color Android Development] Awats:
I'm still getting a random pop or click in the headphones. In the speaker it sounds more like a cut out. I've enabled/disabled everything I can think it and it still happens. I wouldn't dare put headphones on. I wonder if it's a random discharge of the backlight circuit or alike.
[Nook Color Android Development] wallsg:
WiFi sleep policy?

Settings->Wireless and network->Wi-Fi settings

Menu->Advanced-Wi-Fi sleep policy

If the sleep policy is "when screen turns off" then maybe the connection has to be re-established. I could be wrong because I'm just guessin'.

I've noticed on my Nook 7.0.3 that it seems to defaulted to "when screen turns off" while on my rooted stock Captivate it seems to be defaulted to "never".
[Nook Color Android Development] wallsg:
Yeah. I tried switching to the official Google app a few months back and quickly switched back. There's no comparison.
[Nook Color Android Development] Miltani:
does that mean i have to reflash my nightlies again? cause my wifi doesn't come back on by itself
[Nook Color Android Development] oldman_58:
Some software will make that change, doubletwist music player forces WiFi always on...
[Nook Color Android Development] greenzee:
I've been running nightlies since about #87, just installed #110 yesterday, reflashed Gapps and also Dal's OC kernel (for the first time). I notice that my wifi has a difficult time connecting to WPA encrypted wireless for some reason. WEP, no issue. I can see the wifi cycling (and never connecting) when I attempt to connect to my WPA connection. If I choose WEP, it locks on quickly.

EDIT: I just installed #111, along with Gapps and Dal's OC, and now I have no wifi connectivity at all. Hmmm.

Any ideas?
[Nook Color Android Development] jay_ntwr:
I'm still having the endless WiFi loop in 108. If I forget all my WiFi connections then reconnect, it starts working again.

What I did find interesting (and pretty much reproducible) is that it has something to do with having more than one WiFi connection (I think). WiFi seems stable until I have three saved connections and do a re-boot. Then it's broken every time. Not sure if that helps the developers or not, but that's what I think it is. If I have one connection and re-boot, it seems solid. I don't have a dead on set of steps, but this is sort of what I've been noticing has been breaking it.
[Nook Color Android Development] matalo:
No ideas but I have same problem. Same builds as you.
[Nook Color Android Development] daugh016:
Same exact situation here. If I forget them all, I get WiFi back. Else, i can't connect at all to WiFi.
[Nook Color Android Development] rhester72:
I'm not sure that's a factor.

I'm on 111, but ever since the wifi driver fix (which has mysteriously disappeared from the encore changelog, so I don't know precisely which revision it was), I've been stable as a rock under a wide variety of wireless circumstances, with 7 SSIDs stored, 4 of which are used on a regular/daily basis (and 2 of those are encrypted, both with WPA2/AES - one is wireless G, the other is N).

Rodney
[Nook Color Android Development] Nburnes:
Mysteriously disappeared or more likely you passed it up right under cm_encore_full-106.zip. Update wl1271 firmware, module and kernel (android_device_bn_encore)
[Nook Color Android Development] rhester72:
Wow...I am blind. *laughs* Thanks.

Rodney
[Nook Color Android Development] frankusb:
Do you know why Google Reader works in stock 1.1? I think it has an LCD density of 169. Different version of Google Reader?

I personally can't do without Google Reader, I've tried every other reader that I can find and Google Reader is the best for my usage.

Frank
[Nook Color Android Development] SCWells72:
Not sure why it works with stock, but I've had the same experience you have where I can't get it to work under CM7 and alternate ROMs. I use gReader and have been VERY happy with it. Have you tried that one? If so, what does Google Reader have that gReader doesn't?
[Nook Color Android Development] khaytsus:
See my signature.. Look on your router and see if AES is enabled on WPA, or if you're using WPA2. Try WPA TKIP-only and see if your issue goes away.

AES was a huge problem for the 2.6.29 kernel, but still can be a bit quirky on 2.6.32.
[Nook Color Android Development] frankusb:
Nevermind.

Frank
[Nook Color Android Development] gudism:
PBD

has the PBD issue been resolved? I thought I saw somewhere a fix was in the latest nightlies, and I havent seen anyone talk of this, and on the thread for PBD nothing has been commented for 3 weeks. So I figured it must be fixed.

I only ask as I am still getting PBD on n108 with 0618 kernal. I get to 15%, receive 'plug in reminder' than moments later off she goes.

Have had this at the same % for the last 3 nightlies I have flashed (95,101,108)

Has it been fixed or am I a little unique?
[Nook Color Android Development] Calla969:
Had a strange problem last night. I'm on the 6/20/2011 (110?) nightly with the 6/18/11 OC. I plugged my Nook in last night to charge it and when I woke up this morning, it was at 25%, but the light was green. I went to move the charger to another outlet and I plugged it into the Nook first and the light on the charger came on and was green with it unplugged from the wall. I'm not sure if that's normal or not. I plugged the charger into the wall and checked the charging status. The unit was still discharging despite being plugged in. I rebooted and the light changed to orange and it began charging normally again.

Also, yesterday, I had been using it a lot and the battery was down to about 70%. I wanted to charge it up a little because I knew I would be using it a lot later, so I plugged it into the 12v car charger for my OG Droid. As soon as I plugged it in, the battery percentage went right to 100%. I unplugged it and it seemed to discharge at a normal level as if it was actually fully charged. I use this charger frequently and have never seen any strange behavior before. I have had absolutely no other problems.

Has anyone else seen anything like this?
[Nook Color Android Development] newellj79:
Same thing happens to me. I finally realized I had USB host on, doh! Make sure u don't.
[Nook Color Android Development] jmak10:
I had a SOD last night after configuring a new WiFi WPA network. Sorry no log files but when I finally got it to reboot CPU SPY displayed all small negative numbers (-2, -4, -5, etc) for all the states. Note that I also had a hard time connecting to the new network before the SOD. Running n110 and dal's 0618 OC kernel. If this info isn't useful just ignore it.

Thanks,

jmak10
[Nook Color Android Development] Calla969:
How do I check? I have never messed with USB Host.
[Nook Color Android Development] newellj79:
Oh, if u have never turned it on then its something else. U wouldn't have by accident. But its in the nook tweaks app or the USB host app from the USB host thread.
[Nook Color Android Development] technicalsquash:
Just had a SOD, nightly 106, not overclocked. /proc/last_kmsg appears to be corrupt, but i'm attaching it anyway. Device was locked, I hit the power button to look at the time and battery level, let it fall back to sleep, 10 minutes later it was frozen. adb devices said it was in an offline state.
[Nook Color Android Development] thejron:
CM7 stable 7.03 seems sluggish on this thing. What kernel are you all using?
[Nook Color Android Development] Deaks2:
I still have this issue as well. However, I get down to ~7%.
[Nook Color Android Development] oldman_58:
I am amazed at how well this has been performing, N112 and 618 kernel..

With very light use I get 2 days out of both of my nooks...

No SOD or PBD since I think it was N108..

Both deep sleep,

When I load the new Nightly I always:

Backup

Clear cache

Load ROM

Load OC Kernel

Clear Dalvik

Fix permissions

reboot...
[Nook Color Android Development] gudism:
Same order I follow, except fixing permissions, might try that next time.

I also flash when it is fully charged and or still on the charger, and clear battery stats after flashing the ROM.

Would you guys recommend flashing when fully charged or not?

Edit. So I just flashed following the list above to 112, will see if PBD remains
[Nook Color Android Development] newellj79:
I know screen sensitivity issues have been addressed since the start of development, but no matter what I do I can't improve responsiveness on the left edge of the screen in portrait mode. When pressing the 1 key I often have to press it 10 times to get it work. And its damn near impossible to use the batch check boxes in gmail. None of the recalibration apps help. N e thoughts?