yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ro_explorer:
Of course ... I can not imagine anyone asking such thing. Anyway, there might be the situation that some configurations in the kernel source, that have changed over time, where the gain is negative. I'm always keeping older versions of kernels so I can recreate test conditions and make a point from my statements.

I've long past the test conditions where the feedback is something like "I feel that this kernel is different than the other" or "I gues"".. "I think..." "I believe" ....

If you want to test for a fact certain things, then you have to recreate the test conditions and you have to be able to reproduce the problem (if any). After that you can say :"I KNOW that there is an issue with this or that".

I'm currently charging my phone running nov 16th version :) ... I'm very anxious to see the result of 24 hours usage.
[Nexus S Android Development] casca:
and what will be your test conditions? deep idle on or off? max freq on or off? what rom?
[Nexus S Android Development] ro_explorer:
Ok .. let's put MY test conditions:

- STOCK 2.3.6 rom (the original odexed one) with root access and CWM installed.

- no UV - standard voltages

- no OC: liveOC = 100

- governor: conservative (so the screen off freq. is irrelevant, being active only in lazy gov.)

- 100 - 1000 frequency range

- BLN ON

- deep idle - ON (until today when I've set the deep idle OFF for test purposes).

- no task killers

- low-mem settings (when allowed - not the case with nov 16 apparently): 4-8-10-16-24-32 MB (I got BEST perfomances with these settings)

My battery used to last about 24 hours with medium usage and ~48 with light-medium (using stock kernel). It is obvious that Franco's work improved that usage quite a lot and it also brings some additional stuff that I'm really using (cifs and tunneling) so ... let's maximize this kernel :).
[Nexus S Android Development] :
Trying the 16th Nov test, normally when i boot the first thing i do is open the exit the camera. this usually causes adw ex to redraw all my widgets with shrunken fonts. Didn't happen this time.

I9020 oxygen 2.3.1

Sent from my SNES
[Nexus S Android Development] casca:
So you were using stock rom!?

damn...I thought you were also using oxygen...

so you are going to test with 16.11 with deep idle on or off?

I've just noticed something...usually with netarchy and matr1x kernel, I've had ondemand governor and with Franco's I've kept using Lazy, since it was the default one! Oh well...will test with deep idle off untill the end of the day, and tommorow I'll use ondemand once again to check.
[Nexus S Android Development] Cybergr:
I agree 100% with u, that when u updating Windows for sure there is no need of a cold boot but for a simple reboot.But in my post I didn't even mention Windows OS or whatever OS, I simple said upgraded PC and all I meant was PC parts like Ram - Hdd etc.

Ok, when we updating or flashing something new on our android devices ( Rom - Kernel in this case) generally a warm boot will be ok, but I personally prefer doing a cold boot and remove the battery too just to remove any electrical - power contact.There are absolutely no genaral need to removing it, but as u said there is no harm at all.
[Nexus S Android Development] casca:
this is CFS right?
[Nexus S Android Development] Cybergr:
Franco, ur latest 16.11 kernel supports those 2 mods from 15.11 release?!

- Changed colors, courtesy of morfic

- Added Ezekeels "crap cleaner" during kernel flashing
[Nexus S Android Development] ro_explorer:
There were no BFS builts at that time.
[Nexus S Android Development] waterface:
Just clicked the beer button, franco. Have one on me.

Testing your last test kernel with deepidle off.

Will report back.
[Nexus S Android Development] casca:
Tks for the info.
[Nexus S Android Development] spyderman33:
Are u using CFS or BFS kernel?

I have the same ROM but want to check which version is working best for you.
[Nexus S Android Development] franciscofranco:
Ok, been testing this last 11/16 test kernel and so far everything is smooth, lag free, data/gsm loss free, excelent battery with deep_idle disabled.
[Nexus S Android Development] y3mita:
Franco, I was using latest Nov 13 BFS kernel and everything was fine until I decided to stay off from WIFION for a while to test the data issues!

Big sad surprise, I lost my HSDPA connection and it was set to UMTS forgot what it means but I believe is for 2G connections only *forgive me for not knowing*

I ran it for about 30 minutes and it stayed the same, I tried Airplane Mode off and on since this is usually a fix for network problems but it did nothing!

So, I went and flashed latest test build Nov 16 (somebody asked before and I confirm that *cleaning* is incorporated in this kernel) and this time I did not reboot my system... I powered off, removed battery for two minutes and then powered on my device.

To my surprise, my network settings did not change I still was not able to see a 'HSDPA' connection as my phone always do. I was about to get upset! but decided to let the phone idle for a while and check back in a couple of minutes and in fact it eventually changed to HSDPA this time. I was happy about it.... but only for a few minutes as it turns out my phone reverted back to UMTS.

I have been checking my about phone for the last ten minutes and phone changes networks back and forth from H to 3G or what it is the equivalent from HSDPA to UMTS

My settings thru NSTOOLS are:

BLD - BLN - DEEPIDLE - SCREENOFF_MAXFREQ are set to OFF

Touchwake is ON

LOC set to 110

Min-Max: 110-880

Governor: LAZY

Voltages: 900-900-1000-1150
[Nexus S Android Development] ro_explorer:
Indeed .. great battery on nov 16 with deep_idle disabled. I didn't went to bed yet but I can tell there is something great about the battery :). No other problems what so ever. It seems that you were right about the Oct releases not enabling deep idle.

Still, I cannot help not thinking .. why then all the fuss with deep idle? Why is NOT saving battery in stand-by mode?

I understand that is a proven fact that it will truly save battery while listening to music with screen off (as an example) ... so I think it should be tweaked not to kick in unless there is an active process which triggers something. What do you think? It can be implemented in this way?
[Nexus S Android Development] polobunny:
Ezekeel has found the problem for battery drain in sleep state, he posted a test kernel in his GLaDOS thread. All will be fine in a short while. Hopefully I can make deep idle work on my phone too! :D
[Nexus S Android Development] Ezekeel:
Slow down, I never said that I did solve the problem. I just pinpointed the issue and changed something in the code that could potentially have caused that. We know whether or not the problem has been solved tomorrow after people have tried the test kernel over night and give feedback.
[Nexus S Android Development] polobunny:
Wanna bet you'll fix it anyway? :p
[Nexus S Android Development] franciscofranco:
I'm gonna try Ezekeel's new fix and see if improves it, doing what it's supposed to do!
[Nexus S Android Development] frenccw:
So far so good with the test build, no loss of network connection woot! One other thing i must commend though, is that since the past few updates i havent got any SODs anymore! Franco....you are genius :cool: thanks for everything
[Nexus S Android Development] Cybergr:
+1 from my side too..I am on 16/11 since yesterday evening and so far everything seems to work as it suppose to work..!!
[Nexus S Android Development] franciscofranco:
New test build is up. Only one change from the testing build I released some hours ago, the new deep_idle patch to fix the extra battery drain when using deep_idle in the previous versions. Please this it and post feedback here and in Ezekeels kernel thread, thank you.
[Nexus S Android Development] Cybergr:
I am in on this.. ;-)

