yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Ezekeel:
Since the testings to track down the reboot problem were inconclusive and I cannot think of any more things to test, there is not much I can do at this point. I have decided to wait for the next official update that probably will roll out soon and see if maybe the problem was in the stock code and fixed in the update.

Also since I have realized that I have no time to develop new tweaks on two different devices, I have decided to sell my NS once the official update is released and GLaDOS stable, because there probably will not be any major updates for some time so I do not need the device to keep GLaDOS updated. This means there will be no more new tweaks from me for the NS, however I will keep GLaDOS up-to-date.
[Nexus S Android Development] nexusphone:
:( Selling NS... :(
[Nexus S Android Development] Ezekeel:
Yes. The Galaxy Nexus is superior in a lot of aspects while having no drawbacks for my usage. And since I only have one SIM card the NS is just sitting there on my desk. So it seems reasonable to sell it to fill up my developer fund for the next Nexus which will be released in 10 month or so.
[Nexus S Android Development] phone_user:
So we must buy GN accordingly... but the stipulated time of NS...
[Nexus S Android Development] mobile_pc:
Our GLaDOS! Our Ezekeel!
[Nexus S Android Development] Ezekeel:
Actually no. As I said I will continue keeping GLaDOS updated. There just will be no new tweaks I will develop for the NS. Then again, I always felt that the NS is working perfectly and I cannot think of any new tweaks that would be an improvement (besides USB OTG which I will add once GLaDOS is stable). So probably me selling or keeping the device will not make any difference for the future of the GLaDOS kernel for NS.
[Nexus S Android Development] phone_user:
I am so relieved. waiting for the stability of GLaDOS :)

I always appreciate your excellent works.
[Nexus S Android Development] Ezekeel:
Believe me, there probably is not one single person in this forum that would like more to get to the bottom of this issue. I guess summed up I easily spend more than 20h trying to figure out where the problem is and still got no answer.

In the step test which included one tweak after another people were having problems at different steps, so it should not be related to a particular tweak. Trying the near-stock kernel config, the stock Makefile flags and another TC also gave no conclusive results.

So currently I am all out of ideas. Since there is a chance that the next official update will bring some kernel bugfixes, this seems to be the most sensible option considering the time I already spend on this issue.
[Nexus S Android Development] nexusphone:
Of course, we do believe in Ezekeel's capacity for great work. :)
[Nexus S Android Development] kong:
Just wonder if the people who has taken step tests ever changed the settings in NSTools? Should they stick with default kernel settings? Can it affect the test results?

For me, GLaDOS was very fragile when running with Lazy governor (got reboot while calling, etc.) but once I changed to ondemand, it was simply rock solid.
[Nexus S Android Development] noobiekins:
May I suggest adding the cold colors tweak? It doesn't have the side effect of the green unlocking when the screen brightness is at the minimum
[Nexus S Android Development] jcolinzheng:
My setting is exactly the same, except with LiveOC 110%. I get reboot during calls on Test 3. So it seems that LiveOC may be the culprit. I will run the test again without LiveOC and report back.
[Nexus S Android Development] android_nexus:
Plz read this
[Nexus S Android Development] stewarta:
@ezekeel: Sorry this is off topic but PM androiduser00110001 if you are disposing of the NXS.
[Nexus S Android Development] caliban2:
I see, that's why I've had this bad feeling when voting for you on rootzwiki... j/k :p

I was bored last night and so I flashed mathkid's latest kernel (v16). Seeing substantial improvement in batt-life already. Don't know if it's caused by cpuidle-backport or lulzsec-gov.

But maybe you could have a look into those before you abandon ship? ^^
[Nexus S Android Development] IIIV:
Totally understandable. At least you'll be sticking around and keeping GLaDOS up to date. Your non-65fps v2.9+ test kernel (BLN/ondemand/100%/400-1200 MHz/Deep Idle) have been solid for me. So, I can live with it until your next official release.

Thanks!
[Nexus S Android Development] phone_user:
Without Live OC, 1.2GHz OC step instead?

---------- Post added at 03:01 AM ---------- Previous post was at 02:54 AM ----------

- Ondemand, even on V2.8 with 65fps no reboot while calling!

(LiveOC 120 : 240~960 / Deep Idle / BLN, BLD, TW)

- Received a Gmail while music was playing and no reboot after LEDs are activated by BLN

Thanks, kong :)
[Nexus S Android Development] IIIV:
No LiveOC this time, because I was getting reboots during phone calls at 110%/220-1100 MHz, and also SoD at 120%/240-960 MHz while screen is off. Though, it could also be because 220-240 MHz is too low when my I9020T is waking up from sleep or deep idle.
[Nexus S Android Development] phone_user:
Give it a try :) The nub of the matter is "governor", maybe! ondemand

