yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] dsellers2:
These two screen shots are beautiful. This means I will be getting over a day and a half of use again out of my phone before recharging. : )

View attachment 824443

View attachment 824442
[Nexus S Android Development] polobunny:
Washed out colors are washed out though. :p
[Nexus S Android Development] hispeedworm:
i disabled auto brightness and i still get random green or weird colors flash at screen lock with voodoo colors... but i do agree that there is something funky going on with autobrightness in ICS . turning it off makes screen better in visibility
[Nexus S Android Development] Zorrich:
I disagree. I am running voodoo colors now with the new voodoo plus app and they look fantastic, AND they stick. No need for a script or anything... works just as it did on GB.

Running Pete's ICS ROM, and GLaDOS v 2.2.

EDIT: As for the green flash, I just stopped using auto brightness (which is too low anyways) and it went away. I have my brightness set to ~30%.
[Nexus S Android Development] IIIV:
Also, I'm using the latest version of Voodoo Control Plus, which now supports NS on ICS 4.0.3. I don't think the free version supports it.
[Nexus S Android Development] dsellers2:
I'm using alt setting in voodoo. I turn brightness down and it got rid of my screen flicker. I can handle these colors. B
[Nexus S Android Development] d_phekt:
You're one of the few lucky ones then. I have Voodoo Control Plus and no matter what I try, including adjusting or disabling auto brightness nothing works. It definitely does not work as well as it did with GB... we could adjust the hell out of it, but now its almost a useless function. ICS and the kernels are all pretty new, so I'm sure in time there will be a fix.
[Nexus S Android Development] Zorrich:
Just encase it helps, here are my settings:

Punchy Setting, with RGB of 322, 322, 429. As I said previously, auto brightness is off and brightness set to 30%.
[Nexus S Android Development] polobunny:
That's weird, the first screenshot still looks washed out for some reason, at the bottom mostly. :confused:
[Nexus S Android Development] hachoo:
Can't get this kernel running for more than 12 hours on stock voltages. Using NexusBeam ROM.
[Nexus S Android Development] kashifsiddique:
Nstools' Touch wake is not working on this kernel, i'm on nexus beam rom 4.1.0 and this kernel, i have i9023. hmmmm i wonder why...
[Nexus S Android Development] mike216:
No I actually read it somewhere. I don't claim to know a lot but was trying to help as no one else posted any opinion. So kernel pro could you give us your opinion? Why do you stick only with BFS?

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
Battery life is good voodoo colors stick after a reboot and work well for me as long as you don't go to high on the gamma hack,I heard some say to disable auto brightness and to choose voodoo profile in color profile. I just hope you keep the color driver in there! I'm sure you don't like all the questions about getting rid of the green screen. Thanks ezekeel 2.2 is solid on alpha 17 ,liveoc at 110 without touching the volts.

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
Touch wake and all mods are working for me and have been since the last couple releases so maybe try flashing again

Ezekeel I see when we flash the kernel cleans out files that could be there from previous kernels but does it also wipe the cache and dalvik cache? I've been wiping them anyways but was just wondering,thanks

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] LibertyMonger:
Its weird everything is super great except can't access any data on 3g only with wifi. Status shows I have 3g but it doesn't show 3g next to the signal bars. Calls and texting is fine. Not saying its the kernel since no one else is having this issue. I forget the name of my ROM its ics v17 something LOL. So many of them with long names

*** edit

It says mobile data -unknown in my quick settings. I'm registered on the network. All settings are good.
[Nexus S Android Development] caliban2:
Had 3 reboots during standby with 2.2 in the last 10 hours. Disabled Didle now, let's see if it's the cause.

Once I checked stats, I had a few ms of top-on - thought that's disabled in 2.2? BT and GPS have been disabled the whole day.