In ur download FTP server i suppose that the latest is : franco.Kernel.16112011-cfs-test.zip ??
[Nexus S Android Development] franciscofranco:
Yes exactly.
[Nexus S Android Development] some_random:
so this has the fix that Ezekeel just released in the glados thread?
[Nexus S Android Development] XxSilent22xX:
11/16 just gave me a radio dump. 11/13 has been working fine but 2g to 3g switch would take a little long, I only tried the test kernel because I heard something about a color fix a few pages back lol.

I was browsing xda via tapatalk when this happened 3g icon went white then vanished, signal came back with out reboot dbm seems strong.

Deep idle - off

volt - stock

Gov - lazy 400/800

Radio - kd1

Sent from my Nexus S
[Nexus S Android Development] Cybergr:
Yes, it has it! ;)
[Nexus S Android Development] some_random:
ok sweet i shall have to give it a go :D
[Nexus S Android Development] got2best:
I am noticing that top on is activating even when Bluetooth isn't on.. is this right? (On latest test build)
[Nexus S Android Development] some_random:
have you got wifi on... anything else?
[Nexus S Android Development] Lalaca:
A few fixes ago, vibration was also added to TOP=ON, to address issues of short or weak vibrate notifications.
[Nexus S Android Development] y3mita:
Yep TOP=ON and TOP=OFF both report usage. I was listening to music with phone off and turned on screen to check tweeter so I guess it's normal.
[Nexus S Android Development] from1989:
about the 16 test

