yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mike216:
Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] mike216:
The app is called system tuner pro

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] steve.garon:
But its missing important functions...
[Nexus S Android Development] Ezekeel:
If you have reboots with GLaDOS and previously experienced even more problems with the CM kernel there might be something seriously wrong not related to the kernel. Unfortunately I have disabled pretty much all logging and debugging features with V1.6. You could try the previous version V1.5.

I have posted a test kernel for NS4G owners in the 4G forum thread to investigate the problems with DEEP IDLE when using 4G. If you have a NS4G please try it and leave some feedback.
[Nexus S Android Development] caliban2:
i think you didn't understand...

voodoo needs to be enabled in cm-settings for "voodoo control plus" to work.
[Nexus S Android Development] matt2053:
There IS something seriously wrong with CM7, and it is NOT in the kernel. It's going to reboot no matter what kernel you use.Something in the ROM is broken, and has been since the alpha nightlies.
[Nexus S Android Development] y3mita:
I think you might've nailed the problem... I changed to another ROM based off Oxygen and I tried Glados 1.6 and now testing Franco's latest BFS and everything working fine so far.;... no reboots, no radio dumps, but I think the 'deep idle' mod may need some revision since I find it is not really saving that much battery!
[Nexus S Android Development] Ezekeel:
I am running CM7.1 stable without any problems, so if you want to stay with CM I can recommend that version.

Regarding DEEP IDLE, I said it many times before that it will only be used if the screen is off and some background process is keeping the device from entering SLEEP, for example music playback (also it must not be connected to USB and keep in mind the CAM bug plus there currently is a problem with 4G which will be fixed in the next version). And since DEEP IDLE will only save battery when it is actually used, you will have to test it under the above conditions.
[Nexus S Android Development] y3mita:
@Ezekeel, I meant the nightlies or Kangs version of CM7 sorry for the lack of information I provided. I'm thinking some of the cherries put into some kangs might interfere somehow.

Your kernel 1.6 is not bad, I tested the deep_idle when sleeping *my phone usually is put to rest* no activity at all, I had syncing once for two minutes every hour at night... WIFI ON and with that my stats are about 12-15% battery usage in about 7 hours of non-use..... I used to get about 1% for every hour before. What I'm saying I'm not getting the battery life as I used to.... *once again maybe is the kangs I flash that interfere*

So to test this issue I had downloaded a stable NON-CM7 ROM and even though I tested your kernel for about day and half I have now switched to Franco's NOV13 to see its performance and battery life.. and I also see the same battery stats but this is my second full battery charge so I will see what happens in a day or two!

PS> I always try lazy governor, Touchwake ON BLN OFF. undervolt 25 all across the board, deep_idle ON, 100-1000 NO LIVE OC (for now) I may OC 110 and change frequencies to 110-880
[Nexus S Android Development] Ezekeel:
I cannot think of any reason why DEEP IDLE should increase the battery drain while the device is in its SLEEP state. With my phone the largest two consumers while in SLEEP are Mobile standby and Phone idle which together make up to 70-80% of the battery usage. Afaik these correspond to the battery drain of the baseband hardware, so the mobile chip and such on the board. I dunno how DEEP IDLE could possibly influence these. But you can try to disable DEEP IDLE and see how the battery drain while in SLEEP changes. Maybe there actually is a problem worth investigating.
[Nexus S Android Development] polobunny:
Well, got a bug with backlightdimmer I think.

GLaDOS v1.6, NSCollab 1.0.50, touchwake and backlightdimmer disabled

At boot it's fine, but after a few text messages it seems it bugs out. I have BLN enabled, using Neldar's app to control it. Whenever I run my fingers over the softkeys they'll light up.

Video taken riiiiight after the terminal session pic:

http://webcamvideo.us/view.php?id=1321412599

Edit: Disabling and re-enabling BLN makes it work fine again. But for how long? D:
[Nexus S Android Development] some_random:
I am finding the same issue.... I was using trinity kernels which have deep idle with all the latest patches and found that the drain I was getting overnight was much larger than I was use to up to nearly 12 to 15% for a 8 hour period.

Nothing was keeping the phone awake everything was acting as it should be but drain was high and I couldn't explain it.

