yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] camalus:
Funny issue I discovered this morning...

Running CM #87. Dal OC kernel. Deep sleep has been working perfectly for a while now. I woke up this morning and checked cpuspy..... and my nook will no longer enter deep sleep.

I have made no changes what so ever the last few days. It just all of a sudden wont deep sleep.

Anyone have any thoughts?

I went ahead and did a clear install, wiped everything. Reinstalled 87 and oc kernel. Didn't restore anything. Still wont deep sleep.

Argh.
[Nook Color Android Development] jkabaseball:
I have tried multiple releases of CM7 and GAPPS, everything installs fine, I boot up and no GAPPS. Any ideas?
[Nook Color Android Development] Nburnes:
You've tried adding your account while connected to Wifi under Settings > Accounts & Sync > Add account (Google) correct?
[Nook Color Android Development] jkabaseball:
I hit add account and it pops up for a Exchange account, no option for Gmail. Also under all applications the market nor framework are there. Are there apk's for them or do I need the zip?
[Nook Color Android Development] newellj79:
Did u download gmail from the market?
[Nook Color Android Development] jkabaseball:
I don't have market. I don't have any of the GAPPS or the framework. I've installed the GAPPS multiple times and CM7 multiple times. The GAPPS says it installs, but doesn't appear to be installing at all.
[Nook Color Android Development] :
So either you don't know how to flash, or you're flashing a worthless zip. Have you checked MD5 sum?

If you want it to work, just unzip and manually push to system/app and where ever else it needs to go.
[Nook Color Android Development] newellj79:
This is the gapps I use. Do a complete wipe, flash rom, then gapps, then oc kernel if u choose. Should work. http://db.tt/SbljZOG
[Nook Color Android Development] LongbowFoSho:
I'm not exactly sure which thread to post this in since I'm not sure which component is causing it (CM7 or the OC kernel), but....

I have two Nooks in my possession. Both are *identical* in the sense that both were originally 1.1, updated to 1.2, then flashed with the 87 nightly and the new OC kernel running the conservative governor at 1200 mHz.

The problem? One Nook (mine) goes into deep sleep without issues and therefore has excellent battery life. I went to sleep last night with 90% and woke up nine hours later with 90% with Battery Snap showing deep sleep the entire time.

The other Nook (a friend's) never goes into deep sleep. While overall battery performance is better on nightly 87 than what I was running previously on mine (7.0.0 stable), it still isn't going into deep sleep.

I'm not really looking for a solution to this as it seems to be pretty random for most people (like PBD, which I haven't experienced yet), but figured I'd post it in here as an FYI type of thing for the devs and users alike. I'm reflashing N87 and the OC kernel as we speak, so we'll see how it does once I get everything set up again.
[Nook Color Android Development] Robertjm:
Set the browser profile from Android to desktop to get videos to play. Speed is catch as catch can sometimes.
[Nook Color Android Development] Nburnes:
That was a pretty old post in terms of development. YT works in browser and in app just fine for me and has for a while.
[Nook Color Android Development] MedLine:
I can offer some useful insight here. From prior postings AFAIK recent issue with lack of deep sleep on 2.6.32 CM7 seen only with 052311 kernel, and I think dalingrin is aware of bug:

I've seen problem twice, both immediately after flashing new CM7 ROM followed by 052311 OC kernel. "Spareparts > Battery History > Partial Wake Usage," running "dumpsys power" and "bugreport" in particular "bugreport | grep PARTIAL_WAKE_LOCK" revealed nothing. Both times, however, "cat /proc/wakelocks" posted at pastebin here and here revealed wakelock designated "omap3-dac3100" acquired and held through standby on my Nook.

This is analogous to what occured after the intitial 2.6.32 test build, where no deep sleep reported here and here, problem identified by dalingrin as due to "AudioOutLock" wakelock here, and fix provided here.

I have no idea what code "omap3-dac3100" belongs to, but it sounds kernel related, thus nothing we can do about it in userspace. What I've found is that rebooting once or twice, as also reported here, or reflashing the 052311 kernel fixes problem. There may be more to deep sleep problem than this wakelock, but once deep sleep normalizes my "/proc/wakelocks" look like this here.

hth