No complaints apart from that.
[Nexus S Android Development] d_phekt:
Ouch! You obviously aren't familiar with who morfic is. i completely understand you were trying to help someone, but you might wanna do some research before you say things like that about one of the most respected devs around.
[Nexus S Android Development] Zorrich:
I'm sure Mike knows exactly who morfic is as we have all most likely tried and loved his work. I think what he was getting at is that if your going to make such an aggressive statement as morfic did, he should at least provide a little bit of info/perspective for us to learn from him.
[Nexus S Android Development] onasri15:
Rebooted during phone call twice today, and once while on standby. I have deep idle on, is that the problem? Also have setcpu profiles set up if that makes a difference.
[Nexus S Android Development] atn0716:
I am using 2.2 with lazy 5percent live oc stock volt and frequency, deep idle enabled. No reboot so far since last night. Wifi and 3g works fine. I'm also using nexus beam ics .
[Nexus S Android Development] polobunny:
He just repeated what brainmaster wrote. Stop picking on poor Mike for nearly quoting him while trying to help. ;)
[Nexus S Android Development] IIIV:
Just because he's a dev doesn't give him the right to be a *****.
[Nexus S Android Development] Jayrod1980:
I still can't for the life of me get live oc to work. Tried opening and closing cam etc. What's the magic formula for this
[Nexus S Android Development] dsellers2:
Maybe it's the stock Screenshot app....or maybe it's my phone. :) No worries, I'm still in love with my Nexus S
[Nexus S Android Development] mike216:
Read carefully! I said to morfic that if that statement by me isn't true then ok but please tell me why he puts out only BFS kernels. I know who morfic is going all the way back to the beloved vibrant days and I appreciate morfic so take it easy and read more carefully before you get on me! Thanks zorrich,IIIV and polobunny!

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] polobunny:
I imagine that's what counts in the end. Just found it weird. Looking at the second screenshot it doesn't seem to be there though. Maybe that's some sort of scrolling glow thingamajig. :p
[Nexus S Android Development] got2best:
I am convinced my phone does not like 2.2 haha.. I tried cm9 alpha 17 with 2.2 2 reboots so far this morning while it was in my pocket.. put 2.0 back on with cm9 alpha 17 still no reboots so far.. idk why..
[Nexus S Android Development] d_phekt:
I wasn't getting on you Mike. I get what you are saying and agree. I guess what I meant was that we (as in all of us) could probably use different words or comments sometimes to get help. You are a lot of help to a lot of us too. I wouldn't take that from you and would stick up for you also.
[Nexus S Android Development] :
I also reboots, especially when I make a phone call
[Nexus S Android Development] d_phekt:
What model phone are the guys experiencing this using?
[Nexus S Android Development] got2best:
I have an i9023
[Nexus S Android Development] d_phekt:
Correct me if I'm wrong, but it seems like its mostly the i9023's that are experiencing most of these issues.
[Nexus S Android Development] :
device I9023

device I9023
[Nexus S Android Development] got2best:
I think you are right the weird part tho is 2.0 gives me no problems
[Nexus S Android Development] d_phekt:
I forget a lot too, but it is usually best to add what device you are using when posting bugs/issues so its easier to pinpoint what the cause could be which could result in quicker fixes... just a reminder for everyone... including myself.
[Nexus S Android Development] michalurban:
Freez

Hi, I`m kinda new (returning after a year or so) to android. I`ve had Nexus S for about a month without any problem with either 2.3.6 and 4.0.3 stock ROM. Now, I rooted and tried the CFS 2.2 version of this kernel and just after 20 minutes, I tried to wake my phone up and it was frozen, I had to remove the battery. I believe I read something about this "deep sleep" something problem, could it be related? Any advice please?

