yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Cotys:
Cant flash or wipe

I've been running 7.1.0 RCO for a while and it has been working great. I let my Nook go completely battery dead over the weekend. After charging it again I had all type of problems with widgets not loading and getting a lot of FCs and occasional reboot loops.

I decided to restore from backup in CWM, it failed. I thought I might just go back to the last CM stable. I did the flash and it booted right back into 7.1.0. I did a wipe data / factory reset, wipe cache, wide davlik. After rebooting it loaded right back into 7.1.0 with all data intact. I'm running CWM 3.0.2.8. I loaded my recovery image CWM (3.0.1.0) and did the same drill. It booted right back into 7.1.0 with all data still in place.

I stepped through each of the mounts and storage options formatting everything. All completed except for System, it would run and hang. After a restart, everything is still there.

Not sure what to do here. It acts like the memory is locked.

Also tried to flash the latest CWM in Rom Manager, it appeared to work. When booting into recovery the old 3.0.2.8 is there.
[Nook Color Android Development] khaytsus:
Anyone else noticed that they're having to reflash Google Apps after every flash now? I updated to 91 and had some apps broken, flashing Google Apps fixed them. Updated to 94 today, same thing.

I've also started flashing with Rom Manager instead of doing it directly in Clockwork, don't know if that'd make any difference.

Anyone else seeing this? I've never had to reflash Google Apps before, but the last two flashes I have..
[Nook Color Android Development] paleh0rse:
I'm using internal CWM (3.0.28) to do all of my flashing, and I have not had to flash gapps again with any recent nightly.
[Nook Color Android Development] derekr:
@khaytsus

No problem for me all the way up to 94... Using CWM 3.0.2.8.
[Nook Color Android Development] Divine_Madcat:
Meh.. call me odd, but i use my tablet, and hate wiping data when i don't have to. Given that the data has nothing to do with the kernel change, i still feel most users will be fine without such a setback.
[Nook Color Android Development] mr_fosi:
+1

Q) What's better than using Titanium to easily restore my apps+data?

A) Not having to restore them at all.
[Nook Color Android Development] frankusb:
Does anyone know if the source for the above change is available anywhere? I've checked dalingrin's kernel source and don't see it there yet he checked the binary in to CM7.

thanks,

Frank
[Nook Color Android Development] boxcar8028:
n94 I see "Wifi: Minor change in SDIO release behavior" in the change log. does anyone know if this is something to do with SOD. does the SDIO release behavior have something with the nook waking up

Im starting to think SOD has something to do with the recovery of the screen after a sleep. I mean the system is up and running I can hear the beep sound when I press the volume buttons and I the hear the notification sound so I know the system is up and running it only the screen that is not. the waking up of the screen may have some kind of conflict with the wifi or something else waking up at the same time. just my guess. not sure.

cm7 stock n93
[Nook Color Android Development] newellj79:
I just used emmc cwm 3.2.0.1 to flash nightly 94 and the 5/23 oc kernel. No problems here. Have never had to reflash the gapps. When making the switch to .32 I did a complete wipe and then used TB to restore apps only. I have had way less problems than most, maybe that is why.
[Nook Color Android Development] Ophbalance:
I found this to always be the case when trying to flash by way of using CWM on the nook interface, eg I tell CWM in the GUI to grab the update and flash it. However, if I manually reboot to CWM and then install the file I download from the mirror, it doesn't require reflashing gapps.
[Nook Color Android Development] ADude:
You win the Award !

The Award for most off-topic post of 2011 ! :cool: :cool: :cool:

( I think the earliest that this award has been given. )
[Nook Color Android Development] boxcar8028:
I've always wondered about Tibu, restore data+apps vs apps only. so its a bad idea to restore data. is that because of old bad data can be transfer to your fresh flash?
[Nook Color Android Development] danvee:
I found that a reboot took care of that...
[Nook Color Android Development] khaytsus:
That sells it then, next time I'm going to flash "manually" from CWM vs Rom Manager and see what happens. If it doesn't happen, I wonder what the heck Rom Manager is changing?

Doesn't for me, I tried it last night going to 93 and today going to 94. Perhaps you're thinking of Apps2SD issues?
[Nook Color Android Development] Ronin3178:
I always notice that after a d/l in ROM Manager, it's only options are to "Wipe Data/Cache" and "Wipe Davlik", so I back out after d/l and then boot into Recovery and manually pick zip. ROM Manager d/ls to sdcard/cyanogen/clockworkmod/get/ or something like that.
[Nook Color Android Development] danvee:
I just updated from r93 to r94 a few minutes ago. Experiencing the missing app syndrome, I just rebooted and all apps were back and functional.

