yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] loudaccord:
no reboots here in 15 hours on v2.5. I don't use LiveOC.

no deep idle though. Not sure it would matter, my battery is doing pretty amazing. I'm not going to say what % I'm at after 15 hours, you guys wouldn't believe me lol
[Nexus S Android Development] mikkkg:
To be more specific, i get random reboot while using both 2.4 and 2.5 cfs.

From all the extra mods i am using bln and voodoo. Nothing else.
[Nexus S Android Development] alienmind:
NoLED users the whole lcd on, right? BLN uses only the backlight of the buttons, and that's far less power consuming. Besides, probably there are lots of workarounds but this is about reporting a bug. BLN is a feature of this kernel that I would find interesting to fix if it turned out to be buggy (which I can't confirm just yet, this is only a suspicion)

Swyped from my Nexus S

EDIT just to clarify, I haven't tested NoLED I posted according to its description on market
[Nexus S Android Development] CrackDaddy:
Good to hear, gonna stick with 2.4 for now with my previously stated settings (min-110/max-1100, deepidle on & lazy governor with screen off max freq on!) & see how it goes! If I get any reboots the I'll be joining you on 2.5 with all stock default settings, & giving deepidle a wide birth, as I'm getting real peeved with flashing suitable roms/kernels now, just to have smooth & fast daily use of my lovely nexus s!!

---------- Post added at 02:37 PM ---------- Previous post was at 02:23 PM ----------

I understand exactly what you're saying, & yes it would be nice to have these problems all ironed out! But just for now, using NoLED is a good alternative when you consider how often you really do have missed notifications of any kind! & also you can't see a phone blinking OR static if it's in your pocket anyway! At least with NoLED, ok you may not be just using the backlight notification buttons, but you're more likely to not miss ANYTHING much, when you consider it's moving icons/vibrating/ & playing any notification sound of your choice!! Battery saving goes out the window really because you're adressing the notification a lot sooner in any case! :-)
[Nexus S Android Development] sperelli:
Hi there,

I've used this 2.5 (and preceeding) for a while, in combo with NexusBeam 4.1.

Two bugs on BLN mod:

-if u unlock the phone in the off-interval of the blinking, it stays black till the next lock/unlock.

-no clean behaviour on missed calls... (have to force somehow with neldar pro app)

can those 2 issues be fixed?
[Nexus S Android Development] niteh@wk:
Don't even need to remove the bootanimation from the zip. I don't wanna see the word "dirty" in the kernel description in About phone if I remove the animation. Just install Rom Toolbox and flash one of the many animations it has.
[Nexus S Android Development] marinierb:
Huh? Mine doesn't say that. And I removed the entire /system/media folder before flashing.
[Nexus S Android Development] simms22:
yesterday i tried both bfs and cfs of v2.5, both run fabulously. not a single issue with performance. but neither wireless or wired tether worked with them and the stock/rooted rom im running. i also tried different tether apps as well as the native tether options. but, on a good note, i also tried eugene's kernel. and GLaDOS runs circles around it! too bad tethering didnt work, thats something i need on a daily basis since i dont have internet at home. overall ezekeel, im very impressed :)
[Nexus S Android Development] CrackDaddy:
I'm now on cfs v2.5 with NexusBeam v4.1.0, & wireless tether works just fine & is picked up nicely from my Dell XPS M1530 laptop! :) What rom are you using? maybe it's something to do with OTA ICS stock (If that's what you're using!?)
[Nexus S Android Development] simms22:
and the funny thing is me dell xps m1530 just recently died :(

i got an error message when connecting wirelessly natively and with the wireless tether for root users app. and with the wired tether it just endlessly tried to connect. i can tether with the stock 3.0.8 kernel and trinity without issues though. ill just have to try harder i guess knowing now that it works. maybe some more problem solving on my end is what is needed ;)
[Nexus S Android Development] Icecoldmeat:
Got random reboots when applying LiveOC (at 110%)....