So to test this I disabled deep idle using nstools last night.. what do you know back down to 3% drain over the 8 Hour period I didn't do anything different except turn deep idle off.

I was running 257 nightly and trinity's tuev 14th kernel and the battery usage graph for both night had the screen off and awake section empty so it was sleeping properly both nights no interruptions.

So maybe just maybe there could be something that is causing the phone when in sleep to drain more with deep idle enabled
[Nexus S Android Development] steve.garon:
DeepIdle is a good idea on paper but I never felt like it lives up to the expectation. I too get terrible battery life with it enabled.
[Nexus S Android Development] some_random:
but Ezekeel is right... it shouldn't touch sleep drain because its not even being used when your phone is asleep with the screen off thats just deep sleep at work and every android phone uses that. deep idle is only used when you have the phone's screen off but are using it and keeping it awake the best example is listening to music... the phones screen is off but there is still stuff going on in the background. this is where deep idle is used and where it should use less battery with deep idle enabled. However there seems to be a problem with it also effecting the drain when the phone should be in deep sleep... or this is what I and it seems a couple of other people including yourself seem to be experiencing
[Nexus S Android Development] steve.garon:
I dunno what is draining the battery. The only thing I know is with deepidle, my battery drains lot faster... Its draining twice as fast than without. That's enough for me to just remove it. We are at about 16 bugfixes in deep idle, probably a lot different than first implementation. It looked like first implementation was good. Lots of ppl tried it and adopted it. It was just plagued with SoD and problems with GPS and BT. Maybe what was added to fix those preliminary issues changed its effectiveness ...
[Nexus S Android Development] FloHimself:
In fact the current implementation is not much different from the initial implementation. The most significant change is when deep idle kicks in. And with the current configuration it kicks in lesser than in the initial one (e.g. when bt is on etc). And 16 bugfixes aren't so much, if you take a look at the linux kernel devel mailing list.

What I can think about is: the device is in deep idle currently, while it should go into sleep...
[Nexus S Android Development] coloxim:
It is the same form me..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] frz:
max oc?

whats the max stable oc any1 achieved on GLaDOS1.6?

I got 120 anything over that i got constant fc & reboots
[Nexus S Android Development] polobunny:
Woke up this morning, same glitch. Didn't turn phone off at night, and turning BLN on/off doesn't fix the problem. Hmmm...
[Nexus S Android Development] ChargingPaladin:
What radio are all of you using? I flashed XXKB3 after already using GLaDOS for a while and my battery life was shot to hell. Switched back to UCKF1 and it's back to sane levels.

Sent from my Nexus S
[Nexus S Android Development] polobunny:
Using KB3 is fine for me, I used to get radio dumps often with UCKF1. Depends where you're located, some might be better than others. :)
[Nexus S Android Development] FloHimself:
Take a look at the compatibility chart (at the bottom) here: Nexus S, Nexus S 4G and Galaxy Nexus Bootloader and Cell Radio compatibility
[Nexus S Android Development] moinsheriff:
What are the settings I need to use in NS tools.. Battery is draining even when the screen if off..
[Nexus S Android Development] ellesshoo:
Real quick, what's the terminal command to reset deep idle stats?
[Nexus S Android Development] polobunny:
echo 1 > /sys/class/misc/deepidle/reset_stats
[Nexus S Android Development] coloxim:
Disable idle

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] ChargingPaladin:
Thanks for the link; I didn't realize it was already laid out all pretty. My question was mostly rhetorical actually. I see a lot of people flashing different radios on a regular basis (regardless of baseband/model) for regional compatibility / data caps / sticking it to the man. KB3 is the popular one to om-nom-nom data. ("uncapped")

I thought maybe I was just using more data on KB3 but then I spent 72 hours on wifi, minimal usage and the drain was just as bad.

Oh well, anecdotal!

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
Maybe ezekeel will do a new bugfix in this deep idle drain that we are getting when the screen is off.

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] Ezekeel:
After some testing I can confirm that there actually is an increased battery drain while in SLEEP caused by the DEEP IDLE mod.