With 65fps, LiveOC, BLN and yet solid

Truly,
[Nexus S Android Development] IIIV:
Thanks. I actually always use ondemand. I prefer the non-65fps for better colors, so I'll stick with the v2.9+ test kernel.
[Nexus S Android Development] phone_user:
Weird thing! I distinctly set max freq 800 MHz, LiveOC120 / 240~960

but, sometimes GLaDOS' max freq 1.4 GHz usage shows in CPU Spy or Android System Info

proper

This is the bug of LiveOC related to the recent "reboot or SoD"? maybe...

(btw, no bad issue on v2.8 with 65fps so far)
[Nexus S Android Development] phone_user:
Eek, finally, just now, reboot while charging

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

the othe kernel also shows the max freq usage I din't set
[Nexus S Android Development] Baalzeph:
Hi,

Does anyone can send me the bootanim? Is it possible to drop this only.

Don't really like the generic boot and i'm on speedy till your update.

Thanks a lot!
[Nexus S Android Development] :
Isn't that like painting a nike tick on your reeboks?
[Nexus S Android Development] byrko:
My favorite solution is to delete \system\media\bootanimation.zip
[Nexus S Android Development] gotjazz:
Well maybe he's just a portal fan
[Nexus S Android Development] Baalzeph:
If you are on glados kernel, when u change kernel for matrix or other for example.

The boot animation of glados stay in place right.

I'm on speedy now, but i don't want to change the kernel, just want this image of aperture laboratories on my boot.
[Nexus S Android Development] :
Oh sorry, I misunderstood. Follow this;

For kernel benchmarks and more, see HERE
[Nexus S Android Development] IIIV:
Question: I have NSTools' Battery Life Extender set to 96%. But, when I charge my I9020T it goes up to 98-99% before it says "Charged." Is this normal?

Thanks in advance.
[Nexus S Android Development] Ezekeel:
I have released GLaDOS V2.10 adding USB OTG support and fixing bugs in Custom Voltage and Live OC.
[Nexus S Android Development] IT4ALii3EN:
Hello,

There are "stock Makefile" and "AOSP TC" are included in the 2.10 ?

Because with the Test3 [V2.4 kernel config + stock Makefile + AOSP TC] ; I never had bug !

And the version 2.10 is based on the v2.4 ?

Goog work Ezekeel !
[Nexus S Android Development] gotjazz:
Apart from that is it closer to 2.9 or to the various test kernels?
[Nexus S Android Development] nexusphone:
Thanks for the update. :) I'm flashing with great anticipation.
[Nexus S Android Development] HosainH:
Voodoo sound driver is failing to load for me with this version..

Edit: Nevermind a reboot fixed it o_O
[Nexus S Android Development] phone_user:
Thanks for V2.10 :)

I9020T / BLN ON / lazy / LiveOC 120 : 240-960 MHz / Deep Idle ON

- no reboot while calling (ten minutes)

- received a Gmail while music was playing and no reboot after LEDs are activated by BLN

