yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] mad-murdock:
keep in mind, 66 is kali's kernel, plus a lot, minus some, plus the bat fix.

this is kali's kernel, plus the bat fix. (plus a userspace bootfix)

results might be different - thats the reason i didnt use hrkfdn's kernel, but just cherry-picked the driver modifications.
[Desire HD Android Development] SbTro:
How can i remove FMradio from nightly builds ? I want to use last nighty version with your patch... in #6 or #7 i must to use google search voice ?
[Desire HD Android Development] mrbubba999:
Confused. If I flash #7 do I need to do anything else? I've been running #5 with no issues and haven't had to do anything with it
[Desire HD Android Development] mad-murdock:
you dont need to remove fmradio. just flash #7. you might need voice search / voice dialer once after your first call.

just flash #7 - nothing more.
[Desire HD Android Development] kshting:
Am getting quite reasonable consistency of 3mA since flashing #7....
[Desire HD Android Development] LorD ClockaN:
hm...

my gscript sometimes works, sometimes doesn't..

When it doesn't work it shows those few lines:

suspend

resume

suspend

resume

...

But battery is at 4mA

edit:

now I tried voice dialing and after that script works..

It must be that issue mentioned above...
[Desire HD Android Development] mad-murdock:
Added FAQ to first post

well, it shows the last lines of the kernel message. if you are poweroff, but you got 20 (or more) lines of suspend/resume, you wont see the last poweroff output
[Desire HD Android Development] Chezbel:
For the last 20 minutes my CurrentWidget log shows 3-4mA, but that's too short to be interesting. I'm about to start an overnight test...

EDIT: Should have said I'm using mad #7
[Desire HD Android Development] tommy.:
With #7 im getting 4-6, but with #5 I was getting 1-3. I think I am going back to 5, I prefer to write aic3254pd status every time, but at least get a proper answer from the terminal :p

ps: all this with turned ON skype, 3g, call blocker and Fancy widget.
[Desire HD Android Development] c_felge:
Strange...

Why is the current consumption that inconsistently?

Compared to #5 jumps were about +/- 1 mA.

And now look at that. I'm on #6.

2011/03/14 19:40:00,-69mA,71%

2011/03/14 19:41:09,-8mA,71%

2011/03/14 19:42:18,-9mA,71%

2011/03/14 19:43:26,-3mA,71%

2011/03/14 19:44:35,-9mA,71%

2011/03/14 19:45:40,-10mA,71%

2011/03/14 19:46:49,-9mA,71%

2011/03/14 19:56:21,-11mA,70%

2011/03/14 19:57:59,-11mA,70%

2011/03/14 19:59:08,-10mA,70%

2011/03/14 20:00:16,-3mA,70%

2011/03/14 20:01:28,-5mA,70%

2011/03/14 20:06:02,-5mA,70%

2011/03/14 20:13:01,-10mA,70%

2011/03/14 20:14:02,-3mA,70%

2011/03/14 20:15:13,-9mA,70%

2011/03/14 20:16:22,-10mA,70%

2011/03/14 20:17:31,-10mA,70%

2011/03/14 20:26:21,-5mA,70%

2011/03/14 20:30:04,-3mA,70%

No sync, didn't touch anything, just standby.
[Desire HD Android Development] LorD ClockaN:
I was just at 2mA :)

It was never that low before!!
[Desire HD Android Development] Rosjer:
Still something weird on my phone not accepting the grep command :/

When running the script on #7 i get:

stderr: Permission denied
[Desire HD Android Development] mrbubba999:
Looks good to me so far, high spikes when I'm the phone

2011/03/14 18:17:47,-147mA,47%

2011/03/14 18:17:54,-147mA,47%

2011/03/14 18:17:56,-147mA,47%

2011/03/14 18:19:15,-5mA,46%

2011/03/14 18:25:28,-20mA,46%

2011/03/14 18:25:50,-10mA,46%

2011/03/14 18:25:59,-10mA,46%

2011/03/14 18:26:03,-10mA,46%

2011/03/14 18:26:03,-10mA,46%

2011/03/14 18:27:03,-190mA,46%