I`m 9023, Czech Rep, EU ... :)
[Nexus S Android Development] shubu000:
my i9020T has the same problem too, but that was with 2.1

did you guys have the problem on 2.2?
[Nexus S Android Development] technogravy:
Just wiped and flashed 2.2 after using 2.1 for a few days, seems as smooth as 2.1 will use it and report back.

Testing on Nexus Beam 4.1
[Nexus S Android Development] Soy_Filipo:
Whats do es cfs and bfs means?

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] invd:
http://forums.miuiandroid.com/showthread.php?3520-Difference-Between-BFS-amp-CFS
[Nexus S Android Development] sumeetchawla:
Finally flashed the kernel with NexusBeam 4.0.1

A nub question, what's the advantage of installing a custom kernel other than overclocking the processor?

P.S.: I know Voodoo drivers are pretty good from what I have heard.. Need to check them out.
[Nexus S Android Development] atn0716:
Have you try nstool? From market.
[Nexus S Android Development] mike216:
I9020T AND ON 2.1 I got the reboots on calls only so far 2.2 is solid! No reboots BUT I don't make a whole lot of phone calls?

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] HeavenlyWinds:
Battery life, Overall speed (without even overclocking), Ezekeels Mods (by using NsTools availble on market), Vodoo Controls, Ram improvements, Governer control...and of course overclocking/undervolting

@Ezekeel, did a fresh wipe yesterday. No reboots on Nexus Beam and running very smooth. Battery life is also decent. Thanks
[Nexus S Android Development] Ezekeel:
Thanks for your feedback.

I am currently running GLaDOS BFS V2.2 on the stock ROM and experiencing no issues at all (even using an OC value of 120).

If you are having serious problems like SoDs or restarts and have OC/UV, try the stock settings and see if that solves the issue. Next time you have a SoD connect the device to USB and try to login with adb shell - if that works, take a look at the dmesg log. If you are using the BFS version, try CFS. If you use a custom ROM, try the stock one.
[Nexus S Android Development] mike216:
As you stated voodoo sound and color! Can't live without it, backlight dimmer, touch wake and most of all speed and battery life

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
I think a better question is why wouldn't you run a custom kernel like ezekeels beast lol....

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] DaX05:
Give CM9 Alpha 17 a try. Its insane with your 2.2 :)

I'm still drooling.

Beamed from my Nexus S
[Nexus S Android Development] Psych0Chimp:
Have you got deep idle on?

I was running CFS v2.2 on the stock ICS ROM with stock CPU/voltage, lazy governor and kept getting reboots every 20mins.

Strange how the stability can vary so much...

I'll give BFS a go and see how it goes!
[Nexus S Android Development] terryhau:
You realize, if you take a screenshot on your device, it will turn out exactly the same. How the display is adjusted doesn't have any affect on the screenshot. If you turn the brightness on your monitor down to 0 and take a screen shot, it's not going to come out all black.
[Nexus S Android Development] sumeetchawla:
Yup, just downloaded the NSTools.. in the process of learning how to use it efficiently :) Also, I have the SLCD version of NS, so will the voodoo graphics driver have the same effect it has on the AMOLED one?

Thanks for the info buddy.. Just downloaded the NSTools and Voodoo Controls (was wondering where the controls were :P)

Now need to learn about the NS tools :)

Edit: I just started playing the game FLCommando to test the Voodoo sound and graphics effects.. but it was lagging sometimes, unlike the times I was playing on the stock Kernel? Also it lagged when I pressed the home button to come to the home screen. Did anyone experience any lag while playing this game (If anyone did play this game :P ) or is it just me?
[Nexus S Android Development] Ezekeel:
Yes, I have DEEP IDLE enabled and it works fine (about 1.5h total time in TOP=OFF so far).

Do the reboots only happen when the screen is off or also with screen on? Do you have screenoff_maxfreq enabled (if not, enable it using terminal or adb shell with 'echo 1 > /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq').
[Nexus S Android Development] caliban2:
For me only with screen off and with didle on. None so far with didle off, but too early to be sure.

Thanks for the command, gonna try with didle and Max_freq on instead then. :)
[Nexus S Android Development] seriosbrad:
Is it possible that this kernel is causing the Menu button on my NS to randomly turn off? Back, Search and Home stay lit while Menu goes dark. It's usually easy to fix by just unlocking the phone and hitting a few buttons.

I'm using 2.2 CFS
[Nexus S Android Development] juliano_q:
I had SoD with didle on and off and with no liveoc using the CFS kernel and pete's rom. Sorry, didnt get the logcat, will try to catch it later.
[Nexus S Android Development] kashifsiddique:
I currently using the CFS version. I will try to reflash and use bfs version and do what you said. :o :o
[Nexus S Android Development] Ezekeel:
Since restarts or SoDs seem to be a common problem (at least much more common than on the GLaDOS version for GB and the ICS alpha) please use the following form when reporting such problems so maybe we can see a pattern.

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

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

ROM: ______

Scheduler: [ ] BFS // [ ] CFS

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

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

Minimum frequency: __________

Maximum frequency: __________

[ ] 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

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

If you feel I forgot something important feel free to add any additional information that you think is useful.

Also note that some of these question above are 'trick questions'. If you use OC/UV, do not use lazy with screenoff_maxfreq or use screen-off profiles, I will tell you to fix that first. So, no OC/UV, no screen-off profiles and lazy as CPUfreq governor with screenoff_maxfreq enabled, please.
[Nexus S Android Development] :
good idea .. you are a big;)
[Nexus S Android Development] LibertyMonger:
Hi, I posted earlier that I had lost my 3g but just wanted to restate that as I suspected, it wasn't caused by the kernel. I reflashed everything to try and narrow down the cause and finally flashed back to stock Gb and got my 3g back. I am thinking that when I flashed [ROM] [i9020] CyanogenMod 9 v4.0.3 Alfa 17 I had 2g box checked and didn't realize it and maybe that was the cause. I never check the 2g box so not sure how it was but after flashing back to my previous ROM I checked the settings and sure enough it was checked. Not sure if it could be the case even after I wiped everything but seems it might make a little sense. So now gonna try again and can't wait to get back on this super kernel! Thanks for your work ezekeel much appreciated Buddy

***EDIT I had the 2g box checked on my stock GB before I flashed the ICS ROM and maybe it caused the permanent 3g loss

***Edit

I got it figured out, it was my apn, I simply just had to change the apn type to default. I didn't realize apn settings for nexus s would be different than my old XT720. Sorry for the nonsense lol.
[Nexus S Android Development] mike216:
That's weird it would come all the way over to ICS but good to see you fixed it!

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] onasri15:
All my answers are in red. Hope this covers a few people's issues. Just want to write that it rebooted only twice today, but thought you'd like to know.

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

ROM: _Nexus Beam 4.1 (always flash latest)_

Scheduler: [ ] BFS // [!!] CFS

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

I have Setcpu profiles set up. 400/100 lazy for time 2-7am, screen off, and in call

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

[Twice after calls ] SoD

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

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

Note: Didn't see this with my earlier comment

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: Usually calls, once when browsing and sending texts.

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

I hope it helped.
[Nexus S Android Development] onasri15:
How do I get charging to stay at 100% and not 96
[Nexus S Android Development] wildestpixel:
There is no 100% otherwise your battery will be killed quickly. Any Roms allowing 100% are cosmetic only. 96% is real maximum.
[Nexus S Android Development] Ezekeel:
Everything points to the profiles being the problem. Use lazy with screenoff_maxfreq enabled instead. Do not use profiles, they are unnecessary and only lead to instabilities.

Also a significant portion of the people with problems are running the Nexus Beam ROM. It might just be a coincidence, but I would recommend trying another ROM preferably stock.
[Nexus S Android Development] :
************************************************** ************************************************** **********************************

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

ROM: Pete Alfonso's 12-20-2011

Scheduler: [ ] BFS // [x] CFS

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

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

[ ] SoD

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

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

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

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

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

[x] Restart

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

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

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

[I set max CPU freq = 800]

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

I've reproduced this several times where if I set max CPU to 800MHz, the phone freezes and either reboots or I have to remove the battery. Thanks!
[Nexus S Android Development] Ezekeel:
Did you use an app to set it? Try setting it manually using adb shell or terminal with 'echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq' as root.
[Nexus S Android Development] yaronyud:
is there any reason that since flashing the kernel the phone works slower then version 1.10
[Nexus S Android Development] XxSilent22xX:
If the battery is done charging then it should read 100% not 96% period. even if it is a "cosmetic" fix wouldnt the battery showing 100% be more logical then 96% when charged i mean I would be pissed if I filled my car up and the gas gauge only showed 3/4.
[Nexus S Android Development] :
Yup. i used NS-Tools. I tried using a terminal emulator to change it as you said but it crashes instantly.
[Nexus S Android Development] arifhn:
I tought i found the problem that causing crash

Its caused by su, but this is only happened if we use su programmatically to write the value, not happened in shell (I still can't found the reason)

I can confirm this, because after I chmod those file permission via shell, and use nstools modified version that don't use root for writing, it can work.

Edit:

Confirmed!!

I'm using Android Terminal Emulator to set the value (not adb), and boom.. it was restarted
[Nexus S Android Development] kashifsiddique:
Who has the link of glados version 2.1? i need the file. please. thanks
[Nexus S Android Development] michalurban:
battery mess

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

ROM: Pete Alfonso's 12-20-2011

Scheduler: [ ] BFS // [x] CFS

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

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

[ ] SoD

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

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

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

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

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

[ ] Restart

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

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

PROBLEM: I use 2.2 CFS without rebooting. No overclock, 25mV UV on all values. 10 hours ago I removed the phone from wall charger. 8 hours ago I went to sleep with 88 percent of battery ... now I have 72 percent with Battery info saying the phone is 4 hours off the charger. Weird.

EDIT: According to betterbatterystats, there was no app making the phone to be on. Also, there is a jump in battery use graph, about 10 percent straight down, which I believe could be restart ...
[Nexus S Android Development] phone_user:
CFS version http://www.multiupload.com/EXH0K62THP

BFS version http://www.multiupload.com/WB7HJVG3BB
[Nexus S Android Development] kashifsiddique:
thanks a lot phone. :) :)
[Nexus S Android Development] djjonastybe:
I actually had a strange thing. This night, my device was turned off when I wanted to go to the toilet... I'm still waiting to report. I want to make sure I didn't turn it off myself.

Ezekeel if you want I could make a free website you can use for error reporting. Or I can share my personal website with you if you want to use it. I use htttp://www.frihost.com as a free host. It still takes a week for approval.
[Nexus S Android Development] caliban2:
Trying to keep this short: :-)

I get no SoD's at all or reboots while using the phone in any form. Just reboots in standby, both with only didle on and with didle plus Max_freq. Governor is lazy, everything else is untouched. Most of the time the reboots happen on battery, but had 2 or 3 on wall charger as well.

I disabled didle and max-freq now and intend to test how it does the next 10, 12 hours.
[Nexus S Android Development] lukappaseidue:
even here. 9020T rom stock 403 and glados 2.2 cfs -

everything is default value, no OC or UV!

Reboot of the NEXUS when cell is in standby mode :(
[Nexus S Android Development] bub181:
Is there any chance of patching this kernel up to kernel version 3.0.1.3 from eugene?
[Nexus S Android Development] roshga:
Soon version 3.1.x is out so maybe we should wait for that one