Sent from my Golden Nexus S.
[Nexus S Android Development] CrackDaddy:
& your rom?? like I said before, maybe it's something to do with that!? Sorry to hear about your XPS m8, if it died coz of overheating (known graphics chip problem with these!) try thermel pasting it, which is what I did when I baught it 2yrs ago, & have monitered the GPU temperature since, but stays a nice & cool 53-65 degrees even when benchmarking hard! (Sorry for being off topic, lol :D) Lovely machine ;)
[Nexus S Android Development] stewarta:
GLaDOS 2.5 and Deep Idle

I seem to be having no operational problems. One oddity is that when the governor is set to Lazy I do NOT get deep idle but when set to On Demand, I do and get such as the stats below. Max 1100 Mhz, Min 220 Mhz, OC 110% ... but the Idle Stats show LAZY.
[Nexus S Android Development] simms22:
i bought mine in the begining of 2008, it lived and served its purpose well. it was its time. it actually still works, if i connect a monitor to it. its the screen that is actually fubar.

rom.. im using the official ota of 4.0.3 with root. maybe it is the rom, thats a possibility. but i havent had an issue with any other kernel when tethering(i think i tried them all now) except with glados. anyways, i will try again until i get it working, now that i know its working for someone else.
[Nexus S Android Development] CrackDaddy:
Try troubleshooting/diagnose in windows when connecting & be patient! & also don't forget go to properties of connection & put in your network security key according to the new one youve made for your tether connection on your device, good luck!
[Nexus S Android Development] niteh@wk:
I flashed 2.5. It's been going for 20 hours now without reboots. No OC, everything is stock or kernel defaults, even voodoo colors. Only thing I turned on is the BLN. I'm going to OC it to 1.2GHz and see if it'll start to reboot. I'm trying to eliminating possibilities of reboot causes.
[Nexus S Android Development] CrackDaddy:
Don't forget, if you're overclocking, make sure you adjust voltages accordingly, or you'll not only incur reboots, but SOD's also! ;) Also GlaDOS v2.5 kernel is min freq/100mhz, normal stock min freq is 200mhz!
[Nexus S Android Development] sspikey:
how do you adjust voltage when overclocking?
[Nexus S Android Development] CrackDaddy:
Use NSTools, SetCPU or Proton Voltage Control & search this site for instructions/percentages! ;)
[Nexus S Android Development] mike216:
Alpha 18

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] krex:
GlaDos 2.5 with stock ROM, no OC, no UV, no BLN, no special apps, no incoming notification, deep_idle on -> reboot within half hour
[Nexus S Android Development] CrackDaddy:
Now try min cpu freq/200mhz, ondemand & turn deepidle off! :D
[Nexus S Android Development] IIIV:
App drawer is a little bit laggy opening with Live OC at 105%. So, I decided to bump it up:

Governor: ondemand

Live OC: 110%

CPU: 220/1100 MHz

Deep Idle: off

Voltages: +25 across the board

The result: no more app drawer lag(!) Also, NO reboot on phone calls lasting more than 2 minutes.

I9020T with GLaDOS 2.5 BFS over Brainmaster's Stock ICS 4.0.3
[Nexus S Android Development] CrackDaddy:
Now try it with deepidle on, but with Lazy governor & screen off max freq / ON! ;)
[Nexus S Android Development] IIIV:
Just had a reboot during a phone call with these settings. That was quick. :eek:

Going back down to 105%.
[Nexus S Android Development] aharen:
Just flashed the kernel, very smooth and stable..thanks dev :)
[Nexus S Android Development] nexusphone:
Ezekeel will get rid of worms ;)
[Nexus S Android Development] caleb1783:
it doesnt make sense though... deep idle is not working on 2.5?

or maybe cuz your are using stock rom, didle works and cuz problems...
[Nexus S Android Development] niteh@wk:
Thanks for the advice. I OC'd it to 1.2GHz for the last 3 hours now. Everything stayed defaulted. No reboots so far. I'll keep trying one thing at a time until I find the reboot trigger lol. 2.5 seems pretty stable compared to 2.4 where I had multiple reboots per day.