2011/03/14 18:34:56,-5mA,46%

2011/03/14 18:35:58,-1mA,46%

2011/03/14 18:45:36,-5mA,46%

2011/03/14 18:50:26,-4mA,46%

2011/03/14 18:51:26,-288mA,46%

2011/03/14 18:52:26,-137mA,45%

2011/03/14 18:53:26,-129mA,45%

2011/03/14 18:54:26,-135mA,45%

2011/03/14 18:55:27,-130mA,44%

2011/03/14 18:56:27,-180mA,44%

2011/03/14 18:57:27,-236mA,43%

2011/03/14 18:58:27,-129mA,43%

2011/03/14 18:59:27,-130mA,43%

2011/03/14 19:00:27,-278mA,43%

2011/03/14 19:01:27,-197mA,42%

2011/03/14 19:02:27,-117mA,42%

2011/03/14 19:03:27,-134mA,42%

2011/03/14 19:04:27,-186mA,42%

2011/03/14 19:05:27,-228mA,42%

2011/03/14 19:06:27,-182mA,41%

2011/03/14 19:07:27,-115mA,41%

2011/03/14 19:08:27,-203mA,40%

2011/03/14 19:09:27,-121mA,40%

2011/03/14 19:10:27,-117mA,40%

2011/03/14 19:11:27,-242mA,40%

2011/03/14 19:12:31,-242mA,40%

2011/03/14 19:15:01,-5mA,40%

2011/03/14 19:16:04,-5mA,40%

2011/03/14 19:17:36,-10mA,40%

2011/03/14 19:20:02,-5mA,40%

2011/03/14 19:21:04,-5mA,40%

2011/03/14 19:25:58,-5mA,40%

2011/03/14 19:34:56,-5mA,40%

2011/03/14 19:35:59,-4mA,40%

2011/03/14 19:45:36,-4mA,40%

2011/03/14 19:55:29,-5mA,40%

2011/03/14 20:00:46,-1mA,40%

2011/03/14 20:01:47,-1mA,40%

2011/03/14 20:04:56,-6mA,39%

2011/03/14 20:06:00,-1mA,39%

2011/03/14 20:07:42,-178mA,39%

2011/03/14 20:11:19,-178mA,39%

2011/03/14 20:12:19,-1mA,39%

2011/03/14 20:13:19,-5mA,39%

2011/03/14 20:15:36,-3mA,39%

2011/03/14 20:21:04,-3mA,39%

2011/03/14 20:22:04,-1mA,39%

2011/03/14 20:26:00,-5mA,39%

2011/03/14 20:31:34,-5mA,39%

2011/03/14 20:32:34,-148mA,39%

2011/03/14 20:33:34,-230mA,39%

2011/03/14 20:34:34,-178mA,38%

2011/03/14 20:35:44,-261mA,38%

2011/03/14 20:37:07,-261mA,38%

2011/03/14 20:42:34,-201mA,38%

2011/03/14 20:45:35,-185mA,37%

2011/03/14 20:49:56,-167mA,36%

2011/03/14 20:51:04,-126mA,34%

2011/03/14 20:55:31,-151mA,33%

2011/03/14 20:56:33,-18mA,32%

2011/03/14 20:58:09,-18mA,32%

2011/03/14 20:59:09,-221mA,32%

2011/03/14 21:00:09,-142mA,32%
[Desire HD Android Development] LorD ClockaN:
Have you set it for SU?
[Desire HD Android Development] Rosjer:
yep, all done acordingly to the guide in 1st post.

Had simular problem with #5 were my terminal and adb would'nt recognise grep as and internal or extarnal command for some reason :/

even with latest SDK tools it does the same....