I started out with DEEP IDLE activated and after some hours, disabled DEEP IDLE and rebooted the device. As one can see the battery drain decreased significantly. So there clearly is something wrong with the DEEP IDLE mod since it does increase the battery drain while the device is in SLEEP which should not happen since these two are completely different power states and should not influence each other.

Now comes the interesting part: I enabled DEEP IDLE, turned the screen off just for a few seconds to let is enter DEEP IDLE a few times, then disabled DEEP IDLE again. As one can see even with DEEP IDLE disabled the battery drain has increased to the same level as before with DEEP IDLE enabled. So it seemed that something in the DEEP IDLE code made some persistent changes which did influence the behavior while in SLEEP. I checked the code and noticed that the power down configuration for the GPIO (general purpose I/O) pins which connect the other hardware parts is changed before DEEP IDLE is entered however never restored to the original configuration. Since this GPIO power down configuration is also used while in SLEEP this would explain how the DEEP IDLE code could actually influence the behavior while the device is in SLEEP.

I made some modifications to the code saving the original GPIO power down configuration before it is changed and restoring it after wakeup from DEEP IDLE. Please give the following test kernel a run and check the battery drain while in SLEEP.

Test kernel: http://www.multiupload.com/SBKEA1FQZG
[Nexus S Android Development] coloxim:
I don't undeatand too much because is a bit complicated..but thanks..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] polobunny:
The users weren't too crazy this time. :p Nice find though!
[Nexus S Android Development] polobunny:
Yes it would, but you'd still have the unusal drain when sleeping.
[Nexus S Android Development] franciscofranco:
Great! Could you commit your change or PM us with the changed code so we can test it as well?
[Nexus S Android Development] Ezekeel:
Sure.

Bugfix: http://www.pastie.org/2874507

This also includes the fix for 4G and DEEP IDLE.
[Nexus S Android Development] franciscofranco:
Much appreciated, I'll build a local testing kernel and see what happens ;)
[Nexus S Android Development] caliban2:
Ezekeel, iirc the high drain was introduced with 1.2, the changes to make deepidle more stable.

Now I'm eager to see how the test-kernel does overnight. :)

Edit:

Uhm, is it bfs or cfs?
[Nexus S Android Development] Ezekeel:
The test kernel is CFS. All my test kernels are, because I do not want to risk any possible problem introduced with BFS.
[Nexus S Android Development] brenix:
Bugfix appears to be working as expected.. I would have lost at least 4% already, but haven't lost anything yet.. No issues either... Looking good..
[Nexus S Android Development] some_random:
well what do you know turns out I wasn't crazy I was getting more drain with deep idle enabled thats super awesome that you found that bug shall wait until trinity builds it into his latest teuv kernel
[Nexus S Android Development] steve.garon:
Damn you for fixing bug faster that I can build kernels! ;) See it's not fair. I feel compelled to give it another try :rolleyes:

Seriously, ppl in your tread are already reporting improvement so kudos! I'm giving it a try for sure.
[Nexus S Android Development] mixtapes08:
As expected a very fast bugfix by ezekeel.. tnx

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] asb123:
where is the test kernel download link located?
[Nexus S Android Development] MSgtSimon:
There you go, it was quoted 4 posts up. :P
[Nexus S Android Development] v3rk:
Where have you been? Zeek tirelessly improves. You jumped the gun
[Nexus S Android Development] franciscofranco:
Ezekeel congrats, my initial testing has been very successful. Enabled deep_idle ran some music for over an hour, drain was very low, then I left home and with music off and deep_idle enabled the drain was absolutely normal like it should be.
[Nexus S Android Development] Ezekeel:
I have made some further changes to DEEP IDLE which should only effect NS4G owners. To make sure it does not have any unforeseen side-effect for the i9020/i9023 please check this latest test kernel.

Test kernel V2: http://www.multiupload.com/6VRDP8HFXG (note the version when giving feedback)
[Nexus S Android Development] some_random:
i'm with franco drain on this new bugfix as awesome running trinity's new 16th kernel with the update has been awesome here at work for the past hour or so
[Nexus S Android Development] matmat07:
False, the one you had me try was bfs. 1.4.1 ;)
[Nexus S Android Development] polobunny:
Unsuprisingly, Ezekeel made it work. Psh, knew it. :rolleyes:

(love the update BTW, so far deepidle is working fine on my phone for the first time)
[Nexus S Android Development] steve.garon:
That may be. Only tomorrow's testing will tell. From the past 2h that I've used it. Battery usage seems equal to my kernel without deepidle. Tomorrow I'll be able to tell if drain is fixed and if batt life is better than without deepidle.
[Nexus S Android Development] afzalarsalan:
Ezekeel,

Since your good at tweak and mods I was wondering if you could make slide 2 wake work on the nexus s. Love your mods and great job on the bug fix.
[Nexus S Android Development] y3mita:
Indeed, bug traced and apparently fixed! I used latest Franco's with your fix Ezekeel and battery life is doing great! Even using the phone does not impact much! Loving it now!!!! And thanks for looking into it.
[Nexus S Android Development] got2best:
That's pretty sweet!
[Nexus S Android Development] mike216:
I love that slide to wake, is that a possibility for glados?

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] mixtapes08:
This is good for saving your power on button. But is this a potential battery drain because the the nexus s soft keys are so sensitive?

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] mike216:
But it would be hard to activate the unlock, its a perfect mod on my opinion and would really extend that power button as you said

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] caliban2:
Hehe, forgot my phone on charger over night, so i can't say anything about batt-drain of test v1 in deepsleep. ^^

But idle-stats showed some top-on use? gps & Bluetooth were both disabled. Running v2 now on battery, let's see how it goes. So far no top-on. Lazy, didle & Max_CPU enabled, everything else untouched.
[Nexus S Android Development] Mecid8:
how i can enable logcat for this kernel?
[Nexus S Android Development] coloxim:
What is logcat?

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] MSgtSimon:
Ezekeel disabled logging for speed and kernel size. I think if you compile from source, you can turn the logger module on.
[Nexus S Android Development] arifhn:
Its compiled as module. You can load it with modprobe.
[Nexus S Android Development] polobunny:
Is anyone having issues with WiFi having trouble connecting sometimes? I just experienced this last night at home and once at work. Enabling/disabling wifi usually works, but still wondering.
[Nexus S Android Development] IT4ALii3EN:
Hello,

I installed Oxygen 2.3.2 on my NS, with the kernel 1.6 GlaDOS, and it works good.

But, [there is always a "but" :P], when I turn off the DATA, there is like a big bug and it isn't possible to send a sms or mms, there is an error.

So, I must reboot my phone in order to have the possibility to send a sms...

Options:

OC = 100

CPU max = 1000Mhz

CPU min = 100Mhz

Governor = lazy

DeepIdle = Actived

Touchwake and BLN and BLD = Actived.

Default voltages -> There aren't some voltages customs.

So, I don't know if it's the ROM is the problem, or the kernel...

Bye.
[Nexus S Android Development] got2best:
I notice last night with latest test kernal that my Alarms where not going off..

I am running nscolleb .5

On my i9023
[Nexus S Android Development] 1PATRIK:
Test kernel v1 freezes in lockscreen. Had to do battery pull to wake it.

ROM: Nexus MV

Device: i9023

deep idle 0

screen off max freq 0

default voltages

OC 100

max:1000mhz

min:400mhz

Hmm.. what more? :)
[Nexus S Android Development] Yusei:
Testing here

Till now I'm having radio dumps but I think is a radio problem.
[Nexus S Android Development] mrpdaemon:
Can load it with:

insmod /system/modules/logger.ko