Update: almost 26 hours now and no reboots. 1.2GHz, everything else at default settings, voodoo colors set to samoled settings. 2.5 is doing great. Phone is snappy and smooth.
[Nexus S Android Development] shubu000:
just tried liveoc 110% on eugene's 3.1.6 kernel

no reboots about 3 and a half minutes,

but that kernel doesn't have lazy so i can't isolate whether it is liveoc or liveoc+lazy governor.

maybe Ezekeel or anyone with advance knowledge can compare the two sets of codes?
[Nexus S Android Development] got2best:
He said he forgot to input the patch to get it to work and it will b fixed in the next version
[Nexus S Android Development] krex:
That will be the next one :)

But I left as it was, so far (>7 hrs) no reboot with same settings and deep_idle on!

Though now I'm reading, deep idle isn't going to work in this version because of a missing input patch.

Then I don't know why I had reboot...
[Nexus S Android Development] stewarta:
Deep Idle and GLaDOS 2.5 >> 2.4

Yes ... I dropped back to V2.4 and now have Deep Idle and a bit more battery life from my 1750Mah batteries.
[Nexus S Android Development] AnthonyAldrete:
Is there a reason why it only allows me to charge the to 97% instead of 100%. I downloaded nstools and tried to raise it but it won't let me . Is there a fix for this ?
[Nexus S Android Development] CrackDaddy:
Only thing I can think of is having it ondemand & 200 min cpu freq / 1000 max cpu freq like stock is supposed to be!?

---------- Post added at 11:33 AM ---------- Previous post was at 11:15 AM ----------

GlaDOS kernel doesn't implement the change because it's purely cosmetic! Hardware on a nexus s won't allow above 95% to save battery life/damage!
[Nexus S Android Development] AnthonyAldrete:
So I'm not really loosing battery by it only charging up to 97% is that right ?
[Nexus S Android Development] renna1992:
exactly :)
[Nexus S Android Development] Harbb:
That's correct Anthony. Around 95% - 97% is "fully charged", the battery itself is capable of being charged several millivolts more - though the general consensus is that the life of the battery is cut short dramatically at this upper limit. Most other phones (and kernels) just replace the 95% with 100% to for peace of mind.
[Nexus S Android Development] CrackDaddy:
Not at all, that's how a nexus s is supposed to show! The 100% settings in NSTools like I said previously, is purely a cosmetic feature, so that's why GlaDOS doesn't let you implement it because it's a waste of time! JUST EYECANDY is all! ;) Mine even shows 98% when fully charged, but I know nexus hardware will save battery life/damage & not fully charge to 100% ever (even if 100% is what I visually see on my phone!) because the hardware makes it physically impossible!
[Nexus S Android Development] ArnoutVos:
Yesterday I flashed GLaDOS 2.5 CFS.

This morning I saw the following idle stats. I started Firefox Beta, using it for a while:

I charged the battery fully and disconnected just before sleep. The battery discharged rapidly this night. I think this is the ICS Nexus battery drain bug? I'm using Nexus MV 2.12.25. Especially the last third of the night:
[Nexus S Android Development] loudaccord:
deep idle isn't working but it doesn't look like I need it.
[Nexus S Android Development] metalgear873:
I think deep idle is a thing of the past, ics is really good at preserving battery while idling. Well that's my experience.

2.5 is also giving me problems whole making phone calls, back to 2.4
[Nexus S Android Development] jordivf:
In the past two days I've had three hard crashes which are rather troubling:

Phone crashes and reboots. When you go to battery stats after thi hard crash you notice it has lost all stats for the past 3 to 7 hours (depending on the crash).

SU log hasn't been helpful either.

I've had those with BrainMaster's ICS + GLaDoS 2.4 and with CM9a18 + Eugene's Kernel.