Nice so far. Other things, I'll have to wait and see what happens. Thanks again :)
[Nexus S Android Development] IIIV:
v2.10 CFS working great so far on my I9020T. No reboots while playing music (PowerAmp) + SMS and 10 min. phone call.

My settings:

BLN / ondemand / 100% / 400-1200 MHz / Deep Idle with BT fix / default voltages

Thanks for the update, Ezekeel.
[Nexus S Android Development] nexusphone:
On V2.10, no issue so far

Thanks a lot :)
[Nexus S Android Development] mixtapes08:
No issues so far in the latest update. Im using cfs

Sent from my Nexus S
[Nexus S Android Development] aLNG:
ezekeel,

when the reboot prob is gone, can u add more governor? especially smartassv2. i really like to test, but there is no smartassv2 governor :)
[Nexus S Android Development] mixtapes08:
simple io scheduler also :)

Sent from my Nexus S
[Nexus S Android Development] schurl85:
switched from matrix 15.5 back to glados. currently no problems so far. And even better battery life as seen in the screenshot
[Nexus S Android Development] schurl85:
double post
[Nexus S Android Development] gotjazz:
Hrm voodoo control plus can't seem to load the kernel module on 2.10 here?
[Nexus S Android Development] phone_user:
can load on v2.10 :) re-flash kernel plz
[Nexus S Android Development] :
GlaDOS 2.10 CFS and BFS tested. Looks like BFS harms performance.

See my thread for the link: here
[Nexus S Android Development] gotjazz:
Thanks - that did it
[Nexus S Android Development] veagles:
Oops, Just noticed a reboot in standby after 7 hours of light usage.
[Nexus S Android Development] IIIV:
What settings do you use?
[Nexus S Android Development] veagles:
Touch wake and deep idle ON.

Everything else defaults.
[Nexus S Android Development] IIIV:
Update: Had a SoD while playing music (PowerAmp) with earphones for about 40 mins. So, I adjusted my CPU settings to 120% and 240-960 MHz and no issues after playing music for more than an hour.
[Nexus S Android Development] R-TEAM:
Hi,

looka 2.10 catch the deepIdle bug - have the CFS version flashed and over 1h music play with DeepIdle ON , and no problems ;)

Good work :)

Now i miss an 1100Mhz Step and the new KSM :)

Regards

R-TEAM
[Nexus S Android Development] androidphone2012:
Hmm... the most creative dev but reboot and SoD issues...
[Nexus S Android Development] caliban2:
v2.10 cfs just working fine for me, as expected. Stable and smooth. Wonder where all this semi-scientific blabla about deep idle comes from lately. After all it's not the sacred battsaver, it just comes into play under certain circumstances. And it works.

I've been away from my PC this week, so I used my nexus as a replacement. And while on matr1x, I got better Batt-life with smartassv2-gov. It scales more. Would be nice to have smartassv2 as an additional option. (I'm talking about lots of screen time, surfing, watching vids etc, not standby-drain -> active use)
[Nexus S Android Development] Kitch16:
V2.10 CFS working brill for me, no reboots. Keep up the GREAT work Ezekeel! :p
[Nexus S Android Development] IIIV:
You can get reboots and SoD's from any custom kernel. You just need to test and find out the right settings for your phone.
[Nexus S Android Development] darth7:
Hi, is this kernel still buggy? I been using matrix, and now air, no problem at all.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] b1337:
you could read through the threads a lil...just saying...
[Nexus S Android Development] darth7:
all I see is reboot. So I guess is not working good yet.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] mixtapes08:
No its been really stable now. I didnt have a single reboot since the release of this. Governor lazy deep idle on all the time.

Sent from my Nexus S
[Nexus S Android Development] darth7:
Nice, got to try it.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] IIIV:
My new CPU settings:

lazy / 100% / 400-1200 MHz / Deep Idle + Screen off max freq

...and my NS is a little bit more responsive and battery life is even better.
[Nexus S Android Development] android_nexus:
...and about reboot or SoD?
[Nexus S Android Development] nathanson666:
Unfortunately I got a reboot while in a call tonight.

