yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Zorrich:
So what does this mean for us noobs? Don't use nstools to change min/max freq values? So far I have been running min 400, max 1000 (the 400 was set with nstools) and I haven't had any problems.
[Nexus S Android Development] Psych0Chimp:
Switched to BFS and enabled screenoff_maxfreq via terminal - think NSTools needs updating to add support for the new command - and no reboots so far... Thanks for the tip!

Here's my full config if others want to test it:

ICS 4.0.3 Stock ROM (Rooted)

GLaDOS 2.2 BFS

Lazy Governor

Deep Idle Enabled

200/1000

Stock voltages

LiveOC 100%

Screen-Off Max Freq. Enabled
[Nexus S Android Development] SwatMaster:
Anyone experiencing reboots after changing frequencies and/or voltages?

I tried NSTools and setCPU, but every time I try to set new voltages, lower max frequency or higher min frequency my Nexus gets stuck and reboots after few seconds.

ROM is NexusBeam 4.1, latest Glados 2.2 CFS, Nexus S i9023.
[Nexus S Android Development] onasri15:
Is it recommended to UV? And by how much?

Also, how do you enable screen off Max freq? I turned off profiles, have didle on and crashes seem to have lessened, not stop
[Nexus S Android Development] arifhn:
Strange.. do you use ICS?

What is your su binary version?

If you can make it work then no problem at all
[Nexus S Android Development] arifhn:
Read my previous post. There is problem with su binary.

I'm still find a way to make it work
[Nexus S Android Development] Ezekeel:
Turns out it was a problem with the new frequency code from Samsung/Google.

Released GLaDOS V2.3 which fixes the freeze/reboot problems when changing the frequency limits.
[Nexus S Android Development] Zorrich:
Yes I am using ICS Neapolitan v 1.1.1. My su binary is v 3.0.3.2.
[Nexus S Android Development] arifhn:
LOL

I'm searching for days. And you just minutes?
[Nexus S Android Development] Ezekeel:
Nope. Took me about 3h to find the problem. That was a really nasty bug.
[Nexus S Android Development] caliban2:
Should this take care of reboots in standby as well? I'm still doing my 2.2-test with didle disabled and so far it didn't reboot. (~6 hours)

Too early to be sure it's really caused by didle, but it looks promising. On the other hand I'm always happy to flash a new glados... :D

What to do?
[Nexus S Android Development] got2best:
Will this help those of is that get reboots only when the screen is off?

sent from Nexus S i9023 on xda premium

**please remember to hit the thanks button if I helped u**
[Nexus S Android Development] furiannn:
Well I sure hope it does, installed and trying it out now, so far so good. Question though, does the screenoff_maxfreq tweak work with CFS??
[Nexus S Android Development] arifhn:
Great 2.3 fixed the reboot problem when setting cpu freq and voltage

Maybe this will fix random reboot?

Will report later
[Nexus S Android Development] bmt25:
Touch wake not working

in turn on touchwake then sleep the phone, touch the screen everywhere. does not wake up, how will i fix that?
[Nexus S Android Development] AeroEchelon:
I have the EXACT setup with BFS as well. No reboots for the past 24 hours or so. Everything is pure stock GlaDOS with DEEP_IDLE enabled. After disabling Bluetooth via script and uninstalling Google Talk, I can confirm that more than half of my idle time is with DEEP_IDLE TOP = OFF.
[Nexus S Android Development] caliban2:
yeah well, of course I had to flash 2.3 cfs to see myself.

Didle and max-freq enabled, lazy-gov. Let's see if it restarts... :)
[Nexus S Android Development] 93ae8074:
Back to 2.2 'cos 2.3 doesn't enter in Deep-Idle mode. :confused:
[Nexus S Android Development] Attanasio89:
BLN don't work on missed call or sms, but working on apps that are led notification setting.