noone seem to have an answer why though :(

EDIT: if anyone know how i can adress troubleshooting this issue i would be most happy to try anything :P
[Desire HD Android Development] Scottymeuk:
I have been using my phone as usual from about 8am without charge. It has normally run out of charge by the time i get home from school or is just about to (10% or so). I have done nothing different on my phone today and at 9pm it is still at 52%. Thank you very much for this fix.
[Desire HD Android Development] c_felge:
Why is #6 gone?
[Desire HD Android Development] XL3N7:
Run superuser from the app drawer and see if gscript or terminal is not allowed to run with su privileges.

Regarding #7, I can confirm that after the first call the chip is on. Voice dialer works to deactivate it, as before
[Desire HD Android Development] Rosjer:
that was weird, started SU, Terminal was there and allowed, gscript was not, started gscript while SU was open, then it got the right priveledges.

Thx m8, that did it and my log came running like a dog on heal ;)
[Desire HD Android Development] xd4d3v:
Nice one mad, as soon as I flashed this version, it went down to 3 or 4 ma.

fantastic
[Desire HD Android Development] hedayat7:
Hi mad, on #7 I got too many resume and suspend. And I think this maybe the cause of the spike, is it ?

Edit : ok I've read again first post and that will be ok. :-)
[Desire HD Android Development] Chezbel:
Here's my overnight currentWidget log. In about 7 hours I lost just over 4% of battery, that's quite nice.
[Desire HD Android Development] mad-murdock:
remember that the difference between 1-3 and 3-5 is pretty near where you cannot measure anymore.

its plain and simple: if power down is working (below 10), it is working the same way as in older builds, regardless of the output.

Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
[Desire HD Android Development] mad-murdock:
so, the overall result is, voice dialer needed after first call, then never again?

Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
[Desire HD Android Development] Chezbel:
So far that is my experience with #7 battery.
[Desire HD Android Development] funkatiko:
Hi! Is it possible to use this patch with other kernel??
[Desire HD Android Development] hedayat7:
different kernel ? re-compile back as mr mad murdock said below. :)
[Desire HD Android Development] mad-murdock:
if you re-compile the kernel, yes

if you use this patch on a different rom - well - maybe - worth a try
[Desire HD Android Development] jcrompton:
Tried on LeeDroid latest GB Beta and phone stuck at HTC screen .... I guess not compatible ?
[Desire HD Android Development] mcbobo:
Yes) only for CM7

Sent from my Desire HD
[Desire HD Android Development] Kelthizar:
yes the first time i had to use voice search for powering off the chip but now it switchs off after a call.
[Desire HD Android Development] kshting:
These are the results based on the current widget logs for both overnight and during the day. Phone was in standby mode (no usage):3g/data/sync on during these hours.