EDIT: useful description of stats in "/proc/wakelocks" (active_since, sleep_time, etc) found here middle of page.
[Nook Color Android Development] skwalas:
Medline, I'm on n87 using only the default kernel and am not getting deepsleep. I am not convinced it is only due to the 0523 overclock kernel. I had originally reflashed without the overclock in hopes of fixing the Pbd issue. I had inconsistent deep sleep with the overclocking, and now I get no deep sleep at all without it.
[Nook Color Android Development] MedLine:
yeah, well nothing's been simple recently. look at bright side, at least now we're all expecting good deep sleep with 2.6.32 CM7 and can go about looking for why we don't get it like rest of Android world.
[Nook Color Android Development] pryonix:
hi fattire, thanks for the feedback. yup i've seen the linked thread prior to reporting the issue but my issue is different from PBD as described in the PBD thread.

my nook would shut down but there would be no loss of battery charge (meaning no suddent jumps in battery life).

it just really shuts down. when i turn it on, the level of battery charge is where i'd expect it to be.

EDIT: NVM >.< I've been reading more extensively on the PBD thread and I'm thinking now that it really is PBD/SOD.
[Nook Color Android Development] oldman_58:
Check to serif WiFi has changed, the only way I get deep sleep is to have wifi shutoff when screensleeps
[Nook Color Android Development] only one haze:
Quick question. Is there any particular reason that an app would not scale to fill the screen with CM7? When I ran this app (RBC Ministries Our Daily Bread) on my AutoNootered Stock1.1 it filled the screen. Now on CM7 it is just a small portion of the screen, almost if it was on a phone screen. Is this inherent to CM7 or is there something I need to change?
[Nook Color Android Development] pryonix:
hi, this is inherent on devices that utilize a larger screen on an OS built for mobile phones. you can use a utility called lcd density (you can download it from the android market) to fix/resolve this but i must caution you that you need a rooted nook for this.
[Nook Color Android Development] seth.i.simmons:
Disregard the guy above, changing the LCD density will NOT make the app scale to full screen. Try going into spare parts and unchecking "compatibility mode", rebooting, and then try it again and see if it scales correctly. Hope that helps!
[Nook Color Android Development] only one haze:
Thanks, I will give that a try when I get home. Yeah I knew it wasnt an LCD density thing...
[Nook Color Android Development] RoboRay:
Disregard the guy saying to disregard. There really ARE some instances where specific LCD density settings will prevent certain apps from scaling to fullscreen.