kmsg is 0 b

lastkmsg some 670 b

If someone directs me on how to get a logcat I'll provide one.
[Nexus S Android Development] krex:
Please explain me, why we have so weak results and points in benchmarks under ICS...? ...when we have so many mature "ingredients" and perfect devs!

These are half of I had under Gingerbread. :(
[Nexus S Android Development] loudaccord:
It's the benchmarks, not the ROMs/Kernels. They aren't optimized for Android 4.0
[Nexus S Android Development] metalgear873:
I don't see any reason to benchmark anyway, its just for reference.

I'd rather see some fps benchmarks in games, how long it takes the phone to boot, or any other real life benchmarks
[Nexus S Android Development] t3xboar:
benching just gives you a general idea. I did the kernel compares in the beam thread.

in the bench if you pay attention you can see as it's going through each test where it suffers the most.

in eugenes for example it owns everything in the 2d-3d tests pushing a good +15-25fps over all others but is ass slow in everything else...in the glados in 3d it does fine, but suffers in the 2D pulling down the overall bench score.

its all relative anyways. depends what each person is doing to their own phones.

I will throw the ball to this kernel though. im running 2.5 cfs and its excellent. bat life just hit 12h with 65% left on light usage.

Good job on the kernel !
[Nexus S Android Development] krex:
For me the CPU value is lower always than it was under GB... E.g.:In Smartbench -20%, in Quadrant - 40%... :(
[Nexus S Android Development] mmor101:
What's the performance and reliability difference in BFS vs CFS?
[Nexus S Android Development] shubu000:
from my experience, there are little to no difference between cfs and bfs.

in the hands of a capable dev, like the ones we have in this forum, the two are just as fast.

that said, from experience, BFS will likely be the one that has kinks in the code since the source from google is cfs, (please correct me if i'm wrong).

however there is nothing to fear, from my experience, ezekeel's bfs kernel's great, i'm on it now. morfic, who is an awesome dev, only does bfs, so yeah i'd say give bfs a shot and no need to worry about it if you want to try it. even if anything goes wrong cfs is only a flash away

hope that helps
[Nexus S Android Development] Ibn Saeed:
Thanks, ill keep that in mind.
[Nexus S Android Development] debbio:
Does this kernel show the idle stats? cause in my case it doesn't... but it's enabled (I see it throw cat command which answers 1)
[Nexus S Android Development] caliban2:
yeah, it does.

the numbers are just way lower compared to morfic's kernel. i asked about this some pages back already... looks almost like deepidle kicks in less often. 20% batt-loss during 5 1/2 hours standby aren't good neither. on the other hands cpuspy shows as much deepsleep as i'd expect with morfic's kernel?

i activated max_cpu for lazy-gov, to see if it makes a difference. looks like it doesn't. maybe ezekeel can shed some light on it.
[Nexus S Android Development] got2best:
Another reason is if you have gtalk that supports video calling.. (check first page.. first post read all of it.. it will explaing) to get deep idle to work we need to turn the camera on then off and check them agian after screen is off.. you will notice they work.. hope this helps
[Nexus S Android Development] Ezekeel:
Other i9023 owners also having trouble with BLN or BLD?

You definitely should do that. Franco is a very capable dev and probably more than happy to answer all the questions you might have. :D

What is that even supposed to mean when you say it does not show the idle stats? The stats table is not shown at all? The times for all idle states are zero? The times for the two DEEP IDLE are zero? Can you please be more specific, because otherwise your feedback is totally useless.

The numbers depend on which DEEP IDLE version including which bugfixes morfic has included in the kernel you tried before. I have decided to sacrifice a bit of the DEEP IDLE efficiency for a flawless user experience. However the battery consumption you are experiencing seems unusually high. Do you use the BFS or the CFS version?
[Nexus S Android Development] caliban2:
not using BLD, but BLN works fine for me since v1.0 (didn't get this "only one button lights up"-thing)

great, why do i even care to keep my sig updatet?! people just don't read anymore these days... :p

nah, it's cfs. bfs gave me the loss of connection-bug.

yeah, those 20% were a bit high, kinda like stock-kernel. ^^

i'm sure it has nothing to do with apps or sync-schedules - those are the same as always. but i'll disable data-connection tonight (not flightmode) and see what happens.

(i'm not really complaining - your kernel is perfectly stable since v1.0 for me. that's a first and counts 10 times more than "only stock batt-life")
[Nexus S Android Development] Mecid8:
Please add Jhash3(https://github.com/netarchy/nexus-s/commit/665cd5dc159970027a724217461c2515c490e616.patch and Tiny RCU (http://lkml.indiana.edu/hypermail/linux/kernel/0910.3/00366.html)
[Nexus S Android Development] got2best:
@caliban2 ..Your signature can't be read if u are looking at the post through app.. just so ya know.
[Nexus S Android Development] arifhn:
@Ezekeel

where is your default config?

is it herring_defconfig (glados branch)

thanks
[Nexus S Android Development] N@th_OC:
Thank you so much Ezekeel !!!

I was waiting for a kernel from you since a long time.

I'll test those two kernels later in the day.

Thank you again, your work is amazing.

Edit: running GLaDOS V1.2 BFS and I experience multiple reboot and freeze when I use Liveoc

Strange, BFS was always the best for me... I'll try CFS, maybe that one will work finelly.
[Nexus S Android Development] caliban2:
@ezekeel:

well, here are my drain-results in standby with data-conn disabled. i lost 14% (showed 97 when i removed the plug) in 8:40h.

since taking those screenshots i changed gov to ondemand (15000, 98%) and idle-time has almost trippled in just an hour, deepidle-time is still trickling up slowly.

am i really the only one getting this high drain in standby?! :(

one other thing that could cause this:

I'm on radio xxkf1, you're using a later base from Samsung than all other kernels here. with your kernel only (!) I'm getting one stable bar in my garage (underground), while with all others i had no service at all down there. (never had, be it nexus s or x1)

so radio seems to be more active, which would use more power.

edit:

and again radio. right now I'm in a room where i normally only get 2g. but now, as long as i don't hold it in my hands, i get 2 bars of 3g.

so what now, should i hate the power-drain or love the better signal? :D

edit2:

you never clarified, should deepidle and max_cpu for lazy be enabled by default or not? because they aren't for me.
[Nexus S Android Development] endursa:
i experience instant reboots right after bootup, doesn't matter if i flash over existing rom, or if i do a full wipe!

miui 4.11.11 -i9020 and glados 1.2!

screenoff_lazy active, liveoc set to 110 and undervolted 440 by -25!

i used the same settings before with francos kernel and it worked fine!
[Nexus S Android Development] caliban2:
jesus christ, is it really that hard to answer a simple question with yes or no?! :mad:

normally i'd take no answer as a "yes, you are", but these days...

and before someone comes with time between this and my last post - i asked the same yesterday already. :p
[Nexus S Android Development] JimmieMaul:
I've just flashed the kernel so will give it a few days to stabilise before commenting on my battery usage :)

Mobile details:

i9020 Nexus S 3G

Oxygen 2.3.1 ROM

KD1 Radio

GLaDOS V1.2
[Nexus S Android Development] FloHimself:
I guess, if no one answers your question, the answers IS "yes, you are"! No one here seems to have a high battery drain dependent on a certain radio or the kernel with default values. So it's most likely your setup that is responsible for the drain.

Ezekeel, here is another one for the initial post of the "deep idle" thread:
[Nexus S Android Development] caliban2:
finally, thx. ^^

interesting thing is that I'm able to influence idle-stats via governor. deepidle is not affected. radio kd3 didn't change anything as well.

so yeah, maybe i changed something in setup... but can't think of what. it should be smth about sync, because no new apps are installed. and then, why doesn't disabling data-conn overnight not solve it?

i had a look at logcat, there's constant freeing of men going on. but i don't know if this is normal or not. happens every 1-2 seconds.

D/dalvikvm( 1192): GC_FOR_MALLOC freed 497K, 58% free 3971K/9287K, external 1K/513K, paused 33ms
I/dalvikvm-heap( 1192): Grow heap (frag case) to 7.317MB for 1060016-byte allocation
D/dalvikvm( 1192): GC_FOR_MALLOC freed 1035K, 58% free 3971K/9287K, external 1K/513K, paused 18ms
D/dalvikvm( 1192): GC_CONCURRENT freed 9K, 58% free 3971K/9287K, external 1K/513K, paused 2ms+2ms
D/dalvikvm( 1192): GC_EXTERNAL_ALLOC freed 199K, 59% free 3821K/9287K, external 509K/513K, paused 18ms
W/InputManagerService( 186): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40871618
D/dalvikvm( 186): GC_EXPLICIT freed 175K, 40% free 6451K/10631K, external 4965K/6200K, paused 58ms
W/InputManagerService( 186): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40592740
D/dalvikvm( 804): GC_EXPLICIT freed 123K, 52% free 2763K/5639K, external 32K/512K, paused 24ms
[Nexus S Android Development] FloHimself:
The governors are "cpufreq governors" and decides at what frequency the CPU should run. Therefore, it is normal that the governor has influence on the cpu states.

Maybe a too aggressive task killer, that periodically cleans memory and keeps the system busy by restarting tasks?
[Nexus S Android Development] caliban2:
the question is why it half-fails with lazy. that isn't the case with other kernels i tried. and may i ask what your numbers are for idle and deepidle?

regarding taskkiller: none at all.
[Nexus S Android Development] FloHimself:
$>adb shell cat /sys/class/misc/deepidle/idle_stats
idle state total (average)
===================================================
IDLE 1072984ms (1ms)
DEEP IDLE (TOP=ON) 0ms (0ms)
DEEP IDLE (TOP=OFF) 1062889ms (4ms)
[Nexus S Android Development] Keyser.Soze:
2.5 has been rock solid for me. I use it with NexusBeam, NSTools with BLN on, deep-idle off, on-demand govenor. My phone's uptime is now over 61 hours. I don't think it had rebooted since I flashed 2.5.

:)

KS
[Nexus S Android Development] nexusphone:
Ezekeel WIP
[Nexus S Android Development] kokwei:
Can anyone share the URL to download v2.4 again? I could not locate it on the first post.
[Nexus S Android Development] FloHimself:
GLaDOS-cfs-2.4.zip

GLaDOS-bfs-2.4.zip
[Nexus S Android Development] Chamb':
BFS 2.4 : http://www.multiupload.com/T90CK1BY5D

CFS 2.4 : http://www.multiupload.com/DZITGH8ZSG

EDIT: too slow. :)
[Nexus S Android Development] nexusphone:
(animated gifs by leejunha32)

GLaDOS, the best! :)
[Nexus S Android Development] gouthamsn:
Any luck with USB OTG ?? :)
[Nexus S Android Development] krex:
>32 hrs no reboot with v2.5

I changed many options, OCed many times and benchmarked. No reboot so far. Deep idle have been off all along... (I don't know if it counts since deepidle can't be active in this version) ...but 1 hour is 1% battery now, so I don't need it.

So, I think it is stable, thanks for this great work Ezekeel.
[Nexus S Android Development] caliban2:
Same here, had 2.5 cfs running stable for almost 3 days. Despite bandaid missing, I had didle enabled and got quite a high number of top on, zero for top-off.

Back to 2.3 now to see how much didle really matters regarding batt-drain for me. (2.4 being unstable for me)
[Nexus S Android Development] kokwei:
Thank you. Made my day as 2.4 is indeed very much gentler on the batteries. Deep sleeps very quickly when screen goes off.