Luckily, I've not had any issues with Apps2SD either.

Probably just dumb luck........:rolleyes:
[Nook Color Android Development] junkrobot:
On average, how much battery loss should we be seeing per hour on deep sleep?
[Nook Color Android Development] J-ROCK:
Is anybody else having issues with ADW launcher ex with cm7? Mine keeps freezing up on me and I never had this issue with the regular ADW.
[Nook Color Android Development] paleh0rse:
ADW EX has been rock solid for me -- both with and without OC kernels.
[Nook Color Android Development] J-ROCK:
Thats strange must be something else then!
[Nook Color Android Development] chisleu:
like none. .1%?
[Nook Color Android Development] boxcar8028:
it maybe a widget or a theme. last week after a reboot because of SOD my nook had a bad case of FCs with ADW trying to load my widgets. after trying lots of different things I finally got it back up and running. after trial and error I figured out it was the theme that I was using in fancy widgets pro. I uninstall and re-download it and all is well again. so be careful, its not just the widget. make sure to also check any themes you may have loaded.
[Nook Color Android Development] junkrobot:
Well, darn. I did a complete wipe and fresh install of nightly 93 and I guess I don't have any deep sleep after all.
[Nook Color Android Development] Nburnes:
Should check quickly with this application.

CPU Spy
[Nook Color Android Development] junkrobot:
I'll give this a try. Is there any specific procedure to follow/any risks involved? Sorry if these are silly questions. I certainly appreciate the assistance.
[Nook Color Android Development] Nburnes:
Nope. Open up the app, look at your times in each state.
[Nook Color Android Development] junkrobot:
Deep sleep is listed under unused processes. No good, I assume.
[Nook Color Android Development] Nburnes:
How long have you been messing with it? Should leave it sit for 15 to 30 minutes and check again.
[Nook Color Android Development] junkrobot:
Will do and report back later on. Thanks again!
[Nook Color Android Development] J-ROCK:
Yes I was thinking , maybe it is the theme! Thanks for the heads up, I am also using Fancy widgets. Ill give it a try.
[Nook Color Android Development] MadMikeSS:
Forgive my asking this, but how do you put your NC into deep sleep? Is it just when you hit the power button and turn off the screen? Or is there a setting somewhere?
[Nook Color Android Development] Nburnes:
When you hit the power button and turn of the screen. It is obviously not instant, but should take only a couple minutes.

No need to ask for forgiveness, a question is a question.
[Nook Color Android Development] junkrobot:
Well, after almost and hour of screen off time, CPU Spy still says deep sleep is unused. Is there any way to diagnose what the issue might be at this point?
[Nook Color Android Development] Gin1212:
No sadly there is not, unfortunately it will probably require us the users to report our uses until they can find a common program or configuration that leads to this. As there are others who haven't even had PBD or SOD issues, let alone deep sleep issues.
[Nook Color Android Development] junkrobot:
Fair. So, something is essentially interrupting its process? It might be Droid Wall, in my case.
[Nook Color Android Development] Gin1212:
Not sure if it is something, I'm only guessing since some users are reporting it to work. I will say however I don't have droid wall.
[Nook Color Android Development] junkrobot:
I fixed permissions, shut down completely, powered back on, and now deep sleep is working again, according to CPU Spy. So, that may help others!
[Nook Color Android Development] bradputt:
I flashed N94 and lost my WiFi connectivity.

Had to flash back to N91.

Anyone having the same problem as me
[Nook Color Android Development] paleh0rse:
Try rebooting your router instead... that's what fixes mine every time it goes into the scanning->connecting->disconnecting cycle under wifi options...
[Nook Color Android Development] Gin1212:
You can also long hold press on the network and forget it, I find that helps a lot.
[Nook Color Android Development] Gin1212:
Wish that had fixed it for me... Fixed permissions in both Rom Manager and CWM, hard rebooted after each time, nothin'.
[Nook Color Android Development] bekyndnunwind:
If my nook isn't deep sleeping (happens sometimes after I charge) all I have to do is unplug and restart.

