yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] SCWells72:
The .29 kernel doesn't have the SOD (*sleep* of death) issue because it can't go into deep sleep. That's really its own issue because your Nook never goes into an extremely low power mode and therefore drains ~1%/hour even overnight.

Having said that, I can tell you that I'm using 7.0.3 (actually Phiremod 6.3 as of yesterday) with the .29 kernel as my stable install because while it never goes into a near-zero power usage situation, I don't ever experience the issue you're seeing with a .32 kernel. I was seeing the exact same behavior in my evaluation of it, plus there's something weird about .32 that causes FlexT9 in landscape mode to act up, and that's now my primary keyboard.

I'm hoping that in the next few weeks this will all be resolved and we'll have the best of both worlds, but in the interim I'm sticking with .29.
[Nook Color Android Development] fattire:
p2 is a FAT partition. Can't symlink.

Anyway, here's what I'm trying. This file is called pbdtest.sh..

#!/system/bin/sh

mkdir -p /data/rom
mount /dev/block/mmcblk0p2 /data/rom

# update p2/max17042.bin every hour

while [ 1 = 1 ]
do
cat /sys/bus/i2c/drivers/max17042/1-0036/histdata > /data/rom/max17042.bin
sleep 1h
done

$ adb push pbdtest.sh /data/

$ adb shell

# chmod a+x /data/pbdtest.sh

# ./data/pbdtest.sh &

#