i have face 8 times reboot since i flash it this morning!!!! o my god
[Nexus S Android Development] some_random:
yes thats normal even if your not using bluetooth as Lalaca said vibration has also been added to top=on so its not surprising that there is time spent there as well
[Nexus S Android Development] Cybergr:
Then obviously something u didn`t done in the wright way..try wiping cache/dalvik (for dalvik use morfic`s dalvik wiper) and flash again!
[Nexus S Android Development] franciscofranco:
First, that report is ****, provide an useful report if you want your issue looked into.

Second no one reported that kind of problem so 99% chance it's your problem, if you OC/UV you're on your own.
[Nexus S Android Development] y3mita:
8 reboots?? you did something out of the ordinary... always make sure you wipe caches before flashing a new kernel *even though this kernel has some cleaning incorporated* I still do :)

And try default values first, do not UV-OC etc.... just leave it be. Then work your way up!
[Nexus S Android Development] some_random:
what were you doing when it rebooted have your changed anything like voltages or oc? as others have already said it is assumed that you wiped both cache and dalvik
[Nexus S Android Development] y3mita:
Well after a few hours of trying latest test build! I guess Ezekeel just fixed the bug! Battery life is rocking sweet!!!
[Nexus S Android Development] from1989:
all by default not do anything
[Nexus S Android Development] laidick:
Cfs
[Nexus S Android Development] some_random:
what rom were you running?
[Nexus S Android Development] from1989:
miui latest chinese version
[Nexus S Android Development] ro_explorer:
MY test conditions:

- kernel - nov 16 first test version (before the deep_idle bug attempted fix).

- STOCK 2.3.6 rom (the original odexed one) with root access and CWM installed.

- no UV - standard voltages

- no OC: liveOC = 100

- governor: conservative (so the screen off freq. is irrelevant, being active only in lazy gov.)

- 100 - 1000 frequency range

- BLN ON

- deep idle - OFF

- no task killers

- low-mem settings - user setup NOT ALLOWED (Franco, please let me set my min-free values).

- data on, 3g-auto, wifi used only when high-speed data is required, sync on

Overnight drop (this is what I was testing): 3% over 7 hours. Great ... I can move on peacefully to the latest kernels and forget about the "old" ones.

So ... now let's start testing the deep_idle fix.

As usual, I'll report back my findings.
[Nexus S Android Development] mike216:
So there's 2 different 16th test versions

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] ro_explorer:
Yup .. first one was released to fix the data drop, second was released about 10 hours ago to attempt to fix the deep_idle batt. drain bug.
[Nexus S Android Development] kalinusa:
I AM RE-POSTING AGAIN WHAT I MENTIONED AS A BUG 1-2 WEEKS AGO and NOBODY PAID ATTENTION

!!! PROBLEM HAS NOT BEEN SOLVED !!!

Interestingly when I use the Ezekeel Glados 1.6 kernel the issue does not exist. IT IS A KERNEL ISSUE. I do not think it is related to the latest deep-idle bugs people are talking since Ezekeel is good.

HERE IT IS:

------------------

I have noticed an interesting issue. Please help.

At work when the WIFI is ON the phone cannot get into DEEP IDLE.

I tried this with CM Nightly Latest and also Brainmaster's MIUI

when WIFI IS ON, the PROCESSOR lingers in the lowest frequence

The moment I turn OFF the WiFi then DEEP IDLE happens.

Interestingly, this only happens at my work WIFI not at my home WIFI.

Any suggestions? I installed Brainmaster's MIUI because I thought it was CM Nightly Issue but i guess not.

I have not opened a single app and it is doing this. But only at work.

-------------------
[Nexus S Android Development] ro_explorer:
Ok .. I'll play the jerk now:

Very useful bug report .. especially because you gave the work wi-fi configuration and home wi-fi configuration.

B/G network? both? any encryption? if yes, which one? which type? is it WEP? ... or maybe WPA? or WPA2? Personal or corporate? TKIP or AES? or both? 64 bit key? or maybe less .. or more ?
[Nexus S Android Development] caleb1783:
guess ur work wifi is extracting data from ur phone... which is y ur phone cant didle...

but on more serious note... sounds like ur wifi configuration to me... can u get us details on that?

Sent from Divinus Nexus S...
[Nexus S Android Development] Heretic Infidel:
I did exactly the same thing as you did last night except i turned of my 3g as it shoddy to reduce antenna usage. and my cpu settings are 400/1000.