How can I fix it?
[Nexus S Android Development] andy206:
only bln pro works with missed call,are you sure you have pro version?
[Nexus S Android Development] Attanasio89:
I use NSTOOLS to activate BLN..
[Nexus S Android Development] rquinn19:
can bln pro and nstools coexist? Any issues with having both or do I need to use a different app to o.c. if using bln pro
[Nexus S Android Development] qtwrk:
sorry if anyone has already reported this problem ???

brainmaster's MIUI 09.12 version , stuck on GOOGLE logo after flash GlaDOS 2.2 and 2.3 , i tried both CFS and BFS, all stuck ...
[Nexus S Android Development] Ezekeel:
Re-download V2.3. I forgot the DEEP IDLE bandaid from the previous version.
[Nexus S Android Development] Zorrich:
Assuming we run with deep idle off, is it neccessary to re-flash 2.3?
[Nexus S Android Development] got2best:
So.. I think I found a bug.. I know it is other kernals as well.. but haven't seen it mentioned here yet.. but I am running nscolleb with this amazing kernal! And I am on the i9023 and I think this issue may be only with the i9023.. but I notice that if I restart my phone it will not go into deep idle till I open and close the camera then it shows the phone going into deep idle... hope this helps.. or if there is a fix I am unaware of.. not a big deal just stinks when u forget to open and close the camera after reboot.. lol. Other then that this is an amazing kernal and I love it! Great work!
[Nexus S Android Development] Ezekeel:
That is most likely a bug in the ROM. It also happens on the latest stock ROM, so it seems that this bug was introduced in the stock tree and the custom ROMs inherited the issue from there.
[Nexus S Android Development] FloHimself:
I think this needs further investigation... it appears on my device on 2.3.6 (GRK39F), but not on 2.3.7 (GWK74)...
[Nexus S Android Development] caliban2:
if it helps - doesn't happen on cm.

in some other thread i read that it's caused by cam-process not closing after being initialized during boot. (you kinda boot your phone with cam being active in background)
[Nexus S Android Development] arifhn:
Do you have google talk installed?

Try uninstall it.

Several days ago i noticed in logcat. google talk request for camera on boot, after i remove google talk the problem dissappear. Deepidle always on after reboot.
[Nexus S Android Development] got2best:
I do have talk installed but I can't uninstall it because I use it pretty much every day.. I would rather turn camera in and off when phone turns on. And I agree this should b investigated .. if there is anything I can do to help I am more then willing.
[Nexus S Android Development] FloHimself:
Yes, I stumbled across this "bug" while debugging the kernel to see what prevents my device from going into deep idle. As said already, I've seen this behavior on a stock GRK39F, but not on stock GWK74, CM 7.1.0 and CM 7.0.3... (always the same apps installed).

But: got2best uses NSCollab that is based on CM 7.1.0...

Maybe this be a radio related issue? IIRC there were radio dependent cam issues on bravo / htc desire...
[Nexus S Android Development] Ezekeel:
I am on CM7.1 stable and also have Talk installed (with automatic connection disabled) and I am not having this problem. In fact I never experienced this problem at all, so I did not have any chance to investigate it first hand.
[Nexus S Android Development] FloHimself:
Talk or Talk2? hmmm.. my stock GRK39F comes with Talk2... guess that's the problem then...
[Nexus S Android Development] jorim.tielemans:
I meant wsfic by DrewGaren.
[Nexus S Android Development] got2best:
So I tested this I turned off automatic sign in on google talk and camera issue still persists .. so it's not the automatic sign in .. what version of talk do u have ezekeel?
[Nexus S Android Development] Ezekeel:
Application info shows Talk Version 1.3.

No. A proper version of ICS will be released for the Nexus S 'soon' and I will not waste my time on some hacky beta version or whatever that is.
[Nexus S Android Development] got2best:
Hmmm.. this is interesting... I have talk version 1.3 also... maybe something to do with the i9023 specifically? .. so do u have the i9020?
[Nexus S Android Development] Ezekeel:
I am running the I9020XXJK8 baseband.