yank plug let die.. let's see what happens. If it works it shouldn't be a problem to set up as a service. I'm at 99% so it's gonna be a while :)
[Nook Color Android Development] fattire:
Thought: I wonder if these random (and new) .32 "SOD" events are just PBDs that happen during sleep.
[Nook Color Android Development] Chahk:
Wouldn't the NC then turn on after 3 seconds of holding the power button? When my NC would refuse to wake up it was definitely not powered off, as I always had to hold Power for over 8 seconds and then press it again to turn the NC back on.
[Nook Color Android Development] frankusb:
I think you only need to update at shutdown (hourly won't hurt). I can't find the kernel reading the file (and if it's not mounted how could it?). But I see U-boot reading it.

This kind of makes sense, once the kernel loads, it can continue to monitor in real time and adjust.

Frank
[Nook Color Android Development] verygreen:
Updating periodically probably makes sense so in case of a crash the data is at least somewhat up to date.

What I think is missing is the test methodology itself. Just running the posted script would do nothing.

If you start with incorrect history data, you start with incorrect history data and saving it does not help.

The history data needs to be fixed first, and then saved from time to time.

Then periodic reboots to ensure that the data is restored to a proper state after a reboot.

And then after the reboots to see what happens.

I guess that's an easy verification method:

Without the script, charge to 100% in a known good instance like stock or whatever.

Reboot into CM7, battery should show 100%

run it down to some low value like 30%

Poweroff, then poweron into CM7 again (no external power).

If the history means anything, we'd see battery level reported to be higher than expected.
[Nook Color Android Development] fattire:
I have no known "good" instance.. having run cm7 since early jan :P

I think if it gets old or absurd values in 1.2 it now will change to factory settings and send THAT to the controller instead of what's in bin. So hopefully way old heuristics will slowly bend into correct ones... guess we'll find out.
[Nook Color Android Development] khaytsus:
For me, /rom is already mounted.... Curious why mount it again?

/dev/block/mmcblk0p2 69.5M 103.5K 69.4M 0% /rom
[Nook Color Android Development] Awats:
Do you want us to post when we don't have the problem? I've been running B86 for several days through many 1-100% discharge cycles and it always works. Only difference I can find from others is that I never registered the Nook. Without the SD card in it, it always comes up to the video.

Otherwise, I seem to be running the same thing as some of those having the issue.
[Nook Color Android Development] LongbowFoSho:
Its somewhat unrelated (since I haven't experienced PBD yet), but momentarily running HC from an SD card solved my deep sleep issues.

Basically, I couldn't get it to enter deep sleep at all on N87 w/ the 5/23 kernel (even after multiple reflashes) until I ran HC from an SD card for about 20 minutes.

I didn't install anything while using HC, I didn't change any settings, I didn't even connect to WiFi. All I did was browse the files and apps (you know...both of them lol) and then booted back into CM7 on the emmc. Almost immediately after the screen went off....VOILA....deep sleep galore.

Hope this helps. I posted it here because I thought it might be somehow related to the PBD issue.
[Nook Color Android Development] damnoregonian:
the file is written by a service in the stock firmware.

it is a direct dump from the i2c registers of the max17042, represented as 'histdata' in the appropriate /sys node.

upon boot, u-boot will read this file, and load the registers of the max17042 with the last recorded values.

after the max17042 calculates SOC (state of charge) with the saved values, if it finds it is under 10%, it will not boot.

i don't know what the SOD issues are (i haven't experienced them),

but this is almost certainly the cause of PBD (device shutting down hard at far above 0% SOC)

everyone's mileage will vary here, because the heuristics of the battery vary based on usage patterns.

scotty2
[Nook Color Android Development] bonobomidwest:
Sorry if i am contributing to the deviation from the reporting format here, but I have a godawful hybrid monster going on here, let's call it SODwoPBD...

...in other words the nook will not wake up without a power source, but when it does reboot it reports a "sane" battery level, and continues to run on battery... the last instance just a few minutes ago was at 80% battery, and we are runnign just fine now :)

...my current setup is vanilla nightly 86 with the inbuilt uboot, and the latest dalingrin .32 OC at 1100

...previously i was running stable 7.0.3 with absoluteyl no issues whatsoever

...anybody else seen a simialr hybrid problem?

...sorry for being late to the party :(
[Nook Color Android Development] pryonix:
More testing

Hi all,

I backed up data partition and reflashed my whole SD card 6 hours ago. I charged my Nook to 100% IN STOCK BN and then switched to recovery to wipe battery stats, then booted into CM7 87N.

I'm not experiencing SOD so far which is the first time it has happened since I started using CM7 (coming from PhireMod 6.2).

I also checked my battery stats and everything seems to confirm that my Nook has finally entered proper deep sleep and can be woken up properly as well. My nook discharged just 1% battery throughout the duration of the past 6 hours the screen was off.

What changed from previous configuration:

1. No overclock kernel.

2. Wiped battery stats after reaching 100% in stock BN 1.2

3. I put advanced wifi settings on 'never sleep when charging'

Important things that didn't change from previous:

1. No change in u-boot.bin

2. No change in MLO

3. No change in any of the files in /boot

Next testing step/s:

1. Install 5/13 OC and check

2. Install 5/23 OC and check

3. Modify wifi settings to never turn off and check

Haven't had time to browse through the whole thread but did anyone who ran stock kernel of CM7 87N experience SOD/PBD?
[Nook Color Android Development] TDO:
Any suggestions what app to use to drain the nook as fast as possible.

I just wonder what happens if you charge and have your nook turned off.
[Nook Color Android Development] fattire:
I just wanted to make sure to have a mountpoint in case someone would run it on another non-CM7 os that-- okay, I forgot :eek:
[Nook Color Android Development] khaytsus:
;-)

BTW I have been draining all night periodically copying the history data, almost dead... We'll see what charging looks like now. At 7% now. Got down to 2% and dipped below 3V and shut off immediately. So for me, discharges are pretty normal twice in a row, but last time the charge process was very weird, per the screenshot from a few days ago.

BTW, I noticed the NC booted at 10% battery, I thought that number was 15%? Doesn't really matter I suppose, 10% is plenty.
[Nook Color Android Development] Moxie3000:
I've been using an app called Stability Test, free on the market.

I don't know that it's the FASTEST way, but it's A way to drain it because it fully exercises the CPU and runs on an infinite loop.

If you had something that could also turn on the graphics adapter, that could drain it even faster.
[Nook Color Android Development] Gin1212:
Just load up a game in Psx4droid or N64oid and overclock it to 1200/1200 performance.
[Nook Color Android Development] khaytsus:
Not sure if I've seen any difference today, but I've done this from 50->0 and 0->100 and will keep doing it.. I still don't have PBD, and um, I figured out why my charging looked so screwy.. It was deep sleeping and not updating Battery Snap, when it woke up periodically it would update and jump because it'd charged N % in the meanwhile. Tested that today by turning on "Stay on while charging" and the charge curve looks normal now.

So I might not be the best candidate for this testing since I don't seem to have PBD, but doesn't seem to hurt so far either!
[Nook Color Android Development] Ronin3178:
I thought we couldn't disable the "stay awake while charging" for fear a "hockey nook"
[Nook Color Android Development] khaytsus:
eh? That was on the test builds.
[Nook Color Android Development] dalingrin:
This was only a stopgap solution until we fixed the real problem in ADB. It still won't sleep properly with USB but it shouldn't cause problems.
[Nook Color Android Development] Ronin3178:
I am still on the test build (ie; 7.1 RC0) with the 5/23 OC kernel. Haven't had any PBD in a while, I flashed N87 for a day or so, but got wifi problems (dropping in/out) so I went back. I think I had ONE SOD, ever. That was when I left wifi on/screen off and left my router range. Checked it hours later and it wouldn't come on until holding down power button.
[Nook Color Android Development] WobbleTheHutt:
just read your post a few pages back fattire, great work tracking it down it looks like. right now i get PBD at about 10%. with N86 and dals OC kernel :) let me know if ya need a tester ill be happy to flash!
[Nook Color Android Development] angomy:
Nook shut down in the middle of a movie at 20% (~3400mV), no low battery warning. Would not boot up until plugged in.