oc 105% bln lazy deepidle
[Nexus S Android Development] IIIV:
Made a correction -- No LiveOC and 400-1200 MHz and no issues with playing music for more than an hour and two 10+ minute phone calls. I'll be doing more tests and report back tomorrow.
[Nexus S Android Development] gotjazz:
Is there any particular reason why so many people have min cpu freqs above 100? Just wondering....
[Nexus S Android Development] b1337:
DI, SOD, etc
[Nexus S Android Development] gotjazz:
Hrm is that worth it so to say?
[Nexus S Android Development] b1337:
im not even sure answering your question was worth it ;)
[Nexus S Android Development] gotjazz:
Moody much?
[Nexus S Android Development] AeroEchelon:
I've always had mine at 100 MHz and no bootloops or SODs for me.

Keep it at 100 MHz, uses less voltage.
[Nexus S Android Development] aLNG:
use same voltage but more power
[Nexus S Android Development] IIIV:
The higher the min freq is -> the faster the CPU completes an operation(s) -> therefore, the faster it goes back to Deep Idle -> better battery life.
[Nexus S Android Development] :
Not exactly. If the screen is on, it goes back to Idle.

In order of greatest power saving, the CPU states are:

Deep Sleep - screen off, nothing for CPU to do. Uses almost no power because it's basically powered off.

Deep Idle - screen off, but music playing or other CPU activity, processor wakes up, finishes tasks, then goes back to a partially powered down state.

Idle - The screen is on, but with no tasks, the CPU frequency is set to 0.

Also, I've done some new battery drain measurements using deep idle. With deep idle active, the governor that saves the most power is conservative. This is not a race-to-idle governor. It aims to keep the CPU frequency low.
[Nexus S Android Development] morfic:
You never aim to race to deep idle on purpose.

Deep idle is a "if i can't reach deep sleep, then i guess i *settle* on deep idle" choice.
[Nexus S Android Development] y3mita:
same here always min 100 and no reboots or SOD *note keeping default voltages in kernel that is* once I start OC-UV I may need to change accordingly.
[Nexus S Android Development] kong:
Min 100 does not survive playing FLACs. Other than that I got no issues.
[Nexus S Android Development] IIIV:
Just had a freeze while playing music (FLAC, PowerAmp) while screen off with these settings: lazy/100%/400-1200 MHz/Deep Idle/Screen off max freq/Default voltages.

Now testing @ 110%/440-880 MHz.
[Nexus S Android Development] IIIV:
No problems with playing FLAC but had a reboot during a phone call with LiveOC @ 110%.

I'll stick with 100% and 400-1000 MHz for now.
[Nexus S Android Development] darth7:
Liveoc never works for me in this kernel.

Try matrix kernel. It works for me using liveoc.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] nexus_junkie:
"The be-all and end-all" was GLaDOS v1.12 on GB :)

But.... on ICS, reboot and freeze... :(

We are hoping for the revival of GLaDOS!
[Nexus S Android Development] IIIV:
With lazy, does anyone know if screen off max freq uses the max frequency that you have set? Or does it assign a certain max frequency when the screen is off, like smartass does?

Thanks in advance.
[Nexus S Android Development] aLNG:
as far as i remembered when using lazy with somf, when i checked using cpuspy it will use max freq. let say u have freq from 100-1000Mhz, then it will use 1000Mhz.
[Nexus S Android Development] y3mita:
Very pleased with 2.10 battery life is awesome and performance is great! Idle stats don't show screen off but I guess I need to read more and find out what to do so it shows.
[Nexus S Android Development] mixtapes08:
This one is so stable for me and great battery. Didnt have single reboots or freeze since this update rock solid for me. My phone is loving this glados :)