Yes, I do have the i9020.
[Nexus S Android Development] jorim.tielemans:
I meant "we scream for ice cream" by DrewGaren.
[Nexus S Android Development] FloHimself:
I checked my talk version and it is the one without video chat and it says version 1.3. With this version I don't have the "didle-cam bug".

After that I've installed the talk version with video chat from here. This version also says 1.3 and I have the "didle-cam bug".
[Nexus S Android Development] Ezekeel:
I know.

Good work.

How can we tell the two versions apart if they have the same version number? Are there any differences in the interface? I made two screenshots of the application info for the Talk version I got (I guess the one without video). Maybe the app size or permission are different.
[Nexus S Android Development] polobunny:
My app size for Talk 1.3 is 740KB for reference.
[Nexus S Android Development] Ezekeel:
And you do experience this cam bug with DEEP IDLE or not?
[Nexus S Android Development] FloHimself:
Beside the obvious video chat function inside the talk application, the size and permissions differ. This are the screens for Talk 1.3 with video chat:
[Nexus S Android Development] lukappaseidue:
thank You very much for Your work Ezekeel :D
[Nexus S Android Development] disaster_ita:
@Attanasio89: me too use nstool, I think that it works, missed call turn on backlight after 2/3 minute.

I have random reboot in standby. How can I see what is the problem to advice you?

I'm using cm9 alpha 17 with kernel GLaDOS 2.2.

Nexus S I9023
[Nexus S Android Development] phone_user:
+1 ;)

especially internet browsing
[Nexus S Android Development] 93ae8074:
Thanks!
[Nexus S Android Development] Zorrich:
Just wanted to report that my led buttons randomly appear to be going out until I touch them again (exactly how BLD works). I checked nstools, BLD is off. I tried to enable and then disable it again, but the problem still persists.

My setup:

Model 9020A, AOSP Neapolitan ROM, v 2.3 kernel. DIDLE off, Ondemand gov, min 400, max 1000.

Anyone else having this issue?
[Nexus S Android Development] demo23019:
Sweet another one
[Nexus S Android Development] slickrick:
I was having trouble with this combination. It seems like they're both writing the settings when they exit. My solution was to setup all i needed for LiveOC, DIdle etc in NSTools first, and then set up BLN in BLN Control app.

Every time I opened NSTools after BLN was set up with BLN Control the settings where overwritten.