There are, however, some unusual spikes (similar in #5) from the logs. I still could not figure out what might be causing it. My guess would probably be those mails pushed to me during these hours or the phone may be doing some work in standby (but what??). From the OP, it mentioned that "You find suspend/resume loops in dmesg output. They are harmless," could this also be reason for causing the spikes? From the dmesg output, there was definitely these suspend/resume loops.

With the above said, I am getting different battery drains:

Overnight: 6% in 5hrs i.e. 1.2% per hr

Day: 10% in 5.67hrs i.e. 1.76% per hr

Is anyone here experiencing similar case??? Any insight on this matter?? (Not using Setcpu/ no screen off profile, just as it is)
[Desire HD Android Development] mad-murdock:
first of all, the resume/suspend loops are really harmless. the driver does nothing else than output to the log and set a variable on suspend. no other code is executed. i have the feeling, those loops even appeared without the patch, just noone took a look at it (: if i am right there, i will just disable the log output.

about the spikes - well - i noticed the same. when i disable network connection and/or sync, i dont have any spikes. so its the work of apps doing dirty stuff while you sleep. once i disable network access, k9-push, beluga and some other stuff i use are also disabled, and drain is gone away. for #1 i even tried to not disable the network but force close all background services i could and came to the same result (see screenshot on first post - thats how it was done - network enabled, most background stuff killed)
[Desire HD Android Development] mad-murdock:
from the results so far i guess, #8 could be the final version, solving all issues and making it into cm7 finally. i have an idea how to solve the workaround once and forever - hope it works (:
[Desire HD Android Development] EmptyArea:
Best of luck.

Swyped on transparent XDA app.
[Desire HD Android Development] kshting:
Thank you. At least right now I could ease my mind from thinking what could be the culprit.

Edit: All the best to #8.
[Desire HD Android Development] Chezbel:
I notice that your log has multiple entries for the same time like this:

2011/03/15 03:00:56,-6mA,54%

2011/03/15 03:00:56,-3mA,54%

2011/03/15 03:00:56,-3mA,54%

2011/03/15 03:00:56,-3mA,54%

2011/03/15 03:00:56,-3mA,54%

I had that too until I uninstalled and reinstalled CurrentWidget. These are probably harmless, but...
[Desire HD Android Development] alain57:
i can't wait to see this in CM7 :)

you really did a great job
[Desire HD Android Development] Fihlvein:
I had a lot of inconsistency with CurrentWidget log times. For example when sleeping, CurrentWidget failed to log at configured intervals constantly.

I find Battery Monitor Widget more nice.

I don't want to bash CurrentWidget, it's a very simple and cool software and I hope it will be improved even further.
[Desire HD Android Development] kshting:
But......???????

Noted. :)
[Desire HD Android Development] Chezbel:
I thought you said you didn't have a sense of humor....
[Desire HD Android Development] hypnz:
Well I installed latest fix and I think I noticed some strange behavior. When I plug handsfree w/o playing something only making 15 20 mins calls I have mass battery drain.75% from 7 to 16 am
[Desire HD Android Development] ghostofcain:
Have you really made fifteen x twenty minute phone calls or did you mean fifteen to twenty minutes of phone calls?
[Desire HD Android Development] BumAround:
yep. not to mention what does '7 to 16 am' mean?
[Desire HD Android Development] Fihlvein:
I got expected, good news: I flashed this yesterday evening, and today I've charged battery, used wifi, mobile data, talked some phone calls, and I'm still having the DSP switched off, and a fine 1-4mA consumption.

Only time I had to use Sound Recorder, was after very first phone call yesterday.
[Desire HD Android Development] kshting:
Probably he was trying to say from 7am to 4pm and he lost 75% of battery life in 9hrs by just making that 15-20 minutes phone call :D:D:D
[Desire HD Android Development] hypnz:
Yeah that I mean :) sorry for my bad english:( until now I post the reply I have 20 % battery left:(
[Desire HD Android Development] BumAround:
what is your ROM? radio? did you full wipe? (system, cache, dalvik, boot, batt stat)?
[Desire HD Android Development] Rosjer:
@Murdock

A question m8, is this fix significant to Ace (DHD) only? or can it be used with any phone running CM7?
[Desire HD Android Development] hypnz:
My rom is cm7 nightly 15 and my radio its 26.4.2.17_m2.yeah I did full wipe and also batt stats. Dunno that's happens.
[Desire HD Android Development] ButtonBoy:
I installed Nightly 19 this morning, then power #7. Power consumption is still high, and typing "aic3254pd" in a terminal screen produces "not found". How can I debug this?
[Desire HD Android Development] Rosjer:
OP updated with how ;)
[Desire HD Android Development] ButtonBoy:
Thanks for the rapid response! That was it.
[Desire HD Android Development] in4ra:
I can report that with #7 I still have to use the voice dialer workaround (as noted earlier) and that after a call, the chip remains powered on and that I have to initiate the voice dialer again to turn it off.
[Desire HD Android Development] mad-murdock:
did you use voice search/voice dial after the first call? this is the only know bug right now. need to reset dsp with voice search after first call - thats all atm.

use method in first post to test your power status

it is significant to Ace/DHD only - because there are no other phones using this kind of dsp chip. maybe the upcoming desire s will feature that chip.

make sure its not only after the FIRST call. if its after the first call only, that bug is known and worked on. if its after EVERY call, that would be new and require detailed explaination.

i dont (: i just like to create lolcats.... totally humor less - laughing makes me caugh anyways

i can proof it - look:
[Desire HD Android Development] jeslas:
i also get "not found" when trying aic3254pd status in terminal.

Is this OK ?
[Desire HD Android Development] LorD ClockaN:
OMG why don't people atleast read the first post!?!??!?!

patch #7 doesn't use aic3254pd comand and power deamon!!
[Desire HD Android Development] jeslas:
OMMAGAD, OMMAGAD!!! - chill dude..
[Desire HD Android Development] hypnz:
Haha:)

@mad. Yeah man I have done after first call voice dialer to reset dsp but I say when I plug handsfree the dsp remains on. Also I saw some suspend/resume to log but I dunno what's going on.
[Desire HD Android Development] 1234568:
I agree with both of you, lol.

@ Jeslas - I had the exact same thought as LorD. You really should read the first post. To make matters worse for you someone had asked the same question just a few posts before. Dont be lazy, just read a bit and then ask questions if you are still not sure.

@ Lord - I thought his question clearly showed he was lazy but couldn't be bothered to let it bother me. Enjoy life :D

And now to explain why i'm sharing my random and meaningless views with you all... because I should be studying and cant be bothered.

Back on topic... I am using nightly #19 and Bat #7. I find that I need to use voice search workaround after first phone call lilke everyone else. More importantly though I never have to do it again! Good progress!
[Desire HD Android Development] mad-murdock:
can anyone with a bluetooth receiver confirm no-power-down with it connected?

i guess you talk about a bluetooth device? or the normal wired headset?
[Desire HD Android Development] Rosjer:
I can confirm, using BT when listening to music and also with calls, stays off with the usual startup prosedure, for me at least it does :)
[Desire HD Android Development] flo90:
Compatible with CM6???
[Desire HD Android Development] hypnz:
normal wired headset mate. Mass battery drain . I can't explain