As most of you know, the nook will NOT go into deep sleep when its plugged in...
[Nook Color Android Development] junkrobot:
Strange. According to CPU Spy my NC deep sleeps while plugged into the wall charger.
[Nook Color Android Development] quikt:
Deep sleep working here. moved from n87 to n94. Wiped dalvik and cache. Left data alone. Latest oc kernel. Draining the battery as i type.
[Nook Color Android Development] skwalas:
Well, I'm one who gets instant deep sleep with default 94, and never with the 0523 kernel. I've flashed both ways several times today with the same results every time.

Either something in the 0523 kernel blocks or delays deep sleep, or else its interacting with something inadvertently.
[Nook Color Android Development] bigbob23:
I hadn't seen deep sleep with either 93 or 94 with the 0523 kernel. After reflashing 94 alone, it came right back.
[Nook Color Android Development] greenmky:
I just went from n87/523 OC to 94/53 OC and I've lost deep sleep as well.

Tried fixing permissions and power off/on...no luck. :( Maybe I should have stayed on 87...
[Nook Color Android Development] Gin1212:
Got this PM from Bobshaw, thought I would share with everyone. I've already tried this and though it didn't work for me, I thought I would share anyways.
[Nook Color Android Development] chisleu:
I think we run the risk of starting some false positives on solutions here. We should note that we don't yet know exactly what will fix it. It may be something we aren't thinking about.

Well, I cleared cache and davlic. It didn't seem to work. I turned off wifi and put it to sleep and nothing. Then I turned wifi on and rebooted and just left it alone and it went to sleep. 15 hours of deep sleep.

No clue what happened. It could have been anything or nothing.
[Nook Color Android Development] greenmky:
Thanks chisleu, that did it for me also.

Turned wi-fi on. Rebooted. Wi-fi was disabled again (this has been a bit buggy for me). Turned on wi-fi. Turned off screen. Now I've got deep sleep again.
[Nook Color Android Development] pavlos46:
Retrackted

Pavlos
[Nook Color Android Development] :
Argh. Pptp and l2tp pptp vpn still cause system lockups for me after they connect. Anyone else having these issues with the nightlies?

Sent from my Nook Color
[Nook Color Android Development] seth.i.simmons:
Is anyone else having issues getting the status bar brightness to work?? For the life of me, I can't seem to get it to work at all... I've toggled the brightness control multiple times, but no matter which way or how fast I slide or anything, it won't change the brightness. Any help would be awesome!
[Nook Color Android Development] rhester72:
Works for me. Make sure to start with touching the 'empty' space in the middle before sliding left (darker) or right (brighter). You should see the "notification bar" appear just above the status bar on initial touch before you swipe.

Rodney
[Nook Color Android Development] newellj79:
Does not work for me either. Both n94 and n95.
[Nook Color Android Development] skwalas:
See the update in the changelog for 95. You are not alone. If brightness is set to auto (presumably in the power Widgets) the the statusbar slider won't work. You need to shut off the auto setting.
[Nook Color Android Development] seth.i.simmons:
Just tried it again, and still a no go. I've been doin what you said from the beginning, but it just won't adjust. Tried it in N91 and up. (I think N91 is where it started, can't remember for sure though...)
[Nook Color Android Development] seth.i.simmons:
Yep, saw that, but I never use auto brightness, since as far as I know, it doesn't even work on our Nooks. I checked just to be sure iit wasn't on when I saw that change, but its not on auto, and still doesn't work :/

Where do I find the auto brightness setting besides toggling it through Widgetsoid??
[Nook Color Android Development] lyam23:
brightness sliding does work for me on n94, however it's a bit glitchy. I have to hold my finger on the notification bar for a second, then I slide to the right for a bit, then I slide to the left for a centimeter or so, then it becomes immediately responsive from there-on out.
[Nook Color Android Development] Gin1212:
Had a similar situation Chisleu, except I didn't do anything special... I didn't reboot it, I didn't toggle wifi on and off... I just read a book till I got tired and put it to sleep when my eyes got to blurry to read the book...

Woke up this morning with deep sleep... =\
[Nook Color Android Development] Nanan00:
With the last major build 7.0.3 and nightly hence, the hide menu bar down arrows always show, hitting them hides the bar with no way to get it back without rebooting the nook. I set the up volume arrow to unhide the bar but it does not seem to function.

Jumped to Nightly 95 the other day, charged to full, played Pew Pew for about 2 hours and read for 4 hr, battery showed at 93% battery, let nook do its sleep thing over night, checked in the morning and battery was at 93%, let it sleep all day till my bed time reading, still showed 93%, checked battery this morning before work, showed at 92%.
[Nook Color Android Development] khaytsus:
The way I've gotten the status bar brightness to work for me is to touch where the status notification icons are.. Wifi, etc. Wait half a second or so and the notification bar header comes up. Then slide my finger along the status bar (NOT the notification bar or header). Wherever your finger is is how the brightness is set. Sliding right isn't "making it higher", rather if your finger is in the middle, it's at 50%, etc.

It took me a few minutes to figure it out, but I can do it consistently now. Can't really do it fast (have to kind of do it and wait a bit for it to start changing) but it does work.
[Nook Color Android Development] ziggy34:
thanks for that, it does work
[Nook Color Android Development] seth.i.simmons:
It's kinda touch and go, but it does seem to work for me, just a little trouble with it sometimes working and sometimes not. Thanks for the help!
[Nook Color Android Development] :
Anyone else get random skips on music playback? Doesn't matter what app I use. Running latest nightly and no oc yet. Streaming is fine, only local playback suffers. Nothing in logs.
[Nook Color Android Development] ianPhillips1:
Do you have back checked as an option under your extended power menu? Its an option as a failsafe.
[Nook Color Android Development] Colchiro:
Airplane mode bug? :D

Install Android Assistant, open it, tap "tools" at the top, then tap the airplane icon on bottom. Now you're fixed.
[Nook Color Android Development] xdajunkman:
Just thought to add my experience.

I was running 7.0.3 stable, and have been holding out for 7.1.0 stable, but got impatient so decided to flash nightly 94. I have been flashing over previous installs since the nightly somewhere in the 20's, so decided to clear the decks and start over. Here is what I did:

1. Booted with CWR SD card

2. Mounted and formatted system, data, cache

3. Applied repartition flashable zip to give me a 2gb data partition, as per the instructions here: http://xdaforums.com/showthread.php?t=1094371

4. Rebooted as required after step #3

5. Applied reformat flashable zip from the same thread as #3

6. Rebooted to SD card CWR for good measure

7. Flashed to complete stock 1.2, including wiping CWR from recovery partition as per instructions here: http://xdaforums.com/showthread.php?t=914690

8. Rebooted to SD card CWR

9. Cleared Dalvik cache, reboot to CWR

10. Flashed nightly #94

11. Flashed gapps-gb-20110503-signed.zip

12. Flashed dalingrin's OC kernel from 5/23

13. Cleared Dalvik cache, reboot to CWR

13. Unmount and remove SD card, reboot to nightly #94 goodness.

The reason I go into such detail is that I have been running this since yesterday night and alternating between running it hard and letting it try and sleep all day today. I have done multiple reboots (just to make sure it remains stable...not because there were any problems), and have had the wifi on sometimes, off sometimes when I shut it down. I ran the battery all the way down to 2% this morning - got the 15% warning and no unwanted shutdown. Charged it back up to 100% without any issues. All my apps work flawlessly without any FC, including Netflix. No SOD, plenty of deep sleep according to CPUSpy. No PBD.

I don't know if what I did led me to the magic sweet spot, but I have none of the issues that run rampant through this thread. Then again, it is still early and maybe I will start having problems in the coming days. I will report back if things fall apart.
[Nook Color Android Development] Gin1212:
Not to scare you or anything, but most people do have deep sleep initially, but after a while of running these nightlies, it seems to disappear.

Not only that, the PBD issue stemmed from earlier nightlies and was just now fixed in N91, so most of the PBD issues now stem from the battery needing to run a few cycles before fully being restored/calibrated correctly.
[Nook Color Android Development] khaytsus:
Complete nonsense. Next?
[Nook Color Android Development] rhester72:
Yes! Alarms are also broken.

Rodney
[Nook Color Android Development] Gin1212:
Bigfoot exist... He is very real.
[Nook Color Android Development] clamder:
i get this too...
[Nook Color Android Development] TJNooker:
I lost deep sleep on n94 + OC 5/23. Before I could identify which kernel had caused the issue, n95 was out.

I flashed n95 alone and ran that for an hour. Deep sleep was back. After flashing OC 5/23, deep sleep still worked.
[Nook Color Android Development] chisleu:
no it's not.

We don't know what is causing it. It can come and go without any changes to anything done intentionally. (just waking it up, and putting it to sleep. sometimes it will sleep for me. sometimes it won't.)
[Nook Color Android Development] greenmky:
Thanks. These seems to have helped. I noticed lately that wi-fi wasn't enabled upon reboot.

I don't know. It's not LOST per se. It seems like it just temporarily gets lost.

BTW I lost my deep sleep again after a reboot earlier. Turning on wi-fi and then turning off the display brought back sleep again. Maybe wi-fi related somehow...?
[Nook Color Android Development] rhester72:
After several reboots resetting the DPI and manufacturer back to CM7 defaults...music playback no longer stutters, though alarms are still silent. Oddly, when I restored my modified build.prop, music playback is *still* OK, so the stuttering appears to be clearable somehow.

Rodney
[Nook Color Android Development] chisleu:
Yeah that idea has been tossed around a bit. It seemed to be linked to wifi and the wifi sleep policy, but I think I had some experiences counter to that.

Right now my battery is draining super fast for some reason (the percentage displayed.) It has dropped from 100% to 90% in 10 minutes with only watching a couple minutes of video and changing the wave launcher settings a few times. (wave launcher is sweet. check it out.)
[Nook Color Android Development] khaytsus:
I agree that Deep Sleep does sometimes not happen, but his post implied that over Nightly upgrades caused it, which is nonsense. I've updated nightlies since right after 7.0.3 and always had deep sleep. I don't use the overclock kernel, some folks seem to attribute it to that but I'm not really convinced of that either.

Various Android apps have problems with wakelocks, particularly Facebook has has historical issues with holding one forever, I suspect it's more of an app problem than a build or kernel problem.
[Nook Color Android Development] odub303:
It is definitely not an app problem. For me, the problem is ALWAYS triggered by flashing the OC kernel. Not once have I lost deep sleep while running a stock nightly.
[Nook Color Android Development] oldman_58:
Fix Permission

maybe a permissions issue on the OC kernel, each time I update to a new nightly then add the OC kernel

No deep sleep

Run Permissions

and then deep sleep works,

This was the case for the last 2 nightlies..
[Nook Color Android Development] HarleyChick:
Maybe I'm just one of the lucky ones. I've NEVER had a problem with SOD, battery drainage, or Deep Sleep. I've been running nightlies since I rooted my NC months ago. Currently on n95 with 052311 kernal.

There's been a lot of speculation about what is causing these various problems for users, including whether or not wifi is part of the problem. I don't have any answers, but I can say that I always turn off my wifi when I'm not using my NC - its just a habit for me. ;)
[Nook Color Android Development] TubeShaped:
No problems here with deep sleep or SoD either, regardless if OC or not, wifi is set turn off with screen. However my battery dies at around 10 percent. I wiped my battery stats but i still get PBD. also my NC seems to run choppy at lower percentages, including the scrolling acting weird and not smooth at all. Maybe my device needs a few more charging cycles?

Sent from my NookColor using Tapatak
[Nook Color Android Development] Gin1212:
You misunderstood then.

I was mentioning that with that combination (The newest nightly and OC kernel 5/23), that people who had lost deep sleep, had initially had it with that combination, but over time it seemed to disappear.

I speak from experience as well as what I've read. I have no problem admitting if I my observations were wrong, when the time comes, however it's just plain silly to try and hinder progress because you haven't personally had this problem.

There are people that have never had SOD (me included) or PBD issues. But they exist, and it would be silly for me to say they don't because I haven't experienced one of em.

That said, as I mentioned in another thread. Deep sleep doesn't seemed to have disappeared completely for me on N93 + OC kernel, however it takes at least an hour and a half of it being idle for it to kick into Deep sleep mode. Which sorry, but that's not very functional.

Oh also, I don't use Facebook and on the regular stock kernel it didn't matter if I kept wifi on or turned it off, Deep sleep kicked on regardless.
[Nook Color Android Development] gudism:
Just flashed from 91 with OC 2305 to 95 stock kernal and just wanted to add a few observations.

On 91 never had SOD but did have PBD twice at 15%.

No sleep issues except after a few days it didn't sleep all day but it came back that night.

On 95 had SOD first time screen turned off. Hard reset and boot back up, and noticed 'screen on animation' was checked, unchecked and no SD since.

Don't know if this is a cause of SOD but was what happened for me.

No sleep issues so far with 95 but only installed for 12 hrs.

And havent let the battery run down enough to see if it PBD's

that's my observations