So basically you can get around the problem, but you'll have to be aware of the tricks
[Nexus S Android Development] :
after flashing v2.3 my background is changed to default and my topbar does not work anymore :(
[Nexus S Android Development] IIIV:
Did you wipe Dalvik cache first before installing GLaDOS 2.3? This is what I just did over Brainmaster's Stock ICS ROM, and everything's working fine so far.
[Nexus S Android Development] bmt25:
I have a stock 4.0.3, and after flashing the 2.3kernel, my nexus s became the worst phone i ever had, so sluggish, reboots multiple times, hangs, lags are there and when opening games, it reboots. Ive wipe the dalvik and cache, and that was the result i planned to downgrade to 2.3.6 then stuck at googleboot so what i did is flash miui 1.12.2 and thanks God and miui my phone starts again. This my first to flash a kernel, and maybe that was the problem
[Nexus S Android Development] 93ae8074:
You are describing the opposite experience that is happening to me. And I'm in stock 4.0.3 too.

EDIT: I've to say that after that, today, I'm having a lot of reboots while in the middle of a conversation. So, back to V2.2
[Nexus S Android Development] renna1992:
would you recommend deleting battery stats after flashing v2.3 over v2.2 without a rom change?
[Nexus S Android Development] l don.tee l:
liking this kernel so far! However, I am running into a slight problem with voodoo colors. I changed my colors back to pre 2.3.3, but upon reboot, Voodoo doesn't save my color profile and defaults it back to the ugly yellow tint that I hate. Eze, would you happen to know if this a voodoo problem or possibly maybe a bug in the kernel?
[Nexus S Android Development] Icecoldmeat:
Still got a freeze when changing frequency to 1200... :(
[Nexus S Android Development] lukappaseidue:
:( still freeze and reboot.

using the latest 2.3 GLaDOS on rom stock

everything stock

no OC/UV

only lazy governor

and min 400 max 1000 freq.

receiving a call I was not able to answer ... I had to push power button twice and than I was able .
[Nexus S Android Development] qtwrk:
first of all i was running brainmaster's MIUI with Franco's kernel , stuck on google logoafter flash GlaDOS

and then i reflash ROM with its default kernel which doesn't not have deep idle all that kinda stuff , but still stuck on google logo after i flash GlaDos.

well , i still like 2.3.7 ,and feel kinda strenge with ICS's new UI, and i didn't see what good for ICS so far ...
[Nexus S Android Development] mike216:
2.3 alpha 17 I9020t, so far so good, thanks ezekeel!

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] FL0OD:
What ICS rom are you using?

°•neXus S4G•°
[Nexus S Android Development] :
thx man now it works :)
[Nexus S Android Development] mike.b93:
can i delete the media folder in the zip?
[Nexus S Android Development] lukappaseidue:
stock ROM 403
[Nexus S Android Development] nexusphone:
you can
[Nexus S Android Development] ragnarokx:
I'm getting a loud burst of static for about half a second after my notification sound goes off. This happens will all notifications, but doesn't happen when selecting a sound in settings - only when I get a text, etc.

I'm on Peter Alfonso's 12-22 nightly, and when I flashed his ROM again to overwrite Glados, the problem stopped.

Edit: interesting - after a while the problem started again, so I guess it isn't kernel related. I might have to try flashing a different ROM.
[Nexus S Android Development] SwatMaster:
Changing voltages using NSTools works now, but with SetCPU I still get freeze+reboot.

Anyway I get random reboots after a small change of voltages (-0.050v for all frequencies).
[Nexus S Android Development] got2best:
I used to get that with nexus beam once in a while

sent from Nexus S i9023 on xda premium

**please remember to hit the thanks button if I helped u**
[Nexus S Android Development] phone_user:
Unlike v2.2, no random reboot so far :)
[Nexus S Android Development] got2best:
Thanks I have been waiting to here this! :) looks like I am going to give it a shot.. may ask tho.. are you using an i9023?

I am
[Nexus S Android Development] phone_user:
No, 9020T :) rom : ICS Peter Alfonso 2011-12-22 / LiveOC 110 (220~880) / deep_idle enabled / lazy / screenoff_maxfreq ON
[Nexus S Android Development] demo23019:
Not sure if any performance tweaks in v.23 because no mention in changelog.

But feels allot quicker all around. And no lag what so ever especially the occasional minor lag when opening the launcher het and there. Also smoother compared to other to builds an d other kernels

BTW using 2.0.3 CFS @ 1.2
[Nexus S Android Development] reddv1:
To fix this problem enable load sound module at boot, this will force voodoo control app to run at boot up and apply the saved colors. It might not work cause I'm not using this kernel to test it.
[Nexus S Android Development] tehgeekguy:
This should work, it's what I did from the beginning and I've never had my voodoo colors not set at boot.
[Nexus S Android Development] Zorrich:
This seems to have something to do with BLN. I tried a few different kernels and it also happens on lucid kernel white, while it does not appear to happen on eugene's kernel.
[Nexus S Android Development] polobunny:
Hey Ezekeel, I've finally experienced SOD while at home. I could verify that indeed I could adb into the phone.

Since I'm using NSCollab, based off CM7, what are my options? Is CM7 simply doomed? I don't recall getting any SOD back when I used netarchy kernels, but then again I wasn't using NSCollab 1.0.50 either...

Thanks!
[Nexus S Android Development] got2best:
Experienced a reboot with screen off.. 2.3 cfs deep idle off

sent from Nexus S i9023 on xda premium