It.
[Desire HD Android Development] mad-murdock:
you used workaround after first call?

@Rosjer, so you say, with bluetooth connected, switching to power off after you stop playback, but bluetooth device still connected?
[Desire HD Android Development] mad-murdock:
not sure - try it - might work... its the same kernel (kali's kernel), just with newer patches.
[Desire HD Android Development] in4ra:
I've run the script every now and then to monitor the power state but I have a feeling the chip power is turning itself on after a while:

3254_suspend

<6>[ 3389.449798] spi_aic3254_resume

<6>[ 3390.403106] spi_aic3254_suspend

<6>[ 3390.233551] spi_aic3254_resume

<6>[ 3391.855560] spi_aic3254_suspend

etc...etc..

I re-read the first post and I understand the resume/suspend loop is harmless --- how can I verify that the chip is actually in a powered off state if this is all I see or should I take the resume/suspend loop as an indicator (until it's fixed) that it is indeed turned off?

I'm losing between 2-4% battery per hour. I think #5 worked better as I saw a 2% battery drop per hour on average. Can I simply flash back to #5?
[Desire HD Android Development] Rosjer:
@Murdock

Yes, connecting BT headset, playing music and making calls, after i stop music or hang up calls, BT still attached aic poers off, also stays off after disconnecting as intended.
[Desire HD Android Development] mad-murdock:
good news indeed - so except users not understanding the first post, i see no issues at all except the one-time-workaround...
[Desire HD Android Development] SbTro:
This patch is great . 10 x. It work very good. 2 ~ 5 mA.
[Desire HD Android Development] buzzboy:
Working beautifully for me, huge battery increase! Thanks.
[Desire HD Android Development] titoodj:
This works with CM Enigma Kernel? Thanx!
[Desire HD Android Development] hypnz:
Yes mate after first call I use voice dialer.
[Desire HD Android Development] Frustu:
Flash built 7 on CM 19 anderweb works good now i get 1/4 mA on standby! !!!
[Desire HD Android Development] rsasecure:
I'm going to apologize first. I've read the first post and I'm not clear if mad-batfix-B7-signed.zip is needed when running update-cm-7.0.0-RC2-DesireHD-signed.zip on my ATT Inspire 4G. Thanks in advance for the help!
[Desire HD Android Development] ghostofcain:
It is if you want a decent battery life.
[Desire HD Android Development] rsasecure:
Thanks. Will I need to re-flash anything after flashing mad-batfix-B7-signed.zip?

Edit:

Regarding Battery Life

1. Is there a big difference between update-cm-7.0.0-RC2-DesireHD-signed.zip and cm_ace_full-19.zip?

2. If I go to cm_ace_full-19.zip do I need to do a full wipe?
[Desire HD Android Development] undave:
I'm using CM7RC2. With #5, battery life was great. With #7? It's by far the best battery life I've ever managed to achieve with my DHD.

I haven't bothered to try the nightly builds because I haven't seen the need. Can anyone report on what's changed in the latest builds?
[Desire HD Android Development] Chezbel:
igor.tonky created this link. It only shows the last few latest nightlies though.

http://cm-nightlies.appspot.com/?device=ace
[Desire HD Android Development] undave:
Ah, that's perfect! :)

Tells me exactly what has changed in each nightly. I'll keep an eye on it, and if anything significant changes, I'll know I should update.
[Desire HD Android Development] gururajkg:
well build #20 up

GPS ISSUe is solved

Have to install #7 for the battery fix
[Desire HD Android Development] Chezbel:
This a bit general and possibly belongs in a different forum, but I'm posting it here since the battery patch is a perfect example.

I assume that the safest practice when installing multiple .zip files is to reboot between each install. Although in the case of the battery patch it doesn't seem to matter whether that gets flashed immediately after a nightly or whether there is a reboot in between.

So is there a recommended best practice when doing this or is the answer "it depends what you are flashing"?
[Desire HD Android Development] c_felge:
Hi,

I have a problem with #7.

What I've done: Starting with Nightly #18 and fix #5. Upgrading to Nightly #19 and still batt fix #5. With a drain always around 5mA (-2 | +1). Flashing fix #6 I didn't experience any notable improvement in battery life compared to #5. So I flashed #7 and tested it and what I got was an inconsistent drain. The consumption was jumping every minute between 3, 9, 11, mA. So my thought was to make a fresh start, so wiped everything, flashed #19 again, set it up and flashed fix #7 again. Last night I logged the drain again and nothing has changed. I still have an inconsistent consumption.

I'll post the log so you can have a look for yourself. To make myself clear I'm not talking about peaks! I lost about 8% in 8 hours of standby! That's way too much IMO!

Can anyone help me with that issue? Or just give an advise? Am I the only one with this issue? If you need more information just ask!

Best regards

Felge
[Desire HD Android Development] mad-murdock:
rule of thumb is: update nightlies without wipe. if you got issues (some stuff not working like it should - but works for others), wipe dalvik cache and cache first, if still those issues, you have to do a full wipe. from my experience, that doesnt happen often.

about the bat-fix: well, you have to flash it after each nightly. nothing else is touched / needs wiping / needs reinstall.

yeah! a big thumbs up for this great changelog! a great thing that was totally missing (:

the "rule" usually is, you can flash them all at once without reboot. the only exception i personally know were some wierd things for leedroid on bravo - but that is long ago. if the zip file doesnt say "reboot once first" in bold letters, you should be save to flash it in one cycle. since you for sure do regular nandroid backups, there is nothing to worry about.

what you describe sounds like background apps to me. but for one, i personally think 8% in 8hours is more than okay. when i run through the night with wifi enabled, so my background apps can access the inet, i take 1-2% an hour. when i switch wifi off (or kill all background tasks), i end up like you - about 1% an hour.

i dont think, #7 behaves worse than #5. proof me wrong, but from all what i know, #7 is superior to #5
[Desire HD Android Development] off centre:
8% battery loss in 8 hours on standby? How is that too much? You will probably find that you won't get much better than that mate :) I'm sure others here will back me up on this.

I had a look at your log and while the drain seems a little bit inconsistent, I wouldn't be worried about that dude. Personally, 1% loss per hour on standby is the best I have ever had... Mine is usually a tad over 1% per hour actually..

What were you expecting? Have you ever had better than this previously? If so, please tell me how you did it, I'd like to know. :D

Edit: See? Mad-Murdock has confirmed this also. :) Don't worry about it c_felge, your battery drain is quite normal.
[Desire HD Android Development] 1234568:
@Mad

You mentioned that you had a solution to the workaround currently needed in #7. Will it require a lot of work to get it running?

Also a personal question you don't have to answer... how many hours do you work on CM7 a day? Is it part time hobby or full time work for you?

Keep up the good work!