Sent from my Nexus S
[Nexus S Android Development] y3mita:
Well, if I set Performance up to 1200 I get reboots!
[Nexus S Android Development] CrackDaddy:
:( Back to v2.9 for me, after constant reboots nearly 5 or so times a day when screen's off! NexusBeam v4.2.3, DeepIdle on, 200mhz/1200mhz, ondemand, no live oc, bln on & everything else stock values! :confused:
[Nexus S Android Development] y3mita:
Same here, had to flash another kernel!! Too many reboots no matter what governor especially on phone calls.
[Nexus S Android Development] IIIV:
Have you tried adjusting voltages, since you overclocked to 1200 MHz?
[Nexus S Android Development] zirra:
I'm getting reboots whenever i'm on a phone call for more than 30 minutes. Is anyone else getting that problem?
[Nexus S Android Development] CrackDaddy:
No I didn't adjust voltages @ 1200 MHz, because with GlaDos v2.9 kernel everything was really stable for me with those settings! Also I'm not too sure about adjusting voltages & the such, so tend to steer clear from that sort of stuff! :rolleyes: read this:http://www.xda-developers.com/tag/samsung-nexus-s/
[Nexus S Android Development] IIIV:
I was having SoD with 100%/400-1200 MHz as well. So, I'm sticking with stock settings + lazy and deep idle for now.
[Nexus S Android Development] IIIV:
I've switched back to the non-65fps v2.8+ test kernel, as it has been the most stable version for me with LiveOC and Deep Idle on and also best battery life.
[Nexus S Android Development] [David]:
I was flashing v2.10 to my gf's Nexus S but I read of many issues.

I even read 'bout 2.9 as the best one, and 'bout 2.8 as the most stable so I'm gonna ask you : Which is the really best one in terms of stability, no SOD and best battery usage??

Can you help me? Thanks guy ;)

Sent from my Galaxy Note with DarkyROM 3.3
[Nexus S Android Development] IIIV:
It depends on what model your NS is. My I9020T didn't have any issues with the v2.8+ test kernel after using it extensively for more than 2 weeks. My settings were LiveOC @ 120% and 480-960 MHz. But, now I've lowered down to 110% and 440-880 MHz for better battery life, since I listen to music for about 2 hours every day.
[Nexus S Android Development] ljordan2:
Just tried Glados v2.10 cfs and it is awesome. My setup is conservative, live oc : 110%, 880/220, deadline, deep idle : on. It is great for battery while not losing the performance.
[Nexus S Android Development] IIIV:
Giving v2.10 another try. I just re-flashed my ROM, set it up, then flashed GLaDOS v2.10 CFS and set it with BLN / lazy / 100% / 400-1200 MHz / default voltages.

So far, no issues...

Playing FLAC (PowerAMP)

SMS + BLN + while playing FLAC

11-minute phone call while playing FLAC (music resumed without lag after phone call)

*Not using Deep Idle, as the BT fix is causing problems with my network signal.
[Nexus S Android Development] caliban2:
Interesting that bt-fix should cause signal-probs. I'm running 4.0.4 with the fix and signal is fine. Point being, I don't remember any problems in that area when running 4.0.3 with the corresponding fix. Sure it's not something else causing it? (Mods etc)

Edit:

I can't find your from from the sig, but how stock is it? Sure it doesn't come with a modified framework-res, where overwriting it with the bt-fix doesn't cause troubles?