**please remember to hit the thanks button if I helped u**
[Nexus S Android Development] LibertyMonger:
Bfs 2.3 with no issues so far! I had issues with calls this morning on bfs 2.2. rebooting while on a call. All's good for now with 2.3. Loving the smoothness and battery life! Nice work Bud!
[Nexus S Android Development] niteh@wk:
I am running stock ICS 4.0.3. I experienced several random reboots on 2.2 CFS @1.2GHz, default voltage, deep idle off. Most reboots happened while the screen was off. I just updated to 2.3. So far only one reboot while the screen was off. This is a good sign. Really like the Voodoo sound and colors. Thanks for a great kernel!!

Here is the script I run in Rom Toolbox to set my Voodoo colors in case anyone is interested. This isn't mine. It's a collection of several sources, sorry I can't remember those links now.

echo 2863311680 >/sys/class/misc/voodoo_color/red_multiplier

echo 3336681600 >/sys/class/misc/voodoo_color/green_multiplier

echo 3913962240 >/sys/class/misc/voodoo_color/blue_multiplier

echo -33 >/sys/class/misc/voodoo_color/blue_v1_offset

echo -26 >/sys/class/misc/voodoo_color/red_v1_offset

echo -30 >/sys/class/misc/voodoo_color/green_v1_offset

If the script hangs, kill Rom Toolbox and try again. It happens sometime.
[Nexus S Android Development] got2best:
Got another:/ .. what can I do to find the prob.. the phone was in my pocket doing nothing

sent from Nexus S i9023 on xda premium

**please remember to hit the thanks button if I helped u**
[Nexus S Android Development] ranasrule:
which was the last version released for Gingerbread ? Can someone please provide a link ? thanks in advance
[Nexus S Android Development] nexusphone:
1.12

cfs http://db.tt/hGgVCrk7

bfs http://db.tt/JAIThulp
[Nexus S Android Development] ranasrule:
thank you !!!!
[Nexus S Android Development] phone_user:
Eek! got 1 reboot in standby :confused:
[Nexus S Android Development] IIIV:
http://xdaforums.com/showthread.php?p=20560212#post20560212
[Nexus S Android Development] djwyman:
So far I really like this kernal matched with androiduser's aosp+ rom. So far I have not had any reboots which was not the case when I was using matr1x v13.
[Nexus S Android Development] phone_user:
Thanks for pointing that form out :)

************************************************** ************************************************** **********************************

Model: [◆] i9020 // [ ] i9023 // [ ] NS4G

ROM: ______

Scheduler: [ ] BFS // [◆ ] CFS

CPUfreq governor: [ ] ondemand // [◆ ] lazy // [ ] other

Using OC/UV? [◆ ] Yes // [ ] No

Minimum frequency: 200

Maximum frequency: 800

(LiveOC 110 ☞ 220~880, arm_volt 1200 1050 950 stock / int_volt 1100 1100 1100 stock) Rock Stable on GB

[ ] SoD

Can you login with adb shell?: [ ] Yes // [ ] No // [ ] Not tried

If you could, what did the dmesg log say?: _______________

Using screen-off profiles?: [ ] Yes // [ ] No

Using 'screenoff_maxfreq'?: [ ] Yes // [ ] No

Power: [ ] Battery // [ ] USB // [ ] Wall charger/Dock

Problem happens when DEEP IDLE is: [ ] enabled // [ ] disabled // [ ] in both cases

[◆ ] Restart

Problem happens when DEEP IDLE is: [◆] enabled // [ ] disabled // [ ] in both cases

Problem happens when screen is: [ ] on // [◆] off // [ ] in both cases

If it happens while screen is on, what did you do when reboot happened: ___________

If it happens while screen is off, were there any background processes (like music) running?: [ ] Yes // [◆] No

************************************************** ************************************************** **********************************

btw, in spite of setteing "echo 1 > /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq", NSTools shows "not available" in that field
[Nexus S Android Development] SPVlover:
hi all. gota chime in quick.

I am still using 2.2 and had no truble @ all. using live oc 110% bln via bln control deep Idle on ( i am getting deepidle top on /off but no. Idle?)

rom is stock ICS rooted.