Now something strange is happening too - the battery % isn't updating while it's plugged into the charger. I had it plugged in for 1.5 hrs and it showed 21% (but accurate @ 3900 mV), when I unplugged it the percentage corrected itself to 82%. It's been doing it for the last hour too -- percentage isn't updating while it's charging, but will instantly do so when unplugged.
[Nook Color Android Development] TDO:
I had a similar experience.

The percent value started to rise after reaching 4200mV.
[Nook Color Android Development] BitingChaos:
Same situation here.

- Nook Color shuts down with apparently a decent amount of battery left.

- Battery percentage does _not_ increase accurately when charging. The "n" logo on my charger turned green after several hours letting me know it was charged.

After unplugging the Nook Color, I noticed my percentage showed something like 86% - but after a few seconds it jumped to 100%.

- Similar when when charging via USB connected to my computer (the instructions say it can't charge this way, but I've been charging it plugged into my computer just fine). It sat at 40-something% (where it was at when I plugged it in) for a long time (over an hour), but then jumped to around 63% or so eventually.

Something is definitely screwy with the battery.
[Nook Color Android Development] phenol312:
This sound exactly like what i was experiencing. Except now hooked up to a power source the nook keeps trying to boot but it keeps getting shut off by something. when it does actually boot up it shows the battery life at 41 percent. :confused:
[Nook Color Android Development] bonobomidwest:
I really like all the changes in the 8x nighlties, but i really need the nook to work when i turn it on :) and haven't had time to revert to stock 1.2 BN like so many people suggest. Instead i flashed the CWM backup of my 7.0.3 install (which included the /boot partition, and so the 1.1 uboot), and that seems to have fixed everything, no SOD no PBD, no hybrid SODwoPBD.

Also battery life is MUCH better. I had suspected that the 8x nighlies had much faster drain, and going back to 7.0.3 makes that painfully obvious.
[Nook Color Android Development] BitingChaos:
Yeah, the goodness that comes with later kernels that "fix" battery draining due to deep sleep seems to be overshadowed by the quicker overall (perceived?) battery drain and completely inaccurate battery percentage readings.
[Nook Color Android Development] rhester72:
I think the 'fast battery drain' is actually an illusion. It's the -apparent percentage- that's dropping faster, not the actual amperage available...and that's very likely the calibration issue.

I did a LOT of testing on this over the weekend, and found that 1.1.0, 1.2.0, beta 3.1, and n86, independent of kernel version, overclock, or WiFi/BT status, all have *identical* levels of battery drain under identical loads.

Rodney
[Nook Color Android Development] dalingrin:
To update, the fix for this issue has been submitted for review by FatTire. Hopefully will be in the next nightly.
[Nook Color Android Development] SCWells72:
That's fantastic! So is the intermittent SoD issue the only remaining major issue with the .32 kernel? That was plaguing me more so than PBD. I had to reboot my Nook at least once each day because it simply wouldn't resume from sleep.

By the way, I can't say enough times just how much I (and so many others here) appreciate the unbelievable work you guys are doing for the benefit of us all! Thanks again for giving up so much of your personal time!
[Nook Color Android Development] quikt:
YAY thank you Fattire and Dal!
[Nook Color Android Development] xxiworld:
Fantastic! Thanks to everyone for their hard work!

How did it end up getting solved? Verygreen seemed dubious about the script Fattire posted earlier. Did it turn out to work, or was there something else found?

Will this fix all of the battery weirdness, including apparently rapid drain, random jumps etc? And will we just need to flash the nightly, or will we need to clear battery stats etc also?
[Nook Color Android Development] dalingrin:
I suppose so though none of us can reproduce any SOD.
[Eee Pad Transformer Q&A, Help & Troubleshooting] acomiskey:
Make sure the update zip youre trying is not zipped....as in a zip inside a zip.....thats what i would try to solve first.
[Eee Pad Transformer Q&A, Help & Troubleshooting] maggotboy:
this is going to sound dumb but did you do settings>about tablet>system update>check update?