Now, that said, there aren't many, and the Spare Parts setting IS far more likely to fix the problem than adjusting LCD density.
[Nook Color Android Development] seth.i.simmons:
Sorry about that, I have never heard of changing the LCD density to fix anything app wise, just some graphical glitches in certain themes. Good to have learned that.
[Nook Color Android Development] skwalas:
Actually, turns out that was probably a red herring. See my last post in the PBD thread ( http://xdaforums.com/showpost.php?p=14294639&postcount=130) describing how my nook seemed to think it was charging all day despite not being connected. Upon reconnecting (which did nothing) and disconnecting (which stopped the ghost recharging behavior), I immediately got deep sleep working again.
[Nook Color Android Development] boxcar8028:
oh my, im getting dizzy...

as the battery issues turn! :D
[Nook Color Android Development] DizzyDen:
You can't be... coz I'M DIZZY :D
[Nook Color Android Development] only one haze:
I have never made any LCD density changes. Is CM7 density different than stock? Like I said, no issues on stock rooted, but having come over to CM7 it doesnt fill the screen.
[Nook Color Android Development] :
Stop it!

Okay, stay above 161, and below w/e cuts off menus for the apps you use... (240+?).

I use 187.

To fix apps to go fullscreen, change compatibility mode to off. Search google if you don't know where that is. Reboot.
[Nook Color Android Development] only one haze:
Stop what? Yeah I know where compatability mode is. I will try that when I get off work. And I may try your 187, have seen many people post how awesome it is.
[Nook Color Android Development] seth.i.simmons:
I would definitely say go with 187, I'm rocking it right now, by far the best resolution.
[Nook Color Android Development] bekyndnunwind:
I tried 187, but it didn't look right with my current settings. I use LauncherPro 5x5, and half of my widgets were partially cut off. If I was using the standard LauncherPro setting of 4 rows by 4 columns it might work out...

161 is the only setting I could find where things fit like they should.
[Nook Color Android Development] :
5x5!?! Can you even fit anything on there!?! :P
[Nook Color Android Development] seth.i.simmons:
Wow, that is tiny! I run mine 7x7, and Im thinking about going bigger if I can... why such a small number of slots??
[Nook Color Android Development] psiphi:
And the latest official Netflix from Android does work with CM7 without modified files... (They took out device checking officially!)
[Nook Color Android Development] bigbob23:
Yeah, but with the latest CM7 kernels you still need to modify build.prop to get the proper playback speed.
[Nook Color Android Development] Divine_Madcat:
Given that the nook color is not even an officially recognized android device (it runs a heavily modified version stock, and has no official market access) the odds of Netflix spending time to make it work on our device are 0..
[Nook Color Android Development] jkabaseball:
I still can't get the GAPPS to install. Is there a way to manually install them?
[Nook Color Android Development] camalus:
Download.cyanogenmod.com
[Nook Color Android Development] jkabaseball:
I have tried the zip, and many different versions. It says it installs, but nothing shows up in CM7
[Nook Color Android Development] camalus:
From what I have seen from some other posts and such... I would almost suggest going back to stock and starting your cm expedition from scratch.... something is definitely messed up.
[Nook Color Android Development] Expatriotex:
you are turning your wifi on and connecting to the intertoobs after booting up, right? the gapps don't appear until you do.
[Nook Color Android Development] newellj79:
Intertoobs? Let me guess, word predict mishap?
[Nook Color Android Development] only one haze:
Compatibility worked. And 187 is awesome. Thanks for that!
[Nook Color Android Development] painter_:
Wish we had a new build. The build bot has been stuck for many days and the updates keep building up. The next nightly that builds is going to have lots of changes.
[Nook Color Android Development] lafester:
I was just about to post that I need my flashing fix. now pls.

Been 6 long days lol.

I might have to learn how to compile the builds myself.
[Nook Color Android Development] seth.i.simmons:
I know, I think I'm starting to have flash withdrawals. Almost a week with nothing to flash, I'm starting to lose it! Must. Have. Nightlies!

Lol....
[Nook Color Android Development] Expatriotex:
No. thats what i typed. The internet is a series of tubes, it is not a dumptruck, hadn't you heard?
[Nook Color Android Development] newellj79:
No I hadn't. Guess I'm not n the know. Oh well.
[Nook Color Android Development] Gin1212:
Can honestly say I'm not having withdrawals at all, with PBD still a major problem and this increased usage of battery (could still be the pbd) during on time; I've actually considered jumping back to .29 for the time being.

.32 deep sleep is awesome, but it's not really that awesome if on a light day of usage I hit 40% battery...

-For those who don't know how big of a CM7 supporter I am (i.e - Bought my nook yesterday guy), please know that I say this with all due respect to the dev's of the Nook Color CM7 team (Teamdouche)-
[Nook Color Android Development] bartonkt:
We question your nook/CM7 loyalty good sir!

Yeah, nightly 87 isn't working so good for me - lost the deep sleep. Not sure when, I think a few days ago when I had a SOD. Now the nook won't deep sleep for me, tried toggling the wifi on screen off setting to no avail, and wiping dalvik/cache + /system + /data + reinstall - no dice. Boo.

Nightly 88 please be my panacea so I don't have to burn HC to SD to fix this.
[Nook Color Android Development] only one haze:
I don't normally run the battery down on mine, but did last night. Got the popup warning a 15% and then it cut off at 3%. Nightly 86, 5/23 OC kernel.
[Nook Color Android Development] leapinlar:
You might just try a bootable CWM SD card to see if that fixes your deep sleep problem. I found that if I booted with the card and removed it immediately and selected reboot, it fixed my battery calibration problem with N87. It may be worth a try.
[Nook Color Android Development] bigbob23:
I saw this in another thread: http://xdaforums.com/showpost.php?p=14324928&postcount=2760

In Locations & Security settings, turn off both entries under My Location. It will probably mess up location-based apps like Google Maps, but after doing this I finally have deep sleep working.
[Nook Color Android Development] tootseroel:
Wifi connect on start

I think this has been answered before, but i cant seem to find the answer with search. Is there a way to automatically connect to Wifi on boot?
[Nook Color Android Development] bartonkt:
@ bigbob23, will try! Thanks.

@ leapinlar, not sure what you mean. I have a bootable CWM SD card that I use to flash over all my ROMs and kernels and such, are you saying you just boot into that, remove the SD card and select reboot, and it fixes it for you? That's weird if so, but I'll give it a shot if @ bigbob23's suggestion doesn't work. I don't mind charging the Nook often, but I was enjoying the deep sleep.

Edit - Thanks bigbob, that worked!
[Nook Color Android Development] Chahk:
double post, ignore plz...
[Nook Color Android Development] Chahk:
It should do this by default if you don't disable WiFi when shutting down or rebooting. Once you successfully connect to a wireless network, it will be remembered and should automatically reconnect to it once it's nearby.
[Nook Color Android Development] tootseroel:
even if wifi is enabled, once i reboot, i need to enable wifi every time my nook boots up. then i have no problem connecting to my router. but i need to enable wifi every time
[Nook Color Android Development] SCWells72:
Have you ever tried to enable Airplane mode? If so, you need to go in and change a sqllite DB setting to fix this situation. I can't remember the exact change, but one of the guys on here has seen the question asked so often that he's added a link to the details in his signature. I'm sure a quick search will turn up the specifics.
[Nook Color Android Development] Chahk:
Excellent point, I've forgotten about that. This is the work-around to the Airplane Mode bug.
[Nook Color Android Development] boxcar8028:
yeah, due to the need to flash something, i mean anything. i think i'll flash a g-tab rom over my nook... :D
[Nook Color Android Development] khaytsus:
No problem here with LBS on, mine deep sleeps 65% of the time. Something else is up with yours.
[Nook Color Android Development] oldman_58:
From ADB

adb shell

sqlite3 /data/data/com.android.providers.settings/databases/settings.db

delete from system where name = 'airplane_mode_on';
.exit

From a terminal session

su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db

delete from system where name = 'airplane_mode_on';
.exit
[Nook Color Android Development] oldman_58:
I am running N87 with the 5/23 OC kernel... No SOD or PBD so far, been 3 days, I left both my nooks unattended all day after a full charge over night, both Nooks were at 100% after 8 hours... Deep Sleep is agreeing with them..

The only things I did:

Nook1 got a full restore to B&N 1.2 then a fresh install of CM7, I was still getting SOD

Nook2 cleared Cache and dalvik same SOD issues.

Now here is where it gets strange, I swapped SD cards, I did format and restore each card's data. I re-downloaded all my apps since .android_secure was cleared. Since the SDCard swap no SOD or PDB.

So it may be the re-download of Apps or Card Swap
[Nook Color Android Development] leapinlar:
That is exactly what I meant. It resets the battery calibration problem for me. It does not prevent the problem from reoccuring though.
[Nook Color Android Development] Calla969:
Every time I flash the oc kernel I lose deep sleep. I've tried rebooting, clearing caches, toggling all kinds of stuff but the only way I have found to get it back is to return to the stock kernel.
[Nook Color Android Development] bigbob23:
Well, it worked for a time but after a reboot it doesn't deep sleep with those settings turned off.

Edit: Somehow deep sleep is working again. The only change I have made is to turn off animations. :confused:
[Nook Color Android Development] bekyndnunwind:
Looks like some interesting commits were made...

Can't wait for the next nightly!
[Nook Color Android Development] rhester72:
The power fix seems awfully hacky tho - we have no clue how stock Froyo does this? (I just can't imagine it using a polling script like that!)

Rodney
[Nook Color Android Development] chisleu:
As long as it won't keep it from sleeping, no big deal for me. I don't know nothing about nothing, but why isn't that just a symlink?
[Nook Color Android Development] khaytsus:
Because it's a stateful file, it needs to exist on boot, etc. Can't just be a symlink. And not sure of the filesystem on /rom, but if it's FAT couldn't symlink anyway.
[Nook Color Android Development] dennisi01:
Need a bit of help - im running n87 with dal's OC kernel. I installed chainfire and samurai 2 - and lost deep sleep. Is there anything i can use to gather information as to why deep sleep isnt working?
[Nook Color Android Development] seth.i.simmons:
Looks like the changelog and mirror are back up, with some nice new commits (and I think I saw fattire's battery fix in there too) hopefully that means we'll have a new nightly soon!
[Nook Color Android Development] newellj79:
This may not b the place but I'm curious. I installed chainfire 3d, and it wiped my SD card. Took me a minute to figure that it was the culprit, tried it again, same thing. What gives?
[Nook Color Android Development] racks11479:
Hope someone can help me out,. I'm on the latest nightly 87 with 5/23 kernel. Trying to connect to bluetooth headset. It says connected and paired. Also says Bluetooth paired with phone audio. But still no sound coming through to my bluetooth headset. Sound is still coming from the internal nooks speaker. Is there something else I need to be doing? Or is is an issue with my bluetooth headset.?

Thanks,Racks
[Nook Color Android Development] TDO:
You are right this is the place for CM7 and not for chainfire.

Ah that are good news - I am also looking forward to try the new build.
[Nook Color Android Development] dexx0008:
only semi related but my bt keyboard stopped functioning with the new kernels. I'm on nightly 86, was on 7.0.2 the last time bt keyboard worked. I'll need to break out the wii controller to see if that still works. btw my keyboard connects and pairs fine and says connected, it does nothing after that though. don't have a bluetooth headset with me to test that.
[Nook Color Android Development] paleh0rse:
As long as the displayed % is accurate, the drain is slow and steady, there's a warning at a true 15%, and the final shutdown is done gracefully at <1%, I don't care how it's handled... :)
[Nook Color Android Development] boxcar8028:
I really hope the new nightly with the battery fix will solved the PBD, SOD, and no deep sleep issues. for me its one or the other, deep sleep with SOD or no DS with no SOD. I see in the change log that the screen on animation has been removed. does anyone know if this is for fixing SOD?
[Nook Color Android Development] rhester72:
It is not. It's because it can hardly ever be seen because of how long it takes the screen to turn on from wake.

Rodney
[Nook Color Android Development] bartonkt:
Speaking of screen on/off animations, I don't enable the screen on for the reason above. However, I did like the off animation - but it only worked for a short period of time after I wiped + installed nightly 87. Now the setting is enabled, but I never see the animation.

Any tips to restore it?
[Nook Color Android Development] chisleu:
It happens too fast to see it because the screen takes so long to come on.

It's disabled in the upcoming nightly for just this reason.
[Nook Color Android Development] boxcar8028:
just filled out the form. yeah, I hope this will be as helpful as fattire's PBD post. :D
[Nook Color Android Development] Deaks2:
Did you change your animation speed to Fast or Fastest? You need to set it to Normal for the CRT-like off effect to work.
[Nook Color Android Development] boxcar8028:
yeah, thanks. I have no problems with the animations, I can see them just fine. Its no deep sleep and SOD, is my menace. Its just I remember reading back somewhere that someone mention that turning animations off can help with SOD :)
[Nook Color Android Development] zombieflanders:
My personal favorite is this one:

Add sanity check for battery capacity range. (android_frameworks_base)

Does this mean each round 1D3 investigators are scooped up by CM7 to PBD hideously? ;)
[Nook Color Android Development] hockeyfamily737:
I can only get my headset to carry the audio signal about 3".... I gave up. Same thing paired and connected, but no tunes until I put my eyeballs against the screen.
[Nook Color Android Development] racks11479:
Lol hahaha. I'm just picturing a bunch of people with their nooks flat on their faces just to use Bluetooth. :D
[Nook Color Android Development] Deaks2:
Oops, I quoted the wrong person, I meant to quote bartonkt.
[Nook Color Android Development] martian21:
I set up a build server in a Vmware virtual server (64-bit Ubuntu 11.04) and built from the latest Encore (Nook Color) source this afternoon in hopes to be able to test out some of the new commits this weekend. The update went smoothly (cleared cache and dalvik then flashed). I modded my framework.jar with Dizzy's program to create an IMEI number based on my serial number. As I expected this broke Swype (un-install, clear data in installer, reinstall with new account fixed it). Had to reinstall Chainfire3D drivers as well but that was expected.

I've connected to at least three different wireless networks (WPA2, WPA, and Open) and had no issues. Haven't ran the battery down yet but percentage was the same before and after flashing so I don't anticipate any PBD issues (haven't had any since briefly flashing stock 1.2). No SOD so far and deep sleep appears to be working just fine. Haven't done anything with Bluetooth yet and don't have any Bluetooth devices with me so can't test but I don't recall seeing any Bluetooth commits recently.

All in all my Nook is running the best it's ever run! One last thing, it's probably just excitement over a new build, but my wireless speeds seem noticably faster with the new build. Everything Internet related feels really snappy!

Martian21
[Nook Color Android Development] clamder:
Wanna share? :)