working great so far. No reeboots, nice smoothe gaming and excelent stability.

no battery life problems either.

One question are you aware of the v6 supercharger? great optimization script.

howerver, kernelizer dosent seem to work, at least the script tells me so. What could be the cause of this? Could you maybe include some of those tweaks, with consent of the developer, or at least make the script work? let me know if you need more info.

thanx for your fantastic work.
[Nexus S Android Development] aLNG:
screenoff_max is not available for me..is it because of nstools or v2.3? can someone confirm this?
[Nexus S Android Development] 93ae8074:
NSTools problem.
[Nexus S Android Development] aLNG:
thanks..just found that out also..gotta use terminal then
[Nexus S Android Development] lukappaseidue:
Hi Ezekeel. It will be useful placing the form at 1st or 2nd post ;)
[Nexus S Android Development] AeroEchelon:
For GlaDOS v2.2 BFS

Model: [*] i9020 // [ ] i9023 // [ ] NS4G

ROM: BrainMaster's ICS

Scheduler: [* ] BFS // [ ] CFS

CPUfreq governor: [ ] ondemand // [* ] lazy // [ ] other

Using OC/UV? [ ] Yes // [ *] No

Minimum frequency: 100

Maximum frequency: 1000

[* ] Restart

Problem happens when DEEP IDLE is: [ *] enabled // [ ] disabled // [ ] in both cases

Problem happens when screen is: [ ] on // [* ] off // [ ] in both cases

If it happens while screen is off, were there any background processes (like music) running?: [ ] Yes // [* ] No

Other Notes:

I've uninstalled Google Talk w/ Video Hardware Controls to enable DEEP_IDLE TOP =OFF

Also, I noticed that I can get TOP=OFF without a bluetooth killing script. Does that mean the BT bug is fixed. I'm not quite sure what happened.

Regarding DEEP_IDLE in NSTools: Could anybody tell me what "Avg(ms) is?" I understand that Time(ms) is the total time in the respective state, though I'm not sure what the other time means.
[Nexus S Android Development] byrko:
Custom Voltage doesn't work here. With NSTools changing from 96 to 100 hasn't any effect.

Shouldn't it work?

Have I missunderstood the changelog:

"Custom Voltage version 1"
[Nexus S Android Development] furiannn:
From other posters Ive read, apparently you cant get 100% anyway, it's just cosmetic, as if you charge a battery to 100% it would drastically reduce the life of it. This is apparently the case for a lot of things.
[Nexus S Android Development] Tzorg:
Changing 96 to 100 where exactly within NSTools? The only 96 in NSTools I can think of is BLX or maybe Live OC and none of them are related to voltages ...
[Nexus S Android Development] byrko:
Battery Life Extender

---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------

If 96% is maxium of the battery in fact, 100% should be desplayed because maxium possible is arrived, IMHO.
[Nexus S Android Development] Tzorg:
BLX is not related to voltages, so I think you are getting confused with that entry in the OP.

The nexus s will only ever charge to like 96 to prevent damage to the battery and extend its lifespan (thus the BLX name), some kernels include a cosmetic change that shows 100 when it's at 96 but I think this is not part of GlaDOS.

Hope that helps.
[Nexus S Android Development] djjonastybe:
Is anyone else having random reboots all the time? It happens when screen is off or sometimes when screen is on too.

Most of the time I don't notice it.
[Nexus S Android Development] TrueYears:
What are some stable undervolting settings with this rom?
[Nexus S Android Development] caliban2:
2.3 seems to have fixed it for me, running stable for 14 hours or so. Cfs, lazy, didle and Max_freq. Rest is stock.

Let's see if it really stopped rebooting or just was in a good mood... ^^
[Nexus S Android Development] alienmind:
I'm having them. sorry for not using the bug template but not on the PC atm. Stock config, no UV, no OC. Ondemand governor, no deep sleep. 5 reboots straight. I plugged the phone and it stopped, so no logcat.

I was with 90% batt.

Thanks for your work.

Swyped from my Nexus S