Rom : CM 7.1

Kernel 13-11

Deepidle : OFF

Governor : Smartass v2

charged too 100, slept 9 hours.

Got 20% battery drop, 65% via mobile standby. Looking at the battery graph my phone woke up multiple times during the night?

65% mobile standby

26% phone idle

4% display

4% android system

Edit : Changing to newest test build, will do the same thing during the day with deep idle on.
[Nexus S Android Development] ro_explorer:
I recommend to flash again three radio. I heard in some cases it helped.

Sent from my green robot ...
[Nexus S Android Development] ro_explorer:
After posting the above I experienced a radio dump. Damn.

Sent from my green robot ...
[Nexus S Android Development] mike216:
Deepidle is only used while music is playing and bluetooth use its not a mod that's activated during normal use and sleep conditions, thanks franco for explaining this to me and like I was I'm sure many had this deepidle mod confused

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] mike216:
I had some issues with deepidle in past versions but the latest bug fix

Is working fine! The latest is good to go or you can disable deepidle and get great battery life if your on an older test release

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] casca:
ok so I've got the latest test kernel 16.11.11, but I was reading a bit about deep idle and couldn't understand it very well...

so deep idle will be enabled while using bluetooth or listening to music right? what a wireless connection ? will it be enabled in that situation?

tks
[Nexus S Android Development] uansari1:
I've noticed something over the past couple kernels, but only with deep idle enabled. I use the pattern unlock, and I've gone to unlock my phone after its been sitting for a while, only to see the message telling me to try again in XX seconds. As if I'd entered the wrong pattern three times. Anyone else?
[Nexus S Android Development] Heretic Infidel:
I'm not getting that exact error seeing as i don't use pattern unlock. But what i am noticing is that my phone is waking up in the middle of the night even while the battery usage meter is saying no applications except my standby radio have been running all night.

I can't pull any conclusions from this as my knowledge of the system, roms & kernels isn't deep enough. Someone able to enlighten us?
[Nexus S Android Development] uansari1:
I haven't noticed anything like that..though I am occasionally experiencing instances where I go to unlock the phone and find that when I press the power button, it just opens to my homescreen completely bypassing the slide to unlock or pattern unlock if that's enabled. The phone is completely frozen, but haptic feedback works when I tap a capacitive button. I have to pull the battery to restart.

I'm not sure if it's related to liveoc or deep idle, so I'm testing just deep idle without liveoc right now to see if I can narrow it down. This specific issue did not occur with the 13.11 stable build.
[Nexus S Android Development] chinopski:
Im having the greatest battery life on the nov 8 kernel
[Nexus S Android Development] Flying Fox:
That´s not much of information. Have you compared it to the latest test-release or what?
[Nexus S Android Development] jark99:
Franco i keep getting a screen on problem. Ill be away from my phone and miss a call, my screen then stays on until i manually turn it off. Same happens if playing around and set the phone down....the screen just stays on.

And yes ive checked my screen on off settings
[Nexus S Android Development] casca:
I'm very sorry you guys, but I simply have to share my frustration.

Don't get me wrong as I appreciate all the work from all developers,but my only conclusion so far is that if deep idle was a nice feature Google's developers would of have implemented it already when they launched their software.

The best battery life experience I have had was with ondemand governors and Netarchy's kernel (stable, not the test version) without deep idle.

Even with the new test version from Franco(16.11-test), I'm getting more drain with deep idle enabled than with it disabled.

Every single kernel I've tried with deep idle enabled either from Franco, Netarchy or Matr1x, turned out the same exact thing, if enabled it would drain more than disabled.

Before anyone comes up with theories, I've made fresh installs with oxygen 2.3.1 and 2.3.2 and we all know what kind of developer AdamG is, when he does something, he just does it right, so I honestly cannot even think of a rom issue.

On the other hand you could tell me maybe I have some application draining my battery...nope, I've checked every freakin thing I could remember, done logs, used system apps to check, you name it, no drains from the apps whatsoever.

I know several people posted their POV's and show their graphs and all of that, but damn, I've had an HTC Hero, Legend, Desire and now the Nexus S that has the strongest battery of all the phones I've had, and indeed I saw improvement but it was to simply last till the end of the day without medium use with the Nexus S.