and check your file again, make sure you open the first .zip up and rename the second one after you extract it. i did it this way once and it just powers through no notification of it flashing but it updated fine.

hope i was able to help
[Galaxy S I9000 Q&A, Help & Troubleshooting] soraxd:
so I was wondering if there is, any solution for apps that require wifi only to work.. like any gameloft download or certain apps like crunchy roll, or uploading a video to youtube directly from our phone.. is there any way to trick our phone into thinking its using wifi?
[Galaxy S I9000 Q&A, Help & Troubleshooting] slaphead20:
In a nutshell ....no!....its the fast data transfer those games need...not the word wifi...come on dude...think about it! ...or u will get ridiculed! ...i am giving u a break....i wont.....plonka!...u deserved that! ;-)

Sent from gt i9000 insanity 8.5/fugumod
[Galaxy S I9000 Q&A, Help & Troubleshooting] soraxd:
so.. anyone?
[Galaxy S I9000 Q&A, Help & Troubleshooting] moophlo:
there is an app to do viceversa ... but I can't remember the name now ... lol
[Galaxy S I9000 Q&A, Help & Troubleshooting] azzledazzle:
a bit sarcastic that ! he was only asking lol
[Galaxy S I9000 Q&A, Help & Troubleshooting] slaphead20:
My apologies :-)

Sent from gt i9000 insanity 8.5/fugumod
[Android Software Development] Budius:
I saw a lot of ppl having this problem and it's something SO common to do, and the solutions I saw were ugly to the point that I bet that Google's solution for it isn't any of those.

Simple scenario, I have a few dialogues in my application being setup inside:

protected Dialog onCreateDialog(int id) {
switch(id){
case DIALOG_LOAD: return new ProgressDialog... etc.. etc..
}
}

and called with

showDialog(DIALOG_LOAD);

and dismissed with

dismissDialog(DIALOG_LOAD);

all inside the activity class.

This approach to dialogues I believe is the 'cleanest' way of doing it and just let the Activity manages the dialogues.

it works fines IF I don't rotate the device, I though because the activity was managing it, it would be all inclusive, but no, life is never that simple. If I rotate the phone when the dialogue is up, the rotation occurs, the dialogue is still visible but the moment the code try to dismiss it it gives a nice:

05-26 20:07:02.951: ERROR/AndroidRuntime(10041): java.lang.IllegalArgumentException: no dialog with id 1 was ever shown via Activity#showDialog

so...

do I have to care about dismissing and re-creating the dialogue onPause and onResume or is there anything I can do to make the activity take care of it by itself?
[G Tablet Q&A, Help & Troubleshooting] TyroneBiggumz:
Background info:

The G Tablet came with 1-1-3389 and I performed the OTA update to 1.1-3588 which went fine. I then rooted it with z4root and that went fine too.

1. I then side loaded ROM Manager and was able to install CWM Recovery and then was able to do a backup of my base ROM.

2. I then copied update-cm-7.0.3-Harmony-signed.zip and gapps-gb-20110307-signed.zip to the internal storage on my G Tablet.

3. In ROM Manager I chose to install ROM and I selected the gapps-gb-20110307-signed.zip and the tablet rebooted and came up in CWM Recovery. I watched it install 7.0.3 and then it rebooted on its own.

4. The tablet now will only come up to the Viewsonic screen with the birds on it and it just sits there.

5. I press the power button and hold it down to power off the tablet. I then press the + side on the volume rocker and press the power button. I get the "Recovery Key Detected" and then get a screen with a box on it with an arrow pointing down and a task bar underneath then it reboots and comes back up to the bird screen and just sits there.

I have read many threads about this but I am not sure just what my problem is exactly. The fact that I am unable to boot into recovery seems to be the biggest issue.

I have downloaded update-smb_a1002-3588-user.zip and update-smb_a1002-3389-user.zip and have went so far as to unzip the 3588 zip and copied its contents to my microSD card and inserted it and have booted it up while holding the + rocker down again...in another post on the subject I thought I should get "Recovery Image detected" due to the fact the microsd has the following on it...

data folder

META-INF folder

boot.img

bootloader.bin

recovery.img

system.img

Or did i totally misunderstand what I read?

Any ideas?
[G Tablet Q&A, Help & Troubleshooting] scyld:
Maybe others can give a more specific answer, but:

If you're willing to completely reset your tablet, you can use nvFlash to get it back to factory condition.

Just Google:

nvFlash "g tablet" roebeet

And follows the steps that roebeet outlines to get your tablet up and running again. It looks rather complicated, because the instructions could be formatted more clearly, but in reality it's a pretty simple process.

Note that doing this WILL erase ANYTHING you have on there.
[G Tablet Q&A, Help & Troubleshooting] TyroneBiggumz:
thanks for the reply....I do not mind losing anything to get it going again
[G Tablet Q&A, Help & Troubleshooting] TyroneBiggumz:
I am back rocking again...thanks!
[Galaxy S I9000 Q&A, Help & Troubleshooting] marcon10:
Want smurfs village on android . or is there an ios emulator to play this game. i know its on apple but im sure there must be a way to get it on android . Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] rschenck:
I can't help but think that the fact that Smurfs Village doesn't run on android is a feature, not a bug.

Just another example of Google looking out for us. Thanks Google!
[Galaxy S I9000 Q&A, Help & Troubleshooting] slaphead20:
Superb answer!! ;)

Sent from gt i9000 insanity 8.5/fugumod
[Galaxy S I9000 Q&A, Help & Troubleshooting] slaphead20:
Ps...there is a forum for these kind of questions....its called the playground!! :o

Sent from gt i9000 insanity 8.5/fugumod
[Galaxy S I9000 Q&A, Help & Troubleshooting] Psy1208:
Hahahaha .... Made my day :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] Mr Woolf:
Lol!

10 chars

Insanity cm - life is now complete.
[Galaxy S I9000 Q&A, Help & Troubleshooting] marcon10:
Thank you hoes
[Galaxy S I9000 Q&A, Help & Troubleshooting] MasterJam882:
First u post in wrong thread, second it's a rly lame game not supported on android and last but not least you abuse us for ur incompetence.

That's rude m8. Gargamel and Papa Smurf won't be amused about such a smurfing-tone in this thread!
[Galaxy S I9000 Q&A, Help & Troubleshooting] rschenck:
Smurfette? Is that you?
[Galaxy S I9000 Q&A, Help & Troubleshooting] jaju123:
Wrong section. Also how does Google not have the answer? Do the work yourself...
[Galaxy S I9000 Q&A, Help & Troubleshooting] jimbob80:
Answer

marcon10:

I recommend that you simply wait and see if it is released. Many games are making the leap to droids, so see what happens. Currently it is not and I have not seen any announcements that it will at this stage. In relation to an iOS emulator on an Android, "I don't think so!"...

I figured that seeing you posted a question on a forum for and answer, I thought I would answer your question rather than leave a smart ass response. You have to give rschenck some credit as it was a pretty good call..! ;)

I also agree that the game is lame, but not all people feel that way. Some people like it. My wife being one of them, she now has an Android and asks the same question.

I used to lay in bed at night having cold sweats from hearing her hammering in those dammed pegs! AGHHH...
[HTC Sensation] Classic0815:
Hi,

Is there an app (working with the Sensation) that can make the LED notification light flash continually until you actually open the new message or am I stuck having to bring the phone out of sleep incessantly to check if anything new has come in?
[HTC Sensation] ToneyEricsson:
Surely such an app would just eat battery up for no reason.
[HTC Sensation] Phil750123:
I've been having a look at this myself,

(i am a noob when it comes to devolping apps)

but i was one first to get desire and there

was a command that you can run (without root)

to get the led to flash different colours length etc..

Tried this on the sensation and just get a file cannot be found.

(if you want to now the command then pm me or

il post it up not that it be much help)

so basically this means all existing apps with run on this old

command, so a new one will be needed when somebody figures

out the file name for the sensation led - then you can

just push a number to it using the echo command and itl work.

put into a java script and your done
[HTC Sensation] xnifex:
wait so the notification light only lasts for 5 minutes? wtf?
[HTC Sensation] Paul22000:
What?? Is this true??? :eek::eek:
[HTC Sensation] Genesis206:
You know, I never noticed that since it's my second line. Interesting. Maybe part the reason the standby time is so good on this phone. (really reaching)

I did leave my phone alone for a few hours and no flashing led for my peep mentions.
[HTC Sensation] catrepair:
any update on this?

I just got the phone and the lack of a notification sound or light is a big negative for me.
[HTC Sensation] ariochenigma:
I would love to see the app NoLED work for the Sen4G which would be a perfect fix for this issue