(I know you're seasoned enough to check this, but hey - no harm done making sure, right? ^^)
[Nexus S Android Development] IIIV:
The signal issue that my I9020T is experiencing is when I go ride the subway (underground, where there's no network reception) for about 45 mins. and then I get off the train and back up ground level, my network signal does not come back (even after more than an hour) and its icon remains gray. It'd only go back to normal and reconnect to my network after I reboot my NS. I'm not exactly sure if it's the BT fix or Deep Idle that's causing this, but I'm guessing it's the former, since it is a known ICS 4.0.3 ROM issue and I've also read from the Matr1x kernel of people having the same issue with the BT fix.
[Nexus S Android Development] endursa:
i can't think of a reason why the bt fix should interfer with network signal as it only changes one boolean variable from true to false. and this variable controlls only the bluetooth Adapter!
[Nexus S Android Development] nexus_junkie:
100% agreed

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
I wish ezeekeel will get some time update this one :)

Sent from my Nexus S
[Nexus S Android Development] IIIV:
So, maybe it's Deep Idle that's causing my I9020T's network signal issue? I have Deep Idle turned off for now, and I will report back if the same issue occurs.
[Nexus S Android Development] ChargingPaladin:
Same since 2.10. For me it's whenever I leave my phone charging overnight while connected to wifi. I was going to switch ROMs but I am going to try 2.8+ again and see what happens.

IIIV, are you using Widgetsoid by chance? It's the only app of mine I can think of that's had a major update lately.

BM stock 4.0.3

GLaDOS 2.10 w/ BT fix

200/1000 lazy, DI, 100% OC, max freq

Sent from my Nexus (IC)S
[Nexus S Android Development] IIIV:
No, I don't use any widgets that controls my Wifi or data.
[Nexus S Android Development] caliban2:
Don't think it's caused by the model. You have the same phone as me apart from the screen (slcd here), yet I'm using didle without any problems.
[Nexus S Android Development] IIIV:
Didn't have any issues for days until today, when my I9020T had a random reboot while playing FLAC (PowerAmp, which was just updated a couple of hours ago).

/proc/last_kmsg: http://depositfiles.com/files/5d2m19ha9
[Nexus S Android Development] IIIV:
Had 2 more reboots while playing music. Switching to ondemand with Up threshold = 90% (for performance).
[Nexus S Android Development] nexusphone:
Maybe GLaDOS become stable after Google's official kernel update
[Nexus S Android Development] lolokman:
Is it possible to lower the display fps?

According to bedalus's battery tests, 65fps drains about 10% more battery than original 56fps.

Lowering the display fps should save some battery.
[Nexus S Android Development] nexusphone:
Latest GLaDOS does not have 65fps
[Nexus S Android Development] IIIV:
GLaDOS went back to stock display frequency since v2.9.
[Nexus S Android Development] mixtapes08:
War maker.

Sent from my Nexus S
[Nexus S Android Development] IIIV:
No issues for 3 days now, since switching to ondemand + Up threshold: 90% (for performance) and overclocked to 1200 MHz. It's almost as smooth and snappy as LiveOC @ 110%, but without the reboots or SoD. :p
[Nexus S Android Development] nexusphone:
You're really loyal, man. :) rara avis! I was impressed by your sincerity.
[Nexus S Android Development] mixtapes08:
Did ezeekel forget about us? So sad :( no more tweaks to mess with.

Sent from my Nexus S
[Nexus S Android Development] IIIV:
Ezekeel says that he won't be updating GLaDOS until the next official ICS release, which should be soon.
[Nexus S Android Development] IIIV:
OK. I can confirm now that the BT fix nor Deep Idle has anything to do with my I9020T's loss of signal issue, as it happened again yesterday after an hour subway ride; I didn't have the BT fix installed and had Deep Idle OFF. Though, I was using lazy governor.

I will now switch to ondemand + Deep Idle + BT fix and test it up to next week.
[Nexus S Android Development] ChargingPaladin:
Having same issues, as noted previously. Consistent across BM stock 4.0.3, GLaDOS 2.10; CM9 v3.x, stock kernel. i9020A specific radios UCKF1x seem to be part of the issue; switched to xxKB3 about a week ago and haven't had any problems. KB3 burns battery a lot faster though. I'm going to switch to a newer radio today and see what happens.

Sent from my Nexus (IC)S
[Nexus S Android Development] ChargingPaladin:
Also, I have an inkling that the Bluetooth folder in efs may be related. ICS has been quite tricksy with the efs folder.

Sent from my Nexus (IC)S