I honestly cannot understand how some users have with a single charge even more than 24h(not a "normal usage" day) with either wifi enabled or 3g data on for instance.

I'm sorry for all of this long speech, but I'm a bit frustrated here as my phone is off charger from 6.45AM, it's been running for 7h42minutes and it has 37% of juice left and!, because I've disabled deep idle when it was about 8:AM or so and changed governor, so if anyone has any ideas on what could be happening here, let me know.

I don't believe I turn ON the damn phone more than you guys, do you?

I'm sorry once again for all of this long speech, but I'm honestly hoping that someone will reply with the same frustration so that I can check I'm not crazy...well, at least not THAT much :)

best regards to you all

(thanks for all your hard work Franco!)
[Nexus S Android Development] caleb1783:
dont be fooled by those images... they barely touch their phone + 8 hours of sleep...

as for me, i unplug around 7:00, have 3-4 hrs display on time. and by 11 pm, i will be at 30%

That was when i was using older version of matr1x kernel.

as for you, if you turn on the didle once, even if you turn it off, the bug will still be there (according to ezekeel's post)... i dont know if restarting it will fix the bug or not.

but if i read correctly, franco implemented the latest bug fix that deals with didle battery drain...
[Nexus S Android Development] Cybergr:
Deep_idle turned out to be a little bit buggy (not 100% ready)..Ezekeel and Franco

knows about that and working on it..Yesterday Ezekeel released a possible fix and Franco implemented it on his latest 16.11 test kernel which i am actually testing since from yesterday.

PS : I will post my thoughts and results later today..
[Nexus S Android Development] casca:
Yes I know, but I've even flashed the latest test version, and after booting again, same thing, drains more than it helps lol

I'm simply fresh installing stock oxygen 2.3.2(again).

If Adamg hasn't implemented a kernel with deep idle yet, then I'm assuming he has a reason for doing it.

Two ways for thouching my phone again...

#1 ICS comes out

#2 Adamg releases a new version of Oxygen

I'll try and enjoy my Nexus S before I sell it and grab myself a Galaxy Nexus next month lol
[Nexus S Android Development] polobunny:
The biggest battery saving I got was from undervolting, not just from using X or X kernel.

Doing nothing at work (6-7ish% over 12 hours):

My settings:

Deep idle isn't meant to save you battery life when you're gaming, it's meant to save you battery when your phone cannot enter sleep state when the screen is off, the most common example being listening to music.

Hope it helps you.
[Nexus S Android Development] casca:
this is exactly what I think my friend. Undervolting is way nicer than everything else.

My phone simply won't last even in standby with any of these kernels that have deep-idle.

Can it have something to do with having lots of apps?! although none of them is draining?
[Nexus S Android Development] got2best:
I am on the latest test kernal and I noticed my alarm hasn't been going off after sitting for a while.. any1 else having this problem?

Nscolleb

I9023
[Nexus S Android Development] polobunny:
I wouldn't think so, I have around 150 apps and as long as they're not running in the background you should be fine. I know some games are notable for having background services running (Glu Mobile for instance) without the user being aware, but if you check your stuff all should be alright.

Deep idle has/had a bug that would drain the battery when entering normal sleep state, Ezekeel is aware and already testing out solutions. I have deep idle disabled at most times by default, I only enable it to test out the patches. I don't feel like it has a use for me considering my usage, and some bugs (like BT bug) kept me from having deep idle enabled all the time.
[Nexus S Android Development] casca:
thank you for your patience and feedback.

I indeed have no apps draining so...

tks once again
[Nexus S Android Development] damnmisur:
I've been getting reboots with this test. All kernel settings left at default. Clean ROM install. Wipe of cache/ davlik and used morphic davlik wiper. Currently running matr1x 1.5 rom. Reboots happen when phone is not in use and will reboot continually. Wi-Fi on no mobile data. This is regardless of settings.

Sent by my Nexus S 9020a on Telus running the flavour of the day.
[Nexus S Android Development] Sykkr0:
I had the exact same problem for the last 2 days with the 13Nov release, 1 to 2 occurences per day.. i think i had deep_idle turned off, but not sure. Flashed the latest 16Nov test kernel and no problems so far, but it's too early to be 100% certain. (with MIUI ROM 1.11.11)
[Nexus S Android Development] y3mita:
Im not getting that, running carbon ROM here and WIFION most of times.