which creates /dev/log/* device nodes but doesn't produce any logs. Perhaps there is a /sys/ node that needs to be poked or a module parameter that should be passed while loading the module?
[Nexus S Android Development] Ezekeel:
Afaik this has to be done at boot to work properly.

New version GLaDOS V1.7 has been released.
[Nexus S Android Development] JmPTaz09:
I'm running the test zip; is there any change in 1.7 not in the test kernel? Just wondering if I need to flash 1.7
[Nexus S Android Development] Ezekeel:
Yes, you need to update to V1.7. All the test kernels still have bugs.

I realized this morning that the changes made for the test kernel did not solve the battery drain problem while in SLEEP, so I made some additional changes which seem to have solved the issue (got less than 1% drain for 2h+).
[Nexus S Android Development] JmPTaz09:
Cool, will flash. Thanks for quick response sir!
[Nexus S Android Development] 1PATRIK:
Just flashed 1.7 cfs. Will report back tomorrow with results of daily use.
[Nexus S Android Development] polobunny:
Rock on. Only fixes in this release are related to deep sleep?

I still have trouble with BLN/soft keys turning on and staying on when I touch them. It seems to ALWAYS be there when I wake up in the morning.

I have a Tasker profile killing a music streaming app after 1 hour, and another one locking the device when I sleep. I'm gonna try to investigate on that, it's driving me nuts.

What's your take on that slide to wake suggestion?

I have a question for you too. When you plug/unplug the device, the screen comes on. Is that controlled by the ROM or the kernel? It's absolutely pointless to me and I was wondering what were my options. For now I have a Tasker profile turning it off instantly when plugged it. Clever but not perfect, and kinda overboard for a little annoyance. Thanks, liking GLaDOS!
[Nexus S Android Development] y3mita:
Flashing CFS 1.7 thanks Ezekeel ;)
[Nexus S Android Development] got2best:
Thank you so much! :)
[Nexus S Android Development] Flying Fox:
Wonderful boot-animation, great!! Will test this kernel overnight, thx!!!!
[Nexus S Android Development] y3mita:
One reboot 2 freezes so far, lemme adjust the voltages up to my usual settings! (-25 overall).
[Nexus S Android Development] some_random:
so will there be a new bugfix for other kernels? did you change anything to do with deep idle or just with your kernel?
[Nexus S Android Development] steve.garon:
There are new bug fixes. Already implemented in mine and Franco's. Thx to ezekeel :)
[Nexus S Android Development] some_random:
but he just said he made more changes

that was only posted 5 hours ago... I'm guessing you don't have those new changes in your kernels but I could be wrong
[Nexus S Android Development] franciscofranco:
Mine does, but let's not get off topic, this is Glados thread.
[Nexus S Android Development] some_random:
holy crap that was quick, what do you do all day....
[Nexus S Android Development] matmat07:
Me too, but it has nothing to do with this kernel since it does happen on others..
[Nexus S Android Development] asb123:
I also had a reset into discoloured bootloop. Stock voltages, no overclock
[Nexus S Android Development] steve.garon:
Yeah its in. I pulled the changes 3h ago...
[Nexus S Android Development] mrpdaemon:
Ah, thanks. Loading logger.ko from an init.d script works fine.

Running GLaDOS 1.7 cfs, and so far battery life has been great testing music playback with the screen off.
[Nexus S Android Development] Ezekeel:
Never had this problems with the touchkey backlights. Can you give a step-by-step instruction to reproduce it?

This behavior when unplugging is controlled by the ROM I think.

This seems to a problem with CM. Unfortunately I have not found any CM version since I left CM7.01 which did not have issues. I am seriously thinking about switching to another ROM.

Great. Good to know.
[Nexus S Android Development] franciscofranco:
Not wanting to derail into an off-topic madness, but I strongly suggest you to try Oxygen or something as close to AOSP as possible. But my money is on Oxygen, been using it for over a month straight without any issue.
[Nexus S Android Development] matmat07:
Hey ez, ever tried MIUI? Would be nice if you had brainmasters'S one too, to help me debug better XD.

Sorry, sometimes i'm pretty selfish
[Nexus S Android Development] mike216:
Ezekeel try nscollab if your a fan of aosp/cyanogen, I think its the perfect rom! Blazing fast and stable with all of the best cyanogen tweaks

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] mixtapes08:
Been running 1.7 the whole day.. the music playback is also saving battery because of the deepidle. Thanks again ezeekeel..

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] mixtapes08:
What nscollab do you suggest sir?

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] margosmark:
I personally use the latest NSCollab 1.0.50, I have not had any of the problems people have been reporting with the other CM roms
[Nexus S Android Development] steve.garon:
If I might add, nightly 259 of CM is completely broken. I had reboots, SoD, non working touch screen.... for those running nightlies stick to 257.
[Nexus S Android Development] mike216:
50 I